Develop Bugs

[Q] soft brick..no os detected.. help?

First off, I am completely new to rooting so my apologies if I don't catch on to some of the terms being used.
So the other night, I attempted in starting the process in rooting my n5110 using the Unified Android Toolkit. I got through installing necessary drivers, flashing rom, installing twrp and then when i installed supersu, it had mentioned something about no binaries found. after some searching, I came to the conclusion that it might be the fact that I was on 4.4.2 and it was an incompatibility issue. I then tried cf-auto-root but after the flashing step, I was expecting supersu to work then but it wouldn't even load, just giving me the "supersu has stopped" message every time. So I instead tried a factory reset to try cf-aut-boot again but supersu just wouldn't work. At that point I tried uninstalling supersu but there wasn't even a option available. From reading around, I concluded that my device had to be rooted in order to do that but since I wasn't even able to do that, I got desperate and wiped my whole entire system with twrp which resulted in my os being deleted also...
That being said, I would really like to learn the in's and out's of rooting an android device but before that, if someone could give me a step-by-step process in restoring my device so that I could try rooting it again, that would be greatly appreciated. Then if someone could point me to a guide or site in learning about rooting since I'm such a "newb", that would be wonderful also.

kombobreaker said:
First off, I am completely new to rooting so my apologies if I don't catch on to some of the terms being used.
So the other night, I attempted in starting the process in rooting my n5110 using the Unified Android Toolkit. I got through installing necessary drivers, flashing rom, installing twrp and then when i installed supersu, it had mentioned something about no binaries found. after some searching, I came to the conclusion that it might be the fact that I was on 4.4.2 and it was an incompatibility issue. I then tried cf-auto-root but after the flashing step, I was expecting supersu to work then but it wouldn't even load, just giving me the "supersu has stopped" message every time. So I instead tried a factory reset to try cf-aut-boot again but supersu just wouldn't work. At that point I tried uninstalling supersu but there wasn't even a option available. From reading around, I concluded that my device had to be rooted in order to do that but since I wasn't even able to do that, I got desperate and wiped my whole entire system with twrp which resulted in my os being deleted also...
That being said, I would really like to learn the in's and out's of rooting an android device but before that, if someone could give me a step-by-step process in restoring my device so that I could try rooting it again, that would be greatly appreciated. Then if someone could point me to a guide or site in learning about rooting since I'm such a "newb", that would be wonderful also.
Click to expand...
Click to collapse
Since you already have a custom recovery installed, I would suggest just flashing a rooted rom. The type of rom depends on whether you want 4.2.2 or 4.4.2.
Might start with one of these and can then flash whatever rom you want from that point on:
4.2.2
4.4.2
As for learning about root....each manufacturer has different methods that work. For the Note 8 specifically there are numerous root threads in General and Dev sections that have step-by-step instructions (like CF Autoroot).

thank you for that. I guess i have to do some research now in order to up my rooting game.

I am like you. I only know enough to be dangerous, as I type this, my Note 8 is bricked and am trying to recover it.
As far as your SU concern, you need to turn it into an app. Get the pro version, and towards the bottom, after you open it, you will have this option to make it an app. This should help.
Good luck
Sent from my SGH-I317 using XDA Premium 4 mobile app

If your getting the supersu has stopped error, try downloading the latest supersu apk from the Internet and open the app. You will be asked to update binary and disable Knox. I had to do this twice but it solved my problem. Hope this helps.
---------- Post added at 01:38 PM ---------- Previous post was at 01:36 PM ----------
Also to flash a custom recovery you will want to flash clockworkrecovery through Odin first, and then I would personally suggest flashing Philz recovery.
Ps it's very important you know what Odin is if you're rooting Samsung devices so I would get familiar with it.

[Q] CyanogenMod not getiing installed. SuperSU Crashing.

Hello All,
I am a beginner to all this stuff. I wanted to root my phone after seeing OnePlus One running on CyanogenMod. So, first I tried to directly install the Mod using the softwares downloaded from Cyanogen's website. But the software gave the error "Unsupported Firmware". Then I researched a bit on manually installing the mod. I followed the instructions.
- First I rooted my phone with Odin 3.09v
- Installed ROM Manger on my phone (Meanwhile the SuperSU app kept on crashing)
- Somehow I managed to install ClockworkMod (What I did was downloaded SuperSU apk, installed it again. It started working and then, not losing the chance I installed ClockworkMod).
- Then I tried to install CyanogenMod through ROM Manager
- My phone re-booted and then gave a error "Can't install package on incompatible data".
- I'm having the latest snapshot version on CyanogenMod.
- Then I left the things as it is. No rooting, unrooting, etc.
- So, now I tried to take backup of my current ROM, in case something happens at least I'll be having something with me to recover
- I used ROM Manager to take backup. But it gave the error "Can't create the image"
So, now I'm stuck between middle of nowhere. Please help me out to reach to some point.

svikramajit said:
Hello All,
I am a beginner to all this stuff. I wanted to root my phone after seeing OnePlus One running on CyanogenMod. So, first I tried to directly install the Mod using the softwares downloaded from Cyanogen's website. But the software gave the error "Unsupported Firmware". Then I researched a bit on manually installing the mod. I followed the instructions.
- First I rooted my phone with Odin 3.09v
- Installed ROM Manger on my phone (Meanwhile the SuperSU app kept on crashing)
- Somehow I managed to install ClockworkMod (What I did was downloaded SuperSU apk, installed it again. It started working and then, not losing the chance I installed ClockworkMod).
- Then I tried to install CyanogenMod through ROM Manager
- My phone re-booted and then gave a error "Can't install package on incompatible data".
- I'm having the latest snapshot version on CyanogenMod.
- Then I left the things as it is. No rooting, unrooting, etc.
- So, now I tried to take backup of my current ROM, in case something happens at least I'll be having something with me to recover
- I used ROM Manager to take backup. But it gave the error "Can't create the image"
So, now I'm stuck between middle of nowhere. Please help me out to reach to some point.
Click to expand...
Click to collapse
Ok, first I think your SuperSu is not working properly. Open the Supersu app to see if it needs to update binaries. If it continues to crash, go into recovery manually (not using rom manager) and flash the latest SuperSu. Wipe Cache, go to advanced and Wipe Dalvik. Reboot. Your phone will say "android is upgrading" for a bit. Once it's booted up, go back into the supersu app and see if it needs to update binaries, if so- let it update, if not- move on. Here's a link to download SuperSu 2.02
Go back into recovery manually and select backup and restore-> backup to sdcard (or sdcard1, external sd, is my preference) This will start the backup process.
Once that is done, you need to find the CyanogenMod file specific to your phone, then you can enter recovery and flash it.
If you have trouble entering recovery, you can flash a new one via recovery or with odin.

Hello absinthesummer,
I followed every instruction you told. Now I'm done till creating backup. The problem now I'm facing is this 'Status 7' error. It says "Can't install package on incompatible data.....". Now what to do?

Status 7 is a very specific error. It means your recovery is out of date. Get the absolute newest you can find and try again. This is good news though, you've got progress!
---------- Post added at 11:48 AM ---------- Previous post was at 11:46 AM ----------
Edit: flash the latest recovery you can find via Odin. You probably won't be able to do it in recovery while you're getting the status 7 error.

absinthesummer said:
Status 7 is a very specific error. It means your recovery is out of date. Get the absolute newest you can find and try again. This is good news though, you've got progress!
---------- Post added at 11:48 AM ---------- Previous post was at 11:46 AM ----------
Edit: flash the latest recovery you can find via Odin. You probably won't be able to do it in recovery while you're getting the status 7 error.
Click to expand...
Click to collapse
No, I've got the latest recovery. But I figured out the problem. It was with the package I downloaded. The CM 11 M9 version was giving errors. I researched and tried few fixes, but still it didn't work.
The fixes I tried :-
1. Deleting some coding lines from the updater-script file. But this fix gave the status 6 error.
2. Changing the updater-script file format to UNIX format. Then again it gave the status 7 error.
So, what I did, when I had no more brain to fix it, I downloaded the CM 11 M6 version and tried installing it. And VOILA! It worked. Then I updated it to M9 version through phone. Now it's working. Though it has some bugs. And some features are missing too that I wanted badly.

svikramajit said:
No, I've got the latest recovery. But I figured out the problem. It was with the package I downloaded. The CM 11 M9 version was giving errors. I researched and tried few fixes, but still it didn't work.
The fixes I tried :-
1. Deleting some coding lines from the updater-script file. But this fix gave the status 6 error.
2. Changing the updater-script file format to UNIX format. Then again it gave the status 7 error.
So, what I did, when I had no more brain to fix it, I downloaded the CM 11 M6 version and tried installing it. And VOILA! It worked. Then I updated it to M9 version through phone. Now it's working. Though it has some bugs. And some features are missing too that I wanted badly.
Click to expand...
Click to collapse
Awesome! I'm glad you got it working. You can also try comparing the two files to see what's different, or maybe swap the updater script. Maybe you'll be able to get the one you wanted working with a little modification

absinthesummer said:
Awesome! I'm glad you got it working. You can also try comparing the two files to see what's different, or maybe swap the updater script. Maybe you'll be able to get the one you wanted working with a little modification
Click to expand...
Click to collapse
Thanks to you. You too helped me in working it out!
But, I have some more questions
Question 1 : If I flash stock ROM on my rooted phone, will I receive the new updates? If yes, will I be able to install them via Kies on my phone without getting into any trouble?
Question 2 : If I install stock ROM of any other phone, say Galaxy S5, will it work on my phone properly without any problems? If yes, will I receive the updates for that too and able to install them via Kies? If no, is there any way to install it? Cause I have seen people using S5 ROM on Note 2.

First question the answer is yes. As long as you have the stock recovery and stock kernel (along with the stock rom) you will receive ota updates. You can use ota root keeper (an app) to keep root during an ota update. There are many people who choose to stay fully stock but root to get rid of bloatware & stuff. However, if you want to get ota, I recommend freezing the bloatware instead of uninstalling, because an ota usually replaces old bloatware with new bloatware and can sometimes abort the ota if those apps are missing... but keep on mind this is not always the case, only certain devices.
Second question, no you cannot. Roms from other devices have to be ported to be compatible. But if you look in the development forums, you can find many roms that are basically stock but have specific features from other roms, along with the system ui (ie S5, note 3, & so forth). These rom devs have ported either parts/features or full on roms to be compatible on our device. They are excellent! I recommend reading up them and if you see some you like, try them out!

absinthesummer said:
First question the answer is yes. As long as you have the stock recovery and stock kernel (along with the stock rom) you will receive ota updates. You can use ota root keeper (an app) to keep root during an ota update. There are many people who choose to stay fully stock but root to get rid of bloatware & stuff. However, if you want to get ota, I recommend freezing the bloatware instead of uninstalling, because an ota usually replaces old bloatware with new bloatware and can sometimes abort the ota if those apps are missing... but keep on mind this is not always the case, only certain devices.
Second question, no you cannot. Roms from other devices have to be ported to be compatible. But if you look in the development forums, you can find many roms that are basically stock but have specific features from other roms, along with the system ui (ie S5, note 3, & so forth). These rom devs have ported either parts/features or full on roms to be compatible on our device. They are excellent! I recommend reading up them and if you see some you like, try them out!
Click to expand...
Click to collapse
- Stock Recovery
- Stock Kernel
- OTA Root Keeper
- Bloatware
Well, to be honest, just right now I learned these new terms but know nothing about them. Can you please give me a brief description for these four terms so that when I do advanced search on them, I'd have a idea in my mind about what these are. It will make it easy for me to understand the advance things.
And I'm looking for S5 ROM for my phone. Let's see what I get.

One more question. I made a backup of my rooted stock ROM via latest ClockwordMod, manually. Now, if I reset the binary counter using Triangle Away and then wipe Cache and Dalvik and then flash my stock ROM which is located on my memory card and then after flashing I use SuperSU to unroot and then a factory reset (I don't know the method of factory reseting cause I'm confused. Whether to do it manually, like going into recovery mode or just from the phone settings. So please tell me this also.), will my phone be unrooted totally?
And sorry for bugging you so much. I hate to do that, but I don't want to take risk with my phone. So I am just collecting information. I hope so many queries are not a problem for you.

Ok...
You already know what a rom is. A kernel is a lower-level base. It controls the hardware. So when you do something on the interface, in the rom, it tells the hardware how to react. (Ie if you're playing music it tells which speakers to play and how loudly). The kernel controls almost everything you can't see, it relates to performance. Most stock kernels can be limiting as they underclock the cpu by a certain percentage. Because of this, people seek out custom kernels to max out their device's potential. Louder speakers, faster cpu, better graphics, etc. This is all stuff the kernel can optimize... but because you can change so many factors there is a risk of instability if you push your device too hard (max performance) or limit it too much (max battery saving).
Recovery is exactly what it sounds like. When you boot your device the very first screen that pops up is the bootloader. It's giving you time to boot in 3 different modes. The first mode, by doing nothing, is a normal boot into the rom/OS. The second mode, which you get to by one button combination, takes you to recovery. The stock recovery is very limited. It gives you the option to factory restore, wipe cache, update, or boot normally. Stock recovery only exists for emergencies, if your phone fails to boot normally. We have custom recoveries so we can do more stuff, flash custom roms and tinker with things. The third mode is download mode/Odin mode. This is the bootloader interface itself. It's the last resort for recovery if your recovery has been damaged or corrupted. It allows you to connect to Odin or kies and perform an emergency recovery of the device. If you damage your bootloader, your device is completely bricked.
So the order of operation is this:
Lowest level- bootloader
Second level- recovery
Third level- kernel
Fourth level- rom
Bloatware is all the pre-installed apps that your carrier adds to your phone. Most people don't use it, don't like it, and don't want it. That why we root. Without root we basically are just guest users of the device. With root we become the administrators of the device. Until you root, your carrier has admin rights over your phone (to use windows terms).
When you receive an ota update, your carrier can make it to where the update won't proceed if their pre-installed apps have been removed (although this isn't always the case). Additionally, the update package itself checks the integrity of the device. It checks recovery, kernel, and rom. If any have been altered, it will not proceed because it could cause conflict and potentially brick your device. That's why those things have to be stock.
Ota root keeper is simply an app that backs up your superuser rights before an update and restores them after its done.
You should be able to find plenty of roms with S5 features. I'm using one that makes my device fully like an S5 (my device even thinks it is an S5 and every app identifies it as such) I can think of at least 2 others as well. There's plenty to choose from, and if you see a rom you like but it's mudding a particular feature, you can probably find that feature as a stand-alone installation in the forum's themes & apps section. Just about every feature of S5, S4, and note 3 has been ported to this device, so look around!
Also, for future reference, if someone helps you on the forum, hit the thanks button instead of saying it. I don't mind either way, but some people get annoyed and will stop helping them if they don't hit that button lol. It's silly, but it's part of "forum decorum"
---------- Post added at 12:54 AM ---------- Previous post was at 12:44 AM ----------
svikramajit said:
One more question. I made a backup of my rooted stock ROM via latest ClockwordMod, manually. Now, if I reset the binary counter using Triangle Away and then wipe Cache and Dalvik and then flash my stock ROM which is located on my memory card and then after flashing I use SuperSU to unroot and then a factory reset (I don't know the method of factory reseting cause I'm confused. Whether to do it manually, like going into recovery mode or just from the phone settings. So please tell me this also.), will my phone be unrooted totally?
And sorry for bugging you so much. I hate to do that, but I don't want to take risk with my phone. So I am just collecting information. I hope so many queries are not a problem for you.
Click to expand...
Click to collapse
You're fine, I don't mind answering your questions. Yes, you can unroot fully in the way you just mentioned but you don't even have to go through all the trouble of factory reset. Just unroot in the app. The app can be uninstalled afterwards via the play store.
You can factory reset either way, the same commands are given no matter which way you go about it. But it can be more efficient to do it from recovery because when you do it from the rom it has to create a wipe script for when it reboots, and it has to shut down the rom first. If you do it from recovery it doesn't have to anything, the rom isn't running and it can execute the wipe command immediately. (The wipe command is wipe /data /cache etc)

Thanks again for all that great info!
Questions : Is there no way to fix the Bootloader if it gets damaged by chance? And which S5 ROM are you using?

svikramajit said:
Thanks again for all that great info!
Questions : Is there no way to fix the Bootloader if it gets damaged by chance? And which S5 ROM are you using?
Click to expand...
Click to collapse
If you damage the bootloader it's a hard brick and you would have to send it in for jtag services (this is a low level emmc chip flash service) The bootloader won't get damaged unless you do something to corrupt it. If you ever feel the need to flash a new bootloader, do it via Odin, never recovery! If you remember that you should be fine.

svikramajit said:
Thanks again for all that great info!
Questions : Is there no way to fix the Bootloader if it gets damaged by chance? And which S5 ROM are you using?
Click to expand...
Click to collapse
I meant to tell you I'm using DN3 rom. It has an aroma installer that lets you choose whether you want an S5 ui, a note 3 ui or a mixed ui. Choosing S5 ui & S5 build prop allows your device to work with S5 apps & it looks just like an S5. It's not the only rom out there, but it's beautiful, fast, and stable & the team works hard on it.

absinthesummer said:
I meant to tell you I'm using DN3 rom. It has an aroma installer that lets you choose whether you want an S5 ui, a note 3 ui or a mixed ui. Choosing S5 ui & S5 build prop allows your device to work with S5 apps & it looks just like an S5. It's not the only rom out there, but it's beautiful, fast, and stable & the team works hard on it.
Click to expand...
Click to collapse
Hey absinthesummer!
I tried to unroot my phone with the method I told you. But in the restore option, I am stuck at 'Checking MD5 Sums..'. What to do now?

MD5 checking takes forever! You have to wait it out. Most recoveries offer a way to turn it off. You shouldn't have to factory reset though, just click unroot in the super su app and then uninstall the app from the play store.

absinthesummer said:
MD5 checking takes forever! You have to wait it out. Most recoveries offer a way to turn it off. You shouldn't have to factory reset though, just click unroot in the super su app and then uninstall the app from the play store.
Click to expand...
Click to collapse
I waited and the system was restored. But I got an error on 'Restoring Data'. I rebooted the phone and now it's showing glowing Samsung logo from like 3-4 minutes.

I've seen that before. Can you get back into recovery? You may have to flash stock in Odin, flash recovery and then do the Restore again. Data got messed up.

absinthesummer said:
I've seen that before. Can you get back into recovery? You may have to flash stock in Odin, flash recovery and then do the Restore again. Data got messed up.
Click to expand...
Click to collapse
I'll try removing the battery now. Let's see what happens.

Ok if you can get into recovery, do a fresh flash and then try to restore again. And see if it offers a way to turn off MD5 checking. That's why I use philz or twrp, they offer that and move much faster through MD5 check by default.
---------- Post added at 11:13 AM ---------- Previous post was at 11:12 AM ----------
If you still fail on data, flash stock in Odin, flash custom recovery, then you should be able to enter recovery and have a successful restore.

[Q] "System UI has stopped" forever after installing custom ROM.

I'm not very good at Android technical stuffs as I'm new to it but learned decent basic knowledge before doing any rooting and flashing stuffs.
To start off, I installed ARHD 22.1 back in December and then upgraded to ARHD 30.1 just yesterday, successfully. I'm S-On, using Taiwan HTC One M8x 2.5 ghz unlocked.
I then decided to add the eXtremeBeats audio mod which is compatible to Android L. I followed the instruction there ( DL File, put to phone, flash via recovery, wipe cache & dalvik, reboot ). At the reboot the problem starts, after optimizing the apps, and then it says "starting apps" there it got stuck, I waited it for an hour and a half and decided to force shut my phone. So after turning it on again, it's now stuck on the HTC logo only. I decided to re-install ARHD 30.1 at that same day, successfully installed but when the phone starts, it says "Unfortunately, HTC Dot View has stopped" then followed by "Unfortunately, System UI has stopped". So yeah, I don't have any on screen bottons on my phone, no slide down notification, but can access apps ( no going back though ). I tried to wipe cache & dalvik again, tried re-installing the ARHD 30.1 again for the 3rd time, no luck.
I searched my problem at Google but mine's different. Their "Unfortunately, System UI has stopped" is like soldemly happening in the middle of phone usage and returning back to normal after some seconds, mine gets that problem at the very start up and the UI doesn't return.
What did I do wrong? What must I do? Thanks in advance!
Edit: I noticed that my OS is missing where it's supposed to say something like 3.28.xxx.x. I wiped everything including system at the time I install ARHD 30.1 the second time (where the problem occurred). I think this might have caused the problem? How do I fix this?

Restore your nandroid and see what happens.

redpoint73 said:
Restore your nandroid and see what happens.
Click to expand...
Click to collapse
Yes, I'm currently trying to figure out on how to do this. I'm having problems.
I have a Nandroid backup file in my PC. But I don't know how to push it to /sdcard/TWRP/BACKUP/. I tried the pushing file tutorial via mini-sdk and some cmd commands from ARHD's website tutorial, it can push to /data but I can't get it to work on /sdcard ( I tried to >mount /sdcard == gives error ). The other way I know is to transfer the Nandroid backup file from PC to phone normally via the file copy pasting, my computer can recognize my phone having the ARHD 30.1 (w/ UI problem) installed and USB Debugging on, though I can't access the storage or transfer files.
How do I push my Nandroid backup file from PC to /sdcard/TWRP/BACKUP ... ? Any advice please? I think this will solve my issue.

TheMabaet said:
How do I push my Nandroid backup file from PC to /sdcard/TWRP/BACKUP ... ? Any advice please? I think this will solve my issue.
Click to expand...
Click to collapse
Yes, the syntax for adb pushing a TWRP backup to internal storage can be challenging. If you have a removable SD available, that might be easier, change the save location in TWRP to that. Then make a "mock" backup, purely so that the TWRP folder is created on the SD card. Then either copy/paste your nandroid to the SD with your phone connected to your PC; or use a card reader connected to your PC.
Alternately, you can try to mount the internal storage in TWRP instead of in the OS. That might work better.

redpoint73 said:
Yes, the syntax for adb pushing a TWRP backup to internal storage can be challenging. If you have a removable SD available, that might be easier, change the save location in TWRP to that. Then make a "mock" backup, purely so that the TWRP folder is created on the SD card. Then either copy/paste your nandroid to the SD with your phone connected to your PC; or use a card reader connected to your PC.
Alternately, you can try to mount the internal storage in TWRP instead of in the OS. That might work better.
Click to expand...
Click to collapse
Amazing! I understand the first method, but the alternative... can you explain a bit further? As I tap the Mount button at the main page of TWRP, it says "Select Partitions to Mount:", having System, Cache, Data, Micro SDCard, USB-OTG as options. And then nothing else to do, I see no any other button. Clearly I didn't understood the practice, and I google "How to mount internal storage to TWRP" but somehow didn't get any good result. Could you please tell me how it is done or link me to a guide?
Edit: The first method is fine, though I'd like to know how the second one is done. I apologize if you find me cumbersome but I'd like to learn, might come in handy at some peculiar point. I'm curious as what you said that that might work better but I can't perform the latter, it got me really cheesy
EDIT 2: I managed to do the BACKUP. But now it got stuck to BOOT LOOP. I tried to wipe data, cache, and dalvik... but still it BOOT LOOP. What now?

I'm having a similar problem, did you manage to fix it? How? Thanks.

NOT flashing the correct firmware / Kernel is a most frequent cause of SystemUI crashes. Flash the correct firmware/Kernel to correct this.

wth is wrong with my backup?
alright is there a specific solution to this? me and my mother both have the same phone so i took the lollipop backup from her, renamed it like mines and restored it. once i finish the restore and boot up im greeted with ''unfortunately system ui has stopped''. what gets me crazy and confused is that it works perfectly sometimes when i erase the system and everything then when i restore the same lollipop backup and here we go again, system ui has freakin' stopped! this doesnt happen to any other kitkat backup only lollipop.
i have twrp recovery 2.8.02
my hboot is 2.49
i am currently having s on.
i am sick of htc and their stupid s off and on thing like why should we pay 25 dollars i mean android hacking should be open source right? convert 25 $ to riyals and i cold live for a week, happily!!!

kimosab said:
alright is there a specific solution to this? me and my mother both have the same phone so i took the lollipop backup from her, renamed it like mines and restored it. once i finish the restore and boot up im greeted with ''unfortunately system ui has stopped''. what gets me crazy and confused is that it works perfectly sometimes when i erase the system and everything then when i restore the same lollipop backup and here we go again, system ui has freakin' stopped! this doesnt happen to any other kitkat backup only lollipop.
i have twrp recovery 2.8.02
my hboot is 2.49
i am currently having s on.
i am sick of htc and their stupid s off and on thing like why should we pay 25 dollars i mean android hacking should be open source right? convert 25 $ to riyals and i cold live for a week, happily!!!
Click to expand...
Click to collapse
Hboot should be 3.19 in Lollipop. 2.49 is Android4.4.2 KitKat
Also, update your recovery. 2.8.7.0 works wonderfully.
Bottom line is you need to update your firmware before you try to restore a Lollipop backup.
---------- Post added at 06:40 PM ---------- Previous post was at 06:36 PM ----------
Get into ADB/fastboot and do fastboot getvar all
Post the readout here minus your IMEI and serial# (that's private information you should never post on a public forum)
With that information, it will help us to direct you on the proper way to update, and to provide you with the proper downloads for your device.

kimosab said:
i am sick of htc and their stupid s off and on thing like why should we pay 25 dollars i mean android hacking should be open source right? convert 25 $ to riyals and i cold live for a week, happily!!!
Click to expand...
Click to collapse
Why bash on HTC and sunshine s-off ? You unlocked it, flashed twrp.....that's something HTC didn't nor the guys from sunshine. And you don't need s-off, it's not mandatory but it can make it easier.
I would kindly suggest to drop the ignorant attitude towards the wrong people and focus on the problem you have to solve.

kimosab said:
alright is there a specific solution to this? me and my mother both have the same phone so i took the lollipop backup from her, renamed it like mines and restored it. once i finish the restore and boot up im greeted with ''unfortunately system ui has stopped''.
my hboot is 2.49
Click to expand...
Click to collapse
That is not a valid hboot number for the M8 (which this forum section is specific to). I think you have a One Max.
But as mentioned, you can't just migrate a nandroid from one phone to another. The firmware needs to match also. Running a LP nandroid with KK firmware is going to result in issues.
---------- Post added at 12:00 PM ---------- Previous post was at 11:59 AM ----------
xunholyx said:
Hboot should be 3.19 in Lollipop. 2.49 is Android4.4.2 KitKat
Click to expand...
Click to collapse
Corresponding hboot for Android 4.4.2 on this device is 3.16.
---------- Post added at 12:02 PM ---------- Previous post was at 12:00 PM ----------
Mr Hofs said:
Why bash on HTC and sunshine s-off ? You unlocked it, flashed twrp.....that's something HTC didn't nor the guys from sunshine. And you don't need s-off, it's not mandatory but it can make it easier.
I would kindly suggest to drop the ignorant attitude towards the wrong people and focus on the problem you have to solve.
Click to expand...
Click to collapse
Agreed. S-off isn't the problem, and not needed to remedy the previous user's issue. Main problem is lack of research before messing with the phone.

found an awesome solution. i used to have a nandroid of android 4.4.3, so i restored it, didn't do any kind of wipe and then restored my moms nandroid backup of android L. its working great! i have the htc one m7 dual sim m7_cdug 802w

--delete

Rooting process is taking too much time ?

Hello xda. I'm making this thread in order to know if it's normal that super su is taking so much time to install. My Moto Z play is stuck on this screen since 15 minutes.
Beforehand i unlocked the bootloader and flashed the f2fs kernel. On previous phones it did'nt took this much so I don't understand. Anyone can help me ?
EDIT = Impatience is growing... How can I do to at least reboot the phone without damage ? It's brand new so I don't have to worry about losing any data. Why is it so hard to root a motorola anyway ?

try with MagiskSu, SuperSu is not working correctly in this device because of the Nougat security, if don't flash anything, maybe you should take your time and read this post https://forum.xda-developers.com/moto-z-play/how-to/guide-magisk-official-version-including-t3577875

It is not hard to root Motorola. It is hard to root any device where the /data partition is using f2fs filesystem.
SuperSU in general should work fine after f2fs fix is installed, but I like Magisk more. Not changing system partition when changing system (only do virtual changes using bind) is a very nice idea and the implementation is very good. Only thing that is missing for me is to prevent changes to system (forbid or virtualize "mount -o rw,remount /system" command).
If you want to stay with SuperSU, just use a current one. The 2.79SR3 from January 2017 is the first version that detected need of systemless install on Motorola. All later versions should work also or be improved. There may be some error corrected since then.

Shinobu-Kenji said:
try with MagiskSu, SuperSu is not working correctly in this device because of the Nougat security, if don't flash anything, maybe you should take your time and read this post https://forum.xda-developers.com/moto-z-play/how-to/guide-magisk-official-version-including-t3577875
Click to expand...
Click to collapse
Thanks, my Moto Z play is now rooted and working well. I had problems at first (like reflashing via fastboot a working stock rom) but I re tried flashing magisk and it works fine now

Advice/suggestions on best stable custom rom for new Moto G5 Cedric (XT1671)

Hi, I'm replacing a lost Moto G3 TE with a Moto G5 (xt1671 dual sim) that should be coming in the mail on Monday. I'd like to do whatever mods I want to my phone right away, before activating my google account on it and everything. So, I'd really like any advice any of you can give as to preferred custom rom with root that I should put on my new phone, so I can get to it right away. I've already found the thread to unlock it (same process as in past mostly), and I've found the guides for putting on TWRP (either 32-bit or 64-bit). So, now I just need to decide which custom ROM to use. Please advise!
I've also had a Moto G2 in the past. I've unlocked and used custom roms and root on all my phones so far, from Cyanogenmod 12.1 to AOSP Extended, ViperOS, and LineageOS. My wife's Moto G2 has Oreo on it (through AEX) and we're enjoying it (I had her add me as an account until I get my new phone). So, I'd like to continue using an Oreo system if possible, and I'd even prefer AEX, but it seems that it's discontinued for the Moto G5. Is that correct?
My overall goals for a custom rom are, in order of priority: reliability, speed/performance, battery life, and customization options. I found that AEX balanced all of that well on our past phones. Is the discontinued AEX for this phone reliable, or not? I've also seen the LineageOS thread and the KAOSP thread and have glanced at a few others. I use google accounts and half their apps for sure (so I'll want to install a GApps package with it). And I see there's a possibility to unlock RAW/DNG files for the camera, which I'd really like to try (as I prefer raw file editing instead of JPGs). And the customizations I like (if still possible) are mainly involving the way the launcher responds - I like having the navigation buttons hide, or to swipe up to get them back, I like being able to modify the status bar, etc.... typical customizations that were usually available in AEX that I've used. I also use root for file explorer and a few other functions - I used to always use SuperSU in the past, but just recently started using Magisk (on the Moto G2) and it seems good, though I'm open to any recommendation about which root to use.
So, please fire away! Please give your suggestion as to which currently available custom ROMs are stable, have good performance, good battery life, and offer standard customization, plus which I can root. I appreciate any suggestions and any advice you can give, especially regarding if there's a recommended rom but if it has known issues and any known workarounds. Also, I'd appreciate advice anytime today or tomorrow (since it'll likely be the afternoon or evening of Monday +3 GMT time - Madagascar - that I'm able to start working on unlocking it, installing custom recovery, etc.). But even if the advice is late, I might still be able to use it. I know this is a bit much to ask, but please give your own opinions freely!
Oh, by the way, do I need updated Motorola drivers, or will the motorola drivers and adb/fastboot I installed last time (for the Moto G3 TE) keep working with the new phone? The unlock thread I've found here doesn't say anything about motorola drivers or adb/fastboot. Thanks in advance!

the best stable rom is stock rooted

woozie.2007 said:
the best stable rom is stock rooted
Click to expand...
Click to collapse
Thanks for the response! Is there a stock oreo available? And is stock rooted still customizable (like with AEX or something - can I install some sort of thing to let me customize it more?). And is there a debloated version of the stock rom available? I saw one thread on here about a debloated stock rom, but it looked like it was still nougat.
If it's possible to customize the stock rom further, please point me in the right direction. And if not possible to customize it further... then are you suggesting that any of the custom roms available aren't very stable to be used well for a daily driver?
Again, thanks for your response and also for any more feedback you can give!

So, I have my phone now and it came with stock Nougat. I've unlocked it, and I'm currently working on getting TWRP, Dm-verity thing on it, and then magisk. After that can I still update it to Oreo or not? Please advise. Thank you!

madagascaradam said:
So, I have my phone now and it came with stock Nougat. I've unlocked it, and I'm currently working on getting TWRP, Dm-verity thing on it, and then magisk. After that can I still update it to Oreo or not? Please advise. Thank you!
Click to expand...
Click to collapse
no, you have to update oreo first, after that install twrp and magisk for root it

woozie.2007 said:
no, you have to update oreo first, after that install twrp and magisk for root it
Click to expand...
Click to collapse
Crud, that sucks! I was already finished rooting and everything on magisk, then I let the OTA update download and when it restarted my phone, it just automatically sends it into recovery (TWRP) every time now! I tried to install this TWRP stock Oreo (dirtying flashing it) hoping it would fix the boot-loop-to-TWRP-recovery problem, but it didn't. So now I need to figure out a way to get back to the original, so I can start over and try again.
I'm trying to do a factory reset and try again, but in TRWP it says ""Failed to mount '/data' (Device or resource busy)'" This sucks! Any ideas where I can go or what I can do (such as some fastboot commands or something) to get it all working again?
EDIT: It does reboot to bootloader though, so it's not hardbricked. Just need to figure out what to do from here. Thanks for any help!

try to flash via fastboot only boot, recovery, oem and system from oreo, then aply update, then root

Thanks! I downloaded the firmware (for latest Nougat) from this thread: https://forum.xda-developers.com/g5/development/stock-upgrade-to-official-stock-oreo-8-t3823598
Then I flashed everything they said through fastboot (ignoring the modem stuff) because I'm still downloading the oreo firmware right now anyway (my connection is quite slow). At first the bootloader got stuck and said "error" and I was freaking out thinking I'd hard-bricked it. But I turned it off and on again anyway and it loaded fine back into nougat for that latest version.
So now I'm downloading the latest stock Oreo and I'll probably try to ADB sideload it.
Which root do you recommend? I have the Magisk I did for nougat that worked great - 11.6 But there's this thread here (https://forum.xda-developers.com/g5/how-to/guide-how-to-root-stock-oreo-8-1-soak-t3832347) that talks about what seems like a complicated way of doing Magisk 15.3 and then getting it up to 16. What do you suggest?

magisk 17.1 its ok, but you have to flash only partition that i said, not full firmware, and DONT flash the bootloader and GPT partition
---------- Post added at 06:11 PM ---------- Previous post was at 06:10 PM ----------
better let the phone to update ota for latest security patch, dont flash via fastboot

OK, I installed the stock oreo through ADB sideload (it wouldn't read my storage for some reason).... then I reinstalled TWRP, no problem... then installed Magisk 17.1 (per your suggestion) and then the apk for the manager. Everything's working great! Didn't even need that dm-verity thing.
I'm still looking into the mods I can do to it now that it's rooted (such as changing boot logo and boot animation, adding that 'camera 2' setting, etc.) So I'm not sure I'm at a finished product yet, but I'm definitely at a stable rooted oreo with all my regular stuff installed, so that's a good place to start! I've made a nandroid backup here in case any of my further experimenting messes it up.
Thanks again for your help! And if you can give any suggestions towards the best way to customize the look (for example - is nova launcher still the best way to do that?) or other aspects of the system UI, while still being on this stock rom, then please let me know. I'll look up how to get that better camera mode working.

woozie.2007 said:
magisk 17.1 its ok, but you have to flash only partition that i said, not full firmware, and DONT flash the bootloader and GPT partition
---------- Post added at 06:11 PM ---------- Previous post was at 06:10 PM ----------
better let the phone to update ota for latest security patch, dont flash via fastboot
Click to expand...
Click to collapse
Could you help me with this: if I backup my system (everything) with TWRP.... can I then switch to a custom rom to try it out (in case I want a different user interface, more tweaks, etc.) and if I don't like it can I easily switch back to the stock rom nandroid backup I have saved in TWRP (thus restoring my previous state, but without having to start from factory reset)? Or would it be difficult to switch back - like would I have to redo it through fastboot or something and factory reset, etc.?
I'm asking because in the past I never used the stock rom much and I definitely never switched between a custom rom and the stock rom. Once I went for custom rom, I didn't go back - so I don't know if it's as simple as restoring a nandroid backup or if it's much more effort. Please let me know. Thanks a lot!

you must be very carefully because most of the custom roms need twrp on 64 bits, now you have official twrp 32. When you come back from custom roms 64bit to previous nandroid backup, you must install 32 bits twrp, otherwise you may lose the imei of the phone, just read very well when you want to do something risky

woozie.2007 said:
you must be very carefully because most of the custom roms need twrp on 64 bits, now you have official twrp 32. When you come back from custom roms 64bit to previous nandroid backup, you must install 32 bits twrp, otherwise you may lose the imei of the phone, just read very well when you want to do something risky
Click to expand...
Click to collapse
OK, thanks a lot for that helpful info! So just to clarify to be sure: basically, if I want to switch back and forth, I'll install the 64-bit twrp first, then the custom rom(s). Then if I want to come back to my stock image backup, I re-install the 32-bit twrp (like the one I'm currently using) and then I can just restore my nandroid backup I took of the stock and all is well? And it's not risky if I do it like that?

yes, its correct that