Hello,
I have a nexus one that isn't working anymore. I was trying to install the cyanogenmod, but I guess I didn't do it correctly.
I was following the clockworkmod way from this: h t t p ://wiki.cyanogenmod.com/index.php?title=Nexus_One:_Full_Update_Guide
When flashing the rom something went wrong. After step 6 my phone didnt reboot, it just stayed off. Now it will only give me the nexus sign if i turn on the phone.
I can still acces the recovery menu when holding Power + volume down.
People told that I should go back to the stock rom.
Can anybody please help me?
*don't know if i've posted in the right category
When you get to recovery is it still clockwork or stock? If clockwork then try and flash cm6 again. If not you will have to download a stock rom push it to the sdcard as an update.zip and boot into the boot loader.
Sent from my Galaxy Tab, that makes phone calls
Since you can boot into recovery you have NOT bricked it for sure
As mentioned in the earlier post try to flash the CM ROM again
If you are unable to access the custom recovery (as in, the stock recovery is still in place), you can follow the manual instructions for installing ClockworkMod: http://wiki.cyanogenmod.com/index.php?title=Nexus_One:_Full_Update_Guide#Manual_Method
You can then follow the procedure for flashing the appropriate radio image: http://wiki.cyanogenmod.com/index.p...ll_Update_Guide#ClockworkMod_Recovery_process
And you can even install the ROM without using Rom Manager using this process: http://wiki.cyanogenmod.com/index.p...Update_Guide#Second_Method_.28via_Recovery.29
All of this is, as I'm sure you've noticed, posted on the same page that you linked. Hopefully this information will help you, now that you have been assured that your phone is not bricked.
Thanks for quick replies. I've contacted a guy with a lot of knowledge about these kind of thinks and helped me fixing me phone. I dont know exactly what went down but I will give it a try.
My first mistake was thinking that I rooted my phone (using the one click method). Don't know if thats the right way to do it, but in the end it wasn't rooted and I tought it was.
The guy rooted my phone, did the AmonRa recovery install and installed the Ethernom Rom for me. Great to have my phone back to working and great Rom btw.
[SOLVED -- Read my last post]
Posting on forum was my last resource, but I've tried literately almost everything I can possible find.
I already bricked my phone and had to unbrick, do everything (update firmware etc) all over again.
I am at a point where I am afraid to do something new to my phone now without knowing what they are...
Please bare with me, I am not familiar with exactly what flashing is or whatnot, I just followed the instructions and got where I am....
K, recently I decided to wipe my phone CLEAN and update to new CyanogenMod 9 from factory mode.
So, I have Captivate, I897. It was ECLARE with 2.1 firmware.
I have updated to 2.3.5 (Gingerbread [I897UCKJ2]), Rooted.
I had to Flash BACK to KK4_stock_kernel.tar for me to use WIFI again because I had issue after Rooting my phone, I couldnt access the WIFI.
I installed Clockwork mod (Free version).
My goal is to install CyanogenMod 9, and part of the process requires me to enter the CMW Recovery Mod.
I dont even know what this looks like, but all I know is whenever I boot my phone, after the AT&T logo animation it seems to go into this "messed up" screen, where as if my phone is broken. Stays there for 3 seconds and then continues to boot back to its OS.
In ROM manager, it says Flash ClockworkMod Recovery (You must have the clockworkmod recovery installed to flash and restore ROMs!)
Another option within ROM manager is, Reboot into Recovery (Boot into Recovery mode for manual management.), which if I do access it, it takes me back to that AT&T logo animation and that "messed up" screen again, but this time it stays there. Where all kinds of colored pixels are on my screen as if my screen is broken. It will only continue to boot back to my OS if I press power button or some sort.
Im guessing that's my Recovery Mod, which my phone for some reason cannot see?
So I tried "Download ROM (Upgrade to ROM Manager (premium) to access the full list of ROMs!", hoping this may cure that messed up screen effect, which I think is the Recovery Mod for all I know... When I click to install, it gives me Confirm Phone Models. None are my phone model for me to install.. (It only gives me Google Nexus S / Google Nexus S 4G / Samsung Epic4G / Samsung GalaxyS i9000).
Earlier, I was looking at this, http://forum.xda-developers.com/showthread.php?t=1127578
which is a way to fix recovery mod(?) But I have NO idea how to even install those files... Maybe not the .tar file but the other one.
Please help? Am I the only one experiencing this kind of problem? Couldnt find anywhere else on youtube / google / forum..
Thank you VERY much in advance, really appreciate it..
-Dan.
danroh said:
I had to Flash BACK to KK4_stock_kernel.tar for me to use WIFI again because I had issue after Rooting my phone, I couldnt access the WIFI.
-Dan.
Click to expand...
Click to collapse
This is your likely problem right here. The Kernel that is installed during the rooting process and typically when you install custom roms is what is responsible for installing and therefor you being able to access the CWM recovery. Flashing back to the stock kernel likely messed things up for you.
http://forum.xda-developers.com/showthread.php?t=1300843
Now if you follow that link it will take you to several one click options for flashing your phone to stock gingerbread but with a kernel containing CWM. Also keep in mind that it is possible you could have wifi issues if you've had them in the past, but if your goal is to get to CM9 just ignore the wifi for the time it shouldn't be an isuse in the end.
Hey OP,
See this.... TRusselo's Flashing Guide
Sent from my SAMSUNG-SGH-I897 using xda premium
You need Gingerbread bootloaders.
Thanks guys! I figured out the problem and solved it!
Like you guys said, I didnt have the bootloader. The gingerbread I installed was the no bootloader version. After reinstalling to the one with bootloader, I was able to access the recovery mod and that "rainbow screen" glitch was no more.
Thank you!
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 everyone,
I tried looking for a solution to this problem, but either can't understand the suggestions or it doesn't really fit with my situation...
For some reason I managed to soft brick my TF701, trying to go back to stock after a CM install.
Anyways, I get stuck on the ASUS logo. I can access fastboot buf if I select RCK I get an error message. I can also connect in APX.
Any ideas on how I could flash a ROM on this device?
Many thanks in advance and sorry if there was an answer somewhere I missed...
I feel a bit ashamed now, I actually found a solution on my own and it wasn't that hard...
My main issue was not being able to access recovery. So I ended up doing the recommended steps here :
http://forum.xda-developers.com/showthread.php?t=2425581
up to the flash part and instead flashed this version of CWM
http://droidbasement.com/db-blog/?p=3568
This actually got me a working recovery, which I used to successfully flash a rom and my tablet is running again, as well as recovery mode.
Sorry for the thread, I could have managed on my own. If there's a way to delete it?