I had installed TNT Lite v 4.3.0 a couple of weeks ago and it was working pretty good. But today my tablet has gone into a bad state. Every app that I run results in FC. Even the ADW launcher EX that I had selected default is crashing. It then gives me the options: ADW Laucher, ADW Launcher EX, and the regular Launcher. The plain ADW Launcher also fails, but fortunately the regular Launcher still works so I can access the apps.
But unfortunately almost every app that I am trying fails. The only one that doesn't fail is the Web browser. The Settings starts and I can access Applications menu but once I choose say System Applications, after that if I try to choose some other option such as Installed Application, it crashes as well.
Last night however when I started the tablet the battery was probably down and while it was powering it up, it turned off and then restarted by itself and then turned off, without reaching the lock screen. I don't know if it has something to do with all this.
What do I do now? Any help will be appreciated.
Thanks.
A well known issue.
http://forum.xda-developers.com/showthread.php?t=896395
This is why I'm an advocate of people doing the partitioning right before they flash their first custom rom. This way, they won't have to wipe everything later on.
I could only wonder why people aren't mentioning this in every custom rom thread.
Thank you so much. Will try it out tonight.
Unfortunately it seems I have run into a worse issue (without even doing anything yet). Now when I power it on, it starts and shuts off within a few seconds, just shows the birds for like 5 secs and bang, black screen.
The tablet is fully charged (if I put it on charge the light turns green in no time). Looks like the battery is dead.
You might be dropping into APX mode. Do you know how to use nvflash?
Thanks for the reply. You are absolutely right. After multiple tries it did boot up and I was able to install clockworkmod and it all worked great. It wiped off everything but I could live with that. And I turned it off and back on and it was working fine.
But then it went back into the same mode - shutting off immediately after turning on. I decided to return this tablet thinking that it is bad. But before I would do that I thought to restore it or else Viewsonic won't honor the warranty. So I started reading the thread about restoring the tablet to stock using nvram flash. In that procedure it requires me to put the tablet in APX mode and that's when I thought that maybe it is going into APX without pressing the volume - button.
Anyway I was successfully able to flash nvram. Or so it said. I still have the output from the batch file. But now my tablet is totally bricked. It does not boot at all. No pretty birds for me.
I hope there is some way out of it. Please help.
Edit: After re-flashing and using a different file, it seems to have made it a little better. At least I am seeing the birds again. But the original problem of shutting off, or going into the APX mode without pressing Volume button, has returned. All I am getting is the birds for a few seconds and then black screen. I will continue to retry, and if I see it booting up successfully to the stock, this thing is going back to the factory.
1) What image did you use to nvflash?
2) What happened when the flash was finished? Did it boot normally at least once?
3) Does the screen just stay dark all the time now?
1) First time nvflash_gtablet_46_2010112600.zip and after that it did not boot at all. Only black screen. I flashed it couple of times, no avail. Later I flashed nvflash_gtablet_2010110500.zip. This at least recovered it enough that it shows the birds, but soon after the screen turns black. I have confirmed that it is going in APX mode. If I have USB cable connected to my PC, the PC reports discovering the NVIDEA APX device.
2) It hasn't booted normally since I flashed nvram.
3) No I get the birds, but after that it turns dark.
Ok. Using Bekit's 1105 image...
1) Replace part9.img with the recovery.img out of the clockworkmod installation zip.
2) Put the tablet into APX mode.
3) Type in the command to start nvflash but before you hit the enter key hold down the Volume Up key and continue to hold it down until the flash finishes.
4) The tablet should boot into clockworkmod recovery.
5) Repartition 2048 and 0
6) Clear everything (cache, data and dalvik)
7) You might need to re-nvflash at this point.
Thanks for your response. I tried it. Did not work. When you say Replace part9.img with the recovery.img, does it mean copy recovery.img into the NVFlash directory and rename it to part9.img or leave it as recevery.img. I renamed it to part9.img and backed up the original part9.img to part9.img.tmp. The size of recovery.img and the original part9.img are very different. I am confused. Please help.
K J Rad said:
Ok. Using Bekit's 1105 image...
1) Replace part9.img with the recovery.img out of the clockworkmod installation zip.
2) Put the tablet into APX mode.
3) Type in the command to start nvflash but before you hit the enter key hold down the Volume Up key and continue to hold it down until the flash finishes.
4) The tablet should boot into clockworkmod recovery.
5) Repartition 2048 and 0
6) Clear everything (cache, data and dalvik)
7) You might need to re-nvflash at this point.
Click to expand...
Click to collapse
Yes, that is exactly what I meant.
Are you sure you're holding the volume UP key? Birds and then black screen is APX mode which is normally entered by holding volume DOWN.
Well it goes into APX mode even if I don't press any Volume button at all. That is the problem I am trying to fix. When I press power button (without touching the volume button) the birds come and then black screen. And this is APX mode because if I am connected to the PC it brings up an NVIDIA APX device on the PC.
Now if I press the Volume UP button along with the power button, nothing happens, not even the birds come up.
So the fact that the recovery.img (3.7k) is much smaller than part9.img (16k) is ok? Or I am doing something wrong.
Any ideas?
I was thinking about formatting the gtablet. Please let me know if this is the right move, or there is something else I could try first.
shah123 said:
Well it goes into APX mode even if I don't press any Volume button at all. That is the problem I am trying to fix. When I press power button (without touching the volume button) the birds come and then black screen. And this is APX mode because if I am connected to the PC it brings up an NVIDIA APX device on the PC.
Now if I press the Volume UP button along with the power button, nothing happens, not even the birds come up.
So the fact that the recovery.img (3.7k) is much smaller than part9.img (16k) is ok? Or I am doing something wrong.
Click to expand...
Click to collapse
A little more than "It did not work" would be helpful.
What step failed? Please tell me what happened after each step.
Did you get into CWM and repartition?
Did you get everything cleared?
What happened when it rebooted?
What was the original filename of the image you tried to flash?
What version of clockworkmod do you have installed?
Have you ever used ROM Manager?
All of this is important and no one can help you if you don't provide enough information.
Oh, I am sorry. Here are the answers to the questions you asked:
What step failed? Please tell me what happened after each step.
Ans: Out of the 7 steps you provided, the steps 1, 2 and 3 worked fine. It is the step 4 that failed (and of course I can't proceed with the steps anymore). In other words I cannot go into clockworkmod recovery.
Did you get into CWM and repartition?
Ans: No I was not able to do so. If I press power and Volume Up key at the same time, nothing happens, screen remains black, not even birds come up.
Did you get everything cleared?
Ans: I believe you are referring to step 6. No, I could not get to that step.
What happened when it rebooted?
Ans: Nothing showed up. Because when Volume Up is pressed while it is powered on, nothing shows up on the screen.
What was the original filename of the image you tried to flash?
Ans: Actually first time nvflash_gtablet_46_2010112600.zip (and this is before you provided the 7-step recipe - see post #6, 7, 8 of this thread) and after that it did not boot at all. Only black screen. I flashed it couple of times, no avail. Maybe that was my mistake. I chose a wrong file. Later I flashed nvflash_gtablet_2010110500.zip. This recovered it enough that it shows the birds now, but soon after the screen turns black (goes into APX mode).
What version of clockworkmod do you have installed?
Ans: v08
Have you ever used ROM Manager?
Ans: No. What is it?
I really appreciate your help.
What happened at the end of step 3?
Did you start holding the volume UP before you pressed the return key for the nvflash? If not... go back and do it again.
Did you continue to hold it until the flash was happening? You must continue to hold it down for at least 5 - 10 seconds after the flash starts.
When the flash was done did it say "Recovery Key detected" on the screen? If it didn't say this that is an indication that you didn't hold the volume UP key long enough.
If all of the above was done correctly and did happen but you didn't get to clockworkmod then what did you get? Did it look like stock recovery?
It sounds to me like you did the nvflash then tried to reboot into recovery.
Its unbelievable. Tonight when I powered it on it started booting up normal instead of going into the APX mode. I was glad. The stock UI came up, but some of my apps like Quadrant, File Expert etc were still there. It also notified me of the Update 3588. So I downloaded it and started installing it. Pretty soon it rebooted itself (sooner than I thought - I don't know if the remaining installation was supposed to happen after the reboot).
But instead of booting up into 3588 it is unfortunately gone back to the same old issue - the birds followed by black screen - aka APX mode. It never booted up after that. No matter how many times I tried to reboot, it goes into APX mode just like before. I don't know what caused it to complete bootup. One thing I noticed was that the battery was totally drained when I started tonight. I don't know if the drained battery somehow took it out of the APX mode. But now it has a little bit of charge because of hooking up to power supply. I have disconnected the power supply and will leave it in APX mode over night and try it again tomorrow when the battery would be totally drained and see if it boots up fully.
To answer your questions though:
What happened at the end of step 3?
The screen went black and after that it stayed black. No CWM.
Did you start holding the volume UP before you pressed the return key for the nvflash? If not... go back and do it again.
Yes, I did.
Did you continue to hold it until the flash was happening? You must continue to hold it down for at least 5 - 10 secondsafter the flash starts.
Yes, I continued to hold it all the way until the flash completed and the screen went black and quite some time after that.
When the flash was done did it say "Recovery Key detected" on the screen?
I don't think it did.
If it didn't say this that is an indication that you didn't hold the volume UP key long enough.
So I guess I need to give it another try. Tomorrow I will try to reboot the tablet again and if it continued to go into APX I will do the nvflash one more time.
If all of the above was done correctly and did happen but you didn't get to clockworkmod then what did you get? Did it look like stock recovery?
A black dark screen. No CWM or stock recovery.
It sounds to me like you did the nvflash then tried to reboot into recovery.
No at the time of nvflash I held the Volume UP button and nothing happened. Since then I have been trying to bootup or put it in CWM Recovery but only thing the tablet wants to do is go into APX mode.
So I guess my theory of "drained battery takes it out of the APX mode" is correct. I tried to reboot the tablet several times but it just kept on going into the APX mode until the battery was completely drained. And then it started booting up normally but it went into some installation (probably the stock 3588 that I had downloaded in the previous successful bootup). And then the green android with the exclamation sign came and the exclamation sign was rotating for a second or two and then stopped. And it looked like it was hung. I waited for a minute or two but nothing happened, so I pressed one of the buttons, I don't know if it was Menu or Back button, and all of a sudden clockworkmod recovery screen came up.
I have attached the picture of the screen. It still shows the green android with the exclamation sign in the middle of the screen, along with the CWM Recovery.
One other thing I noticed and I am not sure if it is normal is that if I choose say Reboot System Now from CWM menu and it shows like 10 entries with many No's and only one Yes. I can only use the volume Up + button to go down, if I try to go up using volume Down - button it does not go up. Is that normal? Is the only way to go is go down using Voume Up button in CWM menus? I have a feeling that my Volume Down button has gone crazy and it is not functioning properly and that is what is causing it to go into APX mode at the startup as well.
Anyway I first attempted "Apply SDCARD:update.zip" hoping that it might continue with the stock 3588 installation, but that failed. You can see the messages in the picture. Then I tried the Factory Reset and it was successful. I then rebooted the tablet. But now again it keeps on going up into APX mode. I will have to wait until tomorrow for it to completely drain battery again and then try to reboot again.
Any ideas? I know it is overwhelming and the behavior is very weird. At this point I am trying to bring it back to the stock firmware so that I can get this tablet replaced under warranty.
There are quite a few things that are not acting normal from what I see here.
Did you try to repartition 2048 and 0? If not, I would start with that then I would format everything and re-nvflash a stock ROM onto it. That might clear things up. If not you could be looking at a hardware reset.
Related
YUP. I "soft bricked" my t-mobile galaxy s (vibrant here in the us) or so I hope. The phone was rooted via z4 on the latest android t959uvji6 from t-mobile.
How did i do it? Brick my phone that is...
The 3d gallery was pissing me off by picking up everything on the phone. I tried clearing the default setting via the manage app but nothing changed so I decided to delete it. First backing up the apk and odex file from the system folder with titanium backup then deleted them from the system folder via root explorer. Rebooted the phone, pulled out the battery, waited for 30 seconds or so, popped in the battery and booted up the phone w/o any issues.
I tried installing the backup 3d gallery apk file and got the "app not installed" error on numerous attempts. Then tried simply copying it over again with ti backup and nothing happens. Gave up and said the heck with and went the factory restore route, got all the relevant apps installed and tried reinstalling the 3d gallery apk but resulting in the same "app not installed" error prompt. So I again copied over the apk and odex file into the system folder. Rebooted and nothing... phone does not boot into the home screen.
At this point here is what the phone is able to do.
It will boot up and display the default galaxy s animation, goes through it's array of colors then comes to a stop at all white letters then the screen goes blank and nothing happens - zip. nadda. i left it on for 12hrs like that - blank screen w/all the hard keys lit up.
What i did notice was win7x64 recognizes the phone after it gets into the blank screen of death as mass storage units.
So far i've tried booting into the recovery screen via the three button method and none of them works.
Did the karma-volume up-home-power twist - nothing
Did the karma-volume down-home-power roll - nothing
Did the karma-volume up and down-power jiggy - nothing
I tried the key combos for about 2hrs without any success then jumped into adb. After reading for a bit I realized that the phone was still rooted and the debug mode was enabled the last time i shutdown the phone (good'ol ti-backup)
For a while there adb did not recognize the phone at all but with an odd power cycling while spamming "adb reboot recovery" it was able to finally nab hold of the phone and jump into the recovery console. At first I thought it was pure luck so unplugged everything and tried it again - works every time if i did the odd out of sequence power cycle while spamming the adb console with "adb reboot recovery".
In the reboot recovery - deleted the user data and did the restore.
Here's where I think I really screwed up - now the phone is no longer in debug mode.
Long story short - is there a way to get into the recovery screen w/o debug mode on?
**quickly pulls on flack jacket**
but seriously any suggestions would be great
Wrong section bro. You probably won't get an answer here.
To answer your question. Yes, Remove Battery, Plug your phone to USB, Press and hold the volume down and the power button Put the batter back on. This should get you into download mode. Use ODIN to restore.
the usb jig trick did the work - now i have two phones!!!! (bought the nexus s yesterday) lol
Time to ODIN.
To access Download mode.
Unplug. press volume up and down togheter, and connect USB. VOILA!
If ODIN does not recognize it, plug and unplug again
chichu_9 said:
To answer your question. Yes, Remove Battery, Plug your phone to USB, Press and hold the volume down and the power button Put the batter back on. This should get you into download mode. Use ODIN to restore.
Click to expand...
Click to collapse
no!
Why the hell are people giving others ideas on how to get into download when their doing it wrong.
its JUST THE VOLUME BUTTONS, NOT THE POWER BUTTON ALONG WITH IT.
volume + power = Recovery, which in this case you probably cant get into
Volume - Power = Download mode, which everyone can get into unless if they somehow hard bricked, if its possible.
Ok, I done it now.
Had CWM installed with the vegan version. Using 1.1 bootloader. Ran great.
Then I decised to try honeycomb and thats when all hell broke loose.
Then I decided to go back to the stock ROM using APX and all loaded fine and the tablet came up, but every time I would power off it would not boot up. When I hit the power button with or without the + or - volume button it would go into a silent recovery mode with a dead screen. Then I could nvflash a ROM back in and go though the same cycle all over agin. No boot after power up. I cannot get into the CWM recovery. So I tried loading some different ROMS. All did the same thing until I loaded the stock 1.2 ROM, now I cannot even get into the NVFLASH. Totally dead. No action from ay buttons.
The tab ran fine until I messed with the ROMs. Now what do I do?
Update,
USB started working again, so I am back to able to NVflash, but with same problem. Cannot run cwm recovery and every ROM I install loads fine and boots up fine, but as soon as I power down I cannot boot again. I never get the birds splash screen. Power button with volume up/down has no efect. Buttons work fine when in software after an NVflash.
Problem is when I power off, I cannot reboot unless I reload the NVflash.
http://viewsonic-gtablet-for-dummies.webs.com/
Can't get to CWM so nothing in that link fixed it, although that is a nicely put together site.
found answer here
http://forum.xda-developers.com/showthread.php?t=1038689&page=17
Problem solved
Yes, I know this is a common issue. But My Gtab is really stuck. I tried days of following the stock Bekit install. Everything installs just fine and after the nvflash it goes right into the opening screen and starts up normally. Never see birds.
The issue is if I power off, it cannot reboot, always goes to APX mode. I tried several times.
If I run a command such as nvflash --bl bootloader.bin --sync --go I can get back into the startup screen and the tablet runs normally.
There must be a file missing that is part of the normal booting sequence. Is there something missing that the stock install doesn't do?
Yes I have installed CWM and repartitioned and cleared the data. Many times.
Can run the tablet fine if I start it from APX mode, just can't start it from the power button.
I also tried to update to 3588 with same results. Nothing allows a boot from the power button.
I also tried all the files on the "dummies" site. 1.1 and 1.2 install and run just fine, It's just if I power down the tablet. I only get APX mode when powering up.
I also let the tablet update over the internet to version 1.2.5699. It downloaded, then did a restart and went into APX mode. When I forced a boot in APX mode it came up with an android and a red triangle. Another APX boot got me back into version 1.2.4349
Even if I do a reboot from CWM it shuts off tablet and then the power button goes into APX mode
Any help is greatly appreiated.
Try this. My old Gtablet got stuck in APX mode....was like that for about 8 or 9 months until I followed the link in this thread here...
http://forum.xda-developers.com/showpost.php?p=19175683&postcount=106
Possible vol rocker internally stuck
dcol said:
Yes, I know this is a common issue. But My Gtab is really stuck. I tried days of following the stock Bekit install. Everything installs just fine and after the nvflash it goes right into the opening screen and starts up normally. Never see birds.
The issue is if I power off, it cannot reboot, always goes to APX mode. I tried several times.
If I run a command such as nvflash --bl bootloader.bin --sync --go I can get back into the startup screen and the tablet runs normally.
There must be a file missing that is part of the normal booting sequence. Is there something missing that the stock install doesn't do?
Yes I have installed CWM and repartitioned and cleared the data. Many times.
Can run the tablet fine if I start it from APX mode, just can't start it from the power button.
I also tried to update to 3588 with same results. Nothing allows a boot from the power button.
I also tried all the files on the "dummies" site. 1.1 and 1.2 install and run just fine, It's just if I power down the tablet. I only get APX mode when powering up.
I also let the tablet update over the internet to version 1.2.5699. It downloaded, then did a restart and went into APX mode. When I forced a boot in APX mode it came up with an android and a red triangle. Another APX boot got me back into version 1.2.4349
Any help is greatly appreiated.
Click to expand...
Click to collapse
Could be the contact portion of the volume rocker is stuck (I've heard of one user with this issue). Remove the back cover & disconnect the volume switch connector at the motherboard (see attachment) and then try booting.
Al
Tried tcrews suggestion. Same result. APX only on power on. Only thing different was the partitioining 3 times. Didn't work.
Volume button works perfectly. When I am in the tablet, it adjusts volume up and down correctly.
Give K J Rad's technique a whirl.
Tried that one already. Think I am going to just toss it and give up on this and just assume there is some sort of hardware problem with this Gtablet.
I must have reflashed it at least 25 times and spent days on it. I give up. Shame it works fine if you boot it from the APX mode, just not from the power button.
dcol said:
Tried tcrews suggestion. Same result. APX only on power on. Only thing different was the partitioining 3 times. Didn't work.
Volume button works perfectly. When I am in the tablet, it adjusts volume up and down correctly.
Click to expand...
Click to collapse
Did you do all the partitionings ?
Like I said, mine was stuck for near 9 months (just kept it charged and running...if it shutdown would APX boot it).
I tried every nvflash fix that was posted but when I followed the one I linked exactly, it worked. Shocked me since I had tried so many other sure fire methods didn't.
dcol said:
Think I am going to just toss it and give up on this and just assume there is some sort of hardware problem with this Gtablet.
Click to expand...
Click to collapse
Before you give up, do this for me.
Get bekit's standard 2010110500 zip file. Edit the batch file (or shell script) in it and remove the ``--go'' parameter if there is one. Flash the images. The tablet should remain in APX mode. Now run this command:
Code:
C:\SOME\PATH> [B].\nvflash -r --read 2 a2.img --read 3 a3.img --read 4 a4.img --read 5 a5.img[/B]
After the command completes power the tablet off and immediately boot it back into APX mode. Run this command:
Code:
C:\SOME\PATH> [B].\nvflash --bl bootloader.bin --read 2 b2.img --read 3 b3.img --read 4 b4.img --read 5 b5.img --go[/B]
Let the tablet boot into the Tap 'N Tap desktop, then power off. Put the tablet into APX mode and run the previous command again (change the file names to cn.img). Now you will have 3 sets of img files. Upload all of them somewhere so I can compare them with each other and with my bekit img files.
If everything checks out ok, I'll give you another nvflash command to run and if that fails, you can give up.
I've tried all techniques posted and I can't boot anymore and don't see birds either.
I can nvflash all day long but once it shuts down, I need to use nvflash to boot it up again.
Go it.
I used nvflash to stock 1.2-4349 as I had been doing according to these instructions:
slatedroid com/topic/22124-how-to-recovery-when-gtab-does-not-turn-on-and-stay-in-apx-mode/
Then, after booting to the main screen, I let it download 1.2-5699 and shutdown.
I'm still in APX mode at this point.
Then, I referred back to those instructions and and held Vol+ along with power but I never let Vol+ go. It brought me to the blue Android recovery. I ran 'update.zip' right from that menu and it brought up something different I had never seen at the bottom in yellow text (unfortunately I was so suprised that when I grabbed the tab, I hit the home button to reboot) but it said something like /tmp/bootloader.bin=[0]....
I pressed power by itself and I finally saw birds. 4 days of this **** I'm leaving it alone for a while. :-D
Guys,
I'm rooted, with MDK base, and THOUGHT I had a working version of CWM (maybe 6.0.2.3?)
I was in the process of getting ready to try out a new ROM; going through the usual motions, formatting system, data, cache, and for good measure, I finished with a Wipe Data/Factory Reset (which I believe just does the same things again).
The phone suddenly rebooted and froze at the samsung custom screen. When I try to get back to recovery, I can't (hold down up-vol and power; blue message appears and disappears quickly in upper left, and back to Samsung custom lock screen.
I'm stuck. In the past, I always got into recovery by rebooting with ROM Manager, so I haven't really had to use the power-on/ vol up method (thus it may never have worked).
I can get into download mode. So I'm thinking - assuming - that the first thing I should try is to Odin CWM. But I'm admittedly confused, because all of the posts that relate to installing CWM seem to be in the context of the rooting process, and assume you have the ability to place certain files in rooted directories (like loki), which I obviously can't b/c I can't boot.
1) Is re-flashing CWM the right approach ? If so, is there a .TAR file somewhere with just CWM? I can't find an Odin-flashable .tar. EDIT: I found one, but it's designated for i9505. Same thing?
2) If that's not the right approach (or I'm just an idiot and don't know how to get into a working recovery), please advise
Thanks!
Turn the phone off.
Hold volume up and press the power button until it vibrates.
When it vibrates let go of the power and stay holding volume up until you see the recovery splash.
I've found that sometimes continuing to hold the power button will cancel the call for recovery boot. Not sure why.
You can always Odin if that doesn't work.
And I don't know of an Odin package for vzw recovery.
sent from my GE gs4
Dubbsy said:
Turn the phone off.
Hold volume up and press the power button until it vibrates.
When it vibrates let go of the power and stay holding volume up until you see the recovery splash.
Click to expand...
Click to collapse
O - M - G !? Unbelievable. Thanks a BILLION! You just saved me a ton of time.
EDIT: Cr*p. Not out of the woods yet. Now, when choosing 'Install from SD Card' I'm getting 'E: Can't mount /sdcard/'
I'll post this issue in a separate Q.
How the problem occurred
So a year or two ago I bought a Jiayu G4A/T/Whatever they're calling it and safely got it here. I've used the stock ROM for a bit but I wanted to get rid of the bloatware that was still on it, so I eventually ended up with a properly rooted phone with a ROM from Jiayu.es (Everything worked, have ClockworkMod as recovery, accessible via Mobileuncle Tools), which was essentially a stock Kitkat rom made to work for the phone. Now I got sick of the ROM and recently saw the new EMUI version on Huawei's P8 Lite, so I figured I'd look around for a tailored ROM running that, and ended up at "jiayu-emui-3-0-stable" from Needrom.
What I did
1. I downloaded a ROM from Needrom with identifier "jiayu-emui-3-0-stable" (I can't post external links)
2. Backed up my important files following a guide from androidcentral titled "[Guide] How to Backup and Restore Apps and Data when installing new ROMs" that I can't link,and did a full backup using CWM
3. Placed the ZIP on my internal SD card, went into recovery, wiped data/cache (not dalvik, since it wasn't described in the instructions, I think this might be a probable cause) and installed the new ROM from ZIP
4. Rebooted the phone and now it's stuck in the boot loop I mentioned.
What the problem is
Bootloops aren't that much of a problem usually, except this one is... I can't get into recovery mode. From there on it'd be cake, since I made the right preparations, but I can't get into it. While connected to my PC it keeps powering on, showing a splash screen from Jiayu.es briefly (which shouldn't be present anymore) and powering off after 10 seconds, only to come back to the splash screen.
What I've tried
I've unplugged it, removed the battery, waited to get a full power cycle and tried to hold my buttons in these combinations: [power button + volume up], [power button + volume down] - but neither work. It just keeps going with the boot loop. I can succesfully power it down, and when I plug it in from there it shows the low battery image. At the moment of seeing that I thought I could connect to it using ADB / Fastboot, but no luck there either. It keeps saying no devices found, and with fastboot it keeps on <waiting for device>.
My questions
What exactly can I do if there is no way for me to get into recovery mode? Are there any alternatives? How can I get my device to be recognized by ADB? Is that even possible? Why is this bootloop any different from others?
Update from the massive Q&A thread:
ZipAddict said:
Is it booting up on its own too after being off? This happened to wifes phone and it turned out the power button was stuck. I took a pencil and hit the power button with the eraser a few times and it worked then. Her case mustve dislogded it. I will keep my fingers crossed for u. If not send me a private message and i will look for an answer tomorrow and get back with u
Click to expand...
Click to collapse
Thank you for the reply!
Yes, it does. I took the battery out and let it lay disassembled for a night, after which I cleaned it a little and re-inserted the battery. With the case back on, nothing happened, so the power button wasn't stuck for sure. When I powered it back on with the power button (no USB attached) it showed the emblem for ~8 seconds and powered off. It then buzzes to show it's powered on again and up comes the splash screen again. Could it be that the ROM was just a rebooting falsehood? Why would it disallow me getting into recovery mode? I really hope there is something that can still force the device into recovery mode / interact with it somehow while in this state.
Oh, I also tried to see if the volume down button was broken but all the contacts seem intact, plus, they worked an hour before I started switching roms.