SGP 5.0 wifi, running Chip 1.5 GB ROM, but behavior described below also appears on stock ROM and ICS rom.
I'm not sure exactly what's going on with my player. I noticed this morning when I attempted to turn it on, instead of showing the samsung splash logo, (followed by the animation) it showed the loading/waiting circle then the battery charging screen for a second, then rebooting.
I fooled around with various settings, with no results. I flashed a backup nandroid, with the same behavior. I flashed an ics rom, same behavior. I'm back to my normal ROM right now. But the only way I can use my device (at all) is to do the following.
1. Boot into download mode. (power, voldown)
2. Flash a kernel (heimdall flash --kernel zImage)
3. It boots
Then everything works, until I power off the device. Then I have to flash the kernel again to get the device to boot. Reboots, Rebooting into recovery, etc work. But powering the device down completely requires a flashed kernel to get running again.
Any ideas on what's going on? I'm totally stuck. Thanks.
xterminus said:
SGP 5.0 wifi, running Chip 1.5 GB ROM, but behavior described below also appears on stock ROM and ICS rom.
I'm not sure exactly what's going on with my player. I noticed this morning when I attempted to turn it on, instead of showing the samsung splash logo, (followed by the animation) it showed the loading/waiting circle then the battery charging screen for a second, then rebooting.
I fooled around with various settings, with no results. I flashed a backup nandroid, with the same behavior. I flashed an ics rom, same behavior. I'm back to my normal ROM right now. But the only way I can use my device (at all) is to do the following.
1. Boot into download mode. (power, voldown)
2. Flash a kernel (heimdall flash --kernel zImage)
3. It boots
Then everything works, until I power off the device. Then I have to flash the kernel again to get the device to boot. Reboots, Rebooting into recovery, etc work. But powering the device down completely requires a flashed kernel to get running again.
Any ideas on what's going on? I'm totally stuck. Thanks.
Click to expand...
Click to collapse
That is a known bug that happens when plugged into a PC, but it's happening for you all the time?
Sent from my Galaxy Nexus
Mevordel said:
That is a known bug that happens when plugged into a PC, but it's happening for you all the time?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Yeah, The bootloop is exactly what used to happen when I attempted to charge on the laptop's usb port. Now it does it regardless of power source, or even if there is no power source at all. In addition, I can't boot up the device at all without going into download mode and flashing a new kernel. Annoying.
xterminus said:
Yeah, The bootloop is exactly what used to happen when I attempted to charge on the laptop's usb port. Now it does it regardless of power source, or even if there is no power source at all. In addition, I can't boot up the device at all without going into download mode and flashing a new kernel. Annoying.
Click to expand...
Click to collapse
I'm kinda stumped here... So strange. No hardware mods? And of course no USB port short because it still works. Obviously, the boot loader or kernel is getting confused and always putting it in low power mode. Try running as root
Code:
echo 1 > /proc/param/debug
to reset the boot loader settings and see if that fixes it.
Also, what kernel are you running?
Sent from my Galaxy Nexus
Mevordel said:
I'm kinda stumped here... So strange. No hardware mods? And of course no USB port short because it still works. Obviously, the boot loader or kernel is getting confused and always putting it in low power mode. Try running as root
Code:
echo 1 > /proc/param/debug
to reset the boot loader settings and see if that fixes it.
Also, what kernel are you running?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
No Hardware mods. The above code resulted in the following in my dmesg
Code:
<6>[ 1207.038888] Parameters have been set as DEFAULT values...
<6>[ 1207.046140] -----------------------------------------------------
<6>[ 1207.050839] Information of Parameters
<6>[ 1207.054614] -----------------------------------------------------
<6>[ 1207.062599] - param_magic : 0x72726624
<6>[ 1207.065725] - param_version : 0x13
<6>[ 1207.069769] - 0. SERIAL_SPEED : 7
<6>[ 1207.073483] - 1. LOAD_RAMDISK : 0
<6>[ 1207.077908] - 2. BOOT_DELAY : 0
<6>[ 1207.081888] - 3. LCD_LEVEL : 97
<6>[ 1207.084413] - 4. SWITCH_SEL : 1
<6>[ 1207.087973] - 5. PHONE_DEBUG_ON : 0
<6>[ 1207.091895] - 6. LCD_DIM_LEVEL : 17
<6>[ 1207.096636] - 7. LCD_DIM_TIME : 0
<6>[ 1207.099345] - 8. MELODY_LEVEL : 0
<6>[ 1207.103233] - 9. REBOOT_MODE : 0
<6>[ 1207.106878] - 10. NATION_SEL : 0
<6>[ 1207.111616] - 11. LANGUAGE_SEL : 0
<6>[ 1207.114203] - 12. SET_DEFAULT_PARAM : 0
<6>[ 1207.118078] - 15. VERSION(STR) : I8315XXIE00
<6>[ 1207.122962] - 16. CMDLINE(STR) : console=ttySAC2,115200
<6>[ 1207.129529] -----------------------------------------------------
I figured it could be the usb port, so I cleaned it. It helped a bit, in that usb insertion/unplug events are detected all the time again, but didn't help with my problem.
I've used two kernel's at this point. 2012.03.05 Entropy and the kernel that came with PA 2.57 (which is 2.6.35.7). I've also tried a complete nandroid recovery I made from a "stockish" system back in April 2012. Didn't change behavior of device. I've also tried an nandroid I made of an ICS ROM I fooled with before Christmas. No dice either.
I'm currently back and running Paranoid Android 2.57, which I'm very pleased with overall.
Just to clarify, and because I've been fooling with this problem for a few days now, this is what's happening:
When Nothing is connected (No USB or AC)
* Short Power button depression does not start device
* Holding power button down for 5+ seconds the screen flickers on, and the "pre battery loading" animation shows for a second. Very rarely does the battery actually show. Before the actually battery graphic is actually shown, the device reboots and loops. As nothing is plugged in, I don't see why this sequence should even be loading. It *should* show the samsung logo, but it does not for some reason.
* Holding power down + vol up results in same behavior as above.
* Holding power down + vol down results in download mode.
When Plugged into USB.
* Bootloop, which is normal behavior I guess with custom kernels. I can still get into download mode.
When Plugged into AC
* Under normal circumstances I'd see the pre-battery loading animation then the battery status. Then holding down the power button would start things up. In my case, nothing happens at all. It just sits there, no startup animation or other activity unless I actually depress (and hold) the power button which results in a single loop as describe above. I can get into download mode though.
Behavior I've noticed which is otherwise odd:
* It (used to) behave flakey on detecting usb insertion. Sometimes it wouldn't detect the device, with even adb failing to detect it. Now it seems to work with cleaning up the usb connections. No other changes in behavior through.
* Powering down the device completely results in all the odd behavior described above. Restarting from a running android system works fine. Restarting into recovery works fine too, so the problem is in the cold-boot process.
* The ONLY way I get the device to boot up after powering down is to go into download mode. When I flash a kernel, which resets the device (warm boot?) As soon as it resets, I can hold down the power and vol-up to get into cwm recovery. If I let it continue I get a normal boot.
The only thing I can think of at this point is that possibly a (boot?) partition which normally isn't touched by flashing roms or an nandroid backup was messed up. I'm pretty good with android overall, but I don't know the internals like a developer would. Is this a possibility? Thanks for the advice so far.
when this happened to me I cleaned the USB port with a tooth pic and a little rubbing alcohol
Sent from my YP-G70 using xda app-developers app
xterminus said:
No Hardware mods. The above code resulted in the following in my dmesg
Code:
<6>[ 1207.038888] Parameters have been set as DEFAULT values...
<6>[ 1207.046140] -----------------------------------------------------
<6>[ 1207.050839] Information of Parameters
<6>[ 1207.054614] -----------------------------------------------------
<6>[ 1207.062599] - param_magic : 0x72726624
<6>[ 1207.065725] - param_version : 0x13
<6>[ 1207.069769] - 0. SERIAL_SPEED : 7
<6>[ 1207.073483] - 1. LOAD_RAMDISK : 0
<6>[ 1207.077908] - 2. BOOT_DELAY : 0
<6>[ 1207.081888] - 3. LCD_LEVEL : 97
<6>[ 1207.084413] - 4. SWITCH_SEL : 1
<6>[ 1207.087973] - 5. PHONE_DEBUG_ON : 0
<6>[ 1207.091895] - 6. LCD_DIM_LEVEL : 17
<6>[ 1207.096636] - 7. LCD_DIM_TIME : 0
<6>[ 1207.099345] - 8. MELODY_LEVEL : 0
<6>[ 1207.103233] - 9. REBOOT_MODE : 0
<6>[ 1207.106878] - 10. NATION_SEL : 0
<6>[ 1207.111616] - 11. LANGUAGE_SEL : 0
<6>[ 1207.114203] - 12. SET_DEFAULT_PARAM : 0
<6>[ 1207.118078] - 15. VERSION(STR) : I8315XXIE00
<6>[ 1207.122962] - 16. CMDLINE(STR) : console=ttySAC2,115200
<6>[ 1207.129529] -----------------------------------------------------
I figured it could be the usb port, so I cleaned it. It helped a bit, in that usb insertion/unplug events are detected all the time again, but didn't help with my problem.
I've used two kernel's at this point. 2012.03.05 Entropy and the kernel that came with PA 2.57 (which is 2.6.35.7). I've also tried a complete nandroid recovery I made from a "stockish" system back in April 2012. Didn't change behavior of device. I've also tried an nandroid I made of an ICS ROM I fooled with before Christmas. No dice either.
I'm currently back and running Paranoid Android 2.57, which I'm very pleased with overall.
Just to clarify, and because I've been fooling with this problem for a few days now, this is what's happening:
When Nothing is connected (No USB or AC)
* Short Power button depression does not start device
* Holding power button down for 5+ seconds the screen flickers on, and the "pre battery loading" animation shows for a second. Very rarely does the battery actually show. Before the actually battery graphic is actually shown, the device reboots and loops. As nothing is plugged in, I don't see why this sequence should even be loading. It *should* show the samsung logo, but it does not for some reason.
* Holding power down + vol up results in same behavior as above.
* Holding power down + vol down results in download mode.
When Plugged into USB.
* Bootloop, which is normal behavior I guess with custom kernels. I can still get into download mode.
When Plugged into AC
* Under normal circumstances I'd see the pre-battery loading animation then the battery status. Then holding down the power button would start things up. In my case, nothing happens at all. It just sits there, no startup animation or other activity unless I actually depress (and hold) the power button which results in a single loop as describe above. I can get into download mode though.
Behavior I've noticed which is otherwise odd:
* It (used to) behave flakey on detecting usb insertion. Sometimes it wouldn't detect the device, with even adb failing to detect it. Now it seems to work with cleaning up the usb connections. No other changes in behavior through.
* Powering down the device completely results in all the odd behavior described above. Restarting from a running android system works fine. Restarting into recovery works fine too, so the problem is in the cold-boot process.
* The ONLY way I get the device to boot up after powering down is to go into download mode. When I flash a kernel, which resets the device (warm boot?) As soon as it resets, I can hold down the power and vol-up to get into cwm recovery. If I let it continue I get a normal boot.
The only thing I can think of at this point is that possibly a (boot?) partition which normally isn't touched by flashing roms or an nandroid backup was messed up. I'm pretty good with android overall, but I don't know the internals like a developer would. Is this a possibility? Thanks for the advice so far.
Click to expand...
Click to collapse
Very intriguing. That is what I thought too, but there are only 3 boot partitions that I know of. If either of the first two (PBL and SBL) are corrupted, you're bricked. The third is boot loader config, which you just reset.
What happens when you are plugged into USB and you run adb reboot? You still loop, right? And you say you can reboot fine into recovery. Is that also true on Gingerbread? I know that on JB, low power mode is disabled when booting into recovery.
Now I'm beginning to think it may be a battery/charging circuit issue. After all, it is getting stuck in "low power mode". Does your battery still charge normally? Try draining your battery completely. Use it all the way normally; then reboot into recovery and wait until it shuts off. (Note that wiping battery stats is completely unrelated.) Hopefully that will de-confuse your device.
Sent from my Galaxy Nexus
Mevordel said:
Very intriguing. That is what I thought too, but there are only 3 boot partitions that I know of. If either of the first two (PBL and SBL) are corrupted, you're bricked. The third is boot loader config, which you just reset.
What happens when you are plugged into USB and you run adb reboot? You still loop, right? And you say you can reboot fine into recovery. Is that also true on Gingerbread? I know that on JB, low power mode is disabled when booting into recovery.
Now I'm beginning to think it may be a battery/charging circuit issue. After all, it is getting stuck in "low power mode". Does your battery still charge normally? Try draining your battery completely. Use it all the way normally; then reboot into recovery and wait until it shuts off. (Note that wiping battery stats is completely unrelated.) Hopefully that will de-confuse your device.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
adb reboot works fine. I have problems on a cold-boot or startup from scratch. I've been getting into cwm by flashing the kernel and immediately pressing power/volup. (Or going into recovery via adb or the power-off menu). From a cold-boot, cwm is just as inacessible as the normal android boot without a kernel flash.
Charging seems to work fine while the device is up and running. Charging while powered off doesn't seem to do anything but loop (even from ac power).
I'll run down the power like you suggested. Hopefully that'll clear things up.
follow up
Discharging the battery to 5%, then booting into cwm and letting the battery discharge to completely seemed to do the trick. As soon as I plugged it into the AC, the proper battery charging icon popped up, and it seems to start up now without issues.
Thanks Mevordel for your help.
Related
I woke up this morning and went to the bathroom and thought i heard the alarm go off on the device. It actually didnt so I turned the screen on and clicked on the alarm app and then it wouldnt click and pressing the power button would dim the lights. This is probably the 3rd time its happened.
I then just powered it down holding the power button, like ive done before.. This time it wouldnt power back on. Cant get into the recovery screen/download mode. Plugged it to the outlet and nothing. Doesnt seem to turn on. It had the Touchwiz UX euro update wifi based..
Any idea if anyone knows what to do from this point on? (other than doing a warranty with samsung)
I had this problem once the other day. It was due to one of Pershoot's latest kernels. Are you using his OC'd kernels?
I have had the following behavior:
Touchscreen unresponsive
Hitting power again would cause the screen to dim instead of shutting off.
Holding it down would bring the powerdown menu, which would not be touchable
However if I let the screen time out with the powerdown menu up, I'd usually be able to unlock the device if I tried to power it on 30 sec later.
I've had this with pershoot's kernels (no OC) and with my own kernels (based off pershoot's with OC disabled and conservative gov enabled). Haven't tried returning to a stock kernel.
In your case it sounds like you've also had a sleep of death, whcih hasn't happened to me. Have you tried a long-press (10-15 seconds) of the power button? This should reboot the tab.
Never did pershoots OC kernel .. was just a straight rom flash.
I have tried every combo to get the screen on.. it only seems to go into APX mode.. but i cannot do anything when i get there. i read somewhere to let the battery drain by leaving it on after apx mode but it seems the device shuts off after unplugging or idle after a while since i tried to connect the usb to see if still connected.
Sleep death? Doesnt that usually occur with the device being off? With me i powered down as soon as the screen became unresponsive.. this time it just failed to reboot
I try doing the reroot process since I have access in nvflash ... and just diong steps to see if anything will make it come to life and the first step which is -- nvflash --bl bootloader.bin --go -- i get this
downloading bootloader -- load address: 0x108000 entry point: 0x108000
download command failed NvError 0x120002
command failure: bootloader download failed (bad data)
bootloader status: Bct file not found (code: 21) message: flags: 1073840124
hi guys,
it looks that accidentally i've booted my device into apx mode!
...uploading screens...
br
condi
What do you mean with apx mode?
Where are the screenshots?
How did you reach this?
i didnt wanted to get into apx... accidentally when trying to get root again (after reflash stock rom).. WOW
suddenly device automattically came out from it - still blank-black screen.. some sort of timeout when idle? gr....
now we've got to find out how to enter it with purpose!
will upload mobile-camera photo of that..
Hey its a good news, because APX mode is needed for NVFlash.
As i know with NV flash we can flash our tablet
so the bootloop can be repaired, and more things can be done.
We have to find out how to enter into APX mode.
norberto_ said:
Hey its a good news, because APX mode is needed for NVFlash.
As i know with NV flash we can flash our tablet
so the bootloop can be repaired, and more things can be done.
We have to find out how to enter into APX mode.
Click to expand...
Click to collapse
yeeeeeeeah i was so excited, even wanted to put charger, and keep it in apx mode as long as we could get and make some good things... but it just turned off.
ehhh how did i done it? it was another of several tries to make root, i experimented with turning on/off mtp device in device manager, first of screenshots shows, when apx mode jumped in. i think its concerned in correct rebooting device, but there should be some combination/scenario of behavior to get into apx mode.
C:\Users\Admin\Downloads\NVFlash>nvflash --sync
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
-------------------------------------
only this is what i got before it went out.
Condi,
I also got apx mode once by chance, but i didnt manage to do it again.
I entered into recovery several times while rebooting and pressing the recovery buttons, one of the times it just got into apx...
skoperst said:
Condi,
I also got apx mode once by chance, but i didnt manage to do it again.
I entered into recovery several times while rebooting and pressing the recovery buttons, one of the times it just got into apx...
Click to expand...
Click to collapse
Hi friend,
thanks for confirmation about it, now i've got hope that we'll discover how to enter apx mode
interesting... now we can find a way to use NVFLASH files to flash custom recoveries/kernels...
i had told ppl to test out stuff regarding NVFLASH:
http://forum.xda-developers.com/showthread.php?p=20889203&highlight=nvflash#post20889203
http://forum.xda-developers.com/showthread.php?p=20973791&highlight=nvflash#post20973791
http://forum.xda-developers.com/showthread.php?p=21716011&highlight=nvflash#post21716011
i am busy currently... but when i am free might need some willing users to test out a few things
Any chance the reset button might have something to do with it?
It "seems" to kill all power, yet pressing it whilst on makes it flash the red led a couple times.. so ovbiously there is some power.
Also, when it connected to your pc and was recognised as an Nvidia devices etc, how did the drivers install? Was it something handled automatically by auto update, or had you previously installed drivers yourself trying to find it another time?
Edit: Just too add, has anyone tried contacting Nvidia about it? I sent them an email about it, they just refferred me to their dev section (which ended up being a section for games developers! ) I'm pretty sure they confused APX with APEX. So I email again but no response since.. perhaps if a few of us send through they might sweat a bit and give the answer . Figured we'd possibly have more luck dealing with them than Sony (even though I realise Sony would be the all-knowing in this)
OK, I just stumbled onto this thread where defsix has found a switch inside the tablet.
I can't see the picture but could this potentially be a s-off switch or something like that, that could allow us to either flash unsigned zips or get into APX/NVflash stuff?
this could lead to an unbrick?? do you think that i may better wait for this (or for any other way to unrick) or to go and try to make it replecade by another one?
Well... I recommend waiting just a little bit more, my reasoning being:
There are only 2 potential outcomes for taking it in:
1. All sweet, they fix it or replace it
2. They send it away, discover you've messed with it, log your serial number and label your warranty as void.
If this can't fix it soon enough I'd recommend just sending it back and taking a chance - I mean what the use in still having a warranty for a perma-brick when you could chance having it fixed only risking your warranty (not like they can just keep it after they check it out).
I'll check it out tonight possibly (aus time mind you/+10 hour GMT) if the gf isn't raging at me and see what it let us do!
well then, one day or two days doesn't change anything, i can esaly wait till tuesday/wednesday, if i have to send it to them, and the warranty void...well then...it's just my fault after all...but i can wait 2days..
'mount' command from recovery shell:
Code:
$ /system/xbin/mount
/system/xbin/mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p4 on /cache type ext4 (rw,nosuid,nodev,relatime,barrier=1,dat
a=ordered)
/dev/block/mmcblk0p3 on /system type ext4 (rw,nodev,noatime,nodiratime,barrier=1
,data=ordered)
still no recovery here hmm...
so, if i try to update the firmware via recovery, when it says that it has had an error (the classic of base or sku), adb will be accessible?
sapphire88 said:
so, if i try to update the firmware via recovery, when it says that it has had an error (the classic of base or sku), adb will be accessible?
Click to expand...
Click to collapse
unfortunately not, but maybe something can be discovered through that way
OK so i got home early and just cracked it open (quite literally - a little tab snapped )
So all I can gather so far is that switching this switch to "off" just kills all power. The tab will boot with ac adapter connected but not without it.
All the combos I could think of failed ie
- power on + vol up
- Power on + vol down
- power on + vol up + vol down
- power on +reset
- power on + reset + vol up
- power on + reset + vol down
- power on + reset + vol up + vol down
Nothings changing besides the fact it need ac adapter to turn on
(usb has been plugged in too)
Any ideas?
DreadPirateDan said:
OK so i got home early and just cracked it open (quite literally - a little tab snapped )
So all I can gather so far is that switching this switch to "off" just kills all power. The tab will boot with ac adapter connected but not without it.
All the combos I could think of failed ie
- power on + vol up
- Power on + vol down
- power on + vol up + vol down
- power on +reset
- power on + reset + vol up
- power on + reset + vol down
- power on + reset + vol up + vol down
Nothings changing besides the fact it need ac adapter to turn on
(usb has been plugged in too)
Any ideas?
Click to expand...
Click to collapse
Looking at that original post, I'm pretty sure that's actually just a battery power kill switch. Between the fairly obvious PCB labelling and the position on the board, it would seem to be a purely hardware function. If I got a closer look at the whole PCB (don't want to open mine up just yet), we might be able to see something enlightening, but at this point, I think its just a power switch.
Yeah my thoughts are similar to that. There is nothing else visible at that level of tear down, It must be there simply for sony techs to quickly turn off the battery without dismantling everything.
And until someone gives us a solid reason to pursue the internels, I'd recommend staying away from opening your own tabs. The way the tablet is clipped/taped together, it's either gunna come off easy, or be a ***** like it did for me and snap something. (there's double sided tape as well as clips.. took some firm force to peel it away and when it finally caved, it snapped open in the blink of an eye snapping 2 tabs! booo.)
I can't imagine there's really any promising hardware to boot to apx mode, when people have already gotten there on software alone
yeah, i also think that is related to battery. i disassembled my tab few times, tried some combinations with on/off internal switch, no luck with apx. also tried to ground 'charging' socket - all one by one pins of it. without result. also tried special service microusb cable, with 3 options with resistors - which i use for example for galaxy s - to force download mode - without luck on sony..
about grounding - testpoint - a lot of sony ericsson phones had backdoor in that way, simple grounding one point of service interface.
today i thought about nfx services - they're involved in all of that recovery mistery, decrypting update.zip, and i think that also in apx thing.
apx mode appeared when i was trying to get root - again after hmmm... 5-10 failed try. so maybe nfx logged some number of reboots, reboots in random time, when copying, when some adb commands where running, and forced device to apx mode?
of course its just a theory
Hello guys,
I've got a big problem with my I9300 and therefore I would like to ask here for any help. (If I'm in the wrong section, please move the thread to a correct one)
I had installed the Resurrection Remix ROM, v5.2.6. from 30.12.2014 and Googy-Max 2 recovery (CWM based) on my phone. I was using it for days and all worked fine.
One day I turned the phone off and I wanted to restart it. But it never restarted again; it ends up in a boot loop. It shows me the white Samsung Boot-Logo for some seconds, then a total black screen and the same thing repeats in a loop.
So I wanted to get into the recovery for wiping etc. but I couldn’t access the recovery. Nothing happens by pressing the relevant buttons. The device is still hanging in the boot loop. So I wanted to flash via Odin, but this isn't possible. I also can't go into the download mode. After pressing the relevant buttons, the green warning screen appears, which asks me if I really want to go to the download mode. But when I press volume up for "continue" or even if I don't press anything, the phone turns off and the boot loop with the white Samsung Logo starts again.
Therefore I ordered a USB JIG for forcing the device to go into download mode. When I plug the USB JIG in, the device actually goes into download mode but this status holds on only for a few seconds. After accessing download mode through the JIG, after a few seconds the phone turns off, restarts, (and because the JIG is still plugged in) the download mode appears again and it ends in a loop.
At first I thought maybe the power button is sticking and therefore the device turns on and off autonomous. But definitively I can negate it, because I opened the phone and removed the power button and nothing changed. Also by pressing the power button on the mainboard I can clearly hear the "click".
So I started a new attempt. Although the time, in which the device stays in download mode before turning off, is very short (only a few seconds), I tried flashing an other recovery, namely TWRP v2.8.3.0. So I prepared ODIN, plugged the JIG into the device, by appearing the download mode I switched cables and an other person clicked start at ODIN and it worked. So now TWRP is installed. Now I also can't get into recovery but after flashing TWRP there exist two little differences. First, after pressing the relevant buttons, TWRP appears for less than 1 second until the phone turns off. Secondly, when I plug the device in for charging, the Samsung charging logo appears for some seconds, then for less than 1 second appears a charging logo from Lollipop and the device ends up in a loop by displaying alternately the two different charging logos. Before flashing TWRP, the device booted in a boot loop (as I wrote above) by plugging it in for charging.
So the main question: how can I get my device work again
I tried telling you all details so that you have a better view of the problem.
Maybe I should flash a fully (stock) rom, but as I told you the download mode appears only for a few seconds. Flashing a recovery was possible, because the recovery file is very small - 7 MB. A full rom is much bigger and I think by flashing a complete rom, the device would turn off while Odin is flashing, therefore I ask first here for any assistance.
Thank you very much in advance!
beginnerteur said:
Hello guys,
I've got a big problem with my I9300 and therefore I would like to ask here for any help. (If I'm in the wrong section, please move the thread to a correct one)
I had installed the Resurrection Remix ROM, v5.2.6. from 30.12.2014 and Googy-Max 2 recovery (CWM based) on my phone. I was using it for days and all worked fine.
One day I turned the phone off and I wanted to restart it. But it never restarted again; it ends up in a boot loop. It shows me the white Samsung Boot-Logo for some seconds, then a total black screen and the same thing repeats in a loop.
So I wanted to get into the recovery for wiping etc. but I couldn’t access the recovery. Nothing happens by pressing the relevant buttons. The device is still hanging in the boot loop. So I wanted to flash via Odin, but this isn't possible. I also can't go into the download mode. After pressing the relevant buttons, the green warning screen appears, which asks me if I really want to go to the download mode. But when I press volume up for "continue" or even if I don't press anything, the phone turns off and the boot loop with the white Samsung Logo starts again.
Therefore I ordered a USB JIG for forcing the device to go into download mode. When I plug the USB JIG in, the device actually goes into download mode but this status holds on only for a few seconds. After accessing download mode through the JIG, after a few seconds the phone turns off, restarts, (and because the JIG is still plugged in) the download mode appears again and it ends in a loop.
At first I thought maybe the power button is sticking and therefore the device turns on and off autonomous. But definitively I can negate it, because I opened the phone and removed the power button and nothing changed. Also by pressing the power button on the mainboard I can clearly hear the "click".
So I started a new attempt. Although the time, in which the device stays in download mode before turning off, is very short (only a few seconds), I tried flashing an other recovery, namely TWRP v2.8.3.0. So I prepared ODIN, plugged the JIG into the device, by appearing the download mode I switched cables and an other person clicked start at ODIN and it worked. So now TWRP is installed. Now I also can't get into recovery but after flashing TWRP there exist two little differences. First, after pressing the relevant buttons, TWRP appears for less than 1 second until the phone turns off. Secondly, when I plug the device in for charging, the Samsung charging logo appears for some seconds, then for less than 1 second appears a charging logo from Lollipop and the device ends up in a loop by displaying alternately the two different charging logos. Before flashing TWRP, the device booted in a boot loop (as I wrote above) by plugging it in for charging.
So the main question: how can I get my device work again
I tried telling you all details so that you have a better view of the problem.
Maybe I should flash a fully (stock) rom, but as I told you the download mode appears only for a few seconds. Flashing a recovery was possible, because the recovery file is very small - 7 MB. A full rom is much bigger and I think by flashing a complete rom, the device would turn off while Odin is flashing, therefore I ask first here for any assistance.
Thank you very much in advance!
Click to expand...
Click to collapse
Check and make sure that your volume buttons and home button are not stuck also. If they are not, I would suggest a visit to a repair shop as your EMMC chip might be weak already.
beginnerteur said:
Hello guys,
I've got a big problem with my I9300 and therefore I would like to ask here for any help. (If I'm in the wrong section, please move the thread to a correct one)
I had installed the Resurrection Remix ROM, v5.2.6. from 30.12.2014 and Googy-Max 2 recovery (CWM based) on my phone. I was using it for days and all worked fine.
One day I turned the phone off and I wanted to restart it. But it never restarted again; it ends up in a boot loop. It shows me the white Samsung Boot-Logo for some seconds, then a total black screen and the same thing repeats in a loop.
So I wanted to get into the recovery for wiping etc. but I couldn’t access the recovery. Nothing happens by pressing the relevant buttons. The device is still hanging in the boot loop. So I wanted to flash via Odin, but this isn't possible. I also can't go into the download mode. After pressing the relevant buttons, the green warning screen appears, which asks me if I really want to go to the download mode. But when I press volume up for "continue" or even if I don't press anything, the phone turns off and the boot loop with the white Samsung Logo starts again.
Therefore I ordered a USB JIG for forcing the device to go into download mode. When I plug the USB JIG in, the device actually goes into download mode but this status holds on only for a few seconds. After accessing download mode through the JIG, after a few seconds the phone turns off, restarts, (and because the JIG is still plugged in) the download mode appears again and it ends in a loop.
At first I thought maybe the power button is sticking and therefore the device turns on and off autonomous. But definitively I can negate it, because I opened the phone and removed the power button and nothing changed. Also by pressing the power button on the mainboard I can clearly hear the "click".
So I started a new attempt. Although the time, in which the device stays in download mode before turning off, is very short (only a few seconds), I tried flashing an other recovery, namely TWRP v2.8.3.0. So I prepared ODIN, plugged the JIG into the device, by appearing the download mode I switched cables and an other person clicked start at ODIN and it worked. So now TWRP is installed. Now I also can't get into recovery but after flashing TWRP there exist two little differences. First, after pressing the relevant buttons, TWRP appears for less than 1 second until the phone turns off. Secondly, when I plug the device in for charging, the Samsung charging logo appears for some seconds, then for less than 1 second appears a charging logo from Lollipop and the device ends up in a loop by displaying alternately the two different charging logos. Before flashing TWRP, the device booted in a boot loop (as I wrote above) by plugging it in for charging.
So the main question: how can I get my device work again
I tried telling you all details so that you have a better view of the problem.
Maybe I should flash a fully (stock) rom, but as I told you the download mode appears only for a few seconds. Flashing a recovery was possible, because the recovery file is very small - 7 MB. A full rom is much bigger and I think by flashing a complete rom, the device would turn off while Odin is flashing, therefore I ask first here for any assistance.
Thank you very much in advance!
Click to expand...
Click to collapse
Your power button is failing, stuck in 'pressed' position. Try pressing repeatedly power button for several seconds, then release it completely. It shall bring it back to life. Visit your local service, or prepare tin, heat gun and soldering pistol. One button cost $0.2, they are selling them on eBay in sets of three (and 10, and 100....).
Happened to me some time ago, and video on youtube helped me to dismantle my phone, pull broken button out of it, and change it for new.
My phone was cycling like yours.
beginnerteur said:
Hello guys,
I've got a big problem with my I9300 and therefore I would like to ask here for any help. (If I'm in the wrong section, please move the thread to a correct one)
I had installed the Resurrection Remix ROM, v5.2.6. from 30.12.2014 and Googy-Max 2 recovery (CWM based) on my phone. I was using it for days and all worked fine.
One day I turned the phone off and I wanted to restart it. But it never restarted again; it ends up in a boot loop. It shows me the white Samsung Boot-Logo for some seconds, then a total black screen and the same thing repeats in a loop.
So I wanted to get into the recovery for wiping etc. but I couldn’t access the recovery. Nothing happens by pressing the relevant buttons. The device is still hanging in the boot loop. So I wanted to flash via Odin, but this isn't possible. I also can't go into the download mode. After pressing the relevant buttons, the green warning screen appears, which asks me if I really want to go to the download mode. But when I press volume up for "continue" or even if I don't press anything, the phone turns off and the boot loop with the white Samsung Logo starts again.
Therefore I ordered a USB JIG for forcing the device to go into download mode. When I plug the USB JIG in, the device actually goes into download mode but this status holds on only for a few seconds. After accessing download mode through the JIG, after a few seconds the phone turns off, restarts, (and because the JIG is still plugged in) the download mode appears again and it ends in a loop.
At first I thought maybe the power button is sticking and therefore the device turns on and off autonomous. But definitively I can negate it, because I opened the phone and removed the power button and nothing changed. Also by pressing the power button on the mainboard I can clearly hear the "click".
So I started a new attempt. Although the time, in which the device stays in download mode before turning off, is very short (only a few seconds), I tried flashing an other recovery, namely TWRP v2.8.3.0. So I prepared ODIN, plugged the JIG into the device, by appearing the download mode I switched cables and an other person clicked start at ODIN and it worked. So now TWRP is installed. Now I also can't get into recovery but after flashing TWRP there exist two little differences. First, after pressing the relevant buttons, TWRP appears for less than 1 second until the phone turns off. Secondly, when I plug the device in for charging, the Samsung charging logo appears for some seconds, then for less than 1 second appears a charging logo from Lollipop and the device ends up in a loop by displaying alternately the two different charging logos. Before flashing TWRP, the device booted in a boot loop (as I wrote above) by plugging it in for charging.
So the main question: how can I get my device work again
I tried telling you all details so that you have a better view of the problem.
Maybe I should flash a fully (stock) rom, but as I told you the download mode appears only for a few seconds. Flashing a recovery was possible, because the recovery file is very small - 7 MB. A full rom is much bigger and I think by flashing a complete rom, the device would turn off while Odin is flashing, therefore I ask first here for any assistance.
Thank you very much in advance!
Click to expand...
Click to collapse
As said your emmc chip maybe failing.
The dead boot thread maybe of interest to you.
Virnik0 said:
Your power button is failing, stuck in 'pressed' position. Try pressing repeatedly power button for several seconds, then release it completely. It shall bring it back to life. Visit your local service, or prepare tin, heat gun and soldering pistol. One button cost $0.2, they are selling them on eBay in sets of three (and 10, and 100....).
Happened to me some time ago, and video on youtube helped me to dismantle my phone, pull broken button out of it, and change it for new.
My phone was cycling like yours.
Click to expand...
Click to collapse
He said he has tested this and can also hear the micro-switch clicking.
scorpionhd2 said:
Check and make sure that your volume buttons and home button are not stuck also. If they are not, I would suggest a visit to a repair shop as your EMMC chip might be weak already.
Click to expand...
Click to collapse
Virnik0 said:
Your power button is failing, stuck in 'pressed' position. Try pressing repeatedly power button for several seconds, then release it completely. It shall bring it back to life. Visit your local service, or prepare tin, heat gun and soldering pistol. One button cost $0.2, they are selling them on eBay in sets of three (and 10, and 100....).
Happened to me some time ago, and video on youtube helped me to dismantle my phone, pull broken button out of it, and change it for new.
My phone was cycling like yours.
Click to expand...
Click to collapse
Darke5tShad0w said:
As said your emmc chip maybe failing.
The dead boot thread maybe of interest to you.
He said he has tested this and can also hear the micro-switch clicking.
Click to expand...
Click to collapse
Thank you very much for helping! :good:
So the question is, whether it's the power button's or emmc's fault...
I did a little searching and found this video. I've got exactly the same problem like the guy. At 1:06 following the boot loop, at 1:34 following the problem with downlod mode.
Although he thinks it's caused to the sudden death problem, but at least in my case I think it's wrong because months ago I did the eMMC Brickbug Check.
Also I noticed a probably important detail. When I put the battery in the phone, it automatically turns on without pressing the power button like in 1:04-1:09 in the video. Which normal working phone turns itself on by simply putting in the battery...?
So it must get a command for turning on - (possibly through a defect power button?)
@Virnik0, do you remember, if you could hear the micro-switch clicking on your phone before replacing the button on the mainboard?
beginnerteur said:
Also I noticed a probably important detail. When I put the battery in the phone, it automatically turns on without pressing the power button
Click to expand...
Click to collapse
Your power button is faulty, replace it before you try fixing anything else.
Thank you very, very much for helping! :good: :good: :good:
Truly the power button was fault although you could hear clearly the "click".
I unsoldered and removed the power module and (by startig with JIG and rebooting via ADB) the phone works as it should. :victory:
Now I'm trying to solder a new power button......it's a bit tricky
Again, thank you very much guys!
I had the same problem, pressed the button many times, and it helped. Thank you for your suggestions
Why this phone causing so many issues?
I'm was search how to fix this, but nothing doesn't work.
I have no idea what to do, and now I creating a new thread, maybe somebody can help.
Let's start.
I HAVE SECURITY ERROR when phone power on. After message disappear, screen goes down..
- No bootloader unlocked
- No rooted
- No usb debuging enabled
- No custom rom
- No custom recovery
This is the first time connecting with PC (Windows 10) and
- No driver (this is the most important issus)
I tried some drivers and installed but because phone only show error and go to shut down I don't know is this drivers working...
- Can't run fastboot
- Can't go to safe mode/recovery mode
- Can't do hard reset with hotkeys
The first thing is driver, while PC doesn't see phone I can do nothing.
Another important thing is that I cant do to safe mode. Without safe mode I cant do fastboot and flashing.
So maybe someone can help?
The Security Error means you installed an unsigned image on a device with a locked bootloader. You have to flash the original firmware following either this or this guide. You can get out of the security error by just flashing a signed recovery with fastboot, too.
EdwinMoq said:
The Security Error means you installed an unsigned image on a device with a locked bootloader. You have to flash the original firmware following either this or this guide. You can get out of the security error by just flashing a signed recovery with fastboot, too.
Click to expand...
Click to collapse
I can't put phone in download mode. Doesn't work.
Nothing happening. Only show Security error on the screen.....
When connect with usb charger phone dones'n charge.
----------------------------------------
Put the phone in download mode:
Jellybean bootloader:
Turn off the phone, remove the battery. Put the battery in, hold volume up+down and plug in the USB cable, after 1 second of the USB cable being plugged in, let go of volume down, keep your finger on volume up until you see S/W Upgrade. If you see the LG logo you failed, repeat the step again.
ICS bootloader:
Hold Volume up + down while plugging in the USB cable is the method I think.
--------------------------------------
Volume up OR down, I always forget that.
After a failed attempt to invoke DL mode and switching phone off(hard reset usually), toggling the phone's power once increases the chance for success next time. Same as taking the battery out each time.
After the restore of the stock rom phone should reboot. If it shows the stock recovery's screen instead, phone will be instable later and might brick when trying to root it. Then repeat the flash process and it should boot now.
Just remove the battery, put it again, then hold Vol UP and while doing that plug in the USB. You're now in Download mode.
SOLVED : I managed to charge the battery enough in the stock recovery (several hours and using buttons so it doesnt turn off by itself), then proceeded to boot twrp to charge more and fix everything.
ORIGINAL POST :
Hi everyone, I have an issue preventing me from making a tablet work.
Let me guide you through what I have done and can do :
- Acer Iconia Tab 10 (A3-A40) runnig Android 6.0
Problem :
I cannot boot TWRL through fastboot (fastboot boot recovery.img) because it gives me an error (low power - need battery charging). But there is no other way to get the tablet back .
Plus, I cannot charge it while pwered off as I get the following message (along with a battery charging icon) :
Orange State - Your device has been unlocked and can't be trusted - Your device will boot in 5 seconds .
This prevents off-mode-charging as it boots up the tablets after 5 seconds.
How did that happen :
Unlocked the bootloader, booted the tablet, had to use Magisk 13.0 modified by someone to work on the tablet (SU doesn't work.) and set the tablet up.
I then had a popup for Magisk having an update (to 16.0). Accepted it, which resulted in a bootloop.
Wanted to reflash the stock ROM and root it again, but it was 4am and people were sleeping, so I decided to do it the next day. Unfortunately, the battery died while I was asleep.
I can't run some commands in fastboot because it gives me an error : (not support on security).
What I have tried :
Charging the tablet in the (stock) recovery.
Charging the tavlet in Fastboot mode.
Charging the tablet while letting it bootloop.
fastboot getvar all doesnt give me any battery info.
I have all the files I need to make the tablet work (Stock ROM, root files, TWRP file...). I just can't get to flash anything, and the battery doesn't charge.
I just need either :
- A way to remove Magisk from stock recovery
- A way to bypass the fastboot (low power - need battery charging) error
- A way to charge the battery
- Or any suggestion you have
The fact that there is next to nothing about the tablet on the internet is very unfortunate and makes it harder to troubleshoot.
Thanks in advance for your help.
Did you try charging from a wall outlet, while the device is powered off?
HippoInWindow said:
Did you try charging from a wall outlet, while the device is powered off?
Click to expand...
Click to collapse
Yes. But everytime I do that, the device has a message stating "Orange State - Your device has been unlocked and cannot be trusted. Your device will boot up in 5 second".
I believe this prevents off-mode-charging by forcing booting up my tablet.
Strangly enough, fastboot tells me off-mode-charging is on, as of the following :
fastboot getvar all
(bootloader) off-mode-charging 1
FrWhyMe said:
Yes. But everytime I do that, the device has message stating "Orane State - Your device has been unlocked and cannot be trusted. Your device will boot up in 5 second".
I believe this prevenrts off-mode-charging by forcing booting up my tablet.
Strangly enough, fastboot tells me off-mode-charging is on, as when I do :
fastboot getvar all
(bootloader) off-mode-charging 1
Click to expand...
Click to collapse
Try charging if the phone automatically turns on, keep charging, then hold down the power button until it shuts down.
If it still reboots, try adb reboot bootloader, then choose power off. That should do the trick.
HippoInWindow said:
Try charging if the phone automatically turns on, keep charging, then hold down the power button until it shuts down.
If it still reboots, try adb reboot bootloader, then choose power off. That should do the trick.
Click to expand...
Click to collapse
It reboots before I can power it off manually with the power button.
And I cannot access adb as I only have access to the stock recovery and fastboot.
Plus, I can already choose "power off" in the stock recovery, and it stills boots up when plugged in.
SOLVED : I managed to charge the battery enough in the stock recovery (several hours and using buttons so it doesnt turn off by itself), then proceeded to boot twrp to charge more and fix everything.