Related
I'm new to this whole flashing custom ROMS business. I have a CDMA HTC Hero 2000 and I downgraded to the original 2.1 before the update just fine, rooted my phone just fine. Then I tried to flash Aloysius to it using instructions I found here: [Complete Guide] How To Flash A Custom ROM To Your Android Phone With ROM Manager + Full Backup & Restore | Android News, Reviews, Applications, Games, Phones, Devices, Tips, Mods, Videos, Podcasts - Android Police
After all was said and done, my phone starts to boot with the "HTC quitely brilliant" logo, following by "SPRINT the Now network" logo and after it shows "Now" for many seconds (as it normally does before pulling up the home screen), it reverts back to the HTC logo and repeats this process until I remove the battery.
I removed the microSD and attempted to boot, same thing. Then I held down HOME+BACK+POWER to do a manual hard reset, this took a little longer but again had the same result.
I may just cry now. Please help!!
Run the official sprint ruu, and see what that does for u. Then read the rooting guide here on xda and try it. I personally recommend amon ra recovery to flash roms, rom manger never seemed to work right. Feel free to pm for more help, dont worry u prob arent bricked unless u flashed a gsm rom (which aloysius isn't)
Sent from my HERO200 using XDA App
That's a bootloop not a brick You could try downloading a different rom and flashing it in recovery, nandroid restoring - if you made one, or flashing the same rom again. just wipe your phone before (data/cache/dalvik)
Didn't get a chance to get on here until now but I fixed it last night.
I did this by going back into reboot recovery mode (by pressing HOME and POWER), going to partition settings, COMPLETELY wiping everything on the sd card, mounting the USB and dragging a new ROM .zip file onto it. (I tired this twice without completely wiping and the phone continued to have problems booting.
The flash worked fine that time and all has been well. Turns out the first one I was trying to apply to it was just an upgrade.
Thanks everyone for your help, makes perfect sense now.
chrisdegraw said:
Didn't get a chance to get on here until now but I fixed it last night.
I did this by going back into reboot recovery mode (by pressing HOME and POWER), going to partition settings, COMPLETELY wiping everything on the sd card, mounting the USB and dragging a new ROM .zip file onto it. (I tired this twice without completely wiping and the phone continued to have problems booting.
The flash worked fine that time and all has been well. Turns out the first one I was trying to apply to it was just an upgrade.
Thanks everyone for your help, makes perfect sense now.
Click to expand...
Click to collapse
Four key words to remember when trying out any new rom
Nandroid is your friend!
additionally, you should always remember to wipe before loading a new rom!
Enjoy!
Yeah, don't ever panic, that was, as everyone said, a bootloop by textbook definition. I've never seen a brick before, but I'm damn sure it won't get as far as the Sprint logo. The only way to brick a CDMA Hero is to flash a GSM Radio/Bootloader to it.
I did look around the LG Thrill forum to find an answer for this and I couldn't find anyone with the same problem I am having. My phone is fully rooted and all the other steps one would take.
I have the custom rom on the SD card, everything is backed up. So when I went to go into recovery mode (Pressing and holding down 3D button, volume down and power at the same time) following the right steps I would only get to the blue screen with just the reboot system now, wipe date, etc. I cannot find anyway getting that main recovery screen to come up.
The full version of Rom Manager isn't getting me to the recovery mode either.
It's been awhile since I been on XDA so I am sorry if this isn't in the correct forum.
Thank you for your time.
Overall, just so I know I am taking the proper steps. Would I need to follow this ]http://forum.xda-developers.com/showthread.php?t=1257588[/URL] if the first step into getting into recovery doesn't work?
So are you saying that you are booting into the stock recovery and not CWM recovery? If so then yes just follow the instructions in that thread.
Sent from my LG-P925 using Tapatalk
Yes, it is that basic recovery (Blue Screen). I will now follow that thread. I have all the ADB software I need to do it. It will be the first time I am ever doing it this way. Thank you for your response.
I installed the beats audio installer and things seemed to be working ok, except that my phone volume was either lower than expected or overly loud where the external speaker had distortion. So I opened the app and clicked uninstall from within it. Afterwards I rebooted my phone as it said and now it's stuck in a bootloop. My brother rooted my phone for me when I went home for a visit for me. I'm not root or phone savvy. I live in South Florida and I can't make the 12 hour drive back there anytime soon. How do I fix this? I had performed a nandroid backup but I noticed my external storage was 100% full after I did that a few times. So I went into storage in settings and deleted the clockwork mod stuff sitting at 6.86 gigs. That must have been the backup in there I know. Now with no backup I did a factory reset, still a bootloop. Phone is rooted still. I'm thinking maybe the audio drivers were damaged. Please help how do I fix this? Thanks!
darinthereal said:
I installed the beats audio installer and things seemed to be working ok, except that my phone volume was either lower than expected or overly loud where the external speaker had distortion. So I opened the app and clicked uninstall from within it. Afterwards I rebooted my phone as it said and now it's stuck in a bootloop. My brother rooted my phone for me when I went home for a visit for me. I'm not root or phone savvy. I live in South Florida and I can't make the 12 hour drive back there anytime soon. How do I fix this? I had performed a nandroid backup but I noticed my external storage was 100% full after I did that a few times. So I went into storage in settings and deleted the clockwork mod stuff sitting at 6.86 gigs. That must have been the backup in there I know. Now with no backup I did a factory reset, still a bootloop. Phone is rooted still. I'm thinking maybe the audio drivers were damaged. Please help how do I fix this? Thanks!
Click to expand...
Click to collapse
I don't think the audio drivers were damaged. A factory reset wipes the /data partition, which is where all the personal data is stored, but it does not touch the /system partition, which is probably where the Beats Audio installs/modifies files, since it probably needs root (I'm just assuming, don't know which app that is nor what it does).
Since you have Clockwork Mod (CWM), I'm assuming your recovery is still working, right? When you start up your phone, the LED should turn on (either blue or purple), and then you should press volume up/down to enter recovery. Do you have an external SD card?
yes I have an external sd card
Antiga Prime said:
I don't think the audio drivers were damaged. A factory reset wipes the /data partition, which is where all the personal data is stored, but it does not touch the /system partition, which is probably where the Beats Audio installs/modifies files, since it probably needs root (I'm just assuming, don't know which app that is nor what it does).
Since you have Clockwork Mod (CWM), I'm assuming your recovery is still working, right? When you start up your phone, the LED should turn on (either blue or purple), and then you should press volume up/down to enter recovery. Do you have an external SD card?
Click to expand...
Click to collapse
Thanks for replying, I'm crushed. When I boot the phone the led goes red then purple. If I hold down volume down and power the purple becomes yellow then it goes into recovery but I have absolutely nothing to backup from. If I reboot it bootloops.
also...
darinthereal said:
Thanks for replying, I'm crushed. When I boot the phone the led goes red then purple. If I hold down volume down and power the purple becomes yellow then it goes into recovery but I have absolutely nothing to backup from. If I reboot it bootloops.
Click to expand...
Click to collapse
The phone says there is no OS now and when I power up it's stuck on the Sony logo. At this point am I able to install a custom rom say a stable version of Kit Kat? If so, where do I find one and how do I install it? I don't know how to get into download mode I'm afraid to because I don't want to hard brick my phone. Thanks!
darinthereal said:
The phone says there is no OS now and when I power up it's stuck on the Sony logo. At this point am I able to install a custom rom say a stable version of Kit Kat? If so, where do I find one and how do I install it? I don't know how to get into download mode I'm afraid to because I don't want to hard brick my phone. Thanks!
Click to expand...
Click to collapse
Ok, since you're talking about custom ROMs, I'm assuming you have an unlocked bootloader. You won't hardbrick your phone unless you mess up real bad, although I am wondering how on earth you ended up with "no OS". That would only happen if you wiped the /system partition. Here's what you're going to do:
1.- Download the links number 1,3 and 4 from this post.
2.- Connect your SDcard to your computer with a USB adapter or an SD adapter, and copy all those downloaded files to your external SD card.
3.- Once that is done, put the SDcard back in your phone, and turn it on and enter recovery.
4.- Navigate recovery with volume buttons up/down and Power button for enter, and select the "Wipe Data" option, which is the same as a Factory Reset (just for good measure, since you already did this); it will ask you to confirm the operation, select "Yes".
5.- Do the same with "Wipe Cache".
6.- Go to "Install ZIP from SDcard1", and, with vol +/- navigate to the file you downloaded in number 1 from the link above (filename should be "LT29i_Rockers_X_ROM_v1.2_03292014-signed.zip"), and press the Power button to confirm that you want to flash that file, then confirm with "Yes".
7.- Once that completes, do the same for the file from number 3 (filename should be "LT29i_9.2.A.1.199_kernel.zip").
8.- Finally, do the same with the file from number 4 (filename should be "UPDATE-SuperSU-v1.94.zip").
9.- Reboot your phone.
It should power up now, and if you have any doubts regarding the procedure, post back and/or read through the original thread here.
I just posted how to do method 2, described in the original link.
EDIT: In my opinion, there is no "stable" version of Kitkat. FXP has a CM11 ROM, but it has kernel issues regarding battery life; if you can live with a battery not lasting more than 7 - 9 hours, maybe you'd want to try that, but I wouldn't recommend it.
http://fxpblog.co/qualcomm-krait-200-family-1st-gen/sony-xperia-tx/
Antiga Prime said:
Ok, since you're talking about custom ROMs, I'm assuming you have an unlocked bootloader. You won't hardbrick your phone unless you mess up real bad, although I am wondering how on earth you ended up with "no OS". That would only happen if you wiped the /system partition. Here's what you're going to do:
1.- Download the links number 1,3 and 4 from this post.
2.- Connect your SDcard to your computer with a USB adapter or an SD adapter, and copy all those downloaded files to your external SD card.
3.- Once that is done, put the SDcard back in your phone, and turn it on and enter recovery.
4.- Navigate recovery with volume buttons up/down and Power button for enter, and select the "Wipe Data" option, which is the same as a Factory Reset (just for good measure, since you already did this); it will ask you to confirm the operation, select "Yes".
5.- Do the same with "Wipe Cache".
6.- Go to "Install ZIP from SDcard1", and, with vol +/- navigate to the file you downloaded in number 1 from the link above (filename should be "LT29i_Rockers_X_ROM_v1.2_03292014-signed.zip"), and press the Power button to confirm that you want to flash that file, then confirm with "Yes".
7.- Once that completes, do the same for the file from number 3 (filename should be "LT29i_9.2.A.1.199_kernel.zip").
8.- Finally, do the same with the file from number 4 (filename should be "UPDATE-SuperSU-v1.94.zip").
9.- Reboot your phone.
It should power up now, and if you have any doubts regarding the procedure, post back and/or read through the original thread here.
I just posted how to do method 2, described in the original link.
EDIT: In my opinion, there is no "stable" version of Kitkat. FXP has a CM11 ROM, but it has kernel issues regarding battery life; if you can live with a battery not lasting more than 7 - 9 hours, maybe you'd want to try that, but I wouldn't recommend it.
http://fxpblog.co/qualcomm-krait-200-family-1st-gen/sony-xperia-tx/
Click to expand...
Click to collapse
YES the bootloader is unlocked my brother did it when he rooted it back home but he's not familiar with many of the custom roms. THANKS! I'm going to try this. I erased the OS last night. Before all of this I installed One Click Scroll from GooglePlay. It worked perfectly but it install TeamWin recovery on my phone and it's still there. I'm not familiar with it at all, but it seems to work perfectly on the device. Ok I'll let you know how it goes thank you even if this doesn't work!
darinthereal said:
YES the bootloader is unlocked my brother did it when he rooted it back home but he's not familiar with many of the custom roms. THANKS! I'm going to try this. I erased the OS last night. Before all of this I installed One Click Scroll from GooglePlay. It worked perfectly but it install TeamWin recovery on my phone and it's still there. I'm not familiar with it at all, but it seems to work perfectly on the device. Ok I'll let you know how it goes thank you even if this doesn't work!
Click to expand...
Click to collapse
Well, directions still apply to TWRP; wipe /data and /cache, flash files in the order posted previously, then reboot. Good luck.
I love you!
darinthereal said:
yes the bootloader is unlocked my brother did it when he rooted it back home but he's not familiar with many of the custom roms. Thanks! I'm going to try this. I erased the os last night. Before all of this i installed one click scroll from googleplay. It worked perfectly but it install teamwin recovery on my phone and it's still there. I'm not familiar with it at all, but it seems to work perfectly on the device. Ok i'll let you know how it goes thank you even if this doesn't work!
Click to expand...
Click to collapse
i love you thank you how do i thank matt?!!!!!!!!!
darinthereal said:
i love you thank you how do i thank matt?!!!!!!!!!
Click to expand...
Click to collapse
Glad to be of help. If you must, just clicking on the "Thanks" button on a post is good, that's what it's for. And you'll have to probably find one of matt's posts too (don't know who you're talking about) and do the same, I guess.
THANKS!
Where is the thanks button? Lol
darinthereal said:
Where is the thanks button? Lol
Click to expand...
Click to collapse
Under each post, left side of the screen.
THANKS!
darinthereal said:
i love you thank you how do i thank matt?!!!!!!!!!
Click to expand...
Click to collapse
JUST CLICKED EVERY THANKS BUTTON THAT I COULD FIND THANK GOD FOR YOU! I had to come to my laptop the thanks button don't show in my mobile boat browser weird. Again thank you dearly Antiga Prime, cool name btw!
Q&A for [RECOVERY] TWP 2.7.1.0 for One Mini 2
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] TWP 2.7.1.0 for One Mini 2. 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!
new twrp's won't work
Hi there,
I just tried to root my htc mini 2 with and it says that it is tampered now and I can't reboot my recovery. So I tried the newest twrp and some in between because I've read in this forum that somebody had the same problem and he just got the newest twrp but that didn't work for me at all.
Is there any way to undo the whole thing by replacing the twrp with the original one or do I have to wait till there is gonna be a root for the htc mini 2?
When I try to recover everything it says that this build is for development purpose only...
Does somebody have an idea?
I would appreciate it a lot if somebody has an idea.
Hornochse7958 said:
Hi there,
I just tried to root my htc mini 2 with and it says that it is tampered now and I can't reboot my recovery. So I tried the newest twrp and some in between because I've read in this forum that somebody had the same problem and he just got the newest twrp but that didn't work for me at all.
Is there any way to undo the whole thing by replacing the twrp with the original one or do I have to wait till there is gonna be a root for the htc mini 2?
When I try to recover everything it says that this build is for development purpose only...
Does somebody have an idea?
I would appreciate it a lot if somebody has an idea.
Click to expand...
Click to collapse
When the bootloader says "tempered" means that it was unlocked. when you see " this build is for development purpose only" its referring to TWRP because you now using a custom recovery. Not sure the nature of your problem but to undo, simply boot into boot loader and flash original recovery.img you can find in the forum.
I can't you open TWRP?
kativiti said:
When the bootloader says "tempered" means that it was unlocked. when you see " this build is for development purpose only" its referring to TWRP because you now using a custom recovery. Not sure the nature of your problem but to undo, simply boot into boot loader and flash original recovery.img you can find in the forum.
I can't you open TWRP?
Click to expand...
Click to collapse
Thank you for the quick respond and I wanted to try and undo everything but no my problem is that my phone completely froze in the twrp screen. I can't do anything, I can't unlock it nor shut down my phone or start the bootloader... that kind of sucks. Any suggestions now? Is it possible to open the htc one mini 2 and take out the battery? or do I have to wait till it runs out by it self and than start it again?
Hornochse7958 said:
Thank you for the quick respond and I wanted to try and undo everything but no my problem is that my phone completely froze in the twrp screen. I can't do anything, I can't unlock it nor shut down my phone or start the bootloader... that kind of sucks. Any suggestions now? Is it possible to open the htc one mini 2 and take out the battery? or do I have to wait till it runs out by it self and than start it again?
Click to expand...
Click to collapse
Read this tread. Someone had the same problem
http://forum.xda-developers.com/one-mini-2/help/rooting-htc-one-mini-2-t2880936
Unresponsive after boot up from dead battery
THanks to U-ra I get the enjoy my fav DSP Viper!!!
Cheers Man,
I have a small niggling problem that I can't work out, My battery tends to die alot, once I place the phone on charge after a flat battery, the phone auto boots to Twp, I am really cool with that but the annoying thing is buttons and screen are unresponsive? I can't do a thing, just have the Twp menu. The power of button does turn the screen off/on but thats its. Tried doing factory resets, reboots holding down power, vol buttons. Just nothing.
only way around it is to use adb and reboot command.
Is anyone else experiencing this problem.
http://forum.xda-developers.com/one...recovery-twp-2-7-1-0-one-mini-2-t2801370/page 4 here's the answer, so far
@u-ra is there any clue about getting official twrp support? (I was thinking about that problem of the self-booting recovery when phone is off and plugged in)
gibihr said:
@u-ra is there any clue about getting official twrp support? (I was thinking about that problem of the self-booting recovery when phone is off and plugged in)
Click to expand...
Click to collapse
I'll try to get to it this weekend.
HELP TWRP stuck at swipe to unlock
Hello all,
for unknown reason the phone restarded and now is stuck at swipe to unlock but it is not working. I try to hold power+volume down, but no way to turn it off. What can I do?
Thanks in advance
PS: well, it restarted... I don't know what happend but now it's ok
sorry for sounding like a newb
i have the verizon htc one remix, which i believe is the same as the one mini 2 . will this work on it?
akubenz said:
i have the verizon htc one remix, which i believe is the same as the one mini 2 . will this work on it?
Click to expand...
Click to collapse
you can try but i think someone here couldn't unlock bootloader trough HTC Dev.
Help: Stock rom updated between boots, TWRP non responsive, fastboot doesnt recognise
Hello to anyone that can help or in a similar situation,
Have brand new HTC one mini 2, rooted. Am trying to install cyanogenmod and followed the instructions on their page. All went well and was ready to flash the rom from TWRP. Decided to do a backup to SD first and then apply super user. Forced to reboot and accidentally let it boot to android (stock rom). Didnt notice the last time i had it booted wifi downloaded a system update which was automatically applied next time i booted into the stock rom after backup and Superuser in TWRP. Rebooted to recovery (TWRP) as soon as i could, but TWRP is no longer responding to touch. I realise i have probably updated the phone to a point where TWRP is no longer working, and i have to use something else to flash my rom. Am trying to flash an updated TWRP or Clockworkmod recovery, but fastboot/adb no longer recognise the device when booted into the stock rom, and when i boot into TWRP (non-responsive) it also doesnt recognise the device attached, even if i catch it before the screen goes black from inactivity. Any suggestions greatly appreciated....
snorglamp said:
Hello to anyone that can help or in a similar situation,
Have brand new HTC one mini 2, rooted. Am trying to install cyanogenmod and followed the instructions on their page. All went well and was ready to flash the rom from TWRP. Decided to do a backup to SD first and then apply super user. Forced to reboot and accidentally let it boot to android (stock rom). Didnt notice the last time i had it booted wifi downloaded a system update which was automatically applied next time i booted into the stock rom after backup and Superuser in TWRP. Rebooted to recovery (TWRP) as soon as i could, but TWRP is no longer responding to touch. I realise i have probably updated the phone to a point where TWRP is no longer working, and i have to use something else to flash my rom. Am trying to flash an updated TWRP or Clockworkmod recovery, but fastboot/adb no longer recognise the device when booted into the stock rom, and when i boot into TWRP (non-responsive) it also doesnt recognise the device attached, even if i catch it before the screen goes black from inactivity. Any suggestions greatly appreciated....
Click to expand...
Click to collapse
A kind member replied to me in another post indicating that fastboot commands only work in the bootloader, and that adb commands only work in TWRP which is why I am having problems re-flashing TWRP (requiring the "fastboot flash recovery TWRP.img" command). However I thought TWRP replaced the bootloader, so I seem to be locked out of re-flashing TWRP because i have TWRP. This seems not to make a lot of sense, can anyone else confirm or otherwise explain what I have misunderstood about that? As stated neither adb nor fastboot recognises the device is attached to the computer any more, so commands are not executing...
snorglamp said:
Hello to anyone that can help or in a similar situation,
Have brand new HTC one mini 2, rooted. Am trying to install cyanogenmod and followed the instructions on their page. All went well and was ready to flash the rom from TWRP. Decided to do a backup to SD first and then apply super user. Forced to reboot and accidentally let it boot to android (stock rom). Didnt notice the last time i had it booted wifi downloaded a system update which was automatically applied next time i booted into the stock rom after backup and Superuser in TWRP. Rebooted to recovery (TWRP) as soon as i could, but TWRP is no longer responding to touch. I realise i have probably updated the phone to a point where TWRP is no longer working, and i have to use something else to flash my rom. Am trying to flash an updated TWRP or Clockworkmod recovery, but fastboot/adb no longer recognise the device when booted into the stock rom, and when i boot into TWRP (non-responsive) it also doesnt recognise the device attached, even if i catch it before the screen goes black from inactivity. Any suggestions greatly appreciated....
Click to expand...
Click to collapse
I think I have found the solution for myself: I went back into the stock rom and did a factory reset (from within android booted up as normal), which after completion rebooted me into TWRP which now works fine (is responding to touch again, and i can flash the Cyanogen image now). Hopefully this helps someone else in this situation one day, or maybe I am the only idiot that needed to ask hehe. I should clarify that after flashing TWRP I lost access to the fastboot screen and could not push anything over ADB or fastboot commands from windows (plugged in via USB). Holding down volume down and power booted directly into TWRP, and i had no way to get to fastboot screen. After doing factory resent from within the Android OS, holding volume down and power booted me to the fastboot screen, and only when I selected "Recovery" did it take me to TWRP, and I was again able to run fastboot and ADB commands from PC. Weird (or maybe not if you know more than me), but there it is...
snorglamp said:
A kind member replied to me in another post indicating that fastboot commands only work in the bootloader, and that adb commands only work in TWRP which is why I am having problems re-flashing TWRP (requiring the "fastboot flash recovery TWRP.img" command). However I thought TWRP replaced the bootloader, so I seem to be locked out of re-flashing TWRP because i have TWRP. This seems not to make a lot of sense, can anyone else confirm or otherwise explain what I have misunderstood about that? As stated neither adb nor fastboot recognises the device is attached to the computer any more, so commands are not executing...
Click to expand...
Click to collapse
Sorry, but it seems to me that you don't know the difference between bootloader and recovery. I apologize if you do. If not, search in CM wikis or ask here for explanations.
corbeau56 said:
Sorry, but it seems to me that you don't know the difference between bootloader and recovery. I apologize if you do. If not, search in CM wikis or ask here for explanations.
Click to expand...
Click to collapse
I do indeed know the difference between the bootloader and recovery, its just that the bootloader (Hboot) was not longer accessible in my situation and TWRP (the recovery) was imposing itself when you would normally expect to find the bootloader (i.e. my bootloader was for all intents and purposes replaced by my recovery, while I am sure this is not true in fact, it was in effect). As I say, doing a factory reset from within the OS restored the bootloader (HBoot) and I was able to continue modding. I am today extremely happy with my fully secured cyanogenmodded HTC One Mini 2 via TWRP recovery method. I hope that is somewhat clearer.
Can you enter bootliader now? I got stuck in a bootloop once and couldn't enter bootloader because I continued pressing power and Volume down like I did on my One S. For Mini 2, we have to hold the Volume UP and Power buttons until HBOOT appears, then release the buttons.
corbeau56 said:
Can you enter bootliader now? I got stuck in a bootloop once and couldn't enter bootloader because I continued pressing power and Volume down like I did on my One S. For Mini 2, we have to hold the Volume UP and Power buttons until HBOOT appears, then release the buttons.
Click to expand...
Click to collapse
That may well have been an alternative solution to my problem, however it was fixed by the factory reset and volume down and power then took me to HBoot (this would appear to contradict what you have said above, but maybe volume down and power does different things depending on how what you have done to the phone, not sure), so I cannot confirm whether or not that also would have worked for me. Good suggestion though, especially if you are not in a position to do a factory reset. and it would certainly be easier if it worked...I am convinced my problem was the result of a conflict between the TWRP version i installed (downloaded from here) and the android update that occurred between boots.
I am indeed able to get into bootloader/hboot and successfully flashed cyanogenmod from TWRP. I can confirm post flashing TWRP and Cyanogenmod, holding volume down and power takes me to HBoot (and then the option to go to fastboot or recovery).
Holding power up and power just loads cyanogenmod for me now as if I had just pressed power.
I thought I should confirm whether or not holding volume up vs volume down with power results in bootloader vs recovery loading. For me, they both took me to TWRP.
Also, TWRP doesnt seem to work on HTC One Mini 2 after you do anything to set up your phone. It just doesnt recognise touch input any more so you cant do anything with it. However the fix i noted earlier (factory reset) even works with other roms installed, confirmed for cyanogenmod 11 and 12 nightlies as at the date of this post. After factory reset TWRP works again, but if you go through the setup steps and start installing apps, TWRP goes unresponsive again. I hope we might get an official TWRP update soon!
Hello!
My htc stuck on logo ,,this build is for development purposes only". Twrp and bootloader working. I can instal cm and other rom but after instal htc stuck in logo Please help me. How install a custom rom.
h.t.t.p://i63.tinypic.com/2d0ctwj.jpg
rabus40 said:
Hello!
My htc stuck on logo ,,this build is for development purposes only". Twrp and bootloader working. I can instal cm and other rom but after instal htc stuck in logo Please help me. How install a custom rom.
h.t.t.p://i63.tinypic.com/2d0ctwj.jpg
Click to expand...
Click to collapse
pic not working
Try:
clear cache and dalvik
remove USB cable before reboot.
You must delete . in h.t.t.p. I can't upload photo because I'm a new user. I try clear cache and dalvik and still not working
rabus40 said:
You must delete . in h.t.t.p. I can't upload photo because I'm a new user. I try clear cache and dalvik and still not working
Click to expand...
Click to collapse
yes but it wasnt loading.
OK so you installed HTC stock ROM but gets stuck?
is it the appropriate Rom for your phone or it might be corrupted. Reinstall and make sure its the right one.
Original ROM
Please tell me how to install ,, htc orginal backup" ?
rabus40 said:
Please tell me how to install ,, htc orginal backup" ?
Click to expand...
Click to collapse
download Stock ROM from link above
Make TWRP backup in your phone (not sdcard)
Replace Phone backup you just made with the one you download
In TWRP restore backup
Remove USB cable and Reboot
Flash Stock Recovery from link above
Reboot
Perform HTC OTA update
Reboot
Flash TWRP
Flash SuperUser if Root require
Reboot
Thank me...
Donate me...
Done
rabus40 said:
Hello!
My htc stuck on logo ,,this build is for development purposes only". Twrp and bootloader working. I can instal cm and other rom but after instal htc stuck in logo Please help me. How install a custom rom.
h.t.t.p://i63.tinypic.com/2d0ctwj.jpg
Click to expand...
Click to collapse
When i was stuck in that screen the only way i found to get out of it was to remove the back cover and disconnect the battery
I have the same problem
-I have rooted my htc mini2 and after a while decided to restore the original ROM but everytime i turn on the phone i have that red warning message.
One day i decided to delete de TWRP backup files bacause it takes a lot of space on my internal memory .
Yesterday my baterry died so when i was turning my phone it gets stuck on that message screen . So i can't get through because on my internal memory i don't have the TWRP files to backup or get into recovery mode.
Is there any solution? i was thinking about putting those files on my sd card and see if the phone will read them?
Tiburcio U123 said:
I have the same problem
-I have rooted my htc mini2 and after a while decided to restore the original ROM but everytime i turn on the phone i have that red warning message.
One day i decided to delete de TWRP backup files bacause it takes a lot of space on my internal memory .
Yesterday my baterry died so when i was turning my phone it gets stuck on that message screen . So i can't get through because on my internal memory i don't have the TWRP files to backup or get into recovery mode.
Is there any solution? i was thinking about putting those files on my sd card and see if the phone will read them?
Click to expand...
Click to collapse
Download Nandroid files for your phone and place it in SD Card via computer and then restore it via TWRP..
TryllZ said:
Download Nandroid files for your phone and place it in SD Card via computer and then restore it via TWRP..
Click to expand...
Click to collapse
Ok but how am i going to install TWRP on my phone? i've deleted . Is there a way of doing all this process completely on SD card?
Tiburcio U123 said:
Ok but how am i going to install TWRP on my phone? i've deleted . Is there a way of doing all this process completely on SD card?
Click to expand...
Click to collapse
No, not possible from SDCard alone, you have to flash TWRP by placing TWRP in PC ADB folder (ADB must be installed in PC and device should be able to enter bootloader and fastboot) and entering bootloader>fastboot on device, then connect device to PC, this only works on unlocked devices.
Command is :
fastboot flash recovery twrp.img
fastboot erase cache
Tiburcio U123 said:
I have the same problem
-I have rooted my htc mini2 and after a while decided to restore the original ROM but everytime i turn on the phone i have that red warning message.
One day i decided to delete de TWRP backup files bacause it takes a lot of space on my internal memory .
Yesterday my baterry died so when i was turning my phone it gets stuck on that message screen . So i can't get through because on my internal memory i don't have the TWRP files to backup or get into recovery mode.
Is there any solution? i was thinking about putting those files on my sd card and see if the phone will read them?
Click to expand...
Click to collapse
Hey, i had the same issue. After rooting my phone, when my phone died because of the low battery, the same thing happened to me.
The solution is pretty simple, actually - you have to restart the charging unit of your phone.
So what you gotta do is this:
leave it to charge a couple of minutes (so it will have enough power to boot again) and then just press all the buttons of your phone at the same time and hold it for up to 10 seconds, so power button + volume up + volume down.
This will restart your charging unit and it will get your phone to boot normally again. :fingers-crossed:
I don't know why this keeps happening, but I have to do it all the time, if my phone dies. So I try to make sure it has enough battary not to die, because it is just annoying.
i have the same problem. if you hold the power button + volume up you can reboot your phone if it is frozen.
petie2106 said:
i have the same problem. if you hold the power button + volume up you can reboot your phone if it is frozen.
Click to expand...
Click to collapse
the trick is to keep hold of power vol up & vol down for 2 mins,it will boot,reboot,boot,reboot loads of times,keep hold for at least 2 mins,once you let go it resets itself:good:
make sure you have a some means of installing Android back onto your phone placed on your SD card or internal storage
I recommend updating to the latest version of twrp before trying these (I used 3.0.2.0)
twrp>wipe>advanced wipe>select everything but: "/Micro SDCard" "/Internal Storage" "SD-EXT" and "USB-OTG
after that install Android by restoring from a recovery backup or instal a custom rom onto your device (whatever floats your boat)