Related
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
Hi I've been on the new ICS MIUI by twitish for about a day and its been pretty stable and snappy, but it suddenly freezes at the pattern lock screen every time I try to use the phone. I can slide to unlock but I can't use the power button to display the power button menu and the screen stays on constantly. The time and date have also been displayed incorrectly (always stuck at 6:01, January 1) and when booting up it goes straight from the dual core m screen and skips the boot animation. I'd prefer not to sbf right now, because I have some texts that I want to read. Any ideas on how to get the phone working again? Thanks.
raymond513 said:
Hi I've been on the new ICS MIUI by twitish for about a day and its been pretty stable and snappy, but it suddenly freezes at the pattern lock screen every time I try to use the phone. I can slide to unlock but I can't use the power button to display the power button menu and the screen stays on constantly. The time and date have also been displayed incorrectly (always stuck at 6:01, January 1) and when booting up it goes straight from the dual core m screen and skips the boot animation. I'd prefer not to sbf right now, because I have some texts that I want to read. Any ideas on how to get the phone working again? Thanks.
Click to expand...
Click to collapse
If it skips the Boot Animation, leave your phone alone for a couple minutes (It can take up to 5 sometimes...). It actually should "Hot Reboot" (Play the Boot animation) and fix itself, but if you use it before it can Hot Reboot it will freeze.
If that doesn't work, try booting into Stock Recovery and wiping cache. It may help clear out whatever was bad. If that doesn't work, you may have to wipe data. Sorry, but you will lose those text messages...I am truly sorry if I made you miss any important information...
This is a rare bug that affects this MIUI build, and I'm not sure what causes it and it's been difficult to debug because it happens randomly. And when it does happen, logcat seems to stop wanting to work.
twitish said:
If it skips the Boot Animation, leave your phone alone for a couple minutes (It can take up to 5 sometimes...). It actually should "Hot Reboot" (Play the Boot animation) and fix itself, but if you use it before it can Hot Reboot it will freeze.
If that doesn't work, try booting into Stock Recovery and wiping cache. It may help clear out whatever was bad. If that doesn't work, you may have to wipe data. Sorry, but you will lose those text messages...I am truly sorry if I made you miss any important information...
This is a rare bug that affects this MIUI build, and I'm not sure what causes it and it's been difficult to debug because it happens randomly. And when it does happen, logcat seems to stop wanting to work.
Click to expand...
Click to collapse
All right thanks a lot for all your great work, I'll try those suggestions, how would you hot reboot again? I tried leaving my phone alone after it booted up for ten minutes but it seems to have no effect, I've wiped cache already so I'm assuming i should wipe data now?
raymond513 said:
All right thanks a lot for all your great work, I'll try those suggestions, how would you hot reboot again? I tried leaving my phone alone after it booted up for ten minutes but it seems to have no effect, I've wiped cache already so I'm assuming i should wipe data now?
Click to expand...
Click to collapse
It should hot reboot by itself. If not then yes, unfortunately you must wipe data.
Sent from my Nexus 7 using xda app-developers app
Hmm, I think I may have gotten a bad download or it may be a problem with the theme I'm running. After wiping data last night things began to work well again (i had originally thought it was my pattern unlock screen which caused problems so I refrained from using it) but after installing the theme i was using again (suave redone) I had the same issues I had before. Maybe I just had a bad download of the theme or rom. On the bright side though, it had lost service/gone into airplane mode when it started having issues so I never lost any messages as the were received after i had wiped data.
I'm Having this Same Issue With my motorola Photon 4g Please Help Me Please Guide Me
raymond513 said:
Hi I've been on the new ICS MIUI by twitish for about a day and its been pretty stable and snappy, but it suddenly freezes at the pattern lock screen every time I try to use the phone. I can slide to unlock but I can't use the power button to display the power button menu and the screen stays on constantly. The time and date have also been displayed incorrectly (always stuck at 6:01, January 1) and when booting up it goes straight from the dual core m screen and skips the boot animation. I'd prefer not to sbf right now, because I have some texts that I want to read. Any ideas on how to get the phone working again? Thanks.
Click to expand...
Click to collapse
I'm Having The Same Issue But A Little More Tricky I'm Stuck On Home Screen Like The Above Person's Issue But I Also Can't Get Into Recovery mode For Wiping Caches & Factory Data Reset When I Try To Do That It Gives Me Error Failed To Boot 2, Please Please Help Me To Get Back It Working...!!!!!
---------- Post added at 11:16 PM ---------- Previous post was at 11:09 PM ----------
twitish said:
If it skips the Boot Animation, leave your phone alone for a couple minutes (It can take up to 5 sometimes...). It actually should "Hot Reboot" (Play the Boot animation) and fix itself, but if you use it before it can Hot Reboot it will freeze.
If that doesn't work, try booting into Stock Recovery and wiping cache. It may help clear out whatever was bad. If that doesn't work, you may have to wipe data. Sorry, but you will lose those text messages...I am truly sorry if I made you miss any important information...
This is a rare bug that affects this MIUI build, and I'm not sure what causes it and it's been difficult to debug because it happens randomly. And when it does happen, logcat seems to stop wanting to work.
Click to expand...
Click to collapse
I'm Having The Same Issue But A Little More Tricky I'm Stuck On Home Screen Like The Above Person's Issue But I Also Can't Get Into Recovery mode For Wiping Caches & Factory Data Reset When I Try To Do That It Gives Me Error Failed To Boot 2, Please Please Help Me To Get Back It Working...!!!!!
Umer Ahmed said:
I'm Having The Same Issue But A Little More Tricky I'm Stuck On Home Screen Like The Above Person's Issue But I Also Can't Get Into Recovery mode For Wiping Caches & Factory Data Reset When I Try To Do That It Gives Me Error Failed To Boot 2, Please Please Help Me To Get Back It Working...!!!!!
---------- Post added at 11:16 PM ---------- Previous post was at 11:09 PM ----------
I'm Having The Same Issue But A Little More Tricky I'm Stuck On Home Screen Like The Above Person's Issue But I Also Can't Get Into Recovery mode For Wiping Caches & Factory Data Reset When I Try To Do That It Gives Me Error Failed To Boot 2, Please Please Help Me To Get Back It Working...!!!!!
Click to expand...
Click to collapse
If you can't get to recovery (bootstrap or stock), you might have to SBF. Follow the SBF guide in development section.
Sent from my One using XDA Free mobile app
As I have frequently done without issues, I was flashing a ROM and got stuck into some sort of bootloop.
Here are some details..
I was on a 4.4.2 KitKat ROM (Gummy Nightly) and decided to try out SlimKat 4.4.2. I wiped (advanced wiped System, Data, Cache and Dalvik Cache). I proceeded to flash the ROM and then the gapps file. Nothing out of the ordinary.. I rebooted and noticed I was at the samsung custom screen for a little longer than normal.. I didn't begin to worry too much because sometimes this screen can appear for a little bit before continuing when first booting into a fresh ROM install. Well.. quite some time passed and it became apparent that it wasn't going to go any further, I restarted the phone and consistently got stuck. I tried booting into TWRP and couldn't/can't get past the TWRP Blue Loading screen. I tried letting it sit for a long ass time (1 hour +) and same with regular rebooting at the Samsung Custom screen (1-2 hours +) with no luck or change.
I have a backup but can't get to it obviously. I'm quite frustrated and am confused/worried about attempting any drastic measures because all of the different phone versions/bootloader discussions/issues. I don't want to mess up the phone by bricking it or something when trying to flash the wrong file. I believe that right now the only thing I can do, if anything, is connecting my phone to my computer via a usb cable and running that ODIN program? I'd be inexplicably grateful and appreciative if someone can just give me some steps/instructions so that I can get my phone back up and running. I'm without a phone right now and am stressed out, so I'm hoping that I haven't made too many people upset with me if there's already somewhere this is answered. I searched but can't find someone with the exact variables my situation contains.
To Recap:
Phone will not progress past samsung custom warning screen as well as TWRP Blue Logo screen no matter how much time passes (Have let sit at either screen for hours)
Was flashing SlimKat nightly (the most recent two days ago) coming from Gummy nightly (1-12, I believe).
The samsung custom screen comes up and then the phone reboots 2 seconds later and comes up again etc..
I never had to use 'safestrap' or whatever. When I got my s4, I was able to avoid the update and was always able to flash ROMs without any worry or concerns.
Please XDA, Help me out here.. I'm completely stressed and worried and don't know where to go from here.. What files to I manually push from my computer.. I don't see how I can solve this without a computer because recovery wont load and ROM won't either
Can you plug it into a pc and get Odin to see it? If so, you can odin back to your stock firmware and start over.
I am having this same problem
a.demarco said:
Can you plug it into a pc and get Odin to see it? If so, you can odin back to your stock firmware and start over.
Click to expand...
Click to collapse
Hey I am having the same problem after trying to flash the latest version of hyperdrive, and my phone got stuck on the Samsung custom screen and I'm not able to get back into recovery even. I saw what you said and plugged my phone into my pc to see if odin could see it, but odin didn't recognize it and I even tried on Kies and it wasnt able to connect to my device either. Is there anything else I can do? or any solution?
If anyone can help I would really appreciate it!
This happened to me several times when i was using Gummy a few weeks back. I just kept doing battery pulls and restarting and was eventually able to get into TWRP. Try this some more and then odin.....
I have been trying to get it working with your advice of battery pulls but no luck. I have downloaded ODIN and installed and also downloaded the two tar files (the kernel and pre-source kernels). I *think* it's good news that ODIN/computer DOES see/recognize that my s4 is connected and disconnected. The issue I'm having is that when flashing the kernel, it does the first green bar and says PASS but the phone restarts and enters the bootloop (it restarts right into the Samsung Custom screen and will stay for a minute and restart again and again)..
I feel like I'm so close but so far away... I know that there's someone reading this that may have the solution or advice to help me get on my way.
I'm still without a phone and I know that there is certainly no one else to blame for my situation then myself but regardless, I would like to see this problem solved! I have a backup on my external sd and there's obviously no way to get to it since my phone won't actually let me into the recovery. The blue TWRP screen just hangs...
Please HELP!!! what can I do????
ccert said:
Hey I am having the same problem after trying to flash the latest version of hyperdrive, and my phone got stuck on the Samsung custom screen and I'm not able to get back into recovery even. I saw what you said and plugged my phone into my pc to see if odin could see it, but odin didn't recognize it and I even tried on Kies and it wasnt able to connect to my device either. Is there anything else I can do? or any solution?
If anyone can help I would really appreciate it!
Click to expand...
Click to collapse
I'm having your same problem, except mine was with RLS 13.
fafinaf said:
I have been trying to get it working with your advice of battery pulls but no luck. I have downloaded ODIN and installed and also downloaded the two tar files (the kernel and pre-source kernels). I *think* it's good news that ODIN/computer DOES see/recognize that my s4 is connected and disconnected. The issue I'm having is that when flashing the kernel, it does the first green bar and says PASS but the phone restarts and enters the bootloop (it restarts right into the Samsung Custom screen and will stay for a minute and restart again and again)..
I feel like I'm so close but so far away... I know that there's someone reading this that may have the solution or advice to help me get on my way.
I'm still without a phone and I know that there is certainly no one else to blame for my situation then myself but regardless, I would like to see this problem solved! I have a backup on my external sd and there's obviously no way to get to it since my phone won't actually let me into the recovery. The blue TWRP screen just hangs...
Please HELP!!! what can I do????
Click to expand...
Click to collapse
Just picked up an mdk s4 which was doing the same thing. I odin back to stock and booted into the phone to make sure everything was good. Then I went back into odin and flashed the md2 pre release kernel then booted again into stock and proceeded to use motochopper.
You shouod have 3 files. The mdk tar file and the two kernel files. Worked like a charm for me you sure you're doing the steps correctly?
Sent from my SCH-I545 using XDA Premium 4 mobile app
---------- Post added at 10:12 AM ---------- Previous post was at 10:10 AM ----------
Also when mine was doing that it was TWRP 2.5.0 and I threw the newest TWRP on after rooting and its much faster rebooting .
Sent from my SCH-I545 using XDA Premium 4 mobile app
fafinaf said:
I have been trying to get it working with your advice of battery pulls but no luck. I have downloaded ODIN and installed and also downloaded the two tar files (the kernel and pre-source kernels). I *think* it's good news that ODIN/computer DOES see/recognize that my s4 is connected and disconnected. The issue I'm having is that when flashing the kernel, it does the first green bar and says PASS but the phone restarts and enters the bootloop (it restarts right into the Samsung Custom screen and will stay for a minute and restart again and again)..
I feel like I'm so close but so far away... I know that there's someone reading this that may have the solution or advice to help me get on my way.
I'm still without a phone and I know that there is certainly no one else to blame for my situation then myself but regardless, I would like to see this problem solved! I have a backup on my external sd and there's obviously no way to get to it since my phone won't actually let me into the recovery. The blue TWRP screen just hangs...
Please HELP!!! what can I do????
Click to expand...
Click to collapse
How are you trying to get into recovery?
Sent from my SCH-I545 using XDA Premium 4 mobile app
---------- Post added at 05:58 PM ---------- Previous post was at 05:56 PM ----------
Power + home +volume up. Then as soon as the phone cuts on let go of Power. Continue to hold the other 2.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Mightycaptain said:
How are you trying to get into recovery?
Sent from my SCH-I545 using XDA Premium 4 mobile app
---------- Post added at 05:58 PM ---------- Previous post was at 05:56 PM ----------
Power + home +volume up. Then as soon as the phone cuts on let go of Power. Continue to hold the other 2.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You don't have to to finger Olympics on s4 like other devices... Just vol up and power
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..
Anyone who can answer,
I own a Swipe Legend. Its specifications are listed below.
I last did 2 things due to which it may have happened.
1. I was using ROM Toolbox Pro to change my font and backup old. I didn't like the new font so restored my old one. But there were too many fonts in the backup, so I thought they were in different uses. I selected all and rebooted. My battery suddenly dropped to about 25% from 48% during changing font some minutes before, and the brightness of pre-boot image was high, I plugged it during that image. Rest is in 2nd reason why I think it could have happened.
2. I put it on charger, forgot it and slept. Later after about 4 hours or so, I did unplug it but it is not working since then. However, this has happened a couple of times with me.
I hope you can help.
Problem: Sorry for not stating the problem first, but I am putting in sequence of time.
Whenever I start it, I can do just 4 things:-
1.See the pre-boot image
2.See the boot animation(the reason I can not show it, as it shows that my phone was rooted. Other reason is that the 1 year warranty is over)
3.Go to the recovery mode
4.See the 'Android is upgrading....' screen
After the 'Android is upgrading....' screen, it goes back to boot animation, then back to the 'Android is upgrading....' screen, and finally after some time screen gets off and I can not turn it on, although I can turn on light of the buttons by power button. Screen gets on for battery notification, and I can see the 'Android is upgrading....' screen. I can always take it to recovery mode, but can not switch it off once it is on so I have to wait for battery to finish. So it may not be bootloop, because that happens just 1 time when it goes back to boot animation. It is also not bricked, as it can do the 4 things.
Solutions already tried:
1. I have hard reset the phone at first.
2. I tried adb and fastboot but they do not recognize my device, maybe due to resetting of USB debugging option after the reset
3. No ROM or CWM is available on my phone, after searching and even using Goo manager
4. I tried removing the SD card after reset, but condition is same
About the phone:-
Name: Swipe Legend
Model: Alps hexxing77_ics2
Android: v4.0.4
Memory: 4GB ROM+32GB SD+512MB RAM
Processor: 2x1.5GHz Dual core(But I think it to be 1GHz dual core due to analysis by apps like Pi)
Screen: 7 inch
Pixels: 800*480
Status: Originally rooted, but maybe root is lost after reset
Already experienced reset: Yes, but it was not rooted by that time
USB Debugging: Was on last time, but maybe offed after factory reset
More details: I can not get the links but it can be searched on amazon or a site like naaptol.com.(I'm from India so don't know any shopping sites of other countries)
If any detail is missing, you may ask.
Please help if you can
Dump your recovery image
Go to builder.clockworkmod.com
Upload the image there
Get cwm for your phone
Press thanks :good: I'd helped :highfive:
---------- Post added at 08:34 PM ---------- Previous post was at 08:33 PM ----------
And yes
Take a backup of rom if are able to boot
Press thanks :good: I'd helped :highfive:
arnabbiswasalsodeep said:
Dump your recovery image
Go to builder.clockworkmod.com
Upload the image there
Get cwm for your phone
Press thanks :good: I'd helped :highfive:
---------- Post added at 08:34 PM ---------- Previous post was at 08:33 PM ----------
And yes
Take a backup of rom if are able to boot
Press thanks :good: I'd helped :highfive:
Click to expand...
Click to collapse
This seems good, but I don't have anything like recovery image. I once took a backup of user data but even that's corrupted. Is there any way to get the recovery image for my phone or it needs to be compiled by myself? Actually, I don't know much about recoveries and such things.
Use the command
dd if=/dev/recoverypartition of=/sdcard/recovery.img
Only you need to know the recoverypartition
It may be something like mmblck0p1
Only the numbers vary
Has your phone booted?
Press thanks :good: I'd helped :highfive:
arnabbiswasalsodeep said:
Use the command
dd if=/dev/recoverypartition of=/sdcard/recovery.img
Only you need to know the recoverypartition
It may be something like mmblck0p1
Only the numbers vary
Has your phone booted?
Press thanks :good: I'd helped :highfive:
Click to expand...
Click to collapse
Thats the only problem.
I can not enter any sort of command line.
Terminal: Not possible unless phone boots properly
ADB: Does not detect my phone
Another problem is my internet connection, due to it I can not access internet anytime.