Database Users

[Q] Android 4.4 OTA fails on Status 7 system bin debuggerd

I am currently running Nexus 7 (2012) Wifi Android 4.3 Build JWR66Y rooted with CWM and stick mount but when I try to update Android 4.4 OTA it fails on status 7 system bin debuggered. As I was able to just run the Android 4.3 OTA when I upgraded from Android 4.2.2 without any problems this Android 4.4 update is certainly very frustrating. Since I am still a newbie at this could you please provide a step by step of how to get this to work using NRT? Do you have to unroot before installing the update and then reinstall all your apps after? Any help would be greatly appreciated.
Thanks,
KodachromeBob

I'm in the same boat. Trying not to have to start from scratch so I really prefer to run the update instead of flashing the entire device. Vague recollection was that debuggerd gets replaced by stickmount but I tried reverting to the backup file that I had and it still gave me the same (Status 7) error.
I think we just have to find the correct version of debuggerd and overwrite it, then sideload. Let me know if you make any progress.

If I remember correctly you have to be completely stock. If you changed anything the update will not work.
Sent from my HTC6500LVW using Tapatalk

skiman10 said:
If I remember correctly you have to be completely stock. If you changed anything the update will not work.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
It's only aborting on that one file as far as I can tell. Would love to get an original copy and just overwrite the one that's on my Nexus 7 to try if it would work.
Is there a way to get back to stock but not lose all the installed apps and data? I don't mind not using the update file, I just do not want to go through the hassle of setting everything back up (reloading apps, wifi, etc.) again.

Wayno-san said:
It's only aborting on that one file as far as I can tell. Would love to get an original copy and just overwrite the one that's on my Nexus 7 to try if it would work.
Is there a way to get back to stock but not lose all the installed apps and data? I don't mind not using the update file, I just do not want to go through the hassle of setting everything back up (reloading apps, wifi, etc.) again.
Click to expand...
Click to collapse
Is there anything you changed when you were messing around with it? Like adding the stock browser or flash? Something like that...
Sent from my HTC6500LVW using Tapatalk

skiman10 said:
Is there anything you changed when you were messing around with it? Like adding the stock browser or flash? Something like that...
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
No, I just recall having to change the debuggerd file to get stickmount to work. I don't remember the details exactly (it was a long time ago) but I'm pretty sure that is all it was.

Wayno-san said:
No, I just recall having to change the debuggerd file to get stickmount to work. I don't remember the details exactly (it was a long time ago) but I'm pretty sure that is all it was.
Click to expand...
Click to collapse
Sorry then I can't help you. I would titanium backup and go completely stock or flash or something. Hope you get it worked out buddy.
Sent from my HTC6500LVW using Tapatalk

skiman10 said:
Sorry then I can't help you. I would titanium backup and go completely stock or flash or something. Hope you get it worked out buddy.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
No worries. I just found another post (sucks that search is down) that says that if we just flash the boot, system, and bootload img files from KK that it should update without deleting programs or data... I think I'll give that a try.
---------- Post added at 02:42 PM ---------- Previous post was at 02:10 PM ----------
Apparently I flashed in the incorrect order and just flashed boot and system. Nexus 7 appears to have booted up and my apps/data are still present. About screen shows
Android: 4.4
Kernel version: 3.1.10-gee1a0b2
Build: KRT16S
Do I still need to flash bootloader?
---------- Post added at 03:13 PM ---------- Previous post was at 02:42 PM ----------
KodachromeBob said:
I am currently running Nexus 7 (2012) Wifi Android 4.3 Build JWR66Y rooted with CWM and stick mount but when I try to update Android 4.4 OTA it fails on status 7 system bin debuggered. As I was able to just run the Android 4.3 OTA when I upgraded from Android 4.2.2 without any problems this Android 4.4 update is certainly very frustrating. Since I am still a newbie at this could you please provide a step by step of how to get this to work using NRT? Do you have to unroot before installing the update and then reinstall all your apps after? Any help would be greatly appreciated.
Thanks,
KodachromeBob
Click to expand...
Click to collapse
The method of flashing boot, bootloader, and system img seems to have worked. Might want to give that a shot if no one uploads the proper debuggerd file. Best of luck!

Step by Step Required For This Noob PLEASE
Wayno-san said:
No worries. I just found another post (sucks that search is down) that says that if we just flash the boot, system, and bootload img files from KK that it should update without deleting programs or data... I think I'll give that a try.
---------- Post added at 02:42 PM ---------- Previous post was at 02:10 PM ----------
Apparently I flashed in the incorrect order and just flashed boot and system. Nexus 7 appears to have booted up and my apps/data are still present. About screen shows
Android: 4.4
Kernel version: 3.1.10-gee1a0b2
Build: KRT16S
Do I still need to flash bootloader?
---------- Post added at 03:13 PM ---------- Previous post was at 02:42 PM ----------
The method of flashing boot, bootloader, and system img seems to have worked. Might want to give that a shot if no one uploads the proper debuggerd file. Best of luck![/Q
Did you use NRT to accomplish this and would you mind providing the step by step procedure and files that made this successful for you? Being new at this I just don't want to screw it up.
Thanks in advance
KodachromeBob
Click to expand...
Click to collapse

KodachromeBob said:
Did you use NRT to accomplish this and would you mind providing the step by step procedure and files that made this successful for you? Being new at this I just don't want to screw it up.
Thanks in advance
KodachromeBob
Click to expand...
Click to collapse
Yes, just download the 4.4 image from google here:
https://dl.google.com/dl/android/aosp/nakasi-krt16s-factory-da7dee49.tgz
Unzip it until you can pull out the 3 image files I mentioned above. Then use NRT to Flash the files one at a time. You should be good to go. (fingers crossed)

Yesterday my nexus downloaded the update and asked me to press 'ok' to shut down tablet and install.
Just like after every system update the following happend:
Nexus turns off
... thats it, it simply turns off and nothing happens! Device is 2 weeks old now and i am thinking of returning it.
I'm on 4.3 and system tells me that there is no update available...
Nexus 7 2013 sucks!
Sent from my XT910 using xda app-developers app

Wayno-san said:
Yes, just download the 4.4 image from google here:
https://dl.google.com/dl/android/aosp/nakasi-krt16s-factory-da7dee49.tgz
Unzip it until you can pull out the 3 image files I mentioned above. Then use NRT to Flash the files one at a time. You should be good to go. (fingers crossed)
Click to expand...
Click to collapse
Yes, you have to unzip the .tgz file, then unzip the .tar file to get the folder with the image files. 7zip works great. If you are on the stock rom/kernel rooted with a custom recovery (CWM or TWRP) you can fastboot flash on both the system.img and boot.img. Those are the only ones you need. It doesn't look for file verifications in system, it just puts the latest system image there. Flash the latest supersu in custom recovery and you get back root.

Successfully Updated to KRT16S
Could not have done it without the help of Wayno-san. I flashed Boot, Boot Loader and System images with NRT and voila a successful update to KRT16S. I had to ROOT again and reinstall Busy Box but that was not a problem. Thanks again Wayno--san for all your support.
KodachromeBob

My nexus does not even have the Option to start in bootmenue.
As i told, this tablet sucks.
Sent from my XT910 using xda app-developers app

KodachromeBob said:
Could not have done it without the help of Wayno-san. I flashed Boot, Boot Loader and System images with NRT and voila a successful update to KRT16S. I had to ROOT again and reinstall Busy Box but that was not a problem. Thanks again Wayno--san for all your support.
KodachromeBob
Click to expand...
Click to collapse
You're welcome Sir!

Can anyone send me the JWR66Y debuggerd?
I'm also stuck trying to update to 4.4 and I'm hoping to avoid reflashing back to the stock /system. I've reverted all of the system files I touched so it's only debuggerd that's holding up the update. Thanks!
--
kcc

I also had to update manually because of Status 7 update in CWM during OTA flash. Slight inconvenience yes, but nothing major as I didn't flash "Data" via Fastboot command. Had all my apps retained in the next boot
Missing ART though. I don't really want to flash a custom ROM for it.

Anyone willing to send me the KRT16S debuggerd?
If no one has the JWR66Y version, I can just edit the install script to not check (and not patch) debuggerd, then load the KRT16S debuggerd after the update completes. Thanks!
--
kcc

Factory images with January security patch now available

This update is known as 6.0.1 (MMB29S): https://dl.google.com/dl/android/aosp/shamu-mmb29s-factory-fc7b590e.tgz
Anyone want to confirm that we can still use systemless root for this update?

Xplicit84 said:
Anyone want to confirm that we can still use systemless root for this update?
Click to expand...
Click to collapse
why, whats the point? why wouldnt you be able to use systemless root with it?

simms22 said:
why, whats the point? why wouldnt you be able to use systemless root with it?
Click to expand...
Click to collapse
Because when I updated to 6.0.1 last month, the method changed 3 times before things got worked out. Just want to make sure it is still good to go or if the method changed again in the past 3 weeks.

Xplicit84 said:
Because when I updated to 6.0.1 last month, the method changed 3 times before things got worked out. Just want to make sure it is still good to go or if the method changed again in the past 3 weeks.
Click to expand...
Click to collapse
thats because it was a brand new method for 6.0, it was just developed and bugs were being worked out

Everything's fine for me.

FYI, the radio.img and bootloader.img are the same as MMB29K, so they don't need to be flashed. Boot.img and cache.img are the same size, but I'll flash them anyway. System.img is a different size, so it definitely needs to be flashed.

Looks like the kernel is the same.
Sent from my Nexus 6 using Tapatalk

anyone having trouble downloading the new system image from the site?

simms22 said:
thats because it was a brand new method for 6.0, it was just developed and bugs were being worked out
Click to expand...
Click to collapse
While this is true. These security updates are meant to target thing like the root exploits. So while things may still work don't be surprised if it does start needing updates each time Google pushes a security patch. It's a cat and mouse game that will be played until Google manages to lock it down to the point that it is not worth it to root.

maddoggin said:
anyone having trouble downloading the new system image from the site?
Click to expand...
Click to collapse
The factory image download was very slow. Timed out the first time. Second time it worked OK, but still took about 30 minutes.

Can anyone provide a zip image so that we can flash it in twrp?
来自我的 Nexus 6 上的 Tapatalk

tsongwh said:
Can anyone provide a zip image so that we can flash it in twrp?
来自我的 Nexus 6 上的 Tapatalk
Click to expand...
Click to collapse
I second this too. Thank you in advance

i am stock rooted. what are the steps to flash this via adb fastboot? do i have to unroot etc? im getting annoyed by the android update notification.

daimonmustdie said:
i am stock rooted. what are the steps to flash this via adb fastboot? do i have to unroot etc? im getting annoyed by the android update notification.
Click to expand...
Click to collapse
Stock w/ systemless root and Elite kernel.
To applying the update I downloaded the factory image from https://developers.google.com/android/nexus/images untar and unzip image-shamu-mmb29s.zip to get at the system.img file. Then did fastboot flash system system.img, just finished booting and and 'upgrading' my apps. It looks like something in boot.img changed too, but everything seems to be running perfectly fine without flashing it; note that I do have a custom kernel installed, so that might have something to do with it.
If you also fastboot flash boot boot.img then you will likely need to go through the root process again to modify the boot.img to allow root to work properly.
Code:
$diff shamu-mmb29k shamu-mmb29s
Binary files shamu-mmb29k/boot.img and shamu-mmb29s/boot.img differ
...
Binary files shamu-mmb29k/recovery.img and shamu-mmb29s/recovery.img differ
Binary files shamu-mmb29k/system.img and shamu-mmb29s/system.img differ

Stock ROM, TWRP
I have followed the instructions and flashed only the system.img..Nexus 6 - Unlocked, Rooted, Stock ROM, TWRP. It appears everything is running well and the Update notification hasn't appeared..this update was constantly appearing in the notification window and was reported as 5.8mb downloaded patch.
Thanks for your help.

[MMB29P] January Android 6.0.1 Security Patch Factory Images Available

Nexus Security Bulletin - January 2016
Download the Factory Images
MMB29P for Nexus 5x

westernmg said:
Nexus Security Bulletin - January 2016
Download the Factory Images
MMB29P for Nexus 5x
Click to expand...
Click to collapse
Has someone captured the ota?

Nice find thanks

Now just need the modified boot.img for this newest build.

Does anyone can tell me if this month update restores the baseband menu (#*#*4636*#*#)with all the bands options?
Thank you!

it seems you need to this tread:
http://forum.xda-developers.com/nexus-5x/help/baseband-error-china-t3238867
good luck!

ns2israel said:
it seems you need to this tread:
http://forum.xda-developers.com/nexus-5x/help/baseband-error-china-t3238867
good luck!
Click to expand...
Click to collapse
Thanks!
I actually successfully followed this method and manage to get this right again. I was just curious because I read on the google forums that this bug will be solved in a next update and was curious to know if it has been indeed addressed in this build.

Travisdroidx2 said:
Now just need the modified boot.img for this newest build.
Click to expand...
Click to collapse
Actually since SuperSU 2.60 you don't need to worry about boot.img. Depends on your config though. Check out the thread below.
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3

Got the OTA just now. Any chance it might fix the wifi problems I started getting with last month's update? Or does it strictly contain only boring security fixes?

Can you post a link to OTA

bg1906 said:
Actually since SuperSU 2.60 you don't need to worry about boot.img. Depends on your config though. Check out the thread below.
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Click to expand...
Click to collapse
I did see that after. However, I prefer system root still at this time. But I did see where you can run some commands to make the systemless to be system root.

So I'm on the elementalX kernel, TWRP recovery, and rooted (stock) rom. Can i take the OTA that's prompting my phone without it overwriting any of that? I see that the OTA is only 11.4MB so I would assume that at most it would break ROOT.
Thanks in advance!

Tomyk89 said:
So I'm on the elementalX kernel, TWRP recovery, and rooted (stock) rom. Can i take the OTA that's prompting my phone without it overwriting any of that? I see that the OTA is only 11.4MB so I would assume that at most it would break ROOT.
Thanks in advance!
Click to expand...
Click to collapse
I don't think its even possible to update with a custom recovery.

Tomyk89 said:
So I'm on the elementalX kernel, TWRP recovery, and rooted (stock) rom. Can i take the OTA that's prompting my phone without it overwriting any of that? I see that the OTA is only 11.4MB so I would assume that at most it would break ROOT.
Thanks in advance!
Click to expand...
Click to collapse
ulxerker said:
I don't think its even possible to update with a custom recovery.
Click to expand...
Click to collapse
I have the latest TWRP recovery and I'm rooted and running ElementalX kernel. I updated yesterday successfully.
Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Sent from my Nexus 5X using Tapatalk

Hey folks,
Has the OTA URL been made intentionally harder to capture? I got the OTA noon Jan 6th and immediately dumped logcat, but despite the log covering the entire morning there was no URL in there. The log seemed to reflect that the OTA has already been downloaded over WiFi previously, and the phone's UI simply gave the option to install, not to download.
Am I missing something here, or is the only way to capture now to be intercepting traffic and manually running an update check regularly in hopes you get lucky?
I feel like the Android update model is getting even worse, not better. Now not only do Google not publish the OTA links, enthusiasts have a hard time supporting the community too.

dmudd said:
I have the latest TWRP recovery and I'm rooted and running ElementalX kernel. I updated yesterday successfully.
Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
You rock! I'll do this when I get home.

Tomyk89 said:
You rock! I'll do this when I get home.
Click to expand...
Click to collapse
No problem! Also, when I rebooted into system, my phone bootlooped once but didn't again after that. And you will also have to reflash the EX kernel.
Just FYI, I got all of this information from flar2 over in the EX kernel thread from this post.

tigid said:
Hey folks,
Has the OTA URL been made intentionally harder to capture? I got the OTA noon Jan 6th and immediately dumped logcat, but despite the log covering the entire morning there was no URL in there. The log seemed to reflect that the OTA has already been downloaded over WiFi previously, and the phone's UI simply gave the option to install, not to download.
Am I missing something here, or is the only way to capture now to be intercepting traffic and manually running an update check regularly in hopes you get lucky?
I feel like the Android update model is getting even worse, not better. Now not only do Google not publish the OTA links, enthusiasts have a hard time supporting the community too.
Click to expand...
Click to collapse
I didn't know there was a URL for the OTA and that it might show up in the logcat. Otherwise I would've checked for it. And doesn't logcat clear after each reboot? It would mean you would need to have adb ready and dump the log right after you start the download, but before the reboot which might be automatic. I know I've seen some logcat related stuff under dev options - at least for a longer buffer, not sure if you can make it persist across reboots.

I had not rebooted yet, the log covered from before 2AM that morning until noon when I received the notification. Unless the download occurred over ten hours before I was notified I would have expected to see the URL in the log.

Wow I have an update popped up!
Normally I have to manually do it!
Sent from my Nexus 5X using XDA Free mobile app

OTA Update with systemless root

I just received a notification on my 6P saying that the january security update is available. The thing is that I'm rooted with systemless root, xposed, EX Kernel and TWRP. Can I update using the update button?

With systemless I believe you should be able to.

I just posted about this too....no one got back to me. I got the same message and have more or less the same setup as you. I'm scared to reboot and update lol

Pain-N-Panic said:
I just posted about this too....no one got back to me. I got the same message and have more or less the same setup as you. I'm scared to reboot and update lol
Click to expand...
Click to collapse
No.
If you have TWRP installed you will not be able to take an OTA.
Why bother?
Just flash what you want.

Ok, so if I reboot and my phone tries to install the OTA, what happens?

I have exact the same setup and tried to let the OTA install but in TWRP it aborted because of the mismatching kernel I think (at least it said it expected the generic device name Google angler etc and in stead it found Huawei nexus 6P Dees-troy etc)
So no harm is done when you try to update other than it doesn't work
But as far as I know when using xposed there's no use for systemless root because xposed is changing system partition

This update message won't go away. Can I flash it myself through TWRP with Xposed installed?

You cannot use twrp with an OTA. You need stock recovery. Also I believe that Xposed modifies /system and that in itself would prevent the OTA with stock recovery.

dratsablive said:
You cannot use twrp with an OTA. You need stock recovery. Also I believe that Xposed modifies /system and that in itself would prevent the OTA with stock recovery.
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
I used step 10 from this guide then re-flashed TWRP, Super Su, ElementalX and everything seems to be fine, no data loss.

Pain-N-Panic said:
Ok, so if I reboot and my phone tries to install the OTA, what happens?
Click to expand...
Click to collapse
Nothing happens. it'll just fail to flash the update. It'll reboot to twrp, attempt to flash the update, and it'll fail the flash. So it just won't flash. Then you'll just reboot the system and nothing will be changed. I think you can flash these minor changes, but if you try to flash a major update through OTA it won't work with out stock recovery because that's part of the flash I think
---------- Post added at 03:40 PM ---------- Previous post was at 03:38 PM ----------
regenwurm16 said:
I have exact the same setup and tried to let the OTA install but in TWRP it aborted because of the mismatching kernel I think (at least it said it expected the generic device name Google angler etc and in stead it found Huawei nexus 6P Dees-troy etc)
So no harm is done when you try to update other than it doesn't work
But as far as I know when using xposed there's no use for systemless root because xposed is changing system partition
Click to expand...
Click to collapse
It does not bored because of mismatched kernel. Because I tried flashing the stock kernel and then OTA and it still did not work

kirkgbolton said:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
I used step 10 from this guide then re-flashed TWRP, Super Su, ElementalX and everything seems to be fine, no data loss.
Click to expand...
Click to collapse
This. At this time it's the only fix. I did it as well. Never flashed a factory image via fastboot before so I was a little intimidated but Heisenberg's guide is so smooth and easy to follow I did it in about 5 minutes lol. Plus it was a great learning experience for me.

Is it likely that eventually TWRP flashable zips will make this process easier? Or is there some sort of restriction with these updates for Nexus phones that will always require fastboot?

Not sure. I do know that the above method only took me about 10 minutes. Yeah it sucks you have to utilize a PC to do it but its really not that bad. Maybe in the future someone will figure out how to implement the updates via flashable zip in recovery.

I struggle with this too. I really hope that someone will find a solution to flash it via .zip (sadly I'm more a programmer than an Android-hacker, otherwise I would try my very best right now ).

Just to point it out, it looks like the article you are referring to has been updated since it was linked. I wouldn't want to wipe userdata, so I think 11. How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact) is what you were referring to at the time. Apologies for the resurrection.

I just used the FlashFire app to update my Nexus 6p with the February update and it worked like a charm.
http://nexus5.wonderhowto.com/how-t...thout-losing-root-no-computer-needed-0168428/

How to restore IMEI number on a official rom?

okay now I am starting to get lost and the guide for ''fixing your IMEI number'' caused my phone to soft-brick once again so it didn't really help
and yes I used the most recent SuperSU (stable) version V2.78 (I hope that is a correct version)
http://forum.xda-developers.com/oneplus-one/general/steps-how-to-recover-bad-imei-t3171452
my baseband gives a I think correct version but my IMEI number still is ''0''
Please!, can anyone tell me how to restore my IMEI number?

Also my phone uses tries to use LTE connection like I have U.S. drivers (I don't know if it makes a difference since I am pretty much noob)
I find that just wierd.. sorry to bother you guys with all this, I just want my phone to be fixed

dempixels said:
Also my phone uses tries to use LTE connection like I have U.S. drivers (I don't know if it makes a difference since I am pretty much noob)
I find that just wierd.. sorry to bother you guys with all this, I just want my phone to be fixed
Click to expand...
Click to collapse
Did you try to make a complete reset of the phone?

Dio-Genes said:
Did you try to make a complete reset of the phone?
Click to expand...
Click to collapse
And how am I gonna do that?
the only thing I know and have done is: flashing a official rom on the device that's it

dempixels said:
And how am I gonna do that?
the only thing I know and have done is: flashing a official rom on the device that's it
Click to expand...
Click to collapse
Download the zip from the oneplus link... extract it and read the "REEEEEADME.TXT" last paragraph how to type Imei in "RF_NV_manager.exe"...PM me if you need more help.

dempixels said:
And how am I gonna do that?
the only thing I know and have done is: flashing a official rom on the device that's it
Click to expand...
Click to collapse
EXACTLY!!! follow these instructions step by step. Take a look how many sparsechunk files are in the image that you download and proceed as advised. Take care to choose the right image for your device, also about country and so.
http://forum.xda-developers.com/moto-x-play/general/guide-how-to-flash-factory-image-return-t3261486

Dio-Genes said:
EXACTLY!!! follow these instructions step by step. Take a look how many sparsechunk files are in the image that you download and proceed as advised. Take care to choose the right image for your device, also about country and so.
http://forum.xda-developers.com/moto-x-play/general/guide-how-to-flash-factory-image-return-t3261486
Click to expand...
Click to collapse
I've downloaded the EU image just how it was supposed to go, and installed it in correct order. even though it keeps saying ''Pre-flash validation failed''

bablu048 said:
Download the zip from the oneplus link... extract it and read the "REEEEEADME.TXT" last paragraph how to type Imei in "RF_NV_manager.exe"...PM me if you need more help.
Click to expand...
Click to collapse
well that's just it, it requires root but it's always when I install superSU that my phone soft-bricks. it's the third time that happened.

dempixels said:
well that's just it, it requires root but it's always when I install superSU that my phone soft-bricks. it's the third time that happened.
Click to expand...
Click to collapse
Here use this su2.62-3 it will work. http://forum.xda-developers.com/showpost.php?p=64452858&postcount=1
And remember NOT TO RESTORE THE QCN OF ONEPLUS edit your imei using RFNVmanager only.
---------- Post added at 02:41 PM ---------- Previous post was at 02:35 PM ----------
dempixels said:
I've downloaded the EU image just how it was supposed to go, and installed it in correct order. even though it keeps saying ''Pre-flash validation failed''
Click to expand...
Click to collapse
Have you downgraded earlier??

dempixels said:
I've downloaded the EU image just how it was supposed to go, and installed it in correct order. even though it keeps saying ''Pre-flash validation failed''
Click to expand...
Click to collapse
As far as I remember that happened to me when I tried to relock the bootloader at that moment. Did it work anyway? I mean, did it reboot? Which image did you choose? 5.1 or 6.x? Probably start with 5.1 as this was the original image for the device and later let it update via OTA. Be sure still to grab the appropriate image.

Dio-Genes said:
As far as I remember that happened to me when I tried to relock the bootloader at that moment. Did it work anyway? I mean, did it reboot? Which image did you choose? 5.1 or 6.x? Probably start with 5.1 as this was the original image for the device and later let it update via OTA. Be sure still to grab the appropriate image.
Click to expand...
Click to collapse
According to the Motorola official developer forums I am not ALLOWED to install a android 5.X image when I last ran a 6.X android system. as the result could be that I could Hard brick my device
also some further info:
I think in the past when I tried to install the official stock rom. I accidentally removed/erased the EFS file. or some file that holds my IMEI information.
and now I practically have to re-write it (since.. well you can't just create a IMEI ID or Can I?). but it seems impossible if I look at it.
but I do have the original box with the original IMEI number.

bablu048 said:
Here use this su2.62-3 it will work. http://forum.xda-developers.com/showpost.php?p=64452858&postcount=1
And remember NOT TO RESTORE THE QCN OF ONEPLUS edit your imei using RFNVmanager only.
---------- Post added at 02:41 PM ---------- Previous post was at 02:35 PM ----------
Have you downgraded earlier??
Click to expand...
Click to collapse
no I didn't downgrade earlier. (well i flashed a different logo.bin) but no I didn't downgrade.
so that means the superSU 2.78 does not work on android 6.X?

dempixels said:
According to the Motorola official developer forums I am not ALLOWED to install a android 5.X image when I last ran a 6.X android system. as the result could be that I could Hard brick my device
.
Click to expand...
Click to collapse
Sorry, that's beyond my knowledge.

dempixels said:
no I didn't downgrade earlier. (well i flashed a different logo.bin) but no I didn't downgrade.
so that means the superSU 2.78 does not work on android 6.X?
Click to expand...
Click to collapse
Idk about su2.78... I have always used su2.62-3 ..it worked on lollipop and it works on MM.
What is the need of updating SU app, all it does is give 'root' permissions.

bablu048 said:
Idk about su2.78... I have always used su2.62-3 ..it worked on lollipop and it works on MM.
What is the need of updating SU app, all it does is give 'root' permissions.
Click to expand...
Click to collapse
okay, because you have more experience rooting I am gonna ask you just to be sure.
correct me if i'm wrong:
first I have to flash twrp thingy
next I have to reboot android and copy SuperSU into my storage
then I have to reboot in fastboot and boot into twrp
in twrp I have to flash/install SuperSU into the system.
and.. that's it. so superSU practically roots my device?
oh and from what i've heard/seen I will not be able to update anymore? because when I installed/flash superSU I saw in the log:
''disabling OTA update survival'' or something like that

dempixels said:
okay, because you have more experience rooting I am gonna ask you just to be sure.
correct me if i'm wrong:
first I have to flash twrp thingy
next I have to reboot android and copy SuperSU into my storage
then I have to reboot in fastboot and boot into twrp
in twrp I have to flash/install SuperSU into the system.
and.. that's it. so superSU practically roots my device?
oh and from what i've heard/seen I will not be able to update anymore? because when I installed/flash superSU I saw in the log:
''disabling OTA update survival'' or something like that
Click to expand...
Click to collapse
Yes correct, After flashing twrp take a backup(to be on the safe side) then install su.

bablu048 said:
Yes correct, After flashing twrp take a backup(to be on the safe side) then install su.
Click to expand...
Click to collapse
alright 2 final questions before I am gonna start the whole flashing again
1. does this superSU version work with 6.0.1? (just to be sure)
2.what does it backup to be precise? only the system or everything (probably everything)

bablu048 said:
Yes correct, After flashing twrp take a backup(to be on the safe side) then install su.
Click to expand...
Click to collapse
YES!! it's rooted thanks for the guide but now... ermm.. how do I change my IMEI number?

bablu048 said:
Yes correct, After flashing twrp take a backup(to be on the safe side) then install su.
Click to expand...
Click to collapse
and.... nevermind.. it did not root!... what?
I don't understand I followed the steps on how to install superSU with systemless.. something and it all worked. but it did not root! how is that possible?
do I have to try it again?

dempixels said:
and.... nevermind.. it did not root!... what?
I don't understand I followed the steps on how to install superSU with systemless.. something and it all worked. but it did not root! how is that possible?
do I have to try it again?
Click to expand...
Click to collapse
you dont have su app even after flashing su2.62-3??