can anyone confirm if root from cf's method is working on xt1063 without bootlooping on 5.0?
http://www.theandroidsoul.com/chainfire-releases-android-5-0-root-moto-g-moto-x-2013-2014-editions/
Kobro said:
[...] without bootlooping on 5.0? [/url]
Click to expand...
Click to collapse
Right now, there is no reliable way of rooting XT106x without a couple of bootloops. Results vary between 1-5 loops before the boot process continues.
I'm running the latest beta of SuperSu and the problem persists.
This is *the* lollipop deal breaker currently. I can't live without root, so, I have to live without lollipop right now.
doppelhelix said:
Right now, there is no reliable way of rooting XT106x without a couple of bootloops. Results vary between 1-5 loops before the boot process continues.
I'm running the latest beta of SuperSu and the problem persists.
Click to expand...
Click to collapse
but after a few loops the phone does actually boot up?
Kobro said:
but after a few loops the phone does actually boot up?
Click to expand...
Click to collapse
Yes. After install you may experience non ending loop. Just force reboot into recovery, clean cache and reboot. Be patient. 1st boot is always a bit unreliable. But after that, rebooting the phone works without problem
doppelhelix said:
Yes. After install you may experience non ending loop. Just force reboot into recovery, clean cache and reboot. Be patient. 1st boot is always a bit unreliable. But after that, rebooting the phone works without problem
Click to expand...
Click to collapse
and there shouldnt be any random reboots correct? because i rooted once, after wiping cache it booted then rebooted for no reason
Kobro said:
and there shouldnt be any random reboots correct? because i rooted once, after wiping cache it booted then rebooted for no reason
Click to expand...
Click to collapse
Well, I never used the cf autoroot method. Just downloaded the stable zip download.chainfire.eu/supersu flashed it and everthing is fine (except for the bootloop of course). Never had random reboots related to root.
doppelhelix said:
Well, I never used the cf autoroot method. Just downloaded the stable zip download.chainfire.eu/supersu flashed it and everthing is fine (except for the bootloop of course). Never had random reboots related to root.
Click to expand...
Click to collapse
this zip is to flash from twrp?
Kobro said:
this zip is to flash from twrp?
Click to expand...
Click to collapse
Yes
Related
Sometimes when I boot in recovery I get a "no OS installed error". I have to reboot the recovery in order to fix it. Does that happen to anyone else? If so, do you know what causes it? It seems to have only started happening recently? Maybe it's the 4.2.2 roms?
SkizzMcNizz said:
Sometimes when I boot in recovery I get a "no OS installed error". I have to reboot the recovery in order to fix it. Does that happen to anyone else? If so, do you know what causes it? It seems to have only started happening recently? Maybe it's the 4.2.2 roms?
Click to expand...
Click to collapse
I haven't seen that before, sounds odd. Try reflashing recovery and wiping cache, also make sure you're updated to the latest CWM
MacHackz said:
I haven't seen that before, sounds odd. Try reflashing recovery and wiping cache, also make sure you're updated to the latest CWM
Click to expand...
Click to collapse
I use TWRP.
SkizzMcNizz said:
I use TWRP.
Click to expand...
Click to collapse
Well then... use CWM and see if the issue goes away
I tried rerooting my phone and every time I flash an image.It just stays at the M and never boots.The reason why I needed to re root my phone was because I needed the HDR fix.Please help.
ry_t said:
I tried rerooting my phone and every time I flash an image.It just stays at the M and never boots.The reason why I needed to re root my phone was because I needed the HDR fix.Please help.
Click to expand...
Click to collapse
Get into bootloader mode and flash back to stock system. Be sure and boot into recovery after you flash stock system and then wipe the cache. Then reflash the image you want using mofo. Then wipe the cache after you do, then boot into system.
JulesJam said:
Get into bootloader mode and flash back to stock system. Be sure and boot into recovery after you flash stock system and then wipe the cache. Then reflash the image you want using mofo. Then wipe the cache after you do, then boot into system.
Click to expand...
Click to collapse
I've done that a couple of times and it still stays stuck at the M.I'll try again tonight when I get home from work.Sometimes I can't even get to the wipe cache screen.
ry_t said:
I've done that a couple of times and it still stays stuck at the M.I'll try again tonight when I get home from work.Sometimes I can't even get to the wipe cache screen.
Click to expand...
Click to collapse
Are you sure the stock system images is flashing? What image are you flashing?
Also, I don't know what you mean you can't get to the wipe cache screen - it is recovery. I have all of the instructions on how to get into bootloader mode and flash back to stock as well as getting into recovery here:
http://forum.xda-developers.com/moto-x-2014/general/noob-guide-rooting-verizon-moto-x-2014-t3097375
Also, if you are having trouble flashing the sparsechunks from RJ's site, then you can download the fxz and flash the single image system.img using mfastboot.
http://forum.xda-developers.com/showpost.php?p=60312510&postcount=18
I'm on stock right now. I tried to reflash the root and tether one then flash the one with xposed and that one stays at the M and never boots.I've flashed back to stock fine
ry_t said:
I'm on stock right now. I tried to reflash the root and tether one then flash the one with xposed and that one stays at the M and never boots.I've flashed back to stock fine
Click to expand...
Click to collapse
OK well there are special instructions on what you need to do the first time you flash an image with Xposed. Both ClydeDroid and mikeoswego have those instructions in their OP with the links to the images.
I've flashed both of these files from this thread http://forum.xda-developers.com/mot...mages-mofo-t3100601/post60537982#post60537982 and I still get stuck at the M logo.Wiped and didn't wipe cache and still nothing :/
JulesJam said:
OK well there are special instructions on what you need to do the first time you flash an image with Xposed. Both ClydeDroid and mikeoswego have those instructions in their OP with the links to the images.
Click to expand...
Click to collapse
Try wiping data instead of just a factory wipe. Note that this will nuke your sdcard.
the data wipe didn't help either.I'm stuck.need my phone,so I'm goling to flash back to stock
Bump
Bump
ry_t said:
Bump
Click to expand...
Click to collapse
So to summarize - you are back on stock and everything works fine? But when you try to flash an image via mofo.exe, it never boots and instead hangs on the M?
That sounds to me like your image is corrupted. I would re-download the image.
JulesJam said:
So to summarize - you are back on stock and everything works fine? But when you try to flash an image via mofo.exe, it never boots and instead hangs on the M?
That sounds to me like your image is corrupted. I would re-download the image.
Click to expand...
Click to collapse
I'll give that a try.
ry_t said:
I'll give that a try.
Click to expand...
Click to collapse
Be sure and wipe cache after flashing and let it hang at the M for awhile too before you conclude that it is not going to boot.
JulesJam said:
Be sure and wipe cache after flashing and let it hang at the M for awhile too before you conclude that it is not going to boot.
Click to expand...
Click to collapse
Woot.I have root again.I guess it was a dead file.Thanks
Here is the problem. I accidentally deleted everything on my Nexus, so now I have no operating system. I am trying to flash stock android 6.0 and I recieve the error "package missing system.img". My phone was already running Marshmallow, and I had no problems installing it the first time, so I am not quite sure why this is happening now.
Majava42 said:
Here is the problem. I accidentally deleted everything on my Nexus, so now I have no operating system. I am trying to flash stock android 6.0 and I recieve the error "package missing system.img". My phone was already running Marshmallow, and I had no problems installing it the first time, so I am not quite sure why this is happening now.
Click to expand...
Click to collapse
easy one to solve as its written around so many times.. do not use the flash-all script, you have to flash each partition individually.
simms22 said:
easy one to solve as its written around so many times.. do not use the flash-all script, you have to flash each partition individually.
Click to expand...
Click to collapse
I did this but it got stuck in a boot animation.
Majava42 said:
I did this but it got stuck in a boot animation.
Click to expand...
Click to collapse
try it again. if you get stuck in a bootloop, go back and wipe data/factory reset.
simms22 said:
try it again. if you get stuck in a bootloop, go back and wipe data/factory reset.
Click to expand...
Click to collapse
I tried this 3 more times and it still got stuck in a bootloop, should I keep trying?
Are you using a toolkit to flash?
Sent from my Nexus 6
Majava42 said:
I tried this 3 more times and it still got stuck in a bootloop, should I keep trying?
Click to expand...
Click to collapse
Try reflashing boot.img.
Worked for me.
Did you ever find a solution to this problem? I'm curious now! I've heard of people having this problem before, I started flashing them individually for this reason! You can NEVER be too safe when doing something like this. You get the hang of doing it individually after doing it so many times though.
Sent from my Nexus 6
Hi,
On Wednesday I rooted my SM-T810 (with Android 5.0.2) with cf-autoroot and after that I installed TWRP from this XDA forum.
I took a Nandroid backup and then I installed the CM12.1 root from T_I.
It worked perfectly.
But now after I switch the tablet off and on it doesn't get past the Samsung screen.
I can go to download mode and I then I am able to flash cf-autoroot again with Odin.
After that it starts up, but the problem occurs again the next time I power the tablet off.
I can flash the tablet with a Samsung firmware from SamMobile, but I also have a LG G4 and an older Samsung Galaxy Tab S 8.4 both with CM, so I really would like to keep using CM.
Any ideas how to fix this?
Disable cm root in developer settings.
No, that didn't work either.
I reflashed a sammobile image, but still the same issue.
Then I installed twrp 3.0 and could boot to it (through download mode).
I reinstalled CM12.1 and it works as long as I don't switch the tablet off.
Unfortunally I cannot return it, because of the knox trip counter.
jaap2012 said:
No, that didn't work either.
I reflashed a sammobile image, but still the same issue.
Then I installed twrp 3.0 and could boot to it (through download mode).
I reinstalled CM12.1 and it works as long as I don't switch the tablet off.
Unfortunally I cannot return it, because of the knox trip counter.
Click to expand...
Click to collapse
Have you tried flashing stock firmware from sammobile with odin? It should fix all problems and you should boot.
Have you tried flashing stock firmware from sammobile with odin? It should fix all problems and you should boot.
Click to expand...
Click to collapse
Yes, that didn't work.
I think it cannot erase the volumes back to stock?
ok, I fixed it by restoring the full Nandroid backup.
It is booting and working again.
I think it must have been an issue with the boot image or so.
I'll start over with CM12.1 next weekend...
jaap2012 said:
ok, I fixed it by restoring the full Nandroid backup.
It is booting and working again.
I think it must have been an issue with the boot image or so.
I'll start over with CM12.1 next weekend...
Click to expand...
Click to collapse
You had a nandroid backup but didn't use that first? :sly:
ashyx said:
You had a nandroid backup but didn't use that first? :sly:
Click to expand...
Click to collapse
Yeah, sorry.
I didn't expect that that would fix this boot problem, because this restore already has superSU installed.
jaap2012 said:
Yeah, sorry.
I didn't expect that that would fix this boot problem, because this restore already has superSU installed.
Click to expand...
Click to collapse
A nandroid almost always fixes the issue if it was made from a working system.
Are their currently any kernals which support marshmallow now? I installed emotions kernals but the wifi doesn't work and I do not know how to get back to stock kernel.
Thank you
hunter99507 said:
Are their currently any kernals which support marshmallow now? I installed emotions kernals but the wifi doesn't work and I do not know how to get back to stock kernel.
Thank you
Click to expand...
Click to collapse
try flashing dr.ketens data fix in recovery.
funtimez said:
try flashing dr.ketens data fix in recovery.
Click to expand...
Click to collapse
Using an N910t3 I flashed emotion MM rc25 , confirmed wifi didn't work, tried the data fix it put me in a bootloop, luckily I had made a complete backup in TWRP and restored it already, just want to warn anyone else before they try it.
You should keep A backup of the original the "boot" partition in twrp. In TWRP>Backup>select "boot" only. That keeps the stock kernel.
I haven't tested any alternative kernels personally.
I feel that the stock MM kernel is doing great.
MM works fine. I'm waiting for MM kernel
I had a few problems with Marshmallow but finally installed the latest PG2. My phone N910T boot looped and caused some problems but eventually I finally had a working 6.0.1 stock. I installed TWRP and SuperSU SYSTEMLESS and used the phone for 2 days.
I tried flashing Beastmode and Emotion kernels but neither worked and I was stuck in a boot loop. Eventually I tried to reinstall stock without a wipe as this always works and keeps my apps etc.
The stock said the md5 checksum was invalid even though it was the same file from 2 days earlier. To fix this I removed the file extension, preventing it from doing the MD5 check and attempted to install. It bricked my phone as the process appeared to stop at halfway and I aborted. I found modem and bootloader files for PG2 and took a shot at installing them. I got to another bootloop.
I tried the stock tarfile again and was a little more patient this time. The previous delay was only a few minutes long. It installed succesfully. I Installed TWRP with ODIN, followed by a systemless root in recovery mode.
I'm currently waiting for MM kernels. I hope my little adventure helps somebody else on their journey.
FungusTB said:
I had a few problems with Marshmallow but finally installed the latest PG2. My phone N910T boot looped and caused some problems but eventually I finally had a working 6.0.1 stock. I installed TWRP and SuperSU SYSTEMLESS and used the phone for 2 days.
I tried flashing Beastmode and Emotion kernels but neither worked and I was stuck in a boot loop. Eventually I tried to reinstall stock without a wipe as this always works and keeps my apps etc.
The stock said the md5 checksum was invalid even though it was the same file from 2 days earlier. To fix this I removed the file extension, preventing it from doing the MD5 check and attempted to install. It bricked my phone as the process appeared to stop at halfway and I aborted. I found modem and bootloader files for PG2 and took a shot at installing them. I got to another bootloop.
I tried the stock tarfile again and was a little more patient this time. The previous delay was only a few minutes long. It installed succesfully. I Installed TWRP with ODIN, followed by a systemless root in recovery mode.
I'm currently waiting for MM kernels. I hope my little adventure helps somebody else on their journey.
Click to expand...
Click to collapse
You're able to flash TWRP and root on stock PG2 for N910T?
thebestiam said:
You're able to flash TWRP and root on stock PG2 for N910T?
Click to expand...
Click to collapse
Yes it works. I'm experiencing battery drain through.
FungusTB said:
Yes it works. I'm experiencing battery drain through.
Click to expand...
Click to collapse
Doesn't it update the bootloader to PG2 from PE3 and it'll still work?
Sent from my GT-I9500 using XDA-Developers mobile app
thebestiam said:
Doesn't it update the bootloader to PG2 from PE3 and it'll still work?
Click to expand...
Click to collapse
I don't know. I've upgraded bootloader in the past without issues. There seems to be issues surrounding mismatched modems and bootloader recently.
FungusTB said:
I don't know. I've upgraded bootloader in the past without issues. There seems to be issues surrounding mismatched modems and bootloader recently.
Click to expand...
Click to collapse
Okay, thanks for the clear up
Sent from my SM-N910T using XDA-Developers mobile app