Related
Hello all,
I think I may have bricked my nexus one. It is completely my fault for attempting things that I knew little about, so flame away But after the flaming, if anyone is willing to help I would be sooooo thankfull...
I successfully rooted my phone following the instructions on this page: (all links edited with a double asterisk as I don't believe I can post links)
h**p://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
Then successfully installed cyanogenmod (which is awesome!) following this page:
h**p://theunlockr.com/2010/01/08/how-to-load-a-custom-rom-on-the-nexus-one/
All was well, I even got the modaco desire rom up and running, and was happily switching back and forth using the recovery screen. I had nand backups for specific setups, etc.
Then I decided it would be good to know how to go back to stock, and found this page:
h**p://**w.androidspin.com/2010/05/06/guide-unrooting-your-nexus-one-its-like-it-never-happened-almost/
I followed the instructions to the letter (I think) except for erasing userdata (it said "failed: remote not allowed"). I thought that things would be ok, since I'd recently wiped, so I followed the page till the end.
The phone rebooted, and I got the original nexus boot animation - but it's in an endless loop! What's worse, it that now when I try to go to the bootloader or recovery mode, I get the exclamation triangle with the little android.
Is there any way through a command prompt (or other method) that I can fix this? I tried to re-flash the RA recovery image through the command prompt, but the response was, "waiting for device."
ANYTHING that anyone can suggest to help, I would be so thankful! I've been loving the nexus, and hate to think that I crippled it
Thanks in advance,
Randy
I doubt its bricked.
Noticed you didnt mention that fast boot doesnt work? (power button+trackball) try it.
Once you get to fastboot you can flash any ROM back. (fastboot flash **** commands from a command shell)
Did you ever perform a Nand Backup from Recovery?
It's not bricked, the only way to brick is to interrupt power when flashing a Radio image
Connect phone to PC. Open command prompt.
adb reboot recovery
Wipe, reflash.
So far, nobody has managed to brick a Nexus. There is no way as the fastboot mode can restore the whole phone and can't be messed with. Make sure you have the latest version of the SDK with correct USB drivers and fastboot. Then try and reflash the recovery image.
-------------------------------------
Sent from my Nexus One
nexus5894 said:
So far, nobody has managed to brick a Nexus. There is no way as the fastboot mode can restore the whole phone and can't be messed with. Make sure you have the latest version of the SDK with correct USB drivers and fastboot. Then try and reflash the recovery image.
-------------------------------------
Sent from my Nexus One
Click to expand...
Click to collapse
Actually...
http://forum.xda-developers.com/showpost.php?p=6320068&postcount=404
Paul22000 said:
Actually...
http://forum.xda-developers.com/showpost.php?p=6320068&postcount=404
Click to expand...
Click to collapse
............................
It worked!!!!!
It worked!!
britoso, thank you soooooo much! The only way that I knew to get into bootloader/recovery was via power button/volume down, but power/trackball brought up the bootloader screen, and I clicked on fastboot. I was able to flash the RA recover image through the command terminal via fastboot, then able to get into recovery. I had cyan and modaco sense on the sd, and was able to flash one of them on.
I never thought I'd be so happy to see "quietly brilliant"!!! I WILL buy you a beer, a case in fact as soon as money clears my paypal account.
I have learned my lesson, research research research. (I did do some, but not enough to feel comfortable with what I was doing - hence my cry for help!)
Other than the phone and OS itself, the thing I like most about the nexus is the fact that one CAN root, and then customize (sold a Telus moto droid because I could not do that very thing).
I digress... thanks again so much!
And Paul, thanks for your sense ROM; I've had HTC phones from the Touch to the the diamond to the Hero, and missed the UI!
Randy Malkoski said:
It worked!!
britoso, thank you soooooo much! The only way that I knew to get into bootloader/recovery was via power button/volume down, but power/trackball brought up the bootloader screen, and I clicked on fastboot. I was able to flash the RA recover image through the command terminal via fastboot, then able to get into recovery. I had cyan and modaco sense on the sd, and was able to flash one of them on.
I never thought I'd be so happy to see "quietly brilliant"!!! I WILL buy you a beer, a case in fact as soon as money clears my paypal account.
I have learned my lesson, research research research. (I did do some, but not enough to feel comfortable with what I was doing - hence my cry for help!)
Other than the phone and OS itself, the thing I like most about the nexus is the fact that one CAN root, and then customize (sold a Telus moto droid because I could not do that very thing).
I digress... thanks again so much!
And Paul, thanks for your sense ROM; I've had HTC phones from the Touch to the the diamond to the Hero, and missed the UI!
Click to expand...
Click to collapse
Glad to hear it. You learn the most by trial and error.
I think i got the same problem. i tried to Unlock Bootloader and Root Google Nexus One which was successful but then i tried to superboot it and when it came to the part where you "double click the ‘install-superboot-windows.bat’ file" i clicked it but it did not go to the nnext screen where the superboot completes it just stayed at the "bootloader screen". i must hve not done something or done something wrong i dont know.
So then i unplugged the phone from the pc and rebooted it. when it reeboted i wasnt getting any network, the phone was slow and the notification bar would not slide down...also i noticed the phone restarting on itself...
/i tried all kinds of "restore to factory settings" but not solved. Can anyone tell me what to do tht will work. I coud not understand what was said in the above thread as i am new to this android n my first time rooting n stuff n i believe that solution would work for me too..if some one could please explain in simple tirms the steps i need to take would be good...
Really appreciate it....
revonomics said:
I think i got the same problem. i tried to Unlock Bootloader and Root Google Nexus One which was successful but then i tried to superboot it and when it came to the part where you "double click the ‘install-superboot-windows.bat’ file" i clicked it but it did not go to the nnext screen where the superboot completes it just stayed at the "bootloader screen". i must hve not done something or done something wrong i dont know.
So then i unplugged the phone from the pc and rebooted it. when it reeboted i wasnt getting any network, the phone was slow and the notification bar would not slide down...also i noticed the phone restarting on itself...
/i tried all kinds of "restore to factory settings" but not solved. Can anyone tell me what to do tht will work. I coud not understand what was said in the above thread as i am new to this android n my first time rooting n stuff n i believe that solution would work for me too..if some one could please explain in simple tirms the steps i need to take would be good...
Really appreciate it....
Click to expand...
Click to collapse
Tell me what i need to download again and how to go about it...i really need my phone working again ((((
Some time ago i used the rom manager, to install a new recovery. Ever since then, every time i boot the G1 it boots all the way up, to Cyanogens froyo build, and it FC once i unlock the device,(with the slide unlock screen). Tried to reboot into recovery via home+power buttons, but nothing at all happens..... once i release the buttons it just boots up normally. Is there a way to fix this problem? Or is this G1 seen the last of its days?? I wish i could post the rom build version and the recovery what was supposedly "updated" but this happened over a month ago. I have been using a tp2/tilt2, but windows mobile is garbage and gives me a migraine,(rather have root canal than use windows mobile). Can someone please help me fix this????
wow, thanks for the overwhelming support!!!! You guys are the best!!!
get use it here, i posted about like 3 questions waiting and i end up finding and doing it on my own, But if you are able to boot into rom you are not bricked at all..
brick is only when you cant boot into recovery or bootloader, and you only get tmob screen or jus plain black screen
Q&A forum is normally faster.
As already said, you are not bricked. There has been a warning somewhere not to flash a recovery from cm5/6, not that anyone read it...
As you are on CM6 I guess you have death spl. If you want your recovery back, download you favourite one and flash it via fastboot.
fastboot flash recovery recovery.img
Info on fastboot: http://forum.xda-developers.com/showthread.php?t=532719
mblaster said:
Q&A forum is normally faster.
As already said, you are not bricked. There has been a warning somewhere not to flash a recovery from cm5/6, not that anyone read it...
As you are on CM6 I guess you have death spl. If you want your recovery back, download you favourite one and flash it via fastboot.
fastboot flash recovery recovery.img
Info on fastboot: http://forum.xda-developers.com/showthread.php?t=532719
Click to expand...
Click to collapse
yah, ive been trying to mess with the android sdk, but more or less i was wondering if there was another way. The main reason is i dont know if i have all of the right java plugins. The more i mess wiht it, i realize that it isnt worth my time. Anyone want it?!?!?!?! Will send it to them. Just gonna buy one of the new Samsung Galaxys. Let me know i have no need for it
alroco20 said:
yah, ive been trying to mess with the android sdk, but more or less i was wondering if there was another way. The main reason is i dont know if i have all of the right java plugins. The more i mess wiht it, i realize that it isnt worth my time. Anyone want it?!?!?!?! Will send it to them. Just gonna buy one of the new Samsung Galaxys. Let me know i have no need for it[/QUOTE
Your doing too much with the SDK.
Simply install it, dont worry about that java stuff, just install it. Put your recovery in the tools folder. Open command line and fastboot your recovery in.
That java stuff is for developers --- you just need the fastboot executable and the recovery file in the tools folder and you can flash it in. And then go get a Samsung Galaxy or whatever.
Click to expand...
Click to collapse
Alright, so last night I was fooling around with "Type Fresh," which you guys have probably heard of. It was released here... It's a font changer...
Anyway, things were going good until I tried a font named, "Joystix," which replaced quite a few of my fonts. That caused my phone to go into a crazy bootloop.
So, at this point, I do not have Clockwork Recovery. I actually have the Stock Recovery. For some strange reason, my stock recovery just takes me to a screen with a red triangle, and factory reset just shows this hard drive and a loading bar that never goes anywhere before rebooting my phone into a boot loop.
I've checked to see if ADB will work in my stock recovery, and it does, except for the fact that my phone is, "offline," which is probably not good.
Is there anyway I can get my phone to work again? I remember when I was getting bootloops and I somehow got the phone to reinstall all the correct stuff after going into the stock Volume Down+Power thing a few days ago. I don't know or remember how. Like, it was going into the whole process of giving me the choices and said, "Do you want to update?" I said yes and voila, everything is back to normal. Sadly, this isn't the case atm. :|
halp
wauterboi said:
I've checked to see if ADB will work in my stock recovery, and it does, except for the fact that my phone is, "offline," which is probably not good.
Is there anyway I can get my phone to work again? I remember when I was getting bootloops and I somehow got the phone to reinstall all the correct stuff after going into the stock Volume Down+Power thing a few days ago. I don't know or remember how. Like, it was going into the whole process of giving me the choices and said, "Do you want to update?" I said yes and voila, everything is back to normal. Sadly, this isn't the case atm. :|
halp
Click to expand...
Click to collapse
Well I've never personally used type fresh to change fonts, I've done it in other ways. Just a thought for ya, but I would recommend that if you can get adb to recognize your device (cmd: adb devices) try booting into hboot(volume down + power), and see if it recognizes it regularly that way, from there I recommend trying a program called Droid. It's a windows program that I used when I messed up re-rooting my replacement mt4g (tip: Don't try rooting when having been awake for 26 hours for no apparent reason ). It has a feature called Debug Console which fixed a bootloop, and constant force close that I somehow managed. I also suggest pulling your sdcard, getting a usb scard reader, and installing the stock recovery zip (Pdimg or something like that, I forget off hand).
That's all I can think of, hope it helps
...I finally looked at my SDCard via my brother's phone.
Every thing in my SD Card pretty much has "Font" in front of it in regards to the name.
I mean... Yahoo became FontsYahoo.
wat
Solved.
For those who were wondering, I found out that I had to rename the recovery file to the PBNASFASodhwhatever it was.
Hello guys,
i got a serious and frustrating problem here.
A few days ago my xoom was stuck on the M screen, so I used a thread in the forum and recovered it.
It solved myh problem back then, but since I had 3.2 before this and the solution injected me with Android 3.01 my problems started to show themselves.
the first one is that
<b> Through Fastboot, RecoveryMod, ADB </b> and any other way you can Imagine to install a new ROM or even remove or create a file,
All of them show success message but when I check them out I see no changes.
i tried fastboot and Recovery to install nearly every ROM,Recovery and bootimage in this site but so far it was wild goose chase.
so I want to ask if I'm doing anything wrong or if you need any more information here, but please help me with this
wow I cant believe it, All these masterminds here and no answer to my distress signal??
Guys I am so in trouble and this is the only place I hoped to get answered.
I can provide you with more info if you need, but please dont say I'm on my own here.
all these years this forum was the last hope for me.
i know I'll get my answer here one day
You are not being very clear about what you have done,, but I'm assuming that you reinstalled the stock image that got you back to HC 3.01. Can you see if you are able to get OTA updates to get you back to at least 3.1, or 3.2 if possible?
If that's my problem forgive me please, Ive written that post in 3:00AM
for the sake of clearity I should add some info:
1. I even tried stock ROMs but you see I cant even flash them (Not from Recovery nor Fastboot) the steps seem successful : it opens the package,it installs them and it says everything was a success. But when I restart the device I see nothing has changed.
2. OTA updates are the same, they keep downloading and when the sysem reboots to recovery to install them it cant find them.
3. You dont believe it if I say even files and programs that I remove from device by my hand(Android OS) are back after the first restart.
And you see it's dark magic! everything from a file to a partition are back by one reboot. I dont know what should I call it but I havent seen anything like it on the whole Internet.
So seems like I should make a competition for the xda experts here
Can you publish it so all of them can see it?
Mohfath said:
If that's my problem forgive me please, Ive written that post in 3:00AM
for the sake of clearity I should add some info:
1. I even tried stock ROMs but you see I cant even flash them (Not from Recovery nor Fastboot) the steps seem successful : it opens the package,it installs them and it says everything was a success. But when I restart the device I see nothing has changed.
2. OTA updates are the same, they keep downloading and when the sysem reboots to recovery to install them it cant find them.
3. You dont believe it if I say even files and programs that I remove from device by my hand(Android OS) are back after the first restart.
And you see it's dark magic! everything from a file to a partition are back by one reboot. I dont know what should I call it but I havent seen anything like it on the whole Internet.
So seems like I should make a competition for the xda experts here
Can you publish it so all of them can see it?
Click to expand...
Click to collapse
Actually, I have seen someone with the same problem here on this forum, but I can't recall exactly what the solution was.
Can you describe, step by step what you are doing, what cable you are connecting to your pc with, etc?
okantomi said:
Actually, I have seen someone with the same problem here on this forum, but I can't recall exactly what the solution was.
Can you describe, step by step what you are doing, what cable you are connecting to your pc with, etc?
Click to expand...
Click to collapse
That would be relief to know this could be solvable.
I will look more too.
As for your post I must say:
1. I plug the Xoom to the PC using the included cable
2. I start the xoom and start fastboot
3. on the PC system has the drivers and completely knows it
4. I start with SDK:
I. Fastboot oem unlock (Completing onscreen instructions and reboot device)
II. Fastboot mode again I use Fastboot flash boot boot.img
III. Continuing with Recovery,System
IV. Rebooting the device anything is the same.
My ROM is unchanged by the process and keeeeeeeeps giving the damn error of System process error please submit
5. And with ClockworkrecoveryMod I have the stock ROM on my sd card.
I. I choose install zip from sd card.
II.Choose the correct zip file and start flashing.
III. Choosing Wipe Data/Factory reset will take the device into a complete hang. unless I first use the mount page to mount the System/Data
IV. I reboot the device and ..... you know nothing changed.
so thats my story.
Still hope to find something about it.
Thanks...that was helpful. But now I want to know the following:
Were you rooted before the trouble started?
What did you do to recover?
If rooted, what version of CWM recovery did you have installed? Did you do a nanadroid backup? (I guess the answer is no, because you could have just restored with that).
What recovery are you accessing when trying to flash a zip file?
If you can answer these questions I will continue to wrack my brain trying to recall where I saw that thread.
Edit: please check out this thread http://forum.xda-developers.com/showthread.php?t=1370312
Some of what I said to him may help you .
okantomi said:
Were you rooted before the trouble started?
What did you do to recover?
If rooted, what version of CWM recovery did you have installed? Did you do a nanadroid backup? (I guess the answer is no, because you could have just restored with that).
What recovery are you accessing when trying to flash a zip file?
If you can answer these questions I will continue to wrack my brain trying to recall where I saw that thread.
Edit: please check out this thread http://forum.xda-developers.com/showthread.php?t=1370312
Some of what I said to him may help you .
Click to expand...
Click to collapse
Being rooted? -> Yes, The world is more beautiful with root!
to recover -> I followed this: http://forum.xda-developers.com/showthread.php?t=1097997 Shame it was Android 3.0
I use ClockworkRecovery 3.0.0.28 and I cant upgrade it cause of ... you know
And for your help I must say you are definitely the most caring person I know...
I'm off to check the provided link now
I was thinking of something that might be a reason.
I have this tiny problem:
When I go to CWM and choose Erase userData/Factory Reset Device Hangs
Click to expand...
Click to collapse
I was thinking of may be the userdata partition is corrupted and I gotta find a way to flash it completely.
Somehow I used Fastboot utility to do this and after saying Success, Nothing changed again.
Do you know any other way to physically do this job?
Hi y'all, i recently within the last month 2 months taken up a very unsual craving for delving deeper into my technology, with that being said. my tab 4 7.0 sm-t230 i Downloaded an app called "lucky patcher" was messing with it, been reading about deoxe(ing) my tablet,it gave me the option to do it for me (usually i enjoy the challange of using a emulated terminal and what not) but every file etc would take too long, and it worked, my daughter ot well over 150 million score on subway surfers etc. i notice my phone sluggish even bein over clocked, I/Os that i did myself, running max cpu and performance i could blabber forever since my 3 kids arnt interested in my newly found hobbie and my husbands a truck driver, i'm getting it out here (i'm sorry but i do need help) so anywyas i decided to kick her into recovery and begin to just manually delete all the dex copied files through TWRP went good till i wetn to reboot after staring at my screen for 3 hours and got threw up on twice from sick babies and i was boot looped. i decide to restore a previous freshly flashed rom/root backup. well they were deleted too. and all i could do was a master re format i think is what i read it was called, and excited to get back and re download everything i notice i now have no OS and no recoveries and TWRP fulll of emptiness. i can play through TWRP i've changed file permissions i've tried everything ive read and tried everything i learned and experianced to fix this issue, and yet stillno idea how to fix this issue..
Now the fun part is my set up. the only pc i have means and access too is my samsung Chromebook, and my tablet, that's it, no phone because my tablet handles everything my little heart can desire.
needless to say, i need some kinda recovery tool kit i can use via my chromebook, that'll allow me to use ADB for chrome (which another question i have is how do i enable my tablets USB debugging if i can't get into the phone?) so toolkit for chromebook for a ADB side load if possible. or some way to do it through my emulated terminal in TWRP,. my minds rushing, i'm confused and my over emotionally stressed female head is killing me without my tablet. (drive to any town where i could use anything but my chrome book. 3.5 hours.
sorry i pray this post doesnt get deleted. I need help because my tablet is my main source of income being in real estate when i'm back in town once a month. never made a page or a forum or anything like this usally google magic does it. but 3 days and countless mind numbing forums i've given in.. please help me! i'll donate pay something idc at this point. -a pissed off irish southen woman on the verge of pms and a meltdown thanks in advance i'll try to reply as fast as humanly possible, ill be up for awhile tonight going through more posts.
0well with a little more tinking around, i think i have found the issue as too why no matter what i do i'm unable to boot a rom/os. mt EXT3 wil not mount my system i'm clueless as to how to fix that at all threw TWRP, anyone have an idea of any kind please? i'm for anything, even if after more attempts and countless hours, i'll record me skipping it across my lake, and we'll all take guesses as too how many skips it'll do. hopefully my dog will fetch it if i throw at the wrong angle. (completely dumb jokes are the only thing keeping me from returning Sain.) we all cant be too serious. please very interested on how to fix this issue tho.
s,
you need to get a custom rom zip onto an sdcard, check development section.
in twrp, flash the rom,
if the rom still doesn't boot, then reboot to twrp again and use the format data option, then reflash rom and try again.
twrp terminal sucks, you can try flashing aromafm https://www.androidfilehost.com/?fid=95916177934547314
this is for the marvell variant, it may work for the msm/qcom variant.
stop using lucky patcher.
m
moonbutt74 said:
s,
you need to get a custom rom zip onto an sdcard, check development section.
in twrp, flash the rom,
if the rom still doesn't boot, then reboot to twrp again and use the format data option, then reflash rom and try again.
twrp terminal sucks, you can try flashing aromafm https://www.androidfilehost.com/?fid=95916177934547314
this is for the marvell variant, it may work for the msm/qcom variant.
stop using lucky patcher.
m
Click to expand...
Click to collapse
Hi, that's where another problem lies within, I have no way of communicating with the phone or being able to do much, considering the only pc/laptop i have access too is my chromebook, and this thing is a ssteaming pile of regurgitated dog bile. if theres one regret in life.. buying this thing.. even dual booted i still can't process the zips or compile them properly, maybe i need to find out how to build a zip file from scratch and comepile the corresponding stuff myself in small hopes it'll work on this chromebook
and yes, never again will I use that. it worked don't get me wrong. but then it decided to deodex my system to oblivion.
s,
hey that rhymed !
your alternative is to use a usb thumbdrive and an otg cable , else nada.
m
moonbutt74 said:
s,
hey that rhymed !
your alternative is to use a usb thumbdrive and an otg cable , else nada.
m
Click to expand...
Click to collapse
I'm gla you have a sense of humor, thank you hun. looks like i'm tabletless until i go back into town in two weeks ): i suppose till then i will tinker with it some more and unlock the universe, or find a way to convert zips that are made for windows or mac and be able to convert it to be able to be used and transfered unto the phone. Chromium os or chrome now has ADB for chrome as an extension but very iffy, has 3 options to screen record/screenshot and terminal. i was able to use vitural box for about 2 hours and force odin to pretend i was on a widnows enough to orignally root, then it crashed my chromebook. Maybe i've gotta achieve 88 mph first to get this thing to work? lol my chromebook "overclocked" 810 mghz.... maxx.... frequency says it can go to 2100... i think if i even try that i'd recreate the "hydrogen bomb"