Database Develop

How to COMPLETELY reset phone? Please Read..

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..

Help! Totally messed up device!

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.

phone semi bricked

ok the phone is not bricked an i know there is only one way to brick a hero blah blah blah. but i have psfmod recovery flashed to my phone and i was trying to do the firats mtd partition thing. so i did everything it said and when it came time to do adb shell,reboot recovery it wouldnt work. so after about 5 minutes i realized that the computer wasnt recognizing my phone. i guess cause of the psfmod recovery. and i had already wiped everything. so i wiped everything again and flash zenaraia rom back on. but after rebooting it just stays at the white HTC screen. waited for an hour. i tried wiping and reflashing like 20 times. and i cant mount the sdcard to put another rom on there since the computer wont recognize my phone. anybody following me? lol any suggestions?

It seems like you might need to RUU... have you tried doing that?

cp0020 said:
ok the phone is not bricked an i know there is only one way to brick a hero blah blah blah.
Click to expand...
Click to collapse
Haha I came here just to possibly rip on the OP when I read the title but saw you already mentioned it :/ So you put it in your thread title anyway?
As the guy said before, try running the RUU - should be able to be done in the bootloader.
OR if you can boot up into a rom (wasn't too sure judging by what I read) just get a Dropbox, throw a rom.zip on it, get the app for the phone, sync and bam. New rom.zip on your phone to try.
If neither one can be done, you need to find another phone, camera, sdmount...something so you can add files to it. Even if its just a HERCIMG.zip to update via the bootloader (look up s-off if you don't know what that's about)
Good luck

thanks for your help guys. i'll try the RUU but i dont think it will work since my computer wont recognize my phone while in bootloader. im pretty sure it's just the psfmod recovery that f'd everything up. and yeah i cant boot into a rom. im hoping that somehow my rom.zip just got messed up somehow.

ok yeah RUU didnt work. my only other option is to find a laptop or something

Try getting a live Fedora or Ubuntu linux cd (or any flavor for that matter) and booting it up.

what would that do? i went back to the psfreedom thread and i saw that adb and usb mass storage does not work with that recovery. i should have read better lol

Same thing happenned to my evo..i kept tryna flash the wrong kernel wit nym rom..all i did wuss flashed the rom without da kernel and walla...it started workin again..thnx god..idk if dis would help but it worked for me..
Sent from my PC36100 using XDA App

ok i got it to work. i was talking to nfinitfx45 on google talk and he said to boot up in fastboot and then plug the phone into the computer and then i can run the RUU and it worked like a charm now i just gotta re root :/

cp0020 said:
ok i got it to work. i was talking to nfinitfx45 on google talk and he said to boot up in fastboot and then plug the phone into the computer and then i can run the RUU and it worked like a charm now i just gotta re root :/
Click to expand...
Click to collapse
yay !!! im just quoting this because this bears repeating...
1 - if recovery is not working, go into fastboot to get pc to recognize phone...
2 - if roms (recovery or whatnot) are not working, reflash to RUU to start fresh...
(and adding)
3 - once youve started fresh, then flash a working-recovery and go back to your latest [nandroid] backup...
(you always have a good backup to use, right ?) h.

I think all you had to do was flash a different recovery from terminal if you were able to boot up the reason y I didn't use that mod was the fact you can't use adb wen u flash that recovery in that post I think the op posted the link to the old recovery that allowed you to use adb good luck
Root-Hack-Mod-Always™

that was the problem. i couldnt boot to a rom cause i had erased all data and my rom.zip had got corrupted somehow. and with that recovery you couldnt do adb or usb mass storage. so i started freaking out lol. thanks again nfinite

So I'm having a similar problem. I can use ADB to reboot my phone, so I know the computer is talking to the phone but it wont get past the HTC screen. I was trying the firerat mod and made it to the reboot as well but it never came back up. If I reboot to recovery its a white screen with the android on the skate board but the only option is to clear user data and then reboot again which goes back to the HTC screen. I tried the RUU but it wont install because it says my phone doesnt have enough battery (it's been charging on and off for the better part of 24 hours now.) Any assistance or advice would be greatly appreciated.

first, can you use usb mass storage? if so the you need to put a rom on your sdcard and flash it and see if that fixed it. and if you want to RUU. then pull the battery and put it back. then hold volume up and power at the same time. then hit the button it says to to go into fastboot. you should already be in fastboot though. and then while in fastboot plug the phone into the pc and you may have to install drivers. and then you can run the RUU.

I'm not exactly sure what happened but i got it working. I ran "adb reboot-bootloader" from the menu that brought up i was able to get back to the clockwork recovery, restore my nandroid and finish the mod. all appears to have worked beautifully except that last night my battery went completely dead over night (for the first time) although i'm doubting that that has anything to do with any of this

[Q] LG L90 D315 bricked without recovery access etc

So this is my first xda thread. I spent hours searching without finding a solution for my particular case.
I am using a LG L90 D415 (T-Mobile version) and I got bored of it and so I started playing with the system (not the first phone I'm doing that with, so I know a bit about that sutff). So I tried to install the new Android L home launcher from here http://forum.xda-developers.com/showthread.php?t=2796019
I did everything like explained, installed it and changed the build.prop like described. But after I rebooted my phone, expecting a new home launcher, the phone boots, I am at the lockscreen, but after like 4 seconds I receive multiple errors (like gapps stopped working) and than everything freezes and it reboots.
Unfortunaly I didn't install a recovery or unlocked fastboot. So I can access download mode, but that's it. My computer doesn't see my phone (because usb debugging deactivated?) and so I don't know what to do. I think that's a pretty tough case but I hope some smart person can help me
Thank you

mcfiish said:
So this is my first xda thread. I spent hours searching without finding a solution for my particular case.
I am using a LG L90 D415 (T-Mobile version) and I got bored of it and so I started playing with the system (not the first phone I'm doing that with, so I know a bit about that sutff). So I tried to install the new Android L home launcher from here http://forum.xda-developers.com/showthread.php?t=2796019
I did everything like explained, installed it and changed the build.prop like described. But after I rebooted my phone, expecting a new home launcher, the phone boots, I am at the lockscreen, but after like 4 seconds I receive multiple errors (like gapps stopped working) and than everything freezes and it reboots.
Unfortunaly I didn't install a recovery or unlocked fastboot. So I can access download mode, but that's it. My computer doesn't see my phone (because usb debugging deactivated?) and so I don't know what to do. I think that's a pretty tough case but I hope some smart person can help me
Thank you
Click to expand...
Click to collapse
No custom recovery and no fastboot? Factory reset is your only option. See this post. Scroll down to Q14. Even though it's titled something else, the same button presses apply for your device in it's current state, ie; no recovery, no fastboot

shinobisoft said:
No custom recovery and no fastboot? Factory reset is your only option. See this post. Scroll down to Q14. Even though it's titled something else, the same button presses apply for your device in it's current state, ie; no recovery, no fastboot
Click to expand...
Click to collapse
First thanks for the fast answer. So I figuered that I only need to delete the build.prop file and replace it with my backup file. Isn't there any way to rescue my files and/or access the /system folder? I'm an exchange student now and I don't wanna lose my picture memories
And btw I know that I build the perfect worst case scenario right now
Oh and in the L90 faq it says that when you flashed a recovery and you navigate to factory reset it won't reset but boot into recovery. Does something like this work even without recovery, so I could try doing stuff with adb?

mcfiish said:
First thanks for the fast answer. So I figuered that I only need to delete the build.prop file and replace it with my backup file. Isn't there any way to rescue my files and/or access the /system folder? I'm an exchange student now and I don't wanna lose my picture memories
And btw I know that I build the perfect worst case scenario right now
Click to expand...
Click to collapse
If adb isn't detecting the phone, no. There isn't any other way.
mcfiish said:
Oh and in the L90 faq it says that when you flashed a recovery and you navigate to factory reset it won't reset but boot into recovery. Does something like this work even without recovery, so I could try doing stuff with adb?
Click to expand...
Click to collapse
Unfortunately, no.
Factory reset will not erase your sdcard. It will however erase internal data. It will return the phone to the state it was in the first time it was powered on.

Unable to mount /data, fastboot doesn't seem to be able to write

Hi everyone, I'm having a lot of problems with my phone: last night, after it dropped to 0% battery life, it wouldn't charge. So i waited a while and ifinally managed to turn it on, but It wouldn't go past the Cyanogenmod logo. So i tried few things,first wiping cache, then factory reset from TWRP and I even tried the "Factory" option in the fastboot screen. Nothing worked, and it even got worse I think, TWRP says it's unable to mount /data partition and /storage partition. I don't know what caused it, and i don't remember the precise moment it became "unmountable" for the first time (since I've been trying to fix this thing for like 24 hours now).
Since i couldn't fix it via recovery, I tried looking for people who had the same problem on the internet, and I tried everything i could find. (like this: http://forum.xda-developers.com/showthread.php?t=2683787).
I then tried to go back to stock rom via adb and fastboot, but without success.
The main problem with fastboot is the fact that it doesn't change anything in my phone, it gives no errors when i try to flash the stock rom, but when i reboot my phone, nothing changes, or at least this is my opinion, since I still get the cyanogenmod logo, and TWRP doesn't get replaced (while it should go away, since when in the whole process of flashing the rom, i also flash recovery.img, which shouldn't be TWRP).
I tried a whole lot of other commands too, like "fastboot erase recovery", but TWRP is still there, and so is the cyanogenmod logo.
This is why i think fastboot is unable to write in my phone, but if that's the case, it should at least give errors.
So, wrapping up, my data partition seems to be corrupted, and flashing the stock rom still gets my into a bootloop (with the logo from the previous rom and TWRP still there).
Do you have any advice?
P.S: my phone is a xt1068

Are you able to pull logcat?

Logcat command works, i don't get errors in the terminal, but in the text file there's only this line : "/sbin/sh: exec: line 1: logcat: not found"
Dmesg works though, I don't know if it's helpful
"

dagrot said:
I then tried to go back to stock rom via adb and fastboot, but without success.
The main problem with fastboot is the fact that it doesn't change anything in my phone, it gives no errors when i try to flash the stock rom, but when i reboot my phone, nothing changes, or at least this is my opinion, since I still get the cyanogenmod logo, and TWRP doesn't get replaced (while it should go away, since when in the whole process of flashing the rom, i also flash recovery.img, which shouldn't be TWRP).
I tried a whole lot of other commands too, like "fastboot erase recovery", but TWRP is still there, and so is the cyanogenmod logo.
This is why i think fastboot is unable to write in my phone, but if that's the case, it should at least give errors.
So, wrapping up, my data partition seems to be corrupted, and flashing the stock rom still gets my into a bootloop (with the logo from the previous rom and TWRP still there).
Do you have any advice?
P.S: my phone is a xt1068
Click to expand...
Click to collapse
I have same phone, you mentioned you also tried to flash stock rom without success, did you flash the partition file aswell before flashing system and the rest of files ? Check the flashfile.xml file into the stock firmware folder to make sure you not missing anything.
Code:
fastboot flash partition gpt.bin
Good luck.

i'm on the same boat. It seems it's a NAND issue, but how come it happens randomly?

It seems to happen (its a bit rare, so don't get worried) when you let your battery drop to 0% and the phone suddently turn off, like what happened to the OP.
Sent from my XT1063 using XDA Free mobile app

Lynse said:
It seems to happen (its a bit rare, so don't get worried) when you let your battery drop to 0% and the phone suddently turn off, like what happened to the OP.
Sent from my XT1063 using XDA Free mobile app
Click to expand...
Click to collapse
If it's a bit rare, how come there are a rather interesting quantity of posts regarding that matter? I'd like to know WHY I can't write even with fastboot. There should be a way of unlocking the NAND / partitions. Even if I try to hard brick it, it's impossible.

PS: can we someone a look at this? http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2
Possibly if we can force the way to QHSUSB mode, phone can be saved.

jhonnyx said:
PS: can we someone a look at this? http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2
Possibly if we can force the way to QHSUSB mode, phone can be saved.
Click to expand...
Click to collapse
Unfortunately I didn't quite understand what that is about, if you happen to try it out let us know.
Anyway, if we don't manage to fix it, I guess I'm going to try and take it back to the store, since it is a common problem. Only problem is I'm on a custom rom and I can't even go back to stock and relock the bootloader, so I don't think they are going to replace it, but it's worth a try.

You can try by helping me to look for a circuit PDF from the board or trying it yourself.

I could try and disassemble it, but you're gonna have to wait a few days, I'm not at home and I'm gonna be back on the weekend.
As for the circuit pdf, I was only able to find videos and guides on how to disassemble it, unfortunately

Dude, no worries. Ive took the back out with all the screws, but I have nothng to make shorts with.... I'll come up with something. Take your time and keep me posted.

any news concerning this problem? i have tried searching for a manual but I did not succeed.
Anyways after finding the manual, we can short circuit the 2 capacitors there and the phone will be in qhsusb mode.
And after that ?

gbb14 said:
any news concerning this problem? i have tried searching for a manual but I did not succeed.
Anyways after finding the manual, we can short circuit the 2 capacitors there and the phone will be in qhsusb mode.
And after that ?
Click to expand...
Click to collapse
After that.... well.... after some research, we'll be needing singleimage.bin to use the blankflash utility for lollipop phones (mbm-ci 5.0 lollipop) so somebody can generate the singleimage.bin for us.
Once we have that, we can try to flash the phone at lowlevel to see what happens.

I will search the internets in hoping to find the schematics of this phone.
Keep me informed if you find it faster .
Cheers mate

we can connect through hangouts / etc.
look up for my user at gmail