So I was rooted and tried flashing back to stock after a bootloop and then the weirdest thing happened....Odin completed all of the steps and my s7 started downloading in download mode and everything completed successfully and when it rebooted... it looked like NOTHING CHANGHED. The only thing different was that the 'custom' with the unlocked padlock on the boot screen was removed and super su was telling me there was no binary installed. I used root checker basic and I am unrooted so did it work? It did this 2 times after, I tried again... is this common? I've flashed stock many times before but never has it ended up like this
Related
Hey guys,
My Nexus 4 (in previously perfect working condition!) was rooted with an unlocked bootloader. It was still running stock Android. Then, purely out of the blue, I couldn't start my phone. It would get stuck in the four bouncing circles after the Google logo. After waiting a few hours, I tried again. Failed again. Then I used Wug's toolkit to flash stock 4.4.4 and unroot. Immediately trying to start the device didn't work, but a few hours later it booted up successfully. This went on for a few days till it happened again - I accidentally let it turn off and it wasn't booting. After waiting several hours, it began to work again. Then last night, I accidentally turned it off again. The boot failed once again. In the morning, I tried again. Failed. I tried again throughout the day, and it repeatedly failed. I then reflashed 4.4.4, but it failed to boot. I'm looking for a solution - any explanation or reason this would suddenly crop up or what i can do to fix it.
Notes: Under Wug's toolkit, I did select the soft brick option. When my phone was on, it worked perfectly. No particular event triggered this problem, it happened in what seems like a completely random fashion.
avpatel said:
Hey guys,
My Nexus 4 (in previously perfect working condition!) was rooted with an unlocked bootloader. It was still running stock Android. Then, purely out of the blue, I couldn't start my phone. It would get stuck in the four bouncing circles after the Google logo. After waiting a few hours, I tried again. Failed again. Then I used Wug's toolkit to flash stock 4.4.4 and unroot. Immediately trying to start the device didn't work, but a few hours later it booted up successfully. This went on for a few days till it happened again - I accidentally let it turn off and it wasn't booting. After waiting several hours, it began to work again. Then last night, I accidentally turned it off again. The boot failed once again. In the morning, I tried again. Failed. I tried again throughout the day, and it repeatedly failed. I then reflashed 4.4.4, but it failed to boot. I'm looking for a solution - any explanation or reason this would suddenly crop up or what i can do to fix it.
Notes: Under Wug's toolkit, I did select the soft brick option. When my phone was on, it worked perfectly. No particular event triggered this problem, it happened in what seems like a completely random fashion.
Click to expand...
Click to collapse
The exact same thing happened to me, i finally flashed 4.2.2. it booted, but then my IMEI disappeared and i couldnt make any calls. It was completely random. It is possible that the same thing is happening to you. If that is the case, the only fix I know is to change the board.
if you can flash CWM or TWRP, try wiping the system files and then flashing a rom to see what happens.
What do you mean change the board?
And for the rest of the suggestions I'd really appreciate a bit of an explanation - I'm not terribly experienced with messing with Android;
Well I did some research and I flashed TWRP, wiped system and data. I then flashed 4.4.4, but it didn't boot. I'll try to turn it on again tomorrow.
^^On stock 4.2.2, does your phone have an imei number? If not, you will need to send the phone to LG for repair.
avpatel said:
Hey guys,
My Nexus 4 (in previously perfect working condition!) was rooted with an unlocked bootloader. It was still running stock Android. Then, purely out of the blue, I couldn't start my phone. It would get stuck in the four bouncing circles after the Google logo. After waiting a few hours, I tried again. Failed again. Then I used Wug's toolkit to flash stock 4.4.4 and unroot. Immediately trying to start the device didn't work, but a few hours later it booted up successfully. This went on for a few days till it happened again - I accidentally let it turn off and it wasn't booting. After waiting several hours, it began to work again. Then last night, I accidentally turned it off again. The boot failed once again. In the morning, I tried again. Failed. I tried again throughout the day, and it repeatedly failed. I then reflashed 4.4.4, but it failed to boot. I'm looking for a solution - any explanation or reason this would suddenly crop up or what i can do to fix it.
Notes: Under Wug's toolkit, I did select the soft brick option. When my phone was on, it worked perfectly. No particular event triggered this problem, it happened in what seems like a completely random fashion.
Click to expand...
Click to collapse
Did you wipe the system cache and dalvik cache BEFORE AND AFTER flashing a zip?
I've seen many instances of an unsucessful boot becuase the cache wasn't cleared AFTER flashing the zip.
If it still doesn't work I'd recommend you to redownload the system zip from the factory image site.
It sounds melodramatic but maybe someone else has encountered the same problem and can help.
I got my phone last week and used it for a couple hours before I decided to root and flash a custom ROM onto the phone. I didn't realize that the kernel had dmverity and proceeded to try and root my phone like any other phone.
I followed the usual steps in installing root for the first time. I used Odin to flash twrp onto the phone and proceeded to restart into recovery. I had forgotten to copy supersu to my phone before I restarted it and this is where my problems began. I swiped on the twrp page where it warns of dmverity but because I didn't transfer supersu I had to restart the phone and get it on. The problem being the phone was now stuck in a bootloop and I somehow managed to get supersu onto the memory and flashed it. I was able to boot into the rom but it was extremely unstable. I could work for maybe 5 minutes before the phone froze, got very hot, then shut down. It would go into a bootloop and succeed maybe 1/20 times, all the while the phone got very hot. I flashed a custom rom onto it and it kind of worked but would still freeze and restart every once in a while. I found the stock bootloader, rom, cp, csc, and flashed those. My phone is now stock everything but the crashes still occur frequently (basically every time I try to use it) and I'm at a total loss as to what to do.
I've rooted all of my phones since I got my S3 several years ago and I've never had a problem like this. Anyone know how I can fix this? My phone is model G935w8 so I know it has the exynos processor and rooting is possible, but I must've done something horribly wrong for it to be like this. Any help is appreciated.
I've spent a full day on this and no further ahead.
This is my wife's phone. A few months back (after Lollipop update) she was running into problems that I needed root to solve. I was lazy and tried Kingo Root and it worked on the first shot. Golden.
No problem but I screwed something up by being overzealous with deleting system apps and her cell data stopped working.
No biggie, I unrooted and did a factory reset and all seemed fine. But now I go to root it and... can't. Kingo Root fails.
Why?
But beyond that, I've followed every other tutorial on various other methods and every attempt ends in failure (stalls at startup screen, pre-animation. I've waited >1hr). I've had to reflash stock ROM several times.
In the stock bootloader under Check Root it says the bootloader is locked.
I've put on TWRP no problem, but that's what seems to stall the boot. I've read that TWRP is problematic with this phone and to use CWR (?) instead, but every link is dead, every tutorial regarding it is sketchy.
Advice?
For a week my G935A worked fine... direct out of the box I flashed ENG Kernel and Rooted, then installed apps and configured - no issues.
Today it was working then it hung on wake.. I tried to reboot and now it gets stuck at the AT&T logo and vibrates 3 times - over and over
I can get to Odin and Recovery screens easily so I tried to flash the ENG Kernel again & deleting Cache Partition few times - didnt fix it.
Also tried booting into Safe Mode - it never gets there, stays at AT&T logo.
When I go into the Recovery menu, I see at the bottom, in red... "dm-verity verification failed"
Anyone know how I can recover from this without Factory Reset? It took 6 hours to reinstall and config all my apps - really want to avoid that.
thx for the help!
as far as I know there is no way to fix and save your stuff. I had the same problem with G930A and even doing a factory reset would only allow my phone to boot but then I get apps crashing and then a reboot puts you back at ATT logo and the vibrates. Best to ditch the whole engboot and go back to stock until a more stable rooting method comes out.
Some searches shows posts that say using Odin to flash HOME_CSC without having to wipe and everything survive
... Where can I get HOME_CSC? I dl'd stock rom and dont see it in there.
thx!
Same here this morning on my 930A w/ PK1....went to watch a youtube vid and everything google related began crashing.
Only been on engboot for a couple days but did flash the v15 debloat last night. hmmmm.
Any luck with the files or procedure LivinOne?
Update: Flashed the PK1 CSC and got into recovery.
Wiped cache and reboot, same failure mode....sad face.
Flashed CSC again, into recovery, factory reset, wiped cache.
Back to setting my "new" device up.
Dec 30 update: Same crash, SEMI same problem.
I get the single vibration followed by the 3 vibrations after I put my pin in from a restart.
Same symptoms prior, all background activities began crashing.
Running all PK1 files from QRhinehardt post.
Any thoughts?
I ended up wiping and flashing the T-Mobile firmware and using the ENG bootloader (but not rooted yet). It is WAY faster than the AT&T was. I've only had issues with Wifi Calling (it doesnt seem to work most of the time)
s7 at&t
Hi, did you first flash with eng bootloader and then tmobile rom? I miss this step...I appreciate your help please
Single vibration followed by the 3 vibrations
Hi, were you able to fix the problem? I'm also getting the single vibration followed by the 3 vibrations.
Do you know why is this occurring? I performed a wipe cache and factory reset but still nothing.
bweegn said:
Same here this morning on my 930A w/ PK1....went to watch a youtube vid and everything google related began crashing.
Only been on engboot for a couple days but did flash the v15 debloat last night. hmmmm.
Any luck with the files or procedure LivinOne?
Update: Flashed the PK1 CSC and got into recovery.
Wiped cache and reboot, same failure mode....sad face.
Flashed CSC again, into recovery, factory reset, wiped cache.
Back to setting my "new" device up.
Dec 30 update: Same crash, SEMI same problem.
I get the single vibration followed by the 3 vibrations after I put my pin in from a restart.
Same symptoms prior, all background activities began crashing.
Running all PK1 files from QRhinehardt post.
Any thoughts?
Click to expand...
Click to collapse
I had rooted my S7 edge (Exynos) a few months ago. I tried installing the ambasadii.zip rom.
I also followed there instructions to the letter.
Upon restarting the phone it started loading the apps, but then stopped halfway and froze. Sometimes restarting to then freeze again.
I reinstalled Recovery ROM and after many tries was able to install via Smartswitch the Stock ROM (Sammobile) 7.0 DQB3
Since then I have had a couple of crashes (average 1 a week). Once when opening Alto (game). The screen froze with a horizontal bar with stripes in it. Booted into recovery and factory reset but had to install stock again via Smartswitch.
Yesterday again a screen and system freeze. Thankfully I was able to restart.
I tried wiping everything with TWRP once I was in TWRP. But it seems that there is something else wrong. I would not mind going right back to full stock (I know the knox counter is tripped). Am I doing something wrong in trying to install the stock fw thru Odin3.12.3? Do I need a specific Revovery file? I am wiping with TWRP but someone else suggested that I had to format with TWRP, could this be the issue?
Or are others also having random crashes?