Database Users

HELP, Galaxy Tab 10.1 (Limited Edition) is in Infinite Reboot Loop

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!

[Q] SD Card mounting Issue!

I got my phone less than a year ago. Ran the 1 click root thing worked flawlessly since then and about a week ago my phone just decided to not work. All the applications i would open would force close and you couldn't do anything. So i turned it off and when i turned it on i got my problem.
The phone boots into the "S" and then it hangs at the loading screen until i pull the battery out.
I google searched a few times and i determined it was an SD card failure. The guide i followed told me to go into the 3 button combo thing and when i go to do a factory reset it gives me this "E:Can't mount /dev/block/mmblkOp1 (I/O error)
E:Can;t mount SDCARD:update.zip"
It's still on stock firmware, froyo i think?
Any help please?

Myhm... sometime happens.
It may be some issue.. try to flash clocworkmod 2.5.1.8.. if you are on Froyo, it may help. another solution may be (and I'd try it first) to apply Click

[Q] My phone is dead on stock...(due to rooting/unlocked failure?) Please help!

Hello XDAers,
I am a real noob at rooting or android-related, and a true one voided of any knowledge regarding anything IT- related.
So dear veterans, please go easy on me.
Due to my prior success of rooting and flashing my Nexus 4 successfully a few months back with no issues, I decided to give it a try to flash a custom ROM for my dad's LG Optimus L7 - which seemed an easy task compared to configuring my Nexus 4 - since there was no need for inputting any command lines or any dealing with the abd (using the easy shortcut, that is).
So, I followed the guide here: http://forum.xda-developers.com/showthread.php?t=1906133 ...
I first factory resettled the phone because it was bloated, then applied the "RunMe.bat" from the "What you desire!" folder. (Everything was already backed-up beforehand.) But the process didn't success until I've retried again and again by re-plugging the USB in because the application/PC couldn't detect the phone. In the same time, I was running KDZ_FW_UPD.exe in the background, so unexpectedly for me the phone shut itself and pushed itself to a vividly green emergency screen, then in a few seconds switched back to a screen of purple-white-blue glitches. I had to close KDZ_FW_UPD.exe without knowing what quite happened since it seemed to be the cause and restarted the process with RunMe.bat.
I didn't manage to "Restore" it first due to the fact that the phone stopped responding due to a lag asking for an encryption key. It was lagging so hard and I had to close the cmd around 5 tries while it was processing, but succeeded later on.
And then, to verify whether I've actually suceeded in rooting L7, I installed Root Checker from the Play Store. And again, for the first few tries the program froze on screen for a long period of time due to "system performance", but after rebooting and restarting the app a few times again, the ROOTING proves to be a success. Just to be sure, around this time I've reloaded KDZ_FW_UPD.exe and it suceeded.
So I went to install CWM and ES. CWM for recovery boot and ES for removing pre-installed system apps as the phone was lagging so badly. I've downloaded the CWM restoring(something like ~6.0.28?) first and tried fastbooting immediately right after, but instead of getting the fastboot menu I got a screen emptied in black with these words:
[5020] "Secure booting error"
[5020] "Cause: boot certification verify"
No hard keys could do anything on the presumed "fastboot", and so I had to hard boot again. I thought that it might be due to the lack of memory(checked on ES later on that it was 310~MB/2GB), and so I've used ES to uninstall a lot of system apps which I deemed uneccessary. So I've Googled a bit and it became apparent to me that that I've didn't unlock the device properly, so lurked around and found a file called L7CWM that is supposedly to resolve my problem, but I presume that it's the CWM recovery image that I've installed. So in the end, I didn't bother with it but kept it on tab just in case.
I repeated the same process with CWM again, but this time, the screen was joined with all kinds of flowery glitches. Restarted the device, and it went only downhill: now the Home launcher stayed all pitch black and nothing appeared. I waited a few minutes, but nothing there until the notification bar appeared. The home screen is apparently dead, and so are the menu keys. Switched to Nova Launcher(installed it just in case Home Launcher fails), and still dead. I couldn't access using any of the menu keys and had unusable launchers.
Hopefully I could still access to the settings from my status bar, but when I did, it started crashing immediately.
I've repeated the attempt a few times after restarting the device a few times, but nothing helped. It only got worse that the when the launcher did SEEM to work. It only showed the wallpaper without showing any of the icons/apps. And crashes again.
I could still access to the App menu via the settings, but couldn't open any of them and when I tried to uninstall them, the screen frozes immediately right after I gain access to the page (white page though) and gain this message: "Unfortunately Package Uninstaller Stopped!"
Then I convinced myself that the only thing I could do at the time was to factory reset the phone and then everything would go alright since I've just had to restore the system apps.
But then the black screen of death came right along with it:
"Secure booting error"
It seems that I'm out of luck... ... But just to check if I'm still left with resorts, I've downloaded the L7CWM file online...
... ...but it still didn't help.
So now I'm being left with no other choices other than asking for help. I never really understand what KDZ_FW_UPD.exe does since I had the LG Driver already before installing it, which I presume was for updating the phone to a newer or older version. And too complex tech articles are kind of alien for me.
EDIT(1 hour later): Okay, now I figured out the reason why L7CWM didn't work was because I didn't extract it to the right folder (after double checked via notepad that I was supposed to directly put it into the C:\ drive). Now it worked(?), but then it didn't.
After launching Flash_Bootloader.bat:
This message now appeared on the L7:
"Sorry!"
"SuperSU is not responding.
Would you like to close it?"
"Wait - Report - Close"
and a few minutes later
"Sorry!"
"Unfortunately, SuperSU has stopped."
"Report - OK"
Now I think the bugs till now happened was due to the fact that I've deleted a file that was required for me to launch apps... Now I just need the right fix.
After 5 minutes of screen inactivity the phone restarted by itself, kind of creepy... ...
Flash_Recovery.bat did nothing.
Reboot2Recovery.bat made it reboot but still struck on the same menu.
Nothing seems to be effective via the phone anymore, seems like I have to rely on abd but then again I don't know how... ... My dad is also f*cking pissed off ^ ^;...
__________________________________
I think that I explained the logs pretty precisely in case I missed something... I'll be very very very very very very thankful if someone could tell me what has caused my phone to fail though.
For references, here are the phone's specifications:
Model Number: LG-P705g
Android version: 4.0.3 (Stock)
Rooted:Yes (root checker)
Baseband version: MSM7227A-1-AA
Kernel version: 3.0.8-perf
Build number: IML74K
Software version: V10e-AUG-10-2012
If I don't get the phone fixed to being usable soon I think that I will get butchered real hard... ... Preferably needs a step-by-step guide made for toddlers... ...

remove the battery for 10 seconds,put it back pres VOL+ and VOL - same time and than press the power button.when you feel a vibration press for many times the button wich is down in right,try for many times and maybe it will working :}

Cydes said:
Hello XDAers,
If I don't get the phone fixed to being usable soon I think that I will get butchered real hard... ... Preferably needs a step-by-step guide made for toddlers... ...
Click to expand...
Click to collapse
simple answer for your
just download your stock rom
go to emergency mode
and flash that stock rom

[Q] i9505 won't boot into recovery or Android after it was "washed"

Hello guys, after a extensive research I decided to post thia thread and ask for help.
I recieved this phone (i9505 international version) from my cousin after it was washed in a wash machine inside his pants pocket'.
He told me he had sent it to a repair shop to have it cleaned and repaired before he sent it to me.
I recieved it, charged it's battery on a externalismo charger, put it back and it turns on ok, but gets stuck on The boot screen with a little blue message on the top that says "recovery booting" and never changes from there.
So , i tried The obvious, downloaded a official ROM, and tried to flash it. Flash was sucessful but i still had the same problems with it getting stuck in The first boot screen with the little blue text at The top.
Then i tried flashing The ROM with a pit file to rebuild The partittions. Flash was sucessful again, no errors at all, but I still had the same problem getting stuck at The boot screen.
The I tried flashing a custom recovery.
Clockwork recovery got me a error screen after i flashed it saying something got wrong during flash ask me to flash again.
Reflashed The oficial ROM with the pit file, tried again, same error. Had to reflash again.
Then I tried twrp.
This time something went different. I was still stuck at The boot screen, but The blue text changed to a red/orange 3 line text saying something like "Recovery is not seandroid enforcing".
I've read that this hás something to do with a locked bootloader and knox security.
Also, I've read that some people had this problems when their /data partition got corrupted.
So, I could not clear or format the data partition because I can't get into the recovery. The pit file never touches /data, and I don't really know if flashing the oficial ROM is enough to fix any problems in /data.
I have no idea if the data on /EFS is still OK.
And I'm still stuck with this problem.
Does anyone have any idea what else I can try in order to unbrick this phone?
I think the 3 possible problems are:
Corruption on /data
Corruption on /EFS (still it should boot)
Something wrong with bootloader vs rom version or region or something with Knox security.
Oh, I Aldo tried flashing another modem/radio. Got the same "something went wrong while flashing, try again" error.
Any help would be greatly appreciated.
Sorry if you find any typos, I'm fighting my word corrector (which is in pt-br) as I type this from my phone (n7000).
PS: flashed Samsung 4.4.2 zto (brazil) to the i9505

Another possibility is that the volume rocker shorted and when holding power it is also holding volume. Therefore booting recovery. I would check this by removing the volume rocker ribbon from the board and powering on. I know it sounds silly but could be the problem
Sent from my SCH-I605 using XDA Free mobile app

I openned the phone a few minutes ago to check this. Acctualy the button is soldered into the mainboard. I wasn't able to disconnect it.
I get a new multimeter (mine broke a few weeks ago) and check the contacts, but I don't think this is the problem, because if it was just a problem with a key getting stuck it should still boot into the recovery and do something, but it's not the case, it gets stuck in the bootscreen before booting and never really enters the recovery.
and when I go into download mode, there is a screen that asks me to presse vol up to go into download mode or vol down to cancel, I acctually have to press vol up to enter download mode, so it's probably not the problem. Thanks for the sugestion tho'.

can't fix my galaxy grand prime (dpi + no recovery)

it's been a week that i'm searching for a solution and i couldn't find anything and even any thread that could solve my situation probably becouse it's specific and with various weird problems.
frist of all i have a rooted rom for the SM-G531FX (android 5.1.1) and i can't remember wich model was before rooting it but i was a very similar code changing probably from G531FX to G530F?. but everything was ok i rootend my phone with no problem.
the real problem started like this:
i've changed the dpi of my phone using Root Essential changing it from 240 to 180.
immediatly after changing it the screen became with only the default background and nothing else, no icons, no notification bars, nothing, just a popup that said "unfortunately settings has stopped working".
the only thing i could do was swithing off the phone, (obviously the "reset" "switchoff" "airplane mode" was at loer dpi)
restarting it changed nothing and the phone still remain with the background with only the possbility of swithing it off.
the volume popup won't display but i could tell that the phone still works perfectly under the display becouse i recived messages (from telegram and whatsapp not normal messages becouse i couldn't use the display so i can't put the pin code to enter the phone so i removed the simcard) and also the volume controllers works.
so i decided to searching how to change the dpi from the pc.
i found that Adb could do it so i plugged in but unfortunately not worked, the phone remained in "unauthorized" state and i could not change the build.prop.
i started panic a bit so i wiped the cache from recovery mod.
After doing it i realized that i did a big mistake, now i can't connect usb in debug mod becouse of that.
i decided to reflash the rom i had use to rooting it thinking that could solve the problem.
midflashing odin had an error and the rom din't finished, it was stuck and i unplugged the phone from the pc and obviously the phone gave me an error in download mod (don't remember the error but was the one talking about Kies to solving the problem)
panic increasing couse i never had those types of problems.
i decided to flash the rom in Bootloader instead of AP in odin, that solved the problem of the error (later i found out that even in AP would have solved the problem)
i thought that wiping everything could have been the solution at that point so i restarted in recovery the phone but i could not access it probably becouse the previous BL flash, the phone stay with the Galaxy grand prime logo and on top in red "recovery is not seandroid enforcing". well done me
so i thought about reflashing a stock rom and found a rom w ww. sam mobile. co m / firmwares/galaxy-grand-prime/SM-G530FZ/WIN/download/G530FZXXS1BQC2/131851/ that pretty much fits my phone as i remembered the phone model, it was also an italian rom (i'm from italy) and with my very same phone company (WIND).
and finally odin fail flashing the rom so i remain with a phone with no acces to recovery, that boots normally but can't use the display becouse of just a value.
hope you could help me
thanks

Try to flash stock ROM of your phone with AP on Odin and the problem will be gone
Sent from my Redmi Note 3 using Tapatalk

Messed up everything first of all remove backcover and find what exact model it is..and find if you can go to download mod