Develop Bugs

[Q] Help flashing HTC One X

Hey guys, I had Android HD Revolution running on my phone, but I hated Sense so I decided to flash CM 10.1 RC4, It was super smooth and good, but battery life was horrible. I then flashed ICJ AOSP to see if it made any difference, same thing. I want to now flash back to a Sense rom (Blade Elite) but I can't seem to get it to flash. I wipe my phone in recovery, wipe partition, wipe dalvik cache, all the usual stuff. Then I enter fastboot, erase cache but then when going to boot the boot.img right after it is done the phone reboots, does a little vibration thing then goes onto a htc screen and just stays there instead of going back to the hboot so I can enter recovery. Then If i hold pwr and vol down to enter recovery and press reboot now it is stuck on boot screen and will not load. The only ROM I can flash is CM10.1 (the only AOSP rom Ive tried) but it doesn't work 100% e.g wifi does not turn on and I can't even flash my nanroid backup of my original rom. HELP GUYS PLEASE?

Jonah6 said:
Hey guys, I had Android HD Revolution running on my phone, but I hated Sense so I decided to flash CM 10.1 RC4, It was super smooth and good, but battery life was horrible. I then flashed ICJ AOSP to see if it made any difference, same thing. I want to now flash back to a Sense rom (Blade Elite) but I can't seem to get it to flash. I wipe my phone in recovery, wipe partition, wipe dalvik cache, all the usual stuff. Then I enter fastboot, erase cache but then when going to boot the boot.img right after it is done the phone reboots, does a little vibration thing then goes onto a htc screen and just stays there instead of going back to the hboot so I can enter recovery. Then If i hold pwr and vol down to enter recovery and press reboot now it is stuck on boot screen and will not load. The only ROM I can flash is CM10.1 (the only AOSP rom Ive tried) but it doesn't work 100% e.g wifi does not turn on and I can't even flash my nanroid backup of my original rom. HELP GUYS PLEASE?
Click to expand...
Click to collapse
Which recovery do you have installed ?
Also post your CID info. (fastboot oem readcid)

fietspompje said:
Which recovery do you have installed ?
Also post your CID info. (fastboot oem readcid)
Click to expand...
Click to collapse
i have clockwork mod recovery 5.8.4.0 and CID is (bootloader) DEBUG: cid: OPTUS001

run this command in fastboot: fastboot oem readcid
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

fietspompje said:
run this command in fastboot: fastboot oem readcid
Click to expand...
Click to collapse
CID is (bootloader) DEBUG: cid: OPTUS001

Jonah6 said:
CID is (bootloader) DEBUG: cid: OPTUS001
Click to expand...
Click to collapse
Go to this thread: http://forum.xda-developers.com/showthread.php?t=1975140
CTRL + F and enter your CID (OPTUS001)
Then you will find a download link to a nandroid backup. (which are made with CWM)
Download a backup from there (make sure you are downloading the one with the correct CID) and restore it in CWM.
Don't forget the fastboot flash boot boot.img after you've restored the backup.

fietspompje said:
Go to this thread: http://forum.xda-developers.com/showthread.php?t=1975140
CTRL + F and enter your CID (OPTUS001)
Then you will find a download link to a nandroid backup. (which are made with CWM)
Download a backup from there (make sure you are downloading the one with the correct CID) and restore it in CWM.
Don't forget the fastboot flash boot boot.img after you've restored the backup.
Click to expand...
Click to collapse
So after I flash this I can go back to flashing another sense rom? 4.1.X?

Jonah6 said:
So after I flash this I can go back to flashing another sense rom? 4.1.X?
Click to expand...
Click to collapse
Well this is a stock sense rom, but if you want you can flash an another one, but stock is the most safe.

fietspompje said:
Well this is a stock sense rom, but if you want you can flash an another one, but stock is the most safe.
Click to expand...
Click to collapse
I tried flashing my own nandroid backup didnt work. I got boot.img from mounting storage in clockwork and flashed boot img but it wouldn't boot either. I'll try it out though. And btw which version do I download.
Nandroid Backup / Mirror 3.14.980.27 CID OPTUS001 thanks to mafia187
Nandroid Backup 2.17.980.6 CID OPTUS001 thanks to mafia187

Jonah6 said:
I tried flashing my own nandroid backup didnt work. I got boot.img from mounting storage in clockwork and flashed boot img but it wouldn't boot either. I'll try it out though. And btw which version do I download.
Nandroid Backup / Mirror 3.14.980.27 CID OPTUS001 thanks to mafia187
Nandroid Backup 2.17.980.6 CID OPTUS001 thanks to mafia187
Click to expand...
Click to collapse
Take the most recent one, (3.14.980.27)

fietspompje said:
Take the most recent one, (3.14.980.27)
Click to expand...
Click to collapse
Is the way I tried to flash my nanroid recovery correct? I wiped everything, then mounted sd card go the boot .img from the recovery rom (which was my stock jb) then I booted the boot.img and then flashed the backup. Do I need to do anything with the "recovery.img"?
EDIT: When I try flash my nandroid backup boot.img I get this error.
C:\fastboot>fastboot boot boot.img
creating boot image...
creating boot image - 8390656 bytes
downloading 'boot.img'...
OKAY [ 1.074s]
booting...
FAILED (remote: reproduce boot image with on-flash ramdisk error)
finished. total time: 1.118s
Also one thing you did not answer, is that when I flash a boot.img the phone restarts and vibrates instead of going to hboot.

Jonah6 said:
Is the way I tried to flash my nanroid recovery correct? I wiped everything, then mounted sd card go the boot .img from the recovery rom (which was my stock jb) then I booted the boot.img and then flashed the backup. Do I need to do anything with the "recovery.img"?
EDIT: When I try flash my nandroid backup boot.img I get this error.
C:\fastboot>fastboot boot boot.img
creating boot image...
creating boot image - 8390656 bytes
downloading 'boot.img'...
OKAY [ 1.074s]
booting...
FAILED (remote: reproduce boot image with on-flash ramdisk error)
finished. total time: 1.118s
Also one thing you did not answer, is that when I flash a boot.img the phone restarts and vibrates instead of going to hboot.
Click to expand...
Click to collapse
That is very strange.. You are using the boot.img out of the nandroid backup right (which you just downloaded, you need to download the nandroid backup like i said, put it on your SD card in the "ClockWorkMod" folder, then copy the boot.img to your fastboot location, flash the boot.img and at last do a restore in CWM)?
And no, don't flash the recovery.img, that will only break your current recovery.

fietspompje said:
That is very strange.. You are using the boot.img out of the nandroid backup right (which you just downloaded)?
And no, don't flash the recovery.img, that will only break your current recovery.
Click to expand...
Click to collapse
I get that error using the backup of my own nandroid. The one you linked me the server is slow (2 hours to download) but why wouldn't it work on my own nandroid backup? And why does phone reboot when other boot.img is flashed.

Jonah6 said:
I get that error using the backup of my own nandroid. The one you linked me the server is slow (2 hours to download) but why wouldn't it work on my own nandroid backup? And why does phone reboot when other boot.img is flashed.
Click to expand...
Click to collapse
I really have no idea, i've also had that with my own Phone, after i downloaded the nandroid backup, it worked like a charm, maybe i can download the files faster and re upload it for you.
Edit: My Download is done in 10 minutes. I'll upload them to my FTP server, do you know how FTP works ?

fietspompje said:
I really have no idea, i've also had that with my own Phone, after i downloaded the nandroid backup, it worked like a charm, maybe i can download the files faster and re upload it for you.
Edit: My Download is done in 10 minutes. I'll upload them to my FTP server, do you know how FTP works ?
Click to expand...
Click to collapse
That sounds good, and no I do not really know how FTP works. :/

Jonah6 said:
That sounds good, and no I do not really know how FTP works. :/
Click to expand...
Click to collapse
Lucky enough, i have my own cloud :angel: :
http://owncloud.markdaleman.nl/
user: xda
pass: I will send you a private message with the pass.
You will find the Nandroid backup after you login.

fietspompje said:
Lucky enough, i have my own cloud :angel: :
http://owncloud.markdaleman.nl/
user: xda
pass: I will send you a private message with the pass.
You will find the Nandroid backup after you login.
Click to expand...
Click to collapse
Thankyou very much friend! Only 27 minutes for download now! You were very helpful, thanks a bunch :good: :fingers-crossed:
When installing this. Do I wipe, then flash boot.img and then install zip.
Or wipe, install zip and then flash boot.img?

Jonah6 said:
Thankyou very much friend! Only 27 minutes for download now! You were very helpful, thanks a bunch :good: :fingers-crossed:
Click to expand...
Click to collapse
No problem at all! Let's hope we can fix your phone again! :good:

fietspompje said:
No problem at all! Let's hope we can fix your phone again! :good:
Click to expand...
Click to collapse
When installing this. Do I wipe, then flash boot.img and then install zip.
Or wipe, install zip and then flash boot.img?

Jonah6 said:
When installing this. Do I wipe, then flash boot.img and then install zip.
Or wipe, install zip and then flash boot.img?
Click to expand...
Click to collapse
You Wipe, flash the boot.img than don't install zip, but extract zip to SD and restore it via CWM

how do i backup my stock recovery?

As title says, im going to install cwm but i would like to make a backup of my stock recovery for ota updates but im not totaly sure on how to do that properly, thanks

RENEGAD3 said:
As title says, im going to install cwm but i would like to make a backup of my stock recovery for ota updates but im not totaly sure on how to do that properly, thanks
Click to expand...
Click to collapse
Connect phone to PC, boot into bootloader mode and type fastboot boot name_of_recovery.img that'll just boot the custom recovery as opposed to flashing it, that way you can make a nandroid backup of all partitions including stock recovery.

Great thanks very much mate

RENEGAD3 said:
As title says, im going to install cwm but i would like to make a backup of my stock recovery for ota updates but im not totaly sure on how to do that properly, thanks
Click to expand...
Click to collapse
The guys method of using recovery to backup recovery will only work on Philz… Not twrp as it does not always backup stock recovery properly. The proper way to backup stock recovery is..
1. Root your phone, which can be done by towel root or by just booting a recovery like he said,
fastboot boot twrporwhatever.img, then flash supersu
2. Boot phone that has stock recovery
3. adb shell
4. su "watch your phone to grant root adb access if you haven't ever done it"
5. dd if=/dev/block/mmcblk0p43 of=/sdcard/recovery.img
6. This will put flashable recovery.img on your internal sd card. Copy this and save it for later
7. "fastboot flash recovery recovery.img" will get you back to stock recovery, "fastboot flash recovery twrporwhatever.img" to flash custom recovery.

Just a question
When restoring to stock.Should I flash just the recovery.img or I have to flash kernel.img etc files together with that??

tabandronil said:
When restoring to stock.Should I flash just the recovery.img or I have to flash kernel.img etc files together with that??
Click to expand...
Click to collapse
Not exactly sure what you mean.
If you are just trying to restore stock recovery, than no you do not have to flash kernel.
If you are trying to restore stock ROM, you have to flash the whole ROM, not just the kernel.
Restoring stock recovery alone does not restore the stock ROM (that may be part of your confusion).

Thanks for clarifying.
I don't have a clear idea about flashing. I just read the instructions in the forum that during CWM flashing I would need those rom dumps and replace the recovery.img and misc.img with the one provided and also use parameter file or something. So I wanted to know about the failsafe to restore in case I mess-up. So I thought to restore I might need to do the same but now with my original recovery.img dump file.
---------- Post added at 12:14 AM ---------- Previous post was at 12:08 AM ----------
Also I don't know what parameter file I should use during restoring. Sorry I am a newbie.

tabandronil said:
Thanks for clarifying.
I don't have a clear idea about flashing. I just read the instructions in the forum that during CWM flashing I would need those rom dumps and replace the recovery.img and misc.img with the one provided and also use parameter file or something. So I wanted to know about the failsafe to restore in case I mess-up. So I thought to restore I might need to do the same but now with my original recovery.img dump file.
---------- Post added at 12:14 AM ---------- Previous post was at 12:08 AM ----------
Also I don't know what parameter file I should use during restoring. Sorry I am a newbie.
Click to expand...
Click to collapse
Its not clear to me what you're trying to do exactly, or what guide you are following (can you link it?).
Kinda sounds like you may be making it more complicated than it needs to be.

Or just use flashify after rooting.
Sent from my SM-T805 using XDA Free mobile app

The link you asked http://forum.xda-developers.com/showthread.php?p=46108430

RENEGAD3 said:
As title says, im going to install cwm but i would like to make a backup of my stock recovery for ota updates but im not totaly sure on how to do that properly, thanks
Click to expand...
Click to collapse
After rooting your mobile install rashr
By this you can backup your stock recovery to your sdcard
Sent from my iris SELFIE50 using XDA Free mobile app

tabandronil said:
The link you asked http://forum.xda-developers.com/showthread.php?p=46108430
Click to expand...
Click to collapse
What the heck is an Iball Slide? You have an HTC M8? If so, you should never be using any guides intended for other devices. Could cause your M8 permanent damage.
If your device is the IBall Slide, this forum section is specifically for the HTC M8. Likewise, don't do anything here that isn't specific to your device, except at your own risk.

an0ther said:
The guys method of using recovery to backup recovery will only work on Philz… Not twrp as it does not always backup stock recovery properly. The proper way to backup stock recovery is..
1. Root your phone, which can be done by towel root or by just booting a recovery like he said,
fastboot boot twrporwhatever.img, then flash supersu
2. Boot phone that has stock recovery
3. adb shell
4. su "watch your phone to grant root adb access if you haven't ever done it"
5. dd if=/dev/block/mmcblk0p43 of=/sdcard/recovery.img
6. This will put flashable recovery.img on your internal sd card. Copy this and save it for later
7. "fastboot flash recovery recovery.img" will get you back to stock recovery, "fastboot flash recovery twrporwhatever.img" to flash custom recovery.
Click to expand...
Click to collapse
Very confused with your steps. In step 1, I install custom recovery twrp and flash supersu? then in step 2, how can I boot up stock recovery while in the custom recovery? Did you mean I need to flash back to stock recovery? if so that should be step 2.

MaXi32 said:
Very confused with your steps. In step 1, I install custom recovery twrp and flash supersu? then in step 2, how can I boot up stock recovery while in the custom recovery? Did you mean I need to flash back to stock recovery? if so that should be step 2.
Click to expand...
Click to collapse
In step 1, you boot recovery without actually flashing it, using the indicated fastboot command. The TWRP file resides on your computer, so its sort of a "remote boot".

an0ther said:
The guys method of using recovery to backup recovery will only work on Philz… Not twrp as it does not always backup stock recovery properly. The proper way to backup stock recovery is..
1. Root your phone, which can be done by towel root or by just booting a recovery like he said,
fastboot boot twrporwhatever.img, then flash supersu
2. Boot phone that has stock recovery
3. adb shell
4. su "watch your phone to grant root adb access if you haven't ever done it"
5. dd if=/dev/block/mmcblk0p43 of=/sdcard/recovery.img
6. This will put flashable recovery.img on your internal sd card. Copy this and save it for later
7. "fastboot flash recovery recovery.img" will get you back to stock recovery, "fastboot flash recovery twrporwhatever.img" to flash custom recovery.
Click to expand...
Click to collapse
redpoint73 said:
In step 1, you boot recovery without actually flashing it, using the indicated fastboot command. The TWRP file resides on your computer, so its sort of a "remote boot".
Click to expand...
Click to collapse
Does samsung work with fastboot command? when i use the fastboot command it said waiting for devices. The fastboot devices is empty here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My phone is Samsung Galaxy Note 3 - SM 9005

MaXi32 said:
Does samsung work with fastboot command? when i use the fastboot command it said waiting for devices. The fastboot devices is empty here:
My phone is Samsung Galaxy Note 3 - SM 9005
Click to expand...
Click to collapse
I do not believe that Samsung devices have fastboot.

redpoint73 said:
I do not believe that Samsung devices have fastboot.
Click to expand...
Click to collapse
Thanks... any other way that I can backup my stock recovery.img without installing custom recovery like TWRP/CMW. The reason why I dont want to install this custom recovery is to prevent the Current Binary status to Custom. hmmm.. i have search al lot but mostly they said about using fastboot. unfortunately fastboot doesn't work on Samsung

MaXi32 said:
Thanks... any other way that I can backup my stock recovery.img without installing custom recovery like TWRP/CMW. The reason why I dont want to install this custom recovery is to prevent the Current Binary status to Custom. hmmm.. i have search al lot but mostly they said about using fastboot. unfortunately fastboot doesn't work on Samsung
Click to expand...
Click to collapse
Post to the forum section for your device, and see if others there can help you.

m8, stock, s-on,rooted, 5.0.1, twrp2.8.6.1 latest, only dragon-fi sound mod and custom battery indicator mods installed.
made nandroid backup of rom via twrp before and after mods.
so i couldnt make stock recovery backup. can you share link and guide me , i seen the thread named ruu, stock recoveries,cids, etc, but i could not understand what exactly and only is for me, and now what should i do to get OTA if its available , if sense 7 comes then also i need to stock recovery for getting it? or its for only firmware updates?

wasim9283 said:
m8, stock, s-on,rooted, 5.0.1, twrp2.8.6.1 latest, only dragon-fi sound mod and custom battery indicator mods installed.
made nandroid backup of rom via twrp before and after mods.
so i couldnt make stock recovery backup. can you share link and guide me , i seen the thread named ruu, stock recoveries,cids, etc, but i could not understand what exactly and only is for me, and now what should i do to get OTA if its available , if sense 7 comes then also i need to stock recovery for getting it? or its for only firmware updates?
Click to expand...
Click to collapse
You need the stock ROM and stock recovery in order to be able to install future OTAs (your phone is already up to date, so this would only be for future OTAs).
As long as you have a TWRP backup of the stock ROM without any changes to the /system partition (root is ok) you can just use that, instead of downloading a stock nandroid from the collection thread.
For stock recovery, you need 4.16.401 stock recovery.

M8 Stock recovery

hey XDA, I've got an M8 on Wind Mobile with clockworkmod and a stock ROM, and there's a system update I can't take without the stock recovery. I searched all over the place, but couldn't find the correct recovery. Can someone point me to the download or upload the stock recovery from their phone pretty please? The CID on this phone is GLOBA001. Bootloader unlocked, and S-ON.

Download OTA, select install later. Copy OTA zip from internal storage/Download to PC.
Open OTA zip with 7-zip, open firmware.zip, extract out recovery.img
Use this extracted recovery.img then continue OTA

Ninja'd......

ckpv5 said:
Download OTA, select install later. Copy OTA zip from internal storage/Download to PC.
Open OTA zip with 7-zip, open firmware.zip, extract out recovery.img
Use this extracted recovery.img then continue OTA
Click to expand...
Click to collapse
I'll give that a try, thanks

Hey, I downloaded the OTA but I cant find the file anywhere. I tried OTA snatcher, but nothing happens. I cant even find the file at all. I do have root. how else can I get the OTA onto my PC?
EDIT: Never mind I got it. flashed the recovery but its still not taking the update, it just hangs on the white htc screen. cant boot into the stock recovery at all.
Maybe I'll just start a new thread then...

There is no need for a new thread. Keep everything in one thread. So anyone willing to help you can easily find info on your problem.
Have you try press & hold both power and volume up button, when it goes black quickly release both buttons and press & hold volume down button. This will take youto hboot then select recovery and check whether stock recovery is properly installed.

ckpv5 said:
There is no need for a new thread. Keep everything in one thread. So anyone willing to help you can easily find info on your problem.
Have you try press & hold both power and volume up button, when it goes black quickly release both buttons and press & hold volume down button. This will take youto hboot then select recovery and check whether stock recovery is properly installed.
Click to expand...
Click to collapse
tried that many times. When I select recovery, it just hangs on the white htc screen forever, never booting into the recovery and I have to force reboot it. The only recovery that seems to boot is clockworkmod...

Just forget about entering the stock recovery for awhile as there is no reason for you to go in there except to check the error log when doing update.
After you installed the stock recovery (fastboot flash recovery recovery.img), reboot and do OTA again, download and select install ... what happen then ?

ckpv5 said:
Just forget about entering the stock recovery for awhile as there is no reason for you to go in there except to check the error log when doing update.
After you installed the stock recovery (fastboot flash recovery recovery.img), reboot and do OTA again, download and select install ... what happen then ?
Click to expand...
Click to collapse
Exactly the same thing...reboots, and just hangs on the white screen until I force reboot

bbmaster123 said:
Exactly the same thing...reboots, and just hangs on the white screen until I force reboot
Click to expand...
Click to collapse
Then it boot back to your old version without OTA updating ?
What's your old version no. ?
I know WIND is a rare version around here, don't see any stock backup anywhere.

ckpv5 said:
Then it boot back to your old version without OTA updating ?
What's your old version no. ?
I know WIND is a rare version around here, don't see any stock backup anywhere.
Click to expand...
Click to collapse
Yes, then it boots back up normally into the old version, 4.4.2 and asks to apply the update again.

bbmaster123 said:
Yes, then it boots back up normally into the old version, 4.4.2 and asks to apply the update again.
Click to expand...
Click to collapse
I feel it's odd that it didn't go to recovery when you correctly installed a stock recovery. If the recovery image is wrong version, it still go to recovery and give error mark (the famous red triangle) but yours it just hang .. I run out of idea.
If you have time, maybe you can make a nandroid backup of boot & system (don't need data as it contains your data) and upload for me to have a look at it. Then I can rebuild the nandroid for others too. So far I don't see any Wind backup at all on XDA or anywhere on the internet. So it's up to you. If you do, you can put in dropbox or Drive and PM me the link.

ckpv5 said:
I feel it's odd that it didn't go to recovery when you correctly installed a stock recovery. If the recovery image is wrong version, it still go to recovery and give error mark (the famous red triangle) but yours it just hang .. I run out of idea.
If you have time, maybe you can make a nandroid backup of boot & system (don't need data as it contains your data) and upload for me to have a look at it. Then I can rebuild the nandroid for others too. So far I don't see any Wind backup at all on XDA or anywhere on the internet. So it's up to you. If you do, you can put in dropbox or Drive and PM me the link.
Click to expand...
Click to collapse
okay, I'll do that next time I have the phone (its actually my friend's and I'm helping him out). I'll post the link in this thread when I upload it.

bbmaster123 said:
okay, I'll do that next time I have the phone (its actually my friend's and I'm helping him out). I'll post the link in this thread when I upload it.
Click to expand...
Click to collapse
In case anyone wondering what happen to this case ....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
all files will be uploaded in a few days time.

Need HELP!! with HTC Desire 816

Hello Everyone,
I need help with my HTC Desire 816 Here is my issue :
I rooted my device using this tutoriol : http://forum.xda-developers.com/showthread.php?t=2775801
everything went smooth but when i open SuperSU it says Binary needs to be updated but i'm unable to update it in anyway.
After root the phone restarts randomly.
I even tried to unroot using SuperSU and other ways but nothing seems to work.
I also tried to Disable Write Permission and that's when it all went wrong.
Now my phone keeps rebooting and i can't even use it
N.B: I always had an iphone, it's my first android phone so i'm a Newbie in rooting.
Any help is REALLY appreciated.
Thanks.

the link doesn't work, if you mean v_superuser guide the post was for kitkat
for lollipop you need to flash supersu v 2.46 I guess, atleast that what I did
the write protection post indicated in his guide also was for kitkat
try flashing stock if you took a backup b4 rooting to stop the random restarts, flash supersu and disable write protection for lollipop http://forum.xda-developers.com/des...-disable-writeprotection-sense-stock-t3091456

[/COLOR]
MaE_sTrO said:
Hello Everyone,
I need help with my HTC Desire 816 Here is my issue :
I rooted my device using this tutoriol http://forum.xda-developers.com/show....php?t=2775801
everything went smooth but when i open SuperSU it says Binary needs to be updated but i'm unable to update it in anyway.
After root the phone restarts randomly.
I even tried to unroot using SuperSU and other ways but nothing seems to work.
I also tried to Disable Write Permission and that's when it all went wrong.
Now my phone keeps rebooting and i can't even use it
N.B: I always had an iphone, it's my first android phone so i'm a Newbie in rooting.
Any help is REALLY appreciated.
Thanks.
Click to expand...
Click to collapse
Sorry your having these problems but as long as you can get into your boatloader they should be fixable. Hopefully you did a full nandroid backup of your phone after rooting before attempting any other flashes or mods but if you didn't then that's just friendly advice for any future flashes for everybody , me included. It's an easy step to skip(I've forgotten to do one myself) but it's the most important step to being able to easily restore from any problems.
Try to get into your boatloader by holding power button then volume down and hold. That should reboot into your bootloader and from there you can enter recovery and do a factory reset then wipe cache and dalvik cache then reboot system and see if that stops the bootloops. If not then you might need to find and reflash your stock recovery and relock your bootloader then find a flashable zip or executable RUU (rom utility update) and flash back to completely stock. If your in the U.S. HTC has the RUU executable files on their website in the downloads section(RUU not kernel). These you can either run from a P.C. as an executable program with your phone in fastboot or rename to your model specific firmware image and install to and flash from your phone's external SD card from your bootloader. The only issue would be if your system has been modified by the write permission mod you flashed then that would need to be removed before any signed stock update could work. What's your specific phone model( a5_"what") and are you in the U.S. or overseas?
EDIT: it's volume down not volume up. Volume up reboots the phone. Sorry, I use an app to do all of that now not my keys.

thoctor said:
[/COLOR]
Sorry your having these problems but as long as you can get into your boatloader they should be fixable. Hopefully you did a full nandroid backup of your phone after rooting before attempting any other flashes or mods but if you didn't then that's just friendly advice for any future flashes for everybody , me included. It's an easy step to skip(I've forgotten to do one myself) but it's the most important step to being able to easily restore from any problems.
Try to get into your boatloader by holding power button then volume down and hold. That should reboot into your bootloader and from there you can enter recovery and do a factory reset then wipe cache and dalvik cache then reboot system and see if that stops the bootloops. If not then you might need to find and reflash your stock recovery and relock your bootloader then find a flashable zip or executable RUU (rom utility update) and flash back to completely stock. If your in the U.S. HTC has the RUU executable files on their website in the downloads section(RUU not kernel). These you can either run from a P.C. as an executable program with your phone in fastboot or rename to your model specific firmware image and install to and flash from your phone's external SD card from your bootloader. The only issue would be if your system has been modified by the write permission mod you flashed then that would need to be removed before any signed stock update could work. What's your specific phone model( a5_"what") and are you in the U.S. or overseas?
EDIT: it's volume down not volume up. Volume up reboots the phone. Sorry, I use an app to do all of that now not my keys.
Click to expand...
Click to collapse
Thank you thoctor , as i said i'm a newbie in rooting so i didn't make full nandroid backup but thanks to you and after doing a factory reset the bootloops stopped, i'm able to use the phone now, but i think the write protection is still disabled, as i'm trying to use apps2sd and creating a new partition in the SD is not working, one more thing i'm unable to update SuperSu's binary too, thanks to your help and i would appreciate if you can help me further.
my model number : A5_ul and cidnum: HTC__E11 , and i'm in europe.

Roberto Nigel said:
the link doesn't work, if you mean v_superuser guide the post was for kitkat
for lollipop you need to flash supersu v 2.46 I guess, atleast that what I did
the write protection post indicated in his guide also was for kitkat
try flashing stock if you took a backup b4 rooting to stop the random restarts, flash supersu and disable write protection for lollipop http://forum.xda-developers.com/des...-disable-writeprotection-sense-stock-t3091456
Click to expand...
Click to collapse
Thanks Roberto
that's the exact way i tried to disable write protection, and that's when it all went wrong, but i retried it now it went smooth, but i think it didn't work , is there anyway to make sure if it's enabled or not ?

MaE_sTrO said:
Thank you thoctor , as i said i'm a newbie in rooting so i didn't make full nandroid backup but thanks to you and after doing a factory reset the bootloops stopped, i'm able to use the phone now, but i think the write protection is still disabled, as i'm trying to use apps2sd and creating a new partition in the SD is not working, one more thing i'm unable to update SuperSu's binary too, thanks to your help and i would appreciate if you can help me further.
my model number : A5_ul and cidnum: HTC__E11 , and i'm in europe.
Click to expand...
Click to collapse
No problem buddy. We've all been there trust me on that. You can update the binaries from within the SuperSU apps settings or in custom recovery. Check to verify you have the most current version from the play store and if not download it. Also you might try to wipe your cache and dalvik cache from within your custom recovery then reboot system and see if that fixes it. As for the WP mod there are some that get it to work right off the bat and others who have to add or remove a line in the lib files using a terminal emulator app but I've never personally used this mod as I have true S off on my 816 a5_chl. I use Link2SD not the one your talking about but the partitioning for the app I use is done on a P.C. using EaseUS partition manager. Is yours the same process?

thoctor said:
No problem buddy. We've all been there trust me on that. You can update the binaries from within the SuperSU apps settings or in custom recovery. Check to verify you have the most current version from the play store and if not download it. Also you might try to wipe your cache and dalvik cache from within your custom recovery then reboot system and see if that fixes it. As for the WP mod there are some that get it to work right off the bat and others who have to add or remove a line in the lib files using a terminal emulator app but I've never personally used this mod as I have true S off on my 816 a5_chl. I use Link2SD not the one your talking about but the partitioning for the app I use is done on a P.C. using EaseUS partition manager. Is yours the same process?
Click to expand...
Click to collapse
Yup i have the latest supersu, About the Link2SD i have it also installed, and i've done the partitions on pc , tried EXT2 , EXT4 amd fat32 nothing worked, after so many tries the last error i get is something like that ( bad magic number in superblock ). that's why i thought it has something to do with the WP.
so i should wipe the cache and dalvik cache and it will do no harm right ?(coz i'm really glad now since i got rid of the rebootloop and i can use my phone .

MaE_sTrO said:
Yup i have the latest supersu, About the Link2SD i have it also installed, and i've done the partitions on pc , tried EXT2 , EXT4 amd fat32 nothing worked, after so many tries the last error i get is something like that ( bad magic number in superblock ). that's why i thought it has something to do with the WP.
so i should wipe the cache and dalvik cache and it will do no harm right ?(coz i'm really glad now since i got rid of the rebootloop and i can use my phone .
Click to expand...
Click to collapse
Lol. I know how you feel. You can wipe those two all day long and nothing bad will happen. It's just a cache cleaner that clears out our any leftover files in the firmwares cache folders. System restore wipes the whole phone except for the external SD card and your personal downloads or data files. Custom delete can add those personal data files so be careful there but otherwise your good. Check settings to see in about phone if your SElinux permissions are set to enforcing or permissive. The mod is supposed to change them to permissive for it to work properly.
Also on link2SD set the new data partition to ext2 if your on a stock rom and set as primary then set the remaining partition for your normal storage(not app data) to fat32 (as that's the format the phone will let you view in your SD card) and also as primary. It was the write permissions that wasn't letting it work not the format because I've been down that road many times before I got mine right.

thoctor said:
Lol. I know how you feel. You can wipe those two all day long and nothing bad will happen. It's just a cache cleaner that clears out our any leftover files in the firmwares cache folders. System restore wipes the whole phone except for the external SD card and your personal downloads or data files. Custom delete can add those personal data files so be careful there but otherwise your good. Check settings to see in about phone if your SElinux permissions are set to enforcing or permissive. The mod is supposed to change them to permissive for it to work properly.
Also on link2SD set the new data partition to ext2 if your on a stock rom and set as primary then set the remaining partition for your normal storage(not app data) to fat32 (as that's the format the phone will let you view in your SD card) and also as primary. It was the write permissions that wasn't letting it work not the format because I've been down that road many times before I got mine right.
Click to expand...
Click to collapse
thanks for the fast response , i wiped the cache and i still can't update the binary i get this msg
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
if i press normal the phone reboots, if i press TWRp/CWM ( since i rooted with cwm recovery) it reboots enters recovery starts loading then reboots and i get the same msg about the update again.
Also about the SElinux i can't find it in about :S.

MaE_sTrO said:
thanks for the fast response , i wiped the cache and i still can't update the binary i get this msg
if i press normal the phone reboots, if i press TWRp/CWM ( since i rooted with cwm recovery) it reboots enters recovery starts loading then reboots and i get the same msg about the update again.
Also about the SElinux i can't find it in about :S.
Click to expand...
Click to collapse
Find official TWRP recovery flashable zip for the a5 on their website and download and flash over CWM from your P.C. using ADB/fastboot.Just put the file in your ADB folder and rename it twrp.img and enter fastboot flash recovery"recovery name".img and either enter the name after typing recovery or just drag it down into your command prompt after typing recovery and it should flash automatically with your phone's USB debugging activated and the phone in fastboot. I use TWRP and you might be having an issue with the CWM exe recovery.Can't hurt to flash and you could always go back if you didn't like it but most everybody loves TWRP custom touch recovery. I know I do. It's on all my rooted devices.
As for the SElinux it's at the very bottom of my settings in about phone but I'm on a custom rom CM12.1 but you should be able to see it somewhat in your phone's settings on stock. I just can't remember where it is but it's there
EDIT: try to reflash in recovery the most current flashable zip for SuperSU found on chainfires website for SuperSU. I believe it's 2.4.6 but don't quote me on that just make sure it's the most current one which it will be on his site. That may help the binary issue. Even if the one you flashed is the most current flashable zip flash it again.

thoctor said:
Find official TWRP recovery flashable zip for the a5 on their website and download and flash over CWM from your P.C. using ADB/fastboot.Just put the file in your ADB folder and rename it twrp.img and enter fastboot flash recovery"recovery name".img and either enter the name after typing recovery or just drag it down into your command prompt after typing recovery and it should flash automatically with your phone's USB debugging activated and the phone in fastboot. I use TWRP and you might be having an issue with the CWM exe recovery.Can't hurt to flash and you could always go back if you didn't like it but most everybody loves TWRP custom touch recovery. I know I do. It's on all my rooted devices.
As for the SElinux it's at the very bottom of my settings in about phone but I'm on a custom rom CM12.1 but you should be able to see it somewhat in your phone's settings on stock. I just can't remember where it is but it's there
Click to expand...
Click to collapse
Just flashed TWRP.
tried to update binary same thing happend but now i see in TWRP when it tries to update it says no MD5

thoctor said:
Find official TWRP recovery flashable zip for the a5 on their website and download and flash over CWM from your P.C. using ADB/fastboot.Just put the file in your ADB folder and rename it twrp.img and enter fastboot flash recovery"recovery name".img and either enter the name after typing recovery or just drag it down into your command prompt after typing recovery and it should flash automatically with your phone's USB debugging activated and the phone in fastboot. I use TWRP and you might be having an issue with the CWM exe recovery.Can't hurt to flash and you could always go back if you didn't like it but most everybody loves TWRP custom touch recovery. I know I do. It's on all my rooted devices.
As for the SElinux it's at the very bottom of my settings in about phone but I'm on a custom rom CM12.1 but you should be able to see it somewhat in your phone's settings on stock. I just can't remember where it is but it's there
EDIT: try to reflash in recovery the most current flashable zip for SuperSU found on chainfires website for SuperSU. I believe it's 2.4.6 but don't quote me on that just make sure it's the most current one which it will be on his site. That may help the binary issue. Even if the one you flashed is the most current flashable zip flash it again.
Click to expand...
Click to collapse
Flashed TWRP reflashed SuperSU from chainfires website , same issue , but now i can see when it tries to update in TWRP it says no MD5!!!
and i assure u i can't find SElinux anywhere in about !!!!

MaE_sTrO said:
Flashed TWRP reflashed SuperSU from chainfires website , same issue , but now i can see when it tries to update in TWRP it says no MD5!!!
and i assure u i can't find SElinux anywhere in about !!!!
Click to expand...
Click to collapse
No problem , Don't worry about the permissions for now. The MD5 is the checksum that verifies the file isn't corrupt but if you got it from the chainfire site your fine. Try to update the binary thru twrp or in the SuperSU app and select your recovery as the way you want to update and see what happens.
Also did you have MD5 check enabled in TWRP? I do in mine for file verification but just wondering what yours was set to when you got that notice. It shouldn't stop SuperSU from flashing either way it's just a file verifier.
---------- Post added at 12:56 AM ---------- Previous post was at 12:18 AM ----------
the binaries are what SuperSU uses to get and maintain root . If they are incomplete or corrupt then they have to be reflashed over with an uncorrupted version. That is usually why people keep getting the notice to update the binaries and when they do they can't because they are not complete or corrupt and need to be totally removed i.e. reflashing, which you did, or unrooting from the SuperSU app itself and redownloading again from the play store. This is what I've read on several help sites for this issue. Just wanted to pass along the why not just the what.

Again thank you for giving me so much information so i can understand the way things work and what i am doing, MD5 check was disabled i tried updating binary thru twrp i also tried enabling the MD5 both gave the same result, but the weird thing that it says done proccessing zip file , but when it reboots the update msg shows again, another thing when updating through twrp i noticed this line " full SElinux is present ".

MaE_sTrO said:
Again thank you for giving me so much information so i can understand the way things work and what i am doing, MD5 check was disabled i tried updating binary thru twrp i also tried enabling the MD5 both gave the same result, but the weird thing that it says done proccessing zip file , but when it reboots the update msg shows again, another thing when updating through twrp i noticed this line " full SElinux is present ".
Click to expand...
Click to collapse
No problem. To me that's the whole point of helping here on XDA is to make these things easier to understand for the person asking for assistance so they don't have to come back for the same thing again.Also because I was here in the same situations just a year or so ago and others helped me understand and I'm not a rocket scientist by any means .
Try to verify root through the root checker app on the play store. Almost positive it will say not rooted but it can't hurt to verify. Then , again, I would try to uninstall SuperSU through the app itself in it's settings as I'm almost positive the binaries are corrupted or incomplete and that's why you keep getting the same "update binaries message". If I sound like a broken record it's because I have learned from multiple Android device issues that sometimes for whatever reason things don't take and some combination of things might happen to alter the reason and trying the same thing again fixed it after coming back to it. I would also download SuperSU again but on a different device(laptop, computer) from chainfires site and reflash it just on the off chance the file is corrupted . Although at this point it's unlikely I know.
Lastly I would do an advanced wipe in TWRP recovery and add system to Data and Dalvik cache and cache from the factory reset. Not internal storage or SD card. Then I would flash the newly downloaded SuperSU and wipe Dalvik and cache then reboot system. Back up your contacts and numbers through Google's own backup in settings and they may already be backed up and use Super Backup app as well to save to external SD card as it can backup the same things.

thoctor said:
No problem. To me that's the whole point of helping here on XDA is to make these things easier to understand for the person asking for assistance so they don't have to come back for the same thing again.Also because I was here in the same situations just a year or so ago and others helped me understand and I'm not a rocket scientist by any means .
Try to verify root through the root checker app on the play store. Almost positive it will say not rooted but it can't hurt to verify. Then , again, I would try to uninstall SuperSU through the app itself in it's settings as I'm almost positive the binaries are corrupted or incomplete and that's why you keep getting the same "update binaries message". If I sound like a broken record it's because I have learned from multiple Android device issues that sometimes for whatever reason things don't take and some combination of things might happen to alter the reason and trying the same thing again fixed it after coming back to it. I would also download SuperSU again but on a different device(laptop, computer) from chainfires site and reflash it just on the off chance the file is corrupted . Although at this point it's unlikely I know.
Lastly I would do an advanced wipe in TWRP recovery and add system to Data and Dalvik cache and cache from the factory reset. Not internal storage or SD card. Then I would flash the newly downloaded SuperSU and wipe Dalvik and cache then reboot system. Back up your contacts and numbers through Google's own backup in settings and they may already be backed up and use Super Backup app as well to save to external SD card as it can backup the same things.
Click to expand...
Click to collapse
i went through your instructions , and after the last steps now i'm stuck on HTC logo
i can't even turn it off or get into recovery!!!!
i managed somehow to get into recovery no it says no OS installed , i guess i F**k it up right ?

MaE_sTrO said:
i went through your instructions , and after the last steps now i'm stuck on HTC logo
i can't even turn it off or get into recovery!!!!
i managed somehow to get into recovery no it says no OS installed , i guess i F**k it up right ?
Click to expand...
Click to collapse
No you didn't f***k it up I f*****d it up. I was thinking of what I do on my custom rom when I can't get something fixed and I brainfarted and forgot for a second your on a stock rom. That's on me not you so be mad at me not yourself. The good thing is it's fixable. I just flash a new custom rom but with stock it's a little bit different. You need to flash back the stock recovery which I will find and link you to and then lock the bootloader and flash back your stock Rom which I will also link you to. I am so sorry. I was in a doctor's office waiting room and my mind was on other things but that's no excuse just an explanation. Below is the link to stock lollipop for the a5_ul European version
Better than what I first linked us this forum page from Nukaru a few posts down in this forum for the stock a5_ul. He had links to both the stock recovery and stock rom file with detailed instructions on how to get the stock rom back on your phone. I know it works because he had a problem and figured all this out himself then wrote a detailed tutorial on how he fixed his. Link below.
http://forum.xda-developers.com/desire-816/help/a5ul-unable-to-flash-ruu-t3294835/page2

thoctor said:
No you didn't f***k it up I f*****d it up. I was thinking of what I do on my custom rom even I can't get something fixed and I brainfarted and forgot for a second your on a stock rom. That's on me not you so be mad at me not yourself. The good thing is it's fixable. I just flash a new custom rom but with stock it's a little bit different. You need to flash back the stock recovery which I will find and link you to and then lock the bootloader and flash back your stock Rom which I will also link you to. I am so sorry. I was in a doctor's office waiting room and my mind was on other things but that's no excuse just an explanation. Below is the link to stock lollipop for the a5_up European version
Link to stock lollipop rom below
https://www.androidfilehost.com/?fid=23991606952595166
Click to expand...
Click to collapse
Never mind i have nothing to loose as long as it's fixable lol, anyway i'll try this rom now
note: when i relock boot loader it says RELOCKED with S-ON does this matters?

MaE_sTrO said:
Never mind i have nothing to loose as long as it's fixable lol, anyway i'll try this rom now
note: when i relock boot loader it says RELOCKED with S-ON does this matters?
Click to expand...
Click to collapse
No, hold off on that first link I have a better one buddy. Just edited it above. No, "relocked S on" is what it's supposed to say so your fine but don't lock it yet or if you already did unlock it using the same unlock token you used on htc developers to unlock it in the first place . Then you flash back your stock recovery. Then relock your bootloader. Then you flash back your stock rom in that order.

thoctor said:
No hold off on that first link I have a better one buddy. Just edited it above. No relocked S on is what it's supposed to say so your fine but don't lock it yet orv I'd your already did unlock it using the same unlock token you used on htc developers to unlock it in the first place .
Click to expand...
Click to collapse
Alright downloading now...

TUTORIAL- How To- Downgrade To Lolipop 5.1.1, Galaxy S6 edge+ [UPDATED GUIDE]

- WARNING -
This Guide is not failproof, if you do anything wrong with your device while following this guide, i won't be held responsible if you brick or hard damage your device. I insist about that but you must extract all of your data (Photos, Videos, Music, Apps, Accounts, Messages, ETC) Before proceeding or else you will end up with a loss of data, again i'm still not responsible if you lose all of your data without backing up. I WARNED YOU.
Well, you have a Galaxy S6 edge+ lying around and you want to get back to Lolipop? You want to downgrade? Well then you're in the right place!
So......downgrading to lolipop...... some people claimed it can be done by deleting some file in the odin .tar but that never worked for me.
If you have the sw rev check fail error upon downgrading....this is the guide for you!
This will wipe all your data including internal storage (depending on how you do it)
Confirmed working on my Galaxy S6 edge+ SM-G928F [It should work on Note5 but no promises from now on]
Advantages :
Downgrade procedure is safe, simple.
Your phone should boot faster
battery life should last longer [i said it should]
You can get the animated lock screen animations back.
Get old touchwiz back. [i like the 5.1.1 version]
disadvantages:
1. You cannot boot TWRP while on the downgraded bootloader
2. You will only have system-wide root. DO NOT flash systemless or it will not boot (but nobody cares)
3. Fingerprint is not working (still working on that)
4. You can only flash stock nougat from odin. You cannot flash lolipop, marshmallow tar,twrp tar,cf auto root tar or anything else [except if you have a combination firmware]
Ok, let's get started.
Requirements :
A laptop or home PC : At least running Windows 8/8.1 or Windows 10
Your device
Genuine Samsung charging cable [NOT SPONSERED]
Stable internet connection.
Files :
The lastest SAMSUNG Drivers which can be found here : https://developer.samsung.com/android-usb-driver
Odin3 : https://www.samsungodindownload.com/fr/download-for-windows
The firmware you want to downgrade to : I will link my ROM so u can install it.
TWRP [Newest version] : https://twrp.me/samsung/samsunggalaxys6edgeplus.html
Classy Kitchen [for bulding your rom] : https://forum.xda-developers.com/t/...kitchen-for-android-roms-development.3862584/
Now let's get started!
Let's start first by cooking the ROM! Open Classy Kitchen, and then open the ROM you want to use :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Normally the first time you open the program, there shouldn't be any project [except if you used this app before]
Next click "Create new project", "From PC (Browse for one)"
And then chose the path where you saved your firmware. After chosing your firmware, Classy Kitchen will open the firmware automaticly.
After the ROM is now open, click on "ROM utils" and then click on "Deodex ROM" After you Deodex the ROM, we will have to de-bloat it.
On Classy Kitchen, click on "Debloat / Re-Bloat ROM" to Debloat your ROM.
Last step [optional] We will have to De-Knox our ROM. (again optional) But De-Knoxing our ROM can save a lot of space in our phone storage. So i recommend you do.
After De-Knoxing our ROM, we will have to disable DM-Verity Force Encryption in order to Boot into the ROM [Otherwise if you don't your phone will never boot]
Click on "Remove DM-Verity / Force Encryption"
Next that we disabled DM-Verity, We will have to remove the "meta-inf installer"
Click on "Re-Build META-INF installer" and click on remove.
Finally once we have done the modifications on our ROM, we just have to save.
Click on "Build (system.new.dat) ROM (for recovery)"
and then we are done cooking our ROM!
But the guide is not done yet. We will have to install TWRP in the phone.
HOW-TO-PROCEED?
Step-1 Press and hold the power button on your device
Step-2 Chose "Power Off"
Wait for your device to completly Shut-Off.
Step-3 Re-Boot in download mode "odin mode"
Step-4 connect the phone to your computer
Step-5 open Odin3
In Odin, we will have to install TWRP, click on the AP box and chose your TWRP file [the one that you downloaded]
Don't forget to disable "Auto-Reboot" after installation, otherwise your phone will re-boot normal into Android.
At this point, Knox is tripped in your device meaning that your warranty is now expired. Also the Knox features are no longer usable.
On TWRP, click on wipe, "Format Data". A keyboard will pop-up, type "yes"
Type "yes"
Once Data Format is completed, hit home, reboot, recovery.
your phone will reboot into recovery again, hit wipe again, this time we won't format data. Instead we're going to wipe the phone's partitions
Chose in TWRP,
Then swipe to wipe. Then hit home again. Next hit "Install"
Install the ROM you just made with Classy Kitchen. It can be found in "Documents" - "Output" - "Your-ROM"
Transfert it to your phone
Click on the ROM / ZIP file and "swipe to confirm flash"
After the flashing procedure is complete, you will have to wipe the "cache" / Dalvik.
Hit "wipe dalvik/cache"
Then "swipe to wipe"
After you wiped the cache, hit "Reboot System" and hit "Do Not Install"
One last step before you get back to Lolipop. You will need a custom Bootloader in order to boot.
Just download my "custom Bootloader" https://drive.google.com/file/d/1207Guvk8J_L9FSJv2C9BpkeLpWkXtViQ/view?usp=drive_link
After you downloaded my "custom bootloader" you will have to install it.
so get Odin3 and install my bootloader!
After the Bootloader installation is complete, you just have to reboot your device, cross your fingers and hope it boots!
Congratuations! You are back on Lolipop! Enjoy!
1 : If you want to flash a mod in TWRP, you will have to put your phone in download mode, install the stock bootloader in BL tab, install TWRP in AP tab and then click on "start"
2 : If you want to get back into marshmallow / Nougat, you just have to flash stock firmware in Odin3
If you have any issues or any questions, you can DM me but it isn't guaranteed that i will reply.

Here are some screenshots of Lolipop :

Here the device i used.

what about system sound because on 6.1.1 (sorry 6.0.1) sound was weird and glitchy idk why
oh btw i need a access the drive to download bootloader

iskender4444 said:
what about system sound because on 6.1.1 sound was weird and glitchy idk why
oh btw i need a access the drive to download bootloader
View attachment 5922017
Click to expand...
Click to collapse
Nevermind. This comment is deleted

iskender4444 said:
what about system sound because on 6.1.1 sound was weird and glitchy idk why
oh btw i need a access the drive to download bootloader
View attachment 5922017
Click to expand...
Click to collapse
Actually
iskender4444 said:
what about system sound because on 6.1.1 sound was weird and glitchy idk why
oh btw i need a access the drive to download bootloader
View attachment 5922017
Click to expand...
Click to collapse
Try download downloading my bootloader again. I made it public

TheWiiGuy said:
Actually
Try download downloading my bootloader again. I made it public
Click to expand...
Click to collapse
Why sound coming like creepy from buzzer only on 6.1.1 interesting..

iskender4444 said:
Why sound coming like creepy from buzzer only on 6.1.1 interesting..
Click to expand...
Click to collapse
Have you downgraded to Lollipop yet?

TheWiiGuy said:
Have you downgraded to Lollipop yet?
Click to expand...
Click to collapse
i had bootloop on samsung galaxy s6 edge plus here the photo:

and can you share the twrp? and is this correct one?
"twrp-3.1.1-0-zenlte.img"

iskender4444 said:
and can you share the twrp? and is this correct one?
"twrp-3.1.1-0-zenlte.img"
Click to expand...
Click to collapse
Yes. This is The Good TWRP. Are you trying to get into recovery? If not then there is a problem with my bootloader
Mind if i upload the New bootloader tomorrow?

iskender4444 said:
i had bootloop on samsung galaxy s6 edge plus here the photo:
Click to expand...
Click to collapse
It looks like the phone is trying to get into stock recovery.

TheWiiGuy said:
It looks like the phone is trying to get into stock recovery.
Click to expand...
Click to collapse
idk and i dont get it why doing this i just re-download twrp official website and still same issue i just flash the twrp but can't enter twrp recovery right know.

iskender4444 said:
idk and i dont get it why doing this i just re-download twrp official website and still same issue i just flash the twrp but can't enter twrp recovery right know.
Click to expand...
Click to collapse
Actually i forgot to mention that you can't boot into TWRP on My custom bootloader. Get back in odin. Re-flash stock bootloader in BL Tab and flash TWRP in the AP Tab. Then try to re-boot onto Custom recovery. Tell me some news.

TheWiiGuy said:
Actually i forgot to mention that you can't boot into TWRP on My custom bootloader. Get back in odin. Re-flash stock bootloader in BL Tab and flash TWRP in the AP Tab. Then try to re-boot onto Custom recovery. Tell me some news.
Click to expand...
Click to collapse
Oh yes. Have you backed up all of your partitions on TWRP?

TheWiiGuy said:
Oh yes. Have you backed up all of your partitions on TWRP?
Click to expand...
Click to collapse
i solved twrp but can't boot same as issue on picture

iskender4444 said:
i solved twrp but can't boot same as issue on picture
Click to expand...
Click to collapse
So you can boot onto TWRP ?
OK. I see the problem.
I Will upload my New bootloader tomorrow.
The current bootloader does not allow to Boot onto TWRP and it can't boot into stock recovery either.
Hopefully the New bootloader should fix your problem. It has stock recovery

TheWiiGuy said:
So you can boot onto TWRP ?
OK. I see the problem.
I Will upload my New bootloader tomorrow.
The current bootloader does not allow to Boot onto TWRP and it can't boot into stock recovery either.
Hopefully the New bootloader should fix your problem. It has stock recovery
Click to expand...
Click to collapse
i have another problem i was trying to flash stock 7.0 rom but gives error same like this.

iskender4444 said:
i have another problem i was trying to flash stock 7.0 rom but gives error same like this.
Click to expand...
Click to collapse
Nevermind this comment is deleted

TheWiiGuy said:
What is your phone model number? I see you are installing firmware for a sm-g780f.
Click to expand...
Click to collapse
no this is for example man mine was g928c