Hey,
they title says it. With f2fl everything boots just fine.
Im still on Murshmellow 6.0.1.
For some odd reason i cant update in the OS settings. First it downloads and reboots, but while installing it stops at 24% every time. "install failed"
A solution for that would be cool as well.
Flashing the Update manually also results in a bootloop.
No root but i'd wish to have one.
Thanks
Related
I should mention that this phone is not mine and it was brought to me to fix. It could not get past the samsung bootup animation screen.
So I installed TWRP 2.8.6.0 and wiped everything. Then the first rom I flashed was [ROM][5.1.1][AOSPA] ParanoidAndroid 5.1 (5/21/2015) Then flashed gapps 5-22-15 from euroskank/banks. I wiped dalvik & cache (Is this necessary?) and rebooted.
The intro screen did not let me skip the wifi connecting part (I thought it was a bug in that version) and it told me to turn on wi-fi to connect.
So I tried the same thing with the version before that and it let me skip. After that I managed to turn it on once? But it the phone crashed and soft rebooted.
I tried other 5.1 roms and the wifi doesn't work still. It doesn't let me turn it on. Same with 4.4.4 with cm11. Also, the Wi-Fi MAC address says unavailable. Don't think that's supposed to happen?
Does anyone have a fix?
Edit: I took out the SIM card to see if that did anything. Then all of a sudden the grayed out On button turned blue and wifi networks appeared... But I couldn't do anything else since it made me restart. It stopped working after a reboot :/ Tried it several more times and couldn't get it to do the same thing..
stevenx37 said:
I should mention that this phone is not mine and it was brought to me to fix. It could not get past the samsung bootup animation screen.
So I installed TWRP 2.8.6.0 and wiped everything. Then the first rom I flashed was [ROM][5.1.1][AOSPA] ParanoidAndroid 5.1 (5/21/2015) Then flashed gapps 5-22-15 from euroskank/banks. I wiped dalvik & cache (Is this necessary?) and rebooted.
The intro screen did not let me skip the wifi connecting part (I thought it was a bug in that version) and it told me to turn on wi-fi to connect.
So I tried the same thing with the version before that and it let me skip. After that I managed to turn it on once? But it the phone crashed and soft rebooted.
I tried other 5.1 roms and the wifi doesn't work still. It doesn't let me turn it on. Same with 4.4.4 with cm11. Also, the Wi-Fi MAC address says unavailable. Don't think that's supposed to happen?
Does anyone have a fix?
Edit: I took out the SIM card to see if that did anything. Then all of a sudden the grayed out On button turned blue and wifi networks appeared... But I couldn't do anything else since it made me restart. It stopped working after a reboot :/ Tried it several more times and couldn't get it to do the same thing..
Click to expand...
Click to collapse
Hope you had read the posts, it should had said the Rom is not "stable"
If your friend are going use their phone for daily driver, then I recommend you not have the 5.1 Roms for now because it's not really suitable for that right now.....
I'm not sure the CM11 you have flashed is unoffical or is offical. Offical onces are still work in progress and have most of the things broke (I think)
Here is a Kitkat Rom for SGH-T989
If your friend really wanted to have a Lollipop running on his/her phone, then I will recommend this one. Make sure you read the instruction CAREFULLY if you do wanted to install this one since it's a bit complicated with it's "virtual partition"
Or, if you wanted it to be just stock. Odin it back to normal, here is a instruction (with video too).
This is all the possible way to fix your friend's phone that I can think of, if you have encounter any error or have anymore question, feel free to reply :fingers-crossed::good::highfive:
P.S: yes, wiping dalvik & cache is a way to prevent any error caused by another old Rom if you decided to flash a new one. It's a good way to prevent error during Rom flash process
Thanks! I'll try the 4.4.4 rom you sent me. I'll post an update when I get to it.
Uh and about the 5.1 you linked. For the virtual repartition part in his post, I couldn't open the phone's internal storage on the computer after formatting it to ext4. So I'm confused about that step.
stevenx37 said:
Thanks! I'll try the 4.4.4 rom you sent me. I'll post an update when I get to it.
Uh and about the 5.1 you linked. For the virtual repartition part in his post, I couldn't open the phone's internal storage on the computer after formatting it to ext4. So I'm confused about that step.
Click to expand...
Click to collapse
For the virtual partition, it's best for you to have it on the External SD card. Since TWRP transporting file to Internal Storage after that seems bugged (not working)
I've been trying to update my firmware all day, I'm running TWRP2.8.7.2, updated to the newest bootloader, and tried 6 different ROMs, nothing will boot, except the alpha AOSP Marshmallow, but with that play services keeps crashing as soon as I try to set up my google account, and I can't get past the first run wizard. I've wiped my cache and data and internal storage a couple times now, and nothing is working. could someone give me an idea? I've never had so much trouble flashing a device before.
try going back to 100% stock by flashing stock firmware on ODIN. Next root and twrp.
sarreq said:
I've been trying to update my firmware all day, I'm running TWRP2.8.7.2, updated to the newest bootloader, and tried 6 different ROMs, nothing will boot, except the alpha AOSP Marshmallow, but with that play services keeps crashing as soon as I try to set up my google account, and I can't get past the first run wizard. I've wiped my cache and data and internal storage a couple times now, and nothing is working. could someone give me an idea? I've never had so much trouble flashing a device before.
Click to expand...
Click to collapse
I have a t700 and had the same problems you have installing marshmallow. What worked for me was advanced wipe in twrp, everything except internal storage and sd card. From there hit the home key, and flash the marshmallow rom, then reboot into recovery, next flash su 2.5x, then reboot into recovery. Lastly, flash the benzo gapps, and reboot system. My play store started working after i installed in that sequence on t700. Ive heard a few others have had to do that process 2 or 3x before it works, and some, it doesnt work at all. Worth a try though. Good luck.
Hello,
I'm having a weird issue with my Note 7 that I didn't have at all until tried to root for the first time....
It randomly restarts, sometimes is very often and sometimes it take a few hours to do it, but when it does it just restarts out of nothing and when Android loads again it asks me for a password that doesn't even exsits
"To start your device, enter your password" (Picture attached)
This started to happen after used the rootable kernel that was published before SuperSU 2.77 Beta but even reflashing the stock firmware, bootloader, modem, CSC it keeps doing it even when my Android is not yet configured (at the first Welcome screen before setting the phone up), so there is no password at all at this point. I've tried my Google account password, but it doesn't work.
This message is the same that comes up when you select "Secure Boot" so you need to enter a password or PIN to decrypt your data and be able to load it, but I don't have that option checked, and could not be checked when the phone is not even configured.
The way to work around this issue is flashing the no-verity-opt-encrypt mod that is not supposed to be needed anymore after SuperSU 2.77 has been released. So flashing this mod will get me into my Android home screen but it will eventually restart again and I need to flash this mod again.
This is what I've tried so far and it keeps happening:
- Flashed the rootable kernel when it was published and the no-verity mod. I formated data as indicated in the post. Then this problem appeared.
- Flashed stock firmware, bootloader, modem, csc thinking this would remove any trace of the mods I flashed, but kept happening.
- Factory reset from the Samsung recovery, had the "no verity" errors sometimes and sometimes not.
- Flashed other firmwares, bootloaders, modems, csc from other countries but for the same model N930F and kept happening.
- Flashed custom ROMs, formated system, data, everything.
- Flashed stock firmware again.
- Flashed custom ROMS again with the new SuperSU 2.77 and keeps happening.
I have done every single flash that actually exists for the Note 7 and formated everything with no luck....
Has anyone have this issue or had it at all at some moment? If so... How did you manage to get rid of this message?
I hope someone can help, If it was faulty phone I think it would restart at any point even in Recovery or Download mode, but only happens inside of Android.
Seems a common problem I think?
http://forum.xda-developers.com/showthread.php?t=3444510
Sent from my Nexus 6P using Tapatalk
Yep, saw that post... But never seen anyone complaining about the phone asking for a password when reboots (only when it crashes) its like it was asking for a password to decrypt the phone.
I disassembled my phone lately for maintenance reasons, The battery was out for about 30 minutes, (My phone already had a trouble keeping the clock even though the battery was taken out for a short period), after assembling the phone, it booted up properly till the lock screen appeared and it all became black. software and hardware buttons were working properly, but the LCD itself was totally black.
I booted-up the phone in recovery mode and wiped everything from system, data, to cache, and then installed the newest version of Lineage. After booting the system gave me "process system isn't responding" and close and wait options with infinite bootloops.
I tried installing the full stock Rom and it gave me "setting has stopped working" and "google play services has stopped working".
My guess then was the time on the device, so I went back into recovery opened a shell session and fixed the time using "date" and "hwclock", but it never worked.
After searching online I found that this might be a battery issue, so I bought a new one, and guess...It didn't work either.
I really need help with this device! :crying:
_____________________________________
Solved it by installing the NJ2:
Wiped everything, then installed the stock rom using odin 3.10, after that the system kept telling me the same messages, so I went back and installed twrp 3.10 .. I guess .. then wiped everything except for the system and internal memory, then I corrected my clock using this method:
https://forum.xda-developers.com/galaxy-s3-sprint/help/how-to-edit-time-hardware-time-using-t3621875
and frankly it worked! and booted up normally.
Sadly I wasn't able to install any linage version! ... I hope that I find the solution so soon!
Hello, recently I got the poco f3 (256-8gB) and I have experienced a really weird behavior (I know about random reboots other peooke expperience, but please read what happened to me)
I rooted it with magisk (patching boot image using latest stable apk from official github).
I added smali oatchee module to it.
At some point miui auto-updated to 12.5.1.0 RKHEUXM, I had to get boot image from the update, extract from payload and reparch to get magisk back.
After this I noticed the phone rebooted randomly, it happened like once in 2-3 days, son nothing really anoying, I didn't pay much atention to it since the phone worked flawlessy for everything else. Then I tried to connect to a router wifi (router setup with openwrt) and I noticed EVERY TIME I tried to connect to that specific wifi the phone rebooted. I tried to reconfigure the wifi network but it still happened. No problem with other devices.
Then the next day, I openwd an app which had embedded adds (an app I have been using for a long time, the very same version). 1 second into the add the phone rebooted...and it became stuck in a bootloop in MIUI logo. I couldn't even power off the phone, I could enter recovery/fastboot though.
I used twrp to wipe it without erasing my data, but problem still persisted. Only reflashing boot image (I used stock version) revived my device. I tried to boot it without flashing, phone seemes to boot but with no display.
So I decided to make a full wipe, then reinstall magisk. Phone has been working fine since then, but the occasional random reboot still happens and I'm afraid eqch time my poco f3 will be stuck in bootloop again.
My conclusion is somehow boot image got coreupted, but I can't think of anything I could have done for that to happen, as I only had magisk set up, I didn't even use any app with root permisions yet. Any ideas why that my have happened?
I'm thinking of flashing twrp to recovery so I can reflash boot image from it in case this hapens again...
You mentioned your device rebooted when it connects to a specific WiFi network. Can you get logs for connecting to the network?
I do not use magisk, but I read this thread a lot lol, so as I see the simpler way to root ur phone is to boot to TWRP (fastboot boot xxxx.img) and install magisk from Advanced settings. As I know, there is even an option that allow u to keep ur root after an rom update. U can give it a try, maybe it will solve ur random reboot problem.
Robert314 said:
You mentioned your device rebooted when it connects to a specific WiFi network. Can you get logs for connecting to the network?
Click to expand...
Click to collapse
How may I get those logs?
Alin45 said:
I do not use magisk, but I read this thread a lot lol, so as I see the simpler way to root ur phone is to boot to TWRP (fastboot boot xxxx.img) and install magisk from Advanced settings. As I know, there is even an option that allow u to keep ur root after an rom update. U can give it a try, maybe it will solve ur random reboot problem.
Click to expand...
Click to collapse
My phone is already rooted via magisk patching the roms's boot.img, then flashing via fastboot. That's the recommended method for this device afaik.
Try clean flash. Backup all your stuff that you want to keep. Format data in TWRP before booting into system.
OTA auto-update from time to time causes issues.
I tried again and the revoot when connecting to that certain wifi network persists.
Is there anyway I can reflash my current firmware without having to wipe? Can I jast flash my current update with twrp with no data loss? (Basically what happens when a system update is out...)
Just posting to note that update 12.5.3.0.RKHEUXM solved all those random reboots for me.
They were also happenning when trying to share image/links/anything via bluetooth, telegram....only thing that worked without reboot was "copy link" in the share button.