THIS POST IS EXTENSION TO
https://forum.xda-developers.com/xperia-x/how-to/root-xperia-x-f5122-android-n-34-2-2-47-t3594502
Please read carefully and flash kernel for the LATEST UPDATE (Project SUZU )
34.3.A.0.244 - 7.1.1 - 09 NOV 2017 update
F5122 IS AT https://mega.nz/#F!DEQykYjL!Vux2m1_Rug9hg9B4_q0ifw
F5121 .. https://mega.nz/#F!CBhRyR7Z!L5uo_GWiCzXcNWQaZGJ9bQ (THANKs @eagleeyetom )
both f5121/5122 folders have 1 kernel image,
FLASH THE ROM
FLASH THE KERNEL,
FLASH TWRP,
BOOT IN TO TWRP .
FLASH MAGISK or SUPERSU, VIA FLASHABLE ZIP
BOOT THE DEVICE
IF YOU HAVE FLASHED MAGIK THEN INSTALL MAGIS MANAGER
MAGISK POST https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
CHAINFIRE SUPERSU ZIPs LATEST AT https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
-if you don't have th 34.3 fsc script , i have included in the folder (closing Partitions takes TIME, so be Patient ! )
-also i have inclused mixer_paths_wcd9335.xml, on 98% VOLUME level, IF you think sound output is LOW,,, just REPLACE it from /system/etc folder!
-
.
Click to expand...
Click to collapse
PREVIOUS KERNELS
for F5122_34.3.A.0.238 - 7.1.1 - 2 OCTOBER 2017 update
https://forum.xda-developers.com/xperia-x/development/rooted-kernels-f5121-f5122-34-3-0-238-t3683968
for F5122_34.3.A.0.224 - 7.1.1 - 8 SEPTEMBER 2017 update
https://forum.xda-developers.com/xp...ted-kernels-f5121-f5122-34-3-0-224-8-t3669793
for F5122_34.3.A.0.217 - 7.1.1 - 8Aug2017 update
https://forum.xda-developers.com/xperia-x/how-to/root-xperia-x-f5121-f5122-34-3-0-217-7-t3654368
for F5122_34.3.A.0.206 - 7.1.1 - july2017 update
https://forum.xda-developers.com/xperia-x/how-to/root-xperia-x-f512234-3-0-206-7-1-1-t3635595
Hi,
Thx for this new update but i dont found the kernel in the package.
I found the img.clean, twrp, fsc, sr5 and magisk but no kernel..
So what can i do for F5121!?
Siggi
siggi77 said:
Hi,
Thx for this new update but i dont found the kernel in the package.
I found the img.clean, twrp, fsc, sr5 and magisk but no kernel..
So what can i do for F5121!?
Siggi
Click to expand...
Click to collapse
on https://mega.nz/#F!CBhRyR7Z!L5uo_GWiCzXcNWQaZGJ9bQ
the F5121_34.3.A.0.244_su.img is the kernel
just flash and your device will wakup ROOTED.
twrp 3.1.1 problem
on my 64 GB xperia X F5122
1. after flashing ROM if
2. I flash twrp 3.1.1 it will
3. make my system partition 40GB and i get only 20gb workable
I tried many things but flashing recovery via adb always create this problem and if i BOOT the device before going in to the partition , sony stockrom makes internal storage encrypted which then twrp3.1.1 is unable to read
plz help
@serajr @shoey63 @munjeni
Hi,
Ok thx this package is complete...
Great
Siggi
---------- Post added at 09:37 PM ---------- Previous post was at 09:33 PM ----------
Hi,
OK this file is not a .img:
F5121_34.3.A.0.244_su is the kernel but isn´t a .img
Please make a new package
Siggi
---------- Post added at 10:22 PM ---------- Previous post was at 09:37 PM ----------
In the package for F5122 is the corret .img, but for F5121 not or is the same?
siggi77 said:
Hi,
Ok thx this package is complete...
Great
Siggi
---------- Post added at 09:37 PM ---------- Previous post was at 09:33 PM ----------
Hi,
OK this file is not a .img:
F5121_34.3.A.0.244_su is the kernel but isn´t a .img
Please make a new package
Siggi
---------- Post added at 10:22 PM ---------- Previous post was at 09:37 PM ----------
In the package for F5122 is the corret .img, but for F5121 not or is the same?
Click to expand...
Click to collapse
i am sorry,
i have fixed it
please check again
thank you
Hi, great
thx for the new package
Siggi
clean kernel image is drm fixed??
kloroform said:
clean kernel image is drm fixed??
Click to expand...
Click to collapse
yes sir, it is,
That is little bit complicated we need a good guide
---------- Post added at 02:56 PM ---------- Previous post was at 02:31 PM ----------
I flashed rom>kernel with su then flashed twrp.
Later I flashed the magisk.zip and reboot the system but everytime its entering the twrp screen.
Wont going bootanimation and starts the phone. Just twrp screen.
OH GOD I SOLVED THIS. HERE MY SOLUTION:
First things first, I WANT TO FLASH MAGISK AND NO MORE USE SUPERSU, THATS I WANT. IF YOU WANT TO USE MAGISK HERE IS MY SOLUTION.
1. Flash the stock rom on the post. (up)
2. When flash finished, boot the phone and close the phone.
3. Flash the clean kernel with flashtool.
4. Boot the phone, is everything okay, close again.
5.a So there is little bit strange, open adb on windows (yes really. dont use flashtool this time)
5.b Flash the twrp-3.1.1-suzu-2017.07.16.img from this address: https://androidfilehost.com/?w=files&flid=197369 (on the middle)
5.c the command is here "fastboot flash recovery twrp-blablabla.img"
6. and type "fastboot reboot" will boot up your phone.
7. If its really open, -not stuck at the sony logo or everytime goin in twrp- you did! congrats!
I hope it help you
xxarigattoxx said:
That is little bit complicated we need a good guide
---------- Post added at 02:56 PM ---------- Previous post was at 02:31 PM ----------
I flashed rom>kernel with su then flashed twrp.
Later I flashed the magisk.zip and reboot the system but everytime its entering the twrp screen.
Wont going bootanimation and starts the phone. Just twrp screen.
OH GOD I SOLVED THIS. HERE MY SOLUTION:
First things first, I WANT TO FLASH MAGISK AND NO MORE USE SUPERSU, THATS I WANT. IF YOU WANT TO USE MAGISK HERE IS MY SOLUTION.
1. Flash the stock rom on the post. (up)
2. When flash finished, boot the phone and close the phone.
3. Flash the clean kernel with flashtool.
4. Boot the phone, is everything okay, close again.
5.a So there is little bit strange, open adb on windows (yes really. dont use flashtool this time)
5.b Flash the twrp-3.1.1-suzu-2017.07.16.img from this address: https://androidfilehost.com/?w=files&flid=197369 (on the middle)
5.c the command is here "fastboot flash recovery twrp-blablabla.img"
6. and type "fastboot reboot" will boot up your phone.
7. If its really open, -not stuck at the sony logo or everytime goin in twrp- you did! congrats!
I hope it help you
Click to expand...
Click to collapse
the guide is here
https://forum.xda-developers.com/xperia-x/how-to/root-xperia-x-f5122-android-n-34-2-2-47-t3594502
also twrp3.1.1 works best at 32gb variant by giving 20gb workable and putting systemparittion to 12gb
however it does the SAME with 46gb variant and give only 20gb workable and put system partition 40 gb
thats why for 64gb variants i don't recomend using twrp3.1.1
Hi, when you say flash the rom you mean in Flashtool ? There is no twrp flashable rom here ?
Jomoteck said:
Hi, when you say flash the rom you mean in Flashtool ? There is no twrp flashable rom here ?
Click to expand...
Click to collapse
once you flash the modified kernel with supersu then there is no need for twrp, simply boot your device and it will wakeup rooted.
however if you wana use magisk and your device is 64gb then i highly recommend you to do this
1. flash rom
2. flash the modified kernel
3. boot the device and go thru sony setup , give google account and let it sync
4. switch off mobile after 15 or so mins
5. flash twrp3.1.1 suzu (given in the mega link, in the OT)
6. HOLD power and VOLUME DOWN BUTTON till PINK led comes on sonylogo and you are taken to twrp, keep system readonly and flash magisk ( via otg or if you had it in your sd card prior) ( at this point you may flash other zips also, if there are any)
7. twrp may give you error such as... cannot mount internal storage etc, just ignore.
8. after flashing, switchoff mobile, and boot it into system.
9. for safty purposes, you can erase twrp by connecting device in fastboot mode and executing following command
Code:
fastboot erase recovery
now you can ask me why i let you boot your device first. normally its unprecedented.
the reason i explain here
https://forum.xda-developers.com/showpost.php?p=74573987&postcount=121
hello
i have 34.3.A.0.217 rom with root. how can i update 34.3.A.0.244 ? can you help me anyone ?
nova001 said:
hello
i have 34.3.A.0.217 rom with root. how can i update 34.3.A.0.244 ? can you help me anyone ?
Click to expand...
Click to collapse
1. download 34.3.A.0.244 using xperifirm under flashtool
2. flash it using flashtool (please google the tutorial ) (wipe everything while flashing
**** TAKE BACKUP of EVERYTHING (DATA) ****
YasuHamed said:
1. download 34.3.A.0.244 using xperifirm under flashtool
2. flash it using flashtool (please google the tutorial ) (wipe everything while flashing
**** TAKE BACKUP of EVERYTHING (DATA) ****
Click to expand...
Click to collapse
thats oke, but we cant dowload anywhere? only xperifirm ?
nova001 said:
thats oke, but we cant dowload anywhere? only xperifirm ?
Click to expand...
Click to collapse
Xperifirm is the best
Other servers i cant guarantee
I was able to flash rom, flash kernel, flash root and boot the phone and was able to use it.
PROBLEM:
- It heats up during use.(FIXED) constant mobile data was the cause..
- Everytime I lock the screen my mobile data turns on when I unlock the SCREEN. (FIXED) disable find my device as administrator.
HI question does FCS_thermal_Xperia_X_v1.3.zip work for Nougat?
cyanides13 said:
HI question does FCS_thermal_Xperia_X_v1.3.zip work for Nougat?
Click to expand...
Click to collapse
Yes it works I use it actually.
Related
Made a couple of scripts for people who are having problems moving between the beta and any CM13 compatible rom (and vice versa).
Firstly, they are both zip files but NOT FLASHABLE FILES.
Just unpack either one, go into the folder and run the rescue.bat file as admin (right click and choose "run as administrator") while you have your OP2 in fastboot mode (Windows only, anyone wanting to convert them, feel free )
All it does is flashes all the partitions from the OOS3 beta one by one and then flashes the compatible TWRP version at the end or flashes the CM13 compatible partitions and the latest TWRP (3.0.1.0 for now) at the end.
**MAKE SURE YOU HAVE COPIED THE BETA ZIP FILE ON TO YOUR PHONE FIRST OR A CM13 COMPATIBLE ROM (WITH GAPPS PACKAGE) **
Hold down your volume down key once the script is done and it'll reboot into the compatible recovery, once you wipe your system, data and cache partitions in there and flash the rom you should be good to go. Just make sure when you restart from TWRP you choose to disable the "stock recovery replacement"
To go from any rom to the OOS 3 Beta use this pack:
https://www.androidfilehost.com/?fid=24459283995310520
To go from the OOS 3 Beta to CM13 compatible use this pack (Updated with TWRP 3.0.1.0) :
https://www.androidfilehost.com/?fid=24459283995311240
Any problems after using either one post below but please DON'T FORGET TO HAVE YOUR NEW ROM READY TO GO ON THE STORAGE FOR AFTER THE SCRIPT.
djsubterrain said:
Made a couple of scripts for people who are having problems moving between the beta and any CM13 compatible rom (and vice versa).
Firstly, they are both zip files but NOT A FLASHABLE FILES.
Just unpack either one, go into the folder and run the rescue.bat file as admin (right click and choose "run as administrator") while you have your OP2 in fastboot mode (Windows only, anyone wanting to convert them, feel free )
All it does is flashes all the partitions from the OOS3 beta one by one and then flashes the compatible TWRP version at the end or flashes the CM13 compatible partitions and the latest TWRP (3.0.0.2 for now) at the end.
**MAKE SURE YOU HAVE COPIED THE BETA ZIP FILE ON TO YOUR PHONE FIRST OR A CM13 COMPATIBLE ROM (WITH GAPPS PACKAGE) **
Hold down your volume down key once the script is done and it'll reboot into the compatible recovery, once you wipe your system, data and cache partitions in there and flash the rom you should be good to go. Just make sure when you restart from TWRP you choose to disable the "stock recovery replacement"
To go from any rom to the OOS 3 Beta use this pack:
https://www.androidfilehost.com/?fid=24459283995310520
To go from the OOS 3 Beta to CM13 compatible use this pack:
https://www.androidfilehost.com/?fid=24459283995310560
Any problems after using either one post below but please DON'T FORGET TO HAVE YOUR NEW ROM READY TO GO ON THE STORAGE FOR AFTER THE SCRIPT.
Click to expand...
Click to collapse
Tried it but didn't work. The recovery remains the same een after adb shows its flashed in fastboot mode... maybe I should try unlocking the OEM again as I just flashed 3.0 beta and think it might have locked OEM
indroider said:
Tried it but didn't work. The recovery remains the same een after adb shows its flashed in fastboot mode... maybe I should try unlocking the OEM again as I just flashed 3.0 beta and think it might have locked OEM
Click to expand...
Click to collapse
Which way were you trying to go? From CM13 to 3.0 Beta or the other way round? Also did you run your command window or the script with administrator privileges?
Just updated the CM13 Rescue script to include the newly released TWRP 3.0.1.0:
https://www.androidfilehost.com/?fid=24459283995311240
indroider said:
Windows only, anyone wanting to convert them, feel free
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=66166823&postcount=7
gonna bookmark this x)
Go to OxygenOS 3.0 -> https://mega.nz/#!0xxWEAzR!jv4I-FzULD7l0tNWPsIq3Im6w91YZ1hVVuFmv6h55TA
Go back to CM13 -> https://mega.nz/#!R5oFBb6D!tzSYYafx8Uqm-ToJrU3YlHOZQ93_EQyjH5ibM_50Yxk
Disclaimer:
By using this script YOU will take full responsibility for any damage to your device!
Hardware or software! no one forcing you to use it.
So please do not blame me if you read wrong! or didn't read at all the instructions that i have written for YOU.
Will update after work with new TWRP 3.0.2.0...
Here you got I have updated the recovery in the cm13 resuce for you. Its all your work... Thank you.. Here is the link
https://mega.nz/#!LARRCTiZ
---------- Post added at 08:11 PM ---------- Previous post was at 08:03 PM ----------
First thanks for the scripts!
I tried today to get back go from OOS3 to CM13 but I now have a Chinese TWRP. Can anybody tell me how to change that back to English?! My Chinese is not really existing
Found the menue entry by testing. In case anybody else gets that problem:
- in the main menu click the 3rd button on the right
- on the top menu click the globe icon
- now you can change the language
guys , can someone share the steps for going back to CM13 to OSS 3.0
---------- Post added at 05:05 PM ---------- Previous post was at 05:05 PM ----------
I tried the process but not working for Switching from OSS 3.0 to CM13.
Please help
---------- Post added at 05:07 PM ---------- Previous post was at 05:05 PM ----------
indroider said:
Here you got I have updated the recovery in the cm13 resuce for you. Its all your work... Thank you.. Here is the link
https://mega.nz/#!LARRCTiZ
Click to expand...
Click to collapse
Hey.. Can you please share the key for decryption ?
hcbhatt said:
guys , can someone share the steps for going back to CM13 to OSS 3.0
---------- Post added at 05:05 PM ---------- Previous post was at 05:05 PM ----------
I tried the process but not working for Switching from OSS 3.0 to CM13.
Please help
---------- Post added at 05:07 PM ---------- Previous post was at 05:05 PM ----------
Hey.. Can you please share the key for decryption ?
Click to expand...
Click to collapse
Try this link
https://mega.nz/#!LARRCTiZ!rfjvwOIYO1v_FhKQ-CA0yDZcm33Lg5lUM_4TtWUwBgU
also u just need to extract the zip and reboot your phone into fastboot mode and the connect the mobile and open the folder where you extracted and run rescure.bat [ please do not run as admin ]
It will flash the partitions for the CM based roms and you can then reboot in recovery when the command prompt ask you to hold the down arrow key and press any key and now the trwp 3.0.2 will open and just wipe the data, system and cache and dalvik and then flash the cm and gapps you will be good to go after the reboot
Does anyone know why OP2 roms are based off two different firmwares?
indroider said:
Try this link
https://mega.nz/#!LARRCTiZ!rfjvwOIYO1v_FhKQ-CA0yDZcm33Lg5lUM_4TtWUwBgU
also u just need to extract the zip and reboot your phone into fastboot mode and the connect the mobile and open the folder where you extracted and run rescure.bat [ please do not run as admin ]
It will flash the partitions for the CM based roms and you can then reboot in recovery when the command prompt ask you to hold the down arrow key and press any key and now the trwp 3.0.2 will open and just wipe the data, system and cache and dalvik and then flash the cm and gapps you will be good to go after the reboot
Click to expand...
Click to collapse
Thanks indroider
Sent from my ONE A2003 using XDA-Developers mobile app
[/COLOR]
knpk13 said:
Does anyone know why OP2 roms are based off two different firmwares?
Click to expand...
Click to collapse
he roms are not based on different firmware the main diff with MM stock n other roms is the partion table and this is a general scenario for many mobiles
---------- Post added at 11:32 PM ---------- Previous post was at 11:26 PM ----------
hcbhatt said:
Thanks indroider
Sent from my ONE A2003 using XDA-Developers mobile app
Click to expand...
Click to collapse
Your most welcome. Is your issue resolved? Hit thanks if you wish ..
Hello, guys.
Primarily, I'm really sorry for my English - I don't speak very well.
I'm having a serious problem on my MOTO E 2015 LTE.
It have CM 14 installed and I was installing some apps from Google Play and suddently the device stopped working and restarted.
Now the device don't even charge (only on fastboot) - I can't install TWRP ... I've tried but every time when I finish it back to the screen of bootloader unlocked.
I think bootloader is corruped but I can't change it.
I try to install the stock ROM, CM 13 and other the version 5.1 and 6.0 of Android.
I also tried use RSD, mfastboot, fastboot, manual installation code by code to install but dosen't work.
The biggest problem is that I can't install any recovery because alawys come back to bootLOOP infinite.
Sombody can help me?
Thank you very much.
hi bro,
1, the first thing u have to do is put command " fastboot wipe system "
2. after that download cm 13 from its official website and download gapps from gapps.org
3.while its downloading get your recovery from here http://forum.xda-developers.com/moto-e-2015/orig-development/twrp-moto-e-2015-recovery-t3049726 flash using adb and minimal drivers command is " fastboot flash recovery recovery.img make sure ur downloaded recovery is in adb drvicers folder.
4.after that boot into recovery copy both the files ( rom and gapps)
5.flash them
6.first flash rom and then gaaps
7.done i hope it works .
P.S any query ask me
Hey, bro
Master ST said:
hi bro,
1, the first thing u have to do is put command " fastboot wipe system "
2. after that download cm 13 from its official website and download gapps from gapps.org
3.while its downloading get your recovery from here http://forum.xda-developers.com/moto-e-2015/orig-development/twrp-moto-e-2015-recovery-t3049726 flash using adb and minimal drivers command is " fastboot flash recovery recovery.img make sure ur downloaded recovery is in adb drvicers folder.
4.after that boot into recovery copy both the files ( rom and gapps)
5.flash them
6.first flash rom and then gaaps
7.done i hope it works .
P.S any query ask me
Click to expand...
Click to collapse
How are you?
I've tried to do what you say but, frist, the command ''fastboot wipe system'' dosen't exist. It dosen't work out.
Than I put the recovery.img, and it was installed with susessfull but also dosen't work out.
The only thing that I got was the screen ''Unlocked device''.
Do you have other ideas to help me? I really don't know what to do anymore. I've almost everything.
Thank you very much.
hey ! I had the same problem, but here's the solution.
First of all, follow the instructions here:
http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3044936
(If the commands dosn't work, remove the "m" of mfastboot in every command.
When it's done, start it, wait 3 minutes (you're gonna have a bootloop) and flash your new rom with the gapps!
The same...
Quentinomino said:
hey ! I had the same problem, but here's the solution.
First of all, follow the instructions here:
http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3044936
(If the commands dosn't work, remove the "m" of mfastboot in every command.
When it's done, start it, wait 3 minutes (you're gonna have a bootloop) and flash your new rom with the gapps!
Click to expand...
Click to collapse
Hey, bro! What's up?
I did everything you said and I follow the commands but also didn't work out. :crying:
The system doesn't start and the recovery also not.
You got anything else to help me? =/
Thanks, bro.
bro tell me whether u r able to access bootloader
yNerd said:
Hey, bro! What's up?
I did everything you said and I follow the commands but also didn't work out. :crying:
The system doesn't start and the recovery also not.
You got anything else to help me? =/
Thanks, bro.
Click to expand...
Click to collapse
Is your phone detected by fastboot in bootloader mode. I recommend you to reflash the bootloader of your device.
Positive.
Master ST said:
bro tell me whether u r able to access bootloader
Click to expand...
Click to collapse
Yeah, bro.
I can access bootloader normally.
It may work.
ayush rao said:
Is your phone detected by fastboot in bootloader mode. I recommend you to reflash the bootloader of your device.
Click to expand...
Click to collapse
How can I do this, bro?
I didn't find a way.
Thanks
yNerd said:
How can I do this, bro?
I didn't find a way.
Thanks
Click to expand...
Click to collapse
Which model do u HAVE?
ayush rao said:
Which model do u HAVE?
Click to expand...
Click to collapse
XT514 LTE (2GEN) 4G
Thanks, bro.
yNerd said:
XT514 LTE (2GEN) 4G
Thanks, bro.
Click to expand...
Click to collapse
Hey man,
Download the Stock ROM corresponding to your device. Then connext your device to the PC in bootloader mode. Then extract the ROM is a folder, in the folder open a command prompt there and type fastboot flash bootloader bootloader.img If this doesnt solve your issue then report back and I'll tell u how to flash ur phone to complete Stock.
never never reflash ur bootloader ...................this will brick ur bootloader
---------- Post added at 06:09 AM ---------- Previous post was at 06:08 AM ----------
sorry it will brick ur phone permanently
---------- Post added at 06:10 AM ---------- Previous post was at 06:09 AM ----------
connect ur phone to ur pc open adb drivers and type " adb devices " is it detects then u must flash the recovery try again and again
if everything goes well i will tell what to do nest
.....its ur luck all d best
---------- Post added at 06:11 AM ---------- Previous post was at 06:10 AM ----------
u can even try ayush rao's idea of installing stock rom
Master ST said:
never never reflash ur bootloader ...................this will brick ur bootloader
---------- Post added at 06:09 AM ---------- Previous post was at 06:08 AM ----------
sorry it will brick ur phone permanently
---------- Post added at 06:10 AM ---------- Previous post was at 06:09 AM ----------
connect ur phone to ur pc open adb drivers and type " adb devices " is it detects then u must flash the recovery try again and again
if everything goes well i will tell what to do nest
.....its ur luck all d best
---------- Post added at 06:11 AM ---------- Previous post was at 06:10 AM ----------
u can even try ayush rao's idea of installing stock rom
Click to expand...
Click to collapse
Dude reflashing the bootloader in fastboot definetly doesn't birck ur phone. And when u flash the stock ROM u always reflash the bootloader.
ayush rao said:
Dude reflashing the bootloader in fastboot definetly doesn't birck ur phone. And when u flash the stock ROM u always reflash the bootloader.
Click to expand...
Click to collapse
Hey, bro.
I also tried this but I didn't have successful.
I'm almost giving up. That seems impossible. =/
I am about to unlock the bootloader but im confused about the TWRP flashing...
I went through the newbie guide and see that we have flash Universal Boot Img Patcher (UBP) after flashing MIUI Recovery ROM Zip
I am confused about the MIUI Recovery ROM Zip... Which ROM is that.??
I am currently on MIUI Global 8.0 Stable (8.0.6.0). Can i just unlock bootloader and flash TWRP and Supersu
Please someone help me with step by step guide to unlock and root this phone...(Unlocking Moto seems easy)
$lim $hady said:
I am about to unlock the bootloader but im confused about the TWRP flashing...
I went through the newbie guide and see that we have flash Universal Boot Img Patcher (UBP) after flashing MIUI Recovery ROM Zip
I am confused about the MIUI Recovery ROM Zip... Which ROM is that.??
I am currently on MIUI Global 8.0 Stable (8.0.6.0). Can i just unlock bootloader and flash TWRP and Supersu
Please someone help me with step by step guide to unlock and root this phone...(Unlocking Moto seems easy)
Click to expand...
Click to collapse
you can try to unlock directly at your current stable rom, somebody able to do it while i can't do it and should move to dev rom to unlock.
if you failed to do it at current rom, you can move to dev rom using miflash and ofc using fastboot rom. if you should move to dev rom to unlock, choose LP rom since MM rom have forced encryption feature by default.
OK.. suppose now I unlocked the bootloader... wat should I do to flash twrp and root the phone.. should I just flash tarp and supersu or should I need to flash anything else... please help me step by step after unlocking bootloader...
follow lolipop unlock process Replace emmc_appsboot.mbn in dev rom and flash via mi flash done,
fastboot oem unlock-go
fastboot flash recovery recovery name.img
then flash radon latest marshmallow version and then flash supersu 2.76 done, its work for me,
$lim $hady said:
I am about to unlock the bootloader but im confused about the TWRP flashing...
I went through the newbie guide and see that we have flash Universal Boot Img Patcher (UBP) after flashing MIUI Recovery ROM Zip
I am confused about the MIUI Recovery ROM Zip... Which ROM is that.??
I am currently on MIUI Global 8.0 Stable (8.0.6.0). Can i just unlock bootloader and flash TWRP and Supersu
Please someone help me with step by step guide to unlock and root this phone...(Unlocking Moto seems easy)
Click to expand...
Click to collapse
This may give you method for rooting...
And for installing cm13 ROM too... With proof...
It worked for me .. I did the same...
First
download the required files from the given link: [50mb]
https://mega.nz/#!1NhDTQoR!cP7vrchwswOfj3oHQ5saZ2d0JkcmunEn5pqyOcpZDoE
INSTRUCTIONS: [redmi note 3]
1. Get into fastboot mode. Charge the phone first. Hold the power button and the volume down button simultaenously.
2. If you can open your current rom, open developer options by clicking on the build no several times in the about phone menu in settings. and select allow oem unlocking and usb debugging.
3. if not leave it... go on and connect your phone to the PC while in fastboot mode.
BUT, before that: open Command prompt on your PC. (search it on the search box). right click on it and open it in administrator mode.
type in: bcdedit /set testsigning on
hit enter and restart your pc
(this is imp.)
4. open the zip file and extract the contents. open the boot edl mode folder and click the edl.bat file. allow it to run.
5. now screen will turn black, do not disturb it. Now flash the twrp by running flash twrp.bat from the 'flash TWRP' folder.
6. Now go to Unlock folder and run the unlock bootloader.bat file.
your phone will boot into the TWRP recovery mode automatically.
if it opens in chineese you select every tab and find the globe icon.
if the globe icon is found on any of the tab select it and change the language to ENGLISH.
wipe your system from the wipe tab:
Now download the latest CM13 SNAPSHOT BUILD ROM FOR YOUR REDMI:
https://download.cyanogenmod.org/get/kenzo-snapshot.zip
and GAPPS:
http://opengapps.org/?api=6.0&variant=mini
do select the arm 64 version and mini one.
download from your pc and copy it to micro sd card. enter this card into you phone and go to mount in twrp.
mount the micro sd card storage.
select the zip file on the micro sd card from the install tab on twrp and flash it.
now go back and flash open gapps zip file.
now REBOOT to system. everything will work fine....
any rom could be installed after it by the same proccess.
you would beome comfortable in doing all this after once trying/.
if you even brick your phone there would always be a way out.
search it on youube.
because everything occurs in partitions , you think hat you have bricked but actually not. there's always a safe way out
---------- Post added at 05:19 PM ---------- Previous post was at 05:17 PM ----------
Do the above method till rooting and installing TWRP.
If you want to install cm14.1 for redmi note 3:
Follow this thread:
http://forum.xda-developers.com/redm...459382/page330
[email protected] said:
This may give you method for rooting...
And for installing cm13 ROM too... With proof...
It worked for me .. I did the same...
First
download the required files from the given link: [50mb]
https://drive.google.com/file/d/0B81...w?usp=drivesdk
INSTRUCTIONS: [redmi note 3]
1. Get into fastboot mode. Charge the phone first. Hold the power button and the volume down button simultaenously.
2. If you can open your current rom, open developer options by clicking on the build no several times in the about phone menu in settings. and select allow oem unlocking and usb debugging.
3. if not leave it... go on and connect your phone to the PC while in fastboot mode.
BUT, before that: open Command prompt on your PC. (search it on the search box). right click on it and open it in administrator mode.
type in: bcdedit /set testsigning on
hit enter and restart your pc
(this is imp.)
4. open the zip file and extract the contents. open the boot edl mode folder and click the edl.bat file. allow it to run.
5. now screen will turn black, do not disturb it. Now flash the twrp by running flash twrp.bat from the 'flash TWRP' folder.
6. Now go to Unlock folder and run the unlock bootloader.bat file.
your phone will boot into the TWRP recovery mode automatically.
if it opens in chineese you select every tab and find the globe icon.
if the globe icon is found on any of the tab select it and change the language to ENGLISH.
wipe your system from the wipe tab:
Now download the latest CM13 SNAPSHOT BUILD ROM FOR YOUR REDMI:
https://download.cyanogenmod.org/get/kenzo-snapshot.zip
and GAPPS:
http://opengapps.org/?api=6.0&variant=mini
do select the arm 64 version and mini one.
download from your pc and copy it to micro sd card. enter this card into you phone and go to mount in twrp.
mount the micro sd card storage.
select the zip file on the micro sd card from the install tab on twrp and flash it.
now go back and flash open gapps zip file.
now REBOOT to system. everything will work fine....
See the following overview video after installing the CM13 ROM:
https://www.youtube.com/watch?v=T--f7ClmQVM
any rom could be installed after it by the same proccess.
you would beome comfortable in doing all this after once trying/.
if you even brick your phone there would always be a way out.
search it on youube.
because everything occurs in partitions , you think hat you have bricked but actually not. there's always a safe way out
---------- Post added at 05:19 PM ---------- Previous post was at 05:17 PM ----------
Do the above method till rooting and installing TWRP.
If you want to install cm14.1 for redmi note 3:
Follow this thread:
http://.xda-.com/redm...459382/page330
Click to expand...
Click to collapse
How we can flash twrp without unlocking bootloder as you say, first flash twrp then unlock Bootloader it's Not posible,
XN Logos said:
How we can flash twrp without unlocking bootloder as you sat, first flash twrp then unlock Bootloader it's Not posible,
Click to expand...
Click to collapse
Both can be done.
Vice versa is also possible.
OK then click unlock bootloader first and then flash twrp.
The reverse can also be done. I did the reverse and I was amazed so thought I should as this to my tutorial
[email protected] said:
Both can be done.
Vice versa is also possible.
OK then click unlock bootloader first and then flash twrp.
The reverse can also be done. I did the reverse and I was amazed so thought I should as this to my tutorial
Click to expand...
Click to collapse
1. bro drive link you provided say file does not exist..............
2. do we have to follow all your steps every time for flashing rom???
Sorptarn said:
1. bro drive link you provided say file does not exist..............
2. do we have to follow all your steps every time for flashing rom???
Click to expand...
Click to collapse
Sorry I accidently removed the link.
I also deleted my review video of YouTube .
I will upload it and get you the link
---------- Post added at 11:08 AM ---------- Previous post was at 11:03 AM ----------
Sorptarn said:
1. bro drive link you provided say file does not exist..............
2. do we have to follow all your steps every time for flashing rom???
Click to expand...
Click to collapse
Once unlocked bootloader and flash twrp.
You don't have to take help of PC or any other thing.
You can always do it on the phone itself.
Boot into twrp by pressing upper volume and power button.
Wipe everything except storages (internal or external)
And then install the ROM zip file and gapps file accordingly.
Do it for any rom
---------- Post added at 11:20 AM ---------- Previous post was at 11:08 AM ----------
Wait uploading the file...
---------- Post added at 11:26 AM ---------- Previous post was at 11:20 AM ----------
Bro file uploaded.
Take it and enjoy.
https://mega.nz/#!1NhDTQoR!cP7vrchwswOfj3oHQ5saZ2d0JkcmunEn5pqyOcpZDoE
---------- Post added at 11:29 AM ---------- Previous post was at 11:26 AM ----------
XN Logos said:
How we can flash twrp without unlocking bootloder as you say, first flash twrp then unlock Bootloader it's Not posible,
Click to expand...
Click to collapse
New link updated for root files
https://mega.nz/#!1NhDTQoR!cP7vrchwswOfj3oHQ5saZ2d0JkcmunEn5pqyOcpZDoE
@[email protected] bro ye global stable miui8 lp mein kaam krega na.............
Sorptarn said:
@[email protected] bro ye global stable miui8 lp mein kaam krega na.............
Click to expand...
Click to collapse
any rom can be install from phone through twrp directly but this is for rom other than miui.
if you install the global stable miui 8 official then its gone. your phone will brick. the bootloader, since is unofficially unlocked, your phone would stuck at mi logo.
now if you wanna install miui rom without any such kinda loss, you see this video: the madthing he explained everything.
download a patched miui 8 rom that will support unofficially unlocked bootloader and will not cause any problem. and it supprts volte too.
or if you want the real miui 8 global rom back . this has to be done by pc.
Install miui 8 patched directly from twrp recovery. [easy one with extra features and safe and volte supported]
https://www.youtube.com/watch?v=B1U1T5gBzbI
Or install the stable miui 8 global offiical rom by pc method. doing everything again. [hard one, success not guaranteed but mostly works. follow each step correctly]
https://www.youtube.com/watch?v=YijIOh9b3mY
his would definetly help you.
do give a thumbs up if you found it helpful
[email protected] said:
any rom can be install from phone through twrp directly but this is for rom other than miui.
if you install the global stable miui 8 official then its gone. your phone will brick. the bootloader, since is unofficially unlocked, your phone would stuck at mi logo.
now if you wanna install miui rom without any such kinda loss, you see this video: the madthing he explained everything.
download a patched miui 8 rom that will support unofficially unlocked bootloader and will not cause any problem. and it supprts volte too.
or if you want the real miui 8 global rom back . this has to be done by pc.
Install miui 8 patched directly from twrp recovery. [easy one with extra features and safe and volte supported]
https://www.youtube.com/watch?v=B1U1T5gBzbI
Or install the stable miui 8 global offiical rom by pc method. doing everything again. [hard one, success not guaranteed but mostly works. follow each step correctly]
https://www.youtube.com/watch?v=YijIOh9b3mY
his would definetly help you.
do give a thumbs up if you found it helpful
Click to expand...
Click to collapse
Thnx fr the update..........
Bt was asking that im currently on miui 8 stable lp........ Th unlock krne k lie miui dev rom th flash nhi krni......
First try this the process I have suggested and given instructions. If any problem comes I would help.
It can alone unlock bootloader. No need to install global kenzo ROM.
I would help just text me
[email protected] said:
First try this the process I have suggested and given instructions. If any problem comes I would help.
It can alone unlock bootloader. No need to install global kenzo ROM.
I would help just text me
Click to expand...
Click to collapse
Tried to unlock bootloader, but the stuck at 50% saying unable to verify device something.. so tried logging into micloud and making hte device active.
Will try it today.
So after unlocking bootloader, just flash TWRP using adb commmands and flash SuperSU??
abihary said:
you can try to unlock directly at your current stable rom, somebody able to do it while i can't do it and should move to dev rom to unlock.
if you failed to do it at current rom, you can move to dev rom using miflash and ofc using fastboot rom. if you should move to dev rom to unlock, choose LP rom since MM rom have forced encryption feature by default.
Click to expand...
Click to collapse
Thank you... I tried to unlock it on global stable rom but not able to do it(stuck a 50%)
Can i just download and 6.9.15 global developer rom and flash it using updater and try unlocking the bootloader or is it necessary to flash fastboot rom only.
If yes, please provide the link for lollipop fastboot rom
$lim $hady said:
Thank you... I tried to unlock it on global stable rom but not able to do it(stuck a 50%)
Can i just download and 6.9.15 global developer rom and flash it using updater and try unlocking the bootloader or is it necessary to flash fastboot rom only.
If yes, please provide the link for lollipop fastboot rom
Click to expand...
Click to collapse
better go to global dev LP to avoid problem with data encryption at global dev MM.
you can download it from this link
abihary said:
better go to global dev LP to avoid problem with data encryption at global dev MM.
you can download it from this link
Click to expand...
Click to collapse
Thanks for the link. Downloading it now..could you please provide the steps to flash this file or a link which helps in flashing fastboot rom...
once i have flashed, just unlock it and flash twrp and supersu.
Any other steps to flash cm 13 or 14..??
$lim $hady said:
Tried to unlock bootloader, but the stuck at 50% saying unable to verify device something.. so tried logging into micloud and making hte device active.
Will try it today.
So after unlocking bootloader, just flash TWRP using adb commmands and flash SuperSU??
Click to expand...
Click to collapse
Yeah
---------- Post added at 10:09 AM ---------- Previous post was at 10:03 AM ----------
[email protected] said:
Yeah
Click to expand...
Click to collapse
If you do it by installing global dev kenzo ROM by mi flash then it may get stuck at 50-60℅ as happened to many here.
I have also experienced it. It got stuck at 40℅. It may happen.
It can say not enough memory to continue or whatever ****.
Leave it don't panic. The ROM has partially been installed.
Now cmtry power off. Or click on boot edl mode. Now directly click unlock bootloader .bat file which I provided. And then click on flash twrp. Bat file.
You phone will automatically boot into twrp and now go last tab of last second row, got to globe icon and change language and now go back and wipe everything.
No wiping internal storage if you have kept any ROM there. But I suggest wipe everything.
Insert a micro SD card or USB otg containing any ROM (because you need to boot up at least) and then flash it along with proper gapps.
---------- Post added at 10:12 AM ---------- Previous post was at 10:09 AM ----------
You phone will boot up and now if you want you can go again to twrp and install a proper ROM of your choice. Or if you want stay there. Boot loader unlocked twrp flashed and everything done.
[email protected] said:
Yeah
---------- Post added at 10:09 AM ---------- Previous post was at 10:03 AM ----------
If you do it by installing global dev kenzo ROM by mi flash then it may get stuck at 50-60℅ as happened to many here.
I have also experienced it. It got stuck at 40℅. It may happen.
It can say not enough memory to continue or whatever ****.
Leave it don't panic. The ROM has partially been installed.
Now cmtry power off. Or click on boot edl mode. Now directly click unlock bootloader .bat file which I provided. And then click on flash twrp. Bat file.
You phone will automatically boot into twrp and now go last tab of last second row, got to globe icon and change language and now go back and wipe everything.
No wiping internal storage if you have kept any ROM there. But I suggest wipe everything.
Insert a micro SD card or USB otg containing any ROM (because you need to boot up at least) and then flash it along with proper gapps.
---------- Post added at 10:12 AM ---------- Previous post was at 10:09 AM ----------
You phone will boot up and now if you want you can go again to twrp and install a proper ROM of your choice. Or if you want stay there. Boot loader unlocked twrp flashed and everything done.
Click to expand...
Click to collapse
Thanks but i don want to unlock it unofficially.. unless its not possible to unlock it officially..
$lim $hady said:
Thanks but i don want to unlock it unofficially.. unless its not possible to unlock it officially..
Click to expand...
Click to collapse
Wait for 1 or 2 weeks then.
And not sure whether it will accept your request or not. OK .
Welcome
Hi guys I was able to root my P10 using magisk and the new treble project on oreo very easily.
All credit goes to @topjohnwu as he's the creator of Magisk and this method all i'm doing is sharing his work and adding the boot image for the P10
Requirements:
Your PC
P10 ON OREO B360 (this only works on oreo if you try to do it on nougat you could easely brick your device)
Bootloader Unlocked (?)
ADB & Fastboot
I actually don't know if you need to have your bootloader unlocked as it's using the treble project to update the boot partition.
I had mine unlocked when i did this.
Step 1:
Get your boot image from update files (huawei update extractor > settings > uncheck the first 3 checkboxes) here i have the boot image from my VTR-L29C432B360
Install the latest Magisk Manager apk from here.
Step 2:
Open Magisk Manager, go to Settings > Update Channel > Custom Update channel with this link http://goo.gl/jefZKH
after that check if the latest magisk update is v15.4 (as the time of posting this guide)
if it says Invalid Update Channel you probably misspelled the link
Step 3:
Copy your boot image to your internal storage/sd card
Go on Magisk Manager > Install > Patch boot image file > Select the boot image on your internal storage/sd card
when it finishes go on your pc and pull the patched boot image to your desktop or desired folder. it will be stored on your internal memory/MagiskManager/patched-boot.img
Step 4:
Open cmd on the same folder as your patched boot image
Go to fastboot (Power-off then Vol+ and Power)
now on cmd type
Code:
fastboot devices
should come as response a serial number and fastboot
this means your device is connected to you pc and on fastboot
after that type
Code:
fastboot flash ramdisk patched_boot.img
it will flash the patched boot image
when it's done just reboot
and you're set!!
You'll have root with Magisk and pass safety net without a problem.
Friend, thanks for the information. Sorry you know how to install viper4android in B360
DarkPJV said:
Friend, thanks for the information. Sorry you know how to install viper4android in B360
Click to expand...
Click to collapse
i wish i knew... i'm also looking for how to install it. if i get it to work i'll post a guide too
D4XT3R said:
i wish i knew... i'm also looking for how to install it. if i get it to work i'll post a guide too
Click to expand...
Click to collapse
It would be fantastic.friend
Thank you very much for this guide, worked like a charm.
I even have full SafetyNet back, incl. CTS. What I didn't have before I flashed the patched bootimage.
I'm just wondering why you suggest to modify the update channel? I got an error message anyway (and I didn't misspell it), so I changed it back to 'Stable' and had not problems.
smashedup said:
Thank you very much for this guide, worked like a charm.
I even have full SafetyNet back, incl. CTS. What I didn't have before I flashed the patched bootimage.
I'm just wondering why you suggest to modify the update channel? I got an error message anyway (and I didn't misspell it), so I changed it back to 'Stable' and had not problems.
Click to expand...
Click to collapse
well the modified channel update is one that @topjohnwu modified for huawei's treble enabled phones like the P10 so that we wouldn't have any problem with safety net or flashing the boot partition but if it worked for you it might work for others too
Hello i just upgraded from nougat to oreo and bootloader is locked again i tried to flash the recovery img without success any solution to root that phone?
samy0x said:
Hello i just upgraded from nougat to oreo and bootloader is locked again i tried to flash the recovery img without success any solution to root that phone?
Click to expand...
Click to collapse
do you have oem unlocking enabled on your phone? if after enabling this option it still fails to flash the patched boot image unlock the boot loader, I know a pain in the ass, but you'll pass safety net without a problem
D4XT3R said:
do you have oem unlocking enabled on your phone? if after enabling this option it still fails to flash the patched boot image unlock the boot loader, I know a pain in the ass, but you'll pass safety net without a problem
Click to expand...
Click to collapse
Yes
Phone Locked
FRP Unlock
have you tried it again and worked? if not it only works with unlocked bootloader
D4XT3R said:
have you tried it again and worked? if not it only works with unlocked bootloader
Click to expand...
Click to collapse
Yes i tried again no solution i'll wait for sometime if no solution i'll unlock bootloader
I'm exploring that solution maybe : https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-root-preserve-user-data-t3716547
I can confirm that Magisk v16 works for me on VTR-L29C432B360. Installed with the Magisk Manager without flashing in TWRP.
Jannomag said:
I can confirm that Magisk v16 works for me on VTR-L29C432B360. Installed with the Magisk Manager without flashing in TWRP.
Click to expand...
Click to collapse
How did you do that
samy0x said:
How did you do that
Click to expand...
Click to collapse
I opened the Magisk Manager app and it prompted me that v16 is available for install. Then I pressed "Install", rebooted and that was it.
What about working Xposed and Magisk like on Nouget EMUI 5.1? I'm always stock in boot-look when i try to flash BETA3 Xposed v90 SDK 26 amr64
---------- Post added at 07:59 PM ---------- Previous post was at 07:58 PM ----------
Jannomag said:
I opened the Magisk Manager app and it prompted me that v16 is available for install. Then I pressed "Install", rebooted and that was it.
Click to expand...
Click to collapse
Yes me to, but first you need 15.4 magisk version and than you can update to v16 in MagiskManager app
urbanboymne said:
What about working Xposed and Magisk like on Nouget EMUI 5.1? I'm always stock in boot-look when i try to flash BETA3 Xposed v90 SDK 26 amr64
---------- Post added at 07:59 PM ---------- Previous post was at 07:58 PM ----------
Yes me to, but first you need 15.4 magisk version and than you can update to v16 in MagiskManager app
Click to expand...
Click to collapse
Oh, of course. Sorry, I meant with "not flashing with TWRP" that I didn't need to flash the zip for v16 manually, just install it within the app. But of course you need to install 15.4 first.
meh , cant extract ramdisk.img from update.zip...
About magisk...is the root gone away finally fixed ?
on my old nova plus,when rooted whit magisk,we had to flash that darn patched boot img every 1-2 weeks in order to re have root again
is that finally fixed ?
Jannomag said:
I can confirm that Magisk v16 works for me on VTR-L29C432B360. Installed with the Magisk Manager without flashing in TWRP.
Click to expand...
Click to collapse
Exactly the same for me... and passes safety net
---------- Post added at 02:04 PM ---------- Previous post was at 01:57 PM ----------
Can we flash TWRP 3.1.1 after rooting with Magisk ?
Big thankyou it worked like a charm
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 ?