Database Users

[Q] Reliability of TWRP??????

Question is basic; can someone with experience please give me the low-down when it comes to TWRP? I am new to Android in the sense but consider myself somewhat tech savvy. I test software and provide technical support for a living so I completely understand that people can do some dumb stuff. Just yesterday I had a man on the phone trying to connect his Pidion PDA to a McDonalds Wi-Fi by standing in his front yard and pointing it in the direction of a McDonalds two miles away. Anyhow I got the device for X-mas and have spent every day since reading about constant issues using TWRP. I’m really just trying to figure out if the blame for these issues can be pinned down on either the recovery itself or the fact that Millions of these things are in the hands of people who should probably not be doing the things they are doing at their current levels of knowledge, or a combination of both? I have owned a Moto-Triumph for a few month and have flashed Roms & Kernels out the Wahoo using CWM and have become very comfortable with its reliability but had not heard of TWRP until a few weeks ago and the association I have goes with all the stuck on Yellow Triangle posts covering just about every forum. I have TWRP installed and running CM7 and if this was my phone I would have flashed 2 Roms by lunch but for the reasons above feel like I should have a day set aside for trouble shooting before considering doing a simple thing like restoring a stock Nandroid. I lucked out with the Phone having an unlocked loader and Sudo installed out the box. Sorry I tend to rant but am basically asking that if I know my way around Roms and CWR will I be OK using TWRP or should I expect that it will have the occasional hiccup or is unstable in any way?

chairshot215 said:
Question is basic; can someone with experience please give me the low-down when it comes to TWRP? I am new to Android in the sense but consider myself somewhat tech savvy. I test software and provide technical support for a living so I completely understand that people can do some dumb stuff. Just yesterday I had a man on the phone trying to connect his Pidion PDA to a McDonalds Wi-Fi by standing in his front yard and pointing it in the direction of a McDonalds two miles away. Anyhow I got the device for X-mas and have spent every day since reading about constant issues using TWRP. I’m really just trying to figure out if the blame for these issues can be pinned down on either the recovery itself or the fact that Millions of these things are in the hands of people who should probably not be doing the things they are doing at their current levels of knowledge, or a combination of both? I have owned a Moto-Triumph for a few month and have flashed Roms & Kernels out the Wahoo using CWM and have become very comfortable with its reliability but had not heard of TWRP until a few weeks ago and the association I have goes with all the stuck on Yellow Triangle posts covering just about every forum. I have TWRP installed and running CM7 and if this was my phone I would have flashed 2 Roms by lunch but for the reasons above feel like I should have a day set aside for trouble shooting before considering doing a simple thing like restoring a stock Nandroid. I lucked out with the Phone having an unlocked loader and Sudo installed out the box. Sorry I tend to rant but am basically asking that if I know my way around Roms and CWR will I be OK using TWRP or should I expect that it will have the occasional hiccup or is unstable in any way?
Click to expand...
Click to collapse
I have had no hiccups or any other problem, backing up. restoring or flashing.​

TWRP is awesome, backups and restores work great. The main issues are people getting stuck in fastboot, which is not really a TWRP issue. As long as you follow directions, you should have no issues.
Sent from my Kindle Fire (CM7) using xda premium

borborpa said:
TWRP is awesome, backups and restores work great. The main issues are people getting stuck in fastboot, which is not really a TWRP issue. As long as you follow directions, you should have no issues.
Sent from my Kindle Fire (CM7) using xda premium
Click to expand...
Click to collapse
I feel the same way as the OP. I have cwr on my phone and I have never messed up anything. I have roms backed up and I can always get up and running quickly. I have tried half assed roms just for the heck of it and no problem.
I don't think that TWRP is the same kind of program as CWM. I think it's almost impossible to brick my phone using clockword mod but I don't think the same can be said for TWRP. I have read so many posts with people who have TWRP installed and yet they manage to "brick" their device. I don't know if it's a TWRP issue or that the kindle is very sensitive. Nevertheless, I am not rooting it because of these issues, besides, I like stock (I would love swype, that's about it).

Twrp works great. They forgot to set it to change bootmodes leaving recovery so don't use apps to force into recovery. Just firefirrfire.
Most issues, are user errors. I haven't had one issue, and I test everything!
Sent from my Kindle Fire using xda premium

although I havent had any issues (that I can think of) with twrp, the constant "cannot mount /misc !" really bothers me. twrp is on several devices and from what I understand about it... the dev responsible for twrp being on the kindle fire joined twrp, got it working for the fire, they rolled out twrp 2.0 then he quit the team to make a recovery + app he plans on being paid only. so with that said... who knows if twrp will be maintained for the fire?
I hate to bash on anyones work, I didnt have any problem flashing zips with it. I dont really backup/restore much but the few times I tried, it worked. I really like the fact it can be themed easily

foxdog66 said:
although I havent had any issues (that I can think of) with twrp, the constant "cannot mount /misc !" really bothers me. twrp is on several devices and from what I understand about it... the dev responsible for twrp being on the kindle fire joined twrp, got it working for the fire, they rolled out twrp 2.0 then he quit the team to make a recovery + app he plans on being paid only. so with that said... who knows if twrp will be maintained for the fire?
I hate to bash on anyones work, I didnt have any problem flashing zips with it. I dont really backup/restore much but the few times I tried, it worked. I really like the fact it can be themed easily
Click to expand...
Click to collapse
That's a great concern. Which is why I've been Working with doomlord to bring clockworkmod to our kindle fires. We need support. Twrp does not have that. But it works.
Sent from my Kindle Fire using xda premium

Thanks for the responses; I think my fears stem from unfamiliarity. Like I said above everything was easily with my Triumph, was able to install CWM without Rooting the stock Rom and outside of doing something dumb like frying the CPU always felt comfortable knowing I could easily get back up and running no matter how bad I messed things up. I’m sure I will be fine, just need to get used to doing things a little differently and school myself on ADB and Fastboot and as recommended above avoid any apps or options for rebooting into recovery.

I haven't had any issues with twrp so far. Installing was a little tricky when i got stuck at the yellow triangle but after that everything has been good so far.

I have TWRP on both my kindle fire and my wife's and neither has had a single issue with it. My brother, who is not what I would call tech savvy, installed it onto his just a couple days ago without issue by reading the instructions and multiple threads posted around here without issue. I think a lot of the issues come from people not reading as closely as they should or just from getting overly excited about being stuck in fastboot.
Sent from my MB860 using Tapatalk

I would like to put twrp on my phone. It works great. Half of what cwm does fails on my phone. Twrp works every time. People having issues likely can't follow instructions and don't have the knowledge if adb to fix their mistakes
Sent from my SGH-I897 using xda premium

all win
TWRP is all win. If you follow directions to a T and dont frustrated it will work fine. In alot of ways TWRP is better than CWM.

The TWRP team is maintaining TWRP. Even though the head developer left, If you would have read there tweets they are taking some time off. They Even Had announced a Twrp 3 for release, But for now everything is onhold until the team is better organised.If a developer would contact the team for the source, the xda community can keep it maintained.

[SOLVED] **6.3 Can't run Market/Google Play**

Hey everyone,
Since rooting my Kindle (v 6.3), I was hoping I could be all fancy and have the Android Market - or Google Play if you will - but it seems my Fire doesn't agree with this. I've tried downloading and installing two separate versions of the Market - each launched but then came back with a force close error.
I've tried running the processes in KFU a few times but nothing seems to have changed.
Anyone have any ideas on how I would go abouts getting get working?
Thanks a lot in advance

BIGboy! said:
Hey everyone,
Since rooting my Kindle (v 6.3), I was hoping I could be all fancy and have the Android Market - or Google Play if you will - but it seems my Fire doesn't agree with this. I've tried downloading and installing two separate versions of the Market - each launched but then came back with a force close error.
I've tried running the processes in KFU a few times but nothing seems to have changed.
Anyone have any ideas on how I would go abouts getting get working?
Thanks a lot in advance
Click to expand...
Click to collapse
Same here... you're not alone.
In fact, I've been having all kinds of issues this morning. I've even tried flashing other roms to see if I can get Gapps there, but Hellfire didn't have Market. No idea why... I'm flashing the stock update.zip right now. I'm just going to wait this one out.

You can't just install the market apk... there's other things that are needed for it to work.. just Google gapps.zip and flash them in recovery... and Hellfire rom dose have market you have to follow thee directions in the OP
Sent from my HellfireKindle using Tapatalk 2

I had the same problem. This is how I fixed it.
Follow these instructions given by ndpete. Follow the first set of steps then use option 2.
Remember to give ndpete a thumbs up.

That works, or you can just root, mount rw, add the googleservicesframework and vending apk 's to /system/app, mount ro, and reboot. Then run market in go launcher and on the second or third run it will update to google play and you're set.

I too am having a seemingly impossible time getting Android Market (Play) to work. I'm kind of a newb so don't totally understand the directions in this thread.
KFU 0.9.5 was supposed to add the market, but it didn't in my case. In fact, it didn't put the Superuser utility on my Fire either, although all other steps seemed to work fine so I assume I am rooted.
Any help is appreciated.

Flash MoDaCo Gr8. Its the stock 6.3 ROM rooted and tweaked with GApps preloaded. I've been running it for a few days now and it works flawlessly. It still uses the Amazon launcher, and you can still do prime videos with OTA rootkeeper. Look in the dev thread.
Sent from my Kindle Fire using XDA

Thanks a lot to everyone

Fix
Going off of what other's said here:
Great big thanks to Vashypooh for helping me out on IRC, and a giant thanks (though I can't find the buttom for it) to ChodaBoyUSA's post on "6th April 2012, 05:49 PM".
Was trying to get Play on my wife's new Kindle and couldn't get it to recognise. Deleting the drivers and reinstalling (like ChodaBoyUSA states) was the trick. From there I still had some issues with installing the Gapps, and a good friend of mine (don't think he's on here) pointed me to this:
Unfortunately, I can't post URLs yet, so just google for this package.
"gapps-ics- 20120317-signed.zip"
Using the delete drivers trick, and this package worked. Up and running now.

Thanks so much, ndpete's solution totally worked! I'd give him and his posts a thumbs up if I could but I dunno how, so thanks!

Wow, its been a while since my old 8125..Kindle Fire question JB

Hi Guys,
First time back here since I used to mod my Cingular 8125/8525 etc...then hopped on the Apple Bandwagon from day1. I have still tinkered and have always found answers but for once I am STUCK!
I have a Kindle Fire with TWRP 2.2.0
Bootloader 1.4a
Trying to put Jelly Bean on it...
The one from these boards causes my screen to flash then cuts out the kindle.
The one from "otter" just played the beautiful loading screen until the battery dies.
Does anyone see anything wrong from my config here? Ive wiped all my caches, started from scratch...nothing seems to work.
Please help!
Thanks...

I installed a C9 mod that just sits at the video splash screen as well...
Why am I stuck at the loading videos? They just play eternally....
lame!

phathead785 said:
Hi Guys,
First time back here since I used to mod my Cingular 8125/8525 etc...then hopped on the Apple Bandwagon from day1. I have still tinkered and have always found answers but for once I am STUCK!
I have a Kindle Fire with TWRP 2.2.0
Bootloader 1.4a
Trying to put Jelly Bean on it...
The one from these boards causes my screen to flash then cuts out the kindle.
The one from "otter" just played the beautiful loading screen until the battery dies.
Does anyone see anything wrong from my config here? Ive wiped all my caches, started from scratch...nothing seems to work.
Please help!
Thanks...
Click to expand...
Click to collapse
Did you do a factory reset?
sent from my Nokia 5110

Flash the latest TWRP someone made a zip at the end of the topic and also wipe everything (system, cache / dalvik, factory).
JB installed fine on my kindle. The only problems I have are connecting to Enterprise WPA2 spots (PEAP).

pbailey212 said:
Did you do a factory reset?
sent from my Nokia 5110
Click to expand...
Click to collapse
this.

Possible Bricked Nexus 7 Please Help!

Hi guys,
I could really use some help. I have researched this for a couple hours and could not much information on the subject. I rooted my nexus 7 and I was attempting to flash a ROMbut I don't think I installed it right so I tried to restore it from the recovery tool but as the device rebooted it just got stuck on the Google boot screen/logo. The reason I was trying to recover it was because when I installed BAMF ROM through ROM Manager it would only me install one file at a time so I just installed the main ROM file and then I figured I would install the Google apps ROM file and the patch. The reason why I did this was because before I tried installing all the 3 files at the same time using twrp2 and it created same issue but instead it would go as far as the nexus logo and just hang. But I managed to restore/recover it. Well after I installed the BAMF ROM everything was working great EXCEPT there was no Google apps! It wouldn't let me setup my Google account and just download my old stuff. There was nothing on the screen except for a couple apps but I couldn't see the ROM manager or anything else. So I was stuck so I decided to just try and recover but I think something went wrong. Ok...now that all that is out of the way here is what I can do.. When I try to get into recovery or fast boot mode it works BUT then I try to access the recovery mode and it wont let me. It will just reset and go to the Google loading screen and hangs. If I plug the device into the USB I can hear the ding but I dont see it come up on "My Computer" under devices. I have read that you can still recover a bricked Nexus as long as it comes up as Android ADB Interface (Unspecified) and when I look at its properties it gives me a Hub and Port #. Is there anything I can do to fix it??? Any advice is greatly appreciated!
I attached some images for what its worth..

gr090401 said:
Hi guys,
I could really use some help. I have researched this for a couple hours and could not much information on the subject. I rooted my nexus 7 and I was attempting to flash a ROMbut I don't think I installed it right so I tried to restore it from the recovery tool but as the device rebooted it just got stuck on the Google boot screen/logo. The reason I was trying to recover it was because when I installed BAMF ROM through ROM Manager it would only me install one file at a time so I just installed the main ROM file and then I figured I would install the Google apps ROM file and the patch. The reason why I did this was because before I tried installing all the 3 files at the same time using twrp2 and it created same issue but instead it would go as far as the nexus logo and just hang. But I managed to restore/recover it. Well after I installed the BAMF ROM everything was working great EXCEPT there was no Google apps! It wouldn't let me setup my Google account and just download my old stuff. There was nothing on the screen except for a couple apps but I couldn't see the ROM manager or anything else. So I was stuck so I decided to just try and recover but I think something went wrong. Ok...now that all that is out of the way here is what I can do.. When I try to get into recovery or fast boot mode it works BUT then I try to access the recovery mode and it wont let me. It will just reset and go to the Google loading screen and hangs. If I plug the device into the USB I can hear the ding but I dont see it come up on "My Computer" under devices. I have read that you can still recover a bricked Nexus as long as it comes up as Android ADB Interface (Unspecified) and when I look at its properties it gives me a Hub and Port #. Is there anything I can do to fix it??? Any advice is greatly appreciated!
I attached some images for what its worth..
Click to expand...
Click to collapse
Boot loader okay, plug into computer and try accessing recovery through boot loader again. It should work as there is a bug in the boot loader.
Sent from my Nexus 7 using xda app-developers app

You have to use the factory image Google has provide to get out of this. Google search on how to use the factory image. It will erase and reset your nexus 7 like if it was straight out of the box.
Sent from my LG-P999 using xda premium

[Q] multirom +n4 halp

Hi, I wanted to reply in the multirom thread but can't because I am still too newb. Hopefully someone here can point me in the right direction? I've tried everything I know how to do. I really appreciate any help I can get!
So here is my problem. I downloaded multirom for my n4, then I updated. I reopened, and noticed I had the red line of text saying I was missing a kernal or something, so I clicked that and install (so instead of just updating the app I updated my kernal? and I also clicked update recovery). I needed to finish in recovery mode so it rebooted. Then it soft bricked. It goes to the load screen (with countdown timer) and then just black screens indefinitely tmk (5+ minutes of adhd agony). I had already downloaded cm 10.2 and gapps on the device in preparation for multirom, so I rebooted into recovery again, launched multirom and added cm 10.2 with gapps. I first tried with sharing kernal because I don't have my laptop to install 4.3 .tar, but that failed, so I installed ROM without sharing kernal. It runs fine, except I can't use bluetooth or wifi... so it really doesn't run fine =/ everything else seems okay though.
All my data is already backed up on my hdd so no worries on losing that, but I would like my phone functioning sooner than later.
I'm on vacation and don't have laptop with me, any ideas on how I can fix this? I have my Nexus 7 too, so I can download stuff, but I don't know how to:
a) install 4.3 so I can get cm 10.2 fully running?
b) reinstall 4.4.2 to stock (I tried factory reset but it didn't do anything either)
I think the biggest problem is lack of laptop because I could easily just reset the phone with that and run my nandroid (which is on laptop too.... ftl) but if there is a solution please let me know! Thanks!!!

krkeco said:
Hi, I wanted to reply in the multirom thread but can't because I am still too newb. Hopefully someone here can point me in the right direction? I've tried everything I know how to do. I really appreciate any help I can get!
So here is my problem. I downloaded multirom for my n4, then I updated. I reopened, and noticed I had the red line of text saying I was missing a kernal or something, so I clicked that and install (so instead of just updating the app I updated my kernal? and I also clicked update recovery). I needed to finish in recovery mode so it rebooted. Then it soft bricked. It goes to the load screen (with countdown timer) and then just black screens indefinitely tmk (5+ minutes of adhd agony). I had already downloaded cm 10.2 and gapps on the device in preparation for multirom, so I rebooted into recovery again, launched multirom and added cm 10.2 with gapps. I first tried with sharing kernal because I don't have my laptop to install 4.3 .tar, but that failed, so I installed ROM without sharing kernal. It runs fine, except I can't use bluetooth or wifi... so it really doesn't run fine =/ everything else seems okay though.
All my data is already backed up on my hdd so no worries on losing that, but I would like my phone functioning sooner than later.
I'm on vacation and don't have laptop with me, any ideas on how I can fix this? I have my Nexus 7 too, so I can download stuff, but I don't know how to:
a) install 4.3 so I can get cm 10.2 fully running?
b) reinstall 4.4.2 to stock (I tried factory reset but it didn't do anything either)
I think the biggest problem is lack of laptop because I could easily just reset the phone with that and run my nandroid (which is on laptop too.... ftl) but if there is a solution please let me know! Thanks!!!
Click to expand...
Click to collapse
WHY DID THE ERROR HAPPENED?:Because multirom app sets the default kernel to 4.2.2 one, since you werent on 4.2.2 it soft bricked.
DO I NEED TO REINSTALL STOCK TO GET CM FULLY WORKING?: Nope, just search in the general section of our device, for the hybrid modem thread, download the hybrid .84 and flash on recovery
PS: I think you will need OTG to pass the file from your n7 to your n4 since no bluetooh,no data and no wifi....
Or search like crazy around google to see if there is a way to pass files thru nfc

Thanks for the quick reply, is that the 27 or the 33 / 84 download?
sites.google.com/site/bpearuploads/
Or does it not matter?

opssemnik said:
WHY DID THE ERROR HAPPENED?:Because multirom app sets the default kernel to 4.2.2 one, since you werent on 4.2.2 it soft bricked.
DO I NEED TO REINSTALL STOCK TO GET CM FULLY WORKING?: Nope, just search in the general section of our device, for the hybrid modem thread, download the hybrid .84 and flash on recovery
PS: I think you will need OTG to pass the file from your n7 to your n4 since no bluetooh,no data and no wifi....
Or search like crazy around google to see if there is a way to pass files thru nfc
Click to expand...
Click to collapse
Got it figured out thanks to your help!