Possible Brick[Fixed] - Motorola Droid 3

So I installed and ran psouza's bloatware removal script, but when it was reset my phone got stuck at the boot screen. So I did battery pull and re-booted the phone, which led me to be stuck at the boot screen once again. Ok, no biggie, I don't really have too much on the phone I'll factory reset it. Once I did that everything was going good until after it asked me what gps services I was going to use(verizon, google, stand alone) I clicked them all pressed finished, and then things started to get a bit weird. The screen was completely black except for the notification bar up top, which I could access and set up things like wifi and such, but pulling it back up showed the same black screen as before. Now what this leads me to believe is that I might have removed the launcher on accident(I don't know how I was being very careful as to watch what I was removing, but it's been a long day...). So my question is, is there any way to recover my phone, whether it be setting it back to stock somehow, downloading another launcher from the android market(keep in mind I don't exactly have access to the market via my phone), or other? Also I really don't want to talk to Verizon/get a new phone unless it's the only thing possible.
Thanks in advance, and sorry for being such a noob >.<
Edit: Managed to install launcher pro and now everything is working fine.

use ADB and install launcherpro to the device. You can get it from www.launcherpro.com and use adb install (not push).
For everyone else reading...
Factory Reset is the last thing you want to do when having issues with your phone if you have modified the system/app files in anyway (renamed, deleted, froze, etc..).
It seems from what I've been reading, most do not know what a Factory Reset does. Factory Reset wipes your /data /cache and /davlik-cache partitions clean. It does not change your /system partition, does not "restore" apps you've deleted, changed, replaced, added or anything else in /system. Why...because there is no hidden partition that holds a copy of "how the phone was" when it was stock. It's only "resetting" what you have (as a user) done on the phone. If you've deleted contacts.apk and added SuperUser.apk to /system/app....then that's the same way it will be after a factory reset. Same for /system/xbin or /system/bin if you've copied SU and BUSYBOX there......
So what it does it is erases all the settings, configurations, apps you've downloaded/installed from the Market, account info and such....things that might still function once configured and then some apps deleted/renamed/frozen but will not function if trying to configure fresh.
If you have a stock phone, Factory Reset can be your friend. If you have a modified phone, Factory Reset can be your worst nightmare.
Complete ROMs (CM7, Bugless Beast, etc..) can be Factory Reset just like a stock ROM...unless you start changing things in /system......
Remember, Factory Reset is not a recovery, it's an "erase the stuff I've added/configured" based off a stock unrooted users abilities. Changes to files/folders/apps that are in areas that require root to access, are not touched by a Factory Reset.
This is why you can get in more trouble....things are missing and now you've wiped your configurations/install apps (example...using LauncherPro and deleted the stock Launcher.apk...do a Factory Reset....now LauncherPro no longer exist and the deleted stock Launcher.apk is still deleted....no home screen launcher).

Thanks for the insight tcrews, I managed to get everything straightened out right before you posted, but it still has some valuable information that I will make sure to remember. I really shouldn't have done to much messing around with my phone since I wasn't quite sure what I was doing(I don't even have a reliable way to recover via sd, or cloud storage yet). I think this instance was just one of carelessness, in that I wasn't paying full attention to what was going on. Oh well, I learned my lesson.

Related

Pushing modified framework-res.apk

I've been working on my framework-res.apk lately, but haven't tried pushing it yet. I know (most of) how to do the procedure, but i want to be sure before i try. If i screw up, i'll be without a phone for a few days due to my current internet connection. (No, i don't want to wait )
What i know, is that i should modify the apk with 7-Zip, replace the graphics i intended (mostly statusbar icons). I don't have to sign the apk since i'm pushing it trough adb shell, and my rom (V10e) is already rooted. The commands for pushing it from adb shell are simply as follows:
Code:
adb push framework-res.apk /system/framework
I have the three following questins that google can't seem to answer for me:
1. Should i wipe dalvik cache (or anything else) after i push the framework-res.apk?
2. If the answer to the previous question is yes, then can i wipe dalvik cache without a custom bootloader?
3. Does anybody have any experience with doing this to the V10e rom? According to google, a lot of users seem to have problems with apps force closing after doing this, even though it's only graphics that has been replaced. However, this is on random handsets, not P-970...
hulkhaugen said:
1. Should i wipe dalvik cache (or anything else) after i push the framework-res.apk?
2. If the answer to the previous question is yes, then can i wipe dalvik cache without a custom bootloader?
3. Does anybody have any experience with doing this to the V10e rom? According to google, a lot of users seem to have problems with apps force closing after doing this, even though it's only graphics that has been replaced. However, this is on random handsets, not P-970...
Click to expand...
Click to collapse
1.you don't have to wipe dalvik cache,just reboot
2.
3.to avoid fc,you should backup your original framework-res.apk,if you face fc,just push the original one back.
Well thanks for your reply
I just found out something stupid. I don't have access to WiFi atm, nor 3g, so i downloaded ClockworkMOD.apk and recovery-clockwork-5.0.2.6-p970.img, figured i could install it manually. So i started CWM, and tapped Reboot into recovery...nope, should note have done that, lol. When it started up, i got a huge error label, with LG security error as a subtitle to that. Now my phone won't start. After that message, my phone proceeds to boot, but stops at the LG logo. Tried removing the battery and start it up again, but same thing happens again, LG saying Error, lol in YOUR FACE to me, and gets locked in booting... Well, suppose i'll be without a phone for a few days...
hulkhaugen said:
Well thanks for your reply
I just found out something stupid. I don't have access to WiFi atm, nor 3g, so i downloaded ClockworkMOD.apk and recovery-clockwork-5.0.2.6-p970.img, figured i could install it manually. So i started CWM, and tapped Reboot into recovery...nope, should note have done that, lol. When it started up, i got a huge error label, with LG security error as a subtitle to that. Now my phone won't start. After that message, my phone proceeds to boot, but stops at the LG logo. Tried removing the battery and start it up again, but same thing happens again, LG saying Error, lol in YOUR FACE to me, and gets locked in booting... Well, suppose i'll be without a phone for a few days...
Click to expand...
Click to collapse
Ilko's package contained CWM I believe, installing via command with single click. Do you have a nandroid? Install v20a, chinese one via smartflash (no net connection needed). Install CWM (UPK) then restore nandroid.
Problem is if you don't have them. It's good to save these files for future troubleshooting.
Edit: my bad, sorry. You don't have CWM before. So no nandroid.
Nope, no nandroid. Recently unbricked my phone using LG software. My current internet connection is to slow to start up LGMobile update, lol. I'll be home in about 32 hrs (i hope, i'm far offshore atm). Guess i won't be able to do anything until then. I'll look into the framework-res.apk then, hehe. Merry x-mas
Thread moved
Questions belong here, not in development, until something is actually developed.
Do i need busybox?

[Q] how to permanently customize setting and appsq

I want to permanently customize setting and apps that stay even after factory resetting phone. so that when I*factory reset*my phone, it would revert back to*almost*factory settings, except with a few alterations. For example: some extra apps (maybe settings within those apps already selected), certain an!droid settings already selected (developer tools, unknown sources etc), superuser with permissions already granted for certain apps, basically things beyond the scope of just pre-installed apps.
I understand the phone would need to be rooted, I would want to keep the original rom with the above mentioned changes. Of course I can always make a backup and simply load it, but I want to know if it can be done through*factory reset. I only have experience rooting and loading custom roms (on many devices*, I've always done so since droid 1) but I have never made a custom rom, which from my understanding, is what I need to do to for something like this.*
Basically if you guys can tell me if I am in the right direction, completely off track and where should I go from here to make it happen.
Factory reset is a reset. Not a partial reset.
Everything you're looking for is accomplished with a nandroid backup. Which also "resets" your phone to the point the backup was created.
But to directly answer you ....no, I've never heard of a way to modify a factory reset. ?
jonagpa said:
I want to permanently customize setting and apps that stay even after factory resetting phone. so that when I*factory reset*my phone, it would revert back to*almost*factory settings, except with a few alterations. For example: some extra apps (maybe settings within those apps already selected), certain an!droid settings already selected (developer tools, unknown sources etc), superuser with permissions already granted for certain apps, basically things beyond the scope of just pre-installed apps.
I understand the phone would need to be rooted, I would want to keep the original rom with the above mentioned changes. Of course I can always make a backup and simply load it, but I want to know if it can be done through*factory reset. I only have experience rooting and loading custom roms (on many devices*, I've always done so since droid 1) but I have never made a custom rom, which from my understanding, is what I need to do to for something like this.*
Basically if you guys can tell me if I am in the right direction, completely off track and where should I go from here to make it happen.
Click to expand...
Click to collapse
That's exactly what you would need to do -- basically make your own stock-based rom. It will require an unlocked bootloader (not just root) - no way around this.
Good Luck
Edit: Keep in mind that OTA updates will absolutely not be possible. You would need to make a new stock-based rom built off the new SBF when a new updates comes out (assuming you want updates).
Your first step will be downloading and researching the SBF for your particular phone. Find the SBF files here:
sbf.droid-developers.org/phone.php?device=0
You'll need to find a guide on custom roms, and learn the procedures. Once you have succeeded and packaged up your rom with all the modifications you want, it will *absolutely* survive a "factory reset".
Additionally, KJ is correct. The 'nandroid' backup option in custom recovery makes this an extremely easy process (though it won't 'survive' a factory reset, it's easy enough to restore back assuming you saved the backup somewhere accessable). Building a ROM is considerably more involved. I personally wouldn't attempt it just for the convenience of having persistent apps and a few mods that survive resets.
Finally, if you are using Safestrap, or don't have a custom recovery, this is NOT possible.

[Q] How to fix a boot loop without a factory reset

I have googled this but all the solution I find are either to factory reset or re-flash your firmware. I'd really like to avoid that.
I have a Z3 compact, rooted and then flashed with the latest firmware I think its the .77 at the end.
Xposed framework with a few mods running beautifully on it.
The last 3 changes I did before the phone got stuck in the boot loop:
- updated minmin xposed module from 1.8.1 to 1.9
- updated another module but forgot its name
- fiddled with the settings of this app: https://play.google.com/store/apps/details?id=org.namelessrom.devicecontrol
I'm pretty sure its the latter as it sets certain kernel parameters at reboot.
Can anyone give me instructions on how to disable this app from booting or how/where to find it and delete it?
Where can I find logs of this boot loop?
I really want to avoid re-flashing, re-rooting, re-flashing and restoring my backup again as that will take half a day.
I've just brought back mine from bootlooping after I've installed several extensions (just discovered that the culprit was DonkeyGuard) and I'm about to do it for the second time, by flashing a Xposed-Disabler-Recovery.zip file that's stored either in the root of your phone or at
/storage/emulated/0/Android/data/de.robv.android.xposed.installer/files/Xposed-Disabler-Recovery.zip
But that would only work in case you messed it up with Xposed.
Thanks, I'll keep that in mind if I encounter this problem again.
Still finding it hard to believe there's no other reply to a seemingly common problem / question, does everyone just pack up and factory reset when boot looping?
Well, it's as common as people repeating to make a nandroid backup, you know
Btw, before I will flash yesterday a black theme (modded system files), I made the backup, so when my Z3C got stuck in a bootloop for the third time, I had nandroid ready. Such a shame, I really liked that mod.
If the kernel is problem, how about just reflashing your kernel?
Believe it or not, I started looking into nandroid backups today already made my first tests.
Until now I relied on titanium backups but that still makes me do a factory restore before I can restore stuff from those backups.
But the issue is, I am not looking for better "protection" I'm trying to find out how I can fix something minor like this i.e. via adb and command line...
Talking about a custom kernel, is there one? I have a rooted xperia z3 compact and wouldn't mind checking out a different kernel but I held back unlocking my bootloader until there is a custom ROM available that can fully replace my rooted stock ROM.
If love to get PAC man ROM for my phone.
I had the same issue, but by using 3C toolbox (similar to the app you've mentioned).
In my case putting back the original build.prop into /system via ADB fixed the bootloop.
As for custom kernel, you can try AndroPlus kernel HERE
@ovizii as @davebugyi said, you could always put some files back via ADB, but you need to have a file that you want to put back, like in davebugyi's case an original file. In your case you don't have it, so unless you know what value you changed, there is nothing much that you could really do with ADB access.
-V-O-Y-A-G-E-R- said:
@ovizii as @davebugyi said, you could always put some files back via ADB, but you need to have a file that you want to put back, like in davebugyi's case an original file. In your case you don't have it, so unless you know what value you changed, there is nothing much that you could really do with ADB access.
Click to expand...
Click to collapse
Hm, I was thinking along the lines of accessing log files, like a system log file, check what went wrong, i.e. auto start of a certain app, or setting of kernel parameters at boot time, then remove the offending apps/entries?
Just not sure if that's possible, hence this question here
Checking out the suggested ap and the kernel! Thanks!

LG Optimus L90 Root problems. HELP

Hello all. I Recently attempted rooting my phone, running on 5.0.2, and it seemed to have worked. But then after attempting to use SuperSU to add root permissions to an app, my screen went black, and the only thing visible was the top status bar, which had some animations still running (Like the battery icon filling up or the signal bars changing), but thats it. It wasn't responsive to any of my button presses, and then it shut off. It keeps doing this over and over, and i cant keep the phone on for more than 5 mins maybe 10. How would I fix this? I used this "tutorial". - andromods .com/news-root/lg-g3-g-flex-2-g2-lollipop-one-click.html - (Stupid thing wont let me post links)
I would like to solve this without factory resetting, as I have apps that have data on them that needs to be transferred from one phone to another, and i dont have a second phone to transfer to at the moment.
Thanks in advance.
As far as I know, flashing kdz with LG Flash Tool following the tutorial to "unroot" won't delete your data, but you will lose root, of course. If you don't have custom recovery nor root, there is little else you can do. Do you have adb root (shell)? If yes you can try re-flashing system partition...
lfom said:
As far as I know, flashing kdz with LG Flash Tool following the tutorial to "unroot" won't delete your data, but you will lose root, of course. If you don't have custom recovery nor root, there is little else you can do. Do you have adb root (shell)? If yes you can try re-flashing system partition...
Click to expand...
Click to collapse
I'm very new to this, and probably shouldnt have attempted this without knowing more, so I have no idea what you are asking me. What is ADB root (shell)? I probably dont have it. And I didnt do any sort of custom recovery. But it seems that me messing around with SuperSU (clicking the uninstall root/turning of superuser once or twice) seems to have stopped the crashing all together. Ive been using my phone since and it hasnt crashed. Whether or not that's fixed the real issue, I don't know. And I'm not sure I want to mess with it further. :crying:

Question How do you run an ADB command on a bootlooping device?

I have uninstalled a system app that I shouldn't have (something to do with network conectivity according to the recovery log) and everything was fine until I updated my device. I hadn't restarted it since removing the system app but after tyhe update it will no longer go past the Samsung galaxy logo. I remember doing something similar to either this device or another and I remember that I was abler to get into the system enough to be able to reinstall the neccessary app and fix the problem. However, this time I cannot get into adb at all. adb won't show any devices when in recovery, download mode, or at any of the three stages of the boot screen. I have tried wiping the cache and everything but factory resetting it as I have data that I can't lose. Any help would be appreciated whether getting adb install-existing to work or to pull important files off of the device before a reset. The device runs android 12 not rooted.
(...)
Go back via odin to the original firmware including the correct BIT.
(...)
Flash in Odin using home CSC file, simple
You only need to run ADB in Windows PC terminal or DOS mode in order to Odin flash firmware. No need to run ADB commands in the phone.
Just be sure that you install the "Samsung ADB Driver" into your PC before
you try Odin flashing firmware.
Just be sure you download the proper firmware for your phone.
Good luck, have a great day and have fun!
Thank you to all the help, but eventually I got into the phone. For anyone who may encounter a similar problem in the future:
After the phone reboots enough, it resets all preinstalled apps and removes any user installed ones and goes into safe mode. From here, the phone goes through the initial setup screens but all data is still intact, just not apps. Concerningly, it doesn't ask for you to enter your password, it just puts you on the homescreen, which seems bad from a privacy perspective as any samsung repair tech can easily cause the phone to boot loop. From here, you can back up anything important and factory reset. There is no way to exit safe mode once you've gotten this far.
I don't remember why odin didn't work, it may have been that I couldn't get the firmware to download as Samsung likes to change that stuff all the time or it may not have reinstalled the system app neccessary.
I should've been more clear in the original post but I have not flashed any unofficial firmware just the U1 firmware to remove carrier bloat, but that was way before this occurred. In case it wasn't clear, the problem happened because through
Code:
adb shell uninstall --user 0 package.name
an important system app was removed (something network related) which caused android to crash when trying to start the service. In short: be careful what you remove when using adb and, for all you forum members: read the whole post instead of jumping to conclusions about the user's mistake and if it isn't clear, ask for more details. Again, thank you to all the helpful comments even if they didn't end up working.
ZenDeveloper said:
Thank you to all the help, but eventually I got into the phone. For anyone who may encounter a similar problem in the future:
After the phone reboots enough, it resets all preinstalled apps and removes any user installed ones and goes into safe mode.
Click to expand...
Click to collapse
May I ask how long it took to "reboot enough"? I'm having issue updating to Android 13. It got into boot loop (the 2nd time actually. I mentioned about it in another thread a few weeks ago. Today I decided to try again). Anyway I am wondering if there's anyway I don't need to reset the whole thing. What you described interested me.
Thanks
hatoxda said:
May I ask how long it took to "reboot enough"? I'm having issue updating to Android 13. It got into boot loop (the 2nd time actually. I mentioned about it in another thread a few weeks ago. Today I decided to try again). Anyway I am wondering if there's anyway I don't need to reset the whole thing. What you described interested me.
Thanks
Click to expand...
Click to collapse
Sorry for the late reply,
I don't know how many times it needs to reboot to go into safe mode but it seemed like quite a bit maybe 20-30 times possibly like 100. But once it does it'll go through the initial setup screens and let you in without a password. It's very important to backup everything on your device before you mess with any system apps or update especially if you've previously messed with system apps. I however don't use google hence I didn't have a backup of anything and needed to get it off before hand.
It could also be possible that Samsung removed this back door in android 13 and just the act of trying to update it gets rid of it. I don't know I'm just throwing around ideas.
Rule #1 - if a OS is fast, stable and fulfilling its mission, let it be! Firmware upgrades/updates can and do break Samsung's.

Categories

Resources