Hello,
I just flashed MM on my E2353, and then rooted it according to the instructions given here (http://forum.xda-developers.com/m4-aqua/general/root-t3421932) and it was successful. I then attempted to install Xposed for my device, which is the ARM64 version, and flashed it on TWRP, which gave it a bootloop, and I had to re-flash MM from Flashtool and etc. Any help is appreciated,
THANKS!
thes3usa said:
Hello,
I just flashed MM on my E2353, and then rooted it according to the instructions given here (http://forum.xda-developers.com/m4-aqua/general/root-t3421932) and it was successful. I then attempted to install Xposed for my device, which is the ARM64 version, and flashed it on TWRP, which gave it a bootloop, and I had to re-flash MM from Flashtool and etc. Any help is appreciated,
THANKS!
Click to expand...
Click to collapse
if After flash ARm64 Wiping Cashe And Dalvic Cashe You not Bootlooped, Wait 30min for Boot Your device. I Have it in E2333 MM And no Have problem
EHSAN™ said:
if After flash ARm64 Wiping Cashe And Dalvic Cashe You not Bootlooped, Wait 30min for Boot Your device. I Have it in E2333 MM And no Have problem
Click to expand...
Click to collapse
Thanks for the hint, I shall try flashing again via TWRP and clear Cache and Dalvik Cache.
**Update**
The device booted up after a strenuous boot, it heated up to 90C, and such, but nevertheless, it was successful, an Xposed is fully working on the E2353.
thes3usa said:
Thanks for the hint, I shall try flashing again via TWRP and clear Cache and Dalvik Cache.
**Update**
The device booted up after a strenuous boot, it heated up to 90C, and such, but nevertheless, it was successful, an Xposed is fully working on the E2353.
Click to expand...
Click to collapse
So what you did was only waiting 30 min. for the device to boot up? ´Cause I was trying the same thing and I thought it got stuck in the bootanimation
Memo537 said:
So what you did was only waiting 30 min. for the device to boot up? ´Cause I was trying the same thing and I thought it got stuck in the bootanimation
Click to expand...
Click to collapse
Go on Recovery and flash Xposed Framework, And Wipe Cashe and dalvic-cashe. Your Phone Boot on 10min that 30min.
Memo537 said:
So what you did was only waiting 30 min. for the device to boot up? ´Cause I was trying the same thing and I thought it got stuck in the bootanimation
Click to expand...
Click to collapse
Yes, it wasn't stuck in bootloop
Related
Sony Xperia Z2, locked bootloader, rooted SuperSU.
I was running MM but wanted to update my phone to latest Firmware .575 Marshmellow. Unfortunately, I made the rookie mistake of not making a backup because I was running low on space. Flashed, wiped cache/dalvik and then It went as far as home screen and then boot looped. I could only get into recovery TWRP.
Did a factory reset, clear cache/dalvik again. Nothing worked. Could only get as far as agreeing to terms screen and then boot loop.
Flashed an older firmware (.232) Lollipop that was pre rooted, same issue (don't know what I expected really)
Recovery is still there, I decided to just turn it off and ask someone because the internet is not giving me answers and I think I did enough damage. Please help!
Maybe too late, but..
What about when you wipe only cache and dalvik cache and flash again 575 zip and after that, flash bootloop fix, then restart phone to system from recovery menu?
Monipeev said:
Maybe too late, but..
What about when you wipe only cache and dalvik cache and flash again 575 zip and after that, flash bootloop fix, then restart phone to system from recovery menu?
Click to expand...
Click to collapse
I haven't tried the bootlop fix bit. I have tried this one though after going back to 570 and it still bootlooped. I'm back to 570 now.
Maybe a more stable flashable version will be revealed soon...one can only wait and see.
So, this is kinda weird and I don't know what's wrong...
I unlocked the bootloader by enabling the orm stuff in the developer settings and flashing a fastboot rom. Then I unlocked the bootloader and installed TWRP. After that I tried some roms (miui, cyanogenmods), but now I want to use the normal global developer version again. So what I did was reinstalling this rom which worked fine. Then I went back into TWRP to install SuperSU, but then I was unable to boot... Any ideas on how to fix this, or how to avoid the boot processing becoming stuck?
Thanks!
try clearing cache and devik cache if that dosent work try flashing this zip http://forum.xda-developers.com/attachment.php?attachmentid=3740290&d=1462390986
leave a THANK if it helped
filthyrich77 said:
try clearing cache and devik cache if that dosent work try flashing this zip http://forum.xda-developers.com/attachment.php?attachmentid=3740290&d=1462390986
leave a THANK if it helped
Click to expand...
Click to collapse
I had to use the boot.img in order to get it working. Thanks!
autCyrius said:
I had to use the boot.img in order to get it working. Thanks!
Click to expand...
Click to collapse
Used alla twrp, it was the simple way to flash official rom: http://en.miui.com/thread-282773-1-1.html?mobile=2
Sent from my Redmi Note 3 using Tapatalk
filthyrich77 said:
try clearing cache and devik cache if that dosent work try flashing this zip http://forum.xda-developers.com/attachment.php?attachmentid=3740290&d=1462390986
leave a THANK if it helped
Click to expand...
Click to collapse
I am also stuck in the same problem with my Redmi 4A. I unlocked the bootloader, installed cofface recovery then installed supersu 2.46 and my phone is stuck on mi logo. I have got this zip file but don't know how to flash it since I cannot start my phone normally so how would I put this zip file in my phone?
I have an unusual problem, in that my Moto Z always boots to TWRP. The only way to boot the ROM is first to boot bootloader and reboot bootloader a few times and then select Start. Any idea why and if there is something I can do?
lollyjay said:
I have an unusual problem, in that my Moto Z always boots to TWRP. The only way to boot the ROM is first to boot bootloader and reboot bootloader a few times and then select Start. Any idea why and if there is something I can do?
Click to expand...
Click to collapse
Try clearing cache
Manish54 said:
Try clearing cache
Click to expand...
Click to collapse
Yes I cleared both dalvik and cache and did not solve the problem.
I'd maybe flash twrp again (optional if twrp seems fine) and then dirty flash your rom again. (without any wipes first.)
If that fails, maybe only wipe system, and flash rom again.
Backing up with twrp before doing anything.
Assuming it's a custom rom. If it's stock, then you need to use fastboot obviously. (or mfastboot if that's what we use, I haven't done anything to my Z yet.) :good:
I finally solved the problem and solved it by reflashing stock ROM using fastboot. Then I could flash twrp again and then the custom ROM.
i installed twrp and lazyflash, then rebooted . everything was fine. Then i went back to recovery to install supersu.zip, I installed and then device rebooted... and then stuck at MI logo.. plz help, i am able to go back to twrp.
waiting for the reply
cutecrocodile said:
i installed twrp and lazyflash, then rebooted . everything was fine. Then i went back to recovery to install supersu.zip, I installed and then device rebooted... and then stuck at MI logo.. plz help, i am able to go back to twrp.
Click to expand...
Click to collapse
Flash lazyflasher again.
MyNameIsRage said:
Flash lazyflasher again.
Click to expand...
Click to collapse
checking
MyNameIsRage said:
Flash lazyflasher again.
Click to expand...
Click to collapse
still bootloop, stuck at Mi Logo
cutecrocodile said:
still bootloop, stuck at Mi Logo
Click to expand...
Click to collapse
Do you have a pc?
MyNameIsRage said:
Do you have a pc?
Click to expand...
Click to collapse
yes,
MyNameIsRage said:
Flash lazyflasher again.
Click to expand...
Click to collapse
can i factory reset it from twrp? if that solves my problem
cutecrocodile said:
can i factory reset it from twrp? if that solves my problem
Click to expand...
Click to collapse
You can actually flash a custom rom, and then revert back to miui, this would take time, but is much more easy, and has less chances to permanently brick your device.
MyNameIsRage said:
You can actually flash a custom rom, and then revert back to miui, this would take time, but is much more easy, and has less chances to permanently brick your device.
Click to expand...
Click to collapse
how to do it, i have already downloaded rr rom and cm 14.1
cutecrocodile said:
how to do it, i have already downloaded rr rom and cm 14.1
Click to expand...
Click to collapse
ok, so first of all what you need is the cm firmware and the rom file, and also gapps if u need.
this is the firmware file - https://androidfilehost.com/?fid=817550096634766008
Follow these steps -
1. Copy the firmware and rom file (and gapps if you have) to a place other than your phones internl storage like on an sd card or i you have a pc, then theres no problem, just leave the files on pc.
2. boot to twrp, here go to wipe and then select format data, here type yes and enter - this will wipe your internal storage. after that go back and wipe system, data, cache, dalvik.
3. now if you have a memory card inserted, with the rom files then skip this step, but if you do not,then connect your phone to pc using the data cable and copy the files to internal storage.
4. now firstly install the firmware,then the rom, and then any addons like gapps.
5. now reboot. you will boot to rr.
6. after booting, if you wish to install miui again, head to http://en.miui.com/download.html
and from there download the build you like, (choose redmi note 4x and there the global build)
7. now again boot to twrp, and format data, and wipe data, cache, system and dalvik. now copy the miui file, super su and the lazyflasher file.
8. install miui and lazyflasher, and reboot (it will say 'no os installed' but its fine, just reboot)
9. now after miui has booted, reboot to recovery, and install super su and lazyflasher, this should do it
thank you so much, i did it
super su should be installed first or lazy flash?
cutecrocodile said:
i installed twrp and lazyflash, then rebooted . everything was fine. Then i went back to recovery to install supersu.zip, I installed and then device rebooted... and then stuck at MI logo.. plz help, i am able to go back to twrp.
Click to expand...
Click to collapse
You have to clear dalvik/art cache after flashing supersu.zip and restart. It will boot loop one time and on second time the phone will successfully boot. Now flash lazyflasher and follow the steps again.
Hello,
I need some suggestion,
I have installed AOSPExtented and after a vendor upgrade i cant boot on any rom.
Tried AOSP, PixelEx, LineageOS..
Clean instal, dirty install, fastboot format userdata/cache
Every single one get stuck on boot animation (most i waited was 1 hour)
Any idea how to fix?
Ty
If you had installed magisk, try unistalling magisk from recovery.
Try clean flash for any rom, meaning wipe cache, dalvik cache, data and system.
This should resolve boot loop.
Amarjeet28 said:
If you had installed magisk, try unistalling magisk from recovery.
Try clean flash for any rom, meaning wipe cache, dalvik cache, data and system.
This should resolve boot loop.
Click to expand...
Click to collapse
Tried all that, nothing worked.
The solution was flash DisableEncryption as last flash..
Dont know why, Never needed this, but well, now everything is ok. Ty
hi i have install pixel os in poco f1 i have an mobile data issue