Related
Well, the home button on my unlocked G1 stopped working about a week or so ago. No big deal, but the problem I now face is that I am unable to install any new roms.
I am able to boot into recovery mode (cyanogen v1.4) using ADB, however once there, I am unable to install a new rom since my home button does not work.
Is there any way around this either using the phone or through my computer (I am using MAC OS 10.5). Any help would be GREATLY appreciated.
- Thomas
fastboot.
10char
evilkorn said:
fastboot.
10char
Click to expand...
Click to collapse
For the life of me, I cannot seem to get fastboot to work for me on my mac. Maybe it is just me and I am unable to follow directions, but for some reason I cannot get it to work under Mac OS10.5 and I have no Window PC to try it out there.
You could try everything from adb shell. I don't know why fastboot wouldn't work if adb is working as they go hand-in-hand. I don't have the shell commands to flash, but I'm sure they are around here somewhere.
http://developer.htc.com/google-io-device.html
They have the fastboot binary if you wanted to try that instead what you have.
evilkorn said:
You could try everything from adb shell. I don't know why fastboot wouldn't work if adb is working as they go hand-in-hand. I don't have the shell commands to flash, but I'm sure they are around here somewhere.
Click to expand...
Click to collapse
Decided to remove and reinstall adb again. For some reason now, fastboot does work even though I did the exact same things as before.
Thanks for the help evilkorn
Less than an hour after you posted... I'd say it's a pretty fast solution. =p
As stated, got flashboot to work, I now have another problem. When I try to install the rom using flashboot, I get this error;
Dell:tools szuba$ fastboot update jacheroski2.2a.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Dell:tools szuba$
Any way around this?
New solution. Flash amon ra's 1.2.2 recovery, that version had verify with send, instead of home. The link in my sig has the download for the current and past version.
dude you can still boot into recovery. go into terminal emultaor and type su then reboot recovery
pistol4413 said:
dude you can still boot into recovery. go into terminal emultaor and type su then reboot recovery
Click to expand...
Click to collapse
Read his first post... The problem is the home key to OK the flash.
szuba said:
Well, the home button on my unlocked G1 stopped working about a week or so ago. No big deal, but the problem I now face is that I am unable to install any new roms.
I am able to boot into recovery mode (cyanogen v1.4) using ADB, however once there, I am unable to install a new rom since my home button does not work.
Is there any way around this either using the phone or through my computer (I am using MAC OS 10.5). Any help would be GREATLY appreciated.
- Thomas
Click to expand...
Click to collapse
One of Amon's recovery versions using the green "call" button to confirm actions (rather than the home button).
Must be my luck... installed Amon's previous recovery img but now my green (send/call) button doesn't seem to be working either.
For some reason, both my green (send/call) and home buttons do not work so both methods do not work for me. The only option that I can think of is to someone create a boot.img, data.img, and system.img from a rom and do a fastboot nandroid backup from those. Now if only I can find away to do that... anyother ideas?
And thanks for the help so far
Do the alt+ commands ask you to verify the update with home?
evilkorn said:
Do the alt+ commands ask you to verify the update with home?
Click to expand...
Click to collapse
Yes, the alt+ commands still requires you to verify with the home (or green) key.
Any chance there is away to do it through the console with code? Tried to do a search, but didn't come up with anything in regards to that.
Totally lost for ideas now... but the help is greatly appreciated evilkorn
--update_package=SDCARD:update.zip" > /cache/recovery/command
Try that
B-man007 said:
--update_package=SDCARD:update.zip" > /cache/recovery/command
Try that
Click to expand...
Click to collapse
Where exactly do I try that?
When I enter;
--update_package=SDCARD:update.zip" > /cache/recovery/command
in the recovery console, nothing happens, just goes to the next line.
So, my captivate is bricked.. but I'm in the mood to try and fix it. So, I was wondering if it is possible to flash 3buttonfix.zip(I renamed to update.zip) using adb. I pushed update.zip to the sd card using adb but I cant reboot into recovery to apply it and I got to thinking that I might be able to flash the update.zip file using adb.. does anyone know how to do it? if so please share.
How is your phone bricked if you can get into it with adb? And, what's preventing you from issuing 'adb reboot recovery' or 'adb reboot download' to fix it?
modest_mandroid said:
How is your phone bricked if you can get into it with adb? And, what's preventing you from issuing 'adb reboot recovery' or 'adb reboot download' to fix it?
Click to expand...
Click to collapse
I can get into adb believe it or not.. I tried flashing CM7 and completely missed the 3 button combo part. Now I have a captivate that is stuck at cyanogenmod screen. I have been trying both recovery and download, all it does is reboots the phone. thats why I wanted to flash update.zip(3buttonfix.zip) and it might fix it. everytime I turn it on and try to get into recovery it just skips it.. I have tried download mode and recovery several, and I mean several times. I bought a jig to put it into DL mode, just gotta wait for the Jig to get here. That's why I have been trying to fix it because I have no backup phone to use.
Try this.
Find the modified recovery file in this forum, push it to /system/bin, check execute permissions, and try 'adb reboot recovery' then.
What files are in the 3button fix.zip? Push them manually with adb also.
another one bites the dust...
Let us know how did it go.
can we have a big sticky:
if you can see things on your screen, it's not bricked. use the search.
ibrutalfatei said:
So, my captivate is bricked.. but I'm in the mood to try and fix it. So, I was wondering if it is possible to flash 3buttonfix.zip(I renamed to update.zip) using adb. I pushed update.zip to the sd card using adb but I cant reboot into recovery to apply it and I got to thinking that I might be able to flash the update.zip file using adb.. does anyone know how to do it? if so please share.
Click to expand...
Click to collapse
Did you try adb reboot recovery command? You don't need 3 button fix if you can connect adb.
gibson3659 said:
Try this.
Find the modified recovery file in this forum, push it to /system/bin, check execute permissions, and try 'adb reboot recovery' then.
What files are in the 3button fix.zip? Push them manually with adb also.
Click to expand...
Click to collapse
Can you explain how to do that? I'm not very good with ADB
foxbat121 said:
Did you try adb reboot recovery command? You don't need 3 button fix if you can connect adb.
Click to expand...
Click to collapse
I have tried that multiple times. I can connect ADB, when I enter "adb reboot recovery" the phone just restarts and goes to the Galaxy S Cyanogenmod Screen.
ibrutalfatei said:
I have tried that multiple times. I can connect ADB, when I enter "adb reboot recovery" the phone just restarts and goes to the Galaxy S Cyanogenmod Screen.
Click to expand...
Click to collapse
Sounds like your recovery mode has been screwed by whatever ROM you have used. Your problem is no long 3e recovery fix. That no longer exists.
You need to get into download mode instead and use OneClick ODIN to flash back to stock.
foxbat121 said:
Sounds like your recovery mode has been screwed by whatever ROM you have used. Your problem is no long 3e recovery fix. That no longer exists.
You need to get into download mode instead and use OneClick ODIN to flash back to stock.
Click to expand...
Click to collapse
I can't get into Download mode either.
ibrutalfatei said:
I can't get into Download mode either.
Click to expand...
Click to collapse
Have to ask, did you try the manual method to get into download?
Open Odin
Verify not connected to usb
Pull battery
Insert battery
While holding both up and down volume button, insert usb
BTW, many people have and will continue to say, you should always verify you can access download and recovery before attempting to apply any ROM.
If you still can't get into download mode using above method, it's time for you to make a jig that will force the phone into download mode. Search for the thread here about how to make such hardware jig.
xcaliburinhand said:
Have to ask, did you try the manual method to get into download?
Open Odin
Verify not connected to usb
Pull battery
Insert battery
While holding both up and down volume button, insert usb
BTW, many people have and will continue to say, you should always verify you can access download and recovery before attempting to apply any ROM.
Click to expand...
Click to collapse
Yeah, It was ridiculous of me not to. Oh well, we all make mistakes.
I tried that also and I still can't get into download mode. I really wanted to get into recovery so I could install the initial package for CM7, then apply the 3buttonfix.zip
ibrutalfatei said:
Can you explain how to do that? I'm not very good with ADB
Click to expand...
Click to collapse
adb push \source\file /target/dir/on/device
I have know idea if this will get you anywhere, but it may be worth a try until your jig arrives.
Get a jig.
Sent from my Captivate using XDA Premium App
I couldn't wait any longer.. went up to Radioshack, ask for a pack of 100K resistors. Now I have fixed my phone and I have Cyanogenmod 7 Running on it. One question, it says "Emergency Calls Only" anyway to fix that?
ibrutalfatei said:
I couldn't wait any longer.. went up to Radioshack, ask for a pack of 100K resistors. Now I have fixed my phone and I have Cyanogenmod 7 Running on it. One question, it says "Emergency Calls Only" anyway to fix that?
Click to expand...
Click to collapse
IIRC, that's the known issue on CM7. You need perform something on the phone everytime you reboot the phone. It pays to read them before you flash
How can't anybody give a simply adb command to flash an update.zip into a broke device???
Instead of that all of you are trying to make the user do thing alternatively!
There is command (adb or fastboot) for that or not?
ibrutalfatei said:
I couldn't wait any longer.. went up to Radioshack, ask for a pack of 100K resistors. Now I have fixed my phone and I have Cyanogenmod 7 Running on it. One question, it says "Emergency Calls Only" anyway to fix that?
Click to expand...
Click to collapse
No - ill give you 50$ for your bricked phone.
Sent from my SAMSUNG-SGH-I896 using XDA App
Hey everyone, so tonight I got the 4.4 ota on my N7, I am unlocked and rooted but stock everything including recovery.
After updating, my N7 keeps going to stalk recovery and that's it.
I know I can just reflash everything but I have a few very important files. Is there a way to reflash 4.3 without losing data or accessing the data partition while soft bricked so I can recovery my files?
I may be wrong, but can't you reflash your phone as long as you don't replace the userdata.img through fastboot to retain the same information? I could be wrong.
chrisinsocalif said:
I may be wrong, but can't you reflash your phone as long as you don't replace the userdata.img through fastboot to retain the same information? I could be wrong.
Click to expand...
Click to collapse
I'm not sure. I'd like to have this confirmed before I do anything. It's not urgent as the due date on my prgect isn't for another couple of weeks. But thanks. I'll look at that as a last resort.
Is it one file or multiple files you are trying to access? Have you tried to pull them using adb to your pc? I do not know how to do it, but I am sure there is a guide somewhere. Or try a phone backup using fastboot then unpack it on your desktop and get the files you need. Again, I am not good with phones, just throwing out idea's.
chrisinsocalif said:
Is it one file or multiple files you are trying to access? Have you tried to pull them using adb to your pc? I do not know how to do it, but I am sure there is a guide somewhere. Or try a phone backup using fastboot then unpack it on your desktop and get the files you need. Again, I am not good with phones, just throwing out idea's.
Click to expand...
Click to collapse
ADB or Wugs root kit don't see my Nexus 7 as it keeps rebooting to the dead droid and I know I don't have it set for debugging. Guess I'm screwed.
When you say "dead droid", you're referring to fastboot mode, right? (Android icon with a bunch of text below it, starting with "Fastboot Mode" in red.)
If you have fastboot, you can flash TWRP Recovery 2.6.3.0. Download it from Team Win's site (Google it). Then:
fastboot flash recovery openrecovery-twrp-2.6.3.0-grouper.img
fastboot reboot-bootloader
Use the Volume keys to select "Recovery Mode" and hit Power. Once you see the TWRP menu, you should have adb root access automatically. Connect tablet to USB, and use adb pull to download the contents of /sdcard:
adb pull /sdcard /dumphere
Replace "dumphere" with whatever directory you want to dump to. I'm sure there's better guides and explanations for this, but this is the quick version.
I guess you could reflash stock recovery afterwards, but I can't think of a reason why you'd want to. It's not like it's that useful.
As a rule of thumb, you should at least know how to get around a command line, and use adb and fastboot before mucking around with your tablet.
-XCN-
P.S. I could be mistaken, but I don't think internal storage (which is /sdcard, or /data/media) is overwritten when you flash a ROM. Obviously, backup first before trying.
Hey xda devs,
I just f ed up very bad. I was trying to flash a new recovery onto my Moto X and I was careless typing commands into the terminal I guess that serves me right.... So I was just rebooting my phone into the bootloader by typing adb reboot bootloader, so I had the "bootloader" sticking in my head there and because I did it a thousand times already I just proceed to flashing the new recovery but I type "fastboot flash bootloader xxxx.img"
So now, I have basically flashed a recovery.img into my bootloader partition
I still have adb and root access though.. is there any way I could save my bootloader partition? like adb dd it maybe ? I dont know
Did you try to manually reflash the correct image file? Or sbf back to stock?
Travisdroidx2 said:
Did you try to manually reflash the correct image file? Or sbf back to stock?
Click to expand...
Click to collapse
I'm not in fastboot anymore, I guess that's what I should have done when I realized my mistake. Because I was well aware of what I had just done.. but I rebooted the phone and now I guess there is no way to enter fastboot anymore.
Without fastboot how can I flash the correct img. file into the bootloader partition?
And what do you mean with sbf back to stock?
yabbandroid said:
I'm not in fastboot anymore, I guess that's what I should have done when I realized my mistake. Because I was well aware of what I had just done.. but I rebooted the phone and now I guess there is no way to enter fastboot anymore.
Without fastboot how can I flash the correct img. file into the bootloader partition?
And what do you mean with sbf back to stock?
Click to expand...
Click to collapse
Ever use RSD to flash a SBF? RSD will need to recognize your device though. There is stickies I am sure. I will find one to link you to.
Hold the power button until the phone is off. Now press and hold both the power button and volume down button for 10 seconds. Then release the power button, but keep the volume down button held. You should then be in fastboot mode.
AGISCI said:
Hold the power button until the phone is off. Now press and hold both the power button and volume down button for 10 seconds. Then release the power button, but keep the volume down button held. You should then be in fastboot mode.
Click to expand...
Click to collapse
The problem is that his bootloader (The mode that you have to get into to use fastboot) is no more. If you could find the block number you could do a dd command.
Vekhez said:
The problem is that his bootloader (The mode that you have to get into to use fastboot) is no more. If you could find the block number you could do a dd command.
Click to expand...
Click to collapse
Yep, good suggestion. It will only work if he has busybox installed (the 'stericson' variant, from the play store).
This command should work (from and ADB SHELL) assuming busybox is installed. First motoboot.img would need to be copied to the working directory on the sdcard where you are running the command from. Might need to be superuser as well.
dd if=motoboot.img of=/dev/block/platform/msm_sdcc.1/by-name/bootloader
Let me know if you have success. After running the command, if it shows success, you should be able to power off and successfully boot into bootloader (AP fastboot mode).
samwathegreat said:
Yep, good suggestion. It will only work if he has busybox installed (the 'stericson' variant, from the play store).
This command should work (from and ADB SHELL) assuming busybox is installed. First motoboot.img would need to be copied to the working directory on the sdcard where you are running the command from. Might need to be superuser as well.
dd if=motoboot.img of=/dev/block/platform/msm_sdcc.1/by-name/bootloader
Let me know if you have success. After running the command, if it shows success, you should be able to power off and successfully boot into bootloader (AP fastboot mode).
Click to expand...
Click to collapse
You're my hero, Sam. I'm gonna try that. I thought about dd but I don't understand this command so well ^^. Thank you for writing it down. I have root access so I can install busybox. I will try :good::good:
edit: did it as root! I think you just saved my phone! A thousand thanks to you, because I love my moto x !!
.img of=/dev/block/platform/msm_sdcc.1/by <
by-name/ by-num/
/block/platform/msm_sdcc.1/by-name/bootloader <
3209+0 records in
3209+0 records out
1643008 bytes transferred in 0.086 secs (19104744 bytes/sec)
Click to expand...
Click to collapse
succcess, success, after that I could succesfully reboot into fastboot. Only my recovery seems to be lost, but I will try to reflash this one now using fastboot which is back and working !!! (will be more careful in the future)
SO HAPPY. THank you !
yabbandroid said:
SO HAPPY. THank you !
Click to expand...
Click to collapse
Fantastic, bud!!! Yep, dd can come in very handy sometimes, and it's good to know some native linux commands (they save our butts every now and then...)
Very glad to hear my method worked for you. :good:
my xt 1032 moto g is not working. it stays on unlocked bootloader warning. worked great after rooting it, but I think I erased everything off it. I cannot do any factory resets, nor can i manage to push a rom to it. I can access it using adb, but I always end up with some kind of error, likely on my noob behalf.
Can someone please help me with this, I tried to push a rom but it said stat cannot access file, or something like that. I think i need help most with the correct steps on doing this, already unlocked bootloader and rooted. adb only recognizes my device when in recovery mode.
Keep pressing volume down + power until your phone turns off and then quickly repeat. Now you should be in fastboot mode. Find your stock firmware and flash it.
xGiorgos said:
Keep pressing volume down + power until your phone turns off and then quickly repeat. Now you should be in fastboot mode. Find your stock firmware and flash it.
Click to expand...
Click to collapse
Thanks but thats not the problem. I need to know the proper words to put in the adb command window, and figure out why it wont push to the sdcard
lee7611 said:
Thanks but thats not the problem. I need to know the proper words to put in the adb command window, and figure out why it wont push to the sdcard
Click to expand...
Click to collapse
Ok you say XT1032 ??? thats Moto G original not the 2nd Generation that this forum is
GO HERE http://forum.xda-developers.com/moto-g