Hello
I am in a great panic mode.
I applied this lagfix : forum.xda-developers.com/showpost.php?p=7587405&postcount=417 and since I did it I cannot use my phone.
I am not able to start my phone. It shows me Galaxy S logo, and after that I hear the start up music but nothing on the screen (no animation). Pressing hardkeys does not do anything either.
Above all I cannot even enter my recovery mode. When I press volumedown+poweron button, the screen keeps showing me Galaxy S logo and it does not go any further.
Please help me if you know how to getaround.
Were you rooted when yoou applied update.zip?
Anyway,did you try to shutdown the phone removing battery,and then try entering recovery?
the fix did not mention I had to root my phone, it said it would self install.
Yes I did shut down after removing the battery, and then I am trying to get into recovery using volumedown+poweron button but I am not able to get into it. All I see is Galaxy logo and hear start up music after that with nothing on screen.
OK, I am able to get into recovery mode.. I was trying wrong combinations
Now what should I select I get these options:
1. reboot system now
2. apply sdcard:update.zip (will never do this again)
3. wipe data/factory reset (should I do this)
4. wipe cache partition
yes.. you should do 3.) wipe data. If that doesnt solve your problem, you need to flash firmware agian
somusingh said:
Hello
I am in a great panic mode.
I applied this lagfix : forum.xda-developers.com/showpost.php?p=7587405&postcount=417 and since I did it I cannot use my phone.
I am not able to start my phone. It shows me Galaxy S logo, and after that I hear the start up music but nothing on the screen (no animation). Pressing hardkeys does not do anything either.
Above all I cannot even enter my recovery mode. When I press volumedown+poweron button, the screen keeps showing me Galaxy S logo and it does not go any further.
Please help me if you know how to getaround.
Click to expand...
Click to collapse
Why did you choose to install something not on main page, something obviosuly not very tested and something 2 month old (god knows there are close to ten newer or more tested fixes).
If you can access download mode, than reflash. If not... Well, try the exotic methods (dont know them, as I have working 3 butons)
Hey, for a second I thought it did noy fix my problem as I did not get my animation screen and ony heard music.. But then suddenly it starts up
I think I lost my animation on start up though
I still see that MCR Scripts icon on app loader screen, How could I know if its enabled or disabled?
Thanks a lot guys.. XDA rocks .
dupel said:
Why did you choose to install something not on main page, something obviosuly not very tested and something 2 month old (god knows there are close to ten newer or more tested fixes).
If you can access download mode, than reflash. If not... Well, try the exotic methods (dont know them, as I have working 3 butons)
Click to expand...
Click to collapse
I regret doing something like that.. But it was really confusing as there are so many topics on the forum and I was really tempted to solve the lag issue I started facing recently (I installed too many apps).
hey i have the same problem.. my phone goes up into the Samsung logo and hangs there forever, occasionally blinking and making a weird vibration. i've tried factory reset but that doesn't help..
How do i flash firmware again?
glbc said:
hey i have the same problem.. my phone goes up into the Samsung logo and hangs there forever, occasionally blinking and making a weird vibration. i've tried factory reset but that doesn't help..
How do i flash firmware again?
Click to expand...
Click to collapse
Read the FAQs
Insanity cm 014/glitch
reflash the rom by odin will solve the problem
make sure your kenel is speedmod if u updated the rom from your sdcad，
enter into recovery ，do the wipe then updated ，disable all lagix ，all this work done u could updated the rom
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!
Hey guys,
i'm in trouble installing a custom ROM on a S4 Active (GT-I9295, Baseband IXXUDOB4, 5.0.1).
Flashed CF--Autoroot with Odin, no problem.
Then i flashed TWRP, Odin showed its green "PASS!"-message but i can't boot into recovery.
I'm well aware of the timing issue when doing the first reboot into a custom recovery, and i assure you this isn't the problem.
I tried countless times, after a while i installed ROM manager to try if i could flash the ROM file that way.
It installed another custom recovery -CWM- on top, and also showed up the TWRP recovery:
http://imgur.com/kSSiuld
Still, booting into any recovery does not work, neither from ROM managers menu or via any button-press combination.
When pressing vol up+home+power, the phone shows the blue "revovery loading"-line AND the red line *****ing about the root, but continues to boot as if it had been switched on normally.
I even looked for the ominous "install-sh" script in system/etc to understand why nothing gets me into recovery-
what the heck can this be?!
Did the same thing to S6 and S5 without any hassle, i'm stuck with this for several days now and i am running out of ideas.
Anyone...?
Not a very technical answer, but have you tried pulling the battery out for 30 seconds and trying again?
Yes we did, unfortunately, this also didn`t help.
Tried loads of things actually, still impossible to access that damn recovery
Hi guys, can anyone pls do help me. been troubleshooting and try to fix this thing for 2 days already.
The problem is, my fon will always boot to recovery. Eventhough i choose restart to system it will always go back to recovery.
I tried turn off, and push the power button only, still it will boot to recovery.
This started happening just a sudden, my fon run out of battery. Then its dead, i recharge. When try boot again the recovery boot problem begin.
I tried to restore my backup that iv made after the fresh installation of the CM13, restoration is good. But it still boot to recovery.
I then tried flashed the original rom with fastboot, ( i can access fastboot via the options in recovery, im using the TWRP recovery.
Or else i wouldnt be able to access fastboot also, even if i push (vol down+power button) when the fon is off, it will goes directly to recovery.
Anyone has any idea? please help =(
Fix
mufanz said:
Hi guys, can anyone pls do help me. been troubleshooting and try to fix this thing for 2 days already.
The problem is, my fon will always boot to recovery. Eventhough i choose restart to system it will always go back to recovery.
I tried turn off, and push the power button only, still it will boot to recovery.
This started happening just a sudden, my fon run out of battery. Then its dead, i recharge. When try boot again the recovery boot problem begin.
I tried to restore my backup that iv made after the fresh installation of the CM13, restoration is good. But it still boot to recovery.
I then tried flashed the original rom with fastboot, ( i can access fastboot via the options in recovery, im using the TWRP recovery.
Or else i wouldnt be able to access fastboot also, even if i push (vol down+power button) when the fon is off, it will goes directly to recovery.
Anyone has any idea? please help =(
Click to expand...
Click to collapse
Go the miui forum and search FIX : MI FLASH PARTITION TABLE DOESNT EXIST
You'll find a link by Harsimrat Sethi, me,, its the perfect fix
Harsimratsethi said:
Go the miui forum and search FIX : MI FLASH PARTITION TABLE DOESNT EXIST
You'll find a link by Harsimrat Sethi, me,, its the perfect fix
Click to expand...
Click to collapse
Hi bro thanks for suggestion, will do try it out. Iv looked at the solution, but it seems that is a problem if cant use fastboot flash with Mi Flash, I have no problem flashing to stock rom in fastboot. Iv used this solution from this link below to manually flash in the fastboot. Its working for people who are having problem of "MI FLASH PARTITION TABLE DOESNT EXIST".
http://forum.xda-developers.com/xiaomi-mi-3/general/guide-flashing-fastboot-miui-roms-t2938279
But the problem is still it will boot up to recovery also.