Related
Every time i turn it on it goes right to the recovery screen, i cant even enter the bootloader screen. What the hell is going on? PLZ HELP
is your home button stuck and what about if you type reboot from the recovery console (alt+x)
Its not stuck and it doesnt do anything when i press alt x
can you scroll down to go to console with the track ball.
What happens when you try to restore or flash a new rom?
What recovery are you using?
yes i can scroll in the recovery screen.
when i flash a new rom it just goes to the recovery screen. the radio give me an error E: can't read MISC
Looks like somebody got an oppsies!!
Please tell us about youp phone a little bit more in depth so we can deduce the problem in a logicial fashion or at least better guesses
No matter what i do everytime i turn it on it heads to recovery mode. I even tried flashing the rom over and over again but it still wouldnt get to the desktop.
I cant even get to bootloader.
That is so not what I meant
What type of rom where you using?
What recovery do you have?
What spl?
What if any themes where you using?
What is your gf's breat size?
Did you throw your phone in a jealous fit of rage?
These are the important types of info that we need to know
Do you just call up a mechanic and tell him a problem and not even say what type of car it is and expect him to tell you an answer or will he ask for more info
I was using the Drizzy Full v0.2
I flashed the latest SPL
Well your phone is telling you that there is something it don't like on it, have you tried reflashing your spl yet or a nandriod backup, try flashing a different rom afterwords, maybe a wipe too while you are at it
I have tried everything u listed above
Have you tried running it over or throwing against the wall, how bout shooting it. There are commands that you would have to type in the console at this point but since my computer is fried with them on it, I can not provide you with them, hopefully someone with the commands will come along at post them
Anyone?????
Is there a way for me to completely reset the phone to make it seem i never had root? or like if i just bought it brand new? im not talking about the wipe in the recovery menu.. I need a different way... ]:
Story: I was switching roms & i by mistake pressed Wipe battery informations or something like that, (using Amon Ra 1.5.2 recovery) The phone got messed up & i put the Dreaimg.nbh in the boot thing, & reset the phone.. i dont have root anyymore but when i go into recovery (non-root recovery, just plain with the exclamation on top of a phone) it says on the bottom of it : "E:Can't open /cache/recovery/command"
I'm sure that is messing with everything, since it wont let me root my phone once more..
Jose_95 said:
Is there a way for me to completely reset the phone to make it seem i never had root? or like if i just bought it brand new? im not talking about the wipe in the recovery menu.. I need a different way... ]:
Story: I was switching roms & i by mistake pressed Wipe battery informations or something like that, (using Amon Ra 1.5.2 recovery) The phone got messed up & i put the Dreaimg.nbh in the boot thing, & reset the phone.. i dont have root anyymore but when i go into recovery (non-root recovery, just plain with the exclamation on top of a phone) it says on the bottom of it : "E:Can't open /cache/recovery/command"
I'm sure that is messing with everything, since it wont let me root my phone once more..
Click to expand...
Click to collapse
I'm assuming you don't actually want to reset everything, but rather just get root back. The way you flashed Dreaimg.nbh the first time was not through recovery but rather through fastboot. Look into how to root your phone again, but I'll put you on the right path. Power up by holding the camera button and power, and flash that image, then do the telnet thing and flash a new recovery image. Best of luck.
Ooglez said:
I'm assuming you don't actually want to reset everything, but rather just get root back. The way you flashed Dreaimg.nbh the first time was not through recovery but rather through fastboot. Look into how to root your phone again, but I'll put you on the right path. Power up by holding the camera button and power, and flash that image, then do the telnet thing and flash a new recovery image. Best of luck.
Click to expand...
Click to collapse
It seems you misunderstood. Those directions you are giving me are exactly what i did. I made it all the way up to The Terminal emulator. It says there is no recovery.img in my system, when i check its there right after i have already downloaded it.. I'm not sure why it isnt working, but maybe do i need to unroot my phone?
Jose_95 said:
It seems you misunderstood. Those directions you are giving me are exactly what i did. I made it all the way up to The Terminal emulator. It says there is no recovery.img in my system, when i check its there right after i have already downloaded it.. I'm not sure why it isnt working, but maybe do i need to unroot my phone?
Click to expand...
Click to collapse
Had the same problem but i then i switched over and used one click root and went straight to cyanogen.
androidboi209 said:
Had the same problem but i then i switched over and used one click root and went straight to cyanogen.
Click to expand...
Click to collapse
Then what do you suggest for this situation? I'm really pissed since this Cache thing is making my phone unable to read anything in my SD card like things that have to do with root..
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've been having trouble with my Vibrant and with T-Mobile in limbo I picked up a N1 off ebay to hold me over. This thing is driving me insane!
The phone came with CM7 installed on it, but the person that shipped it to me didn't erase any of there stuff so I figured I would flash a fresh image on the phone to take care of things. I've flashed my Vibrant a dozen or so times and never had an issue. Flashed the N1 and it comes up with an X made of 4 different colored lines and a little lock at the bottom. I know some roms take a while to load so I let it sit for an hour. Nothing.
Since I've been trying everything I can find out how to recover the phone including all of the guides on the wiki. I'm at my wits end at this point. I can't get into clockwork at all on the phone. It gets stuck in the bootloader and if I select recovery it just takes me back.
I've got droid explorer running, and the phone shows up, but it doesn't show anything on the phone, no folders or files and won't let me load anything on to it. (it says it is, but then stays blank) I have no clue what to do at this point short of taking a sledge hammer to it. (obviously I'm posting this as I consider that to be plan B)
I don't need anything special, I just want a working phone. Is that really so much to ask for?
If ur Phone is running( means u can boot) try flashing cwr from rom manager and flash the rom again or try to hard reset the phone and then see ?
Firstly, I would start of by being more specific about what you have tried.
If you really have tried "everything", then there's nothing anyone can do for you.
I suspect you haven't tried "everything"...?
danger-rat said:
Firstly, I would start of by being more specific about what you have tried.
If you really have tried "everything", then there's nothing anyone can do for you.
I suspect you haven't tried "everything"...?
Click to expand...
Click to collapse
I'm sure I haven't, just what I found in the wiki
I tried the PASSIMG.ZIP and it failed
I tried Amon_Ra's Recovery and the only way I can get it to do anything is to tell it to flash in droid explorer and it just reboots and gets stuck. Now nothing is showing up file wise in droid explorer and I can't transfer the image onto the root.
When I could get into clockwork I tried flashing different roms but it would just go to a screen with the clockwork logo and get stuck.
amolji said:
If ur Phone is running( means u can boot) try flashing cwr from rom manager and flash the rom again or try to hard reset the phone and then see ?
Click to expand...
Click to collapse
I can turn it on to the screen with the multicolored X or the bootloader, that's it. How do I do a hard reset?
n25philly said:
I can turn it on to the screen with the multicolored X or the bootloader, that's it. How do I do a hard reset?
Click to expand...
Click to collapse
in the bootloader I think (dont take my rookie rooting words too serious) theres a hard reset menu under recovery. it will take you to another x and press volume up and power for the menu to pop up.
try fastboot a recovery image (either Amon Ra or CWM) and see if you can get back to recovery after that.
Well I'm assuming you already have a custom recovery since it came with CM and you've, as you said, flashed it (what exactly do you mean by that by the way? flashed another rom?). So all I can recommend is that you wipe a few times and try flashing a few different roms and hopefully one will boot. Not the best advice in the world but its always worked for me before and my N1 and my DEXT before hand when I've messed them up!
You still did not say what you flashed to your phone.
Anyways follow the restore to stock guide.
I don't know what this Droid manager thing is but don't use it. Install the sdk.....
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)