p8 lite stucks at huawei logo after flashing UPDATE-SuperSU-v2.76-SYSTEMMODE.zip - P8lite Q&A, Help & Troubleshooting

hi guys
i tried to flash UPDATE-SuperSU-v2.76-SYSTEMMODE.zip after twrp recovery at huawei p8 lite marshmellow ALE-L21C185B525, device works fine without flashing SuperSU. but when i try to restart after flashing, it stucks at boot logo. i have tried wiping delvik cache, or factory reset but nothing works.
can anyone help me ?

htc.hero said:
hi guys
i tried to flash UPDATE-SuperSU-v2.76-SYSTEMMODE.zip after twrp recovery at huawei p8 lite marshmellow ALE-L21C185B525, device works fine without flashing SuperSU. but when i try to restart after flashing, it stucks at boot logo. i have tried wiping delvik cache, or factory reset but nothing works.
can anyone help me ?
Click to expand...
Click to collapse
Happens sometime.. Happened with me too.. Dont know why but flashing supersu 2.76 sometimes gets stuck at bootlogo.. Try flashing system image.. If that does not help then force upgrade via putting update.app in external memory
Sent from my ALE-L21 using XDA-Developers mobile app

amageek said:
Happens sometime.. Happened with me too.. Dont know why but flashing supersu 2.76 sometimes gets stuck at bootlogo.. Try flashing system image.. If that does not help then force upgrade via putting update.app in external memory
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
force upgrade will overwrite the twrp recovery with huawei stock recovery. isn't it?
should i flash system image extracted from stock update through twrp or bootloader?

amageek said:
Happens sometime.. Happened with me too.. Dont know why but flashing supersu 2.76 sometimes gets stuck at bootlogo.. Try flashing system image.. If that does not help then force upgrade via putting update.app in external memory
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
it didn't work.
flashing system image after supersu flash doesn't work.

it worked for me tutorial-root-emui-4-0-android-6

htc.hero said:
it worked for me tutorial-root-emui-4-0-android-6
Click to expand...
Click to collapse
yes i prefer this version of supersu rather than 2.76... i always flashed these two zips, but that day, on a mood swing, i flashed 2.76... will never do that again...
glad it worked out for you...
cheers

Just take the update.app of b525, tear it apart with Huawei Extractor and flash boot cust system and recovery via fastboot.

Related

[NEED HELP]Phone stuck on "Warning:Bootloader Unlocked"...Urgent plz

Hey sombody plz help me to get through this,I installed the OTA then I unlocked bootlocker and installed the custom recovery twrp 2.8.7v2 ....then I tried to install the SuperSU....but after flashed it through twrp,I was stucked at "Warning Bootlocker Unlocked" screen for like 15 min,so then I tried to clear cache and then reboot....But that also not help,Then i tried format all the data and tried to to strt in factory mode.but still stucked at same screen.Now what should I do to get into the phone ?PLz ....its urgent
Well the thing you could do is factory resetting via TWRP or you could download a new ROM like CM 12.1 that you can find in the original android developer section and flash it with TWRP, your phone would boot up now. Keep in mind that you will lose everything.
anks095 said:
Hey sombody plz help me to get through this,I installed the OTA then I unlocked bootlocker and installed the custom recovery twrp 2.8.7v2 ....then I tried to install the SuperSU....but after flashed it through twrp,I was stucked at "Warning Bootlocker Unlocked" screen for like 15 min,so then I tried to clear cache and then reboot....But that also not help,Then i tried format all the data and tried to to strt in factory mode.but still stucked at same screen.Now what should I do to get into the phone ?PLz ....its urgent
Click to expand...
Click to collapse
The same happend to me, you must have installed the wrong SU version, just reflash stock firmware via fastboot and reinstall OTA, then if u wanna root use SuperSU v2.61, hope it helps.
Just flashed the CM12.1 through twrp ,problem is solved in a way.
anks095 said:
Just flashed the CM12.1 through twrp ,problem is solved in a way.
Click to expand...
Click to collapse
facing the same problem...... is flashing CM12.1 gonna solve it ?
praveen1618 said:
facing the same problem...... is flashing CM12.1 gonna solve it ?
Click to expand...
Click to collapse
It will but you should have unlocked bootloader.
praveen1618 said:
facing the same problem...... is flashing CM12.1 gonna solve it ?
Click to expand...
Click to collapse
unlock ur boot-loader first ,then flash cm through fastboot or if u have twrp then copy the cm zip in the sd card and then flash it through twrp.But remember to wipe the system,cache,dalvik cache and data.problem should be gone.
anks095 said:
unlock ur boot-loader first ,then flash cm through fastboot or if u have twrp then copy the cm zip in the sd card and then flash it through twrp.But remember to wipe the system,cache,dalvik cache and data.problem should be gone.
Click to expand...
Click to collapse
Sorry Noob question- when should I wipe the system,cache,dalvik cache and data ?? Before flashing cm 12.1??
And I am currently on mm rooted. And cm12.1 is based on lollypop, will there be any problem if I flash cm12.1?
bablu048 said:
Sorry Noob question- when should I wipe the system,cache,dalvik cache and data ?? Before flashing cm 12.1??
And I am currently on mm rooted. And cm12.1 is based on lollypop, will there be any problem if I flash cm12.1?
Click to expand...
Click to collapse
It will work fine.Backup your current system using twrp and then flash cm12.1.
bablu048 said:
Sorry Noob question- when should I wipe the system,cache,dalvik cache and data ?? Before flashing cm 12.1??
And I am currently on mm rooted. And cm12.1 is based on lollypop, will there be any problem if I flash cm12.1?
Click to expand...
Click to collapse
hope fully there would not be any problem....but in case of going wrong with something you should make a back up with twrp to go back to previous build,and yes ,before flashing any rom, you should wipe your cache ,dalvik cache and data......and system if u need...depends upon you
about moto x stucked while rooting
anks095 said:
Just flashed the CM12.1 through twrp ,problem is solved in a way.
Click to expand...
Click to collapse
i was trying to root moto x play i unlocked bootloader but when i tried to root my phone stuked in WARNING BOOTLOADER UNLOCKED.......... I TRIED WIPE ALL DATA FROM RECOVERY.... i tried some research someone said try to flash cm12.1 with twrp but i dont know hot to do this..... my mob is not connecting with pc plz help me guyz plz contect me at my gmail [email protected] its very urgent......plz tell me what to do step by step
sonubisht said:
i was trying to root moto x play i unlocked bootloader but when i tried to root my phone stuked in WARNING BOOTLOADER UNLOCKED.......... I TRIED WIPE ALL DATA FROM RECOVERY.... i tried some research someone said try to flash cm12.1 with twrp but i dont know hot to do this..... my mob is not connecting with pc plz help me guyz plz contect me at my gmail [email protected] its very urgent......plz tell me what to do step by step
Click to expand...
Click to collapse
first of all, which super su zip u r trying to flash ???? only this super su - "SuperSU-v2.62-3-20151211162651.zip" works on MXP...... after unlocking the boot loader u need to flash first twrp custom recovery...then entering into twrp interface,format the whole internal memory (I m sorry,u have to do that,no other way is possible)...... then put cm12 zip which u want to flash in sd card then flash the zip through twrp....... I guess this way your problem would be solved.....
If u flashed the correct mentioned supersu you should be fine.It happened 3 times also to me.I just press power continuously to power off and then it boots normally.
Please in case of SuperSU do not use 2.62-3 anymore, use 2.79SR3. Both are supposed to work, but 2.79SR3 is newer and has some bugfixes.
Note: The release 2.79 will not work, the detection fix to install systemless for all Moto devices is only integrated in 2.79SR3. 2.62-3 does no detection, it always installs systemless.
that was rom problm
mausv said:
Well the thing you could do is factory resetting via TWRP or you could download a new ROM like CM 12.1 that you can find in the original android developer section and flash it with TWRP, your phone would boot up now. Keep in mind that you will lose everything.
Click to expand...
Click to collapse
that was a rom problem
my phone is not turning on pls help after updating one ota of marshmallow security patch 1 jan
anks095 said:
Just flashed the CM12.1 through twrp ,problem is solved in a way.
Click to expand...
Click to collapse
Is cm12.1 support direct volte calling,.? Or any other custom rom which support volte calls???.

Moto X pure 6.0 stuck on logo

Rooted my Moto x pure 6.0 and is now stuck on motorola logo after trying to install supersu.
Nope, I didn't make a backup before I tried to install supersu.
I have access to recovery.
Is it possible to flash android 5.1 to my device?
Should I just try to flash another custom rom?
What happens if I do a factory reset ?
Thanks in advance.
Try 2.62-3
lafester said:
Try 2.62-3
Click to expand...
Click to collapse
??? 2.62-3 ???
tjs62 said:
??? 2.62-3 ???
Click to expand...
Click to collapse
supersu version 2.62-3
http://forum.xda-developers.com/app...arshmellow-t3219344/post64161125#post64161125
Thanks.....flashed it but still stuck on bootloader,but a little further on.
Instead being stuck on the M it now is stuck on the M with the stitching circling.
Wipe cache and flash latest su might fix it. Or full wipe and do 2.62-3 again.
lafester said:
Wipe cache and flash latest su might fix it. Or full wipe and do 2.62-3 again.
Click to expand...
Click to collapse
Thanks.
I did wipe cache and davlik cache before I installed 2.62-3 and that got a little further along in the boot process before it started to loop again.
When you say full wipe, your talking about a factory reset?
tjs62 said:
Thanks.
I did wipe cache and davlik cache before I installed 2.62-3 and that got a little further along in the boot process before it started to loop again.
When you say full wipe, your talking about a factory reset?
Click to expand...
Click to collapse
okay..try 2.62 version of supersu. This will work for sure.
HERE IS THE LINK
2.62-3 then flash any thing above that version.
1) Try 2.62-3 from*http://forum.xda-developers.com/apps...5#post64161125
2) Then flash with 3.67 from above.
http://forum.xda-developers.com/mot...mless-root-t3263405/post65691154#post65691154
Sent from XT1575, Stock 6.0 MM, Systemless root
amit.lohar said:
okay..try 2.62 version of supersu. This will work for sure.
HERE IS THE LINK
Click to expand...
Click to collapse
That did the trick.
Thanks to you and the other forum members who helped
Hitti2 said:
2.62-3 then flash any thing above that version.
1) Try 2.62-3 from*http://forum.xda-developers.com/apps...5#post64161125
2) Then flash with 3.67 from above.
http://forum.xda-developers.com/mot...mless-root-t3263405/post65691154#post65691154
Sent from XT1575, Stock 6.0 MM, Systemless root
Click to expand...
Click to collapse
Thanks
Got it working
what else did you do . I too am stuck with m and circle. I flashed 2.62. and nothing. am I missing something.
That worked! Thank you, thank you, thank you. My only other problem is that I can't get into TWRP without being connected to my PC via USB and running "fastboot boot recovery.img". Any ideas?
Edit: Apparently doing the fastboot command didn't permanently load TWRP onto the device. I found a solution on Google Play that worked.
Thank you Amit.lohar. It saved me after 5 days stuck with logo boot loop and ton of attemps flashing different firmwares & superSU versions
Sent from my SM-P600 using XDA Free mobile app
Will this get me root without losing wifi ? I've been at this all day and now I regret unlocking my bootloader etc

Please Help :(. Bootloop after re-flashing stock rom 6.0.1

Hello,
Please help me out guys
I tried for the 1st time to flash custom recovery TWRP - it worked.
Then, i immediately entered to TWRP and i tried to root my phone installing the supersu.zip. When i rebooted my phone - bootloop
In the end, I reflashed stock rom via ODIN but my phone still gets bootloop at SAMSUNG LOGO(NEVER HAPPENED BEFORE)
PS:If i try to enter stock recovery - first it appears "installing system update", then "no command" and then it enters the stock recovery, but nothing can solve the bootloop problem
please help
1.Why bootloop after rooting with the supersu.zip?Should i use the cfautoroot metod?
2.Why bootloop after reflashing stock rom?Never happened before!!!
Thanks!
What Phone have u got mate?
Sent from my Galaxy J5 using XDA Labs
J500F....
I think i managed to solve this...I was flashing the 1st update package .tar which was released for the J5 last summer
Flashing that - not working NOW, ALTHOUGH it worked a few months ago
Flashing .tar from SAMFIRMWARE - working!
But what about the root problem? Which way is the proper way to root your J500F 6.0.1 without bootloops&stuff
johnhux7 said:
What Phone have u got mate?
Sent from my Galaxy J5 using XDA Labs
Click to expand...
Click to collapse
Nothing works: supersu.zip, cf auto root.zip....
i only get bootloops
After flashing using TWRP you should always clear dalvik cache,
The first boot always take some time, 2-5 min,
Before flashing anything try to do a nandroid backup,
The supersu.zip method worked for me,
There is a detailed thread on xda j5 forum on how to upgrade/downgrade and root your device,
After using Odin to flash a ROM enter recovery and wipe data then wipe cache
Sent from my SM-J500H using XDA Labs
Update:
1. It seems it ONLY works to flash 6.0.1 AFTER flashing 5.1.1.(so i have to always repeat this double procedure)
Reflashing 6.0.1 over 6.0.1 - NOT WORKING
2. About root problem - damn, i still can't make it work. I will try your advices and let you know what happened,
Thanks!
saedlar93 said:
After flashing using TWRP you should always clear dalvik cache,
The first boot always take some time, 2-5 min,
Before flashing anything try to do a nandroid backup,
The supersu.zip method worked for me,
There is a detailed thread on xda j5 forum on how to upgrade/downgrade and root your device,
After using Odin to flash a ROM enter recovery and wipe data then wipe cache
Sent from my SM-J500H using XDA Labs
Click to expand...
Click to collapse
I just installed the Recovery then installed @zonik's performance ROM with all its files and my phone was rooted !
I'm using the J5FN
John
Sent from my Galaxy J5 using XDA Labs
Lawr3nce said:
Hello,
Please help me out guys
I tried for the 1st time to flash custom recovery TWRP - it worked.
Then, i immediately entered to TWRP and i tried to root my phone installing the supersu.zip. When i rebooted my phone - bootloop
In the end, I reflashed stock rom via ODIN but my phone still gets bootloop at SAMSUNG LOGO(NEVER HAPPENED BEFORE)
PS:If i try to enter stock recovery - first it appears "installing system update", then "no command" and then it enters the stock recovery, but nothing can solve the bootloop problem
please help
1.Why bootloop after rooting with the supersu.zip?Should i use the cfautoroot metod?
2.Why bootloop after reflashing stock rom?Never happened before!!!
Thanks!
Click to expand...
Click to collapse
I've seen your PM.
I don't really have any idea. But I have a suggestion, although I don't know if it will solve your problem. Backup your stuff from internal memory before. Try to wipe everything including internal memory (internalsd in TWRP recovery), then turn off your phone and re-flash stock rom.
Hello, @Lawr3nce I followed this tutorial by @rjrulz007 http://forum.xda-developers.com/galaxy-j5/how-to/tutorial-upgrade-j5-2015-to-6-0-t3443904 to root my j500h, I downloaded the supersu.zip from this link http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Don't forget to backup your data before upgrading (you can use smart switch), after flashing using Odin go to recovery (stock recovery), wipe data/factory reset and wipe cache partition, this should solve the boot loop problem.
Before flashing the supersu zip file do a nandroid backup using TWRP (boot to TRRP, choose backup, select sdcard as save location then swipe to start backup. In case the flash of zip file failed choose restore and select the backup you did before, better than reflashing the whole ROM using Odin )
Sent from my SM-J500H using XDA Labs
Ok, thank you all for the help. Conclusions:
1. For some reason, it NEVER works to flash directly the 6.0.1...I always have to flash the 5.1.1 first, then the 6.0.1.
2. I will try that root procedure from the link .
I am very willing to root it because i want to remove many useless preinstalled bloatwares from my phone
(due to very low free space i can't even update my apps)
UPDATE: That procedure with that .zip WORKS! THANKS

Mi A1 Bootloop please help

so I installed pie then i flash oreo back and after installing ota update my phone is in bootloop tries to flash many roms but no luck and i followed this tutorial https://forum.xda-developers.com/mi-a1/how-to/solution-bootloop-9-0-beta-t3876533 still no luck in the last step after flashing with mi flash still bootloop i dont even get android one logo please help me
Gattt said:
so I installed pie then i flash oreo back and after installing ota update my phone is in bootloop tries to flash many roms but no luck and i followed this tutorial https://forum.xda-developers.com/mi-a1/how-to/solution-bootloop-9-0-beta-t3876533 still no luck in the last step after flashing with mi flash still bootloop i dont even get android one logo please help me
Click to expand...
Click to collapse
my friend, you just go to fast boot mode and enter twrp through fastboot, do data cleaning, cache / delvik, system, internal memory, then from twrp, reboot Fastboot, after that you can flash rom stock cleanly from miflash tools.
DDPfisher said:
my friend, you just go to fast boot mode and enter twrp through fastboot, do data cleaning, cache / delvik, system, internal memory, then from twrp, reboot Fastboot, after that you can flash rom stock cleanly from miflash tools.
Click to expand...
Click to collapse
The problem is probably because of ARB, not because the partitions haven't been erased.

Bricked

So i was updating my Rom, Havoc OS, Same version, new patch
so i wiped the cache, Dalvik, and system and then installed it, then magisk stopped, and susbstratum stopped so all the apps patched I can't open, ok, i'll install magisk, but when i got to the substratum manager, it was empty, i tried using rescue my system failed, did nothing, and then i tried flashing the rescue me, nothing, and it just won't reboot now, and what's worse i can't access recovery, it's showing an empty battery even though i've been charging it and it will only go to fastboot, hell i tried wiping and factory resetting it trough fastboot it said failed
any help?
Rmdhn said:
So i was updating my Rom, Havoc OS, Same version, new patch
so i wiped the cache, Dalvik, and system and then installed it, then magisk stopped, and susbstratum stopped so all the apps patched I can't open, ok, i'll install magisk, but when i got to the substratum manager, it was empty, i tried using rescue my system failed, did nothing, and then i tried flashing the rescue me, nothing, and it just won't reboot now, and what's worse i can't access recovery, it's showing an empty battery even though i've been charging it and it will only go to fastboot, hell i tried wiping and factory resetting it trough fastboot it said failed
any help?
Click to expand...
Click to collapse
Install an official Rom with Flashtool
Enviado desde mi Redmi Note 7 mediante Tapatalk
Install a new recovery with fastboot flash tool.
Rangdrol said:
Install a new recovery with fastboot flash tool.
Click to expand...
Click to collapse
i tried installing a recovery via Fastboot but when i rebooted to recovery it went back to fastboot
Rmdhn said:
i tried installing a recovery via Fastboot but when i rebooted to recovery it went back to fastboot
Click to expand...
Click to collapse
Maybe bootloader locked?
Than trie mi flash tool. Flash the lastest official mi rom. Make sure that you flash the right rom for your device. I heard, there are problems, if you flash wrong one and downgrade. When flashing don't lock your bootloader again.
Wrong section!!!
Rangdrol said:
Maybe bootloader locked?
Than trie mi flash tool. Flash the lastest official mi rom. Make sure that you flash the right rom for your device. I heard, there are problems, if you flash wrong one and downgrade. When flashing don't lock your bootloader again.
Click to expand...
Click to collapse
My bootloader is unlocked, i reinstalled the custom recovery trough fastboot but it's still like this, i'll do this tommorow, i'm too tired of trying now
This should be on the Q/A thread. Not here.
Rmdhn said:
My bootloader is unlocked, i reinstalled the custom recovery trough fastboot but it's still like this, i'll do this tommorow, i'm too tired of trying now
Click to expand...
Click to collapse
Now you can flash the rom? If not, maybe this treat help you: https://forum.xda-developers.com/redmi-note-7/how-to/guide-steps-to-unbrick-redmi-note-7-t3922543
Also check the helpful post page 2.
Kagamihara said:
This should be on the Q/A thread. Not here.
Click to expand...
Click to collapse
Moved to Q&A section :good:

Categories

Resources