Ok so I purchased a Galaxy tab 10.1 with LTE last Friday, I waited till today to try and unlock and root it. I found the unlock and root procedure but instead of the Tab going into fastboot mode where you get the USB and Backup options the unit simply boots as normal and it says safe Mode on the bottom left hand side.
I've been fidgeting with this thing all day trying to root it but it simply wont go into fastboot mode, ADB sees it just fine and the recovery menu is there but nothing elses. Has anyone else run into this issue.
Model: SCHi905UKV
Provider: Verizon
Version: 32GB
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Related
First off id like to say thanks in advance to any replies and also apologize if this has been posted previously (i searched and could not find anything that was helpful) I lurked around these forums when i had my x1 and im hoping you guys can be as helpful for me as you are for everyone else. anyway onto the issue
I used the superboot method to root my ATT US Streak. My intentions were to update to 2.1 following the steps in the "eclair working on my u.s. unlocked streak!" thread (wont let me put a link since its my first post)
after using fastboot to root the phone will boot up and function fine but recovery and fastboot no longer work. i tried flashing Koush's custom recovery and other things that require fastboot and the terminal just says "sending..." nothing happens no errors or anything, the cmd prompt just sits there and i need to remove the battery to reboot the device.
i then downloaded the Rom Manager apk from the market and flashed the clockwork recovery from there (it said i did anyway). when i load the recovery from boot (volume keys + power and its the stock recovery) and chose option 2 to flash modaco custom rom or even the stock dell rom it just goes to a black screen and i once again need to remove the battery to reboot.
the phone itself is still functioning fine when it boots up and everything works the way it should other than the home, menu, and back button lights flash in random orders, thats just annoying though. again any help is appreciated
so what should i try next?
EDIT: woke up this morning and now the device will not turn on. i tried starting to fastboot and recovery but still nothing. plug it into my pc and i get the "found new hardware wizard" for a Qualcomm CDMA Technologies MSM.
first real brick? ha that would be my luck
EDIT 2: a kid just ran through my work, grabbed my phone and threw it on the ground. it screwed up the 30 pin connector on the phone and the charger. im going to hurt somebody. phone is booting again though... put sd card back in and still boots fine
SOLVED: Dont know the technical reasons behind it but i had to reinstall the drivers and switch usb ports for every fastboot and recovery procedure
removed SD card and its booting up normally. any thoughts?
Currently bought a sch-i905 4g lte verizon galaxy tablet.
Boots normally, and functions.
Last night i was writing a bootloader through odin, and accidently had auto reboot checked. I was unable to write the modem/kernel that goes with it and now have a galaxy tablet that boots into the OS just fine.
The problem now is though that i can not get my tablet/computer to communicate in download mode it says "waiting for cable"
as well as my recovery is a black screen of doom.
Through rom manager when boot the tablet up i can see that clock work is installed just not boot properly..
I need some help here guys since this is outside my knowledge of fixing.
Any advice? :crying:
I have a Hong Kong version Galaxy S6 Edge which I have rooted through Pingpong root. Yesterday, after I installed TWRP recovery through Flashify, the phone could not boot up with this message: "Custom binary blocked by c-rom." I then searched on-line and noted that for our version of the Edge, there is a bootloader lock which must be unlocked before any custom rom or recovery could be installed.
There are on-line solutions for "Custom binary blocked by reactivation" which basically requires the phone to be booted into download mode and install through Odin. I have tried this method but the phone did not seem to react to Odin (not sure if this is due to C-rom lock). Also this method requires removal of the battery which is not possible for Edge.
http://forum.xda-developers.com/showthread.php?t=2486564
I brought the phone back to Samsung Service Centre yesterday but they simply refused to help and suggested that I replaced the motherboard for some US$350. I am sure that there is nothing wrong with the hardware and so did not accept their service plan.
I appreciate that this problem only exists in China version of the phones (see link below) which have C-Rom lock but still I I would be grateful if anyone in the forum could offer me some help here. Would be much appreciated.
http://forum.xda-developers.com/and...locker-apk-t3086609/post60948100#post60948100
Have you tried putting the phone in emergency mode and using the smartswitch recovery mode to try to fix the phone?
Thanks for your comment. As the phone cannot bypass the bootloader lock, I cannot switch it to emergency mode.
Odin works differently you have to boot into download mode by being powered off, then press power, home, volume down, then press up.
Do not connect to computer yet, open Odin, load your files, let it do its thing, then connect to computer, you will see added, then hit start.
Good luck.
Hi, today I tried to downgrade my Galaxy S3 from Cyanogen 12 to stock firmware (So from Lollipop to Jellybean) but now it's stuck on the bootsceen and I can't access the recovery mode, I can just access download mode.
Hi Hencick - Welcome to XDA.
I'll just naturally assume that you're familiar with flashing roms...
Were you running a custom kernel with CM?
Can you access adb functions with a pc?
I have a similar problem on my phone I discovered today. I just get the Samsung logo on screen, it goes off, then comes back (bootloader loop i guess).
It was just sitting on charge. It hasn't done anything for a while other than updates, now when I come to it, it's like this.
I can't get into recovery mode, adb mode, download mode or anything. Just the Samsung logo flashing up, then going and coming back up.
Is this recoverable?
As it it keeps powering up, then off, then back up I'm not even sure I can use Odin on it.
TIA.
Edit: Ok, I can get it into download mode it seems. Only, now I'm not sure what to do! lol
Hello. I have tried to install a custom recovery (TWRP) on my Samsung Galaxy Tab A 8.0" (SM-T290) today, however, it has not exactly gone to plan. I will run over exactly what I did, and what troubleshooting steps I have taken so far.
I downloaded this version of ODIN: https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
I unlocked the bootloader through the bootloader menu and enabled USB debugging after the tablet had turned on.
I downloaded and used the latest .md5.tar TWRP file from here: https://forum.xda-developers.com/t/...-2-for-2019-galaxy-tab-a-8-0-sm-t290.4185235/
ODIN Successfully flashed TWRP and the device rebooted. I attempted to get straight into the recovery by holding volume up, however, the screen remained black.
The tablet now cannot boot into recovery, download mode, etc, and only the backlight of the screen turns on. The tablet does eventually "boot up" and give the little vibration, at which point my computer recognises it, but I cannot see any files on the tablet. I can also see the tablet with ADB using the command "adb devices", however it tells me the tablet is "unauthorized", meaning I cannot use any ADB commands to attempt to reboot into recovery, download mode, etc.
I have tried disconnecting the battery and just powering on with the cable to no avail. I am assuming the device is fully bricked at this point, however, I would be appreciative if any possible solutions could be suggested, and if where I went wrong can be pointed out so I do not make the same mistake in the future.
Thanks in advance.
It's always risky to apply mods.
To get rid off of all mods you applied re-flash tablet's Stock ROM.
If this doesn't work for you then take it to authorized service center and let them try to fix it.
jwoegerbauer said:
take it to authorized service center and let them try to fix it.
Click to expand...
Click to collapse
They never fix anything. The only thing they do is charge you an absurd price and replace the motherboard or the entire tablet.
I'm on the same boat. Tablet can't get into download mode, just shows "This device has unauthorized software on it and is locked". Tried all possible button combinations to no avail.
SmiffyJ said:
Hello. I have tried to install a custom recovery (TWRP) on my Samsung Galaxy Tab A 8.0" (SM-T290) today, however, it has not exactly gone to plan. I will run over exactly what I did, and what troubleshooting steps I have taken so far.
I downloaded this version of ODIN: https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
I unlocked the bootloader through the bootloader menu and enabled USB debugging after the tablet had turned on.
I downloaded and used the latest .md5.tar TWRP file from here: https://forum.xda-developers.com/t/...-2-for-2019-galaxy-tab-a-8-0-sm-t290.4185235/
ODIN Successfully flashed TWRP and the device rebooted. I attempted to get straight into the recovery by holding volume up, however, the screen remained black.
The tablet now cannot boot into recovery, download mode, etc, and only the backlight of the screen turns on. The tablet does eventually "boot up" and give the little vibration, at which point my computer recognises it, but I cannot see any files on the tablet. I can also see the tablet with ADB using the command "adb devices", however it tells me the tablet is "unauthorized", meaning I cannot use any ADB commands to attempt to reboot into recovery, download mode, etc.
I have tried disconnecting the battery and just powering on with the cable to no avail. I am assuming the device is fully bricked at this point, however, I would be appreciative if any possible solutions could be suggested, and if where I went wrong can be pointed out so I do not make the same mistake in the future.
Thanks in advance.
Click to expand...
Click to collapse
Hi,
I have the exact same problem, did you manage to recover the tab?
Thanks heaps