Guest Posted June 20, 2010 Report Posted June 20, 2010 (edited) Heres the deal, and hopefully someone can help me. I unlocked my bootloader, and rooted my N1, running RFR50. Then when RFR79 came out, I found a img and updated my phone... then it went wacko. I was getting lots of forced closed apps, "Process system is not responding" and I have no bars of cell service (I have t-mobile), and I have a few moments when the little nexus flare logo comes on, and I guess the desktop restarts. I tried reimaging it to RFR50 again, and it took, but still same errors, graphics look a lil funny/fuzzy, and now when I start the phone with the trackball pushed in, it doesnt go to the bootloader. Now I dont know how to fix it! PLEASE HELP. Im somewhat a newbee to the android moding, so Im sorry for the generalizations ;) . Thanks for any help. Edited June 21, 2010 by Guest
Guest Batkoto Posted June 20, 2010 Report Posted June 20, 2010 (edited) Heres the deal, and hopefully someone can help me. I unlocked my bootloader, and rooted my N1, running RFR50. Then when RFR79 came out, I found a img and updated my phone... then it went wacko. I was getting lots of forced closed apps, "Process system is not responding" and I have no bars of cell service (I have t-mobile), and I have a few moments when the little nexus flare logo comes on, and I guess the desktop restarts. I tried reimaging it to RFR50 again, and it took, but still same errors, graphics look a lil funny/fuzzy, and now when I start the phone with the trackball pushed in, it doesnt go to the bootloader. Now I dont know how to fix it! PLEASE HELP. Im somewhat a newbee to the android moding, so Im sorry for the generalizations ;) . Thanks for any help. First things first, you need to make your device enter in bootloader. This is how you can run recovery and fastboot. So, give it few more tries to get into bootloader try this: 1. remove battery, put it back in, trackball + power on (fastboot). If this doesnt get you into bootloader, try option 2 2. power on and press volume down (bootloader) Edited June 20, 2010 by Batkoto
Guest Posted June 20, 2010 Report Posted June 20, 2010 And thats the issue, neither of those work any more... It just shows the picture of the nexus one symbol with a unlocked lock, then it goes to the flying colors of the nexus symbol, and then it boots. Is there any other way. Also, in the OS, the usb storage option doesnt come up when I plug in a usb to a computer.... Thanks for the suggestion though.
Guest glitzbd Posted June 20, 2010 Report Posted June 20, 2010 Can you enable USB debugging? If so you can use ADB! Use the command "adb reboot recovery"
Guest Posted June 20, 2010 Report Posted June 20, 2010 Can you enable USB debugging? If so you can use ADB! Use the command "adb reboot recovery" Your right, ADB does work while the OS is on So, I would type adb-mac reboot recovery ____________.img? (with the img file in the same folder on the computer with the adb-mac) Where do I get a img that has unrooted and fixes my radio back? I have a full membership on modaco. I think the img I cooked killed it. Thanks to all!
Guest Posted June 20, 2010 Report Posted June 20, 2010 (edited) Well, I think I found another snag, the phone is very unstable, and when I send ./install-superboot-mac.sh to re-root it, to restore backup it responses back with "waiting for device"... and just sits there. Any ideas? update: fastboot-mac devices comes back without any response I tried abd-mac reboot recovery and it reboots the OS, no recovery mode came up. I can abd-mac shell and it comes back with # Edited June 20, 2010 by Guest
Guest Shuflie Posted June 20, 2010 Report Posted June 20, 2010 Have you tried holding vol-down, power and trackball while the OS is running then releasing only the power button?
Guest Posted June 20, 2010 Report Posted June 20, 2010 Have you tried holding vol-down, power and trackball while the OS is running then releasing only the power button? Thanks for the help, but it just rebooted like usual, no bootloader
Guest Shuflie Posted June 20, 2010 Report Posted June 20, 2010 Don't really know what else to try, except perhaps without your SIM and memory card inserted.
Guest Posted June 20, 2010 Report Posted June 20, 2010 Don't really know what else to try, except perhaps without your SIM and memory card inserted. Tried without sim an sd, same thing, it just restarted os, no bootloader
Guest guruvan Posted June 20, 2010 Report Posted June 20, 2010 Tried without sim an sd, same thing, it just restarted os, no bootloader If you have any access to the device, you might look into how they're solving bricked desires & evos http://android.modaco.com/content/htc-desi...d-b0rked-fixed/ http://forum.xda-developers.com/showthread.php?t=695243
Guest Shuflie Posted June 20, 2010 Report Posted June 20, 2010 You could this with the AmonRA recovery image file copied to the root of the SD card and type adb flash_image recovery /sdcard/recovery-RA-nexus-v1.6.2.img Getting the image on there if you don't have access to an SD card reader might be tricky though, try this adb push recovery-RA-nexus-v1.6.2.img /sdcard then adb shell sync Good luck
Guest Shuflie Posted June 20, 2010 Report Posted June 20, 2010 Missed a step or two out, you need to copy the flash_image script across to the phone, full instructions and links are here
Guest Posted June 20, 2010 Report Posted June 20, 2010 (edited) Missed a step or two out, you need to copy the flash_image script across to the phone, full instructions and links are here Again, thanks for all the help: I was able to go step by step and got to the last step to type: ./adb-mac shell flash_image recovery /sdcard/recovery.img but it came back with: error opening /sdcard/recovery.img: No such file or directory Someone on the internet said to try ./adb-mac shell flash_image recovery /sdcard/recovery.img recovery.img and that came back with no error, so I guess that took. But when I restart, nothing changed. Found more wierd tings going on, I can join wifi, and go to webpages, but the market freezes and when the phone crashes with the X graphics, it closes the market again. Cant download anything. Then, I found that when looking at the space of the sd, it says: total space unavailable, available space, unavailable. Im about done trying to find a answer, and I think my phone is bricked. Can I send it to HTC and pay to have it restored? Is there any "well established" folks on this site that are up to the challenge of fixing it for a fee?? Edited June 20, 2010 by Guest
Guest Posted June 21, 2010 Report Posted June 21, 2010 Ok, I know Im not crazy, and Ive used the bootloader in the past and it worked. I found a forum when someone had the same issue with the HD2 at http://forum.xda-developers.com/showthread.php?t=689768 I dont know if the file they used to fix it will work on the nexus one though.
Guest stevenz Posted June 21, 2010 Report Posted June 21, 2010 Can you not do; adb reboot bootloader to get into Fastboot and then use fastboot to reinstate the recovery & boot images? It might be an idea to flash an older radio onto it as well as a known good 2.1 image. ADB should be available from mid-way during the boot process once the underlying OS has initialised.
Guest Posted June 21, 2010 Report Posted June 21, 2010 Can you not do; adb reboot bootloader to get into Fastboot and then use fastboot to reinstate the recovery & boot images? It might be an idea to flash an older radio onto it as well as a known good 2.1 image. ADB should be available from mid-way during the boot process once the underlying OS has initialised. Thanks for your response but adb reboot bootloader just has the phone reboot directly to the OS.... It wont boot to the bootloader.
Guest stevenz Posted June 21, 2010 Report Posted June 21, 2010 (edited) So you've managed to fry at least part of the bootloader. The string you used above; ./adb-mac shell flash_image recovery /sdcard/recovery.img recovery.img Might not work - the 2nd "recovery.img" is unnecessary. You should've got a couple of lines of text afterwards saying that it was doing something. On a mac you WILL need the ./ in front of the command unless the adb-mac binary is in a searchable path (which it won't be). You will probably need; sudo ./adb-mac flash recovery /sdcard/recovery.img which should do the job. The fact that the phone won't boot into the bootloader is not encouraging though. If you can get the recovery image to work and restore a nandroid backup of a working image AND flash a known good radio image then it MIGHT get it going again, but I wouldn't be on it. the "shell flash_image" you were told to use relies on an app in Cyanogenmod which may, or may not be on your phone. I think it's pretty standard in most images(?) now so it should be ok. The string above should work though. Assuming the "adb shell flash_image" works, and you have a nandroid backup, then you can flash MOST of the partitions with that command, more info here: http://forum.xda-developers.com/showthread.php?t=532113 if it doesn't work, then you can download and install the tool from this page; http://wiki.cyanogenmod.com/index.php/RE-recovery-img Includes instructions on how to get it onto the phone. Gotta say that I don't fancy your chances though... Edited June 21, 2010 by stevenz
Guest Posted June 21, 2010 Report Posted June 21, 2010 So you've managed to fry at least part of the bootloader. The string you used above; ./adb-mac shell flash_image recovery /sdcard/recovery.img recovery.img Might not work - the 2nd "recovery.img" is unnecessary. You should've got a couple of lines of text afterwards saying that it was doing something. On a mac you WILL need the ./ in front of the command unless the adb-mac binary is in a searchable path (which it won't be). You will probably need; sudo ./adb-mac flash recovery /sdcard/recovery.img which should do the job. The fact that the phone won't boot into the bootloader is not encouraging though. If you can get the recovery image to work and restore a nandroid backup of a working image AND flash a known good radio image then it MIGHT get it going again, but I wouldn't be on it. the "shell flash_image" you were told to use relies on an app in Cyanogenmod which may, or may not be on your phone. I think it's pretty standard in most images(?) now so it should be ok. The string above should work though. Assuming the "adb shell flash_image" works, and you have a nandroid backup, then you can flash MOST of the partitions with that command, more info here: http://forum.xda-developers.com/showthread.php?t=532113 if it doesn't work, then you can download and install the tool from this page; http://wiki.cyanogenmod.com/index.php/RE-recovery-img Includes instructions on how to get it onto the phone. Gotta say that I don't fancy your chances though... Thanks for your response and help on this. Yes, I was just leaving ./ out of the post, but I was using it. When typing the command: sudo ./adb-mac flash recovery /sdcard/recovery.img I get a response of Android Debug Bridge version 1.0.25 -d - directs command to the only connected USB device and so on (all the switches and uses of adb-mac) So thats not working still. People say there is plenty posts about sending the phones to HTC for repair, but I havent found one yet on how/where/how much $ etc. Any ideas?
Guest Posted June 21, 2010 Report Posted June 21, 2010 as for the instructions on http://wiki.cyanogenmod.com/index.php/RE-recovery-img I am fine until the last directions: adb shell flash_image recovery /sdcard/recovery.img Yes, Im sure recovery.img is on my sd card too! I get the error back: error opening /sdcard/recovery.img: No such file or directory
Guest stevenz Posted June 21, 2010 Report Posted June 21, 2010 (edited) as for the instructions on http://wiki.cyanogenmod.com/index.php/RE-recovery-img I am fine until the last directions: adb shell flash_image recovery /sdcard/recovery.img Yes, Im sure recovery.img is on my sd card too! I get the error back: error opening /sdcard/recovery.img: No such file or directory Does: adb shell get you to a $ shell prompt? If so you could try running "flash_image recovery /sdcard/recovery.img" directly from there. You may need to use; adb remount first, but not generally needed for sdcard access. From the shell you could try; cd /sdcard ls and see if you get a directory listing and make sure the recovery.img file is showing up. It's case sensitive too, so "Recovery.img" is not the same as "recovery.img". Edited June 21, 2010 by stevenz
Guest Posted June 21, 2010 Report Posted June 21, 2010 yes ./adb-mac shell gives me a # but no $ I used ./adb remount (remount succeeded) so I tried ./adb-mac shell #cd /sdcard #ls (it didnt give any responses, no listing of files) Like I said in a earlier post, the phone gui says that the sd card size is unavailable and the sd available space is unavailable. Do you think thats stopping me from accessing the sd-card?
Guest guruvan Posted June 22, 2010 Report Posted June 22, 2010 People say there is plenty posts about sending the phones to HTC for repair, but I havent found one yet on how/where/how much $ etc. Any ideas? People who had sent their "usbbricked" Desires were being quoted around $150-180. It's just a matter of calling HTC's repair department. If you can sift through the output of adb shell cat /proc/kmsg you may be able to spot errors (and post some relevant chunks) Once you can get a file onto the sd card you should be able to repair yourself.
Guest maedox Posted June 22, 2010 Report Posted June 22, 2010 $ adb shell # mount|grep sdcard /dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702 allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro) tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000) Do you get an output similar to that? If not your sdcard is not mounted, and you need to look through logfiles to find the error, or wait for someone more experienced to show up and help you with the mounting. Did you try sending fastboot commands before trying to reboot to fastboot? That may actually work even if it does not show you the fastboot prompt. Something like fastboot boot recovery.img to get into recovery.
Guest nieldk Posted June 22, 2010 Report Posted June 22, 2010 Since you obviously cant seem to get flashing a working recovery to proceed. Have you tried just booting a recovery image, not flashing it ? fastboot boot recovery.img (or whaterverthenameofrecovery.img) This should boot the device with the specific recovery (AmonRA i suggest) and then you could from there perhaps restore a working nandroid backup, or flash a complete image from an update.zip file. This is all of course assuming that you can figure out why you cant list / access the sdcard. Did you try adb push recovery.img /sdcard/ adb sync adb sync is to ensure that the file is written in complete to sdcard. Does the adb push command spit out errors ?
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now