First of all, I have checked around quite a bit on this forum as well as others to try and avoid having to ask a question that's already been answered. Here's my problem/ what happened. I was rooted (one-click with locked bootloader) and had tried out several roms for a couple of months now. A few days ago I reverted back to an old stock 2.2 backup. My phone received two ota updates and I'm pretty sure I lost root. I had just went on using the phone for about two days when I ran into a problem today. After shutting the phone off I have now become "stuck" at the initial "X" screen (not animated). I pulled the battery and tried again several times. I then tried to reboot into recovery from the bootloader/ 3 skateboards screen with no luck. Any time I hit recovery it simply takes me back to my stuck "X" screen. I have an entire backup of my SD card from earlier as well as at least 4 nandroid backups (one of which was the stock 2.2 before the latest ota). I am thinking I need to somehow put clockwork recovery back on my phone so I can restore to one of my backups. I do not know how to do this. Sorry for the lengthy post but I want to provide as much information as possible. Any help at all would be greatly appreciated.
Just like you restore to stock 2.2. You should have used recovery.img. use adb fastboot to put the stock or anom recovery. I am not am expert but I have had the same problem few times. Always use adb commands
Sent from my Nexus One using Tapatalk
Does my n1 have to be in usb debugging mode because it's acting like it's not connected or something. I get the message "error: device not found." I'm on the fastboot screen on my n1 and using terminal on a mac. I usually didn't leave debugging mode on
No it doesn't but you have to have the drivers installed as well as the SDK with dependencies.
Whew! Thank God! I ended up getting a FRG33 stock rom onto the sd card and the bootloader detected it. I'm not sure what happened but when I tried recovery after that it took me to the android with an "!" point (meaning no recovery?) and then back to the X. This time however it loaded on through and went right back to the way it was before it was stuck. Again, not sure what happened but thanks for the replies and help.
fastbook oem unlock
install Amon RA recovery
flash new rom.
Caseyp789 said:
Whew! Thank God! I ended up getting a FRG33 stock rom onto the sd card and the bootloader detected it. I'm not sure what happened but when I tried recovery after that it took me to the android with an "!" point (meaning no recovery?) and then back to the X. This time however it loaded on through and went right back to the way it was before it was stuck. Again, not sure what happened but thanks for the replies and help.
Click to expand...
Click to collapse
The exclamation mark is just the stock Android recovery - it was re-installed when you loaded the stock FRG33 ROM.
Performing OTA updates requires you to have the stock recovery installed. Simply reverting to a stock 2.2 nandroid isn't sufficient, so trying to install those OTAs (which should have failed without stock recovery) may have broken something there.
GldRush98 said:
fastbook oem unlock
install Amon RA recovery
flash new rom.
Click to expand...
Click to collapse
This is by far the easiest (and safest) way. Google/HTC provided us an easy and safe method for gaining full access to our phones.... Why so many people refuse to use it is beyond me. If you root it the proper way (with fastboot oem unlock), it will make recovery from any further issues a lot more simple.
From what I can tell, I am having the same symptoms as the topic creator. I believe the problems started during a failed flash of cyanogenmod 6, but I am not sure by what means the flashing took place.
I can't boot the phone normally, it hangs on the X splash screen and the same occurs when trying to enter recovery mode.
I have tried the passimg approach to fix this, it either doesn't recognize my zip or starts loading it and freezes on a loading bar.
Fastboot flashing recovery completes, but doesn't fix the issue.
I can fastboot flash every image partition except system or radio, both hang.
As danger rat and dude random both know, I have posted this problem on the nexus one forums but I thought I'd post here to have some more minds look at it.
Related
I haven't touched my Rogers G1 rom, it is as stock as they come. One day the battery died, so I plugged the phone to charge and also tried to start it up.
My problem started after that.
I will try to restart the phone and it'll get stuck on boot screen - where it says HTC or sometimes even just the Rogers screen.
Only solution is to take battery out, do hard reset.
I've searched the forums but everybody else asks regarding modded roms and not stock.
Any idea how I could resolve this issue without flashing new roms? Or is that my only way out?
Thanks.
Did you apply Rogers mandatory 911 update that was released about a year ago? You can check by booting into fastboot mode (hold the camera button while powering it on). If your radio version is 3.22.26.17 you have the update. Rogers locked down fastboot in this latest update and the only way to root it is through the ROM. If you don't have this update I can walk you though the steps to root your phone though fastboot.
Just checked and it does have the update.
Should I just go ahead and flash new roms?
I keep having the same issue as before.
With the latest update Rogers locked down fastboot so it is useless. So, I don't believe that there is any way to flash a new ROM without first booting into your existing ROM.
Sorry but I'm inexperienced with flashing roms...
If I can't flash by the fastboot method, I can still flash by rooting the phone, correct?
JiggyNS said:
Sorry but I'm inexperienced with flashing roms...
If I can't flash by the fastboot method, I can still flash by rooting the phone, correct?
Click to expand...
Click to collapse
I'm not completely sure, but usually you need to be able to get into the rom to root. Maybe there is another way.
6 hours later and i got nowhere...
I rooted phone, flashed new cyanogen rom, setup amon ra's recovery but I didn't do new radio since my current is one of the newer ones.
The booting goes nowhere as soon as the rogers logo shows at the beginning of boot up.
Would a new radio help? Could that be the issue?
edit:
The phone rebooted properly and now I have a working fone!
Wait, how did you root the phone without getting into the ROM?
beav_35 said:
Wait, how did you root the phone without getting into the ROM?
Click to expand...
Click to collapse
I used the Androot method, copied onto sd card, launched file via file manager app on phone and it rooted the phone. This is how I remember anyways - I fiddled with the phone for good part of the afternoon so my memory is all over the place with the specifics.
I used this site for rooting.
I thought you said in the op that you couldn't boot into the ROM (got stuck on boot screen). So, what was the problem in the first place? (or how did you fix the ROM?)
Sorry I guess I wasn't clear enough in op.
The only way I could get to use the phone was to do a hard reset and let the phone boot up from there, however if I ever wanted to turn the phone off or restart the phone it would get stuck on the next boot up.
I was able to flash the rom by constantly hard reseting the phone every time I needed to put files onto the memory card.
Hi all,
I have had my N1 for 1year and two weeks now (yes, warranty just expired). I was charging the device and it seemed to overheat and reboot. I unplugged it, took the battery out, let it rest for a bit and tried to boot it again. The phone now gets stuck on the X logo (not moving) and never boots.
I'm currently abroad (in the UK) and can't have it sent back for repair (I'd have to pay the repair too).
Will rooting the phone and installing an alternate OS fix my phone?
Is there any way to get HTC to honor the warranty after two weeks of expiration (I've been getting this problem for a while now, but that was only an issue if I made extensive use of the device while charging, which I almost never do so I didn't bother.)
Is there any way to fix this issue without messing with rooting? I'm abroad right now and all I want is my phone to work.
Any suggestions are welcome.
Try booting into bootloader from power off (vol- pwr) if that doesn't work then try the 3 figure salute (pwr vol- tb) your phone should boot into fastboot then just select bootloader.
If either of these work the your good you can get the static x fixed all you need to do is passimg (search wiki if you don't know what it is) as for the charging problem passimg will factory reset the phone so if that doesn't fix it then no you'll need to try rooting or it might be hardware.
Yes, I'm able to go into the bootloader.
I tried clearing the storage, choosing fastboot, etc. The phone seems to be working, just won't boot past the static X.
From your last reply, you're saying passimg has good chances to fix my phone. What does that involve? Do you have a link to a how-to that I could follow (it would really be a bad time for me to brick my phone, a good how-to would be really appreciated).
Cheers!
Yes passimg is used for many things it just reflashes a shipment ROM to the phone through bootloader. Like I said you can visit the wiki to have a how to here is a link http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_%26_Tutorials scroll down to "Unroot / Restore your Nexus" then follow the instructions. This should restore you to frg33 then you just need to update back to 2.3.4.
NOTE: this will wipe your data.
Ahh there's a way to unroot the nexus one now!
I had no idea! This is good to know (last time I checked was in December I think).
I will give that passimg a try as soon as I get home.
Can anyone confirm that this ("Attention: Latest stock ROMs don't flash using PASSIMG.ZIP method. Use the provided latest Froyo PASSIMG, and upgrade it after flashing.") means I can still reflash using this if I have the latest ROM (2.3.4) but will simply have to update again after (which I might not do given the issues I'm facing).
Cheers!
Confirmed - Dude is giving you good info... xD
Just to verify, unrooting is not the same as relocking. If you unlocked your bootloader (have a little lock symbol under the X screen), there is no way to relock it.
But the passimg is a good option. It will take you back to an older version of Android, and then you just let the system update itself.
Since you are out of your warranty, I can highly suggest looking into custom firmwares. These give you a lot more features and in many cases, perform better. CyanogenMod is probably the most popular one. These will fully replace your Android OS. CyanogenMod really doesn't even differ in look from stock all that much. Most people probably wouldn't even have a clue they are running something different, except for the stability and performance increases.
You can read up about this stuff in the wiki as well.
Oh, I see, thanks for the info.
I'm actually trying to get the FRG83 passimg file but the link is dead. Does anyone have an alternate one?
Use the FRG33 image
Alright,
I unlocked the device, used fastboot to write the recovery "Amon_Ra's Recovery".
Then I rebooted, went to the bootloader (trackball + power), went to "recovery" but the phone still gets stucked on the X (with the unlocked padlock logo).
Any advices?
Try the passimg, but it's possible that you are looking at hardware failure...
ldiamond2 said:
Alright,
I unlocked the device, used fastboot to write the recovery "Amon_Ra's Recovery".
Then I rebooted, went to the bootloader (trackball + power), went to "recovery" but the phone still gets stucked on the X (with the unlocked padlock logo).
Any advices?
Click to expand...
Click to collapse
If you are still running stock Android, you can't reboot between installing the recovery and getting into it. Stock Android will replace it. Try to go back to the bootloader and select recovery then, or fastboot to load the recovery, and then use fastboot to boot off of it.
Code:
fastboot flash recovery "c:\location to\recovery.img"
fastboot boot recovery "c:\location to\recovery.img"
Hopefully this will get you into Amon_RA so you can try again.
But the passimg method is used in the bootloader, not in recovery. You don't need a custom recovery to use the passimg method.
Amazing, thanks for pointing out my mistake, that give me a little bit of hope now . (I was at the point where I'd open the thing and look for a broken solder joint.)
I will try this as soon as I get home!
**Edit** I actually am not sure if I really rebooted or went straight to recovery. I'll update this thread tonight.
According to some other people, this would be a common issue with the internal memory dieing.
Is there a utility I can use to check the state of the memory?
None that I know of. Our phone internal memory uses the yaffs2 (Yet Another Flash File System v2) file system. I haven't heard of any programs that can check it.
Same situation
Hello, all. I haven't signed in on here in ages just because I've been so happy with how my Nexus has been running.
I ran into the same problem as OP stated.
I think I have some sort of hardware issue because my phone used to randomly freeze and couldn't be restarted unless I pulled the battery. Now it's at the point where I can't even turn it on because nothing happens when I press the power button or if I try to boot into recovery. This is really frustrating.
Is there any way to check for hardware damage? My warranty is over as well so I'd have to pay for any repairs to my phone if I sent it in.
If it's running, you can try to pull a log, and see what error reports you get?
andythefan said:
Now it's at the point where I can't even turn it on because nothing happens when I press the power button or if I try to boot into recovery. This is really frustrating.
Click to expand...
Click to collapse
Your power button might just be dead. Try having the phone plugged into a power source and removing and reinserting the battery. While you are doing that, hold the Volume Down button. This will get you into the bootloader which would allow a passimg to be performed. Hopefully your reboots aren't a hardware problem.
So , after pulling my battery, pulling the sim and the sd card, it finally turned on and went to recovery without freezing. I was able to wipe and reflash cyan 7. It's working well for now, but I'm really afraid this is going to happen again because this isn't the first time that it's just froze repeatedly.
Does anyone know what the problem could be?
Alright,
I did "fastboot flash recovery MYIMG" then "fastboot boot MYIMG", didn't work.
Then I tried "fastboot flash recovery MYIMG" then go to bootloader (without rebooting) and selected recovery.
Still no luck.
It always freezes on the static X logo. What else can I do? Will using passimg be any different (I don't have any way to put the file on the micro SD card but I can manage to do it if it's worth the shot).
Thanks
I recently acquired a locked/non rooted N1 because I needed a device as I believe I damaged my G2x trying to repair. I've had several Android phones, rooted them all etc, from the G1 to most recent G2x. The issue I am having is that once I unlocked the N1 I just got, after the first reboot, I didn't enable USB debugging, instead, I booted back into HBoot and tried to flash it with a new recovery via fastboot. That did't work, I went to reboot it again and now it's stuck on the "X' with the little unlocked image at the bottom. From here I have tried to flash passimg from recovery via update.zip's, as well as a number of roms using the same method. Any suggestions on how to get this to boot passed the X screen? Thanks.
So you tried to flash a recovery but failed. Then you tried to flash roms through recovery? Makes no sense.
Passimg method is done via fastboot anyways.
Just read the wiki/restore guide. You're clearly lost at the moment. That will explain everything.
Thanks my man, clearly I was in bafoon mode when attempting to correct the situation. Turns out, following the right guide makes the biggest difference.
Long story short: Phone won't boot past "Unlocked Bootloader" warning; Recoveries won't stick; Unknown Error & Freezing when trying to Flash System.img
I own an ATT Locked Moto X, but went ahead and unlocked it by purchasing the oem code. No issues there.
I decided to go ahead and try rooting it too, and was able to flash TWRP as my recovery. Still, everything seemed to be looking good, until I tried hard rebooting (to see if root would last). Upon rebooting, I could not get past the warning sign, notifying me that the bootloader was unlocked. I waited, and waited, and restarted again, but all progress stopped there. I would be the first to admit that whatever happened was probably my fault; perhaps I flashed some files in the wrong order, or entered a wrong command into fastboot. I don't know, and frankly don't care. My only question is how to get out of this mess and back to rooting, or at the very least, back to stock ROM now that I'm unlocked.
Booting into recovery only leads to the red triangle over an open android mascot, with the "Android Recovery" title. So clearly TWRP didn't stick; I tried reflashing, but nothing lasts past reboot. Then I tried flashing Philz Touch instead, which, upon exit, notified me that root was not enabled. So I rooted, rebooted, and was finally able to see Philz Tough again, even though I still can't boot normally. That time, both Philz Touch as well as root seemed to have stuck.
With that minor victory I downloaded the latest firmware for my model and tried to flash the components over, thinking I had somehow corrupted the existing OS files, but here's where it gets particularly frustrating. I am able to flash every file except for system.img, even though I am using moto-fastboot, which I understand is a common mistake. I get no specific error code, simply "Unknown Error," upon which the phone is frozen in fastboot. The phone remains unresponsive until I hard reboot [back into fastboot], and see that, once again, Recovery is back to stock. So now I'm baffled. I can't seem to find a way to flash the system file, factory resetting doesn't work, and my recoveries are constantly reverted back to stock. Does anyone have any advice, or suggestions for what I could try next?
You try RSD lite?
Sent from my XT1058 using xda app-developers app
southern87 said:
You try RSD lite?
Sent from my XT1058 using xda app-developers app
Click to expand...
Click to collapse
I was already downloading it just as I saw your post, as my last-ditch effort. It also failed, but it gave me "Unknown USB Error," which is all I needed, it seems. I tried a different USB slot on another side of the computer, and lo-and-behold, the flash finished.
I'm not sure what saddens me more, the fact that I pushed off making this post for hours, only to have the solution less than an hour after I do, or the fact that I never thought to try a different USB port... In any case, sorry for the uselessness of this post. I think I'll save rooting for another day though...
Hey guys, Im fairly new to this stuff, but I got a question or two, it may take me a day to reply so i'll try to put as much info as posible.
Now recently I received the OTA 4.20 (Lolipop) on my phone, so I flashed my stock recovery to download the OTA, making me reroot my phone.
So my phone is re-rooted (after 2 tries) but now it seems like I cant write to my SD card, so I got fed up and went into TWRP recovery and selected wipe data and restore. (Restore point was before I got lolipop) I try to reboot but it takes me as far as HTC One screen. Next I go to recovery and try a factory reset, says its successful, but it lied to me! Still stuck at HTC One screen. So I flash back to stock recovery to try the factory reset with that, it went for a moment, then tried to boot, getting stuck at HTC one screen again, so once more, I flash TWRP to my phone in attempt to get the recovery back, but now I can't load recovery, or boot. So Im stuck there. Is there any advice to what to do from here? I tried command 'fastboot erase cache' thinking that would do something and reflashing the recovery.img but it's still not working. I hope someone can help me.
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
The reason you can't write to your SD card isn't because of lollipop, that was actually added but on kit Kat, but the devs went and added a line of code to a file to allow it again. I am currently running my stock rooted, built from decrypted ruu, originally I wasn't able to but I added that one line of code. I believe all you have to do is flash a stock rooted and SD card write should be enabled. As for not being able to get into recovery or boot at all, boot to bootloader and ruu then flash twrp.
Ok so correct me if im doing something wrong, but I flashed the stock recovery in attempt to factory reset it, it wont work, so I flash TWRP with command line (Fastboot flash recovery twrp.img) And it's 'successful' but it wont load, it will attempt to load but one second in and it goes back to fastboot, how to I move forward from here?
Edit: so idiot me did it again, I was trying to install M7 version into a m8. Resolved, Now I can enter recovery again.
Alright, so now my only problem is now that it wont boot normally, it freezes at HTC one screen. I have access to TWRP recovery, just not sure what to do next from here.
ArthAngel said:
Alright, so now my only problem is now that it wont boot normally, it freezes at HTC one screen. I have access to TWRP recovery, just not sure what to do next from here.
Click to expand...
Click to collapse
I actually just unlocked my bootloader yesterday, installed TWRP today, and had what I thought was the same. The thing is, let it sit. Mine sat at the HTC ONE screen for what seemed to be between 5 and 10 minutes. I read that it happens in one of these threads.
But I let it sit and it eventually went to "Android is Upgrading" and was loading the apps.
dopy25 said:
I actually just unlocked my bootloader yesterday, installed TWRP today, and had what I thought was the same. The thing is, let it sit. Mine sat at the HTC ONE screen for what seemed to be between 5 and 10 minutes. I read that it happens in one of these threads.
But I let it sit and it eventually went to "Android is Upgrading" and was loading the apps.
Click to expand...
Click to collapse
Ok thanks, I'll post back in 20 minutes with an update.
So i've waited about 20 minutes on the HTC one screen, (Still on it as I post this) It is still stuck on it. I dont know if this helps but im able to view my internal and external card via computer cable, but I only see folders, no files of any kind in any of them..
Edit* I WAS able to read it, now I can't.
I GOT IT! I was able to revert to a backup I made. Even though I gotta flash stock again for OTA but F it! I got it working again. Thanks for all your help!