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.
Related
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..
I've tried many different things in alot of the threads I've read on this forum and nothing is working. I tried using the One-Click root on my Droid and it didn't work, come to find out, it was an outdated method for the Droid 3. It messed up my phone. My apps constantly crash. My texts disappear, then sometimes reappear switching the place of the texts randomly. When I reset from settings, it restarts phone, but nothing is reset. It won't let me check my e-mails(G-mail). I can hardly do anything. I've tried flashing back using the AP Fastboot method from psouza(spelling?). On my phone it says Battery OK/Program OK/USB Connected. So I run the "CLICK HERE - Flash Verizon DROID 3 OTA 5.6.890 to phone.bat". It failed.
Then I tried ovelayers method. Everything seems to go good. And I was happy! But when it rebooted, it took me to the android triangle screen. SO I selcected reboot. And absolutely nothing changed. Am I Missing a step? I also tried doing it again, but after it went to traingle android screen, I selected the update from the SD card, installed it, rebooted, and STILL nothing. Nothing changes. Ever. Nothing is working. Please help. I tried being as descriptive as possible so that it answers most potential questions.
*Edit* I've also tried the RDS Lite method. Crashes on step 3.
Phone specs: Version: 5.7.906.XT862.Verizon.en.US
Kernel: 2.6.35.7-g5fa4155
Android 2.3.4
download full system file
http://dev-host.org/uEA
put it on your sdcard, and if you are on "android triangle screen" go to menu
pickup update, select the downloaded file and install it.
After will all done push reboot from menu
thats all
Make sure you use the sbf for. 906 and not the one for. 890
http://d-h.st/mvX
niko99 said:
download full system file
put it on your sdcard, and if you are on "android triangle screen" go to menu
pickup update, select the downloaded file and install it.
After will all done push reboot from menu
thats all
Click to expand...
Click to collapse
I have the full system file already. That's what I tried using to update. The problem doesn't lie there though. The problem is that no matter what I do, the phone never resets. It's on right now. If I uninstall apps right now and restart my phone, they'll still be there. Likewise with installing them. If I text anyone, when I restart my phone, that conversation will be gone. Likewise with call logs and everything else. The phone literally after every restart goes back to the same position it was when I badly rooted the first time. No resets, recoveries, hard resets, flashes, etc have worked thus far. I've used ALL the one click SBF versions also, just to be thorough. The phone literally will not change. What I need is something similar to a computer. I need to completely wipe it. Then I need to completely reinstall it from scratch. Just like reformatting your hard drive. I've heard that there has really been no case of an unbrickable phone, that there is always a way to fix it; but this far, I haven't found anybody that hasn't had their phone fixed. Even those that have had similar issues fixed it, and I've tried the methods they've provided to no avail.
xJolly said:
I have the full system file already. That's what I tried using to update. The problem doesn't lie there though. The problem is that no matter what I do, the phone never resets. It's on right now. If I uninstall apps right now and restart my phone, they'll still be there. Likewise with installing them. If I text anyone, when I restart my phone, that conversation will be gone. Likewise with call logs and everything else. The phone literally after every restart goes back to the same position it was when I badly rooted the first time. No resets, recoveries, hard resets, flashes, etc have worked thus far. I've used ALL the one click SBF versions also, just to be thorough. The phone literally will not change. What I need is something similar to a computer. I need to completely wipe it. Then I need to completely reinstall it from scratch. Just like reformatting your hard drive. I've heard that there has really been no case of an unbrickable phone, that there is always a way to fix it; but this far, I haven't found anybody that hasn't had their phone fixed. Even those that have had similar issues fixed it, and I've tried the methods they've provided to no avail.
Click to expand...
Click to collapse
Can you install bootstrap? That way you can wipe data, and there should be no way it boots back like nothing has changed
http://db.tt/pi5c484a
Edit: or, boot into recovery with x+power (or m+power i always forget) and wipe/factory from there
DoubleYouPee said:
Can you install bootstrap? That way you can wipe data, and there should be no way it boots back like nothing has changed.
Edit: or, boot into recovery with x+power (or m+power i always forget) and wipe/factory from there
Click to expand...
Click to collapse
I will attempt that now. How is it used? I can build pc's and am rather intelligent in the IT of macs and pc's. But haven't had to do much with Androids till now. Lol. I've tried the wipe/factory method already. I understand that .apk is the file extension for Google Play apps, and I can install it via the SD card, but what do I do from then?
*EDIT* It's installed, it has bootstrap recovery and reboot recovery. Reboot does nothing. Bootstrap says there's an error running a command. Looks like a directory about files and hashcodes. "Working Directory: null/Environment: null".
xJolly said:
I will attempt that now. How is it used? I can build pc's and am rather intelligent in the IT of macs and pc's. But haven't had to do much with Androids till now. Lol. I've tried the wipe/factory method already. I understand that .apk is the file extension for Google Play apps, and I can install it via the SD card, but what do I do from then?
*EDIT* It's installed, it has bootstrap recovery and reboot recovery. Reboot does nothing. Bootstrap says there's an error running a command. Looks like a directory about files and hashcodes. "Working Directory: null/Environment: null".
Click to expand...
Click to collapse
First you need root access. Use Motofail if you haven't:
https://www.dropbox.com/s/wpl88mwm6eilhe6/motofail.exe
Open bootstrap, press bootstrap recovery, afterwards press reboot recovery.
If it doesn't work, shutdown your phone, hold X and press power and do it from there
DoubleYouPee said:
First you need root access. Use Motofail if you haven't:
Open bootstrap, press bootstrap recovery, afterwards press reboot recovery.
If it doesn't work, shutdown your phone, hold X and press power and do it from there
Click to expand...
Click to collapse
Figured. My phone won't root. Like I said, nothing will change about it.
xJolly said:
Figured. My phone won't root. Like I said, nothing will change about it.
Click to expand...
Click to collapse
Ok so what about x+power?
DoubleYouPee said:
Ok so what about x+power?
Click to expand...
Click to collapse
No. It doesn't work. I've tried that.
xJolly said:
No. It doesn't work. I've tried that.
Click to expand...
Click to collapse
So you did wipe/factory reset from recovery and it still boots like nothing happened? I'm not sure how thats possible.. stock recovery shouldnt have anything to do with what you messed up in your rom. Maybe for some reason your phone is unable to write data anymore
DoubleYouPee said:
So you did wipe/factory reset from recovery and it still boots like nothing happened? I'm not sure how thats possible.. stock recovery shouldnt have anything to do with what you messed up in your rom. Maybe for some reason your phone is unable to write data anymore
Click to expand...
Click to collapse
I'm going to record a video. And show you the multiple things that happens. I'll have to PM it to you though, and anyone who wants to see it.
I remember someone else having a similar issue on their device. Since I'm home sick today I'll see if I can find the thread and if it ever got solved
Sent from my XT860 using xda premium
Just saw your vid and its exactly as you say. I don't know whats going wrong..
Writing yo your internal might not be the same as writing to your data partition.. I don't see why else wiping from recovery would fail since that part should be unaffected.
You said sbf says its succesful however on your screenshot i see errors.
DoubleYouPee said:
Just saw your vid and its exactly as you say. I don't know whats going wrong..
Writing yo your internal might not be the same as writing to your data partition.. I don't see why else wiping from recovery would fail since that part should be unaffected.
You said sbf says its succesful however on your screenshot i see errors.
Click to expand...
Click to collapse
There's only errors for the click here to flash method, however, the ovelayer method screenshot says there are no errors, unless I am missing something there.
xJolly said:
There's only errors for the click here to flash method, however, the ovelayer method screenshot says there are no errors, unless I am missing something there.
Click to expand...
Click to collapse
You're right. No way you can send it back for replacement? Your phone seems stock
DoubleYouPee said:
You're right. No way you can send it back for replacement? Your phone seems stock
Click to expand...
Click to collapse
Well, I don't have insurance on it, as I had gotten it from a friend. So, no. Not without paying an arm and a leg, at which point I'd pay for a new phone instead. I just really wish this could be fixed. I've heard no phone was unbrickable. AM I THE PRODIGY?!
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)
By mistake i wipe everything from twrp recovery, now i have NO OS!! just boots to a white warning your boot loader is unlocked. i can access twrp and fastboot,
It's may be possible to push a flashable zip to your sdcard, the reboot to recovery and flash it. That would save anything on the sdcard. Or you could download your firmware, then RSD lite or batch script and fully restore the device to stock.
THIS
OR
THIS
OR something like THIS
gokart2 said:
It's may be possible to push a flashable zip to your sdcard, the reboot to recovery and flash it. That would save anything on the sdcard. Or you could download your firmware, then RSD lite or batch script and fully restore the device to stock.
Click to expand...
Click to collapse
Any idea how i can go about doing it, just so much information it hard to tell which one i should be doing. ive been trying to use the moto x toolkit to push the files to the phone and its not working.
gokart2 said:
It's may be possible to push a flashable zip to your sdcard, the reboot to recovery and flash it. That would save anything on the sdcard. Or you could download your firmware, then RSD lite or batch script and fully restore the device to stock.
THIS
OR
THIS
OR something like THIS
Click to expand...
Click to collapse
device not found not matter what i do
If it boots to that bootloader locked screen you can get to fastboot. Start the device in fastboot by holding thepower button and volume (-) button for ~10 sec, after screen turns off. Let go and it should be at the bootloader screen. Then do THIS. Had a similar issue and it worked fine.
gokart2 said:
If it boots to that bootloader locked screen you can get to fastboot. Start the device in fastboot by holding thepower button and volume (-) button for ~10 sec, after screen turns off. Let go and it should be at the bootloader screen. Then do THIS. Had a similar issue and it worked fine.
Click to expand...
Click to collapse
How do i know what firmware i have, i dont want to make this any worse than what it is
This shouldn't be a problem. I'm assuming that your bootloader is unlocked, given that you had TWRP installed. Do you know if you have the SDK and the adb drivers/drivers for your phone installed on your PC?
In the future, I'd do a little more research before you fiddle with custom recoveries or other such utilities too much. There are a lot of valuable resources on this site in particular, and a quick forum search for what you're about to experiment with can save you a lot of stress if you screw something up.
Sent from my XT1056
izzy10459 said:
How do i know what firmware i have, i dont want to make this any worse than what it is
Click to expand...
Click to collapse
Blur_Version.139.12.2.ghost_sprint.Sprint.en.US is the one that originally came with the device.
Blur_Version.139.14.1.ghost_sprint.Sprint.en.US is the update for the camera, etc.
Odds are you should do 139.14.1. Would either be flashing an update, or the same firmware. If you were on Kit Kat (not likely), then I'd worry a little, although heard it has worked going backwards.
IF I WERE IN YOUR SHOES, I'D DO 139.14.1.
When you unzip both, there will be a folder named the same as the zips. Go into that folder and take the contents of one and put it into the other. His directions had me confused for a sec. Good luck.
gokart2 said:
Blur_Version.139.12.2.ghost_sprint.Sprint.en.US is the one that originally came with the device.
Blur_Version.139.14.1.ghost_sprint.Sprint.en.US is the update for the camera, etc.
Odds are you should do 139.14.1. Would either be flashing an update, or the same firmware. If you were on Kit Kat (not likely), then I'd worry a little, although heard it has worked going backwards.
IF I WERE IN YOUR SHOES, I'D DO 139.14.1.
When you unzip both, there will be a folder named the same as the zips. Go into that folder and take the contents of one and put it into the other. His directions had me confused for a sec. Good luck.
Click to expand...
Click to collapse
OMG THANK YOU GUYS!!, I was scared i was going to have a brick phone, that will be the last time i try to hang with the big boys 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.