Database Users

How to remove CWM please?

Hi
I'm going to update my a500 to 3.1
I have unrootedmy device but how to remove CWM completly????
Please help

Why don't just update via CWM:
http://forum.xda-developers.com/showthread.php?t=1154492

1) re root your device
2) go into acer recovery installer and reflash to the backed up recovery (or do the stock recovery for your version)
3) de root.
I had to do this to get my update to work.

Do you know where can I find stock recovery for my version?
I have Acer_A500_1.139.05_COM_GEN1
thank you!
simonsgray said:
1) re root your device
2) go into acer recovery installer and reflash to the backed up recovery (or do the stock recovery for your version)
3) de root.
I had to do this to get my update to work.
Click to expand...
Click to collapse

When i installed ARI, it backed up my current recovery. When i went back into ARI, my old recovery was the first option. Sorry, explanation sucks, i don't have screenshots for you. I know there are threads with most of the software/firmware elements of most of the different versions, maybe do some digging? This would be the best place to start: http://forum.xda-developers.com/showthread.php?t=1126364

Look in system/etc for a filed called install-recovery.sh. if its there change its permission from 444 to 544. Then reboot normally. It'll overwrite cwm with your stock recovery.
Sent from my A500 using Tapatalk

Thanks! I used stock one in ARI, woks good.
simonsgray said:
When i installed ARI, it backed up my current recovery. When i went back into ARI, my old recovery was the first option. Sorry, explanation sucks, i don't have screenshots for you. I know there are threads with most of the software/firmware elements of most of the different versions, maybe do some digging? This would be the best place to start: http://forum.xda-developers.com/showthread.php?t=1126364
Click to expand...
Click to collapse

Euclid's Brother said:
Look in system/etc for a filed called install-recovery.sh. if its there change its permission from 444 to 544. Then reboot normally. It'll overwrite cwm with your stock recovery.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Hi Euclid, are you able to post a copy of that install-recovery.sh file? I don't seem to have it in my system/bin anymore
...That is assuming the file is not unique to each device??
I'm thinking the reason my OTA update wouldnt install is because i dont have the stock recovery menu.
Thanks!

I really don't get why everyone is spazzing over this... If you've already taken the steps to root and install CWM in the first place, why not just install the stock 3.1 image that's been provided in the dev section? It's 100% stock, no need to wait for Acer to stop twiddling their dangly bits...

Floatingfatman, that is exactly what I did, and it worked perfectly. Good advise!

FloatingFatMan said:
I really don't get why everyone is spazzing over this... If you've already taken the steps to root and install CWM in the first place, why not just install the stock 3.1 image that's been provided in the dev section? It's 100% stock, no need to wait for Acer to stop twiddling their dangly bits...
Click to expand...
Click to collapse
Yeah thats what i ended up doing to update it to 3.1.
Reason i want it back to stock is that i couldnt update via OTA at all (downloads fine but install fails at ~20% with the ! in a red triangle).
I was hoping by restoring it to stock the OTA would work, and so any future updates could also be done via OTA as opposed to finding a workaround each time.
Other than that, it's working just fine for now.

Euclid's Brother said:
Look in system/etc for a filed called install-recovery.sh. if its there change its permission from 444 to 544. Then reboot normally. It'll overwrite cwm with your stock recovery.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
I don't understand 'change permission from 444 to 544'. Root Manager lets me choose between, 'Read, Write or Execute'. Could you please elaborate?
Thanks
Never mind. Problem solved.

[Q] Shot self in foot, edited build.prop now N7 won't boot

I was testing tablet UI mode by editing the /system/build.prop file. The N7 went into Tablet UI mode OK but I didn't like it so I reedited the /system/build.prop file to undo my edits, and now the N7 doesn't boot properly. It goes to a black screen and just sit there.
I can boot into recovery and I can get adb to work. I used the pull command to get a copy of the build.prop file and it seems OK but I'm not 100% sure if I made any other edits by mistake. Of course like a fool I didn't make a backup of the original.
Can anyone make some suggestions on how to fix my N7?
Thanks.

lbloo said:
I was testing tablet UI mode by editing the /system/build.prop file. The N7 went into Tablet UI mode OK but I didn't like it so I reedited the /system/build.prop file to undo my edits, and now the N7 doesn't boot properly. It goes to a black screen and just sit there.
I can boot into recovery and I can get adb to work. I used the pull command to get a copy of the build.prop file and it seems OK but I'm not 100% sure if I made any other edits by mistake. Of course like a fool I didn't make a backup of the original.
Can anyone make some suggestions on how to fix my N7?
Thanks.
Click to expand...
Click to collapse
reflash your ROM. it'll replace your build.prop with a good copy. don't wipe a thing, just reflash.

I'm rooted but on stock. Can I just download a copy of the stock rom and flash that with CWM?

lbloo said:
I'm rooted but on stock. Can I just download a copy of the stock rom and flash that with CWM?
Click to expand...
Click to collapse
rooted stock ROM yea. I've also flashed a pure aosp ROM over stock without any reprocussions.

Before I go ahead and reflash I just want to make sure I'm getting it right. I've downloaded the stock rom, extracted image-nakasi-jro03d.zip. I should push this file to my internal storage, then use CWM to flash? Or should I just find a pure aosp ROM and flash that?
Sorry for all the questions, I just don't want to make things worse.

lbloo said:
Before I go ahead and reflash I just want to make sure I'm getting it right. I've downloaded the stock rom, extracted image-nakasi-jro03d.zip. I should push this file to my internal storage, then use CWM to flash? Or should I just find a pure aosp ROM and flash that?
Sorry for all the questions, I just don't want to make things worse.
Click to expand...
Click to collapse
I don't know what you picked up, but here's a stock/rooted ROM that you can flash in your cwm recovery http://forum.xda-developers.com/showthread.php?t=1776330
Aosp works too, its your choice

if you know how to use adb you can just boot to recovery and push the stock build.prop to your tab

I downloaded a stock copy of the stock build.prop, used the adb push command to push it into /system rebooted and nothing. Still hangs on black screen upon boot.
I then downloaded the stock ROM which simms22 kindly pointed me to, used the adb push command to copy the zip file into /data/media/Firmware, used CWM v6.0.1.0 to "install zip file from sdcard" and I got an error, here is the output:
Installing:/sdcard/Firmware/Nexus7 - JRo03d-Odexed-ROOT_4.1.1_signed.zip
Finding update package...
Opening update package...
Installing update package...
E:Error in /sdcard/Firmware/Nexus7 - JRo03d-Odexed-ROOT_4.1.1_signed.zip
(Status 0)
Installation aborted.
I tried both the Odexed and Deodexed files, both gave same results.
Am I missing a step in the process?

It's working now!
I was afraid I was messing up some of the adb commands so I downloaded the Nexus 7 Toolkit 2.0 (Great tool for someone like me)
- via Toolkit re-transferred the odexed and deodexed ROM files, reflashed, same errors as above
- via Toolkit re-installed CWM Recovery 6.0.1.0, reflashed, same errors as above
- via ADB Shell used CHMOD to modify file rights of the ROM files (stab in the dark), same errors as above
- downloaded stock image from CWM site (JRO03D_grouper.zip), pushed via tool kit, flashed via CWM....WORKED!!!
Everything is as it was before, no need for a full wipe! I'm going to do a backup right now!
Not sure why the other ROMS would not flash, but at this point I'm not going to mess around to try to figure it out.
Many thanks to simms22 and PhxkinMassacre for getting me pointed in the right direction.

prly a bad download.
after pushing the file you need to set the correct mode:
Code:
adb shell chmod 644 /system/build.prop

Me too - also hosed my own build.prop
lbloo said:
- downloaded stock image from CWM site (JRO03D_grouper.zip), pushed via tool kit, flashed via CWM....WORKED!!!
Everything is as it was before, no need for a full wipe! I'm going to do a backup right now!
Click to expand...
Click to collapse
Ok, I did the exact same thing and followed these instructions but haven't had any luck.
First, thanks lbloo and the folks who have responded for all the info here. I have downloaded JRO03D_grouper.zip and I am grateful for the tip to the toolkit.
When I have pushed JRO03D_grouper.zip to the N7, it appears to have worked, but I can't find it on the sdcard. I am pushing from the default location to /sdcard/. I then select "install zip from sdcard" and "choose zip from sdcard" but the only zip there is supersu (from Day 1).
For reference, this is CWM Recovery v 6.0.0.6.
Thanks in advance for any help anyone can offer.
Jack

Looking back I don't recall resetting the file rights after modifying the file and that was likely the root cause of my problems.
You should try the chmod command a couple of posts back.

JackinNC said:
Ok, I did the exact same thing and followed these instructions but haven't had any luck.
First, thanks lbloo and the folks who have responded for all the info here. I have downloaded JRO03D_grouper.zip and I am grateful for the tip to the toolkit.
When I have pushed JRO03D_grouper.zip to the N7, it appears to have worked, but I can't find it on the sdcard. I am pushing from the default location to /sdcard/. I then select "install zip from sdcard" and "choose zip from sdcard" but the only zip there is supersu (from Day 1).
For reference, this is CWM Recovery v 6.0.0.6.
Thanks in advance for any help anyone can offer.
Jack
Click to expand...
Click to collapse
What location did you push it to? /sdcard/?
Sent from my Nexus 7 using xda app-developers app

mvmacd said:
What location did you push it to? /sdcard/?
Click to expand...
Click to collapse
Yes. And, to further test, I created a little zip file called test.zip and pushed it to the tablet. I can see it just fine. It's just the grouper zip that I can't find.
Thanks
Jack

I just noticed a diff in filesize between the JRO03D_grouper.zip file I am using and one shown in a Youtube video entitled "how to put a rom to flash on a semi-bricked nexus 7 with recovery" by Youtube user metroid031993. (I'm too green to post outside links on XDA)
Mine is 261814702 bytes, the one shown in the video is 32650144 bytes.
Perhaps this is my problem, an invalid zip file. What do you think? And, can someone please tell me the correct size of JRO03D_grouper.zip?
Thanks
Jack
[Note to moderator(s): If I am heading off track in this thread, please don't hesitate to move it or to instruct me to create a new thread. I think the issue may have changed, but I have stayed here since this is where the conversation is for my root issue. Thx!]

JackinNC said:
can someone please tell me the correct size of JRO03D_grouper.zip?
Click to expand...
Click to collapse
Not sure what's up with the youtube video you're using, but 261814702 bytes is the correct size.

Visa Declined said:
Not sure what's up with the youtube video you're using, but 261814702 bytes is the correct size.
Click to expand...
Click to collapse
Thanks for the confirmation.
Ok, back to trying to figure out why it doesn't appear in CWM Recovery after I've pushed it...
---------- Post added at 11:19 AM ---------- Previous post was at 10:51 AM ----------
JackinNC said:
Ok, back to trying to figure out why it doesn't appear in CWM Recovery after I've pushed it...
Click to expand...
Click to collapse
Well, I got the grouper zip into /sdcard/ and was able to upgrade without losing anything. w00t!
Theory:
I was in the same adb "session" this time since I was using adb from the command line. Meaning, the daemon was still running from the first push I did. So, while I couldn't see the grouper zip after the first push (consistent with your experience, dark_samus), I could see it and upgrade with it after second push (also consistent). And, perhaps my previous attempts didn't work before because I was closing and opening the Nexus 7 Toolkit each time, therefore stopping and restarting the daemon, which meant that each push attempt was the first attempt for that "session."
I don't have any solid technical basis to support or refute that theory, it's just one possible theory that, if true, would result in the experience I had.
My problem is resolved. Thanks to everyone who contributed to this, I truly appreciate your help!
Jack

simms22 said:
reflash your ROM. it'll replace your build.prop with a good copy. don't wipe a thing, just reflash.
Click to expand...
Click to collapse
how to put the stock image if my n7 doesnt boot to android? pls help
i have CWM already

Either replace the complete system partition using 'fastboot flash',
or, probably less intrusive, boot into recovery mount system partition writeable and push build.prop manually using 'adb push'.
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
Either replace the complete system partition using 'fastboot flash',
or, probably less intrusive, boot into recovery mount system partition writeable and push build.prop manually using 'adb push'.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
my bad i already flash a fresh stock rom again, but thanks anyways...

[REQ} Stock Recovery for LG G2

Anyone have a link or a copy of the VZW G2 Stock Recovery?

http://forum.xda-developers.com/showthread.php?t=2448960

fenixnr said:
http://forum.xda-developers.com/showthread.php?t=2448960
Click to expand...
Click to collapse
I see a "return to stock" guide on that page. Thanks, but I'm looking for just the Recovery - not the entire ROM.

You can find it here http://downloads.codefi.re/autoprime/LG/LG_G2
just check your version.

Partager.info said:
You can find it here http://downloads.codefi.re/autoprime/LG/LG_G2
just check your version.
Click to expand...
Click to collapse
If I need D802 stock recovery I need to flash this?
http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware/10b_16G_partitions recovery.img?
Can I install this with TMRW or what is called recovery to get stock recovery yup?

Partager.info said:
You can find it here http://downloads.codefi.re/autoprime/LG/LG_G2
just check your version.
Click to expand...
Click to collapse
Downloaded the TOT file. I'm guessing the Recovery image is in it somewhere. I'm looking for JUST a Recovery zip.

rfarrah said:
Anyone have a link or a copy of the VZW G2 Stock Recovery?
Click to expand...
Click to collapse
My FLASHIFY backup of VS980 11A recovery. Unzip into flashify backup directory under recovery.

Steamer86 said:
My FLASHIFY backup of VS980 11A recovery. Unzip into flashify backup directory under recovery.
Click to expand...
Click to collapse
Can Someone Backup International D802 version? :/

Anyone have a backup of the att d800
Sent from my LG-D800 using XDA Premium 4 mobile app

Steamer86 said:
My FLASHIFY backup of VS980 11A recovery. Unzip into flashify backup directory under recovery.
Click to expand...
Click to collapse
THANK YOU, Sir.
Update:
Having trouble with Flashify. It doesn't see a recovery image, I guess. I tried putting the zip file, the extracted folder, AND the single file into Flashify's Recovery folder. No go. It doesn't see a file to flash for some reason. Am I doing something wrong?

Single file would be the way to go. No clue, have never actually used it. Just backed it up. Sorry. Maybe just may work for me. Shouldn't you be able to remove from a tot or extracted kdz bin?

Reverting to stock recovery in order to accept OTA updates ...
For anyone trying to apply any OTA updates, e.g., from Verizon, after modding your phone, restoring back to your previous version and wanting to go back to stock (for WHATEVER reason):
As you may have found out, trying to apply OTA updates with a custom recovery seemingly bricks your phone (it doesn't really, there are some nifty "dd" Linux commands you can use to get your phone to break out of the boot-loop it's stuck in).
Since I went back to my previously backed up stock ROM, I also wanted to revert to my stock recovery so that I could accept Verizon's OTA updates (if only because the popup reminders are annoying and a drain of the battery).
Here are the steps I followed, thanks to this thread:
- I downloaded the recovery.img from the link in Partager.info's post (#4) (choose the model subfolder which corresponds to your variant of the G2).
- I used "adb push" to copy the file from my computer to /sdcard (good to have on the sdcard partition as the rest get blown away when you flash a ROM)
- I installed "Flashify (for root users)" (found in the Play Store) on my phone
- I ran Flashify and chose the stock recovery file I downloaded which was in the /sdcard folder as expected (no need to put image files in specific folders; whatever works best for you)
- It flashed it in a blink of the eye and asked me to reboot; I did and it's worth mentioning I got the Android with the triangle (*clench*)
- I held the power button and forced it to shut down/reboot
- Upon reboot, I saw the Verizon boot animation (*unclench*)
- I checked for an update from Verizon and it prompted me to reboot and apply it; I clicked "Install now"
- It successfully rebooted and applied the update; what a relief to see the firmware update splash screen
Pfew. Thanks again, Partager.info and Steamer86.

hii
hello . fırstly sorry my bad english..I have lg g2 D802 32 gb.. I have used so much roms for my phone after that i wanted to turn stock rom . and I uptade 6UR/TURKEY_OPEN_16 V10C LGD802 this rom to my phone , firstly gıve error and which is wanted to pın . i tried again and i could installed to rom . but i saw that my phones memory decrease 16 gb. i tried more things suchs as make root again, and ınstall custom roms, install euro stock roms but no cant solve this problem..MY PHONE MEMory was 32 gb BUT NOW 16 gb ... i hope you can help me

Guys Can someone hlep me with a stock recovery for my lg g2 d802 italy vodafone 10c?
Thx a lot!

Root stock 5.1 - Ub only

I'm no expert, so maybe a better way, but it worked for me, so try if you want...
Needed: stock ftf, (I used this https://shry.me/9L9OQ); CM boot img; TWRP img; Flashtool; fastboot, Supersu flashable zip.
1. Flash stock ftf with Flashtool, boot phone, and check 'android debugging ' and 'unknown sources'
2. Power off, hold volume up, and connect in fastboot mode
3. cd to adb directory on PC, type 'fastboot flash boot (CM file).img', and 'fastboot flash recovery (TWRP file).img'
4. disconnect phone, power on, volume up when you see led to enter recovery. Install > Supersu zip.
5. Power off, open Flashtool, and again flash ftf, but in 'exclude' box on right side, check everything except 'boot bundle, kernel, and fotakernel. (hopefully I'm remembering right).
When done, reboot, and you're rooted.

@levone1 link isn't working! pls fix.

itskapil said:
@levone1 link isn't working! pls fix.
Click to expand...
Click to collapse
Sorry, the parentheses got included in link. It's better now. By the way, I got it from here http://forum.xda-developers.com/son...al/ftf-xperia-z1-compact-d5503-5-1-1-t3201650.
Also, here's a couple more links to make it easier...
https://mega.nz/#!E4UQwIoZ!UFpur2wY3tIAU7SdjuEg5fUA6N4BAVwX_TeK_CFpTyo
https://mega.nz/#!k5E0kQpC!XdTudAe5ISAVyfQAHHMkgvjmNuY6TDxm62HzyOAEgmU
I'll post a CM boot link later if needed, or just download one.

http://forum.xda-developers.com/son...root-init-d-support-recovery-busybox-t3202799 is a nice addition to this method, (to get recovery and busybox after root). You can flash it with Rashr app on phone with root, (version 2.2.8).

levone1 said:
I'm no expert, so maybe a better way, but it worked for me, so try if you want...
Needed: stock ftf, (I used this https://shry.me/9L9OQ); CM boot img; TWRP img; Flashtool; fastboot, Supersu flashable zip.
1. Flash stock ftf with Flashtool, boot phone, and check 'android debugging ' and 'unknown sources'
2. Power off, hold volume up, and connect in fastboot mode
3. cd to adb directory on PC, type 'fastboot flash boot (CM file).img', and 'fastboot flash recovery (TWRP file).img'
4. disconnect phone, power on, volume up when you see led to enter recovery. Install > Supersu zip.
5. Power off, open Flashtool, and again flash ftf, but in 'exclude' box on right side, check everything except 'boot bundle, kernel, and fotakernel. (hopefully I'm remembering right).
When done, reboot, and you're rooted.
Click to expand...
Click to collapse
Links to these files?

NRG1975 said:
Links to these files?
Click to expand...
Click to collapse
3rd post has everything but CM boot. I'll post it if you need it. Or you could just download a ROM and extract.

NRG1975 said:
Links to these files?
Click to expand...
Click to collapse
This should work for boot IMG - https://mega.nz/#!Jh0DETBQ!E-9WTlINpfq5r3PIiKaIXRId7ar8g3c8YHTJha1N6LM

This really is not that easy .... While it may be the easiest way, it is far from easy with Win 8 or Win 10. I am gonna forego root till an easier way is found. Thank you for your efforts.

No Busybox
I was able to root my phone following your method. It was easy.. however I can't install busybox or use apps which requires busybox installation. Is there any workaround for this issue?!

aravindclpy said:
I was able to root my phone following your method. It was easy.. however I can't install busybox or use apps which requires busybox installation. Is there any workaround for this issue?!
Click to expand...
Click to collapse
Use stericson busybox from play store. I tried the other one and it didn't work, but that one worked for me. You can also manual push busybox if you have to.

aravindclpy said:
I was able to root my phone following your method. It was easy.. however I can't install busybox or use apps which requires busybox installation. Is there any workaround for this issue?!
Click to expand...
Click to collapse
You can also use this - http://forum.xda-developers.com/son...root-init-d-support-recovery-busybox-t3202799
Since this came out, I recommend it over my method, since everything is included, and it's faster than using FT a second time.

Hey,
Usually this kind of stuff isn't a problem for me, but here I'm stuck at step 4.
When I try to flash superSU.zip, TWRP reboots by itself.
Also when TWRP boots, I'm asked to choose "keep read only" or "allow modifications" for the system partition. Both choices results in a reboot of TWRP.
Any idea ?
(I tried with the method in the link above, same thing happens)

Jackhass said:
Hey,
Usually this kind of stuff isn't a problem for me, but here I'm stuck at step 4.
When I try to flash superSU.zip, TWRP reboots by itself.
Also when TWRP boots, I'm asked to choose "keep read only" or "allow modifications" for the system partition. Both choices results in a reboot of TWRP.
Any idea ?
(I tried with the method in the link above, same thing happens)
Click to expand...
Click to collapse
Only time I ever got that from twrp was after doing ta update and booting into the new recovery. I just picked 'allow' and everything was fine. Are you booting into recovery the new way, or old? Are you using all of the files I posted, or a different boot, etc? My first shot would be to try a different recovery IMG, like an older twrp,and see if it works. I did all the above with the old recovery method, (wait for LED and vol up). Let me know...

@levone1 Thanks for your answer
I redownloaded all your files, did it again (exactly as it's said in the OP) and... it worked. I've done nothing more or less than last time I tried.. Unexplainable
Thanks anyway

Jackhass said:
@levone1 Thanks for your answer
I redownloaded all your files, did it again (exactly as it's said in the OP) and... it worked. I've done nothing more or less than last time I tried.. Unexplainable
Thanks anyway
Click to expand...
Click to collapse
Great... If you want busybox, etc., see the posts before yours.

Update (.216)
Just bumping thread for new fw. After FT flash, there is no r/w access. Can't use method in this forum without busybox, so to get busybox, just download nut dual recovery 'installer' option, and run on pc. Steps are same otherwise. I posted an ftf here - http://forum.xda-developers.com/sony-xperia-z1-compact/general/216-stock-ftf-read-flashing-t3243728

levone1 said:
Just bumping thread for new fw. After FT flash, there is no r/w access.
Click to expand...
Click to collapse
The steps I took with UL BL...
Used the Flashtool and XperiFirm to download and flash 216.
Hot booted 368 kernel and flashed SU zip, confirmed root with TB and Root Explorer after reboot to stock 216 kernel.
Installed Busybox from Play Store.
Extracted kernel.sin from ftf and used @[NUT]'s Kernel Builder to add XZDualRecovery.
Extracted boot.img from zip and flashed with Fastboot.
Now I'm in the process of removing bloatware then I'm going to theme it.

[n910c] go back to stock rom from cm13. [bootloop/ imei/network problem fixed 100%]

MY GUIDES TOWARDS VICTORY:-
FR34K-B1B0
vaskodogamagmail
HmanA6399
Peontikos_Desmos
I am truly very much grateful to you guys! Owe you!!!
TOOLS YOU NEED:-
EFS PROFESSIONAL (PC) [Get it here!]
TWRP Recovery Installed Phone [Get it here!]
BUSY BOX PRO (APK) [Get it Here!]
ODIN (PC)
N910C PIT FILE (FIND ONE FOR YOUR EXACT PHONE MODEL!)
APPROPRIATE STOCK ROM. (AS PER YOUR CURRENT BASEBAND VERSION!)
ROOT EXPLORER PRO (APK).[Get it here!]
Okay, Now carefully follow my instructions.
BOOTLOOP FIX
Make a TWRP NANDROID BACKUP of your current properly working ROM [eg: CM13].
Make sure that your phone is rooted. Then, Install Busybox (Run the application and then install busybox) and Root Explorer in your current custom ROM (Don't forget to grant root permissions).
In Root Explorer, Go to root (R/w mode enabled), Enter EFS folder, Copy the following files to your SD card.
imei (folder)
.nv_data.bak (file)
(Keep these two things safe somewhere, Because you will need it later to fix your IMEI)
In your phone settings, make sure 'USB debugging' is enabled from 'Settings->Developer Options->'.
Run 'EFS Professional' on PC. (On your PC, Make Sure that you have installed 'Samsung USB Drivers' from here & 'Google adb USB drivers' from here.)
Connect the phone to PC, Grant root access to your PC by confirming the dialog box showing up in the phone.
On EFS Professional, Go to "Samsung Tools" tab , Go to "Other tools" and select "Format EFS Folder" then click "Execute".
Power off the phone, Reboot into TWRP Recovery.
Wipe all data/factory reset.
Power down the Phone and Reboot into 'Download' mode.
Start ODIN on PC and Connect the Phone.
In Odin, Load the 'PIT' File, Check 'Re-partition' and Load your Stock ROM file to AP. Click Start to flash the stock firmware.
VOILA!! ONCE FLASHING IS DONE, YOUR PHONE WILL BE AUTOMATICALLY REBOOTED INTO YOUR STOCK ROM WITHOUT ANY FRUSTRATING BOOTLOOPS !!!!!!
NOW YOU PEOPLE WILL BE FACING A 'NOT REGISTERED ON THE NETWORK' PROBLEM. DON'T WORRY! LET'S FIX IT! FOLLOW MY LEAD!
EFS / IMEI FIX
Boot to your new stock ROM.
Install BusyBox (Run the application and then install busybox) and RootExplorer.
Start 'root explorer', Go to root ((R/w mode enabled), Go to EFS folder
Delete all the files and Restart the phone.
Again repeat 'Step 3'.
Now you will see some files again. Now, carefully delete only the 'imei' folder and 'nv_data.bin' file.
Make two copies of your previous ROM backup file ".nv_data.bak" into the new ROM's EFS folder and rename it to "nv_data.bin" and "nv_data.bin.bak" respectively.
Finally, Reboot the Device.
THATS IT! YOU NOW GOT YOUR NETWORK BACK!!! ENJOY THE STOCK ROM!!!!
(Keep a TWRP Nandroid backup of your Stock ROM. It will help you out from other troubles in the future!)
Hit 'Thanks' If I helped you out!! Ask for more assistance!
Cheers!
Arun

Grrrrr8??
Sent from my HTC Desire 820s dual sim using Tapatalk

Can anyone confirm this works?
I attempted this method with not much luck in the end

Same, when i open the EFS folder / copy it with Root Explorer, and it say need Root Access. When i press okay the phone is rebooting. Please someone help me.

I'm glad you got your phone back!
But I still don't know what the EFS folder has to do with the bootloops. I guess we should try the following
1- Make an EFS backup in your CM13 rom (just in case) but don't delete anything.
2-Go to recovery and wipe data cache and dalvik.
3-Reboot in download mode and connect your phone to your pc, then open ODIN.
4-Load your .PIT file and tick 'Repartition". Add your stock TW 5.1.1 rom and flash everything
5-Wait until it boots and check if you have signal.
I've used CM12 and reverted to stock Lollipop doing these steps (even without repartitioning) and worked just fine but maybe CM13 partitioning is different. Can anyone follow these steps and report what happend? Remember to make an EFS backup (as I said, just in case) before.

AlStarsKyz said:
Same, when i open the EFS folder / copy it with Root Explorer, and it say need Root Access. When i press okay the phone is rebooting. Please someone help me.
Click to expand...
Click to collapse
Give me more details about your phone, So that I can help you!

ColtD said:
Can anyone confirm this works?
I attempted this method with not much luck in the end
Click to expand...
Click to collapse
Tell me what happened for u. I will assist you.

galaxynote2 said:
I'm glad you got your phone back!
But I still don't know what the EFS folder has to do with the bootloops. I guess we should try the following
1- Make an EFS backup in your CM13 rom (just in case) but don't delete anything.
2-Go to recovery and wipe data cache and dalvik.
3-Reboot in download mode and connect your phone to your pc, then open ODIN.
4-Load your .PIT file and tick 'Repartition". Add your stock TW 5.1.1 rom and flash everything
5-Wait until it boots and check if you have signal.
I've used CM12 and reverted to stock Lollipop doing these steps (even without repartitioning) and worked just fine but maybe CM13 partitioning is different. Can anyone follow these steps and report what happend? Remember to make an EFS backup (as I said, just in case) before.
Click to expand...
Click to collapse
You can't simply restore a lollipop backup into marshmallow. Trust me, It won't work.

arunkrishnanr said:
Give me more details about your phone, So that I can help you!
Click to expand...
Click to collapse
What can i say to you?

AlStarsKyz said:
What can i say to you?
Click to expand...
Click to collapse
Where do you face the problem while doing this method?

arunkrishnanr said:
Where do you face the problem while doing this method?
Click to expand...
Click to collapse
When i'm open the EFS folder with Root Explorer, my phone got reboot automatically. And i try to copy it too and it's still rebooting. I got that after receive the verification root and i press ok, and i my phone reboot it self automatically.

AlStarsKyz said:
When i'm open the EFS folder with Root Explorer, my phone got reboot automatically. And i try to copy it too and it's still rebooting. I got that after receive the verification root and i press ok, and i my phone reboot it self automatically.
Click to expand...
Click to collapse
Try again. Use CF root to properly root your stock ROM. And then flash TWRP Recovery. Then setup busybox and root explorer in your stock rom. Make a backup of your EFS folder by copying it somewhere safe.
I used this method and I worked fine for me.

arunkrishnanr said:
Try again. Use CF root to properly root your stock ROM. And then flash TWRP Recovery. Then setup busybox and root explorer in your stock rom. Make a backup of your EFS folder by copying it somewhere safe.
I used this method and I worked fine for me.
Click to expand...
Click to collapse
Btw, i got this problem only on CM13, but when in stock it's working to open the EFS folder.

At least credit me

FR34K-B1B0 said:
At least credit me
Click to expand...
Click to collapse
May I ask why?

arunkrishnanr said:
May I ask why?
Click to expand...
Click to collapse
May i ask help me?

arunkrishnanr said:
May I ask why?
Click to expand...
Click to collapse
Because you're using the method I found?

FR34K-B1B0 said:
Because you're using the method I found?
Click to expand...
Click to collapse
Yes! Im sorry.. you are the one who helped me in the end.. i will credit u for sure..

AlStarsKyz said:
May i ask help me?
Click to expand...
Click to collapse
Sure. First of all, if your phone model is N910C and you are facing the problem, I would recommend you to try again my methods carefully. If you are facing any difficulty, Please let me know!

AlStarsKyz said:
Btw, i got this problem only on CM13, but when in stock it's working to open the EFS folder.
Click to expand...
Click to collapse
If your stock rom is working, then all you have to do is to follow the steps in the 'IMEI Fix'. Try that! But I hope you have made the backup from cm13.