Related
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?!
Hi,
So I finally got my first error. :crying:
I did a reboot from an app called quick reboot to recovery, and now I am stuck in CWM bootloop.
The sad thing is that I went into recovery to do a nandroid so doing a restore from that backup didn't help.
Any way to fix this without flashing the device back to stock?
Thanks!
Edit:
Sorry, forgot to mention I am running cocore 3.9 kernel with deodexed JB.
YMatrix said:
Hi,
So I finally got my first error. :crying:
I did a reboot from an app called quick reboot to recovery, and now I am stuck in CWM bootloop.
The sad thing is that I went into recovery to do a nandroid so doing a restore from that backup didn't help.
Any way to fix this without flashing the device back to stock?
Thanks!
Edit:
Sorry, forgot to mention I am running cocore 3.9 kernel with deodexed JB.
Click to expand...
Click to collapse
You know how to use ADB shell? You need to install any other kernel with dd command, or try to do "reboot" from ADB shell in recovery.
I have used the ADB shell on a sony xperia phone so I know more or less how to use it.
Do I need to install any additional files for my phone, or is the ADB ready for my phone (in the xperia I had to get the google usb driver and update it to be able to get into fastboot mode)?
How do I get the phone to be recognized by ADB if i'm stuck in recovery mode?
Which commands do I need to run to reboot the device?
Ok, this is weird. It is fixed by itself
I actually didn't do anything.
I removed the battery again to turn the device off.
I got the cable plugged to my PC (the device showed the charging logo) then turned the device on (to get ready to use ADB).
Surprise surpise the device booted up normally.
I had already tried the process of removing the battery, and did multiple reboot from the CWM option, with no success before.
Now to try to understand.
What just happened?
Why did it get stuck in the recovery bootloop in the first place (I have used this app on GB, so it should also work on JB)?
How did it fix itself? Connecting the cable before the device was on "freed it" somehow?
Most importantly what do you need to do if that happens in the future?
If you have any advice how to backtrack what happened, I would be glad also to share for other users who might come across this situation.
YMatrix said:
Ok, this is weird. It is fixed by itself
I actually didn't do anything.
I removed the battery again to turn the device off.
I got the cable plugged to my PC (the device showed the charging logo) then turned the device on (to get ready to use ADB).
Surprise surpise the device booted up normally.
I had already tried the process of removing the battery, and did multiple reboot from the CWM option, with no success before.
Now to try to understand.
What just happened?
Why did it get stuck in the recovery bootloop in the first place (I have used this app on GB, so it should also work on JB)?
How did it fix itself? Connecting the cable before the device was on "freed it" somehow?
Most importantly what do you need to do if that happens in the future?
If you have any advice how to backtrack what happened, I would be glad also to share for other users who might come across this situation.
Click to expand...
Click to collapse
What happend is the problem with J4FS driver in system (kernel). So do not use Reboot recovery untill it is fixed in kernel.
Probably removing battery reseted it, and you could go to system normaly.
shut_down said:
What happend is the problem with J4FS driver in system. So do not use Reboot recovery untill it is fixed in kernel.
Probably removing battery reseted it, and you could go to system normaly.
Click to expand...
Click to collapse
But I just now succeeded going into recovery the normal way (turn off device -> vol up+home+power) 3 times (also did another nandroid :good and back to system with no problems. So I am guessing there is a bug when trying to reboot to recovery with the app?
If removing the battery did the trick why didn't it work the first time I did it?
YMatrix said:
But I just now succeeded going into recovery the normal way (turn off device -> vol up+home+power) 3 times (also did another nandroid :good and back to system with no problems. So I am guessing there is a bug when trying to reboot to recovery with the app?
If removing the battery did the trick why didn't it work the first time I did it?
Click to expand...
Click to collapse
Problem is with doing command "reboot recovery" while you are booted in system. That does not consider going there by using hardware buttons. For ability to use reboot recovery from some app you need fixed J4FS driver in kernel. I got bootloop to recovery too with some version of CoCore. Now you can't do anything untill it is fixed. Look at kernels thread for updates, and report your problem.
About that solution, I do not know. I solved it with flashing other kernel from recovery with ADB shell and DD command. Didn't try anything else.
Thank you!
I will notify cocafe of the bug.
Tried to root, flash rom, now stuck at "This build is for development purposes only"
Hey guys,
I tried rooting my phone, and I rooted it and installed TWRP, etc. However, I tried to install a ROM and now it is stuck at the "This build is for development purposes only" screen.
I can boot into the bootloader, and when I select recovery, nothing happens. Is there anyway to use fastboot or something to restore my device? I made a backup before I rooted.
Please help! I'm also a noob, so please explain everything!
Thank you, I hope i didn't brick my phone.
evilhugbear said:
Hey guys,
I tried rooting my phone, and I rooted it and installed TWRP, etc. However, I tried to install a ROM and now it is stuck at the "This build is for development purposes only" screen.
I can boot into the bootloader, and when I select recovery, nothing happens. Is there anyway to use fastboot or something to restore my device? I made a backup before I rooted.
Please help! I'm also a noob, so please explain everything!
Thank you, I hope i didn't brick my phone.
Click to expand...
Click to collapse
Did you wipe before you flashed the ROM? Try booting into recovery via terminal. If that doesn't work try reflashing twrp and then using boot loader to get to recovery
Sent from my HTCONE using xda app-developers app
youkosnake said:
Did you wipe before you flashed the ROM? Try booting into recovery via terminal. If that doesn't work try reflashing twrp and then using boot loader to get to recovery
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Reflashing TWRP and flashing my backup fixed it.
Thanks! I thought I bricked my phone!
evilhugbear said:
Reflashing TWRP and flashing my backup fixed it.
Thanks! I thought I bricked my phone!
Click to expand...
Click to collapse
Nope, in a "brick" situation, the boot manager gets messed up somehow and the phone will not boot up at all, not even to show an error message. It effectively becomes a fancy paperweight.
In a "soft brick" such as your situation, the OS encounters issues for whatever reason and cannot get into the OS. This is characterized by the phone bootlooping, getting stuck on a splash screen, getting to the boot animation and freezing, pretty much any time when it will power up but will not go into the OS.
CNexus said:
Nope, in a "brick" situation, the boot manager gets messed up somehow and the phone will not boot up at all, not even to show an error message. It effectively becomes a fancy paperweight.
In a "soft brick" such as your situation, the OS encounters issues for whatever reason and cannot get into the OS. This is characterized by the phone bootlooping, getting stuck on a splash screen, getting to the boot animation and freezing, pretty much any time when it will power up but will not go into the OS.
Click to expand...
Click to collapse
Cool, thanks for the info! How difficult is it to accidentally full brick a phone? Just curious, I've heard that it is not common any more.
evilhugbear said:
Cool, thanks for the info! How difficult is it to accidentally full brick a phone? Just curious, I've heard that it is not common any more.
Click to expand...
Click to collapse
No problem, always glad to shed some light on things :thumbup:
Well, how hard it is depends on the device. For the different carrier S3's, its really common because people keep flashing roms made for the international S3 (because they dont read that the model number doesnt match up) and brick their phone. This happens because the misc partition on the international lines up with the boot partition on the carrier-specific S3s so essentially the phone is trying to boot from information that is 1) not for that phone and 2) not the right type of information.
But apart from the international/carrier-specific rom scenario, it is very hard to brick your phone now. One almost sure-fire way to brick your phone (on any device) is by pulling the plug on it halfway through flashing/updating firmware (radios, touch screen software, stuff like that), or by flashing corrupted firmware. Also accidentally writing incorrect information (for example fastbooting a recovery to where the radio or boot partition is) can almost guarantee a brick.
As for the One, I'm sure that "help, phone wont boot" posts will start showing up here in about a month or two when the general buzz has died down some. More people are gonna start rooting their phones, not reading, and innappropriately flashing international roms on their carrier-specific One.
EDIT: Look, not even a month yet. http://forum.xda-developers.com/showthread.php?t=2248629
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.
Hello people, sorry for the long post, but i hope theres sufficient information to help you help me.
So... I come here to ask for your help and opinion. I need your guidance.
History: I was using my Moto G (2nd gen) to control the Smart TV Youtube App when, suddenly, my phone freezed completely. I tried to lock/unlock the screen and to turn off but it reset by himself and i was "oh, ok, good". Well, not so good. When it turned on again it showed the Motorola blue logo screen but turned off. Then turned on again, showed the logo, turned off and stayed is this loop until the battery went dry. After recharging i tried to turn it on again, but the same thing happened. I also tried to enter Recovery and Factory Reset but, again, the same thing happened. It doesn't even shows the screwed android logo upon recovery selection.
I made some research hoping there was a way to access the internal memory, to backup everything i could, before sending it to the technical assistance (i would copy even system files if possible).
I connected via usb to my computer, tried adb, tried fastboot, nothing worked.
Reading about fastboot stuff i found this comments on a website ( lifehacker .com/the-most-useful-things-you-can-do-with-adb-and-fastboot-1590337225 ):
"Another thing that most guides out there seem to miss.... If you need to do something in a custom recovery ROM, you do not need to flash it. You can just directly boot it from a local image on your computer using adb. A lot less destructive.
Something like:
adb boot CMR.img"
"I don't think he means "destructive" in the sense of it harms your phone. But rather, that using one recovery does not mean you have to eliminate the previous one. Say you want to try out some feature of TWRP, but you really like Clockworkmod Recovery. This would allow you to run TWRP temporarily, while still keeping Clockworkmod as the default recovery.
Sort of like using a Live DVD to boot into Ubuntu without destroying your Windows partition."
Now my question(s) is(are): Can I do something to save some data without compromising my warranty, so I can send my phone to Assistance later?
If I can flash the ROM (and access my data), do I need to unlock and/or root the phone? Is this process reversible?
I hope you can help me, thanks.