i am not been able to use twrp recovery on my stock rom marshmallow 6.0 on my xt1521
earlier when i used CM13 i had no issue using twrp but now after flashing stock rom when i flash twrp and try to start my mobile it just show the unlocked bootloader warning screen for forever
as i didn't have a recovery i can't even flash SuperSU and actually root my device
Please anyone help me
thanks i advance
Hi,
Had the same issue on my XT1521. Just got TWRP flashed an hour ago. Use Squids TWRP recovery and it should work fine. I'm not sure about SuperSU though. The last time I tried to flash SuperSU I ended up in a bootloop.
Rahul Salin said:
Hi,
Had the same issue on my XT1521. Just got TWRP flashed an hour ago. Use Squids TWRP recovery and it should work fine. I'm not sure about SuperSU though. The last time I tried to flash SuperSU I ended up in a bootloop.
Click to expand...
Click to collapse
did you try flashing anything else using twrp apart from supersu?
OK mate since you asked I tried installing Xposed and Android N-ify module and it worked perfectly fine.
okay thanks buddy but how are you gonna use anything which demand root access without supersu
Sorry mate I don't know for sure how to do it now. Maybe some senior member will have the answer. Also I read somewhere that you might need to flash a custom kernel after installing SuperSU to avoid the bootloop. I'm not sure about it. I'll check it out tomorrow. Right now I have my 16GB SD card configured as internal with lot of data. After backing up I'll try it tomorrow and post the results.
that'll be a great help friend
Today tried to root with SuperSU 2.77 and 2.78. The phone boots up and us stuck at the Moto logo. Even tried with Squids Kernel latest but it's still same results.
i think we can not root stock rom 6.0 on moto e 2nd gen because earlier when my phone had lollipop it had no issue rooting
anyway do you know any custom rom that supports volte?
Same here bro. No problem in lollipop. I used CM13 till I got stock 6.0. CM 13 is prerooted and can be turned ON as needed. I'm not sure about VoLTE. I think VoLTE is fully working only in stock ROM from what I know. Actually there is another thread with same question on VoLTE regarding Jio SIM. Which region are you from?
Which SIM are you using?
yes same here i used CM13 too before this but i was facing some problem over lte on CM that is the reason why i got back to stock
yes i read that thread but there is no resolution there
i an from chhattisgarh(middle east)
Well I guess for now if u want to use VoLTE it's best to stick with stock ROM. I'm currently staying in Saudi and VoLTE seems to be working here in Moto E2 LTE.
Finally found a way to root Stock MM!! Install Squids recovery Moto LTE, then install SuperSU 2.62-3. Link given below.
http://downloadmirror.co/1iLy/BETA-SuperSU-v2.62-3-20151211162651.zip
could you provide squid recovery link too?
Here you go:
http://forum.xda-developers.com/devdb/project/dl/?id=17768
Okay now let me walk you through the things i did
I downloaded the same squid twrp recovery and flashed it through adb and after that i restarted bootloader and flashed the supersu file and it was successful but when i started my phone it again shows me the same unlocked bootloader screen forever and i again had to flash the stock rom
Yes. That's how I did too. Flashed Squids TWRP recovery, then flashed SuperSU 2.62-3. Then you have to Wipe Dalvik and Cache to avoid any bootloops. My phone is working perfectly with root.
https://drive.google.com/file/d/0B8hsM4iKLYRdOHFnY1JnY0FWNWc/view?usp=drivesdk
I Want to know that did you flashed squid kernel too or you are just using the stock one.
And are you getting volte support now?
sankhemka said:
I Want to know that did you flashed squid kernel too or you are just using the stock one.
And are you getting volte support now?
Click to expand...
Click to collapse
I'm using stock kernel. As for VoLTE stock MM supports it. If ur network supports VoLTE you will see a VoLTE icon next to that cellular network bars. There was a screenshot someone posted in the other thread with VoLTE icon in Jio I think.
---------- Post added at 09:53 AM ---------- Previous post was at 09:31 AM ----------
This was the guide I used for rooting:
http://androiding.how/root-moto-g-2014-marshmallow/
---------- Post added at 09:57 AM ---------- Previous post was at 09:53 AM ----------
Check out this screenshot by Sher1234:
http://forum.xda-developers.com/mot...upported-roms-moto-e-ltesurnia-t3384142/page2
thanks a ton buddy now it really worked
earlier i flashed different recovery
after i flashed recovery you provided it worked
Related
Hi Guys!
Today I need your help. My moto e runs perfectly on kitkat roms only. When I flash lp or mm roms, it's system ui starts force closing. This is how the problem started:
I was on cm13 nightly and I decided to update my twrp from play store. So, I downloaded the twrp manager app from play store and updated my recovery to 3.0.0. And the phone worked perfectly until the next day, when it started giving Fc's all of a sudden. I rebooted to recovery and made a full wipe including internal storage. Then I flashed cm11 and flashed gapps. The ROM booted up perfectly and had no fc's at all. So I decided to flash mm again. I flashed AOKP marshmallow but it again started giving me FC's. So, I reverted back to cm11and found no fc's again.
Here's the list of ROMs I tried and was unsuccessful each time:
AOKP(MM)
AOSP(MM and LP)
Cm13
Cm12.1
Blisspop(MM and LP)
Tesla ROM(LP)
Crdroid(MM)
ZephyrOS(MM)
AICP(MM)
Here's the list of ROMs I flashed and the device didn't give any fc's:
Cm11 nightly
Stock ROM Optimized
Stock ROM Full
CrDroid(kitkat)
Please guys I am in need of Deliberate help. Please do not post condolence comments like,"Strange issue mate, Sorry I don't know, Best of Luck". Please post only if you know the method or you have any links to the method.
In need of your help,
Regards,
PoseidonKing
I had the same issue with other MM roms. I got no fc error on CM13 and Resurrection Remix MM rom. Only these two mm Roms worked for me.
It's surely a device hardware issue. If only kitkat based roms work in your condor, then maybe it doesn't properly support art framework. So your last resort maybe going to service center
Sent from my Moto E
Try flashing factory image
Sent from my Moto E using Tapatalk
i think the problem is in the recovery. download cwm recovery img and flash it with fastboot and after that wipe everything including internal storage (do not reboot recovery at that tyme or before installing rom ) do not wipe ur sd card and then install rom without gapps and boot up after sucessful boot then again boot to recovery and install gapps... if problems remains same then try downloading other gapps package for 6.0 (preferred open gapps).
no need all of this, just record the logcat and post here, surely you'll get proper fix!
I think Twrp 3.0 is causing this revert to old 2.8 version.It is nothing to do with hardware if it is a hardware related problem then you can't even switch on phone.
Agreed! Custom recoveries known to, often cause these sort of problems.. Give the twrp 3.0.2 by magdoez or 2.8.7 a try.. These are the ones that work perfectly for me.
Try updating recovery from your current recovery itself & reboot.. Then try the aforementioned mm roms..
piku 123 said:
I think Twrp 3.0 is causing this revert to old 2.8 version.It is nothing to do with hardware if it is a hardware related problem then you can't even switch on phone.
Click to expand...
Click to collapse
Thanks bro, but the method ain't working. I am currently on TWRP 2.7.1.0 and I still face the same problem...
Adarsh1998 said:
no need all of this, just record the logcat and post here, surely you'll get proper fix!
Click to expand...
Click to collapse
Okay, thanks! But how the hell do I record a logcat??
PoseidonKing said:
Okay, thanks! But how the hell do I record a logcat??
Click to expand...
Click to collapse
Refer this thread: http://forum.xda-developers.com/showthread.php?t=1726238&page=28
Sent from my Moto E using Tapatalk
Hi guys,
Thank You everyone for your generous and quick help. My Moto E is fixed now. I flashed cyanpop mm and then tried the adopted sd option. Rebooted the device and now it is working perfectly. Though it wouldn't have been possible without my brother's help @Andy1911. Thank you once again to all of them who helped me.
Regards,
PoseidonKing.
Hello,
Tried all ROMS, none is working, below is the detail:
Installed
1 . CRISSCROSS ROM - no audio, while on call in earpiece and loudspeaker
2 . XtreStoLite-ROM-3.3.1-DPDP.zip ROM, Problem - AFter flash Phone model shows G925F AND NO CONNECTION TO NETWORK, EMERGENCY CALLS ALL TIME, TRIED flashing MODEM for g925w8 no LUCK
3. KIngfisher ROM, after flashing Kingfisher ROM, phone is STUCK AT
*KERNEL IS NOT SEANDROID ENFORCING* and phone will not turn ON.
SO , I guess there is NO working CUSTOM ROM fOR G925W8,canada. At the end I flashed stock BOJ7 AND Phone is working perfectly with 5 1 1 G925W8 BOJ7
I'm using the G925W8 on Xtrestolite. You must be missing something. I'm not sure what though
KAwAtA said:
I'm using the G925W8 on Xtrestolite. You must be missing something. I'm not sure what though
Click to expand...
Click to collapse
so why am I getting emergency calls?
1 can you tell me in detail that which steps did you follow?
2 what was your android version when you flashed rom?
3 what is your baseband verison now?
4 Was it rooted already?
5 Does this rom have spanish langauage? can you check for me?
Thank you
@Administr4tor
Custom ROMs for that work for W8
I've have confirmation from multiple users that my OZOP Rom is compatible and working flawlessly for the following devices Flat and Edge (rom is Edge based) F/I/T/W8. Could be more this are just the confirmed working devices.
Also OZOP is currently very active with development and actually about to be updated!
What ever Rom you decide is up to you.
Just letting you know there are options available.
Good luck
I believe you need to update your bootloaders using a stock 6.0.1 image or flash them via odin.
Also look in the T mobile section for a custom kernel like stang has a rom showing for. Our devices were basically secondhand tmobile rebranded as W8. Everything is literally the same minus us canadian guys cant use wifi calling.
So in short flash rom, then kernel and let it boot. Once it boots then turn it off and restart into recovery and flash call fix. If you need an updated callfix I can post a link here.
I found if you flash all three before first boot the zip from callfix creates a bootloop. Therefore it tells me the zip needs to be flashed over a built system
Nothing seems to work, No matter what I have No network connection... on any rom..
AndroTechGuy said:
Nothing seems to work, No matter what I have No network connection... on any rom..
Click to expand...
Click to collapse
You mentioned it worked on 5.1.1 thats your problem u need to take the ota or flash stock 6.0.1 with odin or find the 6.0.1 bootloader and radio and flash them cuz all the roms your trying are 6.0.1 base thats why u dont have service im suprised they even boot.
xstokerx said:
You mentioned it worked on 5.1.1 thats your problem u need to take the ota or flash stock 6.0.1 with odin or find the 6.0.1 bootloader and radio and flash them cuz all the roms your trying are 6.0.1 base thats why u dont have service im suprised they even boot.
Click to expand...
Click to collapse
I could have sworn I was running 6.0.1 stock, Maybe I wasn't, but alright I'll try to find the radio. thanks mate
christopherrrg said:
I believe you need to update your bootloaders using a stock 6.0.1 image or flash them via odin.
Also look in the T mobile section for a custom kernel like stang has a rom showing for. Our devices were basically secondhand tmobile rebranded as W8. Everything is literally the same minus us canadian guys cant use wifi calling.
So in short flash rom, then kernel and let it boot. Once it boots then turn it off and restart into recovery and flash call fix. If you need an updated callfix I can post a link here.
I found if you flash all three before first boot the zip from callfix creates a bootloop. Therefore it tells me the zip needs to be flashed over a built system
Click to expand...
Click to collapse
yes, I need updated call fix as the one I have is only for 5 1 1
Administr4tor said:
yes, I need updated call fix as the one I have is only for 5 1 1
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B4Gyz91x5k7gc2NBS2N5TFQwY0k/view?usp=drivesdk
Uploaded to my personal drive because I got tired of chasing the link. (Credits to author of zip, name inside.)
xstokerx said:
You mentioned it worked on 5.1.1 thats your problem u need to take the ota or flash stock 6.0.1 with odin or find the 6.0.1 bootloader and radio and flash them cuz all the roms your trying are 6.0.1 base thats why u dont have service im suprised they even boot.
Click to expand...
Click to collapse
Every time I try to flash the stock 6.0.1 i get SW Rev error Device 4 Binary 3.
AndroTechGuy said:
Every time I try to flash the stock 6.0.1 i get SW Rev error Device 4 Binary 3.
Click to expand...
Click to collapse
http://www.sammobile.com/firmwares/database/SM-G925W8/ get your firmware here for your carrier
I was told you get this error when trying to downgrade or by flashing the wrong package
Follow this http://www.w0lfdroid.com/2015/04/Ho...irmware-on-Samsung-Galaxy-S6-S6-Edge.html?m=1
xstokerx said:
http://www.sammobile.com/firmwares/database/SM-G925W8/ get your firmware here for your carrier
I was told you get this error when trying to downgrade or by flashing the wrong package
Follow this http://www.w0lfdroid.com/2015/04/Ho...irmware-on-Samsung-Galaxy-S6-S6-Edge.html?m=1
Click to expand...
Click to collapse
I know how to do it, the phone is unlocked, so not sure what carrier I should be flashing on it. I legit just need it to be able to use the Network, currently have it custom rom'd but no network.
xstokerx said:
http://www.sammobile.com/firmwares/database/SM-G925W8/ get your firmware here for your carrier
I was told you get this error when trying to downgrade or by flashing the wrong package
Follow this http://www.w0lfdroid.com/2015/04/Ho...irmware-on-Samsung-Galaxy-S6-S6-Edge.html?m=1
Click to expand...
Click to collapse
So the best I've been able to do is get it on a custom rom with no network connection at all. Seems like Im losing the ability to get it working. I tried Wind, telus stock 6.0.1's and i get the SW rev error, I've tried Rogers 5.1.1, and I get the same. Only thing that flashed on my device was "AP_G925W8VLU2AOG2_CL4808800_QB5701859_REV02_user_low_ship.tar" but it didn't boot past Galaxy S6 Edge logo, and recovery wasn't loading to try and factory reset to continue boot. I'm pretty sure this phone is dead.... I mean the custom rom was 6.0.1 with arter kernel, but no service... I'm lost...
christopherrrg said:
https://drive.google.com/file/d/0B4Gyz91x5k7gc2NBS2N5TFQwY0k/view?usp=drivesdk
Uploaded to my personal drive because I got tired of chasing the link. (Credits to author of zip, name inside.)
Click to expand...
Click to collapse
Thanks Sir.
Any ideas to my posts above?
guaranteed it's the bootloader and modem.
Once you flash the 6.0.1 ones via ODIN, then both crisscross and xtrolite should work. Crisscross, you will need to flash an independent audio fix which Christ have provided you in the post above.
Xtrolite (which I'm using with Twisted V4 Kernel) has it integrated so you shouldn't have any audio problems. Mind you, if you're still having trouble. Flash back 5.1.1 stock kernel and then let it update officially via samsung kies or OTA. Our phones now have 6.0.1 release so once you do that, you'll automatically have the new 6.0.1 bootloader and modem for our 925w8 phones. Then it'll be simple to flash a custom rom at that point.
Just update stock system to Marshmallow 6.0.1 (or flash stock 6.0.1 via Odin), then flash TWRP, do standard wipe with TWRP (Data, Cache and Dalvik), flash XtreStoLite via TWRP and everything will work
I have canadian S6 Edge and XtreStoLite is working very good
cripez said:
guaranteed it's the bootloader and modem.
Once you flash the 6.0.1 ones via ODIN, then both crisscross and xtrolite should work. Crisscross, you will need to flash an independent audio fix which Christ have provided you in the post above.
Xtrolite (which I'm using with Twisted V4 Kernel) has it integrated so you shouldn't have any audio problems. Mind you, if you're still having trouble. Flash back 5.1.1 stock kernel and then let it update officially via samsung kies or OTA. Our phones now have 6.0.1 release so once you do that, you'll automatically have the new 6.0.1 bootloader and modem for our 925w8 phones. Then it'll be simple to flash a custom rom at that point.
Click to expand...
Click to collapse
issue is I can't make the 6.0.1 stock files flash, always getting the SW rev error when cm.bin tries to flash, I've tried, Rogers, Wind, Telus stock files, nothing works. On CrissCross right now but not service... I want to get back to stock or at least make the bootloader work.
EDIT: Apparently using the most recent koodo stock, got me back to stock rom and with service! Now to root and do the custom rom properly! Thanks all!
christopherrrg said:
I believe you need to update your bootloaders using a stock 6.0.1 image or flash them via odin.
Also look in the T mobile section for a custom kernel like stang has a rom showing for. Our devices were basically secondhand tmobile rebranded as W8. Everything is literally the same minus us canadian guys cant use wifi calling.
So in short flash rom, then kernel and let it boot. Once it boots then turn it off and restart into recovery and flash call fix. If you need an updated callfix I can post a link here.
I found if you flash all three before first boot the zip from callfix creates a bootloop. Therefore it tells me the zip needs to be flashed over a built system
Click to expand...
Click to collapse
THIS G925W8 is working perfectly in 5 1 1 , I was able to make calls to all networks including GSM and WCDMA, I checked IMEI status with code 197328640 and IMIE status is OK, then after I flashed 6 0 1 and then the IMIE status turns to NOT GOOD and I am unable to make calls and stuck at EMERGENCY CALLS, looks like this PHONE IS JACKED??
Hi,
I have a bootloader unlocked honor 5x kiwi l22 , I have flashed TWRP on it and tried the usual procedure to install custom ROM ( lineage 14.1) but it installs normally on the system but no matter how much ever I try to boot it back all it shows me was lineage os boot animation and then again screen goes black and reboots again and again there doesn't seem to be an end to this I tried wiping dalvik cache and also formatting but none of which helped my build number is kiw l22c675b360
which built r u on
Suriya1996 said:
Hi,
I have a bootloader unlocked honor 5x kiwi l22 , I have flashed TWRP on it and tried the usual procedure to install custom ROM ( lineage 14.1) but it installs normally on the system but no matter how much ever I try to boot it back all it shows me was lineage os boot animation and then again screen goes black and reboots again and again there doesn't seem to be an end to this I tried wiping dalvik cache and also formatting but none of which helped my build number is kiw l22c675b360
Click to expand...
Click to collapse
If you were on b360, you wont be able to boot custom roms. If may need to go back to lollipop and then marshmallow or just fladh full firmware of b350. You can boot till b350 and any version of b360 or higher.
shashank1320 said:
If you were on b360, you wont be able to boot custom roms. If may need to go back to lollipop and then marshmallow or just fladh full firmware of b350. You can boot till b350 and any version of b360 or higher.
Click to expand...
Click to collapse
Where can I find the flashable stock Roms?
Flash complete B350, then flash lineagros! May I
---------- Post added at 03:03 PM ---------- Previous post was at 03:01 PM ----------
I have also encountered the same problem!
---------- Post added at 04:03 PM ---------- Previous post was at 03:03 PM ----------
Can not flash B350, I use Huawei eRecovery, restore the version of kiw_AL10c92b437, I wonder if this version can be installed through twrp lineage OS? I am not sure, is someone to do? Some people have a more simple way to reduce to the previous version
---------- Post added at 04:05 PM ---------- Previous post was at 04:03 PM ----------
Direct flashing not 350 will be wrong ... I would like to ask the better through twrpflash lineage OS?
shashank1320 said:
If you were on b360, you wont be able to boot custom roms. If may need to go back to lollipop and then marshmallow or just fladh full firmware of b350. You can boot till b350 and any version of b360 or higher.
Click to expand...
Click to collapse
I have the same problem. I am on build 437 .
Where I can find a fitting build for KIW-UL00C00B437 to install custom ROMs?
Florian990107 said:
Where can I find the flashable stock Roms?
Click to expand...
Click to collapse
Install firmware finder app or go to
http://hwmt.ru/oth/HWFF/info/view.php?find_model=
and download zip which is full package
and make a clean flash through twrp
Never use twrp to flash huawei ota updates
I think you need to flash Superuser by TWRP, it will be rooted, then you can flash rom, i already flashed my phone by lineage and Cosmic (7.1 nuguts). by the way i have Huawei GR5-kii-l05.
david3709 said:
I think you need to flash Superuser by TWRP, it will be rooted, then you can flash rom, i already flashed my phone by lineage and Cosmic (7.1 nuguts). by the way i have Huawei GR5-kii-l05.
Click to expand...
Click to collapse
No. It bootloops because OP has B360 base which has VoLTE. Custom ROMs will never boot on that.
Sent from my Honor 8 using XDA Labs
Yes no roms boot on that firmware
Suriya1996 said:
Hi,
I have a bootloader unlocked honor 5x kiwi l22 , I have flashed TWRP on it and tried the usual procedure to install custom ROM ( lineage 14.1) but it installs normally on the system but no matter how much ever I try to boot it back all it shows me was lineage os boot animation and then again screen goes black and reboots again and again there doesn't seem to be an end to this I tried wiping dalvik cache and also formatting but none of which helped my build number is kiw l22c675b360
Click to expand...
Click to collapse
The firmware you're on (b360) won't let you use custom ROMs
Well. Thats the modem issue . To elaborate , kernel panic since it cant start modem and tries to restart the device in order to enable modem . this never happens and leads to endless reboots
How to back in 350b
TWRP 3.1.1-0 Moto G5S plus (sanders)
Latest TWRP changelog :
3.1.1-0 full changelog
Bugs :
Didn't found any for now, if you find something, you can report to me.
IMPORTANT NOTE :
At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
Force encryption is enabled by default in stock OS and twrp will successfully decrypt /data at first boot if all goes well
If in case decryption doesn't go fine, twrp will popup a dialog box asking for password and that means decryption went wrong and you would need to wipe data once via twrp wipe options and reboot back to twrp for functioning of /data
Installation Guide :
Make sure you have unlocked bootloader | Follow these instructions for unlocking it: https://forum.xda-developers.com/g5-plus/how-to/how-to-unlock-bootloader-moto-g5-plus-t3573879
Reboot to bootloader
fastboot flash recovery twrp-****.img (if you want permanent flash) or fastboot boot twrp-****.img (if you want temporary
boot)
For rooting, you can use Magisk or SuperSU, both work fine
Download Link :
twrp-3.1.1-sanders
Ps :
I'm waiting for official kernel sources release for this device (sanders), before compiling custom roms, kernels etc... (I've tried with moto G5 plus sources but camera/flash didnt worked :/ )
Hope you like it!
XDA:DevDB Information
[Unofficial] TWRP 3.1.1-0 Moto G5S Plus, ROM for the Moto G5S Plus
Contributors
GeneticEnginer, Santhosh M, vache
Source Code: http://Stock kernel image/dtb
ROM OS Version: 7.x Nougat
Version Information
Status: Beta
Created 2017-09-08
Last Updated 2017-09-07
will magisk will work for verity disable ?
Do i need to flash the verity disable zip if i flash magisk?
hellboy180699 said:
Do i need to flash the verity disable zip if i flash magisk?
Click to expand...
Click to collapse
No, magisk handles it
GeneticEnginer said:
No, magisk handles it
Click to expand...
Click to collapse
is it ported from g5+ or compiled?
Mohan0004 said:
is it ported from g5+ or compiled?
Click to expand...
Click to collapse
Ported, ive just switched kernel image and dtb
Great...i would be sooooo grateful if someone could just upload the tutorial. Because i was using pixel and it has so many steps included to root.
Thanks in advance.
---------- Post added at 11:14 AM ---------- Previous post was at 11:14 AM ----------
Premkrishna said:
Great...i would be sooooo grateful if someone could just upload the tutorial. Because i was using pixel and it has so many steps included to root.
Thanks in advance.
Click to expand...
Click to collapse
Never mind...found it above. Ignore this dumb guy for now.
I flashed SuperSU for root.. but SuperSU is not working fine.. it shows "Root undetected" after sometime. I want to use Magisk now. But it shows error "boot image already patched by other program". Tell me any solution.
shu006 said:
I flashed SuperSU for root.. but SuperSU is not working fine.. it shows "Root undetected" after sometime. I want to use Magisk now. But it shows error "boot image already patched by other program". Tell me any solution.
Click to expand...
Click to collapse
Did you make a backup of boot partition?
GeneticEnginer said:
Did you make a backup of boot partition?
Click to expand...
Click to collapse
Yes but after flashing SuperSU ????
Can u send backup of boot partition?
Or from where I can download official firmware?
Was anyone able to root the phone successfully according to the tutorial? I am gonna try this, however would like to know if anyone was able to get it right?
Just so that my confident level increases.!
shu006 said:
Yes but after flashing SuperSU
Click to expand...
Click to collapse
GeneticEnginer said:
shu006 said:
Yes but after flashing SuperSU
Click to expand...
Click to collapse
?
---------- Post added at 04:01 PM ---------- Previous post was at 03:58 PM ----------
Premkrishna said:
Was anyone able to root the phone successfully according to the tutorial? I am gonna try this, however would like to know if anyone was able to get it right?
Just so that my confident level increases.!
Click to expand...
Click to collapse
Yes rooted.. Use magisk.. Everything is perfect
Click to expand...
Click to collapse
Rooted with supersu. Now I want to root wit Magisk, can I flash Magisk after selecting Unroot option given in supersu app?
vyaskd said:
Rooted with supersu. Now I want to root wit Magisk, can I flash Magisk after selecting Unroot option given in supersu app?
Click to expand...
Click to collapse
After unrooting its better to restore stock boot img before flashing magisk
Out of curiosity...
Which is better, MAGISK OR SUPERSU.?
Is one thing superior or inferior to the other in any way..? I have been with Supersu all these years, will magisk be complicated for me to flash?
Hurrayyyy rooted!!!
I rooted my device at the first try.! Actually, i flashed SU 2.82, but did not work properly. Then i flashed 2.79 and everything is working pretty fine.
Now i can change fonts.....icons.....themes....layers....etc etc.
Thank you so much developers...
---------- Post added at 11:10 AM ---------- Previous post was at 10:48 AM ----------
Premkrishna said:
I rooted my device at the first try.! Actually, i flashed SU 2.82, but did not work properly. Then i flashed 2.79 and everything is working pretty fine.
Now i can change fonts.....icons.....themes....layers....etc etc.
Thank you so much developers...
Click to expand...
Click to collapse
Guys, i installed SU 2.79 and it was working fine for like 5 minutes and then it started telling me that the phone is not rooted or Root un-deducted.
Need help!
---------- Post added at 11:48 AM ---------- Previous post was at 11:10 AM ----------
Can anyone give me the stock boot image for G5S Plus? I am trying to install Magisk and it is telling me that someother custom app had patched my boot image. So, i have to get back to stock boot image and do the magisk flash.
I initially installed SU and that might have caused this error. HELPPPPP!!!!
---------- Post added at 01:42 PM ---------- Previous post was at 12:48 PM ----------
GeneticEnginer said:
After unrooting its better to restore stock boot img before flashing magisk
Click to expand...
Click to collapse
Where can I find a stock boot image, cuz I am on the same boat as him too...
BRICKED!!!
Probably the first person to successfully brick the MOTO G5S.
I bet you guys wanna know how i did that. I messed up my phone after rooting with SU 2.79. I installed substratum and other customization apps which apparently did not support the stock ROM.
So, i decided to wipe the data and ended up wiping the ROM itself. I am able to get into TWRP.
My only way out is to wait untill @GeneticEnginer , comes up with a ROM to flash. Untill time to say goodbyeee! Seriously guys, i am sad.
---------- Post added at 03:59 PM ---------- Previous post was at 03:59 PM ----------
BRICKED!!!
Probably the first person to successfully brick the MOTO G5S.
I bet you guys wanna know how i did that. I messed up my phone after rooting with SU 2.79. I installed substratum and other customization apps which apparently did not support the stock ROM.
So, i decided to wipe the data and ended up wiping the ROM itself. I am able to get into TWRP.
My only way out is to wait untill @GeneticEnginer , comes up with a ROM to flash. Untill time to say goodbyeee! Seriously guys, i am sad.
Premkrishna said:
BRICKED!!!
Probably the first person to successfully brick the MOTO G5S.
I bet you guys wanna know how i did that. I messed up my phone after rooting with SU 2.79. I installed substratum and other customization apps which apparently did not support the stock ROM.
So, i decided to wipe the data and ended up wiping the ROM itself. I am able to get into TWRP.
My only way out is to wait untill @GeneticEnginer , comes up with a ROM to flash. Untill time to say goodbyeee! Seriously guys, i am sad.
---------- Post added at 03:59 PM ---------- Previous post was at 03:59 PM ----------
BRICKED!!!
Probably the first person to successfully brick the MOTO G5S.
I bet you guys wanna know how i did that. I messed up my phone after rooting with SU 2.79. I installed substratum and other customization apps which apparently did not support the stock ROM.
So, i decided to wipe the data and ended up wiping the ROM itself. I am able to get into TWRP.
My only way out is to wait untill @GeneticEnginer , comes up with a ROM to flash. Untill time to say goodbyeee! Seriously guys, i am sad.
Click to expand...
Click to collapse
No worries just take twrp backup of anyone who has properly booting device and just restore that backup it will help bring your device back to life or wait till stock rom or developers to build a rom
---------- Post added at 06:19 PM ---------- Previous post was at 06:15 PM ----------
Actually i am learning development i learnt how to sync source codes and build a rom but sadly dont have enough internet speed to download that rom source code else i would have built a rom for our device. I will wait till i get enough money to get high speed internet then i will build something for sure
after rooting my pocophone , i was trying different modules from magisk. after installing lkt module, i chose battery profile and rebooted my device. after that my touch screen stopped working completely. i have flashed stock rom and locked the bootloader but the touch screen is still not working. please help
touk1r said:
after rooting my pocophone , i was trying different modules from magisk. after installing lkt module, i chose battery profile and rebooted my device. after that my touch screen stopped working completely. i have flashed stock rom and locked the bootloader but the touch screen is still not working. please help
Click to expand...
Click to collapse
Try flash official recovery and stock firmware (locked bootloader)
or Offcial TWRP (not custom recovery because it a lot touch issues) and Custom Rom (unlocked bootloader)
---------- Post added at 11:30 PM ---------- Previous post was at 11:29 PM ----------
AndreSkywalker said:
Try flash official recovery and stock firmware (locked bootloader)
or Offcial TWRP (not custom recovery because it a lot touch issues) and Custom Rom (unlocked bootloader)
Click to expand...
Click to collapse
And flash magisk unistaller
thanks man. i was flashing developer rom. global stable rom worked fine
help me
touk1r said:
thanks man. i was flashing developer rom. global stable rom worked fine
Click to expand...
Click to collapse
i haved the same issue on my poco f1
can you link the file you've used sir?
kaizer13 said:
i haved the same issue on my poco f1
can you link the file you've used sir?
Click to expand...
Click to collapse
Are you having touch issues?
Touch Screen stopped working pocof1
ironman38102 said:
Are you having touch issues?
Click to expand...
Click to collapse
sir i recently unlocked bootloader to install miui12 pilot tester rom but i got stuck in twrp because of touch issue so i flashed to miui global v11.0.6.0 using miflash tool installation completed but still there is touch scrreen stopped working.. help me sir
Flash via fastboot with mi flash tool a stock ROM V10.2.3.0. Only this firmware fix touch dead after bad update in twrp. Here link for download this firmware https://bigota.d.miui.com/V10.2.3.0....73c9f4b81c.tgz
Flash fastboot rom or else go to service center.
Don't flash older MIUI firmware or ROMs , Due to anti-rollback feature enabled