Database Users

[I9305][ALPHA]Clockworkmod Recovery Guide - I9305 ONLY!

EDIT: After more testing I am not happy with this version. I will put up a new version soon
Clockworkmod Recovery Image - I9305 Samsung Galaxy SIII 4G howto
What is it?
Clockwork mod recovery allows you to load custom OS images (like cyanogenmod and others) to your device
Things to note
This version is super-duper alpha, meaning that it is mostly untested and may not work!
I am not responsible for any damaged caused by using this recovery image.
It will increase your flash counter in odin
What do I need to do?
1. Download Odin (you might be able to use heimdall, however I have not tested this!)
*removed*
2. Download the image (1 part, tar file)
hotfile link;
https://hotfile.com/dl/174141057/71a063e/i9300_XXALI5_CWM.tar.html
3. Unzip Odin to an easy to access place (such as your desktop)
4. Copy the image file to the same directory.
5. Boot your SGS in to download mode
(power off... then press and hold the power + volume down + home buttons at the same time)
6. Connect your phone to your PC using the cable that came with it.
If you are using a laptop make sure you connect it to a port on the machine not the docking station (if you have one). If your machine has USB3 try to avoid using the USB3 ports.
7. Open the Odin application
Make sure your phone is detected, there will be a yellow square in the top left corner (see below screen dump)
8. Make sure it looks similar to the below screen (same options ticked, the .tar file in the 'PDA' section)
{
"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"
}
9. Press start and wait. Your phone will be flashed and reboot when it is finished.
10. When the phone re boots, power it off again.
11. Put the phone in recovery mode
hold down power, volume up and home when the device is turned off and unplugged

Well done Mick. Root and now cwm.
Sent from my GT-I9300 using xda premium

This is the only downfall of the 9305, lack of a large user base for development. Tip my cap to you guys.

So CWM runs and the file system table / mount points are all correct (just as a note they are COMPLETELY different to the non LTE SGS3) however it is unable to mount as a flash drive or apply update zips.
The way I got this far was taking the CWM recovery image for the I9300 and hacking it to boot on the I9305.
I will probably have to build cwm from source for it to work properly. stay tuned

Awesome!
This is awesome! The S3 GT-i9305 is going to be my first real Android phone (I currently have a $80 Samsung Galaxy Y now, but it sucks and doesn't count). I can't wait for it to be available, I'm probably going to travel to Singapore just to buy it (I currently live in Thailand, so it's quite close).
Let's hope the admins can create a separate S3 GT-i9305 forum soon, that would boost interest and development I think. I don't think development with the i9305 will be any less than with the US S3 editions, concidering that i9305 is the new international model that is going to be sold in most of Europe, Asia and Oceania.

You boot to recovery because you change the kernel but not the ramdisk.
You cant do anything cause the partition on I9305 is different from I9300.
You have to unpack ramdisk and add recovery.fstab from the I9305.
As i told yesterday to mick.wheelz i will try to do that job but i dont have the time.
Also i already send a test recovery.img to mick.wheelz to test it.

good work boys... I am missing all the fun by the time i get this thing in just over 1 week, all the fun bit will be over... haha oh well .. keep it up!!
---------- Post added at 07:38 PM ---------- Previous post was at 07:32 PM ----------
jinosong said:
This is the only downfall of the 9305, lack of a large user base for development. Tip my cap to you guys.
Click to expand...
Click to collapse
Give it some time its not even out in most countries

OK, made a new cwm image, its a hybrid of the build cwm ramdisk from the cwm builder, and the stock i9305 kernel... this was the only way I was able get the file systems to mount proplerly.
USB support is non-existent (because of the kernel) and I am still having trouble getting zip's to load.
I was able to make a system backup and I will soon test restoring it.

well it now can load zips, but i manged to hose my file system (oops...)
re flashing and trying something else.

I still can't get my own update zip's to load... so if someone would like to help me create a zip that would be nice.
I will upload my cwm recovery image too, it does *work* but its not 100%

I remember getting cwm touch working on the i9305 from one of the i9300 roots, although it may also have been the one that caused my IMEI data to die.

Guys please can anyone with i9305 rooted and already backup EFS image test that recovery.img?
Is made from original Cfroot from i9300 the kernel is from i9305 i only make changes to ramdisk image so 99% is ok but i whant to test the recovery function's if is all working.
Thank's

ausdim said:
Guys please can anyone with i9305 rooted and already backup EFS image test that recovery.img?
Is made from original Cfroot from i9300 the kernel is from i9305 i only make changes to ramdisk image so 99% is ok but i whant to test the recovery function's if is all working.
Thank's
Click to expand...
Click to collapse
that is what I did with mine... so you will have the same USB issue.
I will test the image tomorrow.

mick.wheelz said:
that is what I did with mine... so you will have the same USB issue.
I will test the image tomorrow.
Click to expand...
Click to collapse
I dont know cause i dont have the device.
But i compare your latest image and have many diff's.
Waiting for you to test and reply.
I wish to have a fully working CWM like i9300.
Thank's

I'd be happy to test but since my EFS is already dead I assume I wouldn't be of any help to anyone.

JJJohan1 said:
I'd be happy to test but since my EFS is already dead I assume I wouldn't be of any help to anyone.
Click to expand...
Click to collapse
If your efs is already died then you cant afraid anything.
Try to flash that untested recovey and reply.
http://forum.xda-developers.com/attachment.php?attachmentid=1360573&d=1348817728

Alright, might as well .
Update: No such luck I'm affraid. I've tried twice now - Open up Odin, select the file as PDA and 'Start' right? Got stuck in both attempts at the very start.

JJJohan1 said:
Alright, might as well .
Click to expand...
Click to collapse
Ok try it and if the flash go well then try to flash SuperSu CWMp and see if all is ok.
EDIT:Are you able to flash the stock recovery.img at all?
EDIT2:Uploaded default i9305 recovery.

ausdim said:
Ok try it and if the flash go well then try to flash SuperSu CWMp and see if all is ok.
EDIT:Are you able to flash the stock recovery.img at all?
EDIT2:Uploaded default i9305 recovery.
Click to expand...
Click to collapse
I wasn't able to flash the stock recovery image either, I guess my phone is FUBAR.

JJJohan1 said:
I wasn't able to flash the stock recovery image either, I guess my phone is FUBAR.
Click to expand...
Click to collapse
Hmm so you cant test it.
I suppose you already talk with Samsung service.
Thank's

5.0.2 - Experience and Discussion

Thought it would be good to have a thread dedicated to 5.0.2, instead of sifting through the 5.1.x Rolling Out and Stock OTA threads.
Got the prompt and updated this morning. Took about 10 minutes -- 3-4 minutes to install the updat and then a good 6-7 to go through app optimization (for 120+ apps).
Haven't had a chance to put it through its paces yet, but interested in what others experiences are. Improvement? Same old?
{
"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"
}

Screen flicker possibly gone? Was pretty bad before on mine, haven't had it since update now.

This will sound dumb probably: I am stock rooted with TWRP recovery. My N9 has a notification that update to 5.0.2 is available. As far as I know from reading guides and tutorials, I can't accept the OTA right? I have to manualy flash factory image? But how am I about to do that if the factory image for Wifi N9 5.0.2 isn't even available?
Thanks in advance.

b1bub4bu said:
This will sound dumb probably: I am stock rooted with TWRP recovery. My N9 has a notification that update to 5.0.2 is available. As far as I know from reading guides and tutorials, I can't accept the OTA right? I have to manualy flash factory image? But how am I about to do that if the factory image for Wifi N9 5.0.2 isn't even available?
Thanks in advance.
Click to expand...
Click to collapse
You basically have two choices:
1) Flash the stock 5.0.1 system.img (this will install stock recovery) and boot.img, then vendor. Img then take the OTA.
2) Wait until Google posts the factory image.

Actually, you will need to flash three things from the LXR22C 5.0.1 factory zip ...
system.img
vendor.img
boot.img
and if you have TWRP, then also recovery.img
once all these are stock, then you can take the OTA.
After the OTA, you can either reflash TWRP, or just simply fastboot boot it, then apply the latest SuperSU zip from chainfire's web site, and you'll be back to stock and rooted.

Can't say i've seen much of a difference
then again the update was only 23MB. What Google are thinking atm I'd love to know.

Ive tried the ota 3 times now and every time it 'errors' in recovery while flashing, I'm flabber gasted this is how Google now treats its nexus customers.

Ok I'm going to update my vendor
if any one wants it just tell me

Something else ... if you attempt the OTA once, you're done ... you can't re-attempt it unless you reflash back to original 5.0.1 stock.
It checks System first, and updates it ...
Then it checks Vendor, and updates it ...
Then it checks the boot image, and updates it.
So you you fail the vendor test, it's already updated System, and it won't run again.
You have to reflash system.img, vendor.img, AND boot.img before you can try again.
A much smarter method would have put the three verification steps one after the other, but obviously Google did not write the script that way.

Roxas598 said:
Can't say i've seen much of a difference
then again the update was only 23MB. What Google are thinking atm I'd love to know.
Click to expand...
Click to collapse
I think it's just some bug fixes. This is the only Nexus not moved to 5.1.1 by now, it's also the only Nexus using the K1 chipset. Not sure if the two are related, but it seems reasonable that they are running into some nVidia issues. 5.1.1 isn't out for the Shield tablet either.

ok guys updated to 5.0.2 just to get the vendor.img. it was hard lol
well here it is for every one that wants it
here is it
MD5sum dae0d789680948890d2bc84989bf3f79

_litz said:
Actually, you will need to flash three things from the LXR22C 5.0.1 factory zip ...
system.img
vendor.img
boot.img
.
Click to expand...
Click to collapse
I appreciate this. Coming from Nexus 6, vendor.img doesn't exist.
And on Nexus 6 when flashing the stock system.img it checks recovery and if not stock will automatically flash recovery.img. Is Nexus 9 the same?

When will my Nexus 9 LTE Model get this?

USBhost said:
ok guys updating to 5.0.2 just to get the vendor.img was hard lol
well here it is for every one that wants it
here is it
MD5sum dae0d789680948890d2bc84989bf3f79
Click to expand...
Click to collapse
Thanks for that! Have you tracked the vendor partition changes? What could it solve and what not...

stadicon said:
Thanks for that! Have you tracked the vendor partition changes? What could it solve and what not...
Click to expand...
Click to collapse
I was going to
But got lazy

The 5.0.2 image is out: https://dl.google.com/dl/android/aosp/volantis-lrx22l-factory-62276615.tgz.
Sorry, UsbHost... ?

stadicon said:
The 5.0.2 image is out: https://dl.google.com/dl/android/aosp/volantis-lrx22l-factory-62276615.tgz.
Sorry, UsbHost... ?
Click to expand...
Click to collapse
I know man I'm crying inside

Ok so I got my ota update and downloaded it. Now my Nexus 9 keeps trying to come on,then saying android updating apps, then shutting off and restarting , and then repeats the same thing ! I never rooted or flashed anything ! Its completely stock ! WTH ! Help !!!!!!!

Update showed up when I turned mine on, ended up bricking my device.
Would show the spinning balls and nothing else, tried wiping cache, factory reset and still ended up at the spinning balls. Google sent me a new one, but I really wish I could just return the stupid thing.
I'll never buy another "premium" Nexus tablet again, the only way I buy another is if they give us another Nexus 7 like device.

I'm doing a factory reset .It seems it still on android deleting screen for 10 min already. Is it frozen ??

Aospa rom 6.0.1

it's finally released for our z3c!!!
http://get.aospa.co/official/aries
I believe need to unlock bootloader first before flashing so take note.

AWESOME!!! Thanks for the information!

Same process then? flash boot.img and zip from TWRP?
Edit: Everytime I do that, my phone doesn't boot. Be it with CM or other ROMs, and I have to flash a stock tft. I'm currently on Concept, since I've never managed to get CM working.
Edit2: tried to install but had to modify the install-script. My device was being recognized as "z3c".
Edit3: error flashing, same thing as CM. Flashing stock MM to see if it has something to do with using Concept before.
Edit4: can't enter recovery after flashing stock MM. Going back to Concept and not sure what to do next
Edit5: that's the error I get in TWRP
{
"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"
}

juliopw said:
Same process then? flash boot.img and zip from TWRP?
Edit: Everytime I do that, my phone doesn't boot. Be it with CM or other ROMs, and I have to flash a stock tft. I'm currently on Concept, since I've never managed to get CM working.
Edit2: tried to install but had to modify the install-script. My device was being recognized as "z3c".
Edit3: error flashing, same thing as CM. Flashing stock MM to see if it has something to do with using Concept before.
Edit4: can't enter recovery after flashing stock MM. Going back to Concept and not sure what to do next
Edit5: that's the error I get in TWRP
Click to expand...
Click to collapse
I actually have no idea what to do. I'm on a locked bootloader and I have never unlocked and flashed a custom rom on my z3c.
Was just, sharing some info and hoping people would test

matthiastan5 said:
it's finally released for our z3c!!!
http://get.aospa.co/official/aries
I believe need to unlock bootloader first before flashing so take note.
Click to expand...
Click to collapse
Thanks for info.

For anyone who already running this rom, how is it? Does the baseband and camera work (no fisheye effect)?

Arch9 said:
For anyone who already running this rom, how is it? Does the baseband and camera work (no fisheye effect)?
Click to expand...
Click to collapse
Neither one nor the other. All other things seems working fine.

juliopw said:
Same process then? flash boot.img and zip from TWRP?
Edit: Everytime I do that, my phone doesn't boot. Be it with CM or other ROMs, and I have to flash a stock tft. I'm currently on Concept, since I've never managed to get CM working.
Edit2: tried to install but had to modify the install-script. My device was being recognized as "z3c".
Edit3: error flashing, same thing as CM. Flashing stock MM to see if it has something to do with using Concept before.
Edit4: can't enter recovery after flashing stock MM. Going back to Concept and not sure what to do next
Edit5: that's the error I get in TWRP
View attachment 3786599
Click to expand...
Click to collapse
I get the same error 7 when trying to install PA. Ive tried modefying the install-script as you did but then i get error 6.
I flashed stock D5803_23.5.A.0.575_R11D_Nordic Generic_1288-5411.ftf and then flashed recovery to TWRP via fastboot but i still get the same error 7 when trying PA after that.
My next attempt is to install that NUT dual recovery and try flash PA after that.

Camera and modem not working

Got it installed (finally...). You need a working TWRP recovery.
What's working:
- WiFi
- Paranoid OTA seems to work; no further build available to try (doubt that it will work without recovery though; see below)
Not working:
- RIL (so no phone or SMS)
- camera
BT and GPS not tested yet.
To be able to flash you need to
- modify updater-script located in META-INF/com/google/android/updater-script (which is actually a text file) of the ROM zip
- open it in a text editor
- replace "aries" with "z3c", save it somewhere (delete .txt if it's saved with this extension; filename must be "updater-script")
- open the zip with 7zip (recommended; dunno if it works with other archivers)
- replace the updater-script with your version in the zip
- place the zip onto your device
- enter recovery
- Factory Reset (no need for a full wipe)
- flash it
- flash MM Gapps directly afterwards (OpenGapps not recommended - use Slim Zero Gapps instead)
- if you want root, flash SuperSU BEFORE rebooting (see below)
Recovery will be lost and can't be installed with TWRP Manager or Rashr after flashing (Didn't work for me - please report if you got it working and if so - how. Maybe with fastboot, didn't try that yet)
Happy flashing...
I'm sure issues will be fixed quite fast in later builds as everything works already in latest Carbon ROM (find it on testing.myself5.de). Maybe @Myself5 can help with that...(?).

juliopw said:
Camera and modem not working
View attachment 3786769View attachment 3786770View attachment 3786771View attachment 3786772
Click to expand...
Click to collapse
I flashed and it's same with you.It's not okay for daily driver.Also it overheats a lot.

Nice, they said they already fixed the mobile radio bug internally and will be releasing a new build soon

radio is fixed and currently fixing camera

From PA's official Google+ post:
We are also announcing that with the help of Sony and their Open Devices Project we will be able to support all 22 Xperia devices on the SonyXperiaDev GitHub Instance. This initial Sony release is for the Shinano family, but the Rhine, Yukon and Kitakami platforms are expected to follow shortly. This is really exciting news for us and it allows us to give you the Android experience we all love on a much wider range of devices.
Click to expand...
Click to collapse
If this is the case, maybe the camera will actually be usable? What do you think guys?
P.S. We should contact a moderator to move this thread to General forums, this is not development.

where is the zip file ?

ultraaslan88 said:
where is the zip file ?
Click to expand...
Click to collapse
It's removed for the meantime
That's because it had so many bugs
Wait for some more days for a better build

Anyone have mirror for last version?

Can i flash this rom on my z3c with SliMM 1.9?

GabrielVacker said:
Can i flash this rom on my z3c with SliMM 1.9?
Click to expand...
Click to collapse
You need unlocked bootloader for this

dont Found file
Wysyłane z Compacta za pomocą Tapatalk 2

[TOOL][PIXEL XL] TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)

This is the Pixel's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"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"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
​

Amazing work! EVERY ONE OF US NEEDS TO LEARN command line, but it's always excellent to see amazing devs make an all in one like this for the guys that refuse to learn the hard (right) way, and for vets that aren't quite smart enough to make a tool like this themselves, like me, but appreciate the **** out of this little gem making my first custom Oreo ROM from stock rooted a breeze! Perhaps a little bold, but im still calling it, OG PIXEL XL NOT DEAD just when I was losing faith! Bravo!
PS:. Donation incoming once my current "being a broke ass" sit-e-ation ends here in a few weeks.

awareunlikeu said:
Amazing work! EVERY ONE OF US NEEDS TO LEARN command line, but it's always excellent to see amazing devs make an all in one like this for the guys that refuse to learn the hard (right) way, and for vets that aren't quite smart enough to make a tool like this themselves, like me, but appreciate the **** out of this little gem making my first custom Oreo ROM from stock rooted a breeze! Perhaps a little bold, but im still calling it, OG PIXEL XL NOT DEAD just when I was losing faith! Bravo!
Click to expand...
Click to collapse
Thanks, all need to learn command line, but this tool help a lot, the advanced options are really good too, see it when you have some time

mauronofrio said:
Thanks, all need to learn command line, but this tool help a lot, the advanced options are really good too, see it when you have some time
Click to expand...
Click to collapse
Just peeped them briefly,. Mad props!

Damn dude, this is amazing. Will definitely give it a shot in the next few days!
Question about the install/uninstall apks feature: how does this work? Is it batch or one at a time?
EDIT: Also, to flash TWRP, do I need to be in bootloader mode and do I need to disable security on my phone before flashing? Will I lose root when flashing it? I'm using the latest Magisk.
Sent from my Google Pixel XL using XDA Labs

Finally i got a solution for Nexus and Pixel Factory Image flash, now it works perfectly

Thank. I've been using the Unified Android Toolkit from Skipsoft for a while now, but a lot of functions are blocked. I'll give this a go.

tutusinghsohi said:
Thank. I've been using the Unified Android Toolkit from Skipsoft for a while now, but a lot of functions are blocked. I'll give this a go.
Click to expand...
Click to collapse
Thanks, remember to give me a feedback

I saw now that i forgot to unlock the flash factory image option for all 4 Pixel, i have released an update to solve that, tell me if it works

I'm running purenexus 7.1 ROM and would like to go to Oreo stock but retain root. Is this the right tool for me?

l2yangop said:
I'm running purenexus 7.1 ROM and would like to go to Oreo stock but retain root. Is this the right tool for me?
Click to expand...
Click to collapse
You can't retain root after flashing a factory image. You can root the oreo factory image after you have flashed it

I take it this is for windows only?

Thanks
Thanks for this toolkit
My phone was loop in no command screen . And you save me
I have questions about this toolkit
- can I use it to flash any custom rom or just original image
- can I root my phone with toolkit
- there is another virgin of toolkit can be use in a pixel book
Best wishes,

Ahmad Alsaeed said:
Thanks for this toolkit
My phone was loop in no command screen . And you save me
I have questions about this toolkit
- can I use it to flash any custom rom or just original image
- can I root my phone with toolkit
- there is another virgin of toolkit can be use in a pixel book
Best wishes,
Click to expand...
Click to collapse
You can't directly flash a custom rom with this tool, you need a TWRP already flashed on your phone and you can use "Recovery Zip Flasher" ( I do not recommend it ), i think is better to put the rom on your phone and flash it from your phone.
This tool can't root directly your phone, but gives all you need to root it (Bootloader Unlock and the flash of a TWRP).
Pixel book? This tool is only available for Windows, maybe you can use it on pixelbook with a virtual machine, but i don't know how pixel book works

With the new update a i make a new recovery flasher option for devices with project treble. Test it and told me if it works

Deleted

does this still work?

eightieskhild said:
does this still work?
Click to expand...
Click to collapse
Yes

This is a virus... how is this on XDA?
Trojan:Win32/Spursint.F!cl

revamper said:
This is a virus... how is this on XDA?
Trojan:Win32/Spursint.F!cl
Click to expand...
Click to collapse
This is not a virus, it's a false positive
https://www.virustotal.com/#/file/8...596c988acd17efa83f70e691c3d1ad7d2ff/detection
as usual, you need to breath your mouth without knowing what you're talking about

Boost E4 1766 Only Boots to TWRP

-Screwed up somewhere as my goal was to install LineageOS and try to use it on an At&t mvno.
-Package was unopened for months, so it still had the older firmware.
-Everything seemed okay after I unlocked the bootloader.
-Then I installed TWRP.
-Did a backup of everything using TWRP before I was going to try and root the device.
-I knew something was wrong when no verity opt encrypt and Magisk gave some error message and failed.
-Now whenever I boot the device, I get a N/A in the top left corner and then goes into TWRP.
-Restoring the backup using TWRP did nothing.
-I thought this would be the solution (dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=1M), but I get the bad key first and then N/A before going back to TWRP.
https://forum.xda-developers.com/moto-e4/help/moto-e4-metro-variant-rebooting-to-twrp-t3825841
What should I do now?
Any help would be appreciated. Even links to other posts that dealt with this issue is fine. Be aware that my skill level is only a little better than following Youtube videos.
Thank you.

N/A is normal. It will be there forever after you unlock bootloader. Did you format data in TWRP and type yes to format?

Thanks for the reply.
As far as I know, I did not format within TWRP. Is that my next step? If not, please advice what should be done next.
My concern is something is wrong because both the suggestions you gave in that other thread did not result in the phone booting to Android properly.

ah-le-le said:
Thanks for the reply.
As far as I know, I did not format within TWRP. Is that my next step? If not, please advice what should be done next.
My concern is something is wrong because both the suggestions you gave in that other thread did not result in the phone booting to Android properly.
Click to expand...
Click to collapse
once you flash TWRP you have to flash a no verity zip and probably magisk and definitely format data to remove encryption for your phone to boot.

Installing no verity zip and magisk produced the following. Did I do this properly because there looks like multiple errors?
{
"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"
}

ah-le-le said:
Installing no verity zip and magisk produced the following. Did I do this properly because there looks like multiple errors?
Click to expand...
Click to collapse
I can't read that, LoL. Maybe... Failed toount data? That's because you're still encrypted.
Put the zips on external storage. Format data, type yes.
Now reboot recovery (not system) then flash the zips.
And you can take screenshots in TWRP.

Thanks so much.
I followed your instructions plus the one from the other thread. Phone is now able to boot to the stock Android. I guess my next step is doing a little more research before trying to install LineageOS to see if the phone works well enough on a USA GSM mvno.

One more question please.
On the E4, are the system firmware updates mandatory? I read that users are first notified and then forced to take the update even if you Disable Automatic System Updates.
Is that true? I wish to stay with the old firmware because people have posted that the new firmware eliminates any chance of using a USA GSM sim on a Boost 1766.
Thanks.

ah-le-le said:
Thanks so much.
I followed your instructions plus the one from the other thread. Phone is now able to boot to the stock Android. I guess my next step is doing a little more research before trying to install LineageOS to see if the phone works well enough on a USA GSM mvno.
Click to expand...
Click to collapse
ah-le-le said:
One more question please.
On the E4, are the system firmware updates mandatory? I read that users are first notified and then forced to take the update even if you Disable Automatic System Updates.
Is that true? I wish to stay with the old firmware because people have posted that the new firmware eliminates any chance of using a USA GSM sim on a Boost 1766.
Thanks.
Click to expand...
Click to collapse
Use caution going with a custom ROM on this device, especially with a mvno. You may score far more hurt than benefit. Also consider what you are trying to accomplished going with custom ROMs given the clean stability of Moto stock ROMs. Toss in Xposed framework and a few modules like Gravitybox for full control/customization.
OTA updates can not be processed with a custom recovery (one of several prerequisites that your device no longer meets). You may get notified but the update won't install; you'll be dumped into TWRP. You can easily disable the update engine and corresponding notifications on a rooted device.