Develop Bugs

[December 6,2013][ROM] [PrimoC] Stock-Rooted Virgin Mobile HBOOT 1.57.0000

View attachment primoc_boot_unsecure.imgPlease excuse my absence. I will not be watching this thread for the time being. Hopefully if you have any questions, they can be answered by using the search option or someone else with this device that happens to check this thread will be kind enough to help.
!#I'M BACK#!​
soon enough we won't need this thread, because we will all be able to RUU lol-Dec 6, 2013
beaups said:
posted on rumrunner.us. should work for both primou and primoc. Note, it is highly recommended (mandatory?) to be on a normal sense-based ICS rom and using an unsecure (preferably stock based) kernel. If you get poor results with other configurations, don't bother asking for help please!
Click to expand...
Click to collapse
S-OFF is here rumrunner.us
Huge thanks to beaups
This rom is probably most compatible with rumrunner
The boot.img inside is unsecure so flash away and GO GET S-OFFED!!!
Here's the unsecure boot.img that I used to achieve s-off.
View attachment primoc_boot_unsecure.img
{
"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"
}
Added init.d support
Added Root Permissions with Chainfire's SuperSu
This ROM was cooked with dsixda's Android Kitchen
Thank you and credit goes out to the both of them.
CLICK HERE TO DOWNLOAD

I have posted this ROM for safetynet/fall-back purposes.
I've noticed fellas posting please help, I forgot/didn't make a backup.
This is for you. Worried and maybe even a little scared that your phone is now a beautiful paper weight.
This ROM is completely stock with added init.d support and root.
It is still odexed, and with stock kernel.( I'm still learning/attempting to build one with extra governors and over clocking abilities ).
Instructions below....

1. Unlock your Bootloader by following the instructions at htcdev
1a. If you've succesfully unlocked your Bootloader, that means you have your fastboot files on your PC and know in general how to use them.
2. Download an openrecovery of your choice. I personally use TeamWinRecoveryProject 2.2.0 without any issues at all. (See the attached File)
3. Place the recovery.img that you have chosen into your fastboot folder.
3a. Change the name of the .img to recovery.img (just easier that way when sending the flash command)
4. Now open a terminal while in the fastboot folder.
4a. On Windows- hold shift+right click the mouse then click open command terminal here.
4b. On Ubuntu- CTRL+ALT+T to open a terninal then cd fastboot.
5.fastboot flash recovery recovery.img​
5a. ^^^^^ Type this into the terminal. ^^^^^
5b. You now have a custom/openrecovery.
6. After the recovery.img is flashed, reboot your Bootloader.
6a. fastboot reboot-bootloader​
7. After booted back into bootloader, use your volume-down button to highlight Recovery.
Now press your Power button to select it.
7a. Now your are in Recovery!
8. Click Wipe, then Cashe, then Dalvick, then Factory Rest, then System.
8a. This will wipe all of your phone nice and clean for a fresh install.
9. Click Home, then Install, and find the ROM.zip, click it, then install. Let it finish installing the click Wipe Cashe/Dalvick.
10. Navigate back to the Home screen and click Reboot, then Bootloader
10a. I hope you have a copy of the ROM.zip on your PC.
11. Open the ROM.zip and copy/extract the boot.img from inside it and place it in your fastboot folder.
12. Open a terminal once again.
13.fastboot flash boot boot.img​
13a. Let it finish.
14. fastboot reboot​
15. Enjoy.
These instructions are for use with TWRP (TeamWinRecoveryProject) They may be different using CWMrecovery (ClockWorkMod).

I made a backup of my stock rom via twrp. Updated the kernel and installed shpongle. When I tried to go back to my stock via twrp it would not boot due to the kernel. I wonder if that will be the case here

lostboybinns said:
I made a backup of my stock rom via twrp. Updated the kernel and installed shpongle. When I tried to go back to my stock via twrp it would not boot due to the kernel. I wonder if that will be the case here
Click to expand...
Click to collapse
u flashed shpongle? that means u are GSM not CDMA so this ROM just simply won't work
as for returning to stock, u can always flash a sense kernel duh

This is for primoc CDMA Virgin Mobile

I just downloaded and flashed to test, everything is working....Just like stock

This should allow me to update my PRL, right?

YUP!

Turns out it was a network fluke?

wont flash for me, i get:
"error executing updater binary in zip
and
error flashing zip
going to try a full format of the sd card...

russellvone said:
Turns out it was a network fluke?
Click to expand...
Click to collapse
What was a network fluke?

I'll cross reference the updater-script to another one I've used on a different Rom I cooked and have been running for over two weeks..... See if there are any differences between the two.

lilrob1213 said:
What was a network fluke?
Click to expand...
Click to collapse
I was replying to zombiegirl's question about updating her/his PRL

Matt_the_Geek said:
wont flash for me, i get:
"error executing updater binary in zip
and
error flashing zip
going to try a full format of the sd card...
Click to expand...
Click to collapse
Ok I found a difference in the updater-script, the update binaries are identical so that shouldn't be the issue. Problem I have is that I don't have a working computer to fix the updater-script. It won't be until June 26th that I can apply it. Sorry for the inconvenience.
P.S. are you flashing with TWRP?

Yes sir, TWRP. and no worries, it apparently just isn't your ROM. Angry HTC and jmz's stock ROM both give the same error. even after a full format of the SD. Rhythmic Rom 1.4 works though, and is what I was running. Was trying to return the device to somewhat stock tho as im either going to sell it or let my gf use it, so I was hoping for stable and to have the charge LED and icons working, hopefully.

Matt_the_Geek said:
Yes sir, TWRP. and no worries, it apparently just isn't your ROM. Angry HTC and jmz's stock ROM both give the same error. even after a full format of the SD. Rhythmic Rom 1.4 works though, and is what I was running. Was trying to return the device to somewhat stock tho as im either going to sell it or let my gf use it, so I was hoping for stable and to have the charge LED and icons working, hopefully.
Click to expand...
Click to collapse
If you downgrade TWRP to 2.3 you should be fine.
Sent from my One V using xda premium

ah, I'm on 2.5, so I'll look into that...

did the downgrade to TWRP 2.3.0.0, still the only thing i can install is Rhythimc Rom, everything else fails to install... unless i just got some really crappy downloads, so i'm off to try to dl the roms again...

Actually, instead I swapped out recoveries for CWM. aaaand it worked.

Replace the android recovery from TWRP

Hello,recently I did root my S3 L710 (Sprint) following this tutorial [HOW TO] Easiest Root and Recovery: SGS3 LTE Sprint, T-Mobile, AT&T, Rogers and was successful and the first thing I wanted to do was a backup with TWRP, install it with GooManager, and did the combination (Volume Up + Center Home + Power button) for 5 seconds, but I appeared the stock recovery.
{
"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"
}
According to what I read, you must do the following:
Removes /system/etc/install-recovery.sh and /system/recovery-from-boot.p left by OTA updates in order to preserve stock recovery. Read the CWM instructions carefully!
Click to expand...
Click to collapse
But seeing that these files are in the system, I'm afraid that if I delete it, the S3 also problems.
I would like to know if it is safe to remove them? whether, if so, the TWRP recovery will become the default?
Thanks!

That picture you posted is TWRP custom recovery? I don't understand what's wrong.
Sent from the future via Tapatalk 4

edfunkycold said:
That picture you posted is TWRP custom recovery? I don't understand what's wrong.
Click to expand...
Click to collapse
The picture is only sample, not my S3, so it has better features than the Clockwork, which I would like to know is, if i need to remove these files so that I leave the TWRP?

kevinrealk said:
The picture is only sample, not my S3, so it has better features than the Clockwork, which I would like to know is, if i need to remove these files so that I leave the TWRP?
Click to expand...
Click to collapse
You can flash TWRP right over CWM or visa versa makes no difference. Cnexus has a set up in which you can have both and switch between which ever you want to use. But it makes no difference which ever you prefer. I personally think CWM works better on my S3 but I use TWRP on my Gnexus because it works better on that device. Let me see if I can find and link @CNexus thread for the switching recovery. And no you do not have to remove any files.
Sent from the future via Tapatalk 4

Flash the Team-Epic-root_from_recovery.zip and it will rename those files so that they cannot do any harm (the zip is somewhere here, just search).
As for my recovery switcher, its right here.

CNexus said:
Flash the Team-Epic-root_from_recovery.zip and it will rename those files so that they cannot do any harm (the zip is somewhere here, just search).
Click to expand...
Click to collapse
I understand, installing the zip file whit Odin3, it automatically turns on the recovery TWRP by default.
In closing, I install TWRP with GooManager, but if I do it with the zip through Odin3, overwrite?

kevinrealk said:
I understand, installing the zip file whit Odin3, it automatically turns on the recovery TWRP by default.
In closing, I install TWRP with GooManager, but if I do it with the zip through Odin3, overwrite?
Click to expand...
Click to collapse
No....you're misunderstanding, do the following.
Power off your device
Boot into download mode
Flash any recovery (you can switch later) through ODIN (it should be a .tar.md5 file)
Pull the battery (DO NOT REBOOT, PULL THE BATTERY)
Boot into recovery from powered off
Flash the Team_Epic_Root_From_Recovery.zip through recovery
The stock recovery will now stop replacing your custom recovery. You can now flash another recovery if you want to.
The TeamEpic.zip file gets flashed through recovery, not ODIN.

CNexus said:
No....you're misunderstanding, do the following.
Power off your device
Boot into download mode
Flash any recovery (you can switch later) through ODIN (it should be a .tar.md5 file)
Pull the battery (DO NOT REBOOT, PULL THE BATTERY)
Boot into recovery from powered off
Flash the Team_Epic_Root_From_Recovery.zip through recovery
The stock recovery will now stop replacing your custom recovery. You can now flash another recovery if you want to.
The TeamEpic.zip file gets flashed through recovery, not ODIN.
Click to expand...
Click to collapse
Hi, I already made the process more or less:
- I put the CWR of this package GalaxyS3RootUSCanada.zip with ODIN
- When I was in CWR, Flash the Team_Epic_Root_From_Recovery.zip
- Went well, I emerged a problem:
By making the combination Volume Up and Center Home buttons, I went the CWR, when I want to backup or Reboot system now, just lay on the logo, forcing me to remove the battery.
That there will be happened?
* Edit: I went back to install the TWRP from GooManager, replacing the CWR, and TWRP recovery is the default
Thank you very much for the help!.:victory:

[Q] Failure to update to Lollipop. Now what?

I have Vodafone IE HTC M8. I tried to upgrade to stock 5.0 (just recently arrived). As people advised, flashed stock recovery and started OTA upgrade... And got big red triangle... Have no idea why I managed to reboot (Power + VolUp). And ... Now I cannot get to recovery any more, the phone says "Software status: modified" and stays in the boot loader.
Any attempts to flash recovery fail with "signature verify fail". I tried various things: stock recovery, philz recovery. Same thing.
Any advice? I would really like to have recovery recovered...

It seems I managed to oem lock the phone again. Unlocked - and can normally flash recovery.
So, philz recovery works, once flashed. But the stock recovery... It does not work, at all. Trying to switch to it, getting back to bootloader (and I see some messages, quickly disappearing: "No image or wrong image". Still not good

1. Unlock your Bootloader
2. Load adb/fastboot (if you're to lazy to install this all, like me, use the version from the video https://www.youtube.com/watch?v=5xVl2dBTnmI)
3. Then load the latest Version of TRWP and flash it with fastboot
4. Download the right nandroid backup here http://forum.xda-developers.com/show...postcount=2960
5. Start Recovery on your Device and Make backup of boot (to see were the right place is to put in the nandroid)
6. Start Backup from the nandroid via TRWP on your device
7. Finish
(The only thing is, that you have got a branded HTC8)
This was the thing I did here. I think it should work for you too.
Here you can see my Thread with a similar Problem:
http://forum.xda-developers.com/htc-one-m8/help/bootl-loop-lollipop-update-t3016142

sudaltsov said:
I have Vodafone IE HTC M8. I tried to upgrade to stock 5.0 (just recently arrived). As people advised, flashed stock recovery and started OTA upgrade... And got big red triangle... Have no idea why I managed to reboot (Power + VolUp). And ... Now I cannot get to recovery any more, the phone says "Software status: modified" and stays in the boot loader.
Any attempts to flash recovery fail with "signature verify fail". I tried various things: stock recovery, philz recovery. Same thing.
Any advice? I would really like to have recovery recovered...
Click to expand...
Click to collapse
When you get the big red triangle, press & hold volume up and tap power button once to read the error log.
As some have same problem like yours, the problem maybe wrong stock recovery.
To ensure the right recovery image for you to proceed OTA, download OTA again, when it ask to install select install later. Connect your device to PC, open the Internal Storage with PC explorer, browse to Download folder, you'll have the OTA.zip there. Copy that OTA.zip to PC, open it with 7-zip then open firmware.zip that you see inside, extract out the recovery.img ---this is the correct recovery image to use.

ckpv5 said:
When you get the big red triangle, press & hold volume up and tap power button once to read the error log.
As some have same problem like yours, the problem maybe wrong stock recovery.
To ensure the right recovery image for you to proceed OTA, download OTA again, when it ask to install select install later. Connect your device to PC, open the Internal Storage with PC explorer, browse to Download folder, you'll have the OTA.zip there. Copy that OTA.zip to PC, open it with 7-zip then open firmware.zip that you see inside, extract out the recovery.img ---this is the correct recovery image to use.
Click to expand...
Click to collapse
I had the same problem. I did exactly what you said. extracted the stock recovery.img from the OTA update, flashed my M8 with this recovery, still no luck
I am on 3.28.401.9 stock rom from last OTA
unlocked
this is the error I'm getting :
{
"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"
}

snowfree52 said:
I had the same problem. I did exactly what you said. extracted the stock recovery.img from the OTA update, flashed my M8 with this recovery, still no luck
I am on 3.28.401.9
this is the error I'm getting :
Click to expand...
Click to collapse
Your error is different .. the libril-qc-qmi-1.so is modified and not pure stock. You need to replace this file with the stock one.
To make thing easier for you, just flash TWRP again and restore my 3.28.401.9 nandroid backup here : http://forum.xda-developers.com/showpost.php?p=56979449&postcount=2960
You can restore only the system part, keep your data part so you have pure stock system but your data intact.

ckpv5 said:
[/HIDE]
Your error is different .. the libril-qc-qmi-1.so is modified and not pure stock. You need to replace this file with the stock one.
To make thing easier for you, just flash TWRP again and restore my 3.28.401.9 nandroid backup here : http://forum.xda-developers.com/showpost.php?p=56827142&postcount=2920
You can restore only the system part, keep your data part so you have pure stock system but your data intact.
Click to expand...
Click to collapse
thanks for your reply. :good:
your link doesn't point to the right files I believe.
How do I flash only the system part ?

snowfree52 said:
thanks for your reply. :good:
your link doesn't point to the right files I believe.
How do I flash only the system part ?
Click to expand...
Click to collapse
Link corrected.
You don't flash, you restore with TWRP.
Read what @swedax94 wrote above and his thread
You also can read http://forum.xda-developers.com/showthread.php?t=2701376
I guided many on how to restore a backup made with TWRP

ckpv5 said:
[/HIDE]
Your error is different .. the libril-qc-qmi-1.so is modified and not pure stock. You need to replace this file with the stock one.
To make thing easier for you, just flash TWRP again and restore my 3.28.401.9 nandroid backup here : http://forum.xda-developers.com/showpost.php?p=56979449&postcount=2960
You can restore only the system part, keep your data part so you have pure stock system but your data intact.
Click to expand...
Click to collapse
ckpv5 said:
Link corrected.
You don't flash, you restore with TWRP.
Read what @swedax94 wrote above and his thread
You also can read http://forum.xda-developers.com/showthread.php?t=2701376
I guided many on how to restore a backup made with TWRP
Click to expand...
Click to collapse
OK I see, still downloading your nandroid.
I had a look at TWRP, just have to uncheck data then ? Am I correct ?
Thanks

snowfree52 said:
OK I see, still downloading your nandroid.
I had a look at TWRP, just have to uncheck data then ? Am I correct ?
Thanks
Click to expand...
Click to collapse
Yes .. uncheck data if you want to keep your data.
If you want everything fully stock, then check all boot, data and system.. it's your choice.

Should I also restore the boot part or only system is good ?
Thanks !

snowfree52 said:
Should I also restore the boot part or only system is good ?
Thanks !
Click to expand...
Click to collapse
Only system is good enough but selecting boot make no harm.
BTW @sudaltsov - how's thing going ?

ckpv5 said:
Only system is good enough but selecting boot make no harm.
BTW @sudaltsov - how's thing going ?
Click to expand...
Click to collapse
OK, did it !
Is it normal that it's still showing HTC boot logo after already 10 minutes ?

snowfree52 said:
OK, did it !
Is it normal that it's still showing HTC boot logo after already 5 minutes ?
Click to expand...
Click to collapse
Lets wait for 10 mins. If still not booting, go back to recovery select system & boot (I expect you have stock boot.img installed), then wipe dalvik & cache before reboot.
You have TWRP 2.8.4.0 installed right ?
If it's still fail to boot, then make a backup of your data then restore data from the downloaded nandroid. This will make you have a new set up phone.

ckpv5 said:
Lets wait for 10 mins. If still not booting, go back to recovery select system & boot (I expect you have stock boot.img installed), then wipe dalvik & cache before reboot.
Click to expand...
Click to collapse
It worked ! thank you
now what ? I replace TWRP recovery with the one from the OTA update then try again to install it ?

snowfree52 said:
It worked ! thank you
now what ? I replace TWRP recovery with the one from the OTA update then try again to install it ?
Click to expand...
Click to collapse
Yes..install the stock recovery then check OTA, download and install
And also note that after a successful update to lollipop, it will take some time for it to complete boot and optimizing ..

ckpv5 said:
Yes..install the stock recovery then check OTA, download and install
And also note that after a successful update to lollipop, it will take some time for it to complete boot and optimizing ..
Click to expand...
Click to collapse
Well didn't work again !
My M8 is european, the lockscreen from your nandroid is different than mine
edit : I see, in parameters, it now says my firmware is 1.54.401.10 ??? and android 4.4.2. How comes ???
I guess I restored an old nandroid of mine !
I see, I didn't put your nandroid in the right folder ! where should I put it ?

snowfree52 said:
Well didn't work again !
My M8 is european, the lockscreen from your nandroid is different than mine
edit : I see, in parameters, it now says my firmware is 1.54.401.10 ??? and android 4.4.2. How comes ???
I guess I restored an old nandroid of mine !
I see, I didn't put your nandroid in the right folder !
Click to expand...
Click to collapse
Never mind ... try again.
Remember when you extract the nandroid zip using extract to 3.28.401.9_ckpv5, there will be another folder inside it, use extract here then you get 3.28.401.9 folder

ckpv5 said:
Never mind ... try again.
Remember when you extract the nandroid zip using extract to 3.28.401.9_ckpv5, there will be another folder inside it, use extract here then you get 3.28.401.9 folder
Click to expand...
Click to collapse
That's what I didn't do !
restoring right now ! :good:

ckpv5 said:
extract out the recovery.img ---this is the correct recovery image to use.
Click to expand...
Click to collapse
That worked! Thank you very much!! There were some errors in the recovery, actually - but at least the installation process passed. Hurray! Thank you again!

[RECOVERY][unofficial][anthias / zenwatch] TWRP 3.0.2

TWRP recovery 3.0 zenwatch
How to install ​Use this giude to unlock bootloader and boot fastboot/recovery
http://forum.xda-developers.com/zenwatch/general/guide-how-to-access-recovery-zenwatch-t3167623
Warning ! Unlock bootloader wipe your data!​
update
Twrp 3.0.2 For android wear 1.4
NOT INSTALL ON ANDROID WEAR 1.3 !
Download twrp 3.0.2
installation
Code:
fastboot flash recovery twrp-3.0.2_anthias.img
Photos
{
"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"
}
Stock Recovery for Android Wear 1.4
installation stock recovery
Download stock recovery
Code:
fastboot flash recovery recovery_MEC23S.img
OLD VERSION FOR ANDROID WEAR 1.5 / TWRP 3.0 /TWRP 3.0.1
Download twrp 3.0.1-0 Zenwtach AW 1.4
Download twrp 3.0
OLD VERSION FOR ANDROID WEAR 1.3 / TWRP 2.8.7.0
old version (for android wear 1.3) download twrp mega.nz
Reboot into bootloader and flash recovery
Code:
fastboot flash recovery twrp_2.8.7.0_anthias.img
source https://github.com/asyan4ik/asus_anthias/tree/master

acbka said:
Twrp recovery 2.8.7.0 zenwatch
How to install ​
Use this giude to unlock bootloader and boot fastboot/recovery
http://forum.xda-developers.com/zenwatch/general/guide-how-to-access-recovery-zenwatch-t3167623
Warning ! Unlock bootloader wipe your data!
download twrp basketbuild.com
Reboot into bootloader and flash recovery
Code:
fastboot flash recovery twrp_2.8.7.0_anthias.img
Click to expand...
Click to collapse
I am not able to download the file. Getting a 404 error off the page. Any chance you could upload it to another service?
Thanks in advance!

btonetbone said:
I am not able to download the file. Getting a 404 error off the page. Any chance you could upload it to another service?
Thanks in advance!
Click to expand...
Click to collapse
Same. Thanks.

Ups , i fix this today ...
Sorry

hecksagon said:
Same. Thanks.
Click to expand...
Click to collapse
reload to mega . sorry

Fantastic! Flashed it and used it to flash a Wear version of SuperSU. Watch is rooted, without having to use KingRoot!
Let's see, somebody posted a system image a while back, didn't they? I guess I could flash that to unroot if there's a firmware update.

CSX321 said:
Fantastic! Flashed it and used it to flash a Wear version of SuperSU. Watch is rooted, without having to use KingRoot!
Let's see, somebody posted a system image a while back, didn't they? I guess I could flash that to unroot if there's a firmware update.
Click to expand...
Click to collapse
Yes, I pulled a system image and another user modified to successfully pass the checks that occur during updates (the original pull didn't pass). Check out this thread: http://forum.xda-developers.com/zenwatch/development/root-t3163248
Makes sure you read up on it, though, as it sounds like you'd need to do some legwork to get the system image to work. Relevant posts in that thread are 32, 52, and 54.
Hopefully, though, having TWRP means that someone smarter-than-I-am may develop even more elegant solutions!
Cheers!

Now that we have twrp we can do a system pull from an unrooted device. The system image posted in the other thread will only work on the previous version of Android Wear. Do not flash if you are up to date.

Flashing the system.img for the ZenWatch on LCA43 does work but I wouldn't recommend it (I had to recently wipe my watch to test something), as long as you do an update path from flashing to directly flashing the OTA zip, but it's long winded (of course now that we have TWRP, updates and flashing back to "stock" will be so much easier). That, and KingRoot seems to leave a lot of trace files.
Also as a sidenote, because of SuperSu, I was able to install Stericson's BusyBox from the app (sideloaded apk). KingRoot's root authorization window didn't play well with Android Wear.

itechnoguy said:
Flashing the system.img for the ZenWatch on LCA43 does work but I wouldn't recommend it (I had to recently wipe my watch to test something), as long as you do an update path from flashing to directly flashing the OTA zip, but it's long winded (of course now that we have TWRP, updates and flashing back to "stock" will be so much easier). That, and KingRoot seems to leave a lot of trace files.
Also as a sidenote, because of SuperSu, I was able to install Stericson's BusyBox from the app (sideloaded apk). KingRoot's root authorization window didn't play well with Android Wear.
Click to expand...
Click to collapse
The current system image in the other thread still has Kingroot on it. After removing that I tried to flash SuperSU but that force closes. Would like to get somebody who has not rooted to do a twrp backup and post it. We should be able to make a new flashable clean system image from that.

hecksagon said:
The current system image in the other thread still has Kingroot on it. After removing that I tried to flash SuperSU but that force closes. Would like to get somebody who has not rooted to do a twrp backup and post it. We should be able to make a new flashable clean system image from that.
Click to expand...
Click to collapse
Make sure you're using this zip file to install SuperSU (it seems to be the same binary as Chainfire's) since the app itself doesn't work, and this one doesn't require authorizations (not completely safe, but it works).
(also, don't forget to unroot from the KingRoot app first; the unroot seems to be clean enough to use Wear SuperSU)

itechnoguy said:
Make sure you're using this zip file to install SuperSU
Click to expand...
Click to collapse
That's the one I used, and it works. (Though there's no authorization popups, as you said.)

Theres an app called Super SUMe, in the Play Store that'll switch out KingRoot for SuperSU. Super easy to do, one click to complete the process. Have no idea if it'll work on watches, but I guess it doesnt hurt to try? Make sure you make backup first, now that TWRP is available..
Hoping to get this watch today! or maybe the Moto360..

Talysdaddy said:
Theres an app called Super SUMe, in the Play Store that'll switch out KingRoot for SuperSU. Super easy to do, one click to complete the process. Have no idea if it'll work on watches, but I guess it doesnt hurt to try? Make sure you make backup first, now that TWRP is available..
Hoping to get this watch today! or maybe the Moto360..
Click to expand...
Click to collapse
It'll probably remove KingRoot successfully, but the Zenwatch can't launch the SuperSU app, so root authorization dialogs never show up (the su binary still gets installed, but it can't do anything without permission from the app first).

Boooooo moto 360. It's sooo damn big.

@acbka How did you set up your build environment? I wasn't exactly sure what to initially use (other than not using the CyanogenMod sources since it doesn't work well with building TWRP; I'm assuming Omni 5?).

itechnoguy said:
@acbka How did you set up your build environment? I wasn't exactly sure what to initially use (other than not using the CyanogenMod sources since it doesn't work well with building TWRP; I'm assuming Omni 5?).
Click to expand...
Click to collapse
hi . i update first message .
add my github

Message for all you zenwatch 2 people.. Don't try to flash this recovery. You will have a soft brick. And with no resources at this time. There is no fix.
Sent from my ASUS_Z00A using Xparent BlueTapatalk 2

Has anyone pulled the stock system partition? I, stupidly, didn't do it before I installed SuperSU. I'd like to be able to go back to stock, if there's another firmware update.

I need a link to the stock recovery.IMG file

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