[ROM] Sony Smartwatch 3 ROM [LCA43] - Sony Smartwatch 3

ROM for Sony Smartwatch 3 [LCA43, Android 5.1.1]​
ROM Features:
Stock LCA43 base
Disabled OTA updates
Custom Kernel tetra_2.x
TWRP recovery
Tweaks
Click to expand...
Click to collapse
Versions
v 2.0
Kernel tetra_2.27.1
Minor tweaks
v 1.0
Stock LCA43 base
Kernel tetra_2.22
Disabled Low Bit Ambient Mode (thanks to andrewia)
Minor tweaks
Click to expand...
Click to collapse
Installation:
Put ROM to your virtual SDCard
Boot into TWRP recovery
Select "Install", and choose ROM zip file
After installation completed- reboot watch
If necessary - make full wipe
Click to expand...
Click to collapse
Downloads
SW3_rom_v2
TWRP recovery
Click to expand...
Click to collapse
Big thanks to scrubber for his ROM backup!
Code:
[COLOR="Red"]DISCLAMER[/COLOR]
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or
you getting fired because the alarm app failed. Please do some research if you
have any concerns about features included in this ROM before flashing it!
YOU are choosing to make these modifications, and if you point the finger
at me for messing up your device, I will laugh at you.
If you like my work- Donate to me
Contributors:
alex6600
scrubber
Version Information
Status: Stable
Created 2016-04-27
Last Updated 2016-05-11

Reserved by OP

thanks alex6600.
can you upload original kernel to ?
edit : found on 4pda https://mega.nz/#!Rt8hBS5T!MHOufeqXYJqrcShyXG2_f3uLO7_ZlP_H6T0cVm0R4Hk
thanks again.

Thanks @alex6600!
Just factory reset, and downgraded from Marshmallow, to this ROM.
All is working well so far!

crunchybutternut said:
Thanks @alex6600!
Just factory reset, and downgraded from Marshmallow, to this ROM.
Click to expand...
Click to collapse
I honestly tried to use Marshmallow. Compiles kernels dozens of times. But no luck.
Reboots and lags does not suit me.
And decides to use 5.1.1, as more stable.

I'm all about this ROM as Marshmallow has just been one big rebooting mess!
However, during flashing everything went fine except the build.prop install...
Your line:
mount("ext4", "EMMC", "/dev/block/platform/sdhci.1/by-name/system", "/system", "max_batch_time=0,commit=1,data=ordered,barrier=1,errors=panic,nodelalloc");
Click to expand...
Click to collapse
Fails saying device is busy, or is not ready...???

Hobbzey said:
I'm all about this ROM as Marshmallow has just been one big rebooting mess!
However, during flashing everything went fine except the build.prop install...
Your line:
Fails saying device is busy, or is not ready...???
Click to expand...
Click to collapse
Did you mount system in twrp before install?
Sent from my HTC One_M8 using XDA-Developers mobile app

I got it sorted out actually, turns out it was because I was using the version of TWRP I got from here:
http://forum.xda-developers.com/sma...24h-twrp-root-busybox-kernel-adiutor-t3365990
I initially skipped installing the one you provided above because I already had that one installed, but switched to the one you provided and reflashed with no errors!
One last question, is it possible to turn off the rounded screen corners? Is that something that can be edited into the build.prop or is it in kernel?

Hobbzey said:
I got it sorted out actually, turns out it was because I was using the version of TWRP I got from here:
http://forum.xda-developers.com/sma...24h-twrp-root-busybox-kernel-adiutor-t3365990
I initially skipped installing the one you provided above because I already had that one installed, but switched to the one you provided and reflashed with no errors!
One last question, is it possible to turn off the rounded screen corners? Is that something that can be edited into the build.prop or is it in kernel?
Click to expand...
Click to collapse
Rounded screen corners is a kernel feature, not ROM.

And do you recommend your LCA43 kernel from here http://forum.xda-developers.com/sma...ment/kernel-sony-smartwatch-3-kernel-t3304102 or should we stick with the one already in the rom? Or are they one and the same?

Hobbzey said:
And do you recommend your LCA43 kernel from here http://forum.xda-developers.com/sma...ment/kernel-sony-smartwatch-3-kernel-t3304102 or should we stick with the one already in the rom? Or are they one and the same?
Click to expand...
Click to collapse
Rom include kernel v. 2.22.
Today I posted 2.23 in kernel thread.
Sent from my HTC One_M8 using XDA-Developers mobile app

Hi everyone, could someone please help me? I'm trying to downgrade my SW3 from MM to this rom, but I don't know how to do it. I've got installed windroid toolkit but it doesn't anything. I can't install twrp, unlock bootloader... nothing. I've got correctly installed ADB drivers, windroid recognises my watch, but this is everything I can do until here. I'm trying to do the downgrade because my battery flies twice per day, meanwhile in MM battery lasted up to 4 days... Has someone the same problem?

asecob said:
Hi everyone, could someone please help me? I'm trying to downgrade my SW3 from MM to this rom, but I don't know how to do it. I've got installed windroid toolkit but it doesn't anything. I can't install twrp, unlock bootloader... nothing. I've got correctly installed ADB drivers, windroid recognises my watch, but this is everything I can do until here. I'm trying to do the downgrade because my battery flies twice per day, meanwhile in MM battery lasted up to 4 days... Has someone the same problem?
Click to expand...
Click to collapse
Reboot to Fastboot, and flash the TWRP .img from there. (note: be sure you are in the directory where the twrp.img file is stored)
Code:
adb reboot bootloader
fastboot flash boot [I]twrp.img[/I]
fastboot reboot
adb reboot recovery
And viola. You can then flash this ROM.

Do you plan feature 6.0.1 update? What are benefits over stock...?

crunchybutternut said:
Reboot to Fastboot, and flash the TWRP .img from there. (note: be sure you are in the directory where the twrp.img file is stored)
Code:
adb reboot bootloader
fastboot flash boot [I]twrp.img[/I]
fastboot reboot
adb reboot recovery
And viola. You can then flash this ROM.
Click to expand...
Click to collapse
Thank you for your help, but unfortunately my watch didn't pass the white screen saying fastboot. PC was saying "waiting for device" for so much time. Am I doing something wrong?

crunchybutternut said:
Reboot to Fastboot, and flash the TWRP .img from there. (note: be sure you are in the directory where the twrp.img file is stored)
Code:
adb reboot bootloader
fastboot flash boot [I]twrp.img[/I]
fastboot reboot
adb reboot recovery
And viola. You can then flash this ROM.
Click to expand...
Click to collapse
Hello and thanks for the command lines.
I want to try it because my battery drain is too high with MM and kernel 3.10.1 (but no reboots).
But .... How can I use the virtual SDCARD? How do I have to do to put the zip file in this SD? AFter, I think it will be ok....
Thanks.
It's OK actually, just after twrp flash, I have "VIRTUAL SDCARD" on my windows pc, I put the zip and I flashed it in recovery.
Thanks

mickael91210 said:
Hello and thanks for the command lines.
I want to try it because my battery drain is too high with MM and kernel 3.10.1 (but no reboots).
But .... How can I use the virtual SDCARD? How do I have to do to put the zip file in this SD? AFter, I think it will be ok....
Thanks.
Click to expand...
Click to collapse
When the watch is connected to computer, type:
adb push rom_file.zip /sdcard/Download/
This command will copy ROM to /sdcard/Download directory.

alex6600 said:
When the watch is connected to computer, type:
adb push rom_file.zip /sdcard/Download/
This command will copy ROM to /sdcard/Download directory.
Click to expand...
Click to collapse
Thanks.... I was editing my post in the same time....
Thank you

More excellent work! Will we be able to root this (i.e. flash supersu.zip in TWRP)? Also, I can't seem to access the files (ROM.zip, TWRP.img), is the site down?

KittenSauce said:
More excellent work! Will we be able to root this (i.e. flash supersu.zip in TWRP)? Also, I can't seem to access the files (ROM.zip, TWRP.img), is the site down?
Click to expand...
Click to collapse
Webserver was in the planned maintenance. Now everything is working as it should.
SuperSu work fine. You can download SuperSu_2.46 here

Related

Jellybean root

ok you need to have clockworkmod installed...
Code:
fastboot flash recovery recovery.img
(insecure boot.img)
unzip boot.img.zip, boot to bootloader and
Code:
fastboot flash boot boot.img
or flash JRN84D-insecure-boot.zip from recovery
-put the CWM-SuperSU-v0.92-mod.zip on your sd and flash
done. :good:
if you have problems...
flash Koush's Jellybean repack (IMM76I OR IMM30D) http://d-h.st/Gkh
If recovery isn't sticking for you, delete recovery-from-boot.p in /system
I can do this for the other superuser as well...this is chainfire's super su
Thanks. May I clarify if I have to do both to get root or either one?
mcdull said:
Thanks. May I clarify if I have to do both to get root or either one?
Click to expand...
Click to collapse
the boot image is insecure...not necessarily needed
Oic.. thanks alot.
Is there any chance to pack the insecure kernel into cwm package as well?
I have no access to computer that allow me to apply fastboot flash. I am sure a lot of ppl will be in the same situation. Thanks alot.
mcdull said:
Oic.. thanks alot.
Is there any chance to pack the insecure kernel into cwm package as well?
I have no access to computer that allow me to apply fastboot flash. I am sure a lot of ppl will be in the same situation. Thanks alot.
Click to expand...
Click to collapse
sure, give me a minute
Okay I installed the jellybean rom from rom manager but I lost clockwork recovery, anyone got any suggestions?
pablo1215 said:
Okay I installed the jellybean rom from rom manager but I lost clockwork recovery, anyone got any suggestions?
Click to expand...
Click to collapse
bootloader mode -> reflash clockwork recovery using fastboot.
pablo1215 said:
Okay I installed the jellybean rom from rom manager but I lost clockwork recovery, anyone got any suggestions?
Click to expand...
Click to collapse
fastboot a new one in...new one will stick
Code:
fastboot flash recovery recovery.img
Thanks guys appreciate the tip.
not working
Just flashed the two .zips. SuperSU is installed, but it says that the binary needs to be updated. When it tries to update it fails, and no root apps work.
krishmasand said:
Just flashed the two .zips. SuperSU is installed, but it says that the binary needs to be updated. When it tries to update it fails, and no root apps work.
Click to expand...
Click to collapse
reboot, then open supersu and then update
Worked like a charm, I've got clockwork back after a little adb action and now I'm restoring some apps with titanium. Can't wait to see the development on this. Just think I almost sold this phone and bought a Galaxy S3 today, may wait a week or so now.
Thanks guys you are amazing!!!
Flashed both zips in cwm
Super su app is there but needs to update binary
It fails on update
tramane said:
Flashed both zips in cwm
Super su app is there but needs to update binary
It fails on update
Click to expand...
Click to collapse
ok your the second guy...first hasn't responded back. did you reboot and try again?
which "jellybean" version are you on? koush's on rom manager seems to be the best (no wifi issues for one)
ogdobber said:
fastboot a new one in...new one will stick
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Is there a reason why my CWM won't stick? I fastboot a new one in and right after, I can access CWM from the bootloader menu if I don't boot into the OS yet. However, once I do boot into the OS and use ADB to reboot into recovery, it goes back to the Android with the red triangle.
What am I doing wrong? I'm usually pretty good with this stuff.
other superuser
still doesn't work, do you think you can try the other SuperUser app? D:
Enhanced said:
Is there a reason why my CWM won't stick? I fastboot a new one in and right after, I can access CWM from the bootloader menu if I don't boot into the OS yet. However, once I do boot into the OS and use ADB to reboot into recovery, it goes back to the Android with the red triangle.
What am I doing wrong? I'm usually pretty good with this stuff.
Click to expand...
Click to collapse
You'll need to delete that recovery from boot.p file otherwise it'll keep deleting CWM
[please delete]
IINexusII said:
You'll need to delete that recovery from boot.p file otherwise it'll keep deleting CWM
Click to expand...
Click to collapse
I knew common sense told me that I would need to delete the /system/recovery-from-boot.p file, but it wasn't posted here so I didn't bother.
Thanks.

[Q] New user rooted unworking phone

Android 4.2.2
HTC Sense 5.5
Software number NuSenseONE-KitKat-m7vzw_RD.1.0_4.19.631.9
HTC ASK ALI level 5.68
Kernel Version 3.4.10-NUM3rn3l- kk-S55
Phone doesn't connect to moblie data .
Xposed installer not working
SuperSU binary not installed?
I just need my phone back to normal I'll figure out this SU and root thing later. Factory reset doesn't do anything. Screen says I'm running a developer version of the OS
Help thanks
Jamesdbritt said:
Android 4.2.2
HTC Sense 5.5
Software number NuSenseONE-KitKat-m7vzw_RD.1.0_4.19.631.9
HTC ASK ALI level 5.68
Kernel Version 3.4.10-NUM3rn3l- kk-S55
Phone doesn't connect to moblie data .
Xposed installer not working
SuperSU binary not installed?
I just need my phone back to normal I'll figure out this SU and root thing later. Factory reset doesn't do anything. Screen says I'm running a developer version of the OS
Help thanks
Click to expand...
Click to collapse
did you make a backup of your stock rom or the rom you had before you flashed the one you are currently having problems with?
nty123 said:
did you make a backup of your stock rom or the rom you had before you flashed the one you are currently having problems with?
Click to expand...
Click to collapse
I was not the one that flashed the rom. I bought the phone three days ago and it was already like this.
Jamesdbritt said:
I was not the one that flashed the rom. I bought the phone three days ago and it was already like this.
Click to expand...
Click to collapse
can you boot into recovery? either twrp or cwm
some updates.. I've been working on it.
Android 4.2.2
HTC Sense 5.5
Software number NuSenseONE-KitKat-m7vzw_RD.1.0_4.19.631.9
HTC ASK ALI level 5.68
Kernel Version 3.4.10-NUM3rn3l- kk-S55
???Phone doesn't connect to moblie data ???
Installed HTC Sync Manager to PC
on Device
Went into boot menu and went to recovery TWRP reinstalled SuperSU and Xposed installer
what is a ROM ? what do I do with the SDK bundle?
Jamesdbritt said:
some updates.. I've been working on it.
Android 4.2.2
HTC Sense 5.5
Software number NuSenseONE-KitKat-m7vzw_RD.1.0_4.19.631.9
HTC ASK ALI level 5.68
Kernel Version 3.4.10-NUM3rn3l- kk-S55
???Phone doesn't connect to moblie data ???
Installed HTC Sync Manager to PC
on Device
Went into boot menu and went to recovery TWRP reinstalled SuperSU and Xposed installer
what is a ROM ? what do I do with the SDK bundle?
Click to expand...
Click to collapse
a rom is a modified software of android from a developer that you can install on your phone through a recovery, it's good that you can boot into recovery but, I'm not completely sure what's going on, the rom that is currently on your device could have a problem and not able to connect to mobile data. you could download a different rom and flash it onto your phone and see if that fixes it, there are plenty of amazing ones to choose from on this forum http://forum.xda-developers.com/verizon-htc-one/development even though you have the mobile data problem on your current rom i would still make a backup of your current rom to go back to incase anything happens when (if) you flash a different one
nty123 said:
a rom is a modified software of android from a developer that you can install on your phone through a recovery, it's good that you can boot into recovery but, I'm not completely sure what's going on, the rom that is currently on your device could have a problem and not able to connect to mobile data. you could download a different rom and flash it onto your phone and see if that fixes it, there are plenty of amazing ones to choose from on this forum http://forum.xda-developers.com/verizon-htc-one/development even though you have the mobile data problem on your current rom i would still make a backup of your current rom to go back to incase anything happens when (if) you flash a different one
Click to expand...
Click to collapse
I am not sure how to flash roms is there a guide?
Jamesdbritt said:
I am not sure how to flash roms is there a guide?
Click to expand...
Click to collapse
there are many videos online but its pretty easy, find a rom and gapps (if its included with the rom) then download those two to your sd card( make sure they are in .zip format) once downloaded boot into twrp and choose the backup icon and swipe to backup. when that's done you will press the wipe icon and perform a factory reset(you lose all data so make sure you have contacts synced to google) when its done wiping your data go back and install zip and locate the downloaded rom and choose that then if you downloaded the gapps(google apps) choose add more zips near the bottom and find that .zip. when you have everything you will then swipe to flash. when its done tap reboot and it will load your new rom.
nty123 said:
there are many videos online but its pretty easy, find a rom and gapps (if its included with the rom) then download those two to your sd card( make sure they are in .zip format) once downloaded boot into twrp and choose the backup icon and swipe to backup. when that's done you will press the wipe icon and perform a factory reset(you lose all data so make sure you have contacts synced to google) when its done wiping your data go back and install zip and locate the downloaded rom and choose that then if you downloaded the gapps(google apps) choose add more zips near the bottom and find that .zip. when you have everything you will then swipe to flash. when its done tap reboot and it will load your new rom.
Click to expand...
Click to collapse
ok I am going to try ViperOne 5.0.0 | 4.19.401.8
ok so why backup the settings if they aren't working now?
Jamesdbritt said:
ok I am going to try ViperOne 5.0.0 | 4.19.401.8
ok so why backup the settings if they aren't working now?
Click to expand...
Click to collapse
Maybe this will save you some time.
Maybe not....
Did you put a working active Sim card of your own into the phone?
That ROM that's on the phone currently, works just fine for verizon cell and data services.
You're welcome to change the ROM to whatever one you want.
Just trying to help you find the actual root of your problem.
Sent from my HTC6435LVW using Tapatalk
Sounds like you're new to the world of modding which is perfectly fine because we all had to start somewhere. You want to familiarize yourself with the basics before you get too far over your head though. Here's a basic terminology guide that will help you right now: http://www.gizmodo.co.uk/2013/05/the-dummys-guide-to-android-rooting-everything-you-need-to-know/
I don't know what the person before you did, but as santod has explained NuSense has perfectly working data. I'm using it now and have never had issue. It's my personal favorite rom, but there are many out there right now you should be trying out for yourself and forming your own conclusions. Almost everyone will have a different opinion on the "best rom" which is why it's a question you'll see avoided around here. Personally, I would start on a "stock" rom like the one offered here: http://forum.xda-developers.com/showthread.php?t=2485319. That thread also includes very important instructions on how to update your firmware (for better radio performance among other things). Good luck and don't be afraid to ask questions before doing something you're not sure of.
No operating system
accidently wiped everything clean the PC cannot recognize the device says I need a driver. I still have twrp but the backup was wiped on accident what do I do to fix it?
I think you'll have to push a rom from your computer to the phone using ADB and then flash it in recovery. I've never had to do that so hopefully someone can chime in with more details.
You need the adb debugging tools installed on your computer. Plus HTC drivers. Once you have those installed, you can try flashing a RUU. Here's 4.2.2 RUU http://www.htc1guru.com/2013/11/verizon-ruu-zip-1-10-605-10-posted/ . This tells you how to setup adb http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/ . To flash the RUU, place the RUU in the same folder as your adb tools, and rename it RUU.zip. In the command prompt type, fastboot oem rebootRUU , then hit enter. Then type, fastboot flash zip RUU.zip ,then hit enter. Afterit finishes you'll have to type fastboot flash zip RUU.zip one more time . Then after about ten minutes it will finish and you'll type fastboot reboot-hboot. Then restart phone.
joeymagnus1 said:
You need the adb debugging tools installed on your computer. Plus HTC drivers. Once you have those installed, you can try flashing a RUU. Here's 4.2.2 RUU http://www.htc1guru.com/2013/11/verizon-ruu-zip-1-10-605-10-posted/ . This tells you how to setup adb http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/ . To flash the RUU, place the RUU in the same folder as your adb tools, and rename it RUU.zip. In the command prompt type, fastboot oem rebootRUU , then hit enter. Then type, fastboot flash zip RUU.zip ,then hit enter. Afterit finishes you'll have to type fastboot flash zip RUU.zip one more time . Then after about ten minutes it will finish and you'll type fastboot reboot-hboot. Then restart phone.
Click to expand...
Click to collapse
the howtogeek site will not come up it crashes IE everytime
the more I read , everything says I need HTC windows seven drivers where can I get them I can not find a reliable source
Read there are plenty of things on the net that will help you with your problems.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
http://vzw1files.dyndns.org/ADB/
bigjohn6582 said:
Read there are plenty of things on the net that will help you with your problems.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
this did not help at all
cmlusco said:
http://vzw1files.dyndns.org/ADB/
Click to expand...
Click to collapse
Great link but does not at all address the question. this thread can be closed problem was solved by @clsA @alray and @nkk71

Can't install CM11 Snapshot M7 on HTC One VZW

I moved from Clockworkmod Recovery to the latest version of TWRP(2.7.1.1) and while trying to flash CM11 Snapshot M7 I receive an error. The error is as followed: "This package is for "m7wlv,m7vzw" devices; this is a "m7".
Also while flashing TWRP I found this nifty guide and was wondering if this would work fine with any compatible recovery for the HTC One M7.
Code:
Download the above file(was a recovery .img file. Save it to the root of your /sdcard directly (internal memory only) and rename it to recovery_name.img
Launch terminal emulator or connect to your computer and open an adb shell, then type the following:
su
dd if=/sdcard/recovery_name.img of=/dev/block/mmcblk0p34
Then reboot to complete installation
You need to update TWRP since to the latest version (2.7.1.1). There was an update from HTC that changed fstab partitioning.
http://techerrata.com/browse/twrp2/m7vzw
To update your recovery:
Boot into Fastboot via Bootloader
On your computer, browse to the same folder where you downloaded the latest TWRP.
Type: fastboot flash recovery filename.zip
Boot into recovery.
Click to expand...
Click to collapse
tflogic said:
You need to update TWRP since to the latest version (2.7.1.1). There was an update from HTC that changed fstab partitioning.
http://techerrata.com/browse/twrp2/m7vzw
To update your recovery:
Click to expand...
Click to collapse
Sorry, I don't know what led to me putting the wrong version in my post, but I am running 2.7.1.1.
I'd like to note that I'm running a M4 Snapshot just fine.
vpxf said:
Sorry, I don't know what led to me putting the wrong version in my post, but I am running 2.7.1.1.
I'd like to note that I'm running a M4 Snapshot just fine.
Click to expand...
Click to collapse
I think you're running the 'm7' version of TWRP instead of 'm7vzw'. Try a new recovery and double check that you've got the right one.
durgis said:
I think you're running the 'm7' version of TWRP instead of 'm7vzw'. Try a new recovery and double check that you've got the right one.
Click to expand...
Click to collapse
Ah, I did not know there was a difference. I'll take a look for the proper recovery when I have time and then follow up. Thanks.
That did the trick, thank you. I must of followed the wrong link.

Stuck rooting

Hi all, so I have Verizon's Pixel XL. I have unlocked it successfully and had rooted. I asked on the forums about upgrading the OTA update and was told it was fine. After doing so, I noticed my SuperSU was gone (although I might have lost it earlier and not noticed). So after trying to get it back and keeping getting stuck, I bit the bullet and ADB sideloaded the factory image from google (NDE63X) and got it able to boot up. Yay.
So then I ran the 'adb reboot bootloader' command, then verified my device was connected with 'fastboot devices' and finally I ran 'fastboot boot boot-to-root.img'. And here I am, stuck on the splash screen again.
So I looked around and saw some mentions of people that had used older versions of Chainfire's SuperSU. I tried the newer one (2.78 SR3) and the same thing happened. I do see that there is a SR5, but I also see Chainfire's comment "Do not use the SuperSU ZIP on work-in-progress TWRP releases for Pixel, it will not work - use the model specific links above instead.
I can get it to run just fine without using chainfire's supersu...but then I don't have the supersu app or any real gains from having rooted.
So, I feel like I must be doing something wrong. Any suggestions?
@smokeydriver,
You probably should update your Android SDK package. This problem can also be caused by an obsolete fastboot.
cam30era said:
@smokeydriver,
You probably should update your Android SDK package. This problem can also be caused by an obsolete fastboot.
Click to expand...
Click to collapse
I can give it a shot, but I only installed minimal adb yesterday on my new laptop. Thanks!
smokeydriver said:
I can give it a shot, but I only installed minimal adb yesterday on my new laptop. Thanks!
Click to expand...
Click to collapse
I understand. Here's the thing: I don't know if minimal has up to date ADB and fastboot for Android 7.1.1.
cam30era said:
I understand. Here's the thing: I don't know if minimal has up to date ADB and fastboot for Android 7.1.1.
Click to expand...
Click to collapse
The OTA update I took only got me to a new version of 7.1, not 7.1.1 (from NDE63P to NDE63X). It still shows an available update to 7.1.1 which I have *not* done.
Try using the Unified Toolkit. It saved me from having a bootloop disaster when I tried upgrading from 7.1.1 due to poor instruction availability around the web. It should fix whatever problem you are having, even if that means flashing the factory image first again.
Nitemare3219 said:
Try using the Unified Toolkit. It saved me from having a bootloop disaster when I tried upgrading from 7.1.1 due to poor instruction availability around the web. It should fix whatever problem you are having, even if that means flashing the factory image first again.
Click to expand...
Click to collapse
I've tried, but keep getting an error 21 code that it can't install...I tried this with SR5 and SR2.
How I Rooted
Personally, I'd flash to latest OTA via Unified Android Toolkit before starting this process.
Then use Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)
AT this point you should already have 2 zips on your phone, TWRP-RC1 and SuperSU v5.
Flash TWRP, then SuperSU.
Reboot into OS, confirm root, give it 5 minutes.
Reboot back to Recovery and flash Kernel if desired.
Do not flash root with RC-1 (thats why we flashed root while using Alpha2 adb twrp.img), do not restore backups made with Alpha2 using RC1 or vic versa. AKA Backup and Restore with same version of TWRP.
FreeSoftwareServers said:
Personally, I'd flash to latest OTA via Unified Android Toolkit before starting this process.
Then use Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)
AT this point you should already have 2 zips on your phone, TWRP-RC1 and SuperSU v5.
Flash TWRP, then SuperSU.
Reboot into OS, confirm root, give it 5 minutes.
Reboot back to Recovery and flash Kernel if desired.
Do not flash root with RC-1 (thats why we flashed root while using Alpha2 adb boot.img), do not restore backups made with Alpha2 using RC1 or vic versa. AKA Backup and Restore with same version of TWRP.
Click to expand...
Click to collapse
Ok, I must be doing something wrong on a very basic level. It gave me error 21 (signature verification error) when trying to use the unified android tookit to install 7.1. Anyways, I'll just move on and skip that step and see what happens.
Flashing SuperSU SR5 works just fine with TWRP RC1. All you have to do is delete the file you're told to before flashing.
Dees_Troy said:
How to install SuperSU SR5 on TWRP RC1: In TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it.
Click to expand...
Click to collapse
FreeSoftwareServers said:
Personally, I'd flash to latest OTA via Unified Android Toolkit before starting this process.
Then use Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)
AT this point you should already have 2 zips on your phone, TWRP-RC1 and SuperSU v5.
Flash TWRP, then SuperSU.
Reboot into OS, confirm root, give it 5 minutes.
Reboot back to Recovery and flash Kernel if desired.
Do not flash root with RC-1 (thats why we flashed root while using Alpha2 adb twrp.img), do not restore backups made with Alpha2 using RC1 or vic versa. AKA Backup and Restore with same version of TWRP.
Click to expand...
Click to collapse
I transferred those 2 files to my download folder on my phone, ran the twrp.img script, and then when I go in...the file names are not normal. Everything is random letters and numbers. Again, I feel like I'm making some stupid basic mistake that I don't understand (and I've rooted plenty of phones).
spotmark said:
Flashing SuperSU SR5 works just fine with TWRP RC1. All you have to do is delete the file you're told to before flashing.
Click to expand...
Click to collapse
So I go in TWRP to advanced, file manager, and I don't see the names of those files. Are they buried in a folder?
smokeydriver said:
So I go in TWRP to advanced, file manager, and I don't see the names of those files. Are they buried in a folder?
Click to expand...
Click to collapse
You have TWRP RC1 installed?
spotmark said:
You have TWRP RC1 installed?
Click to expand...
Click to collapse
Nope...stuck before that. I'm using Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)...but then I go to the sd card and it's all random letters and numbers...so I can't install twrp rc1.
smokeydriver said:
Nope...stuck before that. I'm using Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)...but then I go to the sd card and it's all random letters and numbers...so I can't install twrp rc1.
Click to expand...
Click to collapse
Ah, I see. I misunderstood. I thought you were just under the impression that you couldn't flash SU with RC1. My apologies.
Ok, so can someone tell me why I am getting stuck with 1 thing. I go to my stock recovery and into ADB sideload. When I tell it the file, it keeps failing to verify whole-file signature. What is wrong with this one step?
Or alternatively...when I'm in TWRP Alpha 2- why are all the files within the sdcard random letters and numbers?
smokeydriver said:
Nope...stuck before that. I'm using Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)...but then I go to the sd card and it's all random letters and numbers...so I can't install twrp rc1.
Click to expand...
Click to collapse
Twrp is not decrypting you're data. Try rebooting twrp from fastboot a second time.
toknitup420 said:
Twrp is not decrypting you're data. Try rebooting twrp from fastboot a second time.
Click to expand...
Click to collapse
Son-of-a B#[email protected]#$. It asks me to 'decrypt data' by entering a password. I had hit cancel. What's the password??
smokeydriver said:
Son-of-a B#[email protected]#$. It asks me to 'decrypt data' by entering a password. I had hit cancel. What's the password??
Click to expand...
Click to collapse
Never mind...it's my 4 digit password that's used when my finger unlock doesn't work. Ugh- I knew it was something simple and dumb I was doing!
smokeydriver said:
Ok, so can someone tell me why I am getting stuck with 1 thing. I go to my stock recovery and into ADB sideload. When I tell it the file, it keeps failing to verify whole-file signature. What is wrong with this one step?
Or alternatively...when I'm in TWRP Alpha 2- why are all the files within the sdcard random letters and numbers?
Click to expand...
Click to collapse
Can I ask you how you fixed this? I'm having the same issue and this post popped up on Google.

[Metro][Stock] SOFIAP-T QPRS30.80.64.6.2

100% Stock ROM for the Metro by T-Mobile Moto G Stylus
Requirements:
ADB & Fastboot from here:
https://developer.android.com/studio/releases/platform-tools
ADB & Fastboot set into your OS environment
(This allows adb to be used in any folder)
Instructions here:
https://wiki.lineageos.org/adb_fastboot_guide.html#installing-adb-and-fastboot
7-Zip to extract the .7z file:
https://www.7-zip.org/
Download:
QPRS30.80.64.6.2
Older Downloads:
QPRS30.80.64.6
QPRS30.80.64.3
Flashing Instructions:
1. Extract the zip using 7-Zip
2. Boot into Fastboot
3. Run the flash-all.bat this should automatically start flashing all the partitions
This will wipe everything. If you want to keep your data, before running open the .bat file with a text editor and remove -w from
Code:
fastboot -w reboot
​
(If on another platform than Windows you'll need to change the .bat file to your OS)
Looking for the Retail variant Stock ROM?
See Here:
https://forum.xda-developers.com/mo...t/stock-rom-motorola-g-stylus-retail-t4104451
QPRS30.80.64.6
https://mega.nz/file/nQkRHByR#md9YeMeAS4Vp6_lhL3pm9Bbqx1JrCeMHW8Lbkzr1RQo
cbc0201 said:
QPRS30.80.64.6
https://mega.nz/file/nQkRHByR#md9YeMeAS4Vp6_lhL3pm9Bbqx1JrCeMHW8Lbkzr1RQo
Click to expand...
Click to collapse
Thanks for the download. I added to the OP with the flash-all.bat
DMedina559 said:
Thanks for the download. I added to the OP with the flash-all.bat
Click to expand...
Click to collapse
Okay so I have a question based on my observation maybe stupid may not be I don't care
Q: how do I identify if my phone is the RETUS or the SOFIAP-T?
Q: Sorry this is the observational question,the build number nomenclature in my phone does not have an s at the end of the QPR but in this forum it does but when you download the file it does not. Or does that not matter?
---------- Post added at 03:13 AM ---------- Previous post was at 03:09 AM ----------
LinuxAndroidAlwys said:
Okay so I have a question based on my observation maybe stupid may not be I don't care
Q: how do I identify if my phone is the RETUS or the SOFIAP-T?
Q: Sorry this is the observational question,the build number nomenclature in my phone does not have an s at the end of the QPR but in this forum it does but when you download the file it does not. Or does that not matter?
Click to expand...
Click to collapse
I have QPR30.80.64.6 model XT2043-4
LinuxAndroidAlwys said:
Okay so I have a question based on my observation maybe stupid may not be I don't care
Q: how do I identify if my phone is the RETUS or the SOFIAP-T?
Q: Sorry this is the observational question,the build number nomenclature in my phone does not have an s at the end of the QPR but in this forum it does but when you download the file it does not. Or does that not matter?
---------- Post added at 03:13 AM ---------- Previous post was at 03:09 AM ----------
I have QPR30.80.64.6 model XT2043-4
Click to expand...
Click to collapse
You should be able to tell in the about phone menu in the settings. And the S might be a typo I'm not sure I'll have to check
DMedina559 said:
You should be able to tell in the about phone menu in the settings. And the S might be a typo I'm not sure I'll have to check
Click to expand...
Click to collapse
I figured it out but I'm still confused about the s
LinuxAndroidAlwys said:
I figured it out but I'm still confused about the s
Click to expand...
Click to collapse
The s is just a typo on my end. I'll fix asap
Not sure If I'm in the rightr thread or not but need serious help !!! I had twrp on my phone was trying to reboot system and hit a slot phone went black and will not boot into fastboot turn on, nothing! It is as dead as a dorrnail ie hard bricked . I have loaded all the drivers for phone and qualcomm. Computer only recognizes phone as Qualcomm 9008 mode not bulk mode. Anyone know how to restore phone at least to be able to get into fadtboot? Anyone help would be very much appreciated this is my daily driver and I am screwed without it.
worked great
QPR30.80_64_6_2
https://mega.nz/file/2UMGDb7B#4OZmO_DMUXiJnSkuyf4Y1w3LHVxoXM-P7umpRUWqaAQ
LinuxAndroid4evr said:
Not sure If I'm in the rightr thread or not but need serious help !!! I had twrp on my phone was trying to reboot system and hit a slot phone went black and will not boot into fastboot turn on, nothing! It is as dead as a dorrnail ie hard bricked . I have loaded all the drivers for phone and qualcomm. Computer only recognizes phone as Qualcomm 9008 mode not bulk mode. Anyone know how to restore phone at least to be able to get into fadtboot? Anyone help would be very much appreciated this is my daily driver and I am screwed without it.
Click to expand...
Click to collapse
i did the same thing, booting into slot b got me into the device normally
cbc0201 said:
QPR30.80_64_6_2
https://mega.nz/file/2UMGDb7B#4OZmO_DMUXiJnSkuyf4Y1w3LHVxoXM-P7umpRUWqaAQ
Click to expand...
Click to collapse
Hey man this is my current version as well, but it doesnt have the flashall bat file, do you know if i could just use one from the links in the OP? i am new to flashing roms in this manner and i dont really know how it works
Updated OP with build QPRS30.80.64.6.2
CorporalCactus said:
Hey man this is my current version as well, but it doesnt have the flashall bat file, do you know if i could just use one from the links in the OP? i am new to flashing roms in this manner and i dont really know how it works
Click to expand...
Click to collapse
Yeah using the old flash-all.bat file works with newer builds, just put all the flahsing files in /Recovery-Files/ with the flash-all.bat outisde that folder
Is any way to completely delete Metro PCS bloatware? I have rooted phone. No success to delete bloatware. Can I replace Metro PCS ROM with retail ROM? Is that possible? Any ideas? Thank you
Hello please I used the Moto g stylus as well, using MetroPCS with QPRS30.80-64-6-2, I want to know if this rom is unlocked , will it remove the sim lock on my device as the remote unlock fails. Thanks
Hi new guy here. Got couple moto g stylus (2020 pro). Mine Ive tried out arrow, havoc cr stag, bliss and resurrection. My wife's exact same phone she decided to have me install resurrection remix and magisk root it. ADB installed until last step which was fastboot -w. Had error about not auto formatting RAW format. I managed to fix that but still boot looped or twrp 35. Sofia will load but can't install any rom from zip. Stag logo bootlooeded.. hard to even explain.. damn. Anyway
Any suggestions?
Where is the flash-all.bat ?
MotoLindvall said:
Hi new guy here. Got couple moto g stylus (2020 pro). Mine Ive tried out arrow, havoc cr stag, bliss and resurrection. My wife's exact same phone she decided to have me install resurrection remix and magisk root it. ADB installed until last step which was fastboot -w. Had error about not auto formatting RAW format. I managed to fix that but still boot looped or twrp 35. Sofia will load but can't install any rom from zip. Stag logo bootlooeded.. hard to even explain.. damn. Anyway
Any suggestions?
Click to expand...
Click to collapse
If you still need to figure out the crazy flashing procedure for our device...best answer is make sure you are on STOCK Android 10...if you have updated to Android 11 you will not be able to flash custom ROMs or have a fully functional TWRP recovery...and Magisk root is not good with A11..You can flash GSI on Android 11 Stock firmware or use the DSU loader to install the Beta of Android 12...and the GSI situation is 50/50 if it will boot or not....what I do is flash the A10 stock final upload from the lionnet archive using the ever so awesome Moto flash tool...the tool does everything...and fixed your Beta partition so you can flash custom ROMs...once you finish with the tool reboot into STOCK recovery and format data..reboot to Stock Android 10 once you get to the Android setup welcome screen reboot to boot loader and flash TWRP recovery to both recovery slots...reboot to recovery...and format data...then reboot to fastbootd...your first custom install is recommended to be flashed from fastbootd on both slots...now when you finish reboot to Stock 10 recovery and format data...boot the rom first before and mods installed...then once you boot the rom you can flash mods with TWRP..get in a habit of after new system install format data in stock 10 recovery...now any custom ROM flash at this point forward do from TWRP and before flashing format data in TWRP after format again in stock 10 recovery...gapps install after first boot...Magisk install only after you fully go through the flashing procedure and setup the Rom make sure to enable dev options or it won't boot..and again flash Magisk after full setup and reboot..this procedure works...I keep a copy of stock recovery and TWRP recovery on my sdcard and platform tools on pc...you can flash stock 10 and TWRP in mobile if your rooted with any root kernel mgr so that way you don't have to use pc...the moto flash tool is the best way to setup the phone for custom ROMs.....

Categories

Resources