Hi,
my tablet was acting up after flashing latest pure n rom, ( i love the rom on my n6 so i don't think it is why this happened). so i wiped and reflashed everything. after that i kept getting fc google play service , google voice, google etc etc so i decided to return verything back to stock. using Nexus tool root kit.
i selected 5.1.1 and returned to stock.
on the last screen, it usually reboots and starts your device fresh, however my tablet stayed in fastboot mode so i manually rebooted it and it boots up on a screen asking to type in a password to boot even though i never placed a password on it.
so i booted into boot loader and it showed tevcie state unlocked so i'm assuming return to stock didn't work, so i redid it and same results.
now i don't have access to twrp as it needs the password, nor can i boot up.
i tried normal state and bricked return to stock and same results.
any idea what i should do next?
all feedback related to my question will be thanked
oh and thank you!
Related
Guys, I just finished rooting my Razr, then installed custom recovery. Went to install a rom but forgot to copy it over. rebooted phone and am stuck on the darn Encryption Unsuccessful page. I have clicked reset phone, the process goes thru and phone reboots like normal but comes right back to this screen.
There is not alot of info about thisa on the net. Can anyone please herp me please
edit:
and.... and the custom recovery wont load up. I get the dead android logo :-/
Fixed it. I leasned about fast boot, i was then able to use DROID_RAZR_Utility_Jellybean_XT912_WinMacLin.zip and make the phone brand new again. Thanks anyway. i found all my info in these very forums
Hello,
I've had my S3 for over a year now and it has been mostly running great. Whenever I've had issues I tried to solve them by myself, but this time I was unable to fix my phone, so I must ask for help.
Here's what happened. I left my phone on my desk today and one of my co-workers fiddled with it. He opened SuperSU and then a message popped up saying that SU binary needs to be updated. He then choose to update it via CWM. The phone then restarted and upon starting shows the startup screen then it tries to enter the recovery, but instead it just shows it for a brief moment and then it restarts again. It keeps doing that over and over again. If I remove the battery and then insert it back again, the phone will turn on by itself and continue to reboot after failing to open CWM.
I tried to enter the recovery, but had no success. The phone did enter the Download Mode though, but flasing a ROM via ODIN will remove all of the data stored on the phone and I really need it. The phone is currently running Android Revolution HD 40.
Is there a way to get my phone operational again without loosing the data stored on it?
Thanks in advance.
laxsrbija said:
Hello,
I've had my S3 for over a year now and it has been mostly running great. Whenever I've had issues I tried to solve them by myself, but this time I was unable to fix my phone, so I must ask for help.
Here's what happened. I left my phone on my desk today and one of my co-workers fiddled with it. He opened SuperSU and then a message popped up saying that SU binary needs to be updated. He then choose to update it via CWM. The phone then restarted and upon starting shows the startup screen then it tries to enter the recovery, but instead it just shows it for a brief moment and then it restarts again. It keeps doing that over and over again. If I remove the battery and then insert it back again, the phone will turn on by itself and continue to reboot after failing to open CWM.
I tried to enter the recovery, but had no success. The phone did enter the Download Mode though, but flasing a ROM via ODIN will remove all of the data stored on the phone and I really need it. The phone is currently running Android Revolution HD 40.
Is there a way to get my phone operational again without loosing the data stored on it?
Thanks in advance.
Click to expand...
Click to collapse
did you try reflashing your recovery via Odin?
SuperSU
laxsrbija said:
Hello,
I've had my S3 for over a year now and it has been mostly running great. Whenever I've had issues I tried to solve them by myself, but this time I was unable to fix my phone, so I must ask for help.
Here's what happened. I left my phone on my desk today and one of my co-workers fiddled with it. He opened SuperSU and then a message popped up saying that SU binary needs to be updated. He then choose to update it via CWM. The phone then restarted and upon starting shows the startup screen then it tries to enter the recovery, but instead it just shows it for a brief moment and then it restarts again. It keeps doing that over and over again. If I remove the battery and then insert it back again, the phone will turn on by itself and continue to reboot after failing to open CWM.
I tried to enter the recovery, but had no success. The phone did enter the Download Mode though, but flasing a ROM via ODIN will remove all of the data stored on the phone and I really need it. The phone is currently running Android Revolution HD 40.
Is there a way to get my phone operational again without loosing the data stored on it?
Thanks in advance.
Click to expand...
Click to collapse
First of all what are co workers doing messing with your phone I would seriously not be happy!! screen lock comes to mind!
As the above post said flash another recovery in odin I recommend Philz recovery,backup your data in recovery then factory reset if that does not work flash another rom via recovery or return to stock with odin. You can also boot into recovery with adb but I would try above first.
Then charge your co-worker for all the time wasted trying to fix phone
Thank you so much for the idea, I just tried this and it worked! After flashing new recovery via ODIN, I'm now able to access my phone. There was no need to flash the ROM again, as it was fine, the only problem was with the recovery.
And I still have my data!
Thank you very much again, cheers :laugh:
tallman43 said:
First of all what are co workers doing messing with your phone I would seriously not be happy!! screen lock comes to mind!
Click to expand...
Click to collapse
He's actually a good guy and I'm sure he didn't do it on purpose. He told me that he was playing a game and he tried to add more coins using GameCIH. Then the prompt to allow root access to the app came up along with a notification to update the SU binary. He said he pressed that button by mistake. I wasn't mad at the guy, I was only upset that I may lose my data.
laxsrbija said:
Thank you so much for the idea, I just tried this and it worked! After flashing new recovery via ODIN, I'm now able to access my phone. There was no need to flash the ROM again, as it was fine, the only problem was with the recovery.
And I still have my data!
Thank you very much again, cheers :laugh:
Click to expand...
Click to collapse
you are welcome! glad to see that it works again.
So today I wanted to root my phone again. The first thing I did was go into the stock recovery and do a factory reset. Then the phone boots up and the setup starts. Now the problem is that, for some reason the keyboard is not showing up on the screen, this means I can't enter in my google account to finish the setup. I have tried resetting the phone again but that didn't help.
So to sum up, i just need to finish the setup to get into the phone but the keyboard is not working.
My phone is a Blu Life One X running Android 5.1
Thanks for your help!
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.
Recently, I flashed a TWRP and rooted my Tablet (Galaxy Tab A SM-T350). Yesterday, I made the mistake of installing crdroid (https://forum.xda-developers.com/galaxy-tab-a/development/rom-galaxy-tab-8-0-t3912517) and wiping the recommended partitions (In that post). After confirming that the custom ROM worked, I went back into TWRP to install the Google Apps and SuperSU. That's when I screwed up.
After installing those .zips I went back into crdroid, and the "Weather Pro" or something like that, which appeared to be the launcher, kept crashing.
Regretting my choices and wanting to go back to stock, I flashed this ROM with ODIN: https://androidfilehost.com/?w=files&flid=154234
That didn't seem to work, as when it booted into the setup, it would crash and reboot. I thought I had flashed the wrong version of Android on it, and downloaded this ROM: https://www.sammobile.com/firmwares/galaxy-tab-a/SM-T350/XAC/download/T350XXU1CQJ5/194035/
That also didn't seem to work, as the device would do the same thing. Boot to setup and crash. I tried to boot into ASR and wipe it from there, which is what landed me where I am now:
The device booted, went into setup and immediately shut down. The device does not boot at all, and when plugged in, simply shows the circle with the bolt inside, never showing the green circle and the battery percentage.
Quick FYI: I backed up everything with ADB to my PC way before this happened. Don't know if that will help.
What I mean: https://1drv.ms/v/s!AnXXk5PX0LXn3gd4nJiaPXYOKhFv
Anyone know where to begin in terms of resurrecting my tablet?
Thanks in advance
UPDATE: I don't know what happened, but the device is not charging. Still refuses to boot without crashing but I feel like this could help
Update 2: Ok so it turns out I was stupid and the battery was just dead (I thought it was charged after a night-long charging, but I guess not)