Hi,
I followed the very comprehensive guide here: http://forum.xda-developers.com/showthread.php?t=2271909
however when I tried to reboot it seem the booting process restarts and the Kindle Fire logo will flash on and of with 10 sek intervals.
any ideas how to get out of this?
Thanks
Christiansloth said:
Hi,
I followed the very comprehensive guide here: http://forum.xda-developers.com/showthread.php?t=2271909
however when I tried to reboot it seem the booting process restarts and the Kindle Fire logo will flash on and of with 10 sek intervals.
any ideas how to get out of this?
Thanks
Click to expand...
Click to collapse
Something went wrong. Do you see the blue logo? If you do, you have the bootloader installed properly. Enter recovery and wipe everything (except system and sdcard) and reboot. If not, try to restore using fastboot in step 6.
seokhun said:
Something went wrong. Do you see the blue logo? If you do, you have the bootloader installed properly. Enter recovery and wipe everything (except system and sdcard) and reboot. If not, try to restore using fastboot in step 6.
Click to expand...
Click to collapse
I have the same problem. No blue logo, just an infinite boot loop.
I can't get into fastboot, so I purchased a factory cable last night in hopes that it will help.
bryang said:
I have the same problem. No blue logo, just an infinite boot loop.
I can't get into fastboot, so I purchased a factory cable last night in hopes that it will help.
Click to expand...
Click to collapse
Because the device boots properly, you'll have no trouble getting into fastboot with the cable. I apologize something went wrong, but apparently it's on your end, because many people reported no issues. Please make sure you followed the guide to the tee.
seokhun said:
Because the device boots properly, you'll have no trouble getting into fastboot with the cable. I apologize something went wrong, but apparently it's on your end, because many people reported no issues. Please make sure you followed the guide to the tee.
Click to expand...
Click to collapse
Thanks...yes I also have no blue logo, the logo looks normal (white and orange). I have ordered a factory cable and will try that way.... any tips on this that is NOT covered already in your thread?
Thanks alot
Christiansloth said:
Thanks...yes I also have no blue logo, the logo looks normal (white and orange). I have ordered a factory cable and will try that way.... any tips on this that is NOT covered already in your thread?
Thanks alot
Click to expand...
Click to collapse
Not that I know of. Once you get the cable, it's simple. Use the restore tool linked in my guide, and follow instructions.
seokhun said:
Not that I know of. Once you get the cable, it's simple. Use the restore tool linked in my guide, and follow instructions.
Click to expand...
Click to collapse
Hi again,
I have not gotten hold of the factory cable, and have tried to run the restore tool here: http://forum.xda-developers.com/showthread.php?t=1951254
However, even if it seems to work fine and the img. file is copied, there is no change in the device: it still runs a boot loop with the orange Kindle logo going on and off.
I can get the festboot logo on the screen by plugging in the factory cable, but not sure what to do now?
Would be grateful for any advice...
Christiansloth said:
Hi again,
I have not gotten hold of the factory cable, and have tried to run the restore tool here: http://forum.xda-developers.com/showthread.php?t=1951254
However, even if it seems to work fine and the img. file is copied, there is no change in the device: it still runs a boot loop with the orange Kindle logo going on and off.
I can get the festboot logo on the screen by plugging in the factory cable, but not sure what to do now?
Would be grateful for any advice...
Click to expand...
Click to collapse
Ask in that thread, I've never used the tool, so I wouldn't know.
seokhun said:
Ask in that thread, I've never used the tool, so I wouldn't know.
Click to expand...
Click to collapse
Hi again again,
I got it running again....
In your guide step 4, it says to copy the ROM and Gapps to the sdcard.... is it the zip file there has to be copied or the unzipped files?
Thanks again.
C
Christiansloth said:
Hi again again,
I got it running again....
In your guide step 4, it says to copy the ROM and Gapps to the sdcard.... is it the zip file there has to be copied or the unzipped files?
Thanks again.
C
Click to expand...
Click to collapse
The zip itself. Both come in as zip files, move those to the sdcard in zip form.
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!
So let me explain my situation. I decided to factory reset because I needed to clean up my tablet quite a bit. I did this and it decided to freeze on reboot. I waited 30ish minutes and it was still stuck, so I shut it off. It would not boot after that, it would get stuck at the second asus screen with load wheel. I went into recovery and did data/cache wipe. That allows me to boot once after everytime I wipe otherwise it will be a bootloop. I tried sideloading the firmwares on asus's support page NONE of them worked. I tried fastboot and adb and none of them were successful. I have a bunch of errors in the bootloader. I also have pictures of what it boots to. Aswell as the bootloader errors. What should I do, asus said I should rma but I dont have the money and I also rooted this thing which can be seen whenever I do su in adb it still asks for root. I have very few options anybody's word would probably be a help. Thanks
How I recovered
applerulez1 said:
So let me explain my situation. I decided to factory reset because I needed to clean up my tablet quite a bit. I did this and it decided to freeze on reboot. I waited 30ish minutes and it was still stuck, so I shut it off. It would not boot after that, it would get stuck at the second asus screen with load wheel. I went into recovery and did data/cache wipe. That allows me to boot once after everytime I wipe otherwise it will be a bootloop. I tried sideloading the firmwares on asus's support page NONE of them worked. I tried fastboot and adb and none of them were successful. I have a bunch of errors in the bootloader. I also have pictures of what it boots to. Aswell as the bootloader errors. What should I do, asus said I should rma but I dont have the money and I also rooted this thing which can be seen whenever I do su in adb it still asks for root. I have very few options anybody's word would probably be a help. Thanks
Click to expand...
Click to collapse
Please see what worked for me, when i got it a similar situation.
http://forum.xda-developers.com/memo-pad-7/help/unbrick-memo-pad-me176cx-t2987068#post58231184
ardluc said:
Please see what worked for me, when i got it a similar situation.
http://forum.xda-developers.com/memo-pad-7/help/unbrick-memo-pad-me176cx-t2987068#post58231184
Click to expand...
Click to collapse
I have given you the nickname android jesus in my household, my tablet is fixed now! I love you, thanks so much! This thread can be closed.
Hello everyone.
I don't know what happened but my device entered in the infamous bootloop. I tried to erase cache, partition, reinstall a rom, install a different rom and nothing.
My true problem is that last night I made a horrible mistake: I erased everything including my SD card, which contained the data for boot to recovery. Right now I can only see the SONY logo when I power up my device and nothing else.
I tried to install recovery via fastboot flash boot boot.img but I can't keep my device in fastboot. I mean, I connect my device and hold Volume Up but after a few seconds it continuous to the SONY logo and stays there forever.
Am I missing something? What can I do to reintall a recovery if I can't access my phone data?
Thank you.
How to install recovery in a phone which can't start [Solved]
I just figured it out! I installed Sony's stock rom following this guide and my phone is alive again.
bbabel said:
I just figgured out! I installed Sony's stock rom following this tutorial and my phone is alive agaoin.
Click to expand...
Click to collapse
Good you managed to fix it and posted it back here with a solution. So few people do it. On the side note, link you provided does not work, please fix if you can
kwitu said:
Good you managed to fix it and posted it back here with a solution. So few people do it. On the side note, link you provided does not work, please fix if you can
Click to expand...
Click to collapse
Thank you. I just fixed the link and now it works.
Hi -
I have searched these forums multiple times, had numerous brower tabs open trying to follow instructions, and am at wits end. I am hoping that someone here can help me. I have a Kindle Fire HD 7" which had version 7.5.1 on it. I've rooted, tried using Fireflash to flash TWRP, bricked it twice, recovered it (with the fastboot cable that arrived in the mail 2 days ago), and now I am unable to switch on wifi (I did see the recent thread about this). I'm not sure what I'm doing wrong. The first two times before flashing the TWRP, I did not downgrade to 7.2.3. Could that have been why it bricked both times?
I just did another reset to factory defaults to try to get wifi back, to no avail. I am doing all of this so that I can install a ROM to escape all of the Amazon interface limitations.
Edit: I should add that I have so many files downloaded now (different versions, per each set of instructions) that I am confused.
Update: I just used SRT_v1.3.0 to restore factory recovery and now my wireless is enabled!
I am afraid to use Fireflash to flash TWRP again after two failures.
Thank you for any and all input!
PnGa
NM: Got it working.
Pickngrin said:
NM: Got it working.
Click to expand...
Click to collapse
HOW?? FOR GODS SAKE HOW???
I'm in the same boat, just bricked it now I think, red screen when turning on, thats it
Don't panic... get a factory (Fastboot) cable and use the Unbrick app to revive it. I took so many attempts to get it successfully flashed with CM12. I believe that I was using the incorrect boot image file and had not downgraded to 7.2.3 first. But I don't really understand the whole process. Good luck!
Pickngrin said:
Don't panic... get a factory (Fastboot) cable and use the Unbrick app to revive it. I took so many attempts to get it successfully flashed with CM12. I believe that I was using the incorrect boot image file and had not downgraded to 7.2.3 first. But I don't really understand the whole process. Good luck!
Click to expand...
Click to collapse
Cheers mate... I will try and find out to make one...