Okay so I tried to flash a rom update last night, but I guess I did it wrong, and I tried reflashing the previous update, but the tablet would never go to the system again after doing so, it would just keep restarting before even reaching the lineage logo, and each time it restarts twice then drops me back into twrp.
Now something is different about my tablet cause the first screen that shows up, there used to be one yellow line of text in the upper corner, but now there are two, I can't read what they say though as they flash by in like a single second.
Has this happened to anyone else before? And if so can you please please help me??
That behavior is new to me.
Are you at the point of just wanting a useable tablet? If so, I'd suggest checking this post "Only official released binaries are allowed to be flashed (vbmeta)." from the first post in the original rooting thread.
Sorry I'm not talented enough to suggest anything else.
From reading different thread it seems that problem already corrected.
ElsaReyes said:
Okay so I tried to flash a rom update last night, but I guess I did it wrong, and I tried reflashing the previous update, but the tablet would never go to the system again after doing so, it would just keep restarting before even reaching the lineage logo, and each time it restarts twice then drops me back into twrp.
Now something is different about my tablet cause the first screen that shows up, there used to be one yellow line of text in the upper corner, but now there are two, I can't read what they say though as they flash by in like a single second.
Has this happened to anyone else before? And if so can you please please help me??
Click to expand...
Click to collapse
I am in the same situation. Anyone has a solution for this?
Flash the stock image again.
Reinstall the stock image and it will work again. If you do not how to flash then ask me i will help you.
Related
Last evening, I put a new ROM on my phone, which has been rooted for quite some time running Goldeneye with no issues prior to earlier this week, and the rom installed without a problem, but when I went to flash an addon for the rom that came from the dev, the entire thing went south. I was using TWRP which is what's been on the phone since it was rooted, I do NOT have MF3 on the phone however after this install through TWRP, the phone how has the unlock icon on it, and won't boot past the samsung screen. If I try to get into recovery, it boots into odin, and freezes. I tried to do a recovery through Kies, and it just says connecting, then says the phone is not responding. For the first time since I've owned this phone, I feel well and truly stuck. Any help would be greatly appreciated, since after almost two years of rooting and installing ROMS on various devices from Samsung, HTC and Motorola, I made a mistake somewhere along the way and I am not even sure what the hell I managed to do, and the multiple forums I've been reading on here don't seem to be getting me anyplace. Apologies if this is a repeat and I missed a simple solution somewhere, but I've been at this for almost two hours now, so time to swallow the pride...
Think I figured it out
Well after writing this, for my own personal sense of masochism and an overall morbid curiosity, I kept reading, and figured out how to get the phone to actually boot into proper recovery mode (as in NOT Odin), and was able to get a ROM back on the phone, as I didn't care for any of the nandroids I had there. As I am not sure that anyone actually viewed this before I resolved my own issue much less had a chance to respond, it's not appropriate to thank anyone for solving my own problem, except for the poster of the thing that I read which led to my resolution, but I will throw out a blanket thank you to all those that take the time to develop, write, and help others solve the stupid stuff, it is appreciated, at least by this Ohioan, who sometimes manages to get in over his head!
dsly4425 said:
Last evening, I put a new ROM on my phone, which has been rooted for quite some time running Goldeneye with no issues prior to earlier this week, and the rom installed without a problem, but when I went to flash an addon for the rom that came from the dev, the entire thing went south. I was using TWRP which is what's been on the phone since it was rooted, I do NOT have MF3 on the phone however after this install through TWRP, the phone how has the unlock icon on it, and won't boot past the samsung screen. If I try to get into recovery, it boots into odin, and freezes. I tried to do a recovery through Kies, and it just says connecting, then says the phone is not responding. For the first time since I've owned this phone, I feel well and truly stuck. Any help would be greatly appreciated, since after almost two years of rooting and installing ROMS on various devices from Samsung, HTC and Motorola, I made a mistake somewhere along the way and I am not even sure what the hell I managed to do, and the multiple forums I've been reading on here don't seem to be getting me anyplace. Apologies if this is a repeat and I missed a simple solution somewhere, but I've been at this for almost two hours now, so time to swallow the pride...
Click to expand...
Click to collapse
tl;dr phone is in some kind of bootloop, tried flashing stock firmware (successful but can't get past start splash screen), plz halp me
So I was just simply browsing on my phone on reddit is fun app, some Google Chrome sites, and 9gag. So then I saved a gif on 9gag and the phone just gives up on me. It went straight to shut down without any warning whatsoever and proceeded to restart. Thinking that it was just an unusual one time thing, the phone kept rebooting and I started really getting worried. I kept getting the Samsung Galaxy S4 splash screen and after that a black screen and then it vibrated twice and I saw the splash screen again. Didn't even get to see the menu for SafeStrap. After several unsuccessful attempts, I finally accessed SafeStrap after restarting the phone from download mode pressing the volume down button. To make as much precious time as I had, I made a backup (although I checked enable compression which I shouldn't have but I didn't have a lot of space on my SD card) and made an advanced wipe cleaning everything except the SD card. I then proceeded to flash a different custom ROM (GoldenEye if you were wondering) and hoped that it was just a custom ROM error that kept giving bootloops. No such luck. The different ROM didn't even help. So I went back to SafeStrap and made another advanced wipe. At this point, I decided to flash stock firmware via Odin from this link (http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642) with NB1 base. I remember having flashed the non-rootable version successfully and restarted the phone after that. Got past the Samsung Galaxy S4 splash screen and went all the way to ATT splash screen but then it crashed right there. After that, I couldn't figure out the problem and I couldn't flash any more stock firmware (at least from that link) via Odin because I kept getting a fail notice. I asked this question on reddit and the responses kept saying that I may have a defective power button but it doesn't stay shut down and instead bootloops. Should I try to find a new GS4, get another phone or try sammobile firmwares next to see if there's any luck? I really need to save this phone as it is super dear to me. I'm at the point where I can cry right now :crying:
If you guys need any pictures or videos, I will be more willing to do so
RawSynergy said:
tl;dr phone is in some kind of bootloop, tried flashing stock firmware (successful but can't get past start splash screen), plz halp me
So I was just simply browsing on my phone on reddit is fun app, some Google Chrome sites, and 9gag. So then I saved a gif on 9gag and the phone just gives up on me. It went straight to shut down without any warning whatsoever and proceeded to restart. Thinking that it was just an unusual one time thing, the phone kept rebooting and I started really getting worried. I kept getting the Samsung Galaxy S4 splash screen and after that a black screen and then it vibrated twice and I saw the splash screen again. Didn't even get to see the menu for SafeStrap. After several unsuccessful attempts, I finally accessed SafeStrap after restarting the phone from download mode pressing the volume down button. To make as much precious time as I had, I made a backup (although I checked enable compression which I shouldn't have but I didn't have a lot of space on my SD card) and made an advanced wipe cleaning everything except the SD card. I then proceeded to flash a different custom ROM (GoldenEye if you were wondering) and hoped that it was just a custom ROM error that kept giving bootloops. No such luck. The different ROM didn't even help. So I went back to SafeStrap and made another advanced wipe. At this point, I decided to flash stock firmware via Odin from this link (http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642) with NB1 base. I remember having flashed the non-rootable version successfully and restarted the phone after that. Got past the Samsung Galaxy S4 splash screen and went all the way to ATT splash screen but then it crashed right there. After that, I couldn't figure out the problem and I couldn't flash any more stock firmware (at least from that link) via Odin because I kept getting a fail notice. I asked this question on reddit and the responses kept saying that I may have a defective power button but it doesn't stay shut down and instead bootloops. Should I try to find a new GS4, get another phone or try sammobile firmwares next to see if there's any luck? I really need to save this phone as it is super dear to me. I'm at the point where I can cry right now :crying:
If you guys need any pictures or videos, I will be more willing to do so
Click to expand...
Click to collapse
I'd say try redownloading the firmware and make sure your cable is good, try a back USB port, etc. I'd guess the firmware files didn't download properly and so it didn't flash properly. Before you do anything though, try going into stock recovery and wiping everything you can from there.
DeadlySin9 said:
I'd say try redownloading the firmware and make sure your cable is good, try a back USB port, etc. I'd guess the firmware files didn't download properly and so it didn't flash properly. Before you do anything though, try going into stock recovery and wiping everything you can from there.
Click to expand...
Click to collapse
Thank you for the reply. As for the firmware, where should I acquire them? The link I posted has only one firmware (NB1) and I cannot access stock recovery AT ALL. When I do, I can see the blue text in the corner "Recovery booting..." and then the phone restarts again. This is really frustrating
RawSynergy said:
Thank you for the reply. As for the firmware, where should I acquire them? The link I posted has only one firmware (NB1) and I cannot access stock recovery AT ALL. When I do, I can see the blue text in the corner "Recovery booting..." and then the phone restarts again. This is really frustrating
Click to expand...
Click to collapse
NB1 is the only one you can get, just try downloading either one again.
DeadlySin9 said:
NB1 is the only one you can get, just try downloading either one again.
Click to expand...
Click to collapse
I did twice today and I keep getting the same message in Odin, like setting up a connection and then it fails
RawSynergy said:
I did twice today and I keep getting the same message in Odin, like setting up a connection and then it fails
Click to expand...
Click to collapse
When you plug in the phone in Download Mode, does the blue box in Odin light up? If not, reinstall samsung drivers
Sent from my SM-N910G using Tapatalk
I'm usually fairly good at troubleshooting my own stuff but this really has me stuck in the same place for a few hours now.
So basically Flipboard has been nagging me(well play store is, not the app itself but anyway) so I said to myself why don't I uninstall it since I've never used it and don't plan to, and besides I hate to have pointless apps installed. So I open TitaniumBackup and I see it is installed as a system app, I thought what's the worst that can happen? so I do uninstall it and a minute later my phone shuts off. I try to turn it on and it doesn't go past the Samsung Galaxy Note 4 flash screen, it either reboots or stays like that.
I try to go into recovery to restore a backup and I can't, it is stuck at Recovery Booting and again it either stays like that or reboots and does it again and again and again.
Now, I haven't made any changes or installs on my phone for weeks now, so this is either because I unistalled Flipboard(I know I shouldn't have risked it since it was a system app but I really could not see it going this way) or the hardware is on it's way out(don't see what else could it be).
I figured I should flash a stock rom with odin, I can get into download mode, and reinstall everything from scratch.
I took a stock image from xda and flashed it and it does exactly the same thing.
Right now I'm downloading another stock image from sammobile for my country/provider to see if this will change anything.
What else can I try? I'm completely stuck and I really don't want to send the phone back like this, I doubt amazon is gonna be happy about it.
Specs:
N910F
Emotion Revolution 12.1 Rom
POK1 BL&CP
TWRP 2.8.7.0
Really sorry for the double-post. I'm quite desperate and need my phone for work.
Since last post I've tried flashing N910FXXU1COH4_N910FH3G1COH3_H3G.zip through Odin from SamMobile and it did the same thing with rebooting constantly.
Then I've installed Kies and went to Tools -> Firmware Upgrade and Initialisation and gave it the model and S/N and it downloaded something and everything went all right, the phone reboots and I'm back in the same circle, it just shows me the splash screen(in some video's I've seen that after this procedure they get the splash screen and then the android bot with a progress bar, I don't get that, I only get the splash screen and reboot) and reboots.
I thought this was a last resort thing? Is the phone completely dead or is there something I can try?
Again sorry for the double-post.
Update: still no progress so I've contacted Amazon and they said to send it back so hopefully this works out in the end, no matter how annoying the waiting time will be, if you do have any suggestions on what I should try please let me know as I haven't posted the phone yet.
Hello all! This is the second time this has happened to me, I've rooted my phone for about a week, and then for some reason when I decide to restart my phone -- it no longer boots up. It is stuck at the t-mobile screen and vibrates for a bit then stops, I have booted in to recovery mode and tried wiping that cache, but to no avail.
Any help would be appreciated -- or even how I can backup my data would be great too.
Wah gwan! My T-Mobile S7 Edge running TekHD v2. To have your phone running very nicely, you need to download the APD8 fireware. Make sure everything on your phone running APD8. download the files from max on highonandroid, flash the tar file twice using modified Odin from max. Once boot up screen say custom, next step download and extract TekHD.rar file .there's a part in the file that operates like cmd, right click and let it do its thing. Make sure your phone is on and a low USB debugging.
---------- Post added at 10:09 PM ---------- Previous post was at 09:43 PM ----------
Also this TekHD Rom is best for unlimited hotspot for Windows, Android and Mac. I have download about 20 more GB of files to make sure its good. The tutorial from max is good, the easiest way I see so far is to click on the root.dat in max files to add superSU. For TekHD click tekhd.bat. That was the easiest way after flashing the tar file. The hold process take 2 minutes once done right. I'm not a developer but a big Samsung Android fan. I have a Note 3,4,5 S6 Edge+ and S7Edge, I tried and tested many Roms at my own risk. Never had any problems. Make sure you always have the stock rom tar file for your device before any flashing any roms, is case something goes wrong you can start over.
first of all this is an eng boot root, so expect some hiccups and proble.. before u root make sure u back up everything then odin back to stock then root or else u will run into problems
You're going to have to ODIN back to stock. This seems to be happening to a lot of people (myself included) and a stock flash is the only way anyone has been able to recover. Flash all 4 files in ODIN simultaneously, but if you don't have a backup, try flashing the Home_CSC and see if it'll boot. I've heard reports that the Home-CSC file doesn't wipe your phone. If that doesn't work, then unfortunately you're going to have to re-flash, but this time use the standard CSC file, which will wipe your phone. Good luck.
I just had this happen for my second time and was stuck phoneless out of the house :/ I wish we could figure out the cause... Not sure if related, but my recovery has red text on the bottom "dm-verity verification failed"
ph00ky said:
Not sure if related, but my recovery has red text on the bottom "dm-verity verification failed"
Click to expand...
Click to collapse
No, that is not related, dm-verity verification fails because recovery still checks dm-verity even though the kernel does not.
Damn same thing just happened to me at work. Had to do factory reset...
When at that tmobile screen, hold down volume down + home button + power. It will reboot,and as soon as it does, switch volume down to vol up until it loads recovery to reset
This happened to me also. Go to lockscreen and security options and disable automatic security updates.
I think it could be new firmware update from Google. I tried to install TekHD Rom after update to the newest APG1. And it hapened to me also. Stuck on Samsung screen with random weird vibrations.
I can almost certainly say that the vibrate crash has something to do with the phone installing something behind the scenes. After getting the Amazon/Google/Samsung services multiple crash followed by the reset to the vibrating T-mobile screen I did a non-wipe ODIN, which works and works perfectly. What seems to not work though is re-installing root, it just leads back to the same screen, so I think Samsung is pushing something sneaky onto our phones probably through the security thing as mentioned.
---------- Post added at 01:41 PM ---------- Previous post was at 01:40 PM ----------
pawel30w said:
I think it could be new firmware update from Google. I tried to install TekHD Rom after update to the newest APG1. And it hapened to me also. Stuck on Samsung screen with random weird vibrations.
Click to expand...
Click to collapse
TekHD Only works on PD8, it's mentioned in the thread.
pawel30w said:
I think it could be new firmware update from Google. I tried to install TekHD Rom after update to the newest APG1. And it hapened to me also. Stuck on Samsung screen with random weird vibrations.
Click to expand...
Click to collapse
Can't run that ROM on APG1. If you want to try it, you will have to ODIN PD8. There is a post in a thread in this section that shows how.
I just had this same thing happen on PG1. Using ODIN with all of the various parts and Home_CSC got me back in without having to wipe and everything survived. Going to try and re-root with the engineering boot image now that I made a decent backup. Would be great if someone smarter than me figures out what is updating/changing and causing this problem.
I said it on page 1: In settings, go to lockscreen, then security options and disable automatic security updates.
rp3 said:
I said it on page 1: In settings, go to lockscreen, then security options and disable automatic security updates.
Click to expand...
Click to collapse
That might work to prevent this problem -- but what needs to be reverted once this problem starts? I can flash stock PG1 and if I use the (home_csc) it will fix the problem and not wipe my data.... but if I reflash the engineering bootloader it goes back to hanging at the tmobile screen.
im stuck on tmobile screen, and it keeps vibrating, idk what to do
swaggyyd said:
im stuck on tmobile screen, and it keeps vibrating, idk what to do
Click to expand...
Click to collapse
I haven't rooted but if your stuck just Odin back to stock.
I came to post that I'm having these issues as well, this is the second time it's happened to me.
The first time I had TEKHD on my Phone, and so with it constantly nagging to do a system update.
I figured when it did this the first time, it was because the update ran over my TEKHD side load "ROM" and corrupted. Ok , whatever, reloaded.
But now I'm just rooted, and stock ROM otherwise. Just happened to me again
Each time it's happened, I start getting "playstore has crashed" errors - dismiss and it comes right back. So I reboot, and then it boot loops and gets CRAZY hot. Man I've never been able to fry an egg on a phone quite like my S7 Edge...
Is there any light shed on what could be doing this? I may have to remain stock which makes me want to :crying: but I can't keep bothering my Work Admin's to unlock my Token account so I can re-register my same phone -
I shall try that home_CSC Flash when I get home though, hopefully I can recover it at least in a way to transfer token to my tablet or something.
posted that at work, I'm at home now. I tried to flash just the home CSC and that did not work, just booted into recovery with an error and wouldn't resurrect at all.
I shall try that disable auto updates thing though and see if it helps in the long run...
wotan2525 said:
I just had this same thing happen on PG1. Using ODIN with all of the various parts and Home_CSC got me back in without having to wipe and everything survived. Going to try and re-root with the engineering boot image now that I made a decent backup. Would be great if someone smarter than me figures out what is updating/changing and causing this problem.
Click to expand...
Click to collapse
you got a link for the home csc file you can send me I was good for about a month and a half and it finally happened to me as well and can confirm I was getting the play store/ google services errors right before the reboot and tmobile screen
Was having this issue as well, forgot that I needed to turn off Security policy updates.
I'm having a big problem with my sm-g935v. I've had it for about 6 months now. It's on nougat 7.0 right now and I've had it rooted numerous times. It always just looses root for no apparent reason.. I used engboot root and I did t do anything out of the ordinary that would make me think I did something wrong only this last time I lost root I was flashing the Sony soundmod. It never soft bricks or anything, it just resets from setup wizard. Ever since this last time my phone has been super laggy and kinda seems like its just doing its own thing. I had enough so I was gonna reboot into recovery and it looks like its gonna do it and the blue letters come up in the top left then after 10 seconds they disappear and it just boot like normal. I tried to go into the settings and factory reset it through there and again, it looks like its gonna do it and goes throigh all the steps and resets and when it restarts nothing has changed. Im all out of ideas. Maybe something I froze when I was rooted is still frozen? Im not currently rooted even though samsung pass says i am when i click on that setting. Should my next step be flashing a new stock rom with odin or should i try something else? In all my android days ive never heard of this happening. Any help would be much appreciated, and evwruone gets a thanks that helps. Thanks