Database Develop

No launcher

Hi all,
I have a Google Nexus One which I had rooted a couple of months back (just root and no boot loader unlock). Everything was fine and I had factory restored it successfully once in the due course.
The problem was when I did a factory reset again yesterday so that I can sell it, there was a boot loop. I tired everything like restart, stock restore again from recovery, battery removal but all went vain. Fortunately I tried connecting via USB and thus I escaped from boot loop but still I was stuck there. None of the 4 system keys didn't work.
I just sat researching on Google and at last got the reason for the strange behaviour on the otherwise 2 year old not a single glitch ever phone. The issue was the with the stock Launcher apk. Just then I remembered that I had uninstalled the stock Launcher given the root access and so confident on the Holo launcher.
Again some researches and I came to know I can install (or "push") the launcher using the 'adb' command. I booted into recovery console, connected my phone to Windows 7 PC and installed the driver to get the phone detected. But when I typed 'adb remount' it gives 'error: device not found'. This is where I'm stuck now and since Googling didn't provide anything worth I'm back to my favourite tech forum.
Hope you got it clear here and someone can help me.
Regards,
ursJAR
Sent from my Galaxy Nexus using xda app-developers app
PS: And why is typing on the xda android app so terribly slow??!

Stock recovery doesn't allow ADB access.
Since you did factory reset - ADB isn't running on the phone either.
So you can't recover from this situation without unlocking the bootloader. Unlock it, install custom recovery, adb push the launcher through it.
Forgot to mention - I'm not suggesting PASSIMG, since your phone is likely updated to the latest, and all the PASSIMG are from older builds. You could try, though - if you don't want to unlock the bootloader, Korean PASSIMG might be what you need. See N1 Wiki, section "Unroot/restore", PASSIMG method.

If the boot loader is unlocked, I believe there is no way to revert to the fresh situation.. right?
Sent from my Galaxy Nexus using xda app-developers app

Updating OTA to ICS was successful but root was lost and settings app is frozen.

Long time lurker, first time poster. I have the Droid Razr Maxx and I used Voodoo OTA Rootkeeper to update like a good boy from GB to ICS. So my phone is just fine.
My technologically daft friend has the Droid 4 which I rooted for him when it was running GB. In my absence he decided to freeze some things without consulting me using App Quarantine. He froze settings (like the one in red) among other things. When the OTA update for ICS came, instead of calling me (at which point I would have talked him through updating with Voodoo to keep root) he went ahead and updated. The update somehow did not fail and now he has ICS running but all the frozen apps he froze with App Quarantine are still frozen. I can't unfreeze them because he lost root in the update and I can't root the phone because I can't get into settings, or get the phone out of USB mass storage when I connect to PC (the option is there in the notification bar but when you tap it nothing happens). I tried using RSD Lite 5.7 to flash the latest Fastboot file for the Droid 4, it goes through the process successfully but when the phone reboots nothing has changed.
I'm looking for advice on how to unfreeze the apps frozen with App Quarantine without root access. Or how to root the Droid 4 running OTA ICS without being able to get to the setting menu or change out of USB mass storage mode. Or worst case scenario how to get it back to stock and start from scratch.

Use rsdlite to fastboot back to stock. Do a search in this forum, there are lots of instructions
Sent from my XT894 running ICS

danifunker said:
Use rsdlite to fastboot back to stock. Do a search in this forum, there are lots of instructions
Sent from my XT894 running ICS
Click to expand...
Click to collapse
The OP did say: " I tried using RSD Lite 5.7 to flash the latest Fastboot file for the Droid 4, it goes through the process successfully but when the phone reboots nothing has changed. "

silver6054 said:
The OP did say: " I tried using RSD Lite 5.7 to flash the latest Fastboot file for the Droid 4, it goes through the process successfully but when the phone reboots nothing has changed. "
Click to expand...
Click to collapse
Oops, missed that part. If that's the case, then a factory reset will do the trick. You can perform a factory reset in recovery, power off the device, then press and hold both volume rockers while pressing the power button, choose recovery. When recovery loads up, press both volume rockers simultaneously, then choose erase our wipe data. Another way might be to press posting the menu button on the home screen and choose manage apps. From there go to all apps, and locate the frozen settings app. I think the frozen apps are at the bottom. Good luck!
Sent from my Nexus 7 using Tapatalk 2

danifunker said:
Oops, missed that part. If that's the case, then a factory reset will do the trick. You can perform a factory reset in recovery, power off the device, then press and hold both volume rockers while pressing the power button, choose recovery. When recovery loads up, press both volume rockers simultaneously, then choose erase our wipe data. Another way might be to press posting the menu button on the home screen and choose manage apps. From there go to all apps, and locate the frozen settings app. I think the frozen apps are at the bottom. Good luck!
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I will see if I can create a shortcut on the homescreen first, but since settings itself is frozen I don't think it will load up no matter how I try to access it. I can't quite understand how he was able to use his phone without being able to get to settings, that is beyond me. I wish there was a method to root the phone without changing out of USB mass storage mode, that would effectively solve my (his) problem because then I could unfreeze everything. I know USB debugging is enabled. Anyway, he is coming over tonight after work and factory reset will most likely be the last (and only viable) resort.

Okay... I think I know where you're getting at... If you want to play with some other stuff, you can try doing adb shell then typing the following commands:
am start com.android.settings/.UsbSettings
this is the command to get to the settings menu, not sure of if will work if settings is disabled but it's worth a shot.
You can also try to get to the settings main menu by
am start com.android.settings
and the manage apps list is
am start com.android.settings/.Settings$ManageApplicationsActivity
all these am start commands need to be issued from an adb shell window.
Good luck!

danifunker said:
Okay... I think I know where you're getting at... If you want to play with some other stuff, you can try doing adb shell then typing the following commands:
am start com.android.settings/.UsbSettings
this is the command to get to the settings menu, not sure of if will work if settings is disabled but it's worth a shot.
You can also try to get to the settings main menu by
am start com.android.settings
and the manage apps list is
am start com.android.settings/.Settings$ManageApplicationsActivity
all these am start commands need to be issued from an adb shell window.
Good luck!
Click to expand...
Click to collapse
I couldn't get into settings no matter what I tried, had to do a factory reset. After that I rooted and installed Safestrap and Voodoo OTA Rootkeeper with the Droid 4 ICS Utility. And had a lesson with my friend on what never to freeze and to never update a rooted phone without consulting me or the internet first. All is well.

Im actually in the same boat... well, almost... i rooted GB used voodoo, temp unrooted so i can update to official 6.16.217... finally updated after 6 epic fails. i was stuck in a half root/ unroot phase where the su app was there and so was voodoo but root rights were gone and so was my root back up... i have tried using the droid 4 utility but all i get is errors. no matter what option i use, it doesnt do anything... usb debugging is on, set to camera, only one instance of adb is running, nothing works... i even tried z4root while in half root to see if maybe it would help... (which it didnt, figuered i would try) did a wipe and factory reset, nothing is still working. any ideas? does the utility only work on the ics leak and not the official ota?

[HELP] Moto X won't boot to OS after strange happenings...

Rooted, Bootloader unlocked, TWRP installed, Xposed Running. 5.0 - I did not yet update or press update ever, If I have ever accidentally allowed it to begin downloading I kill the download by deleting the file using SDMaid.
I got home, had problems with other devices, phone was on about 40% at this point. I remember hearing the phone reboot, I noticed it went into TWRP, which was strange, I restarted system > powered up > lockscreen > restart to twrp with no interaction. Phone is now getting low 21%ish. Fix permissions - because used to be the all out fix on my other devices.
Same thing again > straight into twrp.
I notice that some scripts have been ran in the twrp console. Something along the lines of Victara_en_US.zip Some red scripts I assume saying failed to update.
I assume the phone is now too low to power up.
It shows no sign of charging since leaving the last twrp reboot.
Green light in top speaker shows when attempting to power up with usb charger plugged in > nothing else happens.
With charger unplugged from phone I see my modified logo screen and the moto planet spinning before phone turns off completely. This process now repeats.
Anyone have any idea what the hell is wrong with my phone?
EDIT UPDATE:
Managed to get into the fastboot menu:
Battery Low (RED)
Device is UNLOCKED status code 3 (YELLOW)
Software status modified (YELLOW)
As normal aside from Battery...

THE-M1GHTY-BUKO said:
EDIT UPDATE:
Managed to get into the fastboot menu:
Battery Low (RED)
Device is UNLOCKED status code 3 (YELLOW)
Software status modified (YELLOW)
As normal aside from Battery...
Click to expand...
Click to collapse
Get your phone into TWRP and connect it to your charger and let it charge to at least 70% Use Advanced Wipe in TWRP, select Cache and wipe that. Then see if your phone will start normally. Somehow you have downloaded the update file and it is trying to run automatically. Since your phone is modified, the update fails (and nothing is updated or changed.) The update file is in /cache so wiping that should correct the problem. You should go ahead and update to the Stagefright patched version of your ROM so you aren't having to deny the factory update all the time.

mikeoswego said:
Get your phone into TWRP and connect it to your charger and let it charge to at least 70% Use Advanced Wipe in TWRP, select Cache and wipe that. Then see if your phone will start normally. Somehow you have downloaded the update file and it is trying to run automatically. Since your phone is modified, the update fails (and nothing is updated or changed.) The update file is in /cache so wiping that should correct the problem. You should go ahead and update to the Stagefright patched version of your ROM so you aren't having to deny the factory update all the time.
Click to expand...
Click to collapse
Attempting this now....
Phone still boots to a black screen. I don't understand why it would download the update let alone attempt to install it, I religiously deny the update. Also why would it have booted up normally then forced itself into TWRP? :S
What can I next? I dont mind wiping using fastboot as I managed to take all my files off the phone via twrp.

This happened to me a couple times but wiping the cache AND the dalvik cache fixed it. If it still doesn't work, I hope you have a backup because you are going to have to wipe the system and data next. Sometimes these updates like to link themselves to all the phone's partitions, and in that case you should wipe everything and restore your full system and data backup in recovery.

TyNote3Krill said:
This happened to me a couple times but wiping the cache AND the dalvik cache fixed it. If it still doesn't work, I hope you have a backup because you are going to have to wipe the system and data next. Sometimes these updates like to link themselves to all the phone's partitions, and in that case you should wipe everything and restore your full system and data backup in recovery.
Click to expand...
Click to collapse
I wiped both the first time I tried it :-/
I don't have a system backup as a far as I am aware, need to check main pc for something like that. I had a lot of trouble with no signal after changing my phone to x1095 so I could root it etc. Just hope I don't have the same trouble again. Can i reinstall the system through twrp? Or do I need to flash via fastboot?
Whats my best option, system files wise, for fixing this?

THE-M1GHTY-BUKO said:
I wiped both the first time I tried it :-/
I don't have a system backup as a far as I am aware, need to check main pc for something like that. I had a lot of trouble with no signal after changing my phone to x1095 so I could root it etc. Just hope I don't have the same trouble again. Can i reinstall the system through twrp? Or do I need to flash via fastboot?
Whats my best option, system files wise, for fixing this?
Click to expand...
Click to collapse
If you dont have a backup, at this point, I don't see any other options besides formatting your data or flashing the stock firmware. Of course, don't just take my word for it, but in the future just make sure you have a working backup available.

TyNote3Krill said:
If you dont have a backup, at this point, I don't see any other options besides formatting your data or flashing the stock firmware. Of course, don't just take my word for it, but in the future just make sure you have a working backup available.
Click to expand...
Click to collapse
Am I able to flash anything other than the stock 5.0? Last I checked I had converted whatever I had to the x1095. I remember everything being easier on other phones...

Yes, you can, just make sure you have the right file for the job. They are usually about 2 gigs, and they take forever to flash. Note that once you flash the file, your phone will be as if you just bought it from the store, but it always will boot if you have the corresponding build.

THE-M1GHTY-BUKO said:
Attempting this now....
Phone still boots to a black screen. I don't understand why it would download the update let alone attempt to install it, I religiously deny the update. Also why would it have booted up normally then forced itself into TWRP? :S
What can I next? I dont mind wiping using fastboot as I managed to take all my files off the phone via twrp.
Click to expand...
Click to collapse
In TWRP, make a backup now even though it may not be useful depending on what the problem is. Then, use advanced wipe in TWRP and wipe data. If the phone will boot now, something got corrupted in data and you'll just need to set your phone up again. If the problem continues, you'll have to flash your system image. How to do this varies with the model of your phone; some models have TWRP images, others need to use fastboot files. After you flash the new system image, you can either just continue to clean setup the phone, or you can try to restore only data from the backup you made previously.

TyNote3Krill said:
Yes, you can, just make sure you have the right file for the job. They are usually about 2 gigs, and they take forever to flash. Note that once you flash the file, your phone will be as if you just bought it from the store, but it always will boot if you have the corresponding build.
Click to expand...
Click to collapse
Does that include 5.1 roms? I can never seem to find x1095 5.1 roms, or anything for that matter, they are all titled with every other version.

mikeoswego said:
In TWRP, make a backup now even though it may not be useful depending on what the problem is. Then, use advanced wipe in TWRP and wipe data. If the phone will boot now, something got corrupted in data and you'll just need to set your phone up again. If the problem continues, you'll have to flash your system image. How to do this varies with the model of your phone; some models have TWRP images, others need to use fastboot files. After you flash the new system image, you can either just continue to clean setup the phone, or you can try to restore only data from the backup you made previously.
Click to expand...
Click to collapse
I tried wiping data to no avail.
Im trying to download stock 5.0 for now but the download is taking decades for some reason. Do you, or anyone else, recommend any roms which I can easily flash without having to worry about modem files?

THE-M1GHTY-BUKO said:
Does that include 5.1 roms? I can never seem to find x1095 5.1 roms, or anything for that matter, they are all titled with every other version.
Click to expand...
Click to collapse
Hopefully this could provide more information for your situation?
http://forum.xda-developers.com/moto-x-2014/development/rom-xt1095-flashable-stock-rom-t3185945

Thank you for your help, as well as anyone else who helped me. I now have a running phone on 5.1.
How do I gain root from here? My superuser app updated and now tells me I have no binary, despite telling me to flash something only 5 minutes prior.
Sent from my XT1095 using XDA Free mobile app

So you don't have root? I would suggest rooting using towelroot. Go online and search "towelroot" click on the first result, click on the lambda to download the apk, and install it. You can then open the app, and press "make it ra1n" to root your device without any reboot needed.

I had root prior to wiping and installing the 5.1 update that was linked to me. Towelroot gives me the phone not supported message.
Sent from my XT1095 using XDA Free mobile app

Towel root does not work in 5.1.
To root just flash TWRP. Start TWRP. When you exit TWRP it will ask you if you want to root it. Simple.
Sent from my XT1095 using Tapatalk

I'm still in the "phone not responding" phase.. how did you manage to get in the bootloader from there? Tnx!

I found a chainfire autoroot IMG that rooted my phone. Found xposed too. I'm back at a fully working phone now, thank you to all who helped me.
Gotta say, the battery life on 5.1 is a hell of a lot better.
Sent from my XT1095 using XDA Free mobile app

As in you can't get it to fastboot?
I left it to charge for a while, then took about 5 minutes attempting the power button volume button combo to restart and get it into fastboot.
I believe that it's something like:
Power + vol down until the phone screen flashes/green light goes off
Then
Still holding the power and volume down
Hold the vol up too
Then release the power still holding the vol up and down.
That's what worked for me. It's literally the most awkward phone I've had go button combos.
I think vol up from powered off works too.
If you mess up just hold the power and vol down again.
Sent from my XT1095 using XDA Free mobile app

Question After installing TWRP for Android N Bluetooth Adaptive light

So i was running great on developer preview 5. then i installed TWRP after months, just in case. you never know. after installing TWRP Bluetooth hangs it takes about ten minutes to turn on. i used wugfresh to install twrp. also my adaptive lighting goes bonkers, it'll start off way bright when i unlock my screen and take forever to go back to normal. i tried to clear data in bluetooth share app. also tried to do network reset. and restart and all three at once. no avail. i then just restored my phone to factory. everything works great. i then install TWRP from wugfresh and again have the problem. anyone have a good fix?

zmedhaug said:
So i was running great on developer preview 5. then i installed TWRP after months, just in case. you never know. after installing TWRP Bluetooth hangs it takes about ten minutes to turn on. i used wugfresh to install twrp. also my adaptive lighting goes bonkers, it'll start off way bright when i unlock my screen and take forever to go back to normal. i tried to clear data in bluetooth share app. also tried to do network reset. and restart and all three at once. no avail. i then just restored my phone to factory. everything works great. i then install TWRP from wugfresh and again have the problem. anyone have a good fix?
Click to expand...
Click to collapse
Installing TWRP shouldn't cause those issues but I would suggest installing TWRP using Fastboot. Instructions found here under the section titled "Fastboot Install Method (No Root Required):"

alryder said:
Installing TWRP shouldn't cause those issues but I would suggest installing TWRP using Fastboot. Instructions found here under the section titled "Fastboot Install Method (No Root Required):"
Click to expand...
Click to collapse
After wording it differently in Google, I have found that it's a known bug with no work around currently. It's random. Installing TWRP I think was a coincidence
Sent from my Nexus 6 using Tapatalk

Rooting Samsung Galaxy Tablet E (8.0) SM-T377V Please Help

So I've had success rooting the SM-T377V thanks to electronhacker post on the forums.
I thought I would give my experience because anyone else doing this will most likely run into the same problems I did. I still have a few problems I am running into. I hope someone can help me out.
electronhacker had said to downgrade to stock firmware LMY47X.T377VVRU1AOL7 (5.1.1) Lollipop, from firmware MMB29K.T377VVRS1BPL1 (6.0.1) Marshmallow using Odin.
I ran into problems finding LMY47X.T377VVRU1AOL7 but I eventually did find it on samsung-firmware.org Thank you moonsh0t!
It did actually work and passed with Odin, however it got stuck in a bootloop. I thought there was nothing that could be done but after looking into the bootloop matter more I figured out how to get out of it and start it up.
1.) Wait for the device to turn off while it's bootlooping.
2.) Then hold down the power button and the volume up buttons to enter recovery mode.
3.) Restore factory defaults. "I think this actually gave me an error but clearing the cache got it to work."
4.) Clear the cache.
5.) Reboot the device.
There you have it now you're out of your bootloop, the device will start up now.
Now that we have downgraded electronhacker had said to run a program called Kingoroot using the Windows application.
I ran Kingoroot and it got stuck at 44% and my screen went black and would not come on or turn off. I am pretty sure you call this a soft brick, but maybe it's called hard brick as there was nothing that could be done.
So this is what I did to Unbrick the tablet:
1.) Hold the power button and the volume down button for 15 to 30 seconds.
2.) The screen should come back on.
3.) Scroll through settings to reboot device normally.
I tried to use Kingoroot again. This time it got stuck at 51% and my screen on the tablet got stuck. Nothing was responding, not the power buttons, the volume buttons, home button, nor the screen. This is because Google Application had showed up on the tablet while I was in the middle of rooting. The Google Application said "Do you want to enable Google Security?".
Again;
1.) Hold the power button and the volume down button for 15 to 30 seconds.
2.) The screen should come back on.
3.) Scroll through settings to reboot device normally.
The device booted normally and I tried Kingoroot again. I wasn't going to give up. This time it worked, 100% Root Successful. I couldn't believe it the SM-T377V was rooted. I checked and verified with Root Checker.
Now this is where I need help!
#1.) The device only stays rooted until you restart it. Then you have to Re-Root it with Kingoroot every time you restart. I found out if you run SuperSu and go into setting you can stop this from happening. I'm not exactly sure what you do yet because I can NOT get into SuperSu. It tried to install the binaries but gets interrupted by Knox. It says disable Knox on SuperSu but this does NOT work. This tablet does NOT have a way to open Knox in order to disable it. So I need to figure out how to delete it that way I can run SuperSu and stop the never ending root process. So if someone could help me figure out how to do that I would very much appreciate it.
So far I've figured out that you can run an application called Titanium Backup to freeze the Knox files and then remove them followed by a Re-Boot to get rid of Knox. I looked further into my SuperSu problems and found out that you can manually download a SuperSu.apk file that should bypass Knox and actually disable it.
Here is my new problem, installed Titanium Backup from Google Play Store only to find out that I can't freeze the Knox settings unless I pay the $5.99 for Titanium Backup Pro. So I removed Titanium Backup and downloaded Titanium Backup Pro.apk which I found for free on the internet. I can NOT install it though, because I have a new error that says "APP not installed".
This happens with the SuperSu.apk that I found on the internet too. I've tried a lot of things but can't get them to install. Google Play Store gives me error (-504) I've tried clearing cache and data for Google Play Store and Google Play Services but no luck. I even tried downloading APK Installer but it doesn't even work. Please help I don't know what to do.
02-09-2017
<UPDATE>
I'm at a loss, so I decided to do a factory reset from settings and that did not get the applications to install. So then I tried to clear the cache but again no suck luck. Then I decided to enter recovery mode and factory reset, but then got stuck on "Your tablet is getting ready for you". or something along the lines of that and wouldn't get past that on start up. (This is because I disabled setup with another application, and is my fault.) Not being able to get past that I realized I had no choice but to Re-Flash the System Update LMY47X.T377VVRU1AOL7 (5.1.1) Lollipop with Odin and that was successful, thank God. Now I have to Re-Root and before installing the wrong applications, which are Google Play Store SuperSu and Titanium Backup. Reason being that once you install these once and uninstall them you can't install them again without getting error (-504) in Google Play Store or even outside the Google Play Store such as manually downloaded .APK files or you will get the error "APP not installed".
Here is my idea, and I haven't done it yet. Re-Flash, Re-Root, Install for the FIRST time the right SuperSu.apk and Titanium Backup Pro.apk in order to disable Knox and stop the never ending Re-Root every time the tablet it restarted.
02-10-2017
<UPDATE>
I have been running Kingoroot with my PC using USB. This gives me temporary Root access until Re-Boot. So I installed Kingoroot.apk and tried using to mobile application but this one works, but I get stuck in bootloop on restart of tablet. Then have to Re-Flash with Odin to get out of bootloop. I'm not having any luck.
#2.) Even with my temporary root I can not seem to install Xposed because of SDK 22 not supported. I was wondering if anyone knows a way to get it to work on SDK 22 so I can run IMEI Changer. Unless there is another way to change the IMEI without Xposed.
Thank you to electronhacker for your post I found on this forum which has made me a lot of progress, and thank you moonsh0t for your help redirecting me to find that firmware. :good:

I just got a SM-T377V this weekend and have been trying o root it as well. Wow seems like nobody has had any luck getting a reliable root on it. Please update me as you keep at it! Brent your attempts at this are amazing!! Keep at it!

I'm trying to get this thing rooted too, so please keep me updated if you find a
Way!! Thanks for your help!

Yep
Ok

Same issues here. I never have trouble rooting with the APK, but its super annoying having to reroot all the time. also the superuser app is absolute cancer so learning to replace that would be dope.

Alright, so your goal is to run an IMEI changer, but why?
Also my luck was to get it temped root and try and use chainfire's supersu to take over.
from there I tried unlocking the bootloader with samdunk. The issue though, is the CID was deleted from the tablet, so when I restarted, never ending bootloops.
I just Odin'd it back to the AOL firmware today, will look more into samdunk later.

Treyday645 said:
Same issues here. I never have trouble rooting with the APK, but its super annoying having to reroot all the time. also the superuser app is absolute cancer so learning to replace that would be dope.
Click to expand...
Click to collapse
If you use Odin to flash android 5.1.1 via package T377VVRU1AOL7, you can use the kingroot or kingoroot app (desktop or android) to temporarily root the device. From there, if you delete the kingroot or kingoroot app from the device you can use SuperSu to take the binary over. From there you can use any flashing apps you'd like.
The issue is at this point, the second the device turns off, when it comes back it will no longer have root. (note so far in my attempts I've found that Kingroot, will reboot rootless, whereas kingoroot will bootloop.)
Kingoroot will bootloop because it modifies the boot file in some way, which causes the bootlooping. The work around to this is just flashing over the previous android. However, if you flash with Odin, you lose root, but keep your files.
Going back to flashing, when you attempt to use Odin to flash other packages, they are denied, due to the locked bootloader, however, you can use Flashfire to flash these firmwares. I attempted to flash the T-377P firmware and bootloader. Obviously the locked bootloader stayed locked, the recovery partition got errored out, but the android system itself actually started. Just sans root.
It's worth noting I've also attempted using SamDunk, the S5 bootloader unlocking tool, and so far all I've noticed is it deletes the CID file and doesn't finish. So I'm of the impression that the temp root, isn't a full root either.