Related
ok i have no idea what happened. my nandroid backup used to work just fine. but now it doesnt work anymore. i dont know why. all i does is make a backup that will take upwhatever space is left on my sdcard, and keep those dots going an going and going. they dont stop unless i stop it. i hadnt installed anything new like a rom since the last backup i did, so i dont know whats wrong. i also cant make those normal backups. like when you use backup for root users. that just gives me the same thing. i dont know what to do and i dont wanna wipe or really do anything, because i DONT have any backups! please help
Try re flashing cyan's recovery
tried that already. i tried that, tried taking out the battery, tried waiting. one thing i did was i took out my card and put in another one. still didnt work. but when i put my other card back in it worked. now the problem is when i boot my phone all my apps keep force closing. im guessing it might have something to do with the fact that the other card i had put in wasnt partitioned for app2sd. and i let the phone boot with it. now i have a nandroid backup, but my apps keep force closing. someone suggested i should wipe. which i did. but now i dont know if i should just reboot the phone or if i restore the backup now will it bring my settings back after the wipe?
flash ur back up. reboot if u stil get fc. fix the permissions in the recovery terminal. if that fails wipe the g1 and sd repartition it and tart over from there.
tried what you said and its still force closing. i cant access anything really because i had a home alternative, so it keeps saying open home is force closing. so im thinking if i have to fix permissions i have to do it in recovery? but i dont know how =/
yes go into the the console in recovery and just type
Code:
fix_permissions
wait a bit and when its done type reboot
it didnt work.
So, this didn't happen until the other day, but suddenly, my Power/End, Call, Menu, Home and Back buttons aren't working on my G1. The only way I could get the phone to power up was to plug it into a USB, and then place the battery in to force a boot. I can't reset anything, leave screens, accept calls, or do anything really because of this issue, and it's debilitating.
Before you tell me to search, I'll tell you that I've already searched multiple times. I know the rules of the forums, and I wouldn't have created a new thread if the issue had already been solved by a previous thread. However, if I missed a thread that could help, rather than saying "SEARCH FOR CHRIST'S SAKE", I'd appreciate a link.
Thanks, guys. XDA has always been useful to me, and I really just want a solution, since the G1 has been the best phone I've ever had.
If it matters, I'm using Cyanogen 4.1.11.1, with the 2.6.29.6-cm41 kernel. I'd upgrade, but I can't, since my home button isn't working.
Try wiping, enter terminal or use adb shell "reboot recovery" to enter the reboot screen. Once you have wiped or reflashed, use "reboot"
I can't wipe or flash, because I need the home button.
I know, to enter recovery without using the home button user adb shell reboot recovery
Yes, but how do I wipe from there? When I select wipe, it asks me to press the home button.
Oh my you really seem to have dug yourself into a hole here... not good. Hmm. Try wiping from the Settings on your phone, there is a factory reset on there.
"No reset was performed because the System Clear service was not available."
Is there a way to wipe from the console, or adb shell?
electrolemon said:
"No reset was performed because the System Clear service was not available."
Is there a way to wipe from the console, or adb shell?
Click to expand...
Click to collapse
Now thats a right proper one mate..anyway how do you tuen her on if the button doesnt work?
You can use fastboot to clear your data partition (userdata). But this doesn't sound like a software issue if the buttons aren't even working within recovery/bootloader, it sounds more like a hardware issue. I would take it up with T-Mobile or HTC.
I was able to turn it on by plugging in the battery while it was plugged in via USB, but now that doesn't even work. I have a feeling that I just wiped the entire system, as I can only access the fastboot, and when I try to boot normally, I just get stuck at the white G1 screen. So it seems I have two issues now. Any solutions for either? Unfortunately, my G1 is 5 days out of warranty, too.
If you can access fastboot, then you can flash RC29 and start from the beginning again or you can flash a nandroid backup that you can get from your sdcard to your PC.
Any idea how to flash a nandroid backup or downgrade to RC29 if I don't have working power, home, menu, or call buttons? Like, is there a guide?
Nobody has any solution that doesn't require me to get a replacement phone? I'm willing to pay for a solution. I'm in dire need of this phone. I hate the Blackberry Curve so much.
electrolemon said:
Nobody has any solution that doesn't require me to get a replacement phone? I'm willing to pay for a solution. I'm in dire need of this phone. I hate the Blackberry Curve so much.
Click to expand...
Click to collapse
I think your phone is pretty shot. Even if you do manage to get into a ROM, it seems unlikely that your buttons will come back to life. Without being able to use the home or back buttons, you'll be stuck in whatever application you opened until you restart your phone.
If you want to try it out, you can flash an old nandroid backup by first, copying system.img, data.img, and boot.img from the nandroid folder and pasting it in the same folder as your fastboot. Then, boot into the bootloader and type:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata data.img
fastboot reboot
which will restore the nandroid backup.
SOLUTION
I found a fix for this problem on another Android forum, essentially you install "Anycut" from the markey and create a shortcut to the "setup wizard", I had a three setup wizards, the third one worked for me and ran all the way through the phone setup, the others just exited as soon as I selected SKIP. It works, prior to that my HOME, MENU and CALL buttons were not working. I think that a faulty update.zip must have caused permission issues with the software, I had installed some new fonts and straight after I lost the buttons!
http://androidforums.com/updates-cupcakes/4884-can-fixed.html
OK so I tried to use ADB to push an modded Launcher2.apk. For some reason (even though I copied and pasted the commands into the prompt) the launcher force closes over and over. I cannot do anything on the device. Tried a hard-reset but it survives, again force closes over and over.
How can I go back to COMPLETELY STOCK without being able to access the device?
EDIT: FIXED! Thanks grainysand for giving instructions. I'll also take this opportunity to flip the e-bird to the folks who snidely responded with things that not only didn't help, but just makes XDA that much less accessible. I hope those folks got a huge boner off of it. But again, thanks to those who did help.
Plug it into your PC and try rebooting into recovery via ADB commands?
No idea how. If you know what commands to use that'd be greatly appriciated!
adb reboot recovery
Just replace the file you just pushed with it's original, providing you still have it. If you don't find it, and then push it back over the top. It will still mount as adb, if you don't have debugging on persist through the popups and turn it on, adb push.
MatMew said:
Just replace the file you just pushed with it's original, providing you still have it. If you don't find it, and then push it back over the top. It will still mount as adb, if you don't have debugging on persist through the popups and turn it on, adb push.
Click to expand...
Click to collapse
I do have it, and I tried this, it didn't work. I cannot get to the device whatsoever, the launcher will not run, it repeatedly force closes. Tried pushing it back via ADB, the prompt says it copied correctly, but on reboot, same thing. I'm going to need to flash, just don't know how.
Just restore the Nand backup you made before trying to push the modded launcher over.
uansari1 said:
Just restore the Nand backup you made before trying to push the modded launcher over.
Click to expand...
Click to collapse
I didn't make one, which yeah, I know I should had; but I was in a hurry and I thought pushing the backup file back over would be fine if it messed up. But now that I can't get that done, not sure what else to do.
level5music said:
I didn't make one, which yeah, I know I should had; but I was in a hurry and I thought pushing the backup file back over would be fine if it messed up. But now that I can't get that done, not sure what else to do.
Click to expand...
Click to collapse
Return it to Google and buy a prepaid candybar phone that is not a smartphone.
By no means is your phone bricked, or even close to it. Do as we've suggested, there are tons of options that aren't listed here. Wipe, flash, etc. As I stated, push a launcher that won't clash with your system.
ScottC said:
Return it to Google and buy a prepaid candybar phone that is not a smartphone.
Click to expand...
Click to collapse
Look how awesome you are! Dude, could we not have these kinds of posts? If you can't help, don't post.
level5music said:
I didn't make one, which yeah, I know I should had; but I was in a hurry and I thought pushing the backup file back over would be fine if it messed up. But now that I can't get that done, not sure what else to do.
Click to expand...
Click to collapse
I already knew that... but thought someone should make the point. You should be able to fix this issue relatively easily by booting into recovery and flashing a custom ROM again. It should overwrite launcher2.apk, if I'm not mistaken.
uansari1 said:
I already knew that... but thought someone should make the point. You should be able to fix this issue relatively easily by booting into recovery and flashing a custom ROM again. It should overwrite launcher2.apk, if I'm not mistaken.
Click to expand...
Click to collapse
I'm not sure how to do this.. only ADB? I'm fairly new to Android, it's not like booting WinMo devices to bootloader and running an exe of course. I'm really dumb at ADB at the moment, so commands would really help me out. I do appreciate the help though guys!
We already told you to boot into recovery and go from there. Did it not work or something?
I'm not rooted, but IIRC, turning off the phone, then restarting it while holding the volume down button will give you the option to boot into recovery, no? So all you have to do is copy the ROM that you originally flashed to the phone onto the root of your SD card, go into Recovery (I'm assuming you're running Amon_RA's Recovery, which is an excellent product), and flash the zip file.
If what I wrote sounds confusing or you don't understand it, then you were premature in rooting your phone and messing around with files therein, and you need to do some researching and reading on this site (including the G1 forum) for all the info regarding these processes.
Anyway, don't freak out... your phone will be fine. I'm going back to bed...but I'm sure someone can give you a step by step to what I said if need be (hopefully you know how do to this though)...
grainysand said:
We already told you to boot into recovery and go from there. Did it not work or something?
Click to expand...
Click to collapse
What does the filename have to be? What if I only have the regular recovery? I tried the file unzipped and recovery just sat there.
Ok I kept Googling and trying stuff. I got a stock rom from MDC and tried to flash it in stock recovery (I dont think it was amon-ra's, no real way to tell that I could see).. tried to flash the stock rom and it says Verification Failed. Ugh.. does anyone have step by step instructions? I'm really failing here.
You can tell it's Amon_RA's. It's got a... well, depending on which version you got it'll either have the Nexus logo or a green or pink Carebear.
Anyway.
Download the Amon_RA recovery if you haven't already. Flash it (fastboot flash recovery filename.img).
Type:
adb reboot recovery
You should now be in Amon_RA's recovery. Select wipe and wipe everything. Then select "Flash from SD card" and flash whichever ROM you downloaded.
I'm definitely kind of a noob to all of this stuff but I think I've really messed up at this point and could use some help as I've exhausted pretty much everything I can think of. I have a Sprint HTC One. I decided to root my phone yesterday, after rooting it and installing a kernal I wasn't liking the way things were going (Just some things on the phone weren't working right so I decided to wipe it and re-do it all hoping to get better results. Spending quite a while messing around with it, running on no sleep and multitasking I effectively formatted the phone removing OS and everything, so at that point was sitting at the boot menu obviously. So I downloaded the RUU pack from here hoping to just run that and going back to factory, doing that came to realize I had 1.31.651.2 which doesn't appear to have a working RUU at the moment. I really don't have much experience with any of this or much of an idea what I'm doing aside from following the Tutorials you guys have posted. So I thought maybe I would try to flash the 1.31.651.2 ROM posted here by "Indirect" using the fastboot in CMD. Doing that (With an unlocked bootlocker and custom recovery) am getting a problem with writing the Zip with this message- FAILED (Remote: Not Allowed), which after searching I can't find much about how to resolve that. So my next thought was to try to use the all in one toolkit to sideboot the same ROM and was just getting an error when doing that.
So at this point I'm really at a loss and would really like some help from you guys who seem to know a whole lot more than I do
I don't care whether it's rooted, bone stock or anything else I just want the phone to work again and can't figure out what to do and I'm sure I'm just doing something stupid but hoping you guys can shed some light on it for me!
Maxy1292 said:
I'm definitely kind of a noob to all of this stuff but I think I've really messed up at this point and could use some help as I've exhausted pretty much everything I can think of. I have a Sprint HTC One. I decided to root my phone yesterday, after rooting it and installing a kernal I wasn't liking the way things were going (Just some things on the phone weren't working right so I decided to wipe it and re-do it all hoping to get better results. Spending quite a while messing around with it, running on no sleep and multitasking I effectively formatted the phone removing OS and everything, so at that point was sitting at the boot menu obviously. So I downloaded the RUU pack from here hoping to just run that and going back to factory, doing that came to realize I had 1.31.651.2 which doesn't appear to have a working RUU at the moment. I really don't have much experience with any of this or much of an idea what I'm doing aside from following the Tutorials you guys have posted. So I thought maybe I would try to flash the 1.31.651.2 ROM posted here by "Indirect" using the fastboot in CMD. Doing that (With an unlocked bootlocker and custom recovery) am getting a problem with writing the Zip with this message- FAILED (Remote: Not Allowed), which after searching I can't find much about how to resolve that. So my next thought was to try to use the all in one toolkit to sideboot the same ROM and was just getting an error when doing that.
So at this point I'm really at a loss and would really like some help from you guys who seem to know a whole lot more than I do
I don't care whether it's rooted, bone stock or anything else I just want the phone to work again and can't figure out what to do and I'm sure I'm just doing something stupid but hoping you guys can shed some light on it for me!
Click to expand...
Click to collapse
go into recovery and sideload install a rom
flex360 said:
go into recovery and sideload install a rom
Click to expand...
Click to collapse
When I go into TWRP and try to ADB sideload I go through trying to do that and it fails immediately
E: Unable to moundt "/data"
/cache
/data
internal storage
/data/media during gui startup
/cache
E:TW Func: :copy_log -- Can't open destination lo
E: Unable to mount '/cache'
/data/media/twrp/,twrps when
/data
/data
I'm not sure if I'm doing something wrong with it or if this means something I don't know much about
Maxy1292 said:
I'm definitely kind of a noob to all of this stuff but I think I've really messed up at this point and could use some help as I've exhausted pretty much everything I can think of. I have a Sprint HTC One. I decided to root my phone yesterday, after rooting it and installing a kernal I wasn't liking the way things were going (Just some things on the phone weren't working right so I decided to wipe it and re-do it all hoping to get better results. Spending quite a while messing around with it, running on no sleep and multitasking I effectively formatted the phone removing OS and everything, so at that point was sitting at the boot menu obviously. So I downloaded the RUU pack from here hoping to just run that and going back to factory, doing that came to realize I had 1.31.651.2 which doesn't appear to have a working RUU at the moment. I really don't have much experience with any of this or much of an idea what I'm doing aside from following the Tutorials you guys have posted. So I thought maybe I would try to flash the 1.31.651.2 ROM posted here by "Indirect" using the fastboot in CMD. Doing that (With an unlocked bootlocker and custom recovery) am getting a problem with writing the Zip with this message- FAILED (Remote: Not Allowed), which after searching I can't find much about how to resolve that. So my next thought was to try to use the all in one toolkit to sideboot the same ROM and was just getting an error when doing that.
So at this point I'm really at a loss and would really like some help from you guys who seem to know a whole lot more than I do
I don't care whether it's rooted, bone stock or anything else I just want the phone to work again and can't figure out what to do and I'm sure I'm just doing something stupid but hoping you guys can shed some light on it for me!
Click to expand...
Click to collapse
If your unlocked and you have a custom recovery its not a big deal bro. Its alright you can calm down . So first go download any rom like a stock rom ok? once you have one like OMJ's or even indirects take the zip and rename it to lets say stock. Then if you have adb (should be in fastboot folder) add that zip to that folder. Next boot into your recovery either through bootloader or through fastboot command. If your stuck on splash screen just hold power and volume down button until led's start flashing and the phone turns off let go for a sec and hold the power and volume down buttons again until you get into bootloader. Once your in recovery plug your phone into your computer and in twrp or even cwm recovery you should have the option adb sideload. Tap it and start that. Once thats running open cmd (command prompt) and type adb sideload stock.zip seeing as you renamed the stock rom to exactly how I spelled it, no differently. Then it should show you that it is loading in the command prompt once it is done loading it should start flashing and then your good to go. Wow i typed a lot lol.
Edit: wow totally didnt see the two posts above. OK see if what i sent you works. may wanna try reflashing your recovery in fastboot usb mode with fastboot flash recovery twrp.img
HTC_M7 said:
If your unlocked and you have a custom recovery its not a big deal bro. Its alright you can calm down . So first go download any rom like a stock rom ok? once you have one like OMJ's or even indirects take the zip and rename it to lets say stock. Then if you have adb (should be in fastboot folder) add that zip to that folder. Next boot into your recovery either through bootloader or through fastboot command. If your stuck on splash screen just hold power and volume down button until led's start flashing and the phone turns off let go for a sec and hold the power and volume down buttons again until you get into bootloader. Once your in recovery plug your phone into your computer and in twrp or even cwm recovery you should have the option adb sideload. Tap it and start that. Once thats running open cmd (command prompt) and type adb sideload stock.zip seeing as you renamed the stock rom to exactly how I spelled it, no differently. Then it should show you that it is loading in the command prompt once it is done loading it should start flashing and then your good to go. Wow i typed a lot lol.
Edit: wow totally didnt see the two posts above. OK see if what i sent you works. may wanna try reflashing your recovery in fastboot usb mode with fastboot flash recovery twrp.img
Click to expand...
Click to collapse
Thanks for the help, When I typed the command in to the CMD, I got
"Adb server is out of data. killing...
*Daemon started successfully*
error: closed
I've reflashed the recovery like you suggested and still am unable to get much to change, does it have anything to do with anytime I do anything it says it's unable to mount or is that normal?
Sorry if I'm asking stupid questions but this is only the second phone I've rooted and haven't ran into a problem like this before
Also has anyone heard anything about a 1.31.651.2 RUU?
May have found a work around, after formatting again and running through a bunch of reboots and attempts to mount the partitions and everything I think I finally got it mounted. Am flashing a ROM to the phone now so here's hoping!!! :fingers-crossed:
And I'm up and going phew. Thanks for all the help guys. If anyone runs into this problem definitely Format the device again, once you do that it should start to mount
Maxy1292 said:
And I'm up and going phew. Thanks for all the help guys. If anyone runs into this problem definitely Format the device again, once you do that it should start to mount
Click to expand...
Click to collapse
What do you mean format it? How? From where?
axtn95 said:
What do you mean format it? How? From where?
Click to expand...
Click to collapse
From TWRK, under the wipe menu, had to Format it again (Which is what originally caused the problem to begin with ironically). I had to Format it to get the data and whatnot to mount. Once I did that I was able to flash a ROM and was back up and going
Maxy1292 said:
From TWRK, under the wipe menu, had to Format it again (Which is what originally caused the problem to begin with ironically). I had to Format it to get the data and whatnot to mount. Once I did that I was able to flash a ROM and was back up and going
Click to expand...
Click to collapse
Thanks for the reply, so just making sure, you went into advanced wipe and checked cahce?
Edit: oops i saw format data lol
axtn95 said:
Thanks for the reply, so just making sure, you went into advanced wipe and checked cahce?
Click to expand...
Click to collapse
Not quite. When I loaded up TWRK and go into Wipe there's 3 buttons, the slide button for "Factory reset" there's the Advanced Reset button and the 3rd button says "Format". Format wipes literally everything except the custom recovery off the phone. Which is the mistake I made last night (Bonehead move but I was running on zero sleep lol)
Hi a friend of mine has a Nexus 6 but for some reason it wont get past the google screen, it would just turn off again, and if it is plugged it will just go to the Battery Icon and then off again.
He has tried everything, even flashall.bat to add new stock rom, tried pushing TWRP recovery etc, etc.
Is there a way he can extract EFS folder to see if by any chance that or something else is corrupt?
Thanks! I know XDA Peeps have helped me a lot before and I tried almost everything with him with no avail
He wants to extract the EFS, just in case trying to flash more things or something might break it, he just wants to have a backup just in case.
ZeroHart said:
Hi a friend of mine has a Nexus 6 but for some reason it wont get past the google screen, it would just turn off again, and if it is plugged it will just go to the Battery Icon and then off again.
He has tried everything, even flashall.bat to add new stock rom, tried pushing TWRP recovery etc, etc.
Is there a way he can extract EFS folder to see if by any chance that or something else is corrupt?
Thanks! I know XDA Peeps have helped me a lot before and I tried almost everything with him with no avail
He wants to extract the EFS, just in case trying to flash more things or something might break it, he just wants to have a backup just in case.
Click to expand...
Click to collapse
If he can go into bootloader mode he can flash the stock rom manualy, look here http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008, method 2.
ZeroHart said:
Hi a friend of mine has a Nexus 6 but for some reason it wont get past the google screen, it would just turn off again, and if it is plugged it will just go to the Battery Icon and then off again.
He has tried everything, even flashall.bat to add new stock rom, tried pushing TWRP recovery etc, etc.
Is there a way he can extract EFS folder to see if by any chance that or something else is corrupt?
Thanks! I know XDA Peeps have helped me a lot before and I tried almost everything with him with no avail
He wants to extract the EFS, just in case trying to flash more things or something might break it, he just wants to have a backup just in case.
Click to expand...
Click to collapse
Since you want to backup the efs here is my best advice:
Normally you can backup the efs via custom recovery(thats out) or through adb. I don't know the details of adb, nor how one might backup efs in fastboot. I looked through the files in roots I believe the efs partitions are in /dev/block/platform/msm_sdcc.1/by-name/ and the files are probably mdm1m9kefs1 mdm1m9kefs2 mdm1m9kefs3 and mdm1m9kefsc Now this is my best guess and I'm not sure if you can just copy them in adb to save on your comp or wherever, and well you would need to look up some adb commands... But that's all I can say.
What you can do in fastboot is really limited. adb via custom recovery would be the only way really.
I haven't seen any instances of this phone with a corrupted efs yet
Too bad, he tried flashing stock but did not work, not by doing flash all nor by doing one by one, also tried flashing recovery, but when he selects fastboot boot recovery the phone will just turn off again.
He says he is tied and will send it back to t mobile, hopefully they fix it or send him a new one
ZeroHart said:
Too bad, he tried flashing stock but did not work, not by doing flash all nor by doing one by one, also tried flashing recovery, but when he selects fastboot boot recovery the phone will just turn off again.
He says he is tied and will send it back to t mobile, hopefully they fix it or send him a new one
Click to expand...
Click to collapse
Did they flash o.k.?. But won't boot to os. Because I have similar issues. I had it working o.k. was on bliss rom. Then when I woke up phone was on Google logo and won't go any further. I tried flashing the images. They flash only manually. But won't let me go to recovery or the os. Any advice what could went wrong with device.
Nochis said:
Did they flash o.k.?. But won't boot to os. Because I have similar issues. I had it working o.k. was on bliss rom. Then when I woke up phone was on Google logo and won't go any further. I tried flashing the images. They flash only manually. But won't let me go to recovery or the os. Any advice what could went wrong with device.
Click to expand...
Click to collapse
That is exactly what happened to him, everything flashes but it wont get to recovery or OS, if it is plugged it will just show the google screen then battery and that is it
ZeroHart said:
That is exactly what happened to him, everything flashes but it wont get to recovery or OS, if it is plugged it will just show the google screen then battery and that is it
Click to expand...
Click to collapse
What rom he was before this happen?.
Stock Rooted
ZeroHart said:
Stock Rooted
Click to expand...
Click to collapse
So it may be a hardware issue. My guess is something went wrong with the device.