Hi,
I clean flashed CM12.1 official and it was working, except the in call speaker. Somebody on another thread mentioned that I need to flash stock modem for it to work. So I downloaded the stock modem 5.1 and flashed it using `fastboot flash modem` and `fastboot flash fsg`. And now I'm stuck at bootloop. Any idea how to fix this?
If this was a stupid mistake, please do tell. I couldn't find any proper solution for the in-call speaker issue, which led me to this.
Related
I'm currently on CloudyG2 2.2, I tried to flash several lollipop roms(XenonHD, Blisspop, CM12, Crdroid, etc) always following the instructions and changing the modem or bootstack when necessary and always get the same error "Error executing updater binary in zip", even when flashing KK aosp roms
However when I try to flash a stock rom it gets installed without issues
I've restored 26A KDZ and the problem persists, I'm on bumped TWRP 2.8.6.1
Hope you can help me,
Thanks
anyone?
Try using a non bumped recovery.
You'd need to flash the 12B bootloader, its loki'd. Check Xdabebb's sticky, you'll find it there.
Dork6243 said:
You'd need to flash the 12B bootloader, its loki'd. Check Xdabebb's sticky, you'll find it there.
Click to expand...
Click to collapse
I tried that and I can now flash aosp roms without getting the error,
now whenever I install a custom rom I get stucked in boot animation, again, always flashing and downgrading modem/bootstack when necessary.
Thanks
So last time my phone was stuck on the device name and model number screen. I solved that issue by flashing TWRP using Odin.
but now the phone would not go past the boot screen no matter what I do. I re-flashed CM11 4 times now, factory reseted and wipe cache and dalvik cache. What should I do?
1. change your thread title please. Need help is not really helpful or directs to your issue.
2. what version of TWRP are you using? The official TWRP 2.8.7.0 does not work. Too long to explain why's that. To fix this issue there are some solutions if you flashed the faulty recovery:
- flash Stock ROM again and stay on TWRP 2.8.5.0
- some users fixed this issue by just flashing another recovery or just flashing a stock based custom rom to get their phone working. You still need to change recovery.
In my case I had to flash stock again and flash my preferred recovery again to get my phone working.
maultasche said:
1. change your thread title please. Need help is not really helpful or directs to your issue.
2. what version of TWRP are you using? The official TWRP 2.8.7.0 does not work. Too long to explain why's that. To fix this issue there are some solutions if you flashed the faulty recovery:
- flash Stock ROM again and stay on TWRP 2.8.5.0
- some users fixed this issue by just flashing another recovery or just flashing a stock based custom rom to get their phone working. You still need to change recovery.
In my case I had to flash stock again and flash my preferred recovery again to get my phone working.
Click to expand...
Click to collapse
So I should flash TWRP 2.8.5.0 and flash CM11 again? (because I don't have stock rom for S3 LTE)
Where can I get stock rom fro S3 LTE I can't seem to find it all, I find is firmwares.
Also, a few questions
1) If I give it into my phone carrier (Optus) would they know that it is rooted?
2) If they know it is rooted and with a custom rom and don't fix it for free is it possible to get it fixed by paying money??
The firmware provided by Samsung is the stock ROM I'm talking about
No, since you tried to flash a ROM through the faulty recovery you need to flash either official firmware from Samsung or a custom ROM based on Samsung stock like AMCHA or N4 Elite. I'd recommend to go with official Samsung firmware. After that go to stock recovery (it will come when you flash official firmware), do a factory reset and let the phone boot once. After that you can flash TWRP 2.8.5.0 and flash any ROM you want.
The new recovery from TWRP is too big for the S3. The S3 recovery is a little over 8MB, the new one needs more and messes up partitions etc. You won't be able to mount /system, /data and the recovery can't read your internal partitions as it should. Go with the way I provided. It seems like a lot of work but it's done in a few minutes.
For your two questions: yes and yes. But you can fix that on your own and don't need your operator or Samsung to get your phone fixed.
Thanks a lot for helping. I was scared to death cause if something happened I would've had to start using a old brick Nokia phones
Is it possible that after I flash the stock firmware, my phone still doesn't boot up?
I am basically a level above newbie, so I don't get what is happening. I see tutorials and do what they tell me to do. sometime I get what I am doing sometime I don't
as i said, after flashing stock, go into the recovery and do a factory reset. The phone will boot then
maultasche said:
as i said, after flashing stock, go into the recovery and do a factory reset. The phone will boot then
Click to expand...
Click to collapse
Ok sorry for doubting you! My phone is working now, thanks a lot for your help
Glad it's working now, you're welcome
I have rooted my s3 via odin and now i wont to flash twrp via flashify. Now i have a bootloop on my s3. How can i recover the phone. i am a noob on s3 and i don*t know how i could go into fastbootmode. Please help me.
what S3 do you have? Which recovery did you flash?
maultasche said:
2. what version of TWRP are you using? The official TWRP 2.8.7.0 does not work. Too long to explain why's that. To fix this issue there are some solutions if you flashed the faulty recovery:
- flash Stock ROM again and stay on TWRP 2.8.5.0
- some users fixed this issue by just flashing another recovery or just flashing a stock based custom rom to get their phone working. You still need to change recovery.
In my case I had to flash stock again and flash my preferred recovery again to get my phone working.
Click to expand...
Click to collapse
I had this problem too! Flashed stock rom, then flashed TWRP 2.8.5.0 (I was using 2.8.7.0) and then flashed cyanogenmod 12 and boom it booted and worked!
Thank you very much!
Hello,
first post, trust I did not miss aynthing.
Bought a cheap used SM-T810N as "damaged" believing it is a software problem and I can fix it.
Flashed everything I found (Lollipo, Marshmallow, CM, TWRP recovery, etc.)
Tablet stucks at Samsung Logo and shows some strange color effects (lines, artefacts) but screen works fine in Recovery, TWRP, etc.
Anyone any idea how to identify the real problem?
Thanks a lot, you all are doing a great job here.
DaWool
wool242 said:
Hello,
first post, trust I did not miss aynthing.
Bought a cheap used SM-T810N as "damaged" believing it is a software problem and I can fix it.
Flashed everything I found (Lollipo, Marshmallow, CM, TWRP recovery, etc.)
Tablet stucks at Samsung Logo and shows some strange color effects (lines, artefacts) but screen works fine in Recovery, TWRP, etc.
Anyone any idea how to identify the real problem?
Thanks a lot, you all are doing a great job here.
DaWool
Click to expand...
Click to collapse
Have you tried a full wipe before using Odin to flash a ROM? Including the data partition? Or tried booting to "download" instead of TWRP to use Odin?
edit: And you do need to use Odin to get things working before trying to flash anything via TWRP.
Seems like a mismatched bootloader and kernel issue to me.
Flashing stock firmware with ODIN should fix it if it is.
lewmur said:
Have you tried a full wipe before using Odin to flash a ROM? Including the data partition? Or tried booting to "download" instead of TWRP to use Odin?
edit: And you do need to use Odin to get things working before trying to flash anything via TWRP.
Click to expand...
Click to collapse
Tried both, Odin and flashing from recovery... Even different Odin versions
Hi, Dear xda members
Last week i soft bricked my Sony Xperia Z c6603
After flashing modified kernel, i lost everything
I couldn't reach recovery even couldn't flash one with fastboot(as my device was not recognized)
I tried flashing offcial firmware through flashtool. It succeeded flashing
But After reboot i had bootloob and the ROM didn't boot
Finally I had a solution to get my phone fixed. Here's what i did:
*Reboot to FlashMode
*In flashtool I flashed TWRP Recovery in FlashMode
Now all custom ROMs are working but when I flash an official and other ROM's based on official, I'm having bootloops
Tried to wait. NO result
Could you help me with it?
P.S the modified kernel was made by this tool http://forum.xda-developers.com/xpe...ot-automatic-repack-stock-kernel-dm-t3301605/
When i softbricked my phone I tried to fix it according to this guide http://forum.xda-developers.com/xpe...rick-sony-xperia-z-c6602-c6603-c6606-t3215134
after i flashed the cm rom, i got the same problem. after flash the stock ROM or official firmware, It keep bootloop. how you fixed It ?
315cqab said:
after i flashed the cm rom, i got the same problem. after flash the stock ROM or official firmware, It keep bootloop. how you fixed It ?
Click to expand...
Click to collapse
Do you still need the method i have gone through?
do you know how to flash the official ROM or firmware back? now i can only flash the custom ROM
315cqab said:
do you know how to flash the official ROM or firmware back? now i can only flash the custom ROM
Click to expand...
Click to collapse
Sorry even i need this. Currently i have the same problem. I cant flash official firmware or the one that is based on official. I need the solution
Same here, after install CM 14.1, i can't go back to official or rom based in Stock...
gussbravo said:
Same here, after install CM 14.1, i can't go back to official or rom based in Stock...
Click to expand...
Click to collapse
I have several problems too including not being able to run stock anymore. (endless black screen after experia logo). I tried flashtool (latest stock via xperifirm), Sony's flashtool. Companion didn't even want to flash (UEGetPhoneInfoMissingInfo), and left me wondering wether something is corrupt.
I've been running CM's for a while now and was wondering why NFC was not working. Not sure if it needs an updated firmware or what.
Other problem I've seen is that "fastboot flash recovery" always gives an error. "fastboot flash boot" works (this is how I install TWRP).
Can I try zeroing mmcblk0 or would that brick it? (does it really need to have a TA partition to accept boot connection? How does Sony init it anyways?)
I think I have a mmcblk0 backup from after unlocking (DRM lost though) but perhaps that will give me a somewhat clean situation again. Or perhaps I can compare it.
Edit: dd-ed my old mmc backup and now Xperia Companion didn't give an error anymore, did a factory reset, and after a long wait of the blue waving animation, I got it to work.
Even NFC firmware update started after rooting and deleting /data/ucf folder.
Now I want to go back to Nougat xD
I reflashed stock after a TWRP backup sent me into a bootloop and now my phone can't recognize the SIM or connect to Wifi. Can somebody please help?
Edit: I'm not sure why this worked, but I fixed this by trying to flash the Havoc custom ROM. The ROM wouldn't boot, but when I reflashed stock afterwards, the problem was fixed.
was your imei intact before you reflashed back to stock
enzodad said:
was your imei intact before you reflashed back to stock
Click to expand...
Click to collapse
I'm not sure if you're referring to when I reflashed stock and had problems or when I reflashed stock after trying to flash Havoc and fixed it. I can't answer either way because both times I reflashed I was stuck in a bootloop, so I couldn't check the IMEI.
hey guys i got stuck in the same problem but after flashing an android one stock rom i got back working my wifi and sim card, but now i'm stuck on this dead rom, if i try to flash another stock rom again ihte same issue happens, if i try custom doesn't boot, so i don't have a clue of what to do can someone give me some tip about it?
marken said:
hey guys i got stuck in the same problem but after flashing an android one stock rom i got back working my wifi and sim card, but now i'm stuck on this dead rom, if i try to flash another stock rom again ihte same issue happens, if i try custom doesn't boot, so i don't have a clue of what to do can someone give me some tip about it?
Click to expand...
Click to collapse
Since everything works when you have the Android One ROM installed, try backing up the EFS with that ROM installed and restoring on the ROM you want to use.
No wifi after flashing ROM
I had the same thing happen after flashing a ROM. In my case, it was a repeatable error. I reflashed the modem partition from the stock modem after flashing the custom ROM and everything started working again.
doodalydoo said:
Since everything works when you have the Android One ROM installed, try backing up the EFS with that ROM installed and restoring on the ROM you want to use.
Click to expand...
Click to collapse
Thanks for answering!
i've tried that before, always get stuck on boot on any rom and if iflash stock i lose again connections