Related
Starting to get frustrated. When I got the Galaxy Tab 10.1 from I/O it originally had a severe back-light bleed which I described in this thread:
http://forum.xda-developers.com/showthread.php?t=1076349
Samsung Level 3 Support was quite awesome and sent out a replacement. The back-light bleed is still somewhat present, but not nearly as bad. So a few weeks have passed and ran into another major issue: it entered a infinite reboot loop.
I have only about 10 apps or so installed from the "Featured" section in the Android Market. I have never bothered rooting this, dealing with custom ROMs, or anything of that sort.
I just get white text on the display with a black background which says:
Entering upload mode...
Upload_Cause: undefined
Holding down the power button again just takes the tablet into a infinite reboot loop. I see the start up animation and the Samsung logo, then it repeats over and over.
Samsung just set up a RMA to get this re-flashed. Anyone else have this issue? Is there an easy solution to solve this without having to send it back in?
Thanks!
And I have the same issue here any help guys!!
same issue, looking for a solution
exact same issue. Any solution or suggestions?
I have the I/O tab, unrooted. I had the exact same issue. Just overnight the tablet went bonkers. The tablet would continually load the Samsung Splash screen over and over. If I tried to wipe the table, I got Entering upload mode, Upload undefined error. I sent my tab in after pulling my hair out trying to get a fix. I couldn't even work on the tablet because it would not hold a battery charge. Some process was constantly draining the battery. I personally wish thye would just give me a production tablet. I'm afraid that when I get it back, the problem will re-occur.
I have the regular retail version. I've had it for about 9 days and have used it every single day. Last night I downloaded 2 movies onto it and everything was fine. Today it would not power on one bit! I charge it over night so the battery shouldn't have drained. Anyone experience this before???
Nevermind: Fixed my problem by doing the following!
Press and hold the on button.
At the same time, keep a finger on the screen.
Keep watching and you might see a slight change of color on the screen.
Hold it down for 15 seconds or more. Be patient.
IO Boot Loop
same issue for me - working great then all of a sudden it froze, i rebooted and got stuck in boot loop
tried:
ODIN flash recovery - still boot loop
NVFLASH recovery - installed but cannot get into recovery mode -only fastboot and ODIN
FASTBOOT mode - adb not seeing device even though ODIN sees it - installed PDANet to get Android USB driver - still not seeing device
any thoughts?
sINCE THE release of touchwiz roms, a bootloader file is included as bootloader.tar.md5. Flashing this (repartition unselected in odin) gives you retail like options in boot screen with keys combo viz. recovery and odin. Try extracting and flashing the bootloader file from stock roms I uploaded.
COUNT:5 repetitions of this solution!Gladly, though one should bother to search!Or check the similar threads suggested when starting a thread.
thanks mughalgxt - where might this bootloader.tar.md5 be downloaded? To clarify did you mean by the extracting comment below that the bootloader you provided already contains this update?
also as for repetition - since i am still looking for a solution and some of those thread have the same symptoms (boot loop) but different solution methods (nvflash, odin, fastboot) - i thought it might make sense to add my description to my issue to apply additional context/clues
mughalgxt said:
sINCE THE release of touchwiz roms, a bootloader file is included as bootloader.tar.md5. Flashing this (repartition unselected in odin) gives you retail like options in boot screen with keys combo viz. recovery and odin. Try extracting and flashing the bootloader file from stock roms I uploaded.
COUNT:5 repetitions of this solution!Gladly, though one should bother to search!Or check the similar threads suggested when starting a thread.
Click to expand...
Click to collapse
I had uploaded a stock euro rom(check under arabic rom topic in development section), courtesy of samfirmware.com. You can extract the bootloader.tar.md5 file from the rom rar file. This will help you to force key into recovery as the boot options will be replaced from fastboot to recovery. Just make sure you don't select repartition while flashing with odin as that'd leave you bootloader locked!
Hope this clears up! Once in recovery, the options are endless!
lost2030 said:
I have the regular retail version. I've had it for about 9 days and have used it every single day. Last night I downloaded 2 movies onto it and everything was fine. Today it would not power on one bit! I charge it over night so the battery shouldn't have drained. Anyone experience this before???
Nevermind: Fixed my problem by doing the following!
Press and hold the on button.
At the same time, keep a finger on the screen.
Keep watching and you might see a slight change of color on the screen.
Hold it down for 15 seconds or more. Be patient.
Click to expand...
Click to collapse
WORKED like a charm!
I was going to update the latest "PACman v4.3 Build 1" from:
[ROM][Official][4.3 JSS15Q][PA3.95][AOKP][CM10.2]P.A.C True All in 1 ROM[NIGHTLIES]
but it required CWM 6.0.3.3, so I got it off:
[RECOVERY] [GT-i9505] [Discontinued] CWM+TWRP+STOCK-Recovery.zip's
So I flashed the touch version in recovery then when I rebooted back to CWM, I got a "secure fail: kernel ... system software not authorized by at&t" so I googled it and I thought I had to unlock the bootloader, so I used EZ-Unlock 1.4 and tried to reboot into recovery but it never turned back on.
Note that I have at least 70% of battery life and I have an extra battery, tried both but nothing. I tried removing the battery for 30 seconds then holding the power button with no reaction whatsoever.
Any suggestions to bring my phone back to life is welcome.
sey said:
I was going to update the latest "PACman v4.3 Build 1" from:
[ROM][Official][4.3 JSS15Q][PA3.95][AOKP][CM10.2]P.A.C True All in 1 ROM[NIGHTLIES]
but it required CWM 6.0.3.3, so I got it off:
[RECOVERY] [GT-i9505] [Discontinued] CWM+TWRP+STOCK-Recovery.zip's
So I flashed the touch version in recovery then when I rebooted back to CWM, I got a "secure fail: kernel ... system software not authorized by at&t" so I googled it and I thought I had to unlock the bootloader, so I used EZ-Unlock 1.4 and tried to reboot into recovery but it never turned back on.
Note that I have at least 70% of battery life and I have an extra battery, tried both but nothing. I tried removing the battery for 30 seconds then holding the power button with no reaction whatsoever.
Any suggestions to bring my phone back to life is welcome.
Click to expand...
Click to collapse
Sir, you are mixing things!
if you have the I9505 variant, no need to this "unlock bootloader"
boot into download mode and flash stock (see my sig)
samersh72 said:
Sir, you are mixing things!
if you have the I9505 variant, no need to this "unlock bootloader"
boot into download mode and flash stock (see my sig)
Click to expand...
Click to collapse
Yup, I know that now but it's too late. I already did and I can't seem to power my device on, no matter what I do.
Sounds like you hard bricked your phone.... Playing with bootloaders is one of the easiest ways of destroying your phone...
If you haven't done anything else you might be able to return for warranty BUT if the repair tech spots the tampering - flash counter going up - then you may have a bill...
As it stands you have an expensive paperweight....
sey said:
Yup, I know that now but it's too late. I already did and I can't seem to power my device on, no matter what I do.
Click to expand...
Click to collapse
try with a usb jig to force the device in download mode.
if not, see my signature for I9505 repair dead boot
Hi guys i think ive screwed up here massively. I was running stock lollipop on my note 3 and i attempted to gain root using odin and cf auto root hlte hltexx smn9005. After Odin said PASS i unplugged it but i may have done it too soon (not sure). Now when i turn it on it appears to automatically attempt to boot in to recovery over and over. I've removed the battery and tried to boot in to recovery and download holding all the button combinations and it doesn't boot long enough to get into any mode. Any advice to fix or is it completely bricked?
Artriel said:
Hi guys i think ive screwed up here massively. I was running stock lollipop on my note 3 and i attempted to gain root using odin and cf auto root hlte hltexx smn9005. After Odin said PASS i unplugged it but i may have done it too soon (not sure). Now when i turn it on it appears to automatically attempt to boot in to recovery over and over. I've removed the battery and tried to boot in to recovery and download holding all the button combinations and it doesn't boot long enough to get into any mode. Any advice to fix or is it completely bricked?
Click to expand...
Click to collapse
To root you need to flash twrp. Then flash supersu.zip. Don't think cf auto root working with lollipop.
So now try to flash twrp 2.8.5. If your phone boots successfully into twrp, flash supersu2.4.6.zip which your can find it by google.
If your phone still doesn't boot, odin whole firmware.
Rosli59564 said:
To root you need to flash twrp. Then flash supersu.zip. Don't think cf auto root working with lollipop.
So now try to flash twrp 2.8.5. If your phone boots successfully into twrp, flash supersu2.4.6.zip which your can find it by google.
If your phone still doesn't boot, odin whole firmware.
Click to expand...
Click to collapse
Thats the problem though i cant get the phone into download mode so i can flash stock or anything im stuck in a bootloop and i cant get it into recovery or download.
Artriel said:
Thats the problem though i cant get the phone into download mode so i can flash stock or anything im stuck in a bootloop and i cant get it into recovery or download.
Click to expand...
Click to collapse
Did you try pulling the battery? When using Odin the best (safest) way to do it is pull the battery (without the USB cable plugged in ) wait 10 secs or so then put it back in and hold down the DL mode keys. There seems to be a fundamental difference between a hot boot into DL and a physical restart via battery removal.
Happened to me the other day too. Just hold volume down + power + home and THEN plug in the battery. It worked like a charmo for me.
It worked
Wow battery out then insert worked!!! So stoked. You guys are awesome i thought the phone was gone so i went out and got a note 4 on my plan as i was out of contract lol. Oh well all good new phone and i can get the note 3 on ebay. Cheers guys!!!
Hello guys,
A friend of mine gave me his S6EDGE+ because it didnt boot anymore after he woke up. The night before that he installed an update but the phone worked fine after that.
The phone showed this message: http://imgur.com/a/cwLyM
I thought that it was easily fixed by flashing original 7.0 firmware but as you can guess i was wrong... It keeps rebooting right after the "Samsung Galaxy S6 Edge+" screen
So i tried to flash original 6.0.1 firmware but the same result
After that i flashed 7.0 again and after that twrp 7.0 but it never booted into twrp
So i flashed android 6.0.1 and the newest twrp for 6.0.1 but it still didnt booted into recovery and i am not able to boot in recovery.
After that i tried some older versions of twrp for 6.0.1 and it sometimes gave me the error: Recovery is not seandroid enforcing. I tried the same with 7.0 and older twrp versions, same results.
I also tried to flash 5.1.1 but i couldnt flash it.
What i also tried is to flash 7.0 bootloaders and after that 7.0 firwmare and the same for 6.0.1
I'm really desperate and dont know what to do anymore..
Current status: bootloop
I can enter download mode: http://imgur.com/a/XiS6Z
When you say you flashed original firmware, did you use odin to do it? Did you use the firmware from sammobile?
Apologies if it's shows in the pictures, but they aren't showing up on my phone.
1. how about if you try to reflash twrp, full wipe and install a rom?
2. Try fix it with Smart Switch with emergency frimware recovery / emergency device recovery. ?
kdogguk said:
When you say you flashed original firmware, did you use odin to do it? Did you use the firmware from sammobile?
Apologies if it's shows in the pictures, but they aren't showing up on my phone.
Click to expand...
Click to collapse
i can see that the images aren't working, ill fix that in a sec.
Yes i used odin and downloaded everything from sammobile because ive actualy paid them for de downloadspeed
justanpotato said:
1. how about if you try to reflash twrp, full wipe and install a rom?
2. Try fix it with Smart Switch with emergency frimware recovery / emergency device recovery. ?
Click to expand...
Click to collapse
ive flashed several versions of twrp but it never boots in recovery or i get the message recovery is not seandroid enforcing.
I also tried the Smart Switch method but without succes
no, u need learn some things about Binary Vercion, ima sure u have a B3 in this moments, so , download any firmware with Binary 3, if need more infor about that, check here http://forum.gsmhosting.com/vbb/f68...combination-compatibility-w-o-errors-2189001/
ruubs said:
ive flashed several versions of twrp but it never boots in recovery or i get the message recovery is not seandroid enforcing.
I also tried the Smart Switch method but without succes
Click to expand...
Click to collapse
You've never stated the results of your stock firmware flashing, using Odin. This is key, this tells you whether the firmware was flashed correctly or not.. If you picked the wrong stock firmware to flash, Odin will show it "Failed."
If your buddy just updated firmware, then it's likely he's on the newest one, but check in SamMobile to verify if it's accurate. If shows the most current firmware was updated in January or something then he might not be on the most current one, as this shows that he's behind on updating his phone, so it's uncertain which it last updated to.
If I were you, I'd verify first whether the Odin flash passed or not, prior to attempting any custom flashing.. After Odins finished flashing in the upper right corner will either show "Pass" or "Fail," it needs to show "Pass" before you can proceed to do anything else, as this confirm whether the stock firmware flashed correctly or not.
If it doesn't Pass, you have flashed the wrong firmware. Might be good to verify with your buddy, which carrier he had originally. If you indeed have a Samsung S6 Edge+, with the larger 5.7 inch screen, the model numbers begin as so, "SM-G928x" with difference being the "x" at the end, which coincides with whichever carrier it's on, (e.g. "A" for AT&T, "T" for T-Mobile" - U.S. carriers).
It wouldn't be a bad idea to confirm whether you're using the most up to date version of Odin, either. Don't remember what that is but a quick Google search under this topic would do it.
Just for shyts and giggles, you did verify that your PC recognizes the phone, right? And that it lists under "Device Manager" correctly, as well as Odin recognizing it after you plugged it in?
If it does "Pass," it should reboot by itself into the stock firmware since prior to flashing you selected "autoreboot" and "reset time" if it doesn't reboot correctly or gets stuck on the splash screen, unplug it from the PC and manually boot it into stock recovery. Do this by first pressing the following buttons at the same time and holding them till the phone powers off, power button, home button, volume up and volume down.. After it powers off, push and hold, power button, home button and volume up, till the phone boot to stock recovery, amd of course you can let go of the buttons/keys. Then using volume buttons to select factory reset and pressing the power button to confirm the selection. After it factory resets you can then select reboot to system and it should boot normally and you've recovered the phone.
The upper left corner in Odin will show the results of the flash, there shouldn't be a reason for it not booting if it indeed shows "Pass," cuz this confirms firmware flashed correctly, if it shows "Fail" then you flashed the incorrect firmware. You'll need to locate the right one so that Odin shows "Pass," otherwise you wont ever recover your phone, regardless of anything else you find interesting to flash, bootloaders, TWRP, root, ect.. Don't flash anything else till you get the stock firmware flashed correctly. If you're unable to accomplish this then, I'd recommend calling Samsung or your carrier, is it still under warranty? My charging port broke after 2+ years, I have insurance though w/ T-Mobile, called them to see what my options were, was planning on fixing it myself to avoid the $175 insurance deductible, if I made a claim, but as it turns out, since I have insurance, the phones still under warranty and per the CSR, it will continue to hace warranty as long as I pay the $7/month insurance. Thought most warranties are 12 months but I wasn't going to correct her if she was wrong so I went ahead with it and 2 days later new phone came and I sent my broken one back! Old phone has lil scratches on the screen, couple lil dings along the sides, obviously an older phone but now I gotta new one, ita flawless!
It won't to try if this don't work out..
Good luck
i have read through these forums for weeks and followed steps perfect but no version of Odin will succeed in doing a factory rom flash. i had the s4 rooted and uninstalled the touchwiz not realizing it was the launcher required to boot phone. since this happened i cant do a factory reset and odin will not work. in fact last time i tried odin it put my phone in a bootloop where as soon as i put the battery in it boots and continues to reboot. this phone has a locked bootloader and come stock with 4.4.2 i dont want to post a really long post with a bunch of info thats probably not needed so if more info is needed please ask. thanks in advance
If the phone constantly auto-reboots, then your power button is malfunctioning.
As for the other cases, use a different PC, Windows and/or USB ports. A cable switch is advisable too. And make sure you have the right firmware for the phone.
Any of those factors can make a change.
Also, unless it's a Verizon or AT&T phone, there's absolutely no possible way that thing has a locked bootloader.
I have a bootloop on the Samsung first logo with "Recovery Booting..." in blue on the top left (Samsung GT-I95026)
I have flash TWRP recovery, the phone don't want to boot on recovery, it's just bootlooping, flashed stock firmware with Kies, still bootloop, Odin, same thing
So after searching everywhere can't seem to find anything that can help, I assume it's dead then?..
bootloop stopped
Pwnycorn said:
If the phone constantly auto-reboots, then your power button is malfunctioning.
As for the other cases, use a different PC, Windows and/or USB ports. A cable switch is advisable too. And make sure you have the right firmware for the phone.
Any of those factors can make a change.
Also, unless it's a Verizon or AT&T phone, there's absolutely no possible way that thing has a locked bootloader.
Click to expand...
Click to collapse
phone has been sitting like 2 weeks with no battery and after your post i tried to boot to factory reset. it shows the recovery boot at the top of the screen but just goes to a half lit screen and does nothing.this phone wasnt even 2 weeks old when i bricked it. i use the factory oem cord plus have tried others. i have even tried a fresh install of win7 on my second hdd in this laptop with no changes to anything got my firmware here :sammobile.com/firmwares/search/sgh-1337
and yes this is an at&t phone factory unlocked with locked bootloader
soft brick fixable
Bastidn said:
I have a bootloop on the Samsung first logo with "Recovery Booting..." in blue on the top left (Samsung GT-I95026)
I have flash TWRP recovery, the phone don't want to boot on recovery, it's just bootlooping, flashed stock firmware with Kies, still bootloop, Odin, same thing
So after searching everywhere can't seem to find anything that can help, I assume it's dead then?..
Click to expand...
Click to collapse
i have read through these forums a lot trying to fix my s4 and im under the impression that if you can get to odin mode then the phone is "softbricked" and can be fixed.
freezes at at&t screen
galaxys4bricked said:
phone has been sitting like 2 weeks with no battery and after your post i tried to boot to factory reset. it shows the recovery boot at the top of the screen but just goes to a half lit screen and does nothing.this phone wasnt even 2 weeks old when i bricked it. i use the factory oem cord plus have tried others. i have even tried a fresh install of win7 on my second hdd in this laptop with no changes to anything got my firmware here :sammobile.com/firmwares/search/sgh-1337
and yes this is an at&t phone factory unlocked with locked bootloader
Click to expand...
Click to collapse
since that post i tried the factory reset and the phone just boots then stays frozen on the at&t screen
flashed and fixed
galaxys4bricked said:
i have read through these forums for weeks and followed steps perfect but no version of Odin will succeed in doing a factory rom flash. i had the s4 rooted and uninstalled the touchwiz not realizing it was the launcher required to boot phone. since this happened i cant do a factory reset and odin will not work. in fact last time i tried odin it put my phone in a bootloop where as soon as i put the battery in it boots and continues to reboot. this phone has a locked bootloader and come stock with 4.4.2 i dont want to post a really long post with a bunch of info thats probably not needed so if more info is needed please ask. thanks in advance[/QUOTE
i got my s4 flashed with stock rom from this thread:
forum.xda-developers.com/showthread.php?t=2674223
if anyone has the same issues i had with odin not working try that rom.....thanks for those of you who helped me
Click to expand...
Click to collapse
galaxys4bricked said:
if anyone has the same issues i had with odin not working try that rom.....thanks for those of you who helped me
Click to expand...
Click to collapse
Is there any way to unlock bootloader in ODIN? I have I9506 with 4.4.2 that was on it at first. Then i have updated it to 5.0.1 in OTA. So you say that I need to flash it in ODIN with 4.4.2 to make it work?
None of the Galaxy s4 phones have a locked bootloader except for the AT&T, Sprint, Verizon versions.
GT-I9506
S/N: RF8F20W841T
PDA: PL2 / PHONE: OJ2 / CSC: OK1 (NEE)
CAN'T BOOT IN TO THE SYSTEM (no matter what I can't make it to boot properly)
CAN'T ENTER RECOVERY (it's showing that's booting in to the recovery but instead of recovery it just restart)
CAN ENTER DOWNLOAD MODE (no problem with entering DM)
What I have done so far:
- Kies recovery with phone model number and serial number (still bootloop).
- Odin flashing STOCK rom from SamFirm download (still bootloop) (single and 4 files flash).
- Re-partitioning (flashing PIT file).
- Reflashing bootloder (still nothing).
- Tryed CWM, TWRP and other Recovery, non of them boot up.
Using those files to flash:
AP_I9506XXSDPL2_CL6069869_QB11747892_REV03_user_lo w_ship.tar
BL_I9506XXSDPL2_CL6069869_QB11747892_REV03_user_lo w_ship.tar
CP_I9506XXUDOJ2_REV00_CL1318424.tar
CSC_NEE_I9506NEEDOK1_CL6069869_QB7017077_REV03_use r_low_ship.tar
I would really appreciate help from someone more skilled then me.