My nexus one cannot go through the splash screen during the boot process and keeps restarting over and over. The power button is not working on the device, so I can't use the recovery or any option in the bootloader that requires me to push the power button.
I cannot enable the debugging option, since I can't start the phone.
I was trying to use fastboot thingy, but it keeps coming with "FAILED (remote: signature verify fail)" or" FAILED (remote: not allowed)"
Any idea how to bring this phone back to life?
I'm experiencing the same thing, broken power button and endless bootloops. I'm rooted, but only on the most basic ROMs without any sort of way reboot into recovery. Any help would be great...
I would get power button fixed firstly, if I were you. Good luck anyway!
Sent from my Nexus One using xda app-developers app
Connect your nexus to a charger, when led turns on pull the battery out, when led turns off put the battery in before led shows up again.
After you put the battery in correctly, just long press the trackball to get into hboot
After that just use the recovery to wipe and flash a new rom
Sent from my Nexus One using Tapatalk 2
mihovil13 said:
Connect your nexus to a charger, when led turns on pull the battery out, when led turns off put the battery in before led shows up again.
After you put the battery in correctly, just long press the trackball to get into hboot
After that just use the recovery to wipe and flash a new rom
Sent from my Nexus One using Tapatalk 2
Click to expand...
Click to collapse
Okay, so I made it into hboot, but please explain how I can get into recovery without a power button to select recovery.
use trackball and volup/down
trackball to choose, volup/down for marking/selecting
Do you use blackrose?
If so, trackball works 100%
mihovil13 said:
use trackball and volup/down
trackball to choose, volup/down for marking/selecting
Do you use blackrose?
If so, trackball works 100%
Click to expand...
Click to collapse
I don't use Blackrose, my ROM is a very basic form of MIUI from earlier this year and I haven't updated it since. I thought I would be able to use the trackball in place of the power button as well, but so far it's not working. Is there any other way to boot into recovery or another way to use the trackball instead of the power button?
Once u get hboot, connect N1 to PC and try 'fastboot reboot-recovery' in CMD
Sent from my Nexus One using xda app-developers app
longbowz said:
Once u get hboot, connect N1 to PC and try 'fastboot reboot-recovery' in CMD
Sent from my Nexus One using xda app-developers app
Click to expand...
Click to collapse
I'm trying that now and getting the message that the command isn't recognized...
Sorry I was wrong about it. The option is reboot-bootloader so there seems to be no way to boot to recovery directly in your case.
As to the message u got, you need to install android boodloader driver so that fastboot may work. But it can only lead u to hboot, not further.
Sorry for bad news
Sent from my Nexus One using xda app-developers app
longbowz said:
Sorry I was wrong about it. The option is reboot-bootloader so there seems to be no way to boot to recovery directly in your case.
As to the message u got, you need to install android boodloader driver so that fastboot may work. But it can only lead u to hboot, not further.
Sorry for bad news
Sent from my Nexus One using xda app-developers app
Click to expand...
Click to collapse
Don't worry about it, It's cool... I loved this phone, had it since it came out back in January 2010, now I have to find a new one. I was checking out the HTC One S and X, and maybe the X+ if they ever release it, are those good upgrades to the Nexus One?
I'm not expert of hardware, but believe theses are way much better than N1 as you will have bigger screen, more cpu cores, larger RAM and internal storage size, and most impotant - ICS or jelly beans ROMs.
Sent from my Nexus One using xda app-developers app
longbowz said:
I'm not expert of hardware, but believe theses are way much better than N1 as you will have bigger screen, more cpu cores, larger RAM and internal storage size, and most impotant - ICS or jelly beans ROMs.
Sent from my Nexus One using xda app-developers app
Click to expand...
Click to collapse
I tried one out today at a local T-Mobile store, it's a very nice phone but sorta disappointed me with the lack of transferable SIM and Micro SD cards. I'm gonna do more research on it but it's shaping up to look like my N1's replacement... :crying:
Oh well, it's been really good. The Nexus One has been easily the best phone I've had thus far and for the longest (2 years and almost 10 months).
Thank you all for the help in trying to recover it.
Finally, I was able to reset the phone by using the SD card. The steps are outlined here:
http://forum.xda-developers.com/wiki/HTC_Nexus_One/Guides_&_Tutorials
quasiquasar said:
Finally, I was able to reset the phone by using the SD card. The steps are outlined here:
http://forum.xda-developers.com/wiki/HTC_Nexus_One/Guides_&_Tutorials
Click to expand...
Click to collapse
Hi there, I'm having the exact same problem as you.. I tried to follow the instructions on the link you gave but I'm stuck on the 3rd step: how can I transfer a file to my sd card? when I enter the fastboot and the computer is connected I can see on my n1 that it is written "fastboot usb" but the computer doesn't show me that it's recognizing it...
Help would be very much appreciated!
i tried all the tricks and methods but my mobile just doesnt power ON
what might be wrong ? please help
Related
hi
plz help me
my nexus one bricked!
what should i do?
First I gotta say, someone get a fire extinguisher cause girl you are on fire! (lol)
Anyways can you elaborate on how you "bricked" your phone? Can you get to the boot loader or recovery at all? What did you last do before you found out it was bricked?
It's very hard to brick them... hold the trackball and power on, and you should get the bootloader, if so, it's far from dead.
Deekayy said:
First I gotta say, someone get a fire extinguisher cause girl you are on fire! (lol)
Anyways can you elaborate on how you "bricked" your phone? Can you get to the boot loader or recovery at all? What did you last do before you found out it was bricked?
Click to expand...
Click to collapse
tnx for answer
i was full wipe my phone and after that install radio and rom
after reboot it's turn off
now it's off and i cant do every thing!
Not working after radio flash? Oh dear.
Did you install it via fastboot or recovery?
Rusty! said:
Not working after radio flash? Oh dear.
Did you install it via fastboot or recovery?
Click to expand...
Click to collapse
in recovery
flash zip from sd!
Uh oh.
The only real way to brick an N1 is with a bad radio flash. The riskiest way to flash a radio is via recovery.
You can try pulling the battery, plugging it into a charger and re-inserting the battery.
Rusty! said:
Uh oh.
The only real way to brick an N1 is with a bad radio flash. The riskiest way to flash a radio is via recovery.
You can try pulling the battery, plugging it into a charger and re-inserting the battery.
Click to expand...
Click to collapse
thanks a lot
but its not work!
can i repair it with jtag?
You can, but there is no JTAG...
Rusty! said:
Uh oh.
The only real way to brick an N1 is with a bad radio flash. The riskiest way to flash a radio is via recovery.
Click to expand...
Click to collapse
Little OT: what is the more secure way to flash radio?
Use fastboot.
fire girl said:
tnx for answer
i was full wipe my phone and after that install radio and rom
after reboot it's turn off
now it's off and i cant do every thing!
Click to expand...
Click to collapse
Can't do everything, or can't do anything - because there is a difference...
Is there any signs of life from the phone at all (light/vibration)?
I'm asking because you said you flashed radio AND ROM (was it in that order?). If you managed to flash the ROM after the radio, then the radio probably isn't the problem...
Sent from my Nexus One using XDA App
danger-rat said:
Can't do everything, or can't do anything - because there is a difference...
Is there any signs of life from the phone at all (light/vibration)?
I'm asking because you said you flashed radio AND ROM (was it in that order?). If you managed to flash the ROM after the radio, then the radio probably isn't the problem...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
no i cant do any thing
no light, no vibration
in the first i wipe everything
data, cach , dalvic , battery status & ......
after that i flash radio and rom
when the cellphone rebooted
suddenly turned off and ...........( bricked )
the cell phone was have problem before i flash rom and radio
it wasnt come up
when i was turn on it
it was just stay on x picture
with open lock
Phone that suddenly turned off during Radio flash - is bricked, and nothing to do about it. Use the warranty, send in for replacement.
Yeah, it was a long stretch, but I thought I'd ask anyway...
Sent from my Nexus One using XDA App
turn d phone off if its off try to turn it up by holding d volume button down and d power button.c if it will get u to the recovery. from there wipe whatever you can wipe and try to install d rom from your sd card
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
mamboking said:
turn d phone off if its off try to turn it up by holding d volume button down and d power button.c if it will get u to the recovery. from there wipe whatever you can wipe and try to install d rom from your sd card
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
i told
i can not turn on it!
is it charged?
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
Pretty sure it's bricked.
Send it back to HTC.
If they can't fix it, then they probably can't tell how it got messed up either, so your warranty may be OK...
Sent from my Nexus One using XDA App
The bright side, you still have limited warranty as everyone says until January =]. Been reading mixed reviews of getting a replacement or fixed with HTC.
I flashed the Cyanogen 7 Rom to my phone, and it worked great up until last night...
Last night, I go to check my phone and realize that it is stuck at the "X" displayed when booting up. Also, either the proximity or light sensor (not sure which one), is dimly lit red.
The phone will still boot into fastboot, and is recognized by fastboot when connected to a computer. However, adb will not recognize it. I've tried to recover using the PASSIMG.zip method but it just will not work.
Sorry to bother you guys, but I don't know what to do next. And i'm pretty new to rooting and using the SDK, so please go easy on me. lol. Hopefully someone out there can steer me in the right direction. Any help is greatly appreciated.
Do you have a nandroid backup you can flash from recovery? If not...why not?
If all else fails you can always try loading a ROM using fastboot. You'd have to unlock your Bootloader first though, if you haven't already. Which Custom Recovery are you using btw?
Yeah, I have a Nandroid backup. I don't think it's on my SD card though, also I don't think it is a zip if that matters.
And the custom recovery I have is Clockwork.
Lol, this may be a dumb question, but how can I be sure that my bootloader is unlocked?
Nevermind. I think It's bricked, All it will do is flash a red light in the top left hand corner. Please say I'm wrong though...
You would know if you'd unlocked the bootloader.
Have you been in the fastboot mode yet? It's the white background with three Androids on the bottom. This is how you unlock the bootloader.
There should be a guide on how to unlock the bootloader on the Wiki, I'll go find it...
Once you've done that, you can use ADB to try and restore your Nexus using this method. This method has worked for me everytime I've used it.
I'll edit my post when I've got the unlocking bootloader post.
EDIT: http://forum.xda-developers.com/wik...uides_&_Tutorials#ADB.2FFastboot.2FBootloader
The guide is under the heading 'Root', and starts with 'In order to Unlock the Nexus One's bootloader'.
Hope this helps!
If the screen with x had a lock on the bottom of it it was unlocked.
Sent from my Nexus One using XDA App
You don't need to unlock the bootloader to use adb. You unlock the bootloader to use fastboot...
Can you get into the bootloader our recovery?
Sent from my Nexus One using XDA App
Well there seems to be a turn of events! luckily, lol My phone still boots into fastboot, my bootloader is now unlocked, but I still cannot make a connection to ADB... I must be forgetting something or doing something wrong.
You cannot get a connection to ADB? Is ADB installed; did you install the Android SDK?
If you can get a connection, type adb devices into the command prompt/terminal. If the device is connected, it will say your phone's unique code then [devices]; if it is not connected it will say your phone's unique code then [offline].
danger-rat said:
You don't need to unlock the bootloader to use adb. You unlock the bootloader to use fastboot...
Can you get into the bootloader our recovery?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Yeah I can still get into the Bootloader, but when I select recovery, it goes to the splash screen with the lock beneath it, and hangs up and gets SUPER warm to the touch after a few minutes lol
ADB probably isn't working because you aren't booting far enough into the system.
Try using fastboot to flash a new recovery image, and see if you can get into the new recovery...
Sent from my Nexus One using XDA App
When I type in adb devices It says "List of devices attatched" but then has nothing listed... but I'm pretty sure I installed the SDK; I used fastboot in the command prompt to unlock the bootloader.
I flashed a new recovery; I used cmd: "fastboot flash recovery recovery-RA-passion-v2.2.1.img" But I still can't get past the X with the pad lock screen...
Eeeek!
Might be time to give HTC a call.
I know a few people who couldn't flash recoveries, and nothing seemed to work. They returned the phone, and HTC fixed for free...
Sent from my Nexus One using XDA App
Do you have the drivers installed for the phone?
Sent from my Nexus One using XDA App
Ahhhhh, That's exactly what I didn't want to hear! Haha, well I guess there isn't any other way to try and get past this screen is there?
I really didn't want to have to bring HTC into the equation, haha. But, do you think they will still fix the phone after I had It running Cyanogen? AND after I unlocked the bootloader?
I just want to make sure they will still do something about it and not just leave me in the cold with a really nice looking paper weight...
albundy2010 said:
Do you have the drivers installed for the phone?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I should, I don't remember deleting them... How would I go about checking?
It will show up in device manager as nexus one. No yellow exclamation point. I don't recall if they are needed for fastboot/adb etc. Its in the wiki though.
Sent from my Nexus One using XDA App
If you're using fastboot commands, the drivers must be installed.
Don't worry about the phone being unlocked. If you can't boot the phone in it's current state, neither can HTC. So the first thing they will do is a full re-image, which will also fix your problem. Then they will probably test it, and just return it to you, because they can't find a problem...
Sent from my Nexus One using XDA App
So, to avoid bricking my device I relocked the bootloader, used the stock RUU file and upgraded to ICS.
Worked as a charm.
Installed a custom ROM, worked fine.
Installed another one, was great.
And then I changed to Dark Raider (link) and after installation completes my device goes black entirely. I can access CWM Recovery and everything but not the bootloader menu or anything else.
No matter what other ROM I try to flash, it doesnt work, and I can't get RUU going because I can't access flashboot.
Any ideas?
Which kernel did you flash? Did you do any other steps before or after installing the last ROM like factory reset, etc. Just trying to brainstorm some ideas.
Sent from my HTC PH39100 using xda premium
megatronisabeast said:
Which kernel did you flash? Did you do any other steps before or after installing the last ROM like factory reset, etc. Just trying to brainstorm some ideas.
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
I flashed the boot.img as usual that comes with the ROM, then did all the wiping they say we should on the main thread, then flashed the ROM.
What is really weird is that this is something I've done countless times before and never had any trouble. Even on ICS.
Oh and the device is still recognised by the computer, although not by the RUU file itself.
CWM Recovery works just fine but nothing else.
How are you getting to cwm? Normally you only access it through hboot. Are you doing the button combo?
Sent from my HTC PH39100 using xda premium
megatronisabeast said:
How are you getting to cwm? Normally you only access it through hboot. Are you doing the button combo?
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
When I plug it in via USB, it automatically turns the phone on into CWM.
It's just like when they had that bug on CWM Recovery that wouldn't let us charge our phones when they were off without automatically going into Recovery.
I just want a way to make the RUU file recognise the phone so I can go back to stock. Anyone?
in recovery theres an option in developer menu to reboot into bootloader....have you tried this
Wild Child said:
in recovery theres an option in developer menu to reboot into bootloader....have you tried this
Click to expand...
Click to collapse
What exactly is that developer menu?
Because I've been everywhere in Recovery and can't seem to find Reboot into Bootloader. I find Reboot Recovery alright, into the Advanced options, and several ++GO BACK++s that leads me to nowhere. I keep pressing it while on the main screen of Recovery and it just blinks the screen and that's all.
flasozzi said:
What exactly is that developer menu?
Because I've been everywhere in Recovery and can't seem to find Reboot into Bootloader. I find Reboot Recovery alright, into the Advanced options, and several ++GO BACK++s that leads me to nowhere. I keep pressing it while on the main screen of Recovery and it just blinks the screen and that's all.
Click to expand...
Click to collapse
Sounds like you flashed an outdated recovery. How exactly are you getting into recovery?
Sent from my HTC PH39100 using xda premium
kozmikkick said:
Sounds like you flashed an outdated recovery. How exactly are you getting into recovery?
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
By plugging in my phone into the computer via USB. It automatically goes into CWM Recovery.
I always try to follow the most up-to-date topics but rooting HTC Vivid on ICS was a bit weird and I used a tool I randomly came across with and had never used before, some SuperToolv3 or whatever it's called.
I was trying to flash the stoc AT&T ROM via .zip but apparently I can't access my external sd card via CWM due to the sweet fact that apparently iGo created a ext_sd folder by itself, and when I try to access the external sd card it goes into iGo's useless folder.
Grand.
I can't just return my phone to HTC since I bought this phone from a friend and over here it's not sold, and I'm not going to US or anywhere soon so I'm screwed.
Well you are not using the wcxrecovery if that option is not there....unsure what to [email protected] point
Wild Child said:
Well you are not using the wcxrecovery if that option is not there....unsure what to [email protected] point
Click to expand...
Click to collapse
Wild Child can't help me. I'm ready to throw my phone away then.
Can't I just install the other recovery through the one I already have? Okay, I know the answer but I really had to try.
If you cant get into hboot then we have a big issue...cant flash anything....if we could get you into fastboot menu then we could get you at least back on the ruu....what does it do when you hold power and volume down buttons
flasozzi said:
Wild Child can't help me. I'm ready to throw my phone away then.
Can't I just install the other recovery through the one I already have? Okay, I know the answer but I really had to try.
Click to expand...
Click to collapse
flasozzi said:
Wild Child can't help me. I'm ready to throw my phone away then.
Can't I just install the other recovery through the one I already have? Okay, I know the answer but I really had to try.
Click to expand...
Click to collapse
You do know how to get into hboot right?
Unplug it from the USB. Pull your battery out put it back in. Then with it still unplugged from USB press and hold the volume down button while simultaneously holding down the power button. Keep holding them both down for a couple seconds then hboot should load up.
Sent from my HTC PH39100 using xda premium
Wild Child said:
If you cant get into hboot then we have a big issue...cant flash anything....if we could get you into fastboot menu then we could get you at least back on the ruu....what does it do when you hold power and volume down buttons
Click to expand...
Click to collapse
kozmikkick said:
You do know how to get into hboot right?
Unplug it from the USB. Pull your battery out put it back in. Then with it still unplugged from USB press and hold the volume down button while simultaneously holding down the power button. Keep holding them both down for a couple seconds then hboot should load up.
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
Yes, I do know how to get into hboot.
I press both buttons and nothing happens.
The RUU file was the 1st thing i tried, but it doesn't recognise the phone since it's not on the mode it should be for using the RUU.
Grrrr. And I'm not even in a country where this phone is sold so I really can't see how I'll get this fixed.
Well, I'm not THAT noob. I know how to do most things. I've played around with this phone for a few months now and never had a problem with it.
I flashed the kernel properly and then I flashed the Dark Raider ROM the way I always do. Do you think is there any possibility that this was caused by Dark Raider?
I couldn't've done anything wrong. I never did. I wouldn't wait months of practice to finally screw anything up now.
flasozzi said:
Well, I'm not THAT noob. I know how to do most things. I've played around with this phone for a few months now and never had a problem with it.
I flashed the kernel properly and then I flashed the Dark Raider ROM the way I always do. Do you think is there any possibility that this was caused by Dark Raider?
I couldn't've done anything wrong. I never did. I wouldn't wait months of practice to finally screw anything up now.
Click to expand...
Click to collapse
I was just making sure since some people don't know that you can't enter hboot wih USB or a power cable connected to the phone.
Sent from my HTC PH39100 using xda premium
kozmikkick said:
I was just making sure since some people don't know that you can't enter hboot wih USB or a power cable connected to the phone.
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
And it's funny 'cause a guy in the other topic (I kinda think it's the ROM's fault so I posted there as well, maybe the dev has any clue) told me I should plug the phone in and try to get into hboot.
Well, I tried just for the hell of it and obviously didn't work.
Every time I plug the phone in either to a charger or a computer I'm taken straight to CWM Recovery. Like that old bug it had that we couldn't charge the phone off without going into Recovery.
I left it in Recovery but I'm not sure if it's charging, the battery wasn't that low but after all this time it probably is now, so it doesn't hurt to leave it there.
But, like, if this was a complete brick I wouldn't even be getting into Recovery, right? And the computer wouldn't be recognising it.
Isn't there a way to access the internal memory of the phone through the computer? I'd like to try one last thing but iGo created a ext_sd folder inside the phone and now when I try to access the REAL external SD i'm taken to the iGo folder.
And I only saw that now.
Or maybe a way to make the phone recognisable by the RUU .exe file?
Apparently a series of unfortunate things led me to this.
Need to restore your phone back to 100% because you need to send it back to Google or just want to get that feeling when you first got your Nexus 4? Use this guides below for Windows and Mac!
This will restore you back to stock 4.2 Jelly Bean, and yes after you fully finish this process you can send this back to Google for whatever reason.
Windows:
Download Links & Written Step-by-Step Guide with Pictures:
http://www.androidrootz.com/2012/12/how-to-unroot-nexus-4-to-stock-42-jelly.html
Mac:
Download Links & Written Step-by-Step Guide with Pictures:
http://www.androidrootz.com/2012/12/unroot-nexus-4-to-stock-42-on-mac.html
4.2.2
Will this work with 4.2.2?
taylh003 said:
Will this work with 4.2.2?
Click to expand...
Click to collapse
+1
taylh003 said:
Will this work with 4.2.2?
Click to expand...
Click to collapse
+2.
Yesterday i did same thing, only i found some different thread. It must be somewhere on nexus 4 forum. I was on PA 3+ and it worked very well. Only remember what you need to go to recovery and clear catch before booting, because in my case i couldn't boot until i wiped catch. And to enter recovery mode. You need to go enter fastboot, when choose recovery, and when you will see "dead android" you need to hold power button and then press (only one time, not hold) volume up and then you will see menu you can release power button. No need to press vol up and vol down. Just vol up, and press it only one time. Yesterday my mistake was then i always was holding power+vol up and phone was always turning off. Maybe this info will help for someone.
Edit:
this is that thread http://forum.xda-developers.com/showthread.php?t=2010312
We need this if we go to ssc right??
Sent from my Nexus 4 using xda premium
Nice tip! Also we are going to do this to get OTA updates right?View attachment 1846812
Glad to see this guide exists. I just ventured into root land last night. I'm happy this far, but I am happy to see this here for my peace of mind.
Sent from my Nexus 4 using xda app-developers app
Thanks for the guide !
Sent from my Nexus 4 using xda app-developers app
Other than the pictures how is this different from the very detailed guide we have had since day one?
http://forum.xda-developers.com/showthread.php?t=2010312
I don't see the unroot zip when I click on it...
Turb0wned said:
I don't see the unroot zip when I click on it...
Click to expand...
Click to collapse
It is under step 4.
Is there also a way to just unroot without deleting all data?
All I did was replace the customrecovery.img and installing supersu. Cant I just delete that?
I have a battery problem and I need to send the phone back, but Im afraid they will drop warranty because of me rooting it (only to try to calibrate battery -,- )
And what about 4.3 ?
If you reflash your android device to 4.2.2, will it ask to install the update (4.3?)
So, did anyone tried it? does it works? my friend asks me to unroot his nexus, and i want to be sure, that i'll not kill his device
VartLokur said:
So, did anyone tried it? does it works? my friend asks me to unroot his nexus, and i want to be sure, that i'll not kill his device
Click to expand...
Click to collapse
Tried, and so far it seems like I've bricked mine. When I'm supposed to see a dead Android, I have an exclamation mark instead of the "open stomach Android".
Does this work for returning to stock 4.3?
I created this account just to thank you!
It works wonders! save my life cause my nexus 4 was doomed when I installed Cynogenmod with the Cynogenmod Installer.
My wifi not working. Phone not responding when I receive a call and many more problems! Thanks to your guide I'm able to restore it perfectly.
One small problem when I using this guide is one of the steps require us to type in "4.2UnrootNexus4.zip" (actually just type "4.2UnrootNexus4)
Hi guys, I have a little doubt of upgrading my HTC Nexus One :fingers-crossed:
First of all: The power button is broken (I'm searching where to buy this piece)
I was reading to upgrade the BlackRose to a newer version, using the comand line in Windows.
But the main doubt is: If I upgrade the BlackRose, does it affect the current ROM? (I'm using CM 7.2)
Thanks in advance
please expand upon your question
I have the power button broken too.
I don't know where to buy it.
But about your main problem, when you use blackrose you lose all the internal storage data is lost, so also your system and your apps (etc). You have to reinstall you system and gapps after you use blackrose.
Sent from my Nexus One using XDA Free mobile app
Mirko Lona said:
I have the power button broken too.
I don't know where to buy it.
But about your main problem, when you use blackrose you lose all the internal storage data is lost, so also your system and your apps (etc). You have to reinstall you system and gapps after you use blackrose.
Sent from my Nexus One using XDA Free mobile app
Click to expand...
Click to collapse
I was searching in Amazon, but the seller sends from China :/
But, did you reinstall you OS? with the power button power?
Done
I was a litle bit nervous to update blackrose or not with the power buton broken.
But I made it and it was better! The enter menu changed, you use the trackball instead of the power buton (Yai!!) Then you install the rest of the ROM.
So, if you are thinking to do or not, do it (obviously being carefully), because I did it and works, works better.
See you
Ok, I have a week testing 4.4 on my Nexus and works awesome!
Its better than CM7, more stable.
It has a widget to turn off, reboot, enter recovery on the cellphone correctly (if you had the power buton broken) and other widget to lock the screen.
In case that your cellphone reboots and it says that media process closed, reboot your cellphone again.
Sent from my Nexus One using XDA Free mobile app
roberto081194 said:
Ok, I have a week testing 4.4 on my Nexus and works awesome!
Its better than CM7, more stable.
It has a widget to turn off, reboot, enter recovery on the cellphone correctly (if you had the power buton broken) and other widget to lock the screen.
In case that your cellphone reboots and it says that media process closed, reboot your cellphone again.
Sent from my Nexus One using XDA Free mobile app
Click to expand...
Click to collapse
That's great news! For me, I get "waiting for device" when i try to install BlackRose. In Device manager i get HTC Bootloader device unknown, none for the drivers work. Got an idea?
ultra99 said:
That's great news! For me, I get "waiting for device" when i try to install BlackRose. In Device manager i get HTC Bootloader device unknown, none for the drivers work. Got an idea?
Click to expand...
Click to collapse
What OS are you using? If you're using W8/8.1 it doesn't work (at least for me), I tried with W7.
Does it start your "old" Android OS?
Do you have the Stock ROM and Stock Bootloader?
You have to read and understand this post to install BlackRose:
http://forum.xda-developers.com/showthread.php?t=1270589
roberto081194 said:
What OS are you using? If you're using W8/8.1 it doesn't work (at least for me), I tried with W7.
Does it start your "old" Android OS?
Do you have the Stock ROM and Stock Bootloader?
You have to read and understand this post to install BlackRose:
http://forum.xda-developers.com/showthread.php?t=1270589
Click to expand...
Click to collapse
I have CM 7.1, 2.3.7. I'm on win 8.1 pro. I think i have the stock android recovery.
For some reason, in Bootloader: BlackRose, Radio-5.12.00.08; Nov 28, 2011
ultra99 said:
I have CM 7.1, 2.3.7. I'm on win 8.1 pro. I think i have the stock android recovery.
For some reason, in Bootloader: BlackRose, Radio-5.12.00.08; Nov 28, 2011
Click to expand...
Click to collapse
Use other computer with Win 7, I had that problem in terminal saying that message.
PD: Don't use VM, it does't work.
roberto081194 said:
Use other computer with Win 7, I had that problem in terminal saying that message.
PD: Don't use VM, it does't work.
Click to expand...
Click to collapse
FInally, blackrose flashed in win7.