Hi,
sorry if i'm the 100th person to ask this question but how can i go back to the stock ROM with OTA?
I currently have a flavor of LinageOS with the Turbo Z kernel installed on my phone but it's just to buggy for me. I want to have root access on my phone for various reasons though.
I tried to just download different (6.0/7.0) stock ROM files but i can't install them with TWRP. I know that 7.1.x was released but i can not find the ROM for it.
What is the easiest way to just go back to a stock ROM? I know my way around the console but i don't want to brick my phone. I made backups of my files and also with TWRP so data loss is not an issue.
https://forum.xda-developers.com/moto-z/how-to/how-to-update-to-official-7-1-1-moto-z-t3640298
First things first.
On which bootloader are you, MM or are you on Nougat. If your device has been flashed with the 7(N) bootloader, you cannot flash the 6.0 stock, you will have to stay of 7.
Use the fastboot flash / erase commands, as in this thread:
https://forum.xda-developers.com/showpost.php?p=73119650&postcount=1
If at any stage your phone get bricked, ie, black screen after reboot, no charging, etc. Use these instructions. They saved me in the last week from returning my device for a replacement(and paying $350.00):
https://forum.xda-developers.com/showpost.php?p=71874880&postcount=1
lollyjay said:
https://forum.xda-developers.com/moto-z/how-to/how-to-update-to-official-7-1-1-moto-z-t3640298
Click to expand...
Click to collapse
Does this work for the EU version too? I'm not sure if the baseband thingy is compatible. I'll need a EU ROM otherwise but i can't find any for Android 7 :/
bert269 said:
On which bootloader are you, MM or are you on Nougat. If your device has been flashed with the 7(N) bootloader, you cannot flash the 6.0 stock, you will have to stay of 7.
Click to expand...
Click to collapse
I've already updated to Android 7 so i guess i've to use a stock Nougat ROM.
Read my last post on page 15 of this thread
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-root-moto-z-supersu-t3551113/page15
Where can I find the stock recovery for XT1650-03 RETEU without downloading an entire ROM zip file?
I have stock 7.0.0 with TWRP and Magisk 13.3.
I want to install the stock recovery so that I can install the 7.1.1 OTA which is available on my device, after which I will flash TWRP and root again. Will this work?
Byte_76 said:
Where can I find the stock recovery for XT1650-03 RETEU without downloading an entire ROM zip file?
I have stock 7.0.0 with TWRP and Magisk 13.3.
I want to install the stock recovery so that I can install the 7.1.1 OTA which is available on my device, after which I will flash TWRP and root again. Will this work?
Click to expand...
Click to collapse
If you didn't take a backup of your stock boot and recovery before, then i think you'll have to go the long way by flashing the whole rom.
If you manage to install the 7.1.1 OTA after that, boot once into TWRP, backup stock recovery & boot and save it on your sdcard/pc. Then you can start flashing TWRP permantly, root, etc
Someone correct me, if I'm wrong.
Byte_76 said:
Where can I find the stock recovery for XT1650-03 RETEU without downloading an entire ROM zip file?
I have stock 7.0.0 with TWRP and Magisk 13.3.
I want to install the stock recovery so that I can install the 7.1.1 OTA which is available on my device, after which I will flash TWRP and root again. Will this work?
Click to expand...
Click to collapse
What is your build number?
lollyjay said:
What is your build number?
Click to expand...
Click to collapse
The current build number is NPLS25.86-30-12
Byte_76 said:
The current build number is NPLS25.86-30-12
Click to expand...
Click to collapse
Here is my recovery.img for NPLS25.86-30-12
https://drive.google.com/file/d/0B3gcDbDvV4MkOHhPd0lBVE9IMzg/view?usp=drivesdk
It should work for reteu also if not you can just reflash twrp:cyclops:
lollyjay said:
Here is my recovery.img for NPLS25.86-30-12
https://drive.google.com/file/d/0B3gcDbDvV4MkOHhPd0lBVE9IMzg/view?usp=drivesdk
It should work for reteu also if not you can just reflash twrp:cyclops:
Click to expand...
Click to collapse
Thank you!
---------- Post added at 12:31 AM ---------- Previous post was at 12:15 AM ----------
lollyjay said:
Here is my recovery.img for NPLS25.86-30-12
https://drive.google.com/file/d/0B3gcDbDvV4MkOHhPd0lBVE9IMzg/view?usp=drivesdk
It should work for reteu also if not you can just reflash twrp:cyclops:
Click to expand...
Click to collapse
Your recovery works on my Moto Z.
I now have stock 7.0.0 rooted with Magisk 13.3, stock recovery and unlocked bootloader.
If I proceed with the 7.1.1 OTA, will it work?
Byte_76 said:
Thank you!
---------- Post added at 12:31 AM ---------- Previous post was at 12:15 AM ----------
Your recovery works on my Moto Z.
I now have stock 7.0.0 rooted with Magisk 13.3, stock recovery and unlocked bootloader.
If I proceed with the 7.1.1 OTA, will it work?
Click to expand...
Click to collapse
You must have fully stock. I would suggest that you uninstall Magisk
lollyjay said:
You must have fully stock. I would suggest that you uninstall Magisk
Click to expand...
Click to collapse
The reason that I installed Magisk is because after unlocking the bootloader with the stock rom, it would not boot anymore. Installing a custom kernel or Magisk solves that issue.
Byte_76 said:
The reason that I installed Magisk is because after unlocking the bootloader with the stock rom, it would not boot anymore. Installing a custom kernel or Magisk solves that issue.
Click to expand...
Click to collapse
I still would suggest that you uninstall Magisk because the OTA would not work.
lollyjay said:
I still would suggest that you uninstall Magisk because the OTA would not work.
Click to expand...
Click to collapse
Okay I uninstalled Magisk which initiated an immediate reboot and resulted in a bootloop just after the bootloader message.
I think the issue occurs because the Data partition gets encrypted when root is uninstalled and decrpyption fails because of a bad key due to the unlocked bootloader.
To recover, I used TWRP to wipe/format the Data partition and then flashed the no_verity zip file from the thread below which disables encryption. I then ran "fastboot continue" after which my phone booted back into Android:
https://forum.xda-developers.com/moto-z/help/bricked-moto-z-unlocking-bootlader-t3634701
My phone status was then: Stock Android 7.0.0, no_verity patch (no encryption), stock recovery, unlocked bootloader.
So my phone is about as close to stock as I can get it with unlocked bootloader.
I finally attempted to install the 7.1.1 OTA again. It reboots and indicates that it is installing and then pops up with a message that says "Error".
Pressing the power and up button brings up the recovery screen with the error log (with info that I don't understand) and from there I can reboot into system again where I get another message indicating that the update failed and no changes were made.
I'm hesitant to install RETBR or other non-RETEU roms (Because although they might work, there probably are some differences such as LTE bands etc. and they are not actually correct for my phone) so I'm not sure how else to get to 7.1.1 unless the wifi issue is resolved with the image that Erfanoabdi uploaded in another thread or Lenovo releases an official 7.1.1 firmware package for the RETEU model.
Byte_76 said:
.....
To recover, I used TWRP to wipe/format the Data partition and then flashed the no_verity zip file from the thread below which disables encryption.........
Click to expand...
Click to collapse
You still have a modified ROM as you flashed "no_verity patch"
The best for you would be to search for your version of ROM and FASTBOOT FLASH everything back.
Then see if the 7.1.1 OTA wants to stick.
bert269 said:
You still have a modified ROM as you flashed "no_verity patch"
The best for you would be to search for your version of ROM and FASTBOOT FLASH everything back.
Then see if the 7.1.1 OTA wants to stick.
Click to expand...
Click to collapse
So far I have been unable to find the official RETEU firmware from Adnroid 7.0.0 and I'm hesitant to flash the firmware for another region because it isn't technically correct for my phone and there are likely small differences that might become an issue at a later stage. (Maybe the LTE bands are different etc...)
Byte_76 said:
So far I have been unable to find the official RETEU firmware from Adnroid 7.0.0 and I'm hesitant to flash the firmware for another region because it isn't technically correct for my phone and there are likely small differences that might become an issue at a later stage. (Maybe the LTE bands are different etc...)
Click to expand...
Click to collapse
The LTE band on RETEU is 20 and stays 20 with RETBR. No change and everything works. No issues with LTE.
As I mentioned before, the RETBR version is the only working 7.0 backup for RETEU devices. After flashing RETBR , the softwarechannel changed automatically into RETEU. With this, i took the OTA 7.1.1.
Btw. the 7.1.1 OTA doesn't even change the boot loader Nr.( 0x9107). That means, if you mess up with 7.1.1 you can safely downgrade to 7.0 by flashing RETBR (and take a fresh 7.1.1 OTA again)
Did that twice without issues.(for security reason i always skip the two lines with "bootloader" and "gpt" at the top of the flash commands)
bullfinch110 said:
The LTE band on RETEU is 20 and stays 20 with RETBR. No change and everything works. No issues with LTE.
As I mentioned before, the RETBR version is the only working 7.0 backup for RETEU devices. After flashing RETBR , the softwarechannel changed automatically into RETEU. With this, i took the OTA 7.1.1.
Btw. the 7.1.1 OTA doesn't even change the boot loader Nr.( 0x9107). That means, if you mess up with 7.1.1 you can safely downgrade to 7.0 by flashing RETBR (and take a fresh 7.1.1 OTA again)
Did that twice without issues.(for security reason i always skip the two lines with "bootloader" and "gpt" at the top of the flash commands)
Click to expand...
Click to collapse
Thank you for the clarification. I will take your advice and flash the RETBR firmware.
---------- Post added at 08:40 PM ---------- Previous post was at 08:01 PM ----------
bullfinch110 said:
The LTE band on RETEU is 20 and stays 20 with RETBR. No change and everything works. No issues with LTE.
As I mentioned before, the RETBR version is the only working 7.0 backup for RETEU devices. After flashing RETBR , the softwarechannel changed automatically into RETEU. With this, i took the OTA 7.1.1.
Btw. the 7.1.1 OTA doesn't even change the boot loader Nr.( 0x9107). That means, if you mess up with 7.1.1 you can safely downgrade to 7.0 by flashing RETBR (and take a fresh 7.1.1 OTA again)
Did that twice without issues.(for security reason i always skip the two lines with "bootloader" and "gpt" at the top of the flash commands)
Click to expand...
Click to collapse
I cannot get RSDLite to detect my phone in fastboot mode so I guess I'm going to have to run the fastboot commands manually.
What do you mean about skipping the bootloader and gpt commands? If I skip those, I keep my stock "unlocked bootloader" and "gpt" but then the phone probably won't boot again because that is very much like what I have now except that I flashed the no_verity patch when my phone would not boot.
What exactly are you avoiding by skipping those two lines? Should I skip them too?
---------- Post added at 08:46 PM ---------- Previous post was at 08:40 PM ----------
Byte_76 said:
Thank you for the clarification. I will take your advice and flash the RETBR firmware.
---------- Post added at 08:40 PM ---------- Previous post was at 08:01 PM ----------
I cannot get RSDLite to detect my phone in fastboot mode so I guess I'm going to have to run the fastboot commands manually.
What do you mean about skipping the bootloader and gpt commands? If I skip those, I keep my stock "unlocked bootloader" and "gpt" but then the phone probably won't boot again because that is very much like what I have now except that I flashed the no_verity patch when my phone would not boot.
What exactly are you avoiding by skipping those two lines? Should I skip them too?
Click to expand...
Click to collapse
Are these the commands that I should run?
fastboot flash partition gpt.bin
fastboot flash motoboot boot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Byte_76 said:
Thank you for the clarification. I will take your advice and flash the RETBR firmware.
---------- Post added at 08:40 PM ---------- Previous post was at 08:01 PM ----------
I cannot get RSDLite to detect my phone in fastboot mode so I guess I'm going to have to run the fastboot commands manually.
What do you mean about skipping the bootloader and gpt commands? If I skip those, I keep my stock "unlocked bootloader" and "gpt" but then the phone probably won't boot again because that is very much like what I have now except that I flashed the no_verity patch when my phone would not boot.
What exactly are you avoiding by skipping those two lines? Should I skip them too?
Click to expand...
Click to collapse
It's out of my knowledge if your verity patch influences either bootloader or gpt partition. So i would recommend to flash those two commands in order to "repair" them. If you'll get an error message, skip them and proceed with the rest.
I always prefer RSD method instead of manually flashing by fastboot commands.
Have you installed the latest version of RSD-lite 6.2.4? Have you installed the latest moto drivers?
If you have extracted the RETBR. zip, search for "flashall.xml" file. Open it with a texteditor and you'll find the correct flashing commands.
Related
Intro: Below are the instructions for 3 steps to get Kitkat 4.4 (140.44.3.ghost_att) running on the AT&T moto x with locked bootloaders:
Install full 139.44.44.ghost_att (leaked) rom
Patch the rom to 140.44.3.ghost_att (ota to leak)
Patch the modem to the 140.44.3.ghost_att version
The updates came in stages, otherwise it would not have been my intention for this to be so long and messy. I soon hope to create a single rom and simplify the instructions. Testers can help with the WIP items below...
WARNING: I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE.
This rom is simply a flashable zip made from the ATT 4.4 leak which will install version 139.44.44. It is intended for the ATT moto x with locked bootloaders, however it should work with an unlocked bootloader if you fastboot flash the included boot.img. The flashable zip does not modify the bootloader or anything besides /system, but the full instructions will wipe out everything.
Prerequisite:
Att moto x with either the .51 (original) or .54 (1st OTA) stock rom
BACKUP ANYTHING YOU DON'T WANT TO LOSE. THESE INSTRUCTIONS WILL WIPE YOUR USERDATA AND SDCARD.
Instructions for ATT moto x with locked bootloader:
root with PwnMyMoto or RockMyMoto (for .51 or .54 respectively, thanks jcase)
install safestrap (thanks Hashcode and Team Win)
download rom to sdcard (motox-att-kitkat-leak-44.zip, link below)
download supersu flashable to sdcard (link below, thanks Chainfire)
enter safestrap recovery (TWRP) and activate the stock-slot
flash rom (motox-att-kitkat-leak-44.zip) to the stock-slot using TWRP recovery
immediately flash supersu using TWRP recovery
within TWRP reboot to bootloader
flash boot.img (included in ROM) to boot: fastboot flash boot boot.img
flash same boot.img to recovery: fastboot flash recovery boot.img
erase cache: fastboot erase cache
erase userdata: fastboot erase userdata (This wipes everything) This is not necessary. Thanks HeroSon.
powerup normally and enjoy
Update 11/17/2013: I made a patch to safely apply the ota that was received by people running the att 4.4 leak. This will bring the system build up to 140.44.3.ghost_att. The patch script DOES NOT modify anything except /system, and should be safe. The updated kernel (boot.img) is included in the zip. In case something goes wrong, backup your data to be on the safe side. Here are the Instructions:
Complete the installation of the att 4.4 leak (above instructions)
Reinstall safestrap This is not necessary. Thanks HeroSon.
Download the patch to sdcard (motox-140.44.3.ghost_att-ota-safepatch.zip, link below)
Reboot into safestrap recovery (TWRP)
Install the patch (motox-140.44.3.ghost_att-ota-safepatch.zip)
within TWRP reboot to bootloader
flash boot.img (included in the patch) to boot: fastboot flash boot boot.img
flash same boot.img to recovery: fastboot flash recovery boot.img
powerup normally
Update 11/18/2013: I attached a link to the modem patch that will update the 139.44.44 modem to a 140.44.3 modem. I really wanted to create a fastboot flashable NON-HLOS.bin image, but I haven't tested the procedure. Here are the instructions for the modem patch that I have tested:
Download the modem patch to the sdcard (motox-140.44.3.ghost_att-modem-patch.zip, link below)
Fastboot flash NON-HLOS.bin (included within the zip): fastboot flash modem NON-HLOS.bin
erase modemst1: fastboot erase modemst1 (I've done these erases a few times. They are prudent when you flash a modem.)
erase modemst2: fastboot erase modemst2
Reboot into safestrap recovery TWRP
Install the modem patch (motox-140.44.3.ghost_att-modem-patch.zip)
Powerup normally
Notes:
I am running the modem from the .54 ota, and it works with kitkat. I am not sure about the original .51 modem. The 140.44.3 modem is necessary after running patch to 144.44.3. This fixes the settings->security force close.
The safestrap "recovery or continue" screen still appears when you boot. If you erased userdata, reinstall safestrap to get all of the program back.
You should always be able to flash back to stock, as this procedure does not modify your bootloader.
There is a new version of safestrap. These instructions work with either v3.63 and v3.65. (Thanks HeroSon.)
I get a FC in settings->security on the 140.44.3 (patched) version. So far this is the only problem I have noticed. This force close is fixed by the modem patch.
WIP: I would like testers to help with the following:
What happens if you skip step 12 and don't erase useradata (this will keep [more of] safestrap intact)?
How do you remove safestrap manually?
Safestrap has been updated. Does the original 139.44.44 rom now run in a rom slot with 4.2.2 running in the stock-slot? What about the patches? I tried it - doesn't work.
Once 4.4 is installed in the stock-slot, can you backup the stock slot and restore to a rom-slot? (I'm guessing it works this way.) I guessed wrong. This doesn't work. Apparently safestrap needs a bit of tweaking to work with KK.
Is it possible for Safestrap TWRP to flash boot.img to the stock slot? (My experience is that it did not flash boot.img when using a rom-slot)
To clean up this mess, I am considering making a single rom that includes the base 4.4 version with the safepatch included. PM if you want to help by testing this all in one rom once I have it finished. There is a new rom of the official att 4.4.
I have an 100MB ext4 image of /modem. I would like guidance making a fastboot flashable non-HLOS.bin image. (Otherwise I wont be able to combine the leak and the patch.) I see instructions that might work if someone wants to try it and report their findings: http://forum.xda-developers.com/showthread.php?t=1588461 The official att 4.4 SBF includes NON-HLOS.bin
Part of the stock modem procedure is to flash "fsg.mbn", but I have not done that because I have been able to confirm that you can downgrade after flashing it. Can anyone confirm that this is safe on the moto x? (http://forum.xda-developers.com/showthread.php?t=2529569) This works.
139.44.44 rom download : http://www.androidfilehost.com/?fid=23212708291677349
rom patch to 140.44.3 download: http://www.androidfilehost.com/?fid=23212708291678076
modem patch to 140.44.3 download: http://www.androidfilehost.com/?fid=23212708291678561
supersu: http://forum.xda-developers.com/showthread.php?t=1538053 (download "CWM / TWRP / MobileODIN installable ZIP")
Original source files: http://rootzwiki.com/topic/107721-att-moto-x-44-leak/ (thanks designgears)
ooo yeah !! Nice job !!
Sa sens le Rooting icite !!
Wish mine was from AT&T, still have one year of warranty....cant see the time when kitkat comes global.
Is there any reason why I would have to wipe the SD card? It seems unnecessary. I may test this, but I'm a bit leery given that my Moto X is my daily driver...
Sent from my XT1058 using XDA Premium 4 mobile app
How do I do steps 9-12?
Does this include the recent ATT 4.4 OTA as well? Or is it just the system images from the original leak?
Sent from my XT1053
rubiksmoose said:
Is there any reason why I would have to wipe the SD card? It seems unnecessary. I may test this, but I'm a bit leery given that my Moto X is my daily driver...
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It might work without the wipe. Honestly, I tried this so many times that I quit once I had something that worked... I attributed most of my failures to a incompatibility between safestrap and the 4.4 boot process, but each of those attempts was done to a rom slot and not the stock slot.
Hopefully someone else can 'give it a whirl' and report their findings.
penpen72 said:
How do I do steps 9-12?
Click to expand...
Click to collapse
These steps are done using "FASTBOOT" from a PC while the phone is booted to the bootloader in fastboot mode.
phositadc said:
Does this include the recent ATT 4.4 OTA as well? Or is it just the system images from the original leak?
Click to expand...
Click to collapse
The rom was made from the original leak. I have been thinking about the OTA, but I am unclear how to approach this.
I am in AP Fastboot Flashmode on the phone what do I need to do now to do the steps? Sorry but I am coming from Samsung and HTC that have never been this hard.
---------- Post added at 02:52 PM ---------- Previous post was at 02:46 PM ----------
Also, my bootloader is locked. I figured I wouldn't have to do the extra steps since you say that it doesn't change those.
penpen72 said:
I am in AP Fastboot Flashmode on the phone what do I need to do now to do the steps? Sorry but I am coming from Samsung and HTC that have never been this hard.
---------- Post added at 02:52 PM ---------- Previous post was at 02:46 PM ----------
Also, my bootloader is locked. I figured I wouldn't have to do the extra steps since you say that it doesn't change those.
Click to expand...
Click to collapse
I assume you are on windows. First you need to download the FASTBOOT.exe program for our Motorola phones, and make sure the fastboot drivers install on your PC. (Maybe someone can help with this link.) Then you can issue the "fastboot ..." commands 9-12 I listed above from your PC with your phone plugged into the PC.
You certainly need to flash /boot, and you should also flash boot to recovery to allow RW access to /system. It might be possible to skip the "erase userdata" step, but that is unclear to me at this moment.
How is the leaked ROM working for you? Worth it? Any bugs or anything?
rubiksmoose said:
How is the leaked ROM working for you? Worth it? Any bugs or anything?
Click to expand...
Click to collapse
Everything is working fine. Take a look here for other people's observations:http://forum.xda-developers.com/showthread.php?t=2517577
There are only two odd things I have noticed. 1) the recent apps screen acts a bit strange when you swipe away apps 2) the transparent status bar becomes less transparent when you go for a drive and the "driving" notification is displayed. It is almost not worth mentioning, and a reboot fixes this issue.
It is hard to answer the "worth it" question. Ultimately, it is a still a smartphone with the same core capabilities, but I enjoy the challenge and the opportunity to learn something.
[edit]I am starting to think that there is additional battery drain vs the .54 ota version. "Wakelock detector" doesn't work, and settings->battery shows "Android System" at the top. This is a 'deal breaker' for me. I'll try and figure out how to apply the 4.4 ota without modifying the bootloader.[/edit]
question. Do you have to reboot the phone into recovery for system write-protect to be turned off the way you do currently, or is it off by default?
n1ckr0th said:
question. Do you have to reboot the phone into recovery for system write-protect to be turned off the way you do currently, or is it off by default?
Click to expand...
Click to collapse
When you enter SS recovery (step 4), safestrap will reboot itself if necessary to make sure you are in system rw mode.
Ctrl-Freak said:
When you enter SS recovery (step 4), safestrap will reboot itself if necessary to make sure you are in system rw mode.
Click to expand...
Click to collapse
I'm referring to post install. Currently you must be booted into recovery (normal os with write protect off) for changes to system to stick. is this still the norm with the 4.4 leak, or is WP off while booting normally?
n1ckr0th said:
I'm referring to post install. Currently you must be booted into recovery (normal os with write protect off) for changes to system to stick. is this still the norm with the 4.4 leak, or is WP off while booting normally?
Click to expand...
Click to collapse
Yes. After you have 4.4 working, you must still boot to recovery to enable RW mode on /system. Step 10 ensures you have the 4.4 boot.img in the recovery partition.
(The stock bootloader is still enforcing RO mode for a normal boot.)
I install this and skip step 12 and don't erase useradata. Everything working and all the data still there.
So can I clarify a few things for myself?
You made this by taking the leak files and packaging them into the zip, and it just works with safestrap now? Can you explain what you did to make the leak imgs Safestrap-bootable?
j2cool2012 said:
You made this by taking the leak files and packaging them into the zip,
Click to expand...
Click to collapse
I had to tweak and debug the script, but basically this is the only software part of what I did. To keep things simple, I left out the modem and simply included boot.img within the zip. The rom script does not flash boot.img.
Can you explain what you did to make the leak imgs Safestrap-bootable?
Click to expand...
Click to collapse
Nothing.
and it just works with safestrap now?
Click to expand...
Click to collapse
I'm glad you asked these question. First of all I failed to get 4.4 running in a rom-slot - you can read about my methods on this forum...
Finally, it came to me. Hashcode's Safestrap intercepts the boot process so nicely on the stock-slot that the SS:TWRP recovery program is [nearly] as effective as TWRP or CWM running from the recovery partition. Nice work Hashcode! So I made a regular rom that you can flash via safestrap TWRP. This rom only formats and flashes /system to keep things simple.
The only other thing I did was describe a set of instructions that worked for me.
Ctrl-Freak said:
I had to tweak and debug the script, but basically this is the only software part of what I did. To keep things simple, I left out the modem and simply included boot.img within the zip. The rom script does not flash boot.img.
Nothing.
I'm glad you asked these question. First of all I failed to get 4.4 running in a rom-slot - you can read about my methods on this forum...
Finally, it came to me. Hashcode's Safestrap intercepts the boot process so nicely on the stock-slot that the SS:TWRP recovery program is [nearly] as effective as TWRP or CWM running from the recovery partition. Nice work Hashcode! So I made a regular rom that you can flash via safestrap TWRP. This rom only formats and flashes /system to keep things simple.
The only other thing I did was describe a set of instructions that worked for me.
Click to expand...
Click to collapse
Thanks for taking the time to answer. I'm trying to figure out what has been done to see if I can try to do something similar for the VZW moto X using the T-Mobile leak.
j2cool2012 said:
Thanks for taking the time to answer. I'm trying to figure out what has been done to see if I can try to do something similar for the VZW moto X using the T-Mobile leak.
Click to expand...
Click to collapse
the Att bloatware and carrier name in notification bar scared me away
Intro: I hate to update my bootloader, so I created this rom and used this method to install the official AT&T kitkat and get root.
This rom is simply a flashable zip made from the official ATT KitKat 4.4 SBF which will install version 140.44.5. It is intended for the ATT moto x with locked bootloaders. The flashable zip does not modify the bootloader or anything besides /system, but the full instructions will wipe your userdata and sdcard.
WARNING: I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE.
Prerequisite:
Moto x with either the .51 (original), .54 (1st OTA) stock rom.
Have fastboot (motorola version for this phone) and PC drivers installed and working
BACKUP ANYTHING YOU DON'T WANT TO LOSE. THESE INSTRUCTIONS WILL WIPE YOUR USERDATA AND SDCARD.
Instructions for ATT moto x with locked bootloader:
root with PwnMyMoto or RockMyMoto (for .51 or .54 respectively, thanks jcase)
install safestrap (thanks Hashcode and Team Win)
download rom to sdcard (motox-kk-140.44.5.ghost_att-full.zip, link below)
download supersu flashable to sdcard (link below, thanks Chainfire)
extract boot.img, NON-HLOS.bin and fsg.mbn from the .zip to the fastboot directory of your PC
enter safestrap recovery (TWRP) and activate the stock-slot
flash rom (motox-kk-140.44.5.ghost_att-full.zip) to the stock-slot using TWRP recovery
immediately flash supersu using TWRP recovery
within TWRP reboot to bootloader
execute fastboot commands (below). Note: The "fastboot erase userdata" command will wipe you data and sdcard.
boot to recovery (which will boot up normally and allow the next step without rebooting)
reinstall safestrap
Fastboot commands:
Code:
fastboot flash boot boot.img
fastboot flash recovery boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
Notes:
You should always be able to flash back to stock, as this procedure does not modify your bootloader. (I still use the original bootloader from the original att .51 version.)
There is a new version of SuperSU, but I used version 1.65 (Let me know if the newest version still works.)
I wiped userdata. It may not be necessary, but my observation was that people had "soft reboots when uninstalling apps" and ultimately wiped anyway.
Safestrap works as before, and I have used it to backup and restore to the stock slot.
140.44.5 rom download : http://www.androidfilehost.com/?fid=23212708291682137
supersu: http://forum.xda-developers.com/showthread.php?t=1538053 (download "CWM / TWRP / MobileODIN installable ZIP")
Original source files: http://sbf.droid-developers.org/ghost/list.php (Thanks Skrilax_CZ, Pzyduck and the Firmware Team)
thanks ctrl-freak!
Thanks for posting this. If I have a Moto X with an unlocked bootloader, can I skip any of these steps?
I'm currently running rooted 4.2.2 with 139.12.54.ghost_att.ATT.en.us
RichAP said:
Thanks for posting this. If I have a Moto X with an unlocked bootloader, can I skip any of these steps?
I'm currently running rooted 4.2.2 with 139.12.54.ghost_att.ATT.en.us
Click to expand...
Click to collapse
Having not tried it, the following would be my guess:
I assume you have TWRP or CWM recovery installed in the recovery partition (not safestrap:TWRP). If so, then you can skip steps 1, 2, 11 and 12 and use your regular TWRP or CWM on step 6.
Ideally a rom would be created to do all the flashing in 1 step, but this rom is intended for safestrap's TWRP which is limited and/or some things have not been tested to my knowledge.
Reverting back to 4.2.2
never mind. Found the instructions
I am trying this now following your instructions and I'm going to NOT fastboot flash recovery boot.img or erase userdata and see what happens. (I have TWRP & unlocked bootloader)
I will report back if successful...so far I'm at "Android is upgrading..."
---------- Post added at 07:10 PM ---------- Previous post was at 07:07 PM ----------
I have no wifi or cell signal...guessing the modem is screwed up. Guess i will try flashing it again.
---------- Post added at 07:25 PM ---------- Previous post was at 07:10 PM ----------
Tried flashing the modem again but no go, no wifi, no cell radio, no bluetooth and camera doesn't work either.
Since the camera doesn't work I'm guessing its something else besides the modem?
RichAP said:
I am trying this now following your instructions and I'm going to NOT fastboot flash recovery boot.img or erase userdata and see what happens. (I have TWRP & unlocked bootloader)
I will report back if successful...so far I'm at "Android is upgrading..."
---------- Post added at 07:10 PM ---------- Previous post was at 07:07 PM ----------
I have no wifi or cell signal...guessing the modem is screwed up. Guess i will try flashing it again.
---------- Post added at 07:25 PM ---------- Previous post was at 07:10 PM ----------
Tried flashing the modem again but no go, no wifi, no cell radio, no bluetooth and camera doesn't work either.
Since the camera doesn't work I'm guessing its something else besides the modem?
Click to expand...
Click to collapse
You need to manually put your apns in under mobile networks and after that WiFi should turn on, had the same issue with the sbf file flash
Sent on my Moto X
It won't save an APN and I get see how that would stop WIFI from working. Bluetooth does work and Camera "fails to initialize".
I tried wiping everything out and starting from scratch but get the same results, even downloaded the main 4.4 zip file again (in case I had a bad download)
Do i need a windows machine to use RSD Lite or an i fastboot flash from the stock rbf?
It's my understanding that safestrap isn't working with 4.4, does it work through this method because this does not update the bootloader?
RichAP said:
I am trying this now following your instructions and I'm going to NOT fastboot flash recovery boot.img or erase userdata and see what happens. (I have TWRP & unlocked bootloader)
I will report back if successful...so far I'm at "Android is upgrading..."
---------- Post added at 07:10 PM ---------- Previous post was at 07:07 PM ----------
I have no wifi or cell signal...guessing the modem is screwed up. Guess i will try flashing it again.
---------- Post added at 07:25 PM ---------- Previous post was at 07:10 PM ----------
Tried flashing the modem again but no go, no wifi, no cell radio, no bluetooth and camera doesn't work either.
Since the camera doesn't work I'm guessing its something else besides the modem?
Click to expand...
Click to collapse
You will most likely need to do the kernel (boot.img). It wouldn't surprise me if it fixed the camera.
RichAP said:
It won't save an APN and I get see how that would stop WIFI from working. Bluetooth does work and Camera "fails to initialize".
I tried wiping everything out and starting from scratch but get the same results, even downloaded the main 4.4 zip file again (in case I had a bad download)
Do i need a windows machine to use RSD Lite or an i fastboot flash from the stock rbf?
Click to expand...
Click to collapse
This sounds eerily like the problem I was having. I tried several things, but neither data nor wifi worked, and when I went to settings->status the baseband reported "unavailable".
I made three changes to my procedure and the problem went away:
1) I used the older (known working) SuperSU version 1.65
2) I stopped running wipe (data, cache, dalvik) within safestrap:TWRP
3) I ran "erase userdata"
I am not sure which of these changes fixed the problem, but the procedure finally worked. Let us know if you figure it out.
Thanks, I've been flashing boot boot.img and even tried it from a different download.
---------- Post added at 10:04 PM ---------- Previous post was at 10:00 PM ----------
Ctrl-Freak said:
This sounds eerily like the problem I was having. I tried several things, but neither data nor wifi worked, and when I went to settings->status the baseband reported "unavailable".
I made three changes to my procedure and the problem went away:
1) I used the older (known working) SuperSU version 1.65
2) I stopped running wipe (data, cache, dalvik) within safestrap:TWRP
3) I ran "erase userdata"
I am not sure which of these changes fixed the problem, but the procedure finally worked. Let us know if you figure it out.
Click to expand...
Click to collapse
I do have the baseband version: Unknown
I will try the 3 things you did.
Thx.
Thanks for the help guys, after trying to work it out after a few hours I finally used RSDLite and was able to get ATT 4.4 functional.
Will try to root it in the morning.
Would anyone please make a torrent for the 4.4 firmware? My internet keeps disconnecting :crying:
TIA
Really good directions CTRL-Freak.
Brand new Moto X owner, as of this morning. After being a little confused on what SafeStrap was (at first) and finding the thread for PwnMyMoto (which is titled root/write protection bypass) I am now up and running with no issues. Activated my SIM just a few minutes ago with AT&T and I am happy!
SafeStrap - http://rootzwiki.com/topic/104161-recovery-locked-safestrap-recovery-v365-2013-11-13/
PwnMyMoto - http://forum.xda-developers.com/showthread.php?t=2444957
Is it possible to upgrade from you att .43 leak without a full wipe?
So I suppose if I am on the AT&T version and took the 4.4 OTA, then I am SOL? Would live to get root.
Sent from my XT1058 using Tapatalk
Cubfan99 said:
So I suppose if I am on the AT&T version and took the 4.4 OTA, then I am SOL? Would live to get root.
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
You can RSD back to 4.2
Sent from my N7 Razor
I'm currently using this fastboot-ghost_retbr-user-4.2.2-13.9.0Q2.X-116-LCX-35-36-release-keys-cid12-Brazil-BR.tar.gz I install this?
Infekxion said:
You can RSD back to 4.2
Click to expand...
Click to collapse
Are there instructions for that somewhere?
-- Sent from my Moto X on Tapatalk Pro
I want to rollback to B190 to B150. Tried with /dload (B150 update.app), no success. Mostly because, there is no root on B190 with Kingroot. I did not tried Magisk, yet. Have to flash TWRP with ADB. Not likely to me.
So, is there any chance for downgrade?
Phone came with B150, upgraded to B170, then B181 and to B190.
Device is SCL-L01C432.
If You need more information, please tell me.
3zero3 said:
I want to rollback to B190 to B150. Tried with /dload (B150 update.app), no success. Mostly because, there is no root on B190 with Kingroot. I did not tried Magisk, yet. Have to flash TWRP with ADB. Not likely to me.
So, is there any chance for downgrade?
Phone came with B150, upgraded to B170, then B181 and to B190.
Device is SCL-L01C432.
If You need more information, please tell me.
Click to expand...
Click to collapse
With the fastboot method if you have the bootloader unlocked, there are many tutorials on the net. But how did you rate an upgrade to the B170 ??
Androfish said:
With the fastboot method if you have the bootloader unlocked,
Click to expand...
Click to collapse
Unlock bootloader is the very first thing I did.
Androfish said:
there are many tutorials on the net.
Click to expand...
Click to collapse
But I am not really, really sure, which one will work with B190?
You mean flash custom recovery, custom ROM, then try to comeback to stock recovery and stock ROM?
Ok, looking now inside B190 update.zip and there is B190 recovery.img. (12.recovery.img in Huawei Update Extractor)
I see this with magisk:
https://forum.xda-developers.com/showpost.php?p=73838305&postcount=24
Should I try for B190?
Last version of KingRoot (5.3) is not working.
I found (on internet ) for some other Huawei phone, there is some special "middle package" (update.zip) to get the possibility for downgrade. Maybe I need that "special package"?
Androfish said:
But how did you rate an upgrade to the B170 ??
Click to expand...
Click to collapse
With Firmware Finder.
There is update (for me) numbered under #63737.
Update from:
SCL-L01C432B150CUSTC432D008
to:
SCL-L01C432B170CUSTC432D004
Put in /dload and update.
Have not used much B170, but B190 work smoothly.
You just have to download the b150 version and after extracting with Huawei extract the necessary files including the recovery stock, make the flash with fastboot:
fastboot system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cust cust .img
quick reboot
I followed Your instruction for fastboot.
Boot, recovery, system flashed. Cust cannot be flashed. They are from B150.
Code:
target reported max download size of 266338304 bytes
sending 'cust' (194411 KB)...
OKAY [ 6.275s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 6.283s
Tried to flash whole B150 (UPDATE.APP) with:
Settings -> Updater
EMUI Updater (Volume Up + Volume Down + Power)
Project Menu -> Update (it mean *#*#2846579#*#*)
Nothing work.
Now I have "half" B190 and "half" B150 in my phone.
Is there any way to flash whole B150 (UPDATE.APP)?
Please? Anybody?
Have weird problems, like i cannot remove widgets, launcher crash sometimes, etc...
I do not know is there any downgrade package? Or something?
Maybe I need SCL-L01C432B190CUSTC432D002 firmware? If exist?
Given that I still do not understand how you have run the B190 version on this device, try to install this version always with the fastboot method: http: //huawei-firmware.com/rom/huawei-y6/scl-l01/1027
After install any other updated B150 version and it should work.
The cust.img file I do not know why but it does not work with fastboot.
---------- Post added at 09:20 AM ---------- Previous post was at 09:14 AM ----------
Androfish said:
Given that I still do not understand how you have run the B190 version on this device, try to install this version always with the fastboot method: http: //huawei-firmware.com/rom/huawei-y6/scl-l01/1027
After install any other updated B150 version and it should work.
The cust.img file I do not know why but it does not work with fastboot.
Click to expand...
Click to collapse
Rom: http://huawei-firmware.com/rom/huawei-y6/scl-l01/1027
Code:
*** Disclamer * Your warranty is now void. * *
We are 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 us for messing
up your device, we will laugh at you.
DISCONTINUED, MOVED TO BUILDING CRDROID AND AICP ANDROID PIE
Known Issues
No audio through speaker, currently trying to find a fix.
ROM ResurrectionRemix-O-v6.2.1-20181202
TWRP DOWNLOAD
INSTALLATION
I am assuming that most of you already know how to flash custom ROMS.
Boot into TWRP Recovery Flash TWRP 3.2.3-0 image
Wipe the System, Cache and Data.
Flash ROM Zipfile
Flash the GApps (optional, needed for Google Playstore to work).
(Optional) Flash root zipfile Majisk/SuperSU.
Wipe ART/Dalvik cache.
Reboot
Flashing the ROM itself the boot time is around 5 mins, if you flash Gapps + Majisk or SuperSU expect the first boot time to increase to about 7-8 mins
XDA:DevDB Information
SM-T350 ResurrectionRemix Oreo, ROM for the Samsung Galaxy Tab A series
Contributors
nubianprince
Source Code: https://github.com/Nubianprince/gt58wifi_rr
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock Nougat
Version Information
Status: Beta
Beta Release Date: 2018-12-02
Created 2018-12-02
Last Updated 2019-03-23
Reserved
reserved
Did you guys just use the open source code of lineage 15.1 that didn't have working speaker. So is basically the same rom with different name. I'm still going to flash it for kicks but doesn't seem kinda pointless? Twrp should be better I'll let you know I'm assuming you forgot to mention gapps.
Funny cause the guy that built that took the source codes from someone else and that's why the speaker never got fixed because you don't know how to build or compile your just copying.
I got the rom up and running i was on marshmallow firmware and it worked fine. It takes awhile to boot up give it 10 minutes then when you start up it's really slow and lagging but after a couple reboots it works fine. I do say it's resremix tons of customization I haven't used any yet. I still think it's based off the lineage codes but it's different very different setup so it's worth installing if the damn speaker could get fixed it would be great. Bluetooth speaker or headphones work camera works I think the camera on this tablet is **** but works lol. Thanks for the rom guys. Twrp also seems to be working fine which is great because that's been a pain before.
Good job
Enviado desde mi SM-T320 mediante Tapatalk
So i am geting error 7. I have twrp 3.1.1-1_ashyx installed. I flash the new twrp recovery using install > install image > click the recovery file > click recovery partition and swipe to flash. then i follow all the other instructions and it still error 7 "this device is ." i found it odd that it doesnt list any name for the device. any help?
joejunior253 said:
So i am geting error 7. I have twrp 3.1.1-1_ashyx installed. I flash the new twrp recovery using install > install image > click the recovery file > click recovery partition and swipe to flash. then i follow all the other instructions and it still error 7 "this device is ." i found it odd that it doesnt list any name for the device. any help?
Click to expand...
Click to collapse
After you flashed the new twrp 3.2.3 did you reboot back into recovery? You can't just flash it then flash the rom you have to reboot in to recovery again to have it take effect. Also then follow all other instructions what instructions did you follow just a little more detail. Also what room or system were you on before?
I am coming from stock. When I flash from twrp and then click reboot recovery I get a boot loop. I've even tried doing the hold volume down + home + power and then moving to volume up, still doesn't work. I can't get twrp 3.1.0 to work, I always have to use 3.1.1. and I can't get the system to downgrade to marshmallow to test out anything else. It always fails with media failed to launch or something similar. I can only get the stock firmware ending in q1 and q5 to work (the latest ones running nougat). But I did notice on the twrp link that the nougat is for the t355 but appears to work on my t350.
joejunior253 said:
I am coming from stock. When I flash from twrp and then click reboot recovery I get a boot loop. I've even tried doing the hold volume down + home + power and then moving to volume up, still doesn't work. I can't get twrp 3.1.0 to work, I always have to use 3.1.1. and I can't get the system to downgrade to marshmallow to test out anything else. It always fails with media failed to launch or something similar. I can only get the stock firmware ending in q1 and q5 to work (the latest ones running nougat). But I did notice on the twrp link that the nougat is for the t355 but appears to work on my t350.
Click to expand...
Click to collapse
I'm not 100 percent what your saying. I believe your problems is with twrp you need to update twrp to version 3.2.3 which is on the first page of this thread. You need twrp 3.2.3 because the device tree is different for Oreo roms so much that you can't flash them with twrp 3.1.1. Downgrading system was not really the way to do it. I was just saying it worked from marshmallow not that you should be on marshmallow. When I downgraded from nougat firmware q1 and q5 bot to marshmallow I was able to downgrade but I got a drk error upon reboot. I just forced reboot and marshmallow stock worked but Downgrading is not usually good. Let's me also ask did you wipe efs partition with twrp 3.2.1 from the other thread at anytime? Try 3.2.3 either flash tar with Odin or extract img and flash in twrp recovery.
P.s. also yes twrp 355 3.1.1 does work on smt350 very well but still twrp3.2.3 should be the one to use.
If you wiped efs with twrp 3.2.1 and got an error you need to get back on to nougat firmware and then you into twrp terminal in advanced. Type in the first line hit enter then type in second command enter. You will no be able to boot marshmallow but you still might get drk error I got. It's because twrp 3.2.1 came from lte source codes and people think there the same there not the efs partition controls you Bluetooth and wifi on lte I'm sure it controls data. So it's not the same and it damages it and can't fix it because the partitions aren't setup right. I hope this helps. Guys take notes xda is for helping to not just getting root then leaving try to help out.
mke2fs /dev/block/mmcblk0p13
mount -w -t ext4 /dev/block/mmcblk0p13
joejunior253 said:
I am coming from stock. When I flash from twrp and then click reboot recovery I get a boot loop. I've even tried doing the hold volume down + home + power and then moving to volume up, still doesn't work. I can't get twrp 3.1.0 to work, I always have to use 3.1.1. and I can't get the system to downgrade to marshmallow to test out anything else. It always fails with media failed to launch or something similar. I can only get the stock firmware ending in q1 and q5 to work (the latest ones running nougat). But I did notice on the twrp link that the nougat is for the t355 but appears to work on my t350.
Click to expand...
Click to collapse
Device?
Firmware?
TWRP version?
Thanks tech guy. I will try this when I get home. I am back on stock firmware q5. I will just flash with Odin since I don't have twrp at all anymore. I will flash twrp 3.2.3. then I will try these commands. Fingers crossed it will work. Then I will boot into twrp if it works and flash the rom and gapps. I am not trying to root, just a better rom. I will post back soon
joejunior253 said:
Thanks tech guy. I will try this when I get home. I am back on stock firmware q5. I will just flash with Odin since I don't have twrp at all anymore. I will flash twrp 3.2.3. then I will try these commands. Fingers crossed it will work. Then I will boot into twrp if it works and flash the rom and gapps. I am not trying to root, just a better rom. I will post back soon
Click to expand...
Click to collapse
Ok you need root in twrp you'll need to see # on the command line that's super user sign and you can't reset you efs without out it but recovery might have root with flashing it but I don't think so. Main point flash magisk.
Techguy777 said:
I'm not 100 percent what your saying. I believe your problems is with twrp you need to update twrp to version 3.2.3 which is on the first page of this thread. You need twrp 3.2.3 because the device tree is different for Oreo roms so much that you can't flash them with twrp 3.1.1. Downgrading system was not really the way to do it. I was just saying it worked from marshmallow not that you should be on marshmallow. When I downgraded from nougat firmware q1 and q5 bot to marshmallow I was able to downgrade but I got a drk error upon reboot. I just forced reboot and marshmallow stock worked but Downgrading is not usually good. Let's me also ask did you wipe efs partition with twrp 3.2.1 from the other thread at anytime? Try 3.2.3 either flash tar with Odin or extract img and flash in twrp recovery.
P.s. also yes twrp 355 3.1.1 does work on smt350 very well but still twrp3.2.3 should be the one to use.
If you wiped efs with twrp 3.2.1 and got an error you need to get back on to nougat firmware and then you into twrp terminal in advanced. Type in the first line hit enter then type in second command enter. You will no be able to boot marshmallow but you still might get drk error I got. It's because twrp 3.2.1 came from lte source codes and people think there the same there not the efs partition controls you Bluetooth and wifi on lte I'm sure it controls data. So it's not the same and it damages it and can't fix it because the partitions aren't setup right. I hope this helps. Guys take notes xda is for helping to not just getting root then leaving try to help out.
mke2fs /dev/block/mmcblk0p13
mount -w -t ext4 /dev/block/mmcblk0p13
Click to expand...
Click to collapse
So...I am on stock nougat, nothing installed. I flash twrp 3.1.1, I go into twrp, click install, image, click recovery, root and install, then reboot and hold volume up and home, it says in yellow boot recovery, then goes to black screen. Then cannot power on, cannot boot into recovery, can only boot into download mode and reflash and try again.
---------- Post added at 06:40 PM ---------- Previous post was at 06:34 PM ----------
nubianprince said:
Device?
Firmware?
TWRP version?
Click to expand...
Click to collapse
SM-t350
Q5
TWRP 3.1.1
---------- Post added at 06:42 PM ---------- Previous post was at 06:40 PM ----------
Techguy777 said:
Ok you need root in twrp you'll need to see # on the command line that's super user sign and you can't reset you efs without out it but recovery might have root with flashing it but I don't think so. Main point flash magisk.
Click to expand...
Click to collapse
yes there is a # on my terminal when i open twrp 3.1.1.
i think the problem lies in rebooting after flashing the new recovery twrp, it just doesnt work. i am going to redownload and transfer to my sd card again and see if maybe the download was bad.
---------- Post added at 07:00 PM ---------- Previous post was at 06:42 PM ----------
Techguy777 said:
I'm not 100 percent what your saying. I believe your problems is with twrp you need to update twrp to version 3.2.3 which is on the first page of this thread. You need twrp 3.2.3 because the device tree is different for Oreo roms so much that you can't flash them with twrp 3.1.1. Downgrading system was not really the way to do it. I was just saying it worked from marshmallow not that you should be on marshmallow. When I downgraded from nougat firmware q1 and q5 bot to marshmallow I was able to downgrade but I got a drk error upon reboot. I just forced reboot and marshmallow stock worked but Downgrading is not usually good. Let's me also ask did you wipe efs partition with twrp 3.2.1 from the other thread at anytime? Try 3.2.3 either flash tar with Odin or extract img and flash in twrp recovery.
P.s. also yes twrp 355 3.1.1 does work on smt350 very well but still twrp3.2.3 should be the one to use.
If you wiped efs with twrp 3.2.1 and got an error you need to get back on to nougat firmware and then you into twrp terminal in advanced. Type in the first line hit enter then type in second command enter. You will no be able to boot marshmallow but you still might get drk error I got. It's because twrp 3.2.1 came from lte source codes and people think there the same there not the efs partition controls you Bluetooth and wifi on lte I'm sure it controls data. So it's not the same and it damages it and can't fix it because the partitions aren't setup right. I hope this helps. Guys take notes xda is for helping to not just getting root then leaving try to help out.
mke2fs /dev/block/mmcblk0p13
mount -w -t ext4 /dev/block/mmcblk0p13
Click to expand...
Click to collapse
Also in doing this wihtout having the twrp 3.2.3 and just trying from 3.1.1 results in mount: can't find /dev/block/mmcblk0p13 in /etc/fstab
I tried going into mount and clicking system too, still no dice. Really wanted to try this rom though, but all brick walls.
---------- Post added at 07:02 PM ---------- Previous post was at 07:00 PM ----------
Techguy777 said:
Ok you need root in twrp you'll need to see # on the command line that's super user sign and you can't reset you efs without out it but recovery might have root with flashing it but I don't think so. Main point flash magisk.
Click to expand...
Click to collapse
Soi you want me to flash magisk before I flash the new recovery, because i cant get the new recovery to work at all
And I think it is officially bricked now. I have tried to flash stock rom just to go back to having something that is working and I get the Error android and it gets to about 25 percent and resets to do the same thing. I have tried flashing twice, the official from sammobile, BSOD now.
joejunior253 said:
And I think it is officially bricked now. I have tried to flash stock rom just to go back to having something that is working and I get the Error android and it gets to about 25 percent and resets to do the same thing. I have tried flashing twice, the official from sammobile, BSOD now.
Click to expand...
Click to collapse
alright i think i am done being a whiney beezy. i was able ot do a ton of research, found that i might have had an esf failure or something. i flashed stock firmware, then reset odin without letting it reboot, flashed twrp, booted into it, rebooted the tablet and it works. i think i will wait for a from stock explanation on how to get this to work, i cannot get the recovery file to boot from twrp 3.1.1, it just black screens.
joejunior253 said:
alright i think i am done being a whiney beezy. i was able ot do a ton of research, found that i might have had an esf failure or something. i flashed stock firmware, then reset odin without letting it reboot, flashed twrp, booted into it, rebooted the tablet and it works. i think i will wait for a from stock explanation on how to get this to work, i cannot get the recovery file to boot from twrp 3.1.1, it just black screens.
Click to expand...
Click to collapse
Are you not English speaking? I said you had a efs error that's what I thought. You should have flashed the last version of nougat you had working when the error happened boot into stock and turned on USB debugging. Then you flash twrp either t355 3.1.1 or 3.2.3 are the best. I guess flash 3.1.1 for 355 at first then when you flash twrp on stock nougat boot into twrp and flash magisk 17.1 I'm having trouble with magisk 18 on some devices so use 17.1. Those terminal codes are tricky type them perfect or they don't work I recommend a couple times until it works. They should reset your efs partition then you reboot and flash your firmware again I'd say flash nougat again. Cause I flash marshmallow and got drk error. The firmware doesn't touch efs partition so once you screw it up your ass is grass unless you have a efs backup that works not the one from 3.2.1 twrp that screws everyone up. This is why people should not put stuff out until they have tested it. After you fix efs and can reboot then use twrp to flash twrp 3.2.3 by install image find the twrp 3.2.3 image select recovery. Flash because you can't flash Oreo with twrp 3.1.1. Then you can flash this rom.
You need root so you have to flash magisk in twrp after you flash twrp.
Try this code that will list partition blocks. Your efs should be 13. If it's not you don't have smt350 lol. Those codes work it Should say writing inode or something
ls -l /dev/block/bootdevice/by-name enter
mke2fs /dev/block/mmcblk0p13 enter
mount -w -t ext4 /dev/block/mmcblk0p13
Edit try SuperSU 2..82 sr5 beta or 2.79 sr3 because SuperSU is better for Samsung it's made to disable dm verity I think. Only up to nougat SuperSU will not work on Oreo you'll have to use magisk. The most important thing is after you flash the working stock firmware one of them will work I had this problem to only nougat q1 would work the rest didn't boot. So after I got my tablet running I flashed twrp 355 3.1.1 and went into terminal inside advance in twrp. I typed this commands and it worked it reset my efs partition my Bluetooth worked again my tablet would flash custom roms again and even downgrade back to marshmallow but I'm not recommending that. You type the first one hit enter type the second one hit enter then reboot. The firmware needs to be the same one you had when it errors if it's q5 then q5. I'm trying to help man I don't think your tablet is done I think it'll work again but it'll take some time and effort. You got this man . I always flash root first I don't think you have to because twrp already has root but I would say flash SuperSU first .
joejunior253 said:
So...I am on stock nougat, nothing installed. I flash twrp 3.1.1, I go into twrp, click install, image, click recovery, root and install, then reboot and hold volume up and home, it says in yellow boot recovery, then goes to black screen. Then cannot power on, cannot boot into recovery, can only boot into download mode and reflash and try again.
---------- Post added at 06:40 PM ---------- Previous post was at 06:34 PM ----------
SM-t350
Q5
TWRP 3.1.1
---------- Post added at 06:42 PM ---------- Previous post was at 06:40 PM ----------
yes there is a # on my terminal when i open twrp 3.1.1.
i think the problem lies in rebooting after flashing the new recovery twrp, it just doesnt work. i am going to redownload and transfer to my sd card again and see if maybe the download was bad.
---------- Post added at 07:00 PM ---------- Previous post was at 06:42 PM ----------
Also in doing this wihtout having the twrp 3.2.3 and just trying from 3.1.1 results in mount: can't find /dev/block/mmcblk0p13 in /etc/fstab
I tried going into mount and clicking system too, still no dice. Really wanted to try this rom though, but all brick walls.
---------- Post added at 07:02 PM ---------- Previous post was at 07:00 PM ----------
Soi you want me to flash magisk before I flash the new recovery, because i cant get the new recovery to work at all
Click to expand...
Click to collapse
Read everything i ve posted I said it was efs
Dude your all over the map man
1. Flash nougat firmware the last one you had boot up in the rom
2. Flash twrp 3.1.1
3. Flash SuperSU 2.7.9 or magisk 17.1 probably should go with SuperSU 2.82 SR5 beta.
4. Mack a back up
5. Reboot into rom
6. Reboot back into twrp and type that code it fixes your efs partition and resets it. Into terminal emulator inside twrp try it to it says writing inode or something like that. Both lines.
Reboot .
7. Go back into twrp flash image in install menu find twrp 3.2.3 I'm file make sure it's a image file.
Here's a section of my first post
Let's me also ask did you wipe efs partition with twrp 3.2.1 from the other thread at anytime? Try 3.2.3 either flash tar with Odin or extract img and flash in twrp recovery.
P.s. also yes twrp 355 3.1.1 does work on smt350 very well but still twrp3.2.3 should be the one to use.
If you wiped efs with twrp 3.2.1 and got an error you need to get back on to nougat firmware and then you into twrp terminal in advanced. Type in the first line hit enter then type in second command enter. You will no be able to boot marshmallow but you still might get drk error I got. It's because twrp 3.2.1 came from lte source codes and people think there the same there not the efs partition controls you Bluetooth and wifi on lte I'm sure it controls data. So it's not the same and it damages it and can't fix it because the partitions aren't setup right. I hope this helps. Guys take notes xda is for helping to not just getting root then leaving try to help out.
mke2fs /dev/block/mmcblk0p13
mount -w -t ext4 /dev/block/mmcblk0p13
If you can't boot into nougat go into twrp and type that code into the terminal emulator then when you get it to say writing idone or something it's working if you can't see the screen is black you have to search xda on tab a forms there's a fix a don't remember anyone please if you had twrp black screen what did you do? I've never had it.
---------- Post added at 02:36 PM ---------- Previous post was at 02:24 PM ----------
joejunior253 said:
So...I am on stock nougat, nothing installed. I flash twrp 3.1.1, I go into twrp, click install, image, click recovery, root and install, then reboot and hold volume up and home, it says in yellow boot recovery, then goes to black screen. Then cannot power on, cannot boot into recovery, can only boot into download mode and reflash and try again.
---------- Post added at 06:40 PM ---------- Previous post was at 06:34 PM ----------
SM-t350
Q5
TWRP 3.1.1
---------- Post added at 06:42 PM ---------- Previous post was at 06:40 PM ----------
yes there is a # on my terminal when i open twrp 3.1.1.
i think the problem lies in rebooting after flashing the new recovery twrp, it just doesnt work. i am going to redownload and transfer to my sd card again and see if maybe the download was bad.
---------- Post added at 07:00 PM ---------- Previous post was at 06:42 PM ----------
Also in doing this wihtout having the twrp 3.2.3 and just trying from 3.1.1 results in mount: can't find /dev/block/mmcblk0p13 in /etc/fstab
I tried going into mount and clicking system too, still no dice. Really wanted to try this rom though, but all brick walls.
---------- Post added at 07:02 PM ---------- Previous post was at 07:00 PM ----------
Soi you want me to flash magisk before I flash the new recovery, because i cant get the new recovery to work at all
Click to expand...
Click to collapse
No you can't flash magisk before twrp that makes no sense.
Please let me know what firmware update your trying to flash it Should be a the last one you had when you got the efs error and was able to boot into rom. That firmware only that one. No others will work I had this problem and fixed it. Also what twrp were you using when you got the efs error? Please answer it will help others to not touch it. I noticed that twrp 3.2.1 was taking down so I'm wondering did twrp 3.2.3 cause the error?
---------- Post added at 03:34 PM ---------- Previous post was at 02:36 PM ----------
Everyone did I not explain the fix right? I'm trying to learn how to help people on xda and if you guys think I didn't explain things right please let me know. I am fine with criticism so I can learn how to better help people.
liking it so far (been using for a day), i like the customization options for the UI. it took a bit in the setup thingy... it took a couple tries to get passed the "checking for update" spot. but it runs nicely now
Hi Bro., Can I flash this Rom on t355y ?
Hi all,
I made a huuuuuuge mistake : after a failing update of Magisk (don't know why, I already made zillion of updates), my phone is stuck in fastboot mode. And now is the big mistake : I performed a "fastboot lock" (don't ask why, stupid is stupid).
=> I can't boot in recovery because TWRP is not official
=> I can't unlock it as to unlock, I have to boot a full image and select "allow OEM unlock" in the system preferences
=> I can't even flash stock boot.img or system.img (I could find stock firmware), beacause I receive this error :
$ fastboot flash boot boot.img
Sending 'boot' (18472 KB) OKAY [ 0.551s]
Writing 'boot' FAILED (remote: 'device is locked. Cannot flash images')
fastboot: error: Command failed
Any idea on how to recovery my phone ? :crying:
gbetous said:
Hi all,
I made a huuuuuuge mistake : after a failing update of Magisk (don't know why, I already made zillion of updates), my phone is stuck in fastboot mode. And now is the big mistake : I performed a "fastboot lock" (don't ask why, stupid is stupid).
=> I can't boot in recovery because TWRP is not official
=> I can't unlock it as to unlock, I have to boot a full image and select "allow OEM unlock" in the system preferences
=> I can't even flash stock boot.img or system.img (I could find stock firmware), beacause I receive this error :
$ fastboot flash boot boot.img
Sending 'boot' (18472 KB) OKAY [ 0.551s]
Writing 'boot' FAILED (remote: 'device is locked. Cannot flash images')
fastboot: error: Command failed
Any idea on how to recovery my phone ? :crying:
Click to expand...
Click to collapse
You should be able to flash a stock kdz
Sent from my LG-H850 using XDA Labs
To others who have still the phone unlocked: just flash twrp to boot partition. Then boot, you will be in twrp. From there, copy the backup files in /data/ folder to the pc and flash them back with fastboot flash boot boot.img. Tha backups are gz compressed, so you need to extract them before flashing. At the end you will have back Magisk 20.1 and everything else working.
PS. Magisk 20.2 causes LG phones to be stuck in fastboot mode. This has been observed on LG V20, LG G5 and LG G6. So better wait before upgrading Magisk on our devices.
totalnoob34 said:
You should be able to flash a stock kdz
Sent from my LG-H850 using XDA Labs
Click to expand...
Click to collapse
Yes !
I used the official LG tool for recovery (see www.lg.com). The magic key is "vol UP + USB plug" and the phone switches in some specific recovery mode. Nothing particular to do, the tool is automatically downloading the latest offical firmware and flash it.
Thanks !!!
tremalnaik said:
PS. Magisk 20.2 causes LG phones to be stuck in fastboot mode. This has been observed on LG V20, LG G5 and LG G6. So better wait before upgrading Magisk on our devices.
Click to expand...
Click to collapse
Heck. I just upgraded but didn't reboot yet, can I install 20.1 via magisk manager and be safe?
Sent from my LG-H850 using XDA Labs
---------- Post added at 09:47 AM ---------- Previous post was at 09:40 AM ----------
tremalnaik said:
PS. Magisk 20.2 causes LG phones to be stuck in fastboot mode. This has been observed on LG V20, LG G5 and LG G6. So better wait before upgrading Magisk on our devices.
Click to expand...
Click to collapse
Heck. I just upgraded but didn't reboot yet, can I install 20.1 via magisk manager and be safe?
Sent from my LG-H850 using XDA Labs
I think that Magisk Manager already patched the boot image, I don't know whst will happen if you patch the 20.2 version with the 20.1. I would suggest you to check in /data/ folder for the boot image backup, copying them to pc if they are there, and then trying to reboot directly into recovery (Magisk Manager>Modules>Menu>Reboot to recovery) and from there flash back the old boot image. In case after reboot you get into fastboot, you can just flash the backup boot image with fastboot flash boot boot.img
tremalnaik said:
Magisk 20.2 causes LG phones to be stuck in fastboot mode. This has been observed on LG V20, LG G5 and LG G6. So better wait before upgrading Magisk on our devices.
Click to expand...
Click to collapse
My G5 (H830) didn't go into fastboot mode. Are you on stock ROM?
My H850 was stuck in fastboot mode after magisk update. I entered in TWRP and reinstall the kernel. Now, it is stuck on LG logo It seems that System is damaged too. Does someone know what magisk have changed in the System partition? Probably it can be fixed somehow...
For the future, my plan is to cut magisk internet access from the firewall settings, so it will be updated just never.
---------- Post added at 10:25 PM ---------- Previous post was at 10:09 PM ----------
tremalnaik said:
To others who have still the phone unlocked: just flash twrp to boot partition. Then boot, you will be in twrp. From there, copy the backup files in /data/ folder to the pc and flash them back with fastboot flash boot boot.img. Tha backups are gz compressed, so you need to extract them before flashing. At the end you will have back Magisk 20.1 and everything else working.
PS. Magisk 20.2 causes LG phones to be stuck in fastboot mode. This has been observed on LG V20, LG G5 and LG G6. So better wait before upgrading Magisk on our devices.
Click to expand...
Click to collapse
Can you please provide more details about what is backed up in /data and how it can restore the System? I looked in /data and /data/backups but I can't find something like a system backup...
SrZambie said:
My G5 (H830) didn't go into fastboot mode. Are you on stock ROM?
Click to expand...
Click to collapse
Yes, stock Oreo ROM with MK2000 kernel.
tinyspeck said:
My H850 was stuck in fastboot mode after magisk update. I entered in TWRP and reinstall the kernel. Now, it is stuck on LG logo It seems that System is damaged too. Does someone know what magisk have changed in the System partition? Probably it can be fixed somehow...
For the future, my plan is to cut magisk internet access from the firewall settings, so it will be updated just never.
---------- Post added at 10:25 PM ---------- Previous post was at 10:09 PM ----------
Can you please provide more details about what is backed up in /data and how it can restore the System? I looked in /data and /data/backups but I can't find something like a system backup...
Click to expand...
Click to collapse
System is by definition what Magisk shouldn't touch. Are you stuck on the static LG logo or the animated one?
In /data/ folder you should find at least one folder named "magisk" with others letters following. Inside of it you will find a compressed archive with the boot image inside. You can flash it back with both TWRP or fastboot.
tremalnaik said:
Yes, stock Oreo ROM with MK2000 kernel.
Click to expand...
Click to collapse
I looked around and found that this isn't LG specific. Someone with the Razor Phone 2 had their partitions wiped aswell. It sounds like it's having issues installing with certain ROMs which would explain why I wasn't affected. It's best to stay with 20.1 on stock ROMs for right now until it's fixed.
tremalnaik said:
Yes, stock Oreo ROM with MK2000 kernel.
System is by definition what Magisk shouldn't touch. Are you stuck on the static LG logo or the animated one?
In /data/ folder you should find at least one folder named "magisk" with others letters following. Inside of it you will find a compressed archive with the boot image inside. You can flash it back with both TWRP or fastboot.
Click to expand...
Click to collapse
It was stuck on static LG logo. I reflashed the same kernel which I installed last July (mk2000 v2.1). I also wiped cache and dalvik (kernel shouldn't need this but just in case...). It is strange that it stuck on static LG logo because later, I followed your advice and I installed the boot.img from /data/magisk_123... and the phone is back, working as new
So magisk is not so bad as it has a backup solution.
Thanks for your support
Static logo is loaded before system, so the problem wasn't the system partition. Probably my phone couldn't load boot partition at all, falling back to fastboot, while yours was loading boot partition but an error was occourring the meanwhile, leaving it at the logo. I'm glad that you solved the problem.
While reinstalling Magisk after the kernel, don't forget to check if the torch is still working: if it's not working, just flash once again the kernel and it should be ok.