Verizon Galaxy Tab 10.1 4G LTE (sch-i905)
So I got this tablet from a friend who said it was bricked, said I could have it if I got it working. So I plug it in and it turns on no problem, strange. wiped tablet and added a couple apps. Got busy at work and the tablet drain power. That's when I got to see it bricked, but still not sure why it booted for a bit for me.
Symptoms:
Boots to Samsung Galaxy Tab 10.1 splash screen (not the animated one after), sits there for ever.
Boots to Odin update mode
When booting to recovery I get a blank, back lit screen and nothing ever.
I've tried:
-Pushing clockwork mode to fix recovery
-I've had a hell of a time finding stock firmware for some reason (it isn't on sammobile), but I did find one eventually. I pushed it to the tablet via Odin, and it was successful, but rebooted to blank black back-lit screen. Have to hard boot and hold power buttun until I see the splash screen to get that far. I followed the guide on rootzwiki reposted on icsforums - www icsforums com/forum/showthread / 13525 (sorry new member can't post links)
-Followed another guide that involved draining battery completely, no go.
I don't care what firmware I end up on, or if I can use LTE (I won't anyway)
I'm a network engineer so I'm tech savy, but not heavy on Android OS. I'm looking for anything else I can try. I saw another method involving heimdall suite, but can't find the files for my model.
Any help or guidance is greatly appreciated.
@Juicebox4242
I had this problem on my gt-p7510...
What I ended up doing was wiping my sdcard..I must have had something corrupt in my file system or a kernel issue( still not sure which )..
Since you have no recovery..I think you can use odin to repartition ( I CAN NOT STRESS ENOUGH THAT THIS IS JUST A GUESS )..I have not tried it..but i will search after this post to confirm..I also believe there is a way using ADB..again not sure..
I just wanted to post this so you would know somebody was looking and to maybe give you a couple ideas to follow up on...I'll search around and see what I find
Edit...I believe ADB will only work with usb debugging checked...But you can flash a stock rom in odin with re-partition checked..you need a .pit file....I think...
Edit...Here is a link to a stock rom thread for you're device..It seems to have helped a couple people with their soft-bricked devices..just follow directions in OP..no repartition checked. I cant even find a .pit file to do a re-partition with for you're device..
http://forum.xda-developers.com/showthread.php?t=1342995 Let me know if this works for you..
Thanks for the post!! Really appreciate it.
That firmware is the one I found in the end and tried. Odin pushes it ok, but then still doesn't boot. In fact after pushing that firmware it boots to backlit blank screen, but when hard reset boots to splash screen.
I tried a pit file I found that I thought was the right one, but it failed when I used that so it must have been wrong.
Juicebox4242 said:
Thanks for the post!! Really appreciate it.
That firmware is the one I found in the end and tried. Odin pushes it ok, but then still doesn't boot. In fact after pushing that firmware it boots to backlit blank screen, but when hard reset boots to splash screen.
I tried a pit file I found that I thought was the right one, but it failed when I used that so it must have been wrong.
Click to expand...
Click to collapse
I have the exact same problem as you, except sometimes I can't my tablet to boot. I know it is a software problem because before I was messing with recovery yesterday, everything was working just fine. All I wanted to do was restore to factory settings and instead ended up bricking the device... If you find / know the answer, please do share.
Juicebox4242 said:
Verizon Galaxy Tab 10.1 4G LTE (sch-i905)
So I got this tablet from a friend who said it was bricked, said I could have it if I got it working. So I plug it in and it turns on no problem, strange. wiped tablet and added a couple apps. Got busy at work and the tablet drain power. That's when I got to see it bricked, but still not sure why it booted for a bit for me.
Symptoms:
Boots to Samsung Galaxy Tab 10.1 splash screen (not the animated one after), sits there for ever.
Boots to Odin update mode
When booting to recovery I get a blank, back lit screen and nothing ever.
I've tried:
-Pushing clockwork mode to fix recovery
-I've had a hell of a time finding stock firmware for some reason (it isn't on sammobile), but I did find one eventually. I pushed it to the tablet via Odin, and it was successful, but rebooted to blank black back-lit screen. Have to hard boot and hold power buttun until I see the splash screen to get that far. I followed the guide on rootzwiki reposted on icsforums - www icsforums com/forum/showthread / 13525 (sorry new member can't post links)
-Followed another guide that involved draining battery completely, no go.
I don't care what firmware I end up on, or if I can use LTE (I won't anyway)
I'm a network engineer so I'm tech savy, but not heavy on Android OS. I'm looking for anything else I can try. I saw another method involving heimdall suite, but can't find the files for my model.
Any help or guidance is greatly appreciated.
Click to expand...
Click to collapse
Did you ever get this fixed? I've had the same problem for months. I just gave up and put it away. I recently fixed a Galaxy Tab 2 and now I want to see if anyone else was able to fix this i905 not booting issue.
did anyone know the solution of this question
I apologize up front if this is has been previously asked. I found lots of helpful info on here searching through old threads but being a bit of a luddite I was a bit confused exactly which situation applied to me. I live in China and recently bought a s3 I9300I and attempted to root it using the chainfire method from the video on this site. Odin declared success but when the phone rebooted it just went back to download mode with a message at top saying, "Could not do normal boot, ODIN MODE." Turning it off and on, removing battery and retrying Odin flash produce no results. The most important thing of course is just to get the phone back to functioning but I'd also like it rooted if at all possible. I read that using Odin to install a custom kernel would root it and I would not be at all opposed to a good custom kernel. I read something about a binary counter that may need to be reset but that seemed to require doing something with the actual phone functions which don't seem to work. Odin still recognizes it when I plug it in and attempts to let me redo the rooting but it just shows a progress bar then reboots right back into download mode. Sorry if this is basic stuff but I'm kind of terrified of bricking this thing and am just not sure what the best course of action is here. Thanks for any help you can offer.
Chinese stock firmware is different to the international, there is a special thread in general forum on rooting etc.
Do you have a link to that thread? I have looked and cannot find anything that seems specific to this problem.
Please. Searching for "China" or "Chinese" gets me absolutely no relevant results. If this has already been covered can someone please direct me to the thread. I really need to get this phone working and am at a loss. Thanks.
Hi all, long time browser of XDA, first time poster. Up until now, every phone I've had, I've found the answers on this forum. I recently picked up a Samsung Galaxy Mega (SGH-I527M) which was non functional due to what I believe was an interrupted OTA update. When I first turned it on it said ']image size too large!! w:1080 h:1920 display image fail secure fail: kernel' I downloaded stock 4.4.2 from the sammobile website, and flashed it through odin, this got rid of the message, but sent the phone into a bootloop, I couldnt enter recovery, couldn't boot, just download mode. I then tried to use the Kies software to recover it, which brought back the image size error again. Anything stock i try to flash from sammobile results in a bootloop, the only rom that boots is a pre rooted stock 4.2.2. However, with this rom I have no wifi, bluetooth, sound, or USB. In an attempt to fix this I flashed the modem file from a 4.4.2 pre rooted stock rom. This returned my sound and bluetooth, but i still cant enable wifi, and no computer ive tried can connect to the phone via usb. As of now, I still have no wifi or usb. The hardware is completely fine, according to the previous owner, it worked right up until the failed flash. I've been trying to figure this out for 2 days straight now, and I'm at a loss. Does anybody have any ideas what might be causing this? I very much appreciate any help with this situation
Hi..try flashing this rooted rom by @krazykipa with odin 3.09 and it is a 4.4.2 kitkat rom NE5 ..download the rom with the link that is at the bottom of that post.
Link: http://forum.xda-developers.com/showthread.php?p=56268871
Sent from my SGH-I527M using XDA Free mobile app
Thank you for your reply. I had already tried the ROM from that thread to no avail. However, I did manage to restore this phone to working order. It turns out that all of my issues stemmed from an aftermarket screen replacement. Upon searching various forums, I cam! e across one that said to unplug the screen, boot the phone, and plug it back in once the screen would have normally timed out. Lo and behold, the LED turned blue and it didnt bootloop. Upon plugging the screen back in I was presented with my lockscreen, with no touch response. That confirmed my suspicions of an aftermarket screen. Browsing the web with new leads, I came across a video explaining how to fix, flashed megafire v16 as suggested, and the phone lives again! Seems samsung doesnt like when they cant take you for more money on OEM parts
Thanks again for the reply, and may I say just how lost I'd be without XDA?
Hello,
I wish I could explain my problem quickly and clearly, but I lost count on the amount of times I wiped, flashed and reset my Tablet so... I just hope someone comes up with a genius idea, because I'm desperate. I've tried everything.
Today I decided I wanted to try and find a better ROM I could install on my Ainol Tablet, and after doing some research I found out there was a 10.1 version of Cyanogenmod that was apparently quite popular.
I followed a tutorial I found on slatedroid.com (Flashed CM 10.1, Gapps and compatibility file) and only after I found out I just flashed a ROM built for the previous model of my tablet. When I reset it it came up as if it had done a Factory reset (same firmware but everything came up in chinese).
Then I went on and managed to find a tutorial for mine; repeated the process.
Right after doing that I re-read the tutorial (I would love to attach the link but I am a new user and am not allowed to...) and realised I was supposed to update my stock firmware to the latest version before flashing CM on it (apparently so they had the same kernel). Luckily, I had made a backup with TWRP so I went back to it and went looking on my PC for said firmware.
When I managed to find it, I realised the wifi on my tablet was gone. Whenever I switch it on, it goes back off after a few seconds. So no internet.
Then I thought I could just get that update file from my PC and copy it through USB. But that wasn't working either, my laptop will not recognise it whenever I plug it. The tablet won't even recognise a USB flashdrive.
Lastly, I realised there was a miniSD card port so I tried getting the file in through that as well. In this case, the tablet displayed a "preparing SD card" message but nothing happened afterwards...
I'm completely stuck. I have tried several times going back to Factory settings through TWRP, or reloading that backup I made, erasing Dalvik/Cache every single time, but the problems are still there. Everything else seems to be working though...
I did some research and it does look like I flashed a ROM with the wrong kernel so all the drivers are gone... (When the tablet is off and charging it displays a battery that used to stand vertically. Now it comes up horizontally...).
If that was the case, would anyone have any clue on anything I could do to fix it? Any files I could get rid of? Or maybe some secret menu on TWRP I haven't taken into account...?
Any ideas would be extremely appreciated. Please help! :'(
Thanks in advance.
Hello forum people, I need help to revive my S3 i9300, if you could help me I would really appreciate it.
I tell what I remember about the problem:
The phone was rooteado to be able to use it with any company since it was of movistar. a year ago with the rootking (we sent it to root), the phone was my dad and now has a new one, and it stopped using about 2-3 months.
Then I lent it to a friend who had just broken his cell, so I gave it to him so he has something until he buys one, but he told me that it did not work because he did not load and unload very quickly. He gave it back to me and I stopped using it until about 1 month ago, that I was left without a cell phone and I want to use it to have something.
The same thing happens as it does not load and it is very easy to download, BUT if you use the charger and cable of the Huawei ascend Mate 7 that my dad has, it charges perfectly and the cargo is not cut at all.
Well, seeing that this happened, I restarted it from the factory (I guess the root will be removed with that).
It was still branded and only loaded with the charger and the Huawei cable ...
Well now I tell what happened with what I did.
I install the samsung drivers for the compu, install odin 3.10.6 and under the recovery file that I put up, well I install everything but when I realized instead I read fast and instead of saying PDA said AP in the odin.
Well I try to turn it on and it does not turn on, I try to enter into recovery mode and it does not start.
Then I install another odin, version 1.30 and have a PDA, I do everything as I say start the phone in download mode, home odin, connect the phone to the computer, put the file in pda and give start.
He tells me that everything went well but still does not turn on and without going into recovery mode.
Say that when I do recovery mode (volume up, home and power) I see the logo of samsung and like that desinstegra, then it appears again and blinks in blue but as if it were broken and the logo moves. In short broken.
Then then install another recovery, https://dl.twrp.me/i9300/twrp-3.0.2-...0.img.tar.html
Now I want to enter into recovery mode but this appears and I want to touch some option that appears but nothing, as if the touch was dead.
And after that, it seems to me that I tried to change the Kernel and I put any but the one of my model by mistake.
Current status of the s3:
It lights normally but it takes a long time.
Enter DOWNLOAD mode (vol down, home and Power)
The screen touch does not work but it does show an image.
The buttons work, also the easy button of back and home.
DO NOT enter RECOVER mode (vol up, home and power) is frozen in the Samsung logo.
I want to make it work with any other rom that is functional except the STOCK. And that transforms into unlocekd
It does not matter if when I install a new ROM the files are deleted, I do not have anything in the phone.
Thank you very much to those who respond.
Only to get sure, that I understood you right:
after flashing the wrong kernel, your touch in twrp is not working anymore?
Will say the device is not reacting when you press a button on the screen with your fingers? If so than, I am afraid that your touch is broken. What kernel did you use? Can you post the name of the zip or tar file?
Beside of that, after flashing samsung stock, the reboot will last quite long. Maybe around 15 min till up to 25 or 30. And after flashing and before reboot, go to recovery and make a factory reset. Cross my fingers... :fingers-crossed:
rodman01 said:
Only to get sure, that I understood you right:
after flashing the wrong kernel, your touch in twrp is not working anymore?
Will say the device is not reacting when you press a button on the screen with your fingers? If so than, I am afraid that your touch is broken. What kernel did you use? Can you post the name of the zip or tar file?
Beside of that, after flashing samsung stock, the reboot will last quite long. Maybe around 15 min till up to 25 or 30. And after flashing and before reboot, go to recovery and make a factory reset. Cross my fingers... :fingers-crossed:
Click to expand...
Click to collapse
Hello, if I think that the Kernel had changed I do not remember exactly what it was because I downloaded it on a page written in Asian language by mistake and the Google translator confused the words and he said it was from the s3 but I think it was from the note 3.
The tactile does not respond exactly.
I did not understand him completely, he wants me to enter RECOVERY mode (it takes about 15-20 min to enter) and then do a factory reset?
I almost forgot to clarify that I had tried to do this from the video: https://www.youtube.com/watch?v=fA86_HFGx_w
Everything was installed perfect and I did it as is, except to delete.
Or reinstall the factory rom to see if it worked again.
If you flashed a kernel from note3 that the touch will be most probably minimum damaged and does not work proper anymore. I flashed mistakenly the kernel from the note2 and touch was broken, but maybe you were lucky and your touch is still working. No, passing into recovery should take only a few seconds, but rebooting into system after flashing samsung stock, then in recovery, then wiping and factory reset, could take a rather long time.
rodman01 said:
If you flashed a kernel from note3 that the touch will be most probably minimum damaged and does not work proper anymore. I flashed mistakenly the kernel from the note2 and touch was broken, but maybe you were lucky and your touch is still working. No, passing into recovery should take only a few seconds, but rebooting into system after flashing samsung stock, then in recovery, then wiping and factory reset, could take a rather long time.
Click to expand...
Click to collapse
Could you tell me how to do it please? I'm not an expert at all in changing ROM.
but you wrote that you already flashed something (?) via odin? I understood that you flashed samsung stock rom, beside kernel and twrp to proof, whether phone is working with original sw? If not than please check and search the i9300 forum section, there are a few of howtos and todo threads and posts which explains it even more better, that I could ever do
Edit: for example:
https://forum.xda-developers.com/galaxy-s3/general/samsung-galaxy-s3-sticky-roll-thread-t2344125 and from there for example
https://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
rodman01 said:
but you wrote that you already flashed something (?) via odin? I understood that you flashed samsung stock rom, beside kernel and twrp to proof, whether phone is working with original sw? If not than please check and search the i9300 forum section, there are a few of howtos and todo threads and posts which explains it even more better, that I could ever do
Click to expand...
Click to collapse
I used odin but I forgot how I had done and had followed the steps of a tutorial that I lost the link.
check my edited post above, now with links to guides and one of the best feature here on xda is the search button and that we have many things to read
rodman01 said:
check my edited post above, now with links to guides and one of the best feature here on xda is the search button and that we have many things to read
Click to expand...
Click to collapse
Hello, thank you very much for the links that you have passed me. They will be very useful, excuse me but I do not want to be irritating at all but I am really lost.
My only question is to know how to start reliving it?
I start installing CWN and then change the ROM?
I would recommend to start with flashing the original samsung stock sw via odin. To see that everything is working as it should. If it is so, especially your touch, than you can go ahead with routing, flashing an alternative recovery and testing custom roms, like leo or pie as you posted in the other thread. The time you are spending with writing here and in the second thread you could have already finished the sw flash and reboot to system to check the health of your device. Others than that procedure is a waste of time in my opinion. But thats your decision. On the other hand, we, or better I wouldn't spoon feed you further, because you can find almost everything for that years old device here with search, read read and read.
rodman01 said:
I would recommend to start with flashing the original samsung stock sw via odin. To see that everything is working as it should. If it is so, especially your touch, than you can go ahead with routing, flashing an alternative recovery and testing custom roms, like leo or pie as you posted in the other thread. The time you are spending with writing here and in the second thread you could have already finished the sw flash and reboot to system to check the health of your device. Others than that procedure is a waste of time in my opinion. But thats your decision. On the other hand, we, or better I wouldn't spoon feed you further, because you can find almost everything for that years old device here with search, read read and read.
Click to expand...
Click to collapse
Hello, I did the following, I had tried to re-install the stock stock a few days ago and it did not work, I did it for odin.
So what I did today was, install the recovery mode of ClockWorkMod and probe with the rom of MIUI 8 and that of Linage16, no installation. Then try with this: https://forum.xda-developers.com/galaxy-s3/development/rom-t3442868 And install correctly but it does not work, pass the Samsung logo but then when the ROM logo appears it stays there frozen and restarts ... it seems to me that officially the phone is dead.
Again: the right stock samsung sw should work if flash via odin didn't fail and, what I already mentioned, after flashing you did a factory reset in recovery. After that the reboot into system could take several minutes. Otherwise you can try it with repartition efs backup restore etc etc etc.
btw: newer custom roms, like leo-16, cannot be flashed with the old cwm recovery and cwm touch recovery, as you mentioned in the related thread, would not make much sense, if your touch is broken!?! If you do not want to go via samsung stock sw, then get a newer twrp, search for info which one is suitable, and guides how to flash custom roms, and flash the preferred one of your choice.