Related
I'm very new to android and have been using Clockworkmod Recovery basically since day 3 or 4 since I got my HTC One XL...
I'm just wondering how many of you are using TWRP instead of Clockworkmod Recovery.. and if so, do you recommend me flashing that instead of CWM?
I have no real complaints with CWM and dont mind using the volume keys to navigate. But besides that, are there any real advantages besides the touch interface?? also, can someone post a link where i can find TWRP ?
thanks guys!! I LOVE the community on here!! it's great!!!
also, when people refer to "Touch Recovery" are y'all referring to TWRP ?
trichrome1 said:
I'm very new to android and have been using Clockworkmod Recovery basically since day 3 or 4 since I got my HTC One XL...
I'm just wondering how many of you are using TWRP instead of Clockworkmod Recovery.. and if so, do you recommend me flashing that instead of CWM?
I have no real complaints with CWM and dont mind using the volume keys to navigate. But besides that, are there any real advantages besides the touch interface?? also, can someone post a link where i can find TWRP ?
thanks guys!! I LOVE the community on here!! it's great!!!
also, when people refer to "Touch Recovery" are y'all referring to TWRP ?
Click to expand...
Click to collapse
I personally use twrp I like its setup look and feel and it is a little speedier than cwm when making backups, flashing etc in my opinion. I used cwm on every phone I had except this one x. After twrp was introduced I switched and love it.
Sent from my HTC One X using xda premium
i believe CWM is also touch screen, just no buttons, so you gotta be careful not push a wrong link - but they have conf screen as well.... haven't tried TWRP - would also like to know if it has any advantages... thanks!
will try
eraste said:
I personally use twrp I like its setup look and feel and it is a little speedier than cwm when making backups, flashing etc in my opinion. I used cwm on every phone I had except this one x. After twrp was introduced I switched and love it.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks for the reply,
I'm going to flash twrp and try it out.. see what I think. I'm just enjoying playing with my phone
twrp ?
Can someone point me into the right direction to TWRP..
I can't seem to find a download link anywhere..
and correct command is ..
fastboot flash recovery twrp_file_name.whateverextentionis
?
trichrome1 said:
Can someone point me into the right direction to TWRP..
I can't seem to find a download link anywhere..
and correct command is ..
fastboot flash recovery twrp_file_name.whateverextentionis
?
Click to expand...
Click to collapse
here ya go http://forum.xda-developers.com/showthread.php?t=1677447
All needed info is there or the links provided there to the official page of TWRP
attempting first backup
just backed up my current rom... twrp seems a little more thorough with more options and there's even a progress bar when backing up.
eraste said:
here ya go http://forum.xda-developers.com/showthread.php?t=1677447
All needed info is there or the links provided there to the official page of TWRP
Click to expand...
Click to collapse
Would i able to flash CWM one click again....? did u ever try to go back to CWM....?
ted77usa said:
Would i able to flash CWM one click again....? did u ever try to go back to CWM....?
Click to expand...
Click to collapse
No never went back. Not sure what the process would be to get back to CWM. Dont see why the one click wouldnt work but dont take my word for it dont want to give any wrong information.
eraste said:
No never went back. Not sure what the process would be to get back to CWM. Dont see why the one click wouldnt work but dont take my word for it dont want to give any wrong information.
Click to expand...
Click to collapse
I'm just curious....but so far i have no problem with CWM....if ain't broke don't fix it right.....
trichrome1 said:
just backed up my current rom... twrp seems a little more thorough with more options and there's even a progress bar when backing up.
Click to expand...
Click to collapse
Just FYI... u can't restore ur CWM back up file with TWRP.... it's totally different
process
ted77usa said:
Would i able to flash CWM one click again....? did u ever try to go back to CWM....?
Click to expand...
Click to collapse
to go back to CWM, all you would need to do is place the CWM.img in the fast boot folder, and
go to the dir where u have fastboot files (mine is c:\fastboot ) but i am also running a virtual machine on a mac.. process should be the same since i'm still using windows..
anyways in command prompt.. navigate to c:\fastboot
and then,
fastboot flash recovery CWM.img
(or whatever your clockworkmod recovery image is named)
I haven't tried this, but it's how i originally flashed cwm and it's how i just flashed twrp.... so far it's sweet, a lot more options as well.. don't see myself going back anytime soon. (sorry cwm devs, still love cwm)
trichrome1 said:
to go back to CWM, all you would need to do is place the CWM.img in the root of your sdcard on the phone, and
go to the dir where u have fastboot files (mine is c:\fastboot ) but i am also running a virtual machine on a mac.. process should be the same since i'm still using windows..
anyways in command prompt.. navigate to c:\fastboot
and then,
fastboot flash recovery CWM.img
(or whatever your clockworkmod recovery image is named)
I haven't tried this, but it's how i originally flashed cwm and it's how i just flashed twrp.... so far it's sweet, a lot more options as well.. don't see myself going back anytime soon. (sorry cwm devs, still love cwm)
Click to expand...
Click to collapse
+1. Yea it's easy to flash back and forth between recoveries. Just do it the same way you flash the first one.
cwm twrp incompatibility
ted77usa said:
I'm just curious....but so far i have no problem with CWM....if ain't broke don't fix it right.....
Just FYI... u can't restore ur CWM back up file with TWRP.... it's totally different
Click to expand...
Click to collapse
right, wish I'd known that before. I ended up in bootloops when using twrp to ry and restore a cwm nandroid. luckily, i was able to reflash a beans rom and get it running again, but in the process, I believe I have messed up something. the kernel, bootloader, maybe how the file system is set up. dont mix them up. choose one and stick with it.
Well, I'm pretty sure that one, twrp is simpler, more pretty, more useful, faster, easier.
Also Pretty sure cwm in some cases ruins your phone forever.
Go a head and use cwm though.
TWRP has and official release for the One XL although last time I checked CWM only has a port. I highly suggest using TWRP. It should work better
Sent from my HTC One X using xda premium
Another advantage of TWRP is that the sdcard can be mounted while in recovery mode. I don't think that's supported in CWM.
That may be the case for the htc, the thing is, I am on a verizon samsung galaxy s 3.
I wonder if that makes a difference!?
I was reading elsewhere in these forums that the non kexec kernels ( meaning that the bootloader is actually unlocked) don't work as well on twrp
Sent from my SCH-I535 using xda app-developers app
fritzboyle said:
That may be the case for the htc, the thing is, I am on a verizon samsung galaxy s 3.
I wonder if that makes a difference!?
I was reading elsewhere in these forums that the non kexec kernels ( meaning that the bootloader is actually unlocked) don't work as well on twrp
Click to expand...
Click to collapse
Every device is different, this discussion is about the One X(L). If you want more info on CWM vs. TWRP on the Galaxy S3, head over to the forum for your device. Don't follow the GS3, but would assume that its officially supported by CWM (which makes a huge difference). That is not even the case for the One X. Its not yet officially supported, and the CWM we have is just a port. Although an official version is in testing.
redpoint73 said:
Every device is different, this discussion is about the One X(L). If you want more info on CWM vs. TWRP on the Galaxy S3, head over to the forum for your device. Don't follow the GS3, but would assume that its officially supported by CWM (which makes a huge difference). That is not even the case for the One X. Its not yet officially supported, and the CWM we have is just a port. Although an official version is in testing.
Click to expand...
Click to collapse
I needed help how do.you erase battery history with twrp
Sent from my HTC One XL using xda app-developers app
htcbrazilian said:
I needed help how do.you erase battery history with twrp
Click to expand...
Click to collapse
On the main/home TWRP screen, go Wipe>battery stats.
But battery stats get wiped every time you charge the phone, anyway. There is not benefit to wiping it manually: http://www.xda-developers.com/android/google-engineer-debunks-myth-wiping-battery-stats-does-not-improve-battery-life/
I have HTC One X. unlocked bootloader, rooted. Stock version 2.20. Tried to flash CM10 nightly build 01042013 through TWRP. First copied the roms into internal storage. Then used fastboot flash boot boot.img, then entered TWRP to wipe everything, factory reset, then try to flash rom, says error and failed. Tried several times, didn't work. I tried to reboot, the phone enters endless bootloop. Tried to use power+vol to enter fastboot again. Select recovery, phone bootloop, never enters recovery. Then I tried to flash CWM touch to phone. Still cannot enter recovery.
What's worse is that when the phone is on, it cannot charge. When usb is not connected, I can turn the phone off by keep holding power. But once the usb is connected the phone will turn on by itself, and the charging stops -- this way the remaining battery is kept being drained.
Please help! Thanks!!!
Try installing TWRP again via adb.
There is no CWM Touch for our version of the One X (only the non-touch version of CWM, and its not recommended). So you may have flashed a recovery for the wrong device. It doesn't sound like that was the initial cause of your woes, but it may have made the issue worse.
You can also try to relock the bootloader, RUU and start over again (re-unlock, install TWRP and flash).
You sure you downloaded CM10 for our (Snapdragon S4) version, and not the Tegra3 version of the One X? There is no reason that flashing a ROM would mess with recovery, unless you flashed the wrong version.
redpoint73 said:
Try installing TWRP again via adb.
There is no CWM Touch for our version of the One X (only the non-touch version of CWM, and its not recommended). So you may have flashed a recovery for the wrong device. It doesn't sound like that was the initial cause of your woes, but it may have made the issue worse.
You can also try to relock the bootloader, RUU and start over again (re-unlock, install TWRP and flash).
You sure you downloaded CM10 for our (Snapdragon S4) version, and not the Tegra3 version of the One X? There is no reason that flashing a ROM would mess with recovery, unless you flashed the wrong version.
Click to expand...
Click to collapse
I downloaded the ROM through this link
http://forum.xda-developers.com/showthread.php?t=1786696
which brought me to the download site:
http://get.cm/?device=endeavoru
I guess my battery is well below 30% now. I saw people said if I relock it with such low battery, I may end up not able to do anything after. Will that happen? I'll try to flash TWRP first. Thanks
Also, I cannot do adb at this time since I cannot enter system and if I use adb command in cmd on my PC, it says cannot find device.
Do you have a AT&T one x or international? How many cores does it have?
Sent from my HTC One XL using xda app-developers app
HTC One X = International
area51avenger said:
Do you have a AT&T one x or international? How many cores does it have?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
The one is AT&T HTC one x. I think that's the most standard ATT version, I don't know how many cores it has though ..
qb200210 said:
The one is AT&T HTC one x. I think that's the most standard ATT version, I don't know how many cores it has though ..
Click to expand...
Click to collapse
Well if it says AT&T on the top of the phone it's most definitely a dual-core version, instead of the quad-core. But you downloaded a CM-endeavoru ROM which is the international. We here have the device codenamed "evita". It sounds to me that you've bricked your phone, unfortunately. However if it's still booting to the white HTC Screen there might be some hope.
I don't have the link handy, but if you wanna find the unbricking thread, it may help if you have knowledge of Linux
HTC_Phone said:
Well if it says AT&T on the top of the phone it's most definitely a dual-core version, instead of the quad-core. But you downloaded a CM-endeavoru ROM which is the international. We here have the device codenamed "evita". It sounds to me that you've bricked your phone, unfortunately. However if it's still booting to the white HTC Screen there might be some hope.
I don't have the link handy, but if you wanna find the unbricking thread, it may help if you have knowledge of Linux
Click to expand...
Click to collapse
I can still enter fastboot and can flash things into it using cmd from PC usb connection. It's just nothing worked: not able to boot pass htc white screen, keeps rebooting, turns on when usb connected, not able to charge, cannot enter recovery. Tried to re-flash TWRP, didn't work, still cannot enter recovery.
If you can get to fastboot, you're not bricked. Be sure you're pushing the right (Evita) version of TWRP; so far you've loaded your phone up with endeavour stuff.
Does adb devices show your phone? What are you seeing in Device Manager when it's plugged in? Are you sure you have all the HTC drivers installed? You might try switching USB ports and using a different cable.
HTC_Phone said:
Well if it says AT&T on the top of the phone it's most definitely a dual-core version, instead of the quad-core. But you downloaded a CM-endeavoru ROM which is the international. We here have the device codenamed "evita". It sounds to me that you've bricked your phone, unfortunately. However if it's still booting to the white HTC Screen there might be some hope.
I don't have the link handy, but if you wanna find the unbricking thread, it may help if you have knowledge of Linux
Click to expand...
Click to collapse
Thanks for pointing it out. Now I flashed boot.img from evita version and it enters recovery. Now the only question is that how can I download the correct rom into my phone since I don't think I can enter the system? Thanks!
iElvis said:
If you can get to fastboot, you're not bricked. Be sure you're pushing the right (Evita) version of TWRP; so far you've loaded your phone up with endeavour stuff.
Does adb devices show your phone? What are you seeing in Device Manager when it's plugged in? Are you sure you have all the HTC drivers installed? You might try switching USB ports and using a different cable.
Click to expand...
Click to collapse
Now I can enter TWRP, which I used to root this phone before without problems. Now I just need to push the right rom. However, if I choose Mount USB storage, my PC is asking me to format the disk. Should I do that or is there other ways I can push ROM into my phone? Thanks!
qb200210 said:
Now I can enter TWRP, which I used to root this phone before without problems. Now I just need to push the right rom. However, if I choose Mount USB storage, my PC is asking me to format the disk. Should I do that or is there other ways I can push ROM into my phone? Thanks!
Click to expand...
Click to collapse
Now in TWRP, I'm able to use adb push update.zip / to push the CM10 evita ROM into the phone. But when I tried to install, it still reports error:
Updating partition details ...
E: Unable to mount '/sdcard'
E: Unable to mount storage.
E: Mount: Unable to find partition for path '/update.zip'
Error flashing zip '/update.zip'
Updating partition details...
E: Unable to mount '/sdcard'
E: Unable to mount storage.
This happens with or without USB cable connected to PC. Thanks!
Format the sdcard to fat32
Sent from my HTC One XL using xda app-developers app
qb200210 said:
Should I do that or is there other ways I can push ROM into my phone? Thanks!
Click to expand...
Click to collapse
As stated, go ahead and format. It's quite common when having these problems to corrupt your sdcard, esp. when using CWM on this phone.
iElvis said:
As stated, go ahead and format. It's quite common when having these problems to corrupt your sdcard, esp. when using CWM on this phone.
Click to expand...
Click to collapse
Thanks for the tips! Now I formatted it into fat32, reboot into recovery, and I'm able to successfully install the CM10 evita ROM. However, after the reboot, the phone keeps the bootloop. The battery is 50% +. Is there something else I did wrong? Thanks!
qb200210 said:
Thanks for the tips! Now I formatted it into fat32, reboot into recovery, and I'm able to successfully install the CM10 evita ROM. However, after the reboot, the phone keeps the bootloop. The battery is 50% +. Is there something else I did wrong? Thanks!
Click to expand...
Click to collapse
Did you remember to flash the boot.img separately?
iElvis said:
Did you remember to flash the boot.img separately?
Click to expand...
Click to collapse
Yes, I did that. But CM10 didn't work whatever I tried. Then I flashed boot.img of CleanROM and installed CleanROM. Finally it works! Thanks a lot for all the help!
dan6677 said:
HTC One X = International
Click to expand...
Click to collapse
What??? Incorrect, and how can an AT&T user be saying this? The dual core S4 version is called the One X in US (AT&T) and Canada (Rogers), and called the One XL elsewhere.
Outside Canada and US, its true that One X refers to the quad core Tegra3 version. But the term "international" is a bit obsolete at this point, now that the S4 version has been released in some 6 or 7 countries.
The OP said he was on stock 2.20 firmware, which is AT&T. So I knew he had the AT&T version from the start.
To the OP, stick with ROMs and mods from this forum section to avoid the same mistake in the future: http://forum.xda-developers.com/forumdisplay.php?f=1538
---------- Post added at 10:17 PM ---------- Previous post was at 10:14 PM ----------
qb200210 said:
Yes, I did that. But CM10 didn't work whatever I tried. Then I flashed boot.img of CleanROM and installed CleanROM. Finally it works! Thanks a lot for all the help!
Click to expand...
Click to collapse
I know in the past, at least one nightly build of CM10 had a faulty kernel that caused the phone to be stuck on the boot splash. Flashing an older kernel made the ROM boot right up. Maybe that is the case with the one you tried. Or maybe just a bad download.
qb200210 said:
I have HTC One X. unlocked bootloader, rooted. Stock version 2.20. Tried to flash CM10 nightly build 01042013 through TWRP. First copied the roms into internal storage. Then used fastboot flash boot boot.img, then entered TWRP to wipe everything, factory reset, then try to flash rom, says error and failed. Tried several times, didn't work. I tried to reboot, the phone enters endless bootloop. Tried to use power+vol to enter fastboot again. Select recovery, phone bootloop, never enters recovery. Then I tried to flash CWM touch to phone. Still cannot enter recovery.
What's worse is that when the phone is on, it cannot charge. When usb is not connected, I can turn the phone off by keep holding power. But once the usb is connected the phone will turn on by itself, and the charging stops -- this way the remaining battery is kept being drained.
Please help! Thanks!!!
Click to expand...
Click to collapse
I had the same issue today, was trying to flash jellybam. I fastboot flash boot boot.img then entered TWRP and wiped then flashed the ROM and when I tried booting up I was in a boot loop. What I did is entered boot loader mode and factory reset ( which wiped my internal storage) and then I was able to enter recovery.
Sent from my HTC One XL using Tapatalk 2
qb200210 said:
Yes, I did that. But CM10 didn't work whatever I tried. Then I flashed boot.img of CleanROM and installed CleanROM. Finally it works! Thanks a lot for all the help!
Click to expand...
Click to collapse
Glad to hear you got it working. Too many damn bricks around these parts for my taste.
Hello guys, as the title suggest i can't mount any partition on my tab...
i'm using TWRP 2.4.4.0 and i'm on the 4.2 JB bootloader...
what should i do to get it working again?
also in the bootloader i can see this
Code:
Key driver not found... Booting OS
Android cardhU-user bootloader <1.00 e> released by "WW_epad-10.6.1.8-20130225" A03
matt95 said:
Hello guys, as the title suggest i can't mount any partition on my tab...
i'm using TWRP 2.4.4.0 and i'm on the 4.2 JB bootloader...
what should i do to get it working again?
Click to expand...
Click to collapse
As long as you can use fastboot, replace it with the version that works on your bootloader:
TWRP 2.4.4. 0-4.2.
CAREFUL: A lot of people bricked their tablets in this state.
Read one of the many threads on this particular issue.
Sent from my TF300T using Tapatalk HD
i've tried to flash the new recovery but it remains always the same, for instance i've flashed the 2.5.0.0 4.2 version but every time i boot into recovery it says TWRP 2.4.4.0 (which is the one i had before)
matt95 said:
i've tried to flash the new recovery but it remains always the same, for instance i've flashed the 2.5.0.0 4.2 version but every time i boot into recovery it says TWRP 2.4.4.0 (which is the one i had before)
Click to expand...
Click to collapse
Weird.
Are you using fastboot to flash?
What messages are you getting from fastboot?
Sent from my TF300T using Tapatalk HD
Code:
ERROR: could not get pipe properties
and then it flashes it correctly but nothing seems to change
matt95 said:
Code:
ERROR: could not get pipe properties
and then it flashes it correctly but nothing seems to change
Click to expand...
Click to collapse
OK, so flashing fails silently for some reason.
Do you see the blue flash bar on the bootloader screen, when fast boot says "writing"?
Never had any fastboot issues on Linux, but I have seen lots of people having issues with drivers on Windows. If you are using Windows, you might want to read up, how to make sure you have the proper drivers installed.
Short of that, no idea. :-/
Maybe can you post the full output of fastboot?
Should not be more than a couple of lines, right?
Sent from my TF300T using Tapatalk HD
i'm not at home now, i'll post them as soon as i get to it...
anyway i used MacOs, Linux and Windows
Make sure you're using the newest fastboot. There may be a bug on your current version.
Back in August I soft-bricked my tablet - no recovery and no ADB access. Fastboot would turn on on the tablet, but fastboot on my computer (Debian) kept hanging on "waiting for device". I had used fastboot on the same computer a couple weeks earlier to flash a recovery, and lsusb showed all the correct device info, so I thought fastboot was broken on the tablet and I was SOL. Well, fastboot got added to the Debian repos at some point, and I installed that version. 8 months and 2 fastboot updates went by before I even attempted to fix my tablet again (2 weeks ago), but somehow it worked, and I now have an awesome tablet to play with. I have no idea what happened with fastboot when my tablet first bricked, but I can only assume that one of the fastboot updates fixed a nasty bug that only showed up when I bricked the tablet.
I know your device is being recognized by fastboot, and your situation is much different than mine was, but you could be experiencing a completely different bug.
EndlessDissent said:
Make sure you're using the newest fastboot.
Click to expand...
Click to collapse
Good point!
matt, any progress?
http://forum.xda-developers.com/showthread.php?p=40809070
mb it will help you
sorry guys today i was very busy, i'll try to solve it tomorrow
matt95 said:
sorry guys today i was very busy, i'll try to solve it tomorrow
Click to expand...
Click to collapse
In your bootloader, what version of ASUS firmware does it say you are running. It makes a big difference for which version of TWRP you should be using.
edit:
sorry in your first post i could see you listed it, I think you may be getting this besause you dont have the TWRP version for 4.2 jellybean. the versions that are compatible are labeled -4.2 at the end.
here is the link for the right twrp for asus firmware 10.6.1.8 - http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
Version 2.5.5.0-4.2. of twrp is only compatible with the update for our tab that came out last week-asus firmware 10.6.1.15.3
CBank said:
In your bootloader, what version of ASUS firmware does it say you are running. It makes a big difference for which version of TWRP you should be using.
edit:
sorry in your first post i could see you listed it, I think you may be getting this besause you dont have the TWRP version for 4.2 jellybean. the versions that are compatible are labeled -4.2 at the end.
here is the link for the right twrp for asus firmware 10.6.1.8 - http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
Version 2.5.5.0-4.2. of twrp is only compatible with the update for our tab that came out last week-asus firmware 10.6.1.15.3
Click to expand...
Click to collapse
at first i didn't install the correct TWRP but now i can't even flash the correct one that's my problem
I believe this may be the same issue that alot of devices suffered from when the 4.2.1 update first came out.
Here is a thread on the issue
http://forum.xda-developers.com/showthread.php?t=2179874
From what I understand it seems that the 4.2.1 bootloader changed the way that the partition table was setup and thus all previous versions of custom recoveries could not mount any partitions (twrp would ask for password & not be able to mount any partition & cwm also not able to mount any partition) and a new twrp-4.2 version had to be made specifically for the 4.2.1 bootloader.
Still not sure as to why this caused the fastboot issue with the majority of people that flashed an incompatible version of twrp or cwm.
The fastboot issue I am talking about is that when you use the "flash" command everything will seem to go fine , it will say writing... and successful on the command prompt but you will not get any blue progress bar on the tablet itself and after the flash command has completed the fastboot reboot command will not reboot the tablet. Which I find very odd as other fastboot commands will still work without issue.
The only know solution if this is the issue you have is to replace the motherboard.
pjc21 said:
The only know solution if this is the issue you have is to replace the motherboard.
Click to expand...
Click to collapse
bad news
matt95 said:
bad news
Click to expand...
Click to collapse
Well, don't give up yet. That there is no known solution does not mean we can't find any.
If fastboot is broken, can you access via adb, while in recovery?
Also there was a thread on unbricking with fastboot issues. Might try that:
http://forum.xda-developers.com/showthread.php?t=2236885
Sent from my TF300T using Tapatalk HD
i'm able to use adb and also fastboot commands... the recovery however do not work obviously because it isn't the right one... i'm here on xda since 2010 and i still make such mistakes stupid me
matt95 said:
i'm able to use adb and also fastboot commands... the recovery however do not work obviously because it isn't the right one... i'm here on xda since 2010 and i still make such mistakes stupid me
Click to expand...
Click to collapse
Just shows that it can happen to the best of us!
Why don't you try the method from the thread in my last post?
Seems the guy had the same issue with fastboot and solved it.
Sent from my TF300T using Tapatalk HD
i'll definitely try that method! i'll let you know, thanks guys
matt95 said:
i'll definitely try that method! i'll let you know, thanks guys
Click to expand...
Click to collapse
I'm in the same situation that you're in. I can send simple fastboot and ADB commands to the tab but as soon as I try to write anything, it just freezes and requires a hard reset. You'll find that you will be able to erase and send simple reset/info request but no write commands. You'll be able to erase your recovery partition but you will not be able write anything new to it. Good luck!
I ordered a MB from ebay last night. Now I just need to find a guide on replacing it.....
Hello,
My One SV:
Android 4.2.2 Stock
Moonshine S-Off
HtcDev Unlocked
Custom recovery (TWRP 2.7)
Rooted
When my battery goes to 0% and the phone shuts down, when I plug the USB cable, the phone shows the battery charging sign and then starts in recovery mode, BUT the touchscreen doesn't work, the volume buttons don't work, only the power button works. I always have to wait a few minutes for it to charge up (showing in TWRP 3%+, otherwise it will not power on), remove the battery and the USB cable, put the battery in and power it on, then plug in the USB cable to continue charging.
I have to mention that this was happening also when it was:
Android 4.1.2 Saturn III something mod
S-On
HtcDev Unlocked
Custom recovery (clockworkmod)
Rooted
I've bought this phone second-hand, so I don't know how it behaved when was fully stock.
Thanks,
Sebastian.
The TWRP build you are using doesn't have the proper offmode charging binary. There is a TWRP version which has been built for your device that shall solve this problem for you but I unfortunately do not have the link since it is based on the international K2 variants and I am on a US version.
Another method would be to unpack the TWRP recovery, and unpack your stock 4.2.2 based recovery. Swap the kernel binary from stock recovery over to custom recovery. Then, decompress the ramdisk for both. Swap out the binaries inside the ramdisk as well.
Take note on what arguments you must use to rebuild your stock 4.2.2 based recovery because you must rebuild TWRP using those same arguments. If you do it correctly then this should also resolve your issue.
If you know how to build TWRP from source then I would update the source to reflect more so on 4.2.2. That would be the preferred method if necessary.
Modding.MyMind said:
The TWRP build you are using doesn't have the proper offmode charging binary. There is a TWRP version which has been built for your device that shall solve this problem for you but I unfortunately do not have the link since it is based on the international K2 variants and I am on a US version.
Another method would be to unpack the TWRP recovery, and unpack your stock 4.2.2 based recovery. Swap the kernel binary from stock recovery over to custom recovery. Then, decompress the ramdisk for both. Swap out the binaries inside the ramdisk as well.
Take note on what arguments you must use to rebuild your stock 4.2.2 based recovery because you must rebuild TWRP using those same arguments. If you do it correctly then this should also resolve your issue.
If you know how to build TWRP from source then I would update the source to reflect more so on 4.2.2. That would be the preferred method if necessary.
Click to expand...
Click to collapse
Well, mine is k2_u. Does that change anything?
fbpw131 said:
Well, mine is k2_u. Does that change anything?
Click to expand...
Click to collapse
Nope
Modding.MyMind said:
Nope
Click to expand...
Click to collapse
I've misunderstood, my bad.
Well, I've unpacked my TWRP image, it shows a lot of files, however, if I unpack my "recovery.img" stock recovery, it's "ramdisk" folder it's empty.
Bummer
fbpw131 said:
I've misunderstood, my bad.
Well, I've unpacked my TWRP image, it shows a lot of files, however, if I unpack my "recovery.img" stock recovery, it's "ramdisk" folder it's empty.
Bummer
Click to expand...
Click to collapse
So.. before I started installing ubuntu in dualboot with my windows, I checked old.splatterhand's posts, and as always, he posted the compiled version link in this post: http://forum.xda-developers.com/showthread.php?p=41456540#post41457062
Everything works nice now.
fbpw131 said:
So.. before I started installing ubuntu in dualboot with my windows, I checked old.splatterhand's posts, and as always, he posted the compiled version link in this post: http://forum.xda-developers.com/showthread.php?p=41456540#post41457062
Everything works nice now.
Click to expand...
Click to collapse
The version you have linked is for boost, not for k2u
old.splatterhand said:
The version you have linked is for boost, not for k2u
Click to expand...
Click to collapse
ooops, i guess that's why I lost all my data, it changed the partition somehow and it got wiped.
Yup, bad idea!
old.splatterhand said:
Yup, bad idea!
Click to expand...
Click to collapse
So I should flash the old recovery back, the one with the battery issue
At least that.
And pray that no important partition is wiped!
old.splatterhand said:
At least that.
And pray that no important partition is wiped!
Click to expand...
Click to collapse
Too late for praying, it's back on and seems fine. What should I check to make sure I'm ok?
The ones from here don't work: https://goo.im/devs/OpenRecovery/k2_u/
fbpw131 said:
The ones from here don't work: https://goo.im/devs/OpenRecovery/k2_u/
Click to expand...
Click to collapse
Use the twrp from 1. post of my thread you have linked.
And live with this bug, its only cosmetical. Or try to find someone who can fix it.
old.splatterhand said:
Use the twrp from 1. post of my thread you have linked.
And live with this bug, its only cosmetical. Or try to find someone who can fix it.
Click to expand...
Click to collapse
It's more than a visual bug. I need to pull out the battery for the phone to restart. I'll be living with it.
I've lost only some music and a bloons td 5 savegame but I could have lost much more. I have Sky/One Drive for my photos.
I'll wait and see if someone will ever build it. I should be able to compile it myself, but it's better if someone that really knows those config params do it. I'm done messing, this was as close to a brick as it can get. Lucky me!
fbpw131 said:
It's more than a visual bug. I need to pull out the battery for the phone to restart. I'll be living with it.
Click to expand...
Click to collapse
Don't put your phone off for charging. I never did and never noticed that bug
I'll wait and see if someone will ever build it. I should be able to compile it myself, but it's better if someone that really knows those config params do it. I'm done messing, this was as close to a brick as it can get. Lucky me!
Click to expand...
Click to collapse
I also think so, thats why i never messed with recoveries or kernels
old.splatterhand said:
Don't put your phone off for charging. I never did and never noticed that bug
Click to expand...
Click to collapse
It happens when my battery goes empty. This happens because of another bug.
Well, i don't know how often you use TWRP to flash things or make a backup. But a workaround could be, to use the stock recovery and only use TWRP when you need it.
So, where could find the stock recovery firmware?
Inside this firmware.zip - 33.62 MB
It's possible this is also somewhere else, but I am having trouble finding it....so I gave up and figured I'd ask.
Okei. I started with TWRP 2.8.6.1. So from my understanding flashing a modem does not work in versions of TWRP newer than 2.8.6.0. I get that, and so I decided to downgrade. However, that seems to be the version that I am unable to get working. I've attempted to flash the 2.8.6.0 recovery via fastboot. Everything says it's good in my terminal. So I go ahead and boot into recovery, but my phone goes to a black screen for a moment and then reboots into OS. I tried a different method, via the app from the google play store. It tells me that there is an error of some sort, or that I already have it installed. So I used the google play app to install 2.8.6.1, which worked flawlessly. So now I am back where I started.
Is there some trick to getting specifically TWRP 2.8.6.0 working so that I am able to use it to flash a different modem? Will using an even earlier version yield the same results? Or am I better off doing it via fastboot?
Thank you for your time <3
Use philz recovery
Myrskyta said:
It's possible this is also somewhere else, but I am having trouble finding it....so I gave up and figured I'd ask.
Okei. I started with TWRP 2.8.6.1. So from my understanding flashing a modem does not work in versions of TWRP newer than 2.8.6.0. I get that, and so I decided to downgrade. However, that seems to be the version that I am unable to get working. I've attempted to flash the 2.8.6.0 recovery via fastboot. Everything says it's good in my terminal. So I go ahead and boot into recovery, but my phone goes to a black screen for a moment and then reboots into OS. I tried a different method, via the app from the google play store. It tells me that there is an error of some sort, or that I already have it installed. So I used the google play app to install 2.8.6.1, which worked flawlessly. So now I am back where I started.
Is there some trick to getting specifically TWRP 2.8.6.0 working so that I am able to use it to flash a different modem? Will using an even earlier version yield the same results? Or am I better off doing it via fastboot?
Thank you for your time <3
Click to expand...
Click to collapse
I too have experienced exactly what you describe and have yet to find a solution. I own 2 OPO's, plus I administer one for a friend who purchased one based on my recommendation. The oldest one I own which was purchased 4 months prior to the others has worked perfectly with any recovery or ROM I've installed on it. It has TWRP-2.8.6.0 installed and has no problems flashing any partition from recovery. My newer handset and my friend's both refuse to boot into recovery with that version installed. It doesn't matter if I flash from fastboot or from TWRP itself. I have no idea why this phenomena occurs on some of these devices, but it makes administering them a more time consuming pain in the ass. I'm going to try Phil's recovery, as was suggested, as a workaround, but I'm dumbfounded as to why the inconsistencies exhibit themselves on particular devices.
Odysseus1962 said:
I too have experienced exactly what you describe and have yet to find a solution. I own 2 OPO's, plus I administer one for a friend who purchased one based on my recommendation. The oldest one I own which was purchased 4 months prior to the others has worked perfectly with any recovery or ROM I've installed on it. It has TWRP-2.8.6.0 installed and has no problems flashing any partition from recovery. My newer handset and my friend's both refuse to boot into recovery with that version installed. It doesn't matter if I flash from fastboot or from TWRP itself. I have no idea why this phenomena occurs on some of these devices, but it makes administering them a more time consuming pain in the ass. I'm going to try Phil's recovery, as was suggested, as a workaround, but I'm dumbfounded as to why the inconsistencies exhibit themselves on particular devices.
Click to expand...
Click to collapse
Well....at least now I know I'm not totally crazy. Thank you~
=)
Ejvyas said:
Use philz recovery
Click to expand...
Click to collapse
Is there any particular reason for Philz recovery over standard CWM?
Also, while this might be a viable option my understanding is that, that would render my old backups useless since I was previously using TWRP? That's kind of unfortunate. =(
Myrskyta said:
Is there any particular reason for Philz recovery over standard CWM?
Also, while this might be a viable option my understanding is that, that would render my old backups useless since I was previously using TWRP? That's kind of unfortunate. =(
Click to expand...
Click to collapse
uploaded the file for you (Take out .apk extension), hope you know how to flash thru fastboot. Else google.
KSKHH said:
uploaded the file for you (Take out .apk extension), hope you know how to flash thru fastboot. Else google.
Click to expand...
Click to collapse
Unfortunately, if that is the same one from twrp's website it isn't going to do me any good. I already attempted that through fastboot. 2.8.6.1 works flawlessly. 2.8.6.0 seems to bootloop once and then toss me back into the OS. Thank you though, I appreciate it.
Had the same problem tried to flash back to 2.8.6.0 via TWRP and didn't work and seemed like recovery had disapeared so used TWRP App to install 2.8.6.1 booted into recovery then rebooted and tried to downgrade to 2.8.6.0 but got a message about same recovery, rebooted phone tried again and it installed no problem.
stylez said:
Had the same problem tried to flash back to 2.8.6.0 via TWRP and didn't work and seemed like recovery had disapeared so used TWRP App to install 2.8.6.1 booted into recovery then rebooted and tried to downgrade to 2.8.6.0 but got a message about same recovery, rebooted phone tried again and it installed no problem.
Click to expand...
Click to collapse
Hmm...maybe I'll give it another shot then. I had opted to just flash them via fastboot because I couldn't get it to work. It's not the worst thing ever. Thank you =)
Myrskyta said:
Is there any particular reason for Philz recovery over standard CWM?
Also, while this might be a viable option my understanding is that, that would render my old backups useless since I was previously using TWRP? That's kind of unfortunate. =(
Click to expand...
Click to collapse
just FYI, philz recovery does support TWRP backups. you just have to enable that feature in the settings
Oh! Thank you for letting me know. I'll keep that in mind. =)
Save yourself all that trouble, just flash modems with fastboot....fastboot flash modem modem.bin