As title says, im getting bootloops after i try to flash dotzi75 deodexer.
My M2 is the correct version in case someone might think asking, D2303 FW 18.3.C.0.40
I tried everything, wiping cache,dalvik,factory reset, i tried flashing over clean firmware over and over again
erased and formated sd for no reason but what the hell.
I tried with root and without root.
Currently when i try to flash Deodex with CWM, after reboot sony/xperia logos load quite slow then it stuck at the floating blue wave screen.
After i try rebooting again and enter recovery, it just doesnt work, so i have to flash it again, but its not helpful anyway. I think something is wrong with the CWM version itself.
I tried to flash the prerooted FW with CWM but CWM failed to do so.
Anyone having similar problems and/or solutions ?
Related
Hi guys!
Yesterday I successfully rooted my NS (it is a European SLCD model with stock 2.3.6 on it) following the newest guide on nexusshacks.com. So I ended up with TWRP recovery.
Then I thought the easiest to install CM is via Rom Manager. Therefore I had to change recovery for CWM. (I flashed the latest one.)
And here comes my question: why am I unable to flash CM?
First I tried it in Rom Manager, after wiping everything and rebooting system nothing happens, except for a big yellow exclamation mark.
Then I downloaded the proper CM myself and I tried to do the whole process manually in recovery menu. After wiping and choosing update from SD card I get a message like the process is aborted.
I also tried with an older CWM and with other ROM.
Any suggestions?
Thanks a lot
Sent from my Nexus S using XDA App
Boot into bootloader, then flash recovery via fastboot.
fastboot flash recovery recovery.img
stock firmware will rewrite your recovery after each boot. flash recovery then flash this right after.
Follow what SEAN SAys..............He is a Master in all these , and he helped me with details to root, flash cwm, make it sticky and flash custom ROMS.
It took me 5 minutes to do all those , and Now I am switching Roms like I switch my underwears every day twice.
I must say, Sean has the best possible way which is like a finger click.
So in the process of updating my rom, I managed to damage my /data/ partition, meaning I now have no ROM on my phone. I've updated TWRP to the newest version, I've got a stock firmware on file and a custom firmware if needed, both CWM and TWP on file, I've tried flashing or running all of the above but I can't get anything to actually load to the phone. I've also tried loading a rom via USB-OTG but I can't get it to mount. Normally in this situation I'd run an odin update for the stock firmware but I can't find anything about that, and all the brick threads in XDA don't seem to be helping. Does anyone have some suggestions?
Edit: I do have fastboot access but no ADB. Sideload isn't working through TWRP and I don't know why.
You have to return to stock using flash boot... It happened to me as well...
Well, I tried http://forum.xda-developers.com/showthread.php?t=2542219 and now I'm looking at the "warning: unlocked bootloader" screen...
Hi,
Just for you to know:
Model: r7plusf
Recovery: TWRP 3.0.2-0
----------------------------------------
So earlier today I did an OTA update (cm-14.1-20161205-NIGHTLY-r7plus.zip), but couldn't get my phone to boot.
So naturally, I tried wiping Cache and ART cache, but was still bootlooping.
Thought there might be someting wrong with my ROM and data, so I formated data and Installed ROM and GAPPS again after ADB pushing them onto my phone.
Now, and although CM14.1 and GAPPS are successfully installed on my Oppo R7 Plus, I can't boot into the OS. Every time I try reboot system, whether through POWER_BUTTON, RECOVERY or ADB, I just boot into Recovery.
Worst of all, for some unknown reason, I can't get into BOOTLOADER, neither through button combination, nor through Recovery nor ADB.
I found this article (http://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386) in the LG G3 thread about executing some shell commands, but I haven't tested testing it with my phone's variables because it might hard brick it...
Please Help!
[EDIT] I now have access to fastboot but still recovery looping like crazy.
I installed the same update via CyanDelta , worked like a charm ! hopefully you get back up and running.
[UPDATE] strangely I tried to flash stock recovery and boot CM13 and it worked!
Will try to flash twrp again and insall CM14
keep you up to date
Same thing happened to me! Where did you get a copy of the stock recovery? Link?
resverse said:
[UPDATE] strangely I tried to flash stock recovery and boot CM13 and it worked!
Will try to flash twrp again and insall CM14
keep you up to date
Click to expand...
Click to collapse
I had the same problem. Can't remember exactly how I resolved it. But I think, I use CM recovery to flash nightly. Then flash TWRP to flash gapps. For some strange reason, using CM recovery also show no enough disk space whenever I try to flash opengapps. But TWRP recovery can flash opengapps successfully.
Don't use the OTA, use adb sideload to flash the nightly next time. So far, adb sideload has not given me any issue to flash nightly.
Same problem...
I tried a lot of things nothing works and now I've installed the cm recovery but I have the "unauthorized phone" in terminal when I try to flash the ROM... I can do nothing because I can't enable the usb debugging. I don't know what to do.
If somebody can help I appreciate.
corbalan12 said:
Same problem...
I tried a lot of things nothing works and now I've installed the cm recovery but I have the "unauthorized phone" in terminal when I try to flash the ROM... I can do nothing because I can't enable the usb debugging. I don't know what to do.
If somebody can help I appreciate.
Click to expand...
Click to collapse
Since then I found how to fix it :
first of all I flashed cm13 through TWRP,
Then I flashed the stock recovery (Google it, I found it in OPPO forums) with fastboot,
After that I did a factory reset in the stock recovery,
Booted cm13 with stock recovery,
Then re-flashed TWRP,
From TWRP, I wiped both data and system partitions,
Then fresh installed cm14 and Gapps
And it worked!
Not sure if those are the exact steps I followed because all I did was a hole lot of messing around and trying absurd things out, but think this is how I fixed it.
Let me know if it worked for you or if you still can't fix your problem
Best of luck
Resverse
resverse said:
Since then I found how to fix it :
first of all I flashed cm13 through TWRP,
Then I flashed the stock recovery (Google it, I found it in OPPO forums) with fastboot,
After that I did a factory reset in the stock recovery,
Booted cm13 with stock recovery,
Then re-flashed TWRP,
From TWRP, I wiped both data and system partitions,
Then fresh installed cm14 and Gapps
And it worked!
Not sure if those are the exact steps I followed because all I did was a hole lot of messing around and trying absurd things out, but think this is how I fixed it.
Let me know if it worked for you or if you still can't fix your problem
Best of luck
Resverse
Click to expand...
Click to collapse
Thank you very much!!!! I'll try tomorrow and tell you.
I appreciate a lot!
First of all now works but to be honest, I don't know if the way I fix makes sense or if is correct but not for the same reason I do but I'll try to explain...
I had cm-14.1-20161218-NIGHTLY and I tried to update via OTA to 20161220 the phone reboot and I get the bootloop. The first I thought, install again the ROM making wipe data and blabla... nothing work.
I tried to "reflash" the recovery, nothing. Flashed cm recovery, it always gave me error trying to flash the rom. I tried to install with stock recovery, errors too.
I was reading hundred of post looking for my issues, device unauthorized, "error 7" in twrp... I was crazy.
At last I thought, I've been trying to install from SDcard, if I try to install from internal memory? and I install again the twrp to transfer the ROM and Gapps to the internal memory and... it worked!!!!
Long story but with happy ending.
Thank you for your help I appreciate and sorry for my english.First of all now works but to be honest, I don't know if the way I fix makes sense or if is correct but not for the same reason I do but I'll try to explain...
I had cm-14.1-20161218-NIGHTLY and I tried to update via OTA to 20161220 the phone reboot and I get the bootloop. The first I thought, install again the ROM making wipe data and blabla... nothing work.
I tried to "reflash" the recovery, nothing. Flashed cm recovery, it always gave me error trying to flash the rom. I tried to install with stock recovery, errors too.
I was reading hundred of post looking for my issues, device unauthorized, "error 7" in twrp... I was crazy.
At last I thought, I've been trying to install from SDcard, if I try to install from internal memory? and I install again the twrp to transfer the ROM and Gapps to the internal memory and... it worked!!!!
Long story but with happy ending.
Thank you for your help I appreciate and sorry for my english.
Got my new XZP yesterday, unlocked it fine. But Im a dumbass and WIPED THE WHOLE THING so there's No OS. No matter how many times I try to Wipe it and Flash TWRP it Won't boot into TWRP. It won't even give me a Sony Logo. It only gives me the "Your device is unlocked - Boot in 5 seconds " message and then Endlessly will do that. I can't boot into recovery. I need to know if there's a way to remedy this I'm desperate as hell cause I rooted my Xperia X just fine. I even used Newflasher to flash a new updated Stock ROM to it. Seemed to work fine, still wouldn't give me a Sony Logo or Boot into recovery.
PLEASE HELP!!! Edit: I re flashed just a system .sin and that allowed me to get back into TWRP. I still have no clue why flashing a ROM didn't work. But I have TWRP and an SD Card.
CRIMNALSNEAK said:
Got my new XZP yesterday, unlocked it fine. But Im a dumbass and WIPED THE WHOLE THING so there's No OS. No matter how many times I try to Wipe it and Flash TWRP it Won't boot into TWRP. It won't even give me a Sony Logo. It only gives me the "Your device is unlocked - Boot in 5 seconds " message and then Endlessly will do that. I can't boot into recovery. I need to know if there's a way to remedy this I'm desperate as hell cause I rooted my Xperia X just fine. I even used Newflasher to flash a new updated Stock ROM to it. Seemed to work fine, still wouldn't give me a Sony Logo or Boot into recovery.
PLEASE HELP!!! Edit: I re flashed just a system .sin and that allowed me to get back into TWRP. I still have no clue why flashing a ROM didn't work. But I have TWRP and an SD Card.
Click to expand...
Click to collapse
that is very very interesting... did you try flashtool and flash older android version?
Can you boot into Fastboot and flash a valid rom via newflasher?
It could be possible, that in fastboot the screen is still dark
Hello, some days ago i found a Samsung Galaxy Ace Style (SM-G310HN/heatnfc3g) and i decided to mod it, i installed TWRP via Odin and all was ok, but when i tried to install CyanogenMod 12.1 it didn't work. Since it didn't work, i decided to flash stock ROM. It worked once, but now it doesn't work anymore. I suspect it's the PIT file, because when i reflashed stock ROM another time with a PIT file now it doesn't work anymore, let me try to explain:
When i try to flash anything (Stock ROM or recovery, custom or stock), it... doesn't, Odin says it flashed but when i reboot to recovery or reboot to stock, it stays at the Samsung logo or doesn't flash the recovery, even if it says that it flashed. What should i do? Is my phone bricked? How can i unbrick it if it's bricked?
Michy234 said:
Hello, some days ago i found a Samsung Galaxy Ace Style (SM-G310HN/heatnfc3g) and i decided to mod it, i installed TWRP via Odin and all was ok, but when i tried to install CyanogenMod 12.1 it didn't work. Since it didn't work, i decided to flash stock ROM. It worked once, but now it doesn't work anymore. I suspect it's the PIT file, because when i reflashed stock ROM another time with a PIT file now it doesn't work anymore, let me try to explain:
When i try to flash anything (Stock ROM or recovery, custom or stock), it... doesn't, Odin says it flashed but when i reboot to recovery or reboot to stock, it stays at the Samsung logo or doesn't flash the recovery, even if it says that it flashed. What should i do? Is my phone bricked? How can i unbrick it if it's bricked?
Click to expand...
Click to collapse
Have you tried booting into stock recovery and selecting the factory reset option and the wipe cache partition option? It is sometimes necessary after flashing via Odin, I've had to do it a few times to solve a bootloop.
Droidriven said:
Have you tried booting into stock recovery and selecting the factory reset option and the wipe cache partition option? It is sometimes necessary after flashing via Odin, I've had to do it a few times to solve a bootloop.
Click to expand...
Click to collapse
Well the problem is... i cant reboot into stock recovery. Its stuck in twrp, and it's not really a "bootloop", it stays stuck at the Samsung logo. I tried to wipe cache and dalvik on Twrp but nothing.
I cant even flash the stock recovery since as i said in the original post, if i try to flash EVERYTHING Odin says it flashed but on the phone nothing happened.
Michy234 said:
Well the problem is... i cant reboot into stock recovery. Its stuck in twrp, and it's not really a "bootloop", it stays stuck at the Samsung logo. I tried to wipe cache and dalvik on Twrp but nothing.
I cant even flash the stock recovery since as i said in the original post, if i try to flash EVERYTHING Odin says it flashed but on the phone nothing happened.
Click to expand...
Click to collapse
Could please someone help me?
Michy234 said:
Could please someone help me?
Click to expand...
Click to collapse
I revive this post even if its pretty old. Could someone please help?