Hello,
Am I the only one with a boot-loop problem after the .14 update download and install ?
Since then, my tablet has been into a boot loop, and none of the methods found to find in the forums worked sor far.
1) Tried pinhole reset
2) Tried recovery data swipe
3) Tried the "EP201_SDUPDATE.zip" method. It just goes to a screen with a blue diamond in the droid. Then after 20 seconds, the droid is on the floor with a "!" red symbol. After 30 seconds, the device goes back to boot-loop ...
Nothing worked. I tried to root it via adb but somehow I can't install the drivers on my computer, my computer doesn't even see the device via USB since it's stuck in the boot loop.
Did someone had this kind of problem earlier ? I did nothing special, the device is not rooted, nothing ... and had 0 problem with .11 firmware, worked perfectly ...
Thanks for any advice you could have !
I'm having a similar issue since the 14 update. My TP was perfect until last night when the 14 update arrived; but has been suddenly re-booting and getting frozen on the reboot screen since. However, pinhole restart did work, at least temporarily. I'm tempted to try rolling back the firmware.
Likewise, my device is not rooted or altered in any way.
Can't believe they have rolled out a firmware upgrade that actually corrupts a fully functional device! Who are these jokers?
Will update if I find a solution; please do likewise!
I am experiencing the exact same issue since yesterday and so desperate about it since I had no problems at all before. .
So frustrating.
Some more info I found :
During the night I let my device on, rebooting etc ...
I've noticed yesterday it wasn't really a boot loop because sometimes it'd go to the screen with a grey asus logo and a spinner, sometimes it was even going to the screen where the system updates and tries to optimize applications. Each time I went to this screen, it was updating a couple apps then crashing and going back to boot.
So, I figured out that maybe if it was on all night, it owuld update all apps, and boot eventually ...
This morning, the screen was off ... pushed the power button and OH ! I was on the "First start" screen, where I had to choose my keyboard language. Did it, then chose wifi and .... back to boot !
So, it's not technically a boot loop, it's a MASSIVE reboot defect, the .14 firmware totally killed it, the OS doesn't have time to boot, it crashes before ? How can it be ?
I think I'm good for RMA, will try to contact ASUS also ...
Again, same problem for me .
Except the application optimization was made yesterday (not as it should be, I had one reboot after 1/87 applications optimized then the whole optimization).
Since then, sometimes (once in a blue moon), the tablet reboot completely as yours, and then after a few seconds/minutes "playing" on it, it reboots itself.
Etc...
adinava said:
Again, same problem for me .
Except the application optimization was made yesterday (not as it should be, I had one reboot after 1/87 applications optimized then the whole optimization).
Since then, sometimes (once in a blue moon), the tablet reboot completely as yours, and then after a few seconds/minutes "playing" on it, it reboots itself.
Etc...
Click to expand...
Click to collapse
I think our only hope is to recover it using the EP201_SDUPDATE.zip and be lucky enough for the tablet not to reboot during the recovery ... but it might take a lot of tries and it's boring to do ...
I think so. But is it possible to do so without root-access ? What does this method consist of exactly ? Where does this file come from ?
I downloaded the .11 update zip archive from Asus support, isn't it the same ?
adinava said:
I think so. But is it possible to do so without root-access ? What does this method consist of exactly ? Where does this file come from ?
I downloaded the .11 update zip archive from Asus support, isn't it the same ?
Click to expand...
Click to collapse
From what I read root is not required
Yes, it's the good file. Unzip it, inside there will be another zip file.
Rename this : EP201_SDUPDATE.zip
Put it in the root of a microSD card and then put the microSD in the Prime.
Once you've done that, reboot the prime (anyway yours will reboot quickly lol) by holding power and Volume Down button at the same time. Hold it until the first screen of boot comes up and until text appears on the top left.
As soon as you see the text, release everything, then press Volume UP.
It'll say "Booting recovery kernel image" "Signature Match".
If the tablet doesn't reboot before actually starting the recovery, you'll go to a screen with a droid with a blue diamond and then a "dead droid" with a "!" red symbol. I never passed this step as my device reboots before the end of the recovery ...
Good luck
I'm going to try that .
Have you seen testimonials of successful attempts ?
I mean, is it a valid method ?
---------- Post added at 02:18 PM ---------- Previous post was at 02:09 PM ----------
What should I do when I see the dead droid with the exclamation mark ? Wait ?
---------- Post added at 02:19 PM ---------- Previous post was at 02:18 PM ----------
Again, I don't think it's possible without root-access
---------- Post added at 02:22 PM ---------- Previous post was at 02:19 PM ----------
Damn, after a few seconds/minutes,it's rebooting again and stuck at Eee pad logo again
adinava said:
I'm going to try that .
Have you seen testimonials of successful attempts ?
I mean, is it a valid method ?
---------- Post added at 02:18 PM ---------- Previous post was at 02:09 PM ----------
What should I do when I see the dead droid with the exclamation mark ? Wait ?
---------- Post added at 02:19 PM ---------- Previous post was at 02:18 PM ----------
Again, I don't think it's possible without root-access
---------- Post added at 02:22 PM ---------- Previous post was at 02:19 PM ----------
Damn, after a few seconds/minutes,it's rebooting again and stuck at Eee pad logo again
Click to expand...
Click to collapse
It's supposed to work, look here : http://forum.xda-developers.com/showthread.php?p=22768294
I think the problem we're having is that our tablet randomly reboots during the process ...
Yes and no.
As I thought, elsewhere in the post (I already read partially), they said you must have a root-access. Maybe (and I think) the tablet will be unrooted again after that but I'm p***ed off with the idea to root my tablet for a problem I am not responsible for...
adinava said:
Yes and no.
As I thought, elsewhere in the post (I already read partially), they said you must have a root-access. Maybe (and I think) the tablet will be unrooted again after that but I'm p***ed off with the idea to root my tablet for a problem I am not responsible for...
Click to expand...
Click to collapse
They're talking about two different things I think, one thing is to flash the firmware with command line, this requires root of course.
Just wondering if anyone experiencing these reboots has captured a logcat? Seems to be a good first step in figuring out the problem.
Sent from my GT-I9000 using Tapatalk
Maybe, it's not clear out there. And I'm not sure to understand anything anymore.
Perhaps you should ask them to confirm this method doesn't need a root access.
xxbeanxx said:
Just wondering if anyone experiencing these reboots has captured a logcat? Seems to be a good first step in figuring out the problem.
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
I'd love to, but I'm unable to get adb access to the prime, it reboots before my computer can even install the drivers
Ok so, once plugged with USB to my computer, and when finally the device wants to boot and stays on the "android configuration screen", windows is able to access the TF201 folder system ... but not luck with ADB, I guess that's because the debug option is not activated on the device and I can't pass the first configuration screen, it always reboots before the end of it
Another update : using the EP201_SDUPDATE.zip method, I was able to install the US .14 firmware, but result is the same, reboots like crazy.
I'm currently trying to get the .11 US firmware to try to downgrade, but it's hard to find, asus removed all the older US firmwares from their servers, god knows why
EDIT : found the 11.1 firmware, doesn't work ... I'm stuck with .14 firmware
anthonyalberto said:
Another update : using the EP201_SDUPDATE.zip method, I was able to install the US .14 firmware, but result is the same, reboots like crazy.
I'm currently trying to get the .11 US firmware to try to downgrade, but it's hard to find, asus removed all the older US firmwares from their servers, god knows why
EDIT : found the 11.1 firmware, doesn't work ... I'm stuck with .14 firmware
Click to expand...
Click to collapse
did you try this for downgrade? http://forum.xda-developers.com/showthread.php?t=1492887
cyberguest said:
did you try this for downgrade? http://forum.xda-developers.com/showthread.php?t=1492887
Click to expand...
Click to collapse
I can't use it, no adb access ...
anthonyalberto said:
I'm currently trying to get the .11 US firmware to try to downgrade, but it's hard to find, asus removed all the older US firmwares from their servers, god knows why
Click to expand...
Click to collapse
here old firmwares for prime
Hello,
I got a weird problem after unlocking my phone's bootloader and flashing the kernel:
When I power off the phone, it gets into a state where I cannot control it by itself (black screen, no charging light if connected to a power source, does not react in any way to any key).
However, I am able to access it via adb over USB. Using adb, I can put it into some other state (reboot, reboot bootloader, etc) and again gain control over it (also through its own keys). When I select the "power off" function of the bootloader, it enters this state again.
I can even reboot the phone (also into recovery/bootloader/fastboot) from any state
So I can use the phone, but I can't power it on by itself, which isn't a good situation when I don't have a computer around.
device: HTC One S
ROM: CyanogenMod 10 (device is officially supported by CM10; I used the version I found in the Wiki.)
kernel: The one included in CM10 (had to be flashed manually via fastboot because of restrictions by the device; I flashed the kernel before flashing the ROM)
Does anyone can tell me something more about this (or even a solution)? I don't even know how to call this state
Really no-one?
*push*
It's a really annoying state that I'm depending on a pc when my phone shuts down (which may happen when the battery is empty)
*push*
I really don't know what's wrong with your device. but I have a solution. You can download an app or a widget to turn off your device.
did u checked the md5 of the zip file with the md5 in cyanogenmod site?
RavinduSha said:
I really don't know what's wrong with your device. but I have a solution. You can download an app or a widget to turn off your device.
did u checked the md5 of the zip file with the md5 in cyanogenmod site?
Click to expand...
Click to collapse
Thank you for your reply.
An app or widget should also just call the system's shutdown signal, shouldn't it. And since this also happens when I just turn it off without shutdown (power+volDown), the same happens.
Yes, I checked the md5sum.
sylar_5 said:
Thank you for your reply.
An app or widget should also just call the system's shutdown signal, shouldn't it. And since this also happens when I just turn it off without shutdown (power+volDown), the same happens.
Yes, I checked the md5sum.
Click to expand...
Click to collapse
I have used many apps having shut down option. they are going on a different process
---------- Post added at 08:10 PM ---------- Previous post was at 08:04 PM ----------
in my device power+voldwn = screenshot. don't really know what that command do in HTC device.
RavinduSha said:
I have used many apps having shut down option. they are going on a different process
---------- Post added at 08:10 PM ---------- Previous post was at 08:04 PM ----------
in my device power+voldwn = screenshot. don't really know what that command do in HTC device.
Click to expand...
Click to collapse
Sry, i meant volUp, which turns the power off (crash)
However, the problem has been solved somehow (even though I don't know how). I haven't shut it down for a while to avoid this, so I don't know what I might have done. (Without the purpose of solving this issue)
But again, thank you for your help
if it has been solved, nothing to worry. cheers!!!
Is your device s-on [at the top of the bootloader]? Probably not, but that's supposed to prevent the flashing of a kernel. Sounds like a kernel issue. Did you wipe cache(s) and factory reset after flashing?
bodh said:
Is your device s-on [at the top of the bootloader]? Probably not, but that's supposed to prevent the flashing of a kernel. Sounds like a kernel issue. Did you wipe cache(s) and factory reset after flashing?
Click to expand...
Click to collapse
It is s-on.
I wiped cache and dalvik cache and made a factory reset.
BTW: It's not solved, as I previously thought. Looks like it takes some time to enter this "unbootable"-state, and during this period (about half a minute, maybe less) I can boot the phone as it should be.
My Lava Mtab MG7 has become locked due to too many wrong pattern attempts. I can't log into the Google account to unlock it. I wanted to enter recovery mode to wipe data (hard reset). But I don't know the combination of key presses to enter the bootloader. I have tried the following:
1. Vol Up + Power
2. Vol Down + Power
3. Vol Up + Vol Down + Power
Can someone please help me understand how to go around this problem?
I think what you mean is recovery..... lava mtab's data cannot be wiped with stock recovery.... you need to install a custom one through archtools which requires root..... since you said your device is locked ...your lucky if your adb was set to on in developer option before the device got locked .... otherwise the only option is to flash the stock firmware image through rkflashtool.......
---------- Post added at 11:11 PM ---------- Previous post was at 11:02 PM ----------
and one more thing the stock firmware us almost impossible to get, I managed to get one from the service centre but seems the kernel image was not the right one..... cause its actually a Chinese tab callec D7 rebranded by lava .....I found that out after opening a unit which burned after I patched the kernel with overclock binaries ....
so I'd suggest you take it to the service centre they'll give you a replacement with a new unit.... ... I got mine replaced....but I manges hardbrick both of them....
Greyjawripper said:
I think what you mean is recovery..... lava mtab's data cannot be wiped with stock recovery.... you need to install a custom one through archtools which requires root..... since you said your device is locked ...your lucky if your adb was set to on in developer option before the device got locked .... otherwise the only option is to flash the stock firmware image through rkflashtool.......
---------- Post added at 11:11 PM ---------- Previous post was at 11:02 PM ----------
and one more thing the stock firmware us almost impossible to get, I managed to get one from the service centre but seems the kernel image was not the right one..... cause its actually a Chinese tab callec D7 rebranded by lava .....I found that out after opening a unit which burned after I patched the kernel with overclock binaries ....
so I'd suggest you take it to the service centre they'll give you a replacement with a new unit.... ... I got mine replaced....but I manges hardbrick both of them....
Click to expand...
Click to collapse
can u please provide that Chinese tab called D7 firmware link.
wbr
yash_npj said:
can u please provide that Chinese tab called D7 firmware link.
wbr
Click to expand...
Click to collapse
You can get the Lava Mtab MG7 stock rom from here : http://support.moulnisky.com/index.php?dir=Lava/Mtab MG7/
BR
Alex
Greyjawripper said:
I think what you mean is recovery..... lava mtab's data cannot be wiped with stock recovery.... you need to install a custom one through archtools which requires root..... since you said your device is locked ...your lucky if your adb was set to on in developer option before the device got locked .... otherwise the only option is to flash the stock firmware image through rkflashtool.......
---------- Post added at 11:11 PM ---------- Previous post was at 11:02 PM ----------
and one more thing the stock firmware us almost impossible to get, I managed to get one from the service centre but seems the kernel image was not the right one..... cause its actually a Chinese tab callec D7 rebranded by lava .....I found that out after opening a unit which burned after I patched the kernel with overclock binaries ....
so I'd suggest you take it to the service centre they'll give you a replacement with a new unit.... ... I got mine replaced....but I manges hardbrick both of them....
Click to expand...
Click to collapse
To go to recovery mod on lava MG7. All you need to do is to plugin your charger and switch off your
Tablet and let it be completely off.
Then after that press vol+ and power botton for 5seconds. . .
And wait. It will show an android warning. Then press power and vol+ again to enter to recovery mod. And from there you may 'wipe factory reset' and there you go. . .
Go to Terminal and "reboot recovery"
Hello. So, I was trying to install a ROM on my LG Optimus Extreme (LG L40G) using Nexus Root Toolkit and I botched it up. Now it only displays the LG logo and NOTHING I have tried works. It is permanently stuck on the logo. What software would be best for fixing this?
Gurren Lagann said:
Hello. So, I was trying to install a ROM on my LG Optimus Extreme (LG L40G) using Nexus Root Toolkit and I botched it up. Now it only displays the LG logo and NOTHING I have tried works. It is permanently stuck on the logo. What software would be best for fixing this?
Click to expand...
Click to collapse
Let's to clarify your problem, You've bricked your phone. Be careful what you are doing. You shouldn't root your phone.
fa2020 said:
Let's to clarify your problem, You've bricked your phone. Be careful what you are doing. You shouldn't root your phone.
Click to expand...
Click to collapse
Is there anyway to fix it?
Gurren Lagann said:
Is there anyway to fix it?
Click to expand...
Click to collapse
Firstly, you should check out whether you're able to go to Recovery by pressing VOL+ and POWER button.(Do this when the phone is off)
If ok, you could install a safe and healthy ROM base on your phone model but if not, I fear to tell you that you fell into hassle. And probably you'll have to throw your phone out to the garbage.
---------- Post added at 06:38 PM ---------- Previous post was at 06:28 PM ----------
fa2020 said:
Firstly, you should check out whether you're able to go to Recovery by pressing VOL+ and POWER button.(Do this when the phone is off)
If ok, you could install a safe and healthy ROM base on your phone model but if not, I fear to tell you that you fell into hassle. And probably you'll have to throw your phone out to the garbage.
Click to expand...
Click to collapse
The same thing happend to my last Android phone and I did this work.( aiming and throwing it out)
fa2020 said:
Firstly, you should check out whether you're able to go to Recovery by pressing VOL+ and POWER button.(Do this when the phone is off)
If ok, you could install a safe and healthy ROM base on your phone model but if not, I fear to tell you that you fell into hassle. And probably you'll have to throw your phone out to the garbage.
---------- Post added at 06:38 PM ---------- Previous post was at 06:28 PM ----------
The same thing happend to my last Android phone and I did this work.( aiming and throwing it out)
Click to expand...
Click to collapse
So, I'm guessing there's absolutely no way to fix this phone. I tried booting into recovery but it always goes to the LG logo. /cry
Gurren Lagann said:
So, I'm guessing there's absolutely no way to fix this phone. I tried booting into recovery but it always goes to the LG logo. /cry
Click to expand...
Click to collapse
Note that you should firstly take the battery out for 3 minutes and then put it in and HOLD VOL+ and POWER button for about 15 seconds. Don't release it soon. check it out and make me aware.
fa2020 said:
Note that you should firstly take the battery out for 3 minutes and then put it in and HOLD VOL+ and POWER button for about 15 seconds. Don't release it soon. check it out and make me aware.
Click to expand...
Click to collapse
Just tried it. No dice.
Gurren Lagann said:
Just tried it. No dice.
Click to expand...
Click to collapse
I wouldnt say just throw it away.. Is this Nexus Root Toolkit even made for your device? and if so does it have a page where there are trouble shoot options?
Also does this device have a specific thread? I looked and didnt see one but not that familiar with this device..
Dear Devs,admins,
I purchased recently nokia 1 ta-1066 model. recently During installation google security patch my phone got shutdown, then i think there is no charge in my phone , i have taken charging my phone whole day( 8hrs) , my phone not responponding for power button and also power+ vol up button to boot recovery
i finally conformed my phone is hardly dead
no sign,
no life,
just a toy(even childd not like somuch)
" hard bricked"
help pls......................................................
Hey people any update on TA- 1066 Firmware files?
Phone bricked BAD
unlocked Bootloader
flashed TWRP
and the phone bootlooped (boots straight to TWRP)
messed around too much and long story short; No OS anymore,
can push/pull adb and Fastboot still usable but that's pretty much it..
Even GSI roms don't boot.
any help is MUCH appreciated
thanks, hoping for some help
https://forum.xda-developers.com/nokia-1/help/nokia-1-ta-1066-dual-sim-india-hard-t3880265
---------- Post added at 11:25 PM ---------- Previous post was at 11:19 PM ----------
https://forum.xda-developers.com/nokia-1/help/nokia-1-ta-1066-dual-sim-india-hard-t3880265