So I've seen this question covered a few times but not sure if my situation is the same as the ones that have been answered prior.
I have a 1-1/2 year old S4 that I rooted when I received it, using whatever flavor of the day rooting method was out there. I have never used any kind of custom firmware with this device, just rooted and disabled some of the built in features like jedi hand wave mode, follow my eyes, etc. (yeah I know those aren't the real names)
Over the past few days I've been noticing apps not being able to open, the screen would go black for a second like the app was launching and then it would return to the home screen. Also a few times the notification bar would flicker while trying to open an app. So I decided to reboot today and now it is stuck at the verizon boot screen.
I've tried all of these options:
Pull battery for 30 sec, remove and replace sim card, replace battery boot.
go into recovery mode and wipe cache
go into recovery and do factory reset
Of course none of these options worked, which is why this thread exists.
now the next option I'm seeing when I'm looking for an answer is either
replace/update the firmware
return to verizon
I guess I'm wondering if the first option is even available to me since I never flashed anything custom before? If it is, I'm sure there's a wonderful thread here that would walk me through the process, if anyone would be so kind as to point me there. I'm just a little confused over what's available in my particular flavor of firmware.
Or, is there a verizon flavor that I could update to and be able to root as well? I remember when I originally rooted it was suggested to keep the older version so you wouldn't get locked in to not being able to do any custom stuff, but not sure if that's been overcome since. I don't need anything fancy, just a rooted phone works for me.
If updating is not an available option for me, is a verizon return my next step? And if so, can/should I remove signs of rooting before sending it in?
Related
Hello folks,
Generally loving my Vibrant, of course hungry for Froyo. I have two Vibrants, the first I've been using and have modded it with root and other enhancements. I gave the other phone to a friend as a gift, but when I wanted to root theirs using the same method I've used on multiple occasions, it would NOT boot into the recovery mode. I use the UP + DOWN push, plus the power button. No dice, just get the cheesy "come together" Tmobile screen, I tried up, down, waited for the Samsung to flash twice, no dice. It was not that complicated on my phone and I can continue to do so. I have looked up threads and there is suspicion that T Mobile disabled this on later vesrions? This version was shipped to me slightly after my own, within a week or so.
It would be disheartening if I couldn't root and make his phone more efficient to deal with the battery hog issues as well as other enhancments. Maybe I'm doing it wrong but I've treid multiple combinations and never get into the utility/recovery screen.
Any thoughts on this? I tried rooting before that with the Ryan one click lag fix, and it seemed to indicate it was done,b ut then Iwhen I opened ROM manager, it said it was not rooted yet. Then when I tried the one click app fix again, it mentioned it couldn't because soemthing about the SD card mounting,etc. I could put the stock PIT file on it via ODIN could I not? But I dont' want to go to all that hassle if it's something else. Is there a another app solution that can root for you? I can mount and drag the update zip there, but can't get tot he screen to reinstall packages.
Hopefully TMobile isn't stripping this down so we can't customize and it's something else but I'm trying all combinations short of doing the hokey pokey.
Thanks in advance!
Kelly
Samsung Vibrant
Apparently either Samsung or Tmobile are having the option disabled via the normal ways to get into recovery. There are numerous other threads regarding this throughout the forums detailing other peoples experiences regarding this.
Take a look here for one:
http://forum.xda-developers.com/showthread.php?t=771247
Join the club. I'm on my third vibrant with this same issue. I am returning it this week for a refund. My first....and last samsung phone.
thank you guys, I was afraid of that. one of the phones greatest assets was it's hackability. Froyo had better do something with battery consumption, speed, etc, or this phone will be a great screen and not much more. boo to hardware lockdowns! let the hackers hack and if you want to void the warranty, do it. I'll see about this ADB mode, I'm wondering if someone can create an app that would successfully root so ROM manager will work. I wonder why the one click fix lag app, which supposedly roots, did not. It seems like an overall lock down on this access?
At any rate, I'll try the other options but it's looking like more and more, my buddy will be a slave to Samsung release timeframe, and thats assuming froyo and updates will fix significant bugs and improve battery life.
thanks again guys! I'll keep trying.
And what about the download mode, can you get in it?
not sure, you mean the little digging android feller? I will try that, I gave the phone to my friend but sent him the page in this thread earlier regarding multiple attempts to get into either / or mode. would that actaully help install the packages aka root the phone? I only used that last time to reinstall via Odin, the T Mobile factory build because it was soft bricked due to a bad lag fix that froze the phone on the Samsung logo.
download mode , can that get it rooted? Or just wanting to know if all hardware access has been blocked?"
not sure, you mean the little digging android feller? I will try that, I gave the phone to my friend but sent him the page in this thread earlier regarding multiple attempts to get into either / or mode. would that actaully help install the packages aka root the phone? I only used that last time to reinstall via Odin, the T Mobile factory build because it was soft bricked due to a bad lag fix that froze the phone on the Samsung logo.
download mode , can that get it rooted? Or just wanting to know if all hardware access has been blocked?
Yeah, that the digging guy. It won't help you to get rooted, but i can't get in download mode, so if you can advise me how can i do that, i appreciate
Alright, so I did a bit of a stupid thing and I acknowledge it. Anyway, here's my steps for what I did:
1). KingRooted the phone, SuperSUme'd to remove KingRoot's stuff
2). Flashed a deodexed ROM through FlashFire for OF1 using a how to list to upgrade and keep root(This is where I think I went wrong, I should have stuck with OC1 to begin with but I was curious ), the flash was successful
3). Because one of my apps(Greenify) requires the Xposed framework for many of the useful settings, I tried flashing a version of the framework designed for non-MDK bootloaders(Arter97's unofficial TouchWiz) through FlashFire, since it seems to be the only way to flash custom stuff on 5.0+ stuff at the moment
4). After this(Just like when I tried Arter's framework with regular OC1), my phone's Google apps started their mass crashing and force closing, which I tried to combat with factory resets but no dice
Unlike before, however, something along the line in my steps disabled the ability to go to stock recovery mode(I think it was KingRoot itself but it might have been the deodexed ROM) and after a bit I couldn't factory reset. Before, I was able to simply Odin flash the stock OC1 ROM. Now, however, Odin won't work either to restore the firmware. I always get the "fail" messages(This I'm not sure why, though it happens with both OC1 and OF1 ROMs so I don't think it's a matter of downgrading). This leaves me with very few options to recover from, especially because I've even tried Verizon's repair program(Stops at 83% and disconnects) and Kies' emergency recovery(Phone isn't recognized and upon manual recovery the result is the same).
The biggest thing that grinds my gears is that my phone isn't even bricked...technically. It started, it went to the Setup Wizard, but then the Setup Wizard crashed once the Gmail portion of the setup was supposed to start in an infinite loop....a "setup loop" rather than a boot loop. I have been working for hours to try and find a solution but so far nothing is working. My phone only starts to the "Software update failed, please use the Verizon Repair etc." message now but no program can recognize it.
Is this a form of hard-bricking? Just not having any method of recovery work even if it turns on? I will admit I'm not the most advanced user but I've been flashing ROMs and custom stuff(Using guides and the like, I'm not fluent enough to go freestyle) for years through a couple of different phones so I'm not a completely new user either. This is the most FUBAR'd I've gotten a phone so far though and I honestly can't afford a new one...that's why I'm going through all the paces I possibly can. Is there any possible way to salvage this? I've been wanting to go to the LG G3 anyway(Despite the G4 being out, the G3's cheaper and still miles better than any Samsung phone, my old one got stolen) but right now it's just not possible. Any suggestions?
Edit: After switching USB ports(Mine are notoriously bad for connections being gained and lost, my memory is bad but I can't see why I didn't think this was the issue), the Verizon repair method has made the phone able to start up. Everything seems to be in order now, more or less. I will say the custom Samsung screen(The unlocked one) came up which makes me think I still have the deodexed ROM installed. If so, then cool beans.
Hey guys, please forgive me for any bad etiquette or lack of information (any information I can provide is available upon request if I leave anything out). I am new to forums in general and especially to XDA, which seems like a good place to get help.
I recently purchased a Sony Xperia Z2 Tablet from Craigslist under the assumption it was a fully unlocked tablet not associated to a carrier. Turns out it was a Verizon Z2 tablet. I dislike Verizon with a firey passion and without getting into too many details, I'm fairly certain they won't help me because a) this tablet wasn't purchased through them as a customer and b) Verizon and I have bad history (unauthorized account modification, shady charges, etc.)
So I thought I'd do my best to make the tablet mine since the asshole who sold it to me has ceased all contact and I don't know how to get a hold of him anymore. No receipt and a data-less tablet.
Anyway, I successfully rooted the tablet and began installing apps that I installed for my G4 when I rooted it (SuperSU, Adaway, Greenify, etc.)
Things were going well but I realised I wanted anything that had to do with Verizon removed from the tablet so I was going to flash Cyanogenmod onto it with a guide I found online. Now rooting and installing custom recoveries was familiar territory and I did these flawlessly. It had TWRP and I made a backup of the system -no Nandroid, sadly-and I began the flashing process. The process said it completed without issue and I went to reboot my device. Enter my current situation:
The device, when I attempted to turn it on, all it did was vibrate constantly until I let go of the power button. Attempting to enter recovery mode (green LED, power + vol down) it showed me, instead of TWRP, a very basic recovery mode with basic options. "Continue booting up", "enter safe mode", "system recovery", and "power down". I tried entering safe mode and it just shut back down, I tried doing a system recovery and it shut down. The only time I ever see the "SONY" logo is if I'm entering this mode. I can enter what I assume is "fastboot mode" (power + vol up and plugging the device into a PC). Nothing on the screen but the LED is blue. I am trying to find guides to restore it if I can and it all looks promising but the only things I know how to really do are root and install custom recovery. I know there are PC tools I can use to send commands to it while it's in fastboot, or send commands in general I just don't know where to begin.
Does anyone know how to fix this? I know it was from Verizon, which sucks, and I know the problem most likely occurred with the attempted flashing of Cyanogenmod. I think I read somewhere I might have done something regarding mismatching kernal numbers. I couldn't find a way to unlock the bootloader so I assume that had something to do with it too.
If someone could give me a guide to restore it to at least its stock ROM where I can begin rooting and installing a custom recovery again, that would be great. Even better would be just flashing a ROM on there that doesn't need Verizon or being able to take it to a stage where it's unlocked and the only evidence it was ever with a carrier is the Verizon logo on the back. I'd really hate to think I wasted money on this and now I'm at a dead end because of a mistake I made. This was supposed to be a gift for my mom on her birthday which is coming up soon. So if anyone knows anything, or has a guide where we can at least get the thing bootable again and I'll just try and deal with a rooted locked device, that would be great.
Thanks for considerations,
Marmalade_Shaws
I have spent time on that screen too.
2 things
1. .. If you installed dual recovery, there is an up, down sequence to select the recovery.
2. Find a downgrade guide, use flashtool to flash. Ft back to stock.
Also you need to know what hardware you are running..511, 561.. And use the proper version.
There are some options with the flashtool and prf maker that can remove branding and vendor stuff. I have not tried those options.
Ez-go said:
I have spent time on that screen too.
2 things
1. .. If you installed dual recovery, there is an up, down sequence to select the recovery.
2. Find a downgrade guide, use flashtool to flash. Ft back to stock.
Also you need to know what hardware you are running..511, 561.. And use the proper version.
There are some options with the flashtool and prf maker that can remove branding and vendor stuff. I have not tried those options.
Click to expand...
Click to collapse
Sorry if this is late... But where can I find the stock? I've searched everywhere and I would need to do it from a flash tool on my PC? I could use all the help I can get.
I just had a very similar experience to the OP, seemingly identical in every way, and am curious if anyone has a solution.
ADB won't function at all, and the bootloader has blocked any sort of flashing via fastboot. Can't boot into TWRP, it goes into a very minimal "recovery," which I imagine is the stock tool, and the Factory Restore option there does absolutely nothing. Flashtool would work great if ADB / Flashmode was at all functional (device blinks and vibrates in a fashion typical of something bricked, and no connection is picked up).
Verizon Z2 Tablets are 561s.
This thing dead or is there some way to push back onto it?
So I posted the following on a few other places
(please expand)
I am in desperate need of help . Yesterday, I woke up and went on my phone and it was acting strange. It was saying that apps that I wasn't using had stopped working or something like that, which was pretty weird, so I decided to restart it. However, when I tried to turn it on again, it got to the carrier screen (I have AT&T) it didn't do anything after. It just stayed on that screen and vibrated in a pattern. I was able to hold home + power + volume down to restart it, and I was able to get to the recovery options screen. I tried clearing the cache and all the data, but no luck. I tried flashing the stock firmware but I couldn't find anything new enough. I had rooted my phone about 5 days earlier, but it had worked perfectly fine up until yesterday. I tried everything I could think of and find online. I recently called AT&T up and they're sending me a new phone, but I have to send my phone to them, and I feel almost certain that they'll find that I've been messing with it. Whether it's the giant lock with the word "Custom" above it, or something in the files. I have 10 days to send it in to them and I need a way to either fix my phone, or wipe ALL of my phone's data before then, but I feel like completely wiping everything might void the warranty as well. I'm not even sure that the root caused the problem.
I do have friends who have the same phone as me, would it be possible to somehow get the most recent firmware off of one of their phones and get it on to mine? I have the G930A and I couldn't find firmware recent enough for my device. I have read A LOT about this issue in the past day and I vaguely remember something about being able to get someone at Best Buy or some other store to flash the most recent firmware onto the phone? Is something like that possible?
Please help, I can't afford the $600+ if it doesn't pass. Any and all ideas are welcomed. Thanks .
After reading some stuff here, I have found out that I can somehow make a backup of the stock firmware. I wouldn't actually be using my phone to make the backup since I don't actually have the stock firmware. I wouldn't be using my phone to make the backup, I have friends with the same phone and carrier. All I need is direction on how to do it. I have a Galaxy S7 (not the bomb edition) and my carrier is AT&T, although I'm not sure that's needed.
first do a factory reset then flash latest stock firmware from sammobile
messi2050 said:
first do a factory reset then flash latest stock firmware from sammobile
Click to expand...
Click to collapse
sammobile.com doesn't have G930A which I need. I've been finding it from other places but none of them have worked so far.
Hey,
I'm pretty new here, so don't hate on my lack of knowledge^^
Maybe I'm even in the wrong sub-forum
(I think there was a sub-forum dedicated to moto x, but this isn't a device-specific issue, so here should be fine - no?)
Got the following problem:
My moto x (2nd gen) is stuck in a loop. I get to the logo-screen, then it goes to "Encryption unsuccessful" and when I click "Reset", it restarts and fails upon trying to reset.
How I got here:
1) A while ago I wanted to encrypt the phone for the lulz (using its' own encryption-tool)
Followed the simple steps, as in having it charged up, but the encryption did not go through.
Don't remember having it to reset at first, it just booted, even though it had bugs after that:
-whenever I charged it, I had problems turning it back on after charging, had to turn off and back on for it to actually work.
-those notifications on top which one can normally open via sliding down, that sliding down did not work after that.
Eventually I did a hard-reset and it fixed the sliding-problem.
Charging also worked fine at first until it did not.
2) I ended up stuck in a boot-loop that went to the logo-screen back and forth (got to logo-screen, restarted, got to logo-screen, restarted, ...)
Tried to soft-/hard-reset using the VOL- and POWER combo.
The hard-reset itself threw some errors at me, something like "can't delete [whatever]".
Still, after a few tries it eventually went past the logo-screen to the encryption-step.
After another few failed resets and emptied cache via recovery-screen, it somehow ignored the encryption-step and turned on the phone (was a fresh version).
3) Worked fine for 1 whole evening, no crashes/glitches/anything until I had to charge it up.
Then it was back to the broken state.
Note: during 2) I tried to boot with a custom recovery-mode(TWRP), but couldn't get it running.
Then I tried to flash it, but anything I tried to install failed.
I had my suspicions, but eventually I got it straightened out: my phone isn't rooted, and the bootloader is locked.
I did get the code to root it via some steps and the motorola service, but the code did not work as it wanted me to unlock the phone first.
From what I've read, to do that I need to get into the settings and unlock/root it...
Funny thing: I can not turn on the phone to get into the settings.
So - anyone got ideas?
Warranty is gone since apparently my tinkering with the locked bootloader and unrooted phone still was visible and they voided the warranty.
Not sure I broke much/anything with that, though, since it DID work at some point after that (even if it was for a few hours before needing recharging)
Therefore I'm open to any suggestions since the alternative stop would be throwing it into the bin^^
Can I unlock the bootloader without having a working system?
Can I root it somehow without having to get into settings (since I can not turn it on in the first place)?
I did a fair share of reading, but most times the guides just assumed that I already rooted it, or forwarded me to a guide where it said "go into settings and spam the build to get advanced options, then simply root/unlock that damn thing". Tried to find a way to unlock/root it without being able to turn it on, but did not get lucky with the search.
If I could unlock and root it, I probably could go from there. Guides are pretty specific and seem to work for most.
Also, I would try the original android version first before searching for any custom systems.
(that is the smartest way to do, right? since I'm just a user and dont plan on doing more hacking/breaking)
Hope all that above wasn't too much to read
Thx for any advice in advance.
Edit:
Well, after what feels like 50 restarts it miraculously did not send me to the "Encryption unsuccessful" but instead booted like it should (as a fresh version, though - so had to backup).
Now I've turned on the thing in the settings so next time it breaks, which I expect to happen by tomorrow, I can flash that sucker.
Still - anyone knows how to enable all that stuff one normally does via settings some way that does not involve successfully booting it?
I mean, there should be a way to root/unlock it without having to turn it on first, right?
Edit2:
As expected, the flashing part was pretty easy, so I'm now sitting with a fresh android 6.0.
Two days in and it's still working fine, haven't had any complications (except battery draining faster then at the very beginning, but I think that's due to it hanging too much on the usb-cable during all those sessions of me trying to fix it - and generally I've had it charge over night a few times to often)
Still would appreciate any advice on how to unlock developer mode and usb-debugging within the bootloader or recovery-mode.