Database Develop

Update 4.2 failet with trinity kernel

Please help, my nexus was unlocked rooted with trinity kernel. When i pushed update, my tablet restarted with clockwokmod and failed to update
to 4.2. i believed it was because of custom kernel so i then flashed to stock factory, and re locked using nexus toolkit.
When i go to setting for update, it's showing me that my system is up to date 4.1.2. I don't understand. I thought flashing it back to stock factory will solve the problem.
Thanks a lot in advance for you hep

diamondx911 said:
Please help, my nexus was unlocked rooted with trinity kernel. When i pushed update, my tablet restarted with clockwokmod and failed to update
to 4.2. i believed it was because of custom kernel so i then flashed to stock factory, and re locked using nexus toolkit.
When i go to setting for update, it's showing me that my system is up to date 4.1.2. I don't understand. I thought flashing it back to stock factory will solve the problem.
Thanks a lot in advance for you hep
Click to expand...
Click to collapse
1) If you are using a custom kernel and/or custom recovery and/or removed/froze required system apks and/or modified build.prop and/or have a dozen other "custom" things, then the OTA update will NOT work. Period. You need to revert ALL of that. Stock kernel, recovery, system apks, build.prop, etc. Because if any of those aren't stock, the install will abort.
2) Having root is irrelevant. The update will remove suid access on the binary, so you will need to "re-root", but the binaries presence is irrelevant.
3) If it failed the OTA update, it won't download it again right away. Your best bet is to download the file and try to flash manually in a custom recovery (which will work as long as everything else is stock).
4) Did you say you relocked the tablet? If so, why? That was NOT required, and you just f*cked yourself, because you won't be able to flash a custom recovery back without unlocking the bootloader again, which will wipe your sdcard. There is NO reason to relock unless you are returning the device.
5) Again, this is why I hate toolkits. Learn to do things manually and you will be much better off.
At this point, assuming you relocked the bootloader, you will probably need to do a full factory reset and unlock it again. Then flash custom recovery and then flash the update. Or, since it would have been reset at that point, just download the full image from Google and flash that, then flash custom recovery.

phonic said:
1) If you are using a custom kernel and/or custom recovery and/or removed/froze required system apks and/or modified build.prop and/or have a dozen other "custom" things, then the OTA update will NOT work. Period. You need to revert ALL of that. Stock kernel, recovery, system apks, build.prop, etc. Because if any of those aren't stock, the install will abort.
2) Having root is irrelevant. The update will remove suid access on the binary, so you will need to "re-root", but the binaries presence is irrelevant.
3) If it failed the OTA update, it won't download it again right away. Your best bet is to download the file and try to flash manually in a custom recovery (which will work as long as everything else is stock).
4) Did you say you relocked the tablet? If so, why? That was NOT required, and you just f*cked yourself, because you won't be able to flash a custom recovery back without unlocking the bootloader again, which will wipe your sdcard. There is NO reason to relock unless you are returning the device.
5) Again, this is why I hate toolkits. Learn to do things manually and you will be much better off.
At this point, assuming you relocked the bootloader, you will probably need to do a full factory reset and unlock it again. Then flash custom recovery and then flash the update. Or, since it would have been reset at that point, just download the full image from Google and flash that, then flash custom recovery.
Click to expand...
Click to collapse
Haha, thanks for answering... the update came back by itself.
I was not aware of anything when i unlocked and rooted my nexus. please bare with me. I'm new to the android scene. but i'm very familiar with the hacking tool, i hacked and unlocked everything i own in my house, from 3 iphones, to my psp , xbox, ps3 and psp. when i first got my hand on the nexus i saw some dead black line of pixel that was appearing for half a second, after i read that a custom kernel can fix it,
I just did it fast and was not in a mood to start learning that sh*t from scratch. so now i'm on 4.2 , i know i lost everything. i will just have to unlock again and and root it....

diamondx911 said:
Haha, thanks for answering... the update came back by itself.
I was not aware of anything when i unlocked and rooted my nexus. please bare with me. I'm new to the android scene. but i'm very familiar with the hacking tool, i hacked and unlocked everything i own in my house, from 3 iphones, to my psp , xbox, ps3 and psp. when i first got my hand on the nexus i saw some dead black line of pixel that was appearing for half a second, after i read that a custom kernel can fix it,
I just did it fast and was not in a mood to start learning that sh*t from scratch. so now i'm on 4.2 , i know i lost everything. i will just have to unlock again and and root it....
Click to expand...
Click to collapse
Understood, and "hacking" android, especially Google devices, is pretty easy once you know what you are doing. The reason I dislike toolkits is that it prevents people from understanding the process, which really is fairly easy to understand, and can complicate troubleshooting steps.
The bootloader can easily be unlocked and locked. It takes one command and it's done. In order to flash anything with fastboot, you need it to be unlocked. The problem is, when you do this, it factory resets the device. So if you inadvertantly relock it, your going to need to reset it to unlock it again.
Even without the toolkit, going from unopened stock Nexus7 to fully rooted, updated and custom firmware Nexus7 only takes maybe 10 minutes, and 9 minutes of that is waiting for it to finish doing the various steps (flashing, rebooting, etc.). The most time consuming part is, unless you have good backups, restoring all your apps and settings. Titanium Backup is the best tool (IMHO) for that.
But yeah, in this case, you're going to need to unlock/wipe again. However, you CAN backup your "sdcard" to your computer and push the files back to it after the wipe. That can be very time consuming depending on how much you have.

Confused about my current Moto X's root and write protection situation

I'll admit, I didn't fully understand the root process back when I did this. I don't even remember all the steps I took. I got a locked Verizon (black 16GB) for an upgrade back in March. I always wanted this phone but never had an upgrade available. Well I forgot they had a Dev model out and stupidly got the free one with a new contract renewal.
I am running android 4.4 KK and am currently rooted with Xposed installed. I'm pretty sure the only way I can have write protection disabled is by booting into recovery, correct? Even though I select recovery at the fastboot screen, it just boots like normal. I guess my question is, is there any reason for me to be booting into recovery every time? Is there a way to tell if I have WP disabled on /system and root after a normal boot process? I swear I've had Xposed stop working after a normal boot.
EDIT: I'm seriously considering swapping this out for a new Dev model if they go on sale. I could use the extra storage and can easily just unlock the bootloarder and have root when L comes out for the first gen X.

IEcansuckit said:
I'll admit, I didn't fully understand the root process back when I did this. I don't even remember all the steps I took. I got a locked Verizon (black 16GB) for an upgrade back in March. I always wanted this phone but never had an upgrade available. Well I forgot they had a Dev model out and stupidly got the free one with a new contract renewal.
I am running android 4.4 KK and am currently rooted with Xposed installed. I'm pretty sure the only way I can have write protection disabled is by booting into recovery, correct? Even though I select recovery at the fastboot screen, it just boots like normal. I guess my question is, is there any reason for me to be booting into recovery every time? Is there a way to tell if I have WP disabled on /system and root after a normal boot process? I swear I've had Xposed stop working after a normal boot.
EDIT: I'm seriously considering swapping this out for a new Dev model if they go on sale. I could use the extra storage and can easily just unlock the bootloarder and have root when L comes out for the first gen X.
Click to expand...
Click to collapse
You can try installing something as a system app (App Ops for Root comes to mind https://play.google.com/store/apps/details?id=droidmate.appopsinstaller&hl=en) and see if it works. If it does, than write protection is off. The app on Play store is actually an installer that will put App Ops into your /system folder. If you have Xposed working properly, it might be OK already.
I remember when I rooted my VZW Moto Maker Edition on 4.2.2 (I think) I used SlapMyMoto and MotoWPNoMo (or something weird like that). I ran both and then installed Xposed and the framework failed to install properly (the version numbers in the app were red). I tried a few times and it didn't work. I ran the WP script a second time then Xposed worked fine. I must have missed a step in the WP off procedure.
If you boot normally and Xposed doesn't work, or you can't install to /system then I'd say you don't have WP off when booting normally.

fury683 said:
You can try installing something as a system app (App Ops for Root comes to mind https://play.google.com/store/apps/details?id=droidmate.appopsinstaller&hl=en) and see if it works. If it does, than write protection is off. The app on Play store is actually an installer that will put App Ops into your /system folder. If you have Xposed working properly, it might be OK already.
I remember when I rooted my VZW Moto Maker Edition on 4.2.2 (I think) I used SlapMyMoto and MotoWPNoMo (or something weird like that). I ran both and then installed Xposed and the framework failed to install properly (the version numbers in the app were red). I tried a few times and it didn't work. I ran the WP script a second time then Xposed worked fine. I must have missed a step in the WP off procedure.
If you boot normally and Xposed doesn't work, or you can't install to /system then I'd say you don't have WP off when booting normally.
Click to expand...
Click to collapse
Ok, I installed what you suggested, went into the app and tapped the "Install AppOps Root" button. It asked for root access and then rebooted my phone. So I guess this means that by default on a normal reboot, I have WP disabled and root access? Thanks for help clearing this up! I guess the phone was just acting weird that one time when the Xposed modules wouldn't work.
One last question, is there a reason why I can't get to recovery? Whenever I reboot into Recovery, it just starts up like normal? Is that because the normal recovery has been overwritten by a custom one in the root process?

IEcansuckit said:
Ok, I installed what you suggested, went into the app and tapped the "Install AppOps Root" button. It asked for root access and then rebooted my phone. So I guess this means that by default on a normal reboot, I have WP disabled and root access? Thanks for help clearing this up! I guess the phone was just acting weird that one time when the Xposed modules wouldn't work.
One last question, is there a reason why I can't get to recovery? Whenever I reboot into Recovery, it just starts up like normal? Is that because the normal recovery has been overwritten by a custom one in the root process?
Click to expand...
Click to collapse
If your bootloader isn't unlocked I don't think you can change recovery. You may be able to reflash the stock recovery from fastboot/mfastboot for your proper version, but don't quote me on that.
Someone with more experience can chime in. How are you rebooting to recovery? With an app/button, or via fastboot?

fury683 said:
If your bootloader isn't unlocked I don't think you can change recovery. You may be able to reflash the stock recovery from fastboot/mfastboot for your proper version, but don't quote me on that.
Someone with more experience can chime in. How are you rebooting to recovery? With an app/button, or via fastboot?
Click to expand...
Click to collapse
Correct. No unlock - no custom recovery.
It also depends on which method you used to achieve wp-off. Is rather not get into the finer details because it's really not important...

Are you using VOL+ to select recovery in the bootloader?
Edit: yes, when you rooted your phone, the stock recovery was overwritten to give you Android with write protection off. Looks like normal Android, but you have write access to system.

[Q] Need Help with cusotm recovery and root

I just bought the developer edition for verizon. I unlocked the bootloader successfully, i installed twrp is cmd and it said it installed successfully. I did not, however, open twrp immediately, which may be the problem. because if i go into download mode and click on recovery, nothing happens, my phone just goes black, like it powers off.
I tried opening cmd window again and installing again, only now the cmd window says the device is not connected, even though it is, or says it can't load the file. and ive tried twrp and cwm.
Is it because when i got the phone it was already on 4.4.4?

cnoevl21 said:
I just bought the developer edition for verizon. I unlocked the bootloader successfully, i installed twrp is cmd and it said it installed successfully. I did not, however, open twrp immediately, which may be the problem. because if i go into download mode and click on recovery, nothing happens, my phone just goes black, like it powers off.
I tried opening cmd window again and installing again, only now the cmd window says the device is not connected, even though it is, or says it can't load the file. and ive tried twrp and cwm.
Is it because when i got the phone it was already on 4.4.4?
Click to expand...
Click to collapse
no that does not matter because you are able to unlock your bootloader so android version dose not matter.
when installing your recovery you are running the CMD commands with your phone in bootloader mode correct.
if you are in bootloader mode and still having issues here are a couple things you can try.
1. Restart the phone
2. try a different USB port
3. restart ADB
4. Check drivers
you already know this but once you flash your recovery make sure you boot into the recovery before booting back into android.
if you get it installed Root is simple just download the SuperSU flashable zip and flash it via your custom recovery.
lmk if you are still having issues and we will look into other issues

thanks!
I ended up deleting everything (adb, sdk, fastboot, etc) and redownloading everything. So that got me able to install twrp, but when i tried to boot into recovery it would turn off the phone. Then I realized that in download mode you scroll down to recovery, then hit vol up to select. I am coming from galaxy nexus where the power button is select. So was i figured this out, i got into twrp and installed superuser, so i am rooted now. Time to find a 4.4.4 rom (may have to wait for a stable one since its pretty new) so i can get rid of all this bloatware. I can freeze some of it in titanium, but a lot of it I'm not sure what it does, again, Ive been on samsung for the past 5 years lol. Thanks again for the help.

4.4.4 isn't new. If you want all the Motorola features, stick with a stock-based rom or stock. I prefer stock with Xposed.

Being on vzw, I would recommend Krypton. It's based off the Verizon image and has a lot of bloatware removed. Xposed will get you about all the customizations you might want past that.

i was looking in the 'Original' development section an saw mostly 442 roms so i assumed 444 was new and didnt have stable roms yet, but now i know where to look and will probably try the krypton rom. gna have to look into xposed and learn what its about since i never used it before.

cnoevl21 said:
i was looking in the 'Original' development section an saw mostly 442 roms so i assumed 444 was new and didnt have stable roms yet, but now i know where to look and will probably try the krypton rom. gna have to look into xposed and learn what its about since i never used it before.
Click to expand...
Click to collapse
Right now Android L or 5.0 Roms are New and buggy. Most 4.4.2 and 4.4.4 roms are stable.
Me personally i like Stock with Xposed and gravity box installed, then i use Titanium Backup there is a battery thread somewhere that list what can and can't be removed. just be careful what you remove or you will end up like me with no active display but everything else about my phone is perfect so i dont want to go back to stock and redo everything.
after xposed and TBU i normally find a launcher i like, then maybe a lock screen but i think i ended up with stock. then i find a Text MSG app i like and other little add-ons to make my phone just for me.
here us a list of what i am running on my Stock Sprint 4.4.4\
LockScreen - Stock but tweaked with GravityBox
Launcher - Google Now Launcher
Text App - Google's Messenger App
Gesture Shortcut Menu - Lazy Swipe( i just found this app about a week ago and so far i love it, it allows me to have a very clean homescreen)
everything else changed on my phone is done threw Xposed and gravity Box.
Here are some App's you might want to check out.
AirDroid
Google Calender(if you use a calendar)
Google Keyboard(my keyboard of choice)
GSam Battery Monitor
Lazy Swipe(listed above)
Lucky Patcher(for thous pesky trial apps)
Pushbullet( alternative app for transferring all kinds of files to and from your device)
Zedge(ringtones and wallpapers)
I also attached some screenshots nothing fancy like i said but i love it and its perfect for me
The first one is my lockscreen, second one is my launcher homescreen, Third one is Lazy Swipe just one of the three tabs.
anyways hope this helps get you started post your setup once you get everything set up to your liking
Good Luck

what is that clock/weather widget? Thats pretty sick

http://forum.xda-developers.com/moto-x/themes-apps/droid-turbo-circle-widget-moto-x-t2941506

nhizzat said:
http://forum.xda-developers.com/moto-x/themes-apps/droid-turbo-circle-widget-moto-x-t2941506
Click to expand...
Click to collapse
yup that is correct enjoy

error while flashing recovry in cmd ....
I have already unlock bootloader successfuly... But when i try to flash custome recovery in fastboot mode with cmd it shows error....
I have tried on different laptops but same ....
Already instlall all drivers ...
Pls help me what to do......!!

commuditi said:
I have already unlock bootloader successfuly... But when i try to flash custome recovery in fastboot mode with cmd it shows error....
I have tried on different laptops but same ....
Already instlall all drivers ...
Pls help me what to do......!!
Click to expand...
Click to collapse
well first thing when u are posting for help you need to include more info. Like for starters what error are you getting so we can figure out what you are doing wrong. post your error and we will go from there.
Thanks

ATT nexus 6 questions

Couldn't find much about this varient just wanted to ask a few questions.
1. Do I treat it like every other google play nexus? Unlock boot loader, flash twrp, boot, backup, reboot, wipe, install ROM? No different partition weirdness?
2. Cm12, are the hotspot checks removed? Fiance is limited data plan I'm not so while out she normally uses my data via hotspot.
3. Cm12 have notification light activated and customizable?
Don't really care about the Sim lock honestly. Been with ATT forever and poor so not leaving the country anytime soon.
Thanks, sorry for repeat questions just didn't get solid answers from things I found.

No partition weirdness. Root as normal. It does have its own boot logo-thing though, which is lame.
Unfortunately I don't know about CM12. Sorry

squattingdonkey said:
No partition weirdness. Root as normal. It does have its own boot logo-thing though, which is lame.
Unfortunately I don't know about CM12. Sorry
Click to expand...
Click to collapse
At least you answered my bricking level question! Thanks!

CM 12 does have working hot spot on AT&T and customizable notification light. And, boot logo is easily removed after root.

Somehow I soft bricked my n6. I unlocked boot loader, installed twrp, went to backup and it couldn't find any partitions. Tried the flash all script from google factory image and that failed as well. Had to flash boot radio recovery etc images each manually to get back to a booting phone. Then installed twrp again and backup and flashing worked.
It was an adventure but I'm good now. Weird not sure why it did that. Must have been an encryption issue.

On the stock ROM you have to tick a box in developer options to enable OEM unlock. I forgot to mention that earlier. That may have been the issue.

ajjames01 said:
On the stock ROM you have to tick a box in developer options to enable OEM unlock. I forgot to mention that earlier. That may have been the issue.
Click to expand...
Click to collapse
Oops yeah that may have been it. I just did the usual fastboot OEM unlock code. Mild panic attack but when I saw I could get to the bootloader I knew I could save it.

Moto X always boots into recovery unless I manually choose normal startup each time

I rooted my XT1052 straight after updating to 5.1, a few years back. As a result I have never been able to install the OTA update (the one which fixed Stagefright, so far as I'm aware it's the only OTA Moto did after the 5.1 update.)
I've been unable to install a few apps recently due to SafetyCheck failing on the rooted phone, so yesterday I decided I would unroot and return to stock, which would also enable me to install the bugfix OTA. (And with Magisk, nowadays we can keep root access without a modified system partition.)
I didn't have a stock image (or I had an image of some sort on a hard drive but couldn't remember its provenance). Moto's download page has images for the XT1053 but not the XT1052… Eventually I found firmware.center, where (I thought) I found the right image.
However, when flashed it (following the step-by-step guides which are the same on various pages, including Moto's own instructions), it failed to flash the `system` image. I got messages about invalid block sizes (IIRC) and then an error saying the image was corrupt (it wasn't; I checked the MD5).
This left me unable to boot. So I downloaded LineageOS (I'd been considering switching to LineageOS anyway to get Android 6), and was able to flash it from TWRP without any issues (other than the fact that a newer version of TWRP is required than the one published on their website…)
All well and good – except that now, when I turn my phone on it goes straight into Recovery (TWRP). Initially I could only get System to boot by starting the bootloader (Pwr+VolDn) and selecting 'BP Tools', which would cause it to boot normally. (I found this by trial and error.) Now, after re-flashing the boot image, It also works if I select Standard Boot from the bootloader. But I still have to select it manually. If I just turn the phone on normally, with the power button, it always boots into Recovery. Also, all the 'reboot' options from fastboot/adb or TWRP all boot to Recovery.
Now, I think I know what I did wrong. The stock image I downloaded was 'XT1052_GHOST_RETGB_5.1_LPAS23.12-15.5-1_cid7_CFC.xml.zip', but my system version before was 5.1_LPA23.12-15.5. I just assumed that the 5.1_LPAS23.12-15.5-1 version was a minor update – likely with the Stagefright OTA installed – so I went for that. But probably I should have gone for the exact version I already had installed.
Searching these forums and the wider web, I haven't found anyone with the exact same issue. But from similar issues, I decided I needed to re-flash the partition table (gpt.bin). I took the gpt.bin image from an older 5.1 ghost ROM I had saved, but I'm not able to flash it – the bootloader shows security warnings when I try.
So I'm stuck now – I have tried pretty much everything I can think of.
If anyone has any ideas I'd be very grateful!

I have the same problem, my moto x only boot in recovery mode.
Did you get any solutions?

Alexjrbr said:
I have the same problem, my moto x only boot in recovery mode.
Did you get any solutions?
Click to expand...
Click to collapse
No :'(
I think our phone is old enough now that not enough people use it any more to find solutions to problems like these.
It's sad, I don't want to upgrade, I've never seen a phone I like as much as my Moto X.

cmjs said:
No :'(
I think our phone is old enough now that not enough people use it any more to find solutions to problems like these.
It's sad, I don't want to upgrade, I've never seen a phone I like as much as my Moto X.
Click to expand...
Click to collapse
I found a solution!
I did mine and now it's all right! I'll post here explaining how it should be done

Alexjrbr said:
I found a solution!
I did mine and now it's all right! I'll post here explaining how it should be done
Click to expand...
Click to collapse
Woohoo! Well done!
Look forward to seeing your solution

cmjs said:
Woohoo! Well done!
Look forward to seeing your solution
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-x/general/guide-fix-moto-x-boots-recovery-t3699644

Moto X 2014 XT1092
Alexjrbr said:
https://forum.xda-developers.com/moto-x/general/guide-fix-moto-x-boots-recovery-t3699644
Click to expand...
Click to collapse
Can this solution be used in my case. I have the same problem of the phone booting to recovery on start up...