Hello,
This morning, I was reading comics on my tablet, an it froze completely. The touchscreen and buttons were not responding so I held the power button to turn it off. I turned it on again, and I had an "Encryption unsuccessful" message, saying that I needed to perform a factory reset. The problem is that I never set up my tablet with encryption...
That being said, this screen pops in when my tablet starts, and there is nothing else I can do but to turn it off. I tried the following :
Reboot
Reboot to safe mode
Launch the recovery mode and launch the Android icon (I don't know what it's here for)
Launch the recovery mode and launch a factory reset
The factory reset starts for less than one second before showing the Android sign with a red alert triangle, and resets the tablet. At this point, nothing worked, I am still stuck with this screen, I don't really see what I can do.
I bought my tablet in the US in 2012, it runs Jelly Beans if I recall correctly (the ASUS version, I never rooted it). I have a Mac running Mountain Lion if it can help. Does anyone know what I can try now ?
Thank you in advance for your help
Sylv1z said:
Hello,
This morning, I was reading comics on my tablet, an it froze completely. The touchscreen and buttons were not responding so I held the power button to turn it off. I turned it on again, and I had an "Encryption unsuccessful" message, saying that I needed to perform a factory reset. The problem is that I never set up my tablet with encryption...
That being said, this screen pops in when my tablet starts, and there is nothing else I can do but to turn it off. I tried the following :
Reboot
Reboot to safe mode
Launch the recovery mode and launch the Android icon (I don't know what it's here for)
Launch the recovery mode and launch a factory reset
The factory reset starts for less than one second before showing the Android sign with a red alert triangle, and resets the tablet. At this point, nothing worked, I am still stuck with this screen, I don't really see what I can do.
I bought my tablet in the US in 2012, it runs Jelly Beans if I recall correctly (the ASUS version, I never rooted it). I have a Mac running Mountain Lion if it can help. Does anyone know what I can try now ?
Thank you in advance for your help
Click to expand...
Click to collapse
Is the bootloader unlocked ?
lj50036 said:
Is the bootloader unlocked ?
Click to expand...
Click to collapse
No, it is the default bootloader. Everything is standard, I never felt the need to modify the OS of my tablet. Do you have a theory?
Sylv1z said:
No, it is the default bootloader. Everything is standard, I never felt the need to modify the OS of my tablet. Do you have a theory?
Click to expand...
Click to collapse
Read this understand it and follow it to a T and all should be good...
http://www.transformerforums.com/fo...irmware-tf700-tf300-tf101-possibly-tf201.html
Thx Josh
Thank you for the advice, I will give it a try once I get my hands on a microSD card. I will let you know how it goes!
Related
hello, my name is shahrukh and i need some help. i downloaded animmod (from 4shared) and then i donwloaded busybox. then i pressed blur and then it asked me if i want to reboot it. i pressed yes. this is when the problem starts. It turned off and then it turned on half way and then it turned off. it kept doing that and then i just left it for the night. in the morning it was not doing anything. when i held the power button it turned off and on for like two times and then turned off. i cant even start it up so i have no idea what to do.
i don"t know what to do
please help!!!!
Okay, we need details, describe exactly when "halfway on" is. We need your full model number and rom version (if you know it). Have you tried plugging it in to charge? Does it show anything now that you try to boot it? try holding volume up and powering on to enter recovery menu.
details
ok so when it turns on it says samsung. then after like 10 seconds it turns off. it does that for a few times and then it just goes in a black screen. the model number is YP-G7OC/NAW. when i plug it in to charge it goes on and off two times and then off. if it has low battery it just shows the sign. as for the rom i don't think i have any. i just rooted it using superoneclick. if it goes to recovery mode what do i do?
thanks!
(you got me really fired up when i saw the recovery menu!)
If you can get to recovery menu, try a factory reset, and clear cache. I am not sure if there is a recovery rom for your device, you should check samfirmware.com
tried both of them...no luck. and i couldn't find a recovery rom on samfrimware.com.
Your device has capacitive or mechanical home button?
it has a capacitive home button...the usa version
shahrukhraza said:
it has a capacitive home button...the usa version
Click to expand...
Click to collapse
The phone boots in recovery?
If so, I can investigate a little more what's happening.
I'll try to post a return-to-stock image soon... The problem is that mine is cluttered with crap that the zergRush exploit added (it insisted on installing busybox instead of just rooting...)
(I'm not sure, but I think someone else already posted a stock zImage and system image...)
Here is the post about fixing capacitive buttons. A quick search of forum should have found it.
http://forum.xda-developers.com/showthread.php?t=1421797
Sent from my YP-G70 using Tapatalk
nooooooo!!! you guys have all got it wrong. first of all it doesnt boot in recovery. the only way to get in recovery mode is when it shows the battery sign i hold "up volume"+ power button.and the capaciative button is completely fine. im just stuck in a bootloop (i think) and it has nothing to do with a broken capacitive button! i will try to post a video today to show you guys exactly whats happening.
i kind of had the same problem, one time i thought i had entropy's kernel on and i had CWM well i didn't but i still thought i had so i tried rebooting into recovery using the terminal:
su
reboot recovery
then i turned off and went to this weird recovery menu it had four options, reboot system, apply update from SD card, wipe data partition, and power off and it had a ton of red letters and words saying like, couldn't access data partition or cache partition and couldn't access /data/media, or system, and then i just turned it off because i wouldn't let me choose an option, and then i got stuck in a loop but not during when it says SAMSUNG mine happened during the animation music part that look like fireworks and then SAMSUNG would light up blue then go through it again and 2 more times then go black and i tried flashing the US stock ROM in download mode but still would go through the loop and it doesn't even charge so i got nothing
so did you somehow fix yours? and i never got a recovery menu that showed something about shut down.:confused
Before brick
xxxxxxxxxxxxxxxxx
wait....are you asking me those questions? just to tell you im no developer or something. im just a 12 year old who has his galaxy player stuck in a boot loop. you have to make another thread if you have a problem.
sorry!
Ok. : ) You got it wrong. No problem. His case is different from mine. Just wanted to use her Brick in case. Nothing more. good luck.
I resolve my doubts alone. Nothing that Google does not respond. haha
At least before brick.
ok. let me ask google too xD
anyways..anyone have any idea of how to fix this boot loop?
im trying to do the Linux thing by running the ressurector ans the VM windows the forum is posted under development called hard brick recovery for galaxy 5.0
ok.(i have no idea what you are saying...just saying!)
Hello everyone,
I'm a bit crying right now, i hope you can help :-/
So, i thought about going to cyanogen on my tf201 some months ago. What i remember is that i unlocked it using the asus software then i installed some versions of twrp (i think). After that i stopped because i was kind of lost between many tutorials.
I did not use the tablet since that, i was abroad.
I get it back today and i tried to reset everything, so i went in the settings and click on the reset thing. It did not work, the tablet just blocked on Asus screen and when i manually restarted it, it was like i did nothing (normal boot and no reset).
So i went in the bootloader (power + vol down) and i tried the (4th?) option to wipe everything. The thing said something like "loading image ...." and blocked.
Now the tablet is blocked on the first screen (with asus writen in the middle) and it won't boot, i can not go into the bootloader either, i only have that screen.
I can not even shut it down, keeping power pressed will only restart it.
Is there anything i can do or is the tablet dead ?
Thanks for any help
Hello, as you can see the title, because of my stupid friend, my tablet can't work well now..
He set the password in my tablet and I didn't even noticed at that time.
After I asked him the password, He told me He forgot it.
Unfortunately, that was true, so for unlocking the tablet, I did the wipe data and factory reset.
That was the problem.
After did that, my tablet starts to bootloop, just showing the dell logo.
I tried to access the recovery mode again, but all I can see is that the broken robot, and can't go next step.
I searched the similar threads and I found that if I can approach the fastboot menu, it is able to unbrick the tablet.
I could approach that menu which I can choose normal boot, power off, reboot fastboot, and recovery mode, but that's it. I pressed the volume buttons (up & down simultaneouly) tried many times to recovery mode but after did the factory reset, it couldn't do it again.
Could you give me some advice to solve this problem? I'm looking forward to getting the solution. Thanks. :crying:
guesstres said:
Hello, as you can see the title, because of my stupid friend, my tablet can't work well now..
He set the password in my tablet and I didn't even noticed at that time.
After I asked him the password, He told me He forgot it.
Unfortunately, that was true, so for unlocking the tablet, I did the wipe data and factory reset.
That was the problem.
After did that, my tablet starts to bootloop, just showing the dell logo.
I tried to access the recovery mode again, but all I can see is that the broken robot, and can't go next step.
I searched the similar threads and I found that if I can approach the fastboot menu, it is able to unbrick the tablet.
I could approach that menu which I can choose normal boot, power off, reboot fastboot, and recovery mode, but that's it. I pressed the volume buttons (up & down simultaneouly) tried many times to recovery mode but after did the factory reset, it couldn't do it again.
Could you give me some advice to solve this problem? I'm looking forward to getting the solution. Thanks. :crying:
Click to expand...
Click to collapse
Reflash firmware with intel flash tool.
Look THIS thread and follow instruction.
Thanks for your tips!
minnaing said:
Reflash firmware with intel flash tool.
Look THIS thread and follow instruction.
Click to expand...
Click to collapse
Thanks for your tips!
I followed the steps which you told me, and I could flash that files.
But after did that, it made the tablet freeze, not bootloop.
The screen just shows dell logo and didn't work well. I waited for 15 minutes, even more but it didn't work well.
And still I can't approach the recovery mode. Just I can see the broken robot..
Is there anything I can do? Hope to get advice :'(
Alright, so after having my Fire HD 6 rooted for a few months I started experiencing some random restart issues. I decided to reset to Factory Defaults as I believe that it doesn't touch root (Please verify that one.)
Whenever I clicked on Facotory Reset, however; it immediately restarted and DID NOT RESET.
Then I tried to boot into TWRP and just reflash 4.5.3 (Downgrade) but when I tried to boot into recovery nothing happened, it just booted as normal. Thinking that it was just an error on my part, liking the wrong buttons, etc, I tried running 'adb reboot recovery'
This yielded the same result, just a normal reboot.
I have since unrooted my Kindle to try to update to 5.0.1 (To downgrade again)
Upon trying to update, I restart with no change just like in Factory Reset.
This leaves me with no Root, and no Recovery.
Next I tried using Fastboot to reset it, which now leaves me in a reboot loop that's stuck on the "Fire" logo.
TL;DR:
I have no root, I cannot get into recovery, I cannot access bootloader since ADB doesn't have permission without me giving it (Again, bootloop)
Overall, I'm kind of screwed, any help appreciated.
KeybladePaladin said:
Alright, so after having my Fire HD 6 rooted for a few months I started experiencing some random restart issues. I decided to reset to Factory Defaults as I believe that it doesn't touch root (Please verify that one.)
Whenever I clicked on Facotory Reset, however; it immediately restarted and DID NOT RESET.
Then I tried to boot into TWRP and just reflash 4.5.3 (Downgrade) but when I tried to boot into recovery nothing happened, it just booted as normal. Thinking that it was just an error on my part, liking the wrong buttons, etc, I tried running 'adb reboot recovery'
This yielded the same result, just a normal reboot.
I have since unrooted my Kindle to try to update to 5.0.1 (To downgrade again)
Upon trying to update, I restart with no change just like in Factory Reset.
This leaves me with no Root, and no Recovery.
Next I tried using Fastboot to reset it, which now leaves me in a reboot loop that's stuck on the "Fire" logo.
TL;DR:
I have no root, I cannot get into recovery, I cannot access bootloader since ADB doesn't have permission without me giving it (Again, bootloop)
Overall, I'm kind of screwed, any help appreciated.
Click to expand...
Click to collapse
Please help.... I see you random viewer >.>
I think if someone had an answer they would have posted. Unfortunately, fastboot doesn't work on the 2014 HDs, and it sounds like that's what put you into the bootloop. At this point I think your only option is to contact Amazon for replacement if you're still under warranty.
DoLooper said:
I think if someone had an answer they would have posted. Unfortunately, fastboot doesn't work on the 2014 HDs, and it sounds like that's what put you into the bootloop. At this point I think your only option is to contact Amazon for replacement if you're still under warranty.
Click to expand...
Click to collapse
You're sure fastboot doesn't work? I believe I have used it prior to this with no issues. (By the way, warranty is out >.<)
KeybladePaladin said:
You're sure fastboot doesn't work? I believe I have used it prior to this with no issues. (By the way, warranty is out >.<)
Click to expand...
Click to collapse
Bootloader screen doesn't indicate fastboot mode. Getvar doesn't return anything. If flash commands worked, I'm sure someone would have reported it.
If you haven't tried all button combinations, you should. (You know, hold down power; try power and vol down; try all three.) Without recovery that's all I can suggest. Sorry this happened.
I got the same problem too.
I tried to root and install gapps follow this tutorial. Everything work perfectly.
One day, my Fire's battery was empty and it turned off. I charged it and when it started, it falt in bootloop. The screen show amazon about 8sec and reboot.
I booted into twrp and flashed only 2 files update-kindle-full_ariel-20.5.2.2_user_522053520 and supersu, try to make it work but it didn't
Now, when i hold power button , "Amazon" and then "Fire" appear and it stuck there.
I tried to get into recovery by power and volume+ but didn't work, the screen show "Amazon" and reboot and stuck on "Fire" again.
What should I do now?
Sorry about my English.
Hello XDA.
After whipping my Moto E out the other day, I noticed that turning it on results in it just... laying there and showing me the "WARNING - BOOTLOADER UNLOCKED" message.
Around 1 1/2 years ago, it just turned itself on after clicking the power button once. Now, not even Fastboot mode helps, as choosing any of the options listed there results in the warning mentioned above. For clarification, here is everything in short:
The phone does NOT turn on normally
Using any option in the Fastboot boot menu restarts the loop (i. e. instantly goes back to warning message)
NEITHER does Minimal ADB and Fastboot recognize the device, NOR does the phone recognize the connection to any PC (I've tried 4 different PCs)
Since Fastboot is unresponsive, suggestions to restore stock recovery are useless to me
Suggestions to perform a factory reset are also useless, since Fastboot is unresponsive.
So, am I right if I suppose that this is a hard brick? Or is this somehow salvageable? If so, please help me...
Thanks in advance!
DeBedenHasen said:
Hello XDA.
After whipping my Moto E out the other day, I noticed that turning it on results in it just... laying there and showing me the "WARNING - BOOTLOADER UNLOCKED" message.
Around 1 1/2 years ago, it just turned itself on after clicking the power button once. Now, not even Fastboot mode helps, as choosing any of the options listed there results in the warning mentioned above. For clarification, here is everything in short:
The phone does NOT turn on normally
Using any option in the Fastboot boot menu restarts the loop (i. e. instantly goes back to warning message)
NEITHER does Minimal ADB and Fastboot recognize the device, NOR does the phone recognize the connection to any PC (I've tried 4 different PCs)
Since Fastboot is unresponsive, suggestions to restore stock recovery are useless to me
Suggestions to perform a factory reset are also useless, since Fastboot is unresponsive.
So, am I right if I suppose that this is a hard brick? Or is this somehow salvageable? If so, please help me...
Thanks in advance!
Click to expand...
Click to collapse
If its stuck on boot, its definitely not hard brick.
What was the android version when you wiped data?
Was there any custom recovery you used to wipe data?
You possibly wiped /system too, wiping system can result in bootloop.
Daman5202 said:
If its stuck on boot, its definitely not hard brick.
Click to expand...
Click to collapse
That's a relief. Thanks.
What was the android version when you wiped data?
Click to expand...
Click to collapse
I'm not sure about it, but I think it was 4.x.
Was there any custom recovery you used to wipe data?
Click to expand...
Click to collapse
No, there wasn't.
You possibly wiped /system too, wiping system can result in bootloop.
Click to expand...
Click to collapse
Sorry, but that doesn't make sense. The phone's been rooted for almost 2 years now, and 1 year ago, it turned on perfectly fine.
But let's assume that actually happened somehow, how do I recover from this?