I'm super new to rooting, apologies if the things I've done or questions I'm asking are stupid, and this website is a little confusing to navigate so I'm not sure if this question has popped up before.
Tablet Specs:
Samsung Galaxy Tab 4 10.1 (link i bought it from forever ago: apparently not allowed to post, will try to add the links in a comment)
Model Number: SM-T530NU
Android Version: 5.0.2
So I tried to root my tablet via this tutorial (which I'm apparently not allowed to add here until i've made 10 posts). Everything was going smoothly until around 6:15 in the video, where I hit start on the Odin program to download on my tablet. Unfortunately, Odin displayed "Failed!" instead of "Reset!", and the video gave no information on this part. The tablet seemed to be frozen in the loading screen. Out of frustration, I tried resetting it with power+vol up+home (probably a stupid move, in retrospect), and got it to turn off. When I turned it back on, the screen displayed the following information (apparently not allowed to post, images 1 and 2). After turning it off and trying to turn it on with power+vol down+home, I got the screen asking me to restart normally or continue, at which point I returned to the frozen loading screen (images 3 and 4 from the above link).
Is there anything that can be done to fix and continue rooting my tablet, or is it bricked? If it can be fixed/rooted, can someone link me to the proper way to do it or walk me through it? I don't care if it has to be factory reset, so if that allows for an easier pathway to get it usable, I'm fine with that.
Thanks for all the help, and sorry for the ****ty newbie questions/actions.
Alright well I'm not allowed to make comments with links until 10 posts either, so that's super ****ing stupid. If anyone can help me with the issue, I'll email/discord/whatever them the links that I was trying to add here
Related
I tried to flash the Overcome Rom onto my Tab, but it didn't work. I would turn it on see the Samsung Galaxy Tab screen, but then immediately go to a black screen.
So I tried to download my stock .tar file (M180S.DL08.0204-REV3-UPGRADE-CL761350_user.tar) and flashed it again. I went into download mode and put it into the .pda slot, and tried again. Still nothing. The same Samsung Logo then a black screen.
Then I read something about using P1_add_hidden.pit and then flashing the Roto JME_Full to get it back to life. So I did this, and then rebooted. This definitely did not work. Now I saw just a red line on the screen when I booted.
So anyway, I am able to get into download mode, but NOT recovery mode.
Also, when I try to charge it or plug it into the computer I can see the battery come up for a second, then it automatically goes to a black screen.
PLEASE HELP ME! I am a noob and don't know what to do.
Thanks.
UPDATE:
I tried out that program Heinberg(?). I don't remember the name and I am at work now. I was able to get a tar file somewhere and take out all the parts and flash. i am now able to see the Samsung Galaxy Tab logo, then the blue progress bar under it but it seems to freeze up after that and goes nowhere. I am also still unable to boot into recovery mode.
Good Luck. I am in SK and when I found out the other countries didn't have the DMB TV antennae it was a simple guess to assume there was software that the devs in other countries didn't know about.
I took mine to Samsung this week and they asked if I had downloaded anything recently. They did a hard reset and brought back my WiFi. Seems there are some laws in place that you have 14 days buyer's remorse to return it, followed by 30 days (or maybe 90) to replace a bad unit, and then 1 year free repairs. If you are within the first 2 time frames I would find a reason to return it as broken.
If someone can help you, I really am a noob when it comes to rooting and etc, then remind them of the DMB TV section and to watch out for it when they suggest something.
Hope this helps!
deadhead85: Have you found a way to fix it? Can you please share the firmware or at least a download link so i can "ressurect" my Korean Galaxy Tab?
Thanks in advance!
what happened with you?!!!
I've been searching for the last 6-7 hours straight for an exact answer. I have read http://forum.xda-developers.com/not...ass-lock-screen-pattern-password-pin-t2948336 a few times. I've Googled. I've YouTubed. Facebooked. All that.
I bought a refurbished AT&T Galaxy Note 4 (SM-N910A) from eBay that was unlocked so I could use Straight Talk service. I believe it is using 4.4 KitKat but I could be completely wrong. I've had the phone for a year now. I never had to use the lock screen before until today. Reason is is because last time I didn't and I left it around co-workers, I ended up with a few unsightly photos from my 400lbs manager. Hahah. So today, I decided to use the pattern lock and put it on charge as I was outside for about an hour. I came in, was able to take the pattern off. But noticed my swipe option had been greyed. So I put the pin on (using only four numbers). For some reason, I thought it would enable the swipe option. I was obviously wrong. So I went to change it from the pin to the pattern and my pin became unrecognized/incorrect. Thought it was only because of the option settings. So I locked my screen. Obviously an extremely bad idea.
I now cannot get past my screen lock. I have tried getting into it with my computer through USB, it won't connect. Not even trying a Mini SD mounted (won't read on my computer). I have tried ADM, but apparently it has been **** for the "Lock" option for over a year now. I didn't register the phone with Samsung so "FindMyMobile" isn't working. The option to enter my Google account info doesn't show up; even after 35 attempts. No idea how to use ADB. Have read that Windows OS is pretty much impossible to use debugging. Especially with Win10. I have nothing backed up as I never expected/thought this would/could happen.
Of course, like nearly every other person, I just want to save the thousands of photos I have accumulated over the year of having my phone. At least before I have to do a factory reset.
I am a hardcore n00b at going so in depth with phones. So Layman's terms would be extremely appreciated. Or direct links would be great as well.
I believe I have covered as much information as I can think of. If any more info is needed to help figure out this issue, please ask. And thank you to all in advance!
itsjoshwho said:
I've been searching for the last 6-7 hours straight for an exact answer. I have read http://forum.xda-developers.com/not...ass-lock-screen-pattern-password-pin-t2948336 a few times. I've Googled. I've YouTubed. Facebooked. All that.
...
Click to expand...
Click to collapse
I am no expert in this matter, but I believe factory reset is one option but you will loose all your data.
(non-root method- safest)
1. Power off
2..Keep holding the power button +volume up+home button together to go into recovery
3. Use volume keys to navigate and select factory reset
4. reboot and you are done
Second option is to root your phone. This will trip knox and your warranty will be void if you still have it
(Root Method)
The method I use to root is :
1. Download TWRP recovery for your mobile(search for your device) from https://twrp.me/devices/samsunggalaxynote4qualcomm.html site and keep it ready on your system
2. dowload super su 2.71 beta and put that into your external sd card using card reader.
3 Put your phone on download mode(power off and restart by holding power button + vol down + home)
4. Open latest version of Odin and connect phone to system via usb cable. Now "COM" in odin should turn blue
5. select tar file in AP section. Make sure repartition and reboot is unchecked just before flashing
6. click start
7.It will run for a few min and say pass when complete.
8.now remove your battery and insert after a few seconds. reboot into recovery by using step 2 in non-root method and you should login to twrp recovery
9.click install button and select super user zip u placed in sd card. flash it (u may have to uncheck signature verification). Now you are rooted!
10. wipe cash and reboot again into recovery
11. download the zip from :http://forum.xda-developers.com/not...ass-lock-screen-pattern-password-pin-t2948336 (Developed by Dr. Ketan)
12. Install this zip as you installed Super SU and you should be good to go.
There are so many links and step by step guides on how to root your device. You can choose your favorite. This is what I can think of and please don't hold me responsible if you damage or brick your device. Good luck!
Note : It would be better to keep super su and the zip from Dr. Ketan downloaded and moved to external SD card before you flash the recovery
itsjoshwho said:
I've been searching for the last 6-7 hours straight for an exact answer. I have read http://forum.xda-developers.com/not...ass-lock-screen-pattern-password-pin-t2948336 a few times. I've Googled. I've YouTubed. Facebooked. All that.
I bought a refurbished AT&T Galaxy Note 4 (SM-N910A) from eBay that was unlocked so I could use Straight Talk service. I believe it is using 4.4 KitKat but I could be completely wrong. I've had the phone for a year now. I never had to use the lock screen before until today. Reason is is because last time I didn't and I left it around co-workers, I ended up with a few unsightly photos from my 400lbs manager. Hahah. So today, I decided to use the pattern lock and put it on charge as I was outside for about an hour. I came in, was able to take the pattern off. But noticed my swipe option had been greyed. So I put the pin on (using only four numbers). For some reason, I thought it would enable the swipe option. I was obviously wrong. So I went to change it from the pin to the pattern and my pin became unrecognized/incorrect. Thought it was only because of the option settings. So I locked my screen. Obviously an extremely bad idea.
I now cannot get past my screen lock. I have tried getting into it with my computer through USB, it won't connect. Not even trying a Mini SD mounted (won't read on my computer). I have tried ADM, but apparently it has been **** for the "Lock" option for over a year now. I didn't register the phone with Samsung so "FindMyMobile" isn't working. The option to enter my Google account info doesn't show up; even after 35 attempts. No idea how to use ADB. Have read that Windows OS is pretty much impossible to use debugging. Especially with Win10. I have nothing backed up as I never expected/thought this would/could happen.
Of course, like nearly every other person, I just want to save the thousands of photos I have accumulated over the year of having my phone. At least before I have to do a factory reset.
I am a hardcore n00b at going so in depth with phones. So Layman's terms would be extremely appreciated. Or direct links would be great as well.
I believe I have covered as much information as I can think of. If any more info is needed to help figure out this issue, please ask. And thank you to all in advance!
Click to expand...
Click to collapse
If it's the reactivation lock then Factory reset will NOT help, it will just make you lose the data and still keeps you locked out.
Only "fix" i know for this is through a service center.
You could try to use ADB to pull the data so you won't lose anything, but i'm not sure if that would work (maybe through the recovery)
Good luck though :good:
So I've searched the forums for a while now, and being the noob I am, I do not know what i am looking for. I was trying to root my daughters tablets (Samsung Galaxy Tab 4 8''). I used the CF auto root. Everything list on his download page matched perfectly with what the tablet said in the about device tab (I'm talking about the model number and all the version number were exact. So i use Odin and everything went perfectly. The tablet went through its steps and Odin said PASS in big green letters. But it got stuck in the screen that says "Samsung". So I let it sit there for a while and finally i held the power button and it rebooted. It booted up fully but it kept popping up that all the apps were stopping. Touchwiz and all the storage "has stopped" along with tons of other apps. So i can't go home to get to the apps. I can go into settings and do stuff, but I cant get anything else to work. Is there anything i can go to get Touchwiz to work so that I can navigate? I can provide more info if anyone is willing to help me. Please this my daughters favorite toy in the world. I'll donate $15 to anyone who can help me get the tablet back functional. Thanks! I am such an idiot. I have no idea what I am doing and no clue why I decided to root her tablet.
Duster1d said:
So I've searched the forums for a while now, and being the noob I am, I do not know what i am looking for. I was trying to root my daughters tablets (Samsung Galaxy Tab 4 8''). I used the CF auto root. Everything list on his download page matched perfectly with what the tablet said in the about device tab (I'm talking about the model number and all the version number were exact. So i use Odin and everything went perfectly. The tablet went through its steps and Odin said PASS in big green letters. But it got stuck in the screen that says "Samsung". So I let it sit there for a while and finally i held the power button and it rebooted. It booted up fully but it kept popping up that all the apps were stopping. Touchwiz and all the storage "has stopped" along with tons of other apps. So i can't go home to get to the apps. I can go into settings and do stuff, but I can't get anything else to work. Is there anything i can go to get Touchwiz to work so that I can navigate? I can provide more info if anyone is willing to help me. Please this my daughter's favorite toy in the world. I'll donate $15 to anyone who can help me get the tablet back functional. Thanks! I am such an idiot. I have no idea what I am doing and no clue why I decided to root her tablet.
Click to expand...
Click to collapse
*UPDATE*
I was able to do a factory reset and start over. Although still have the custom kernel warning when it reboots. Is there a way to get rid of that? Thanks!
Do not use CF Auto Root for now, use chainfire's latest Systemless Root, in this time of writing, i can't find the link to his latest systemless root zip, flash it using a custom recovery.
About that kernel warning, it means that you modified something OR rather the CF Auto Root you flashed in the kernel, this happens also when you flash a custom firmware. You can't remove it. But beware if this warning comes out whenever you restart or power on the device, you might have triggered the KNOX status to 0x1 and that means your warranty is now borked and sammy can use it whenever you want a repair from them to deny your request.
Hi guys, got problem with my s7 edge.
It started when i was using google chrome browser.. when i tried to login a site, that website or the app kinda freezed.
I couldn't press back or home. So i did old way, by holding the power button.
After my phone is shut, i reopen by holding the power button. Then i see the red text message on the left corner on the boot screen.
Now i can't power the phone up anymore or even charge it???
it doesn't open up. Getting scared if it died. Any clue's why dis happen? Need help.
It died. Nothing you can do.
AndrOmega said:
It died. Nothing you can do.
Click to expand...
Click to collapse
Oh well, it is in reparation.
Don't listen to that douche. Check out updato.com to download the latest stock firmware package for your phone, and flash it with Odin. Just type "Odin v3.12.3" into Google and download it, the rest is pretty straight forward. Your phone is definitely not dead... it's amazing how easy it is to fix these problems and at the same time moderately depressing how useless posts like the one above yours seem to be what somebody would take the time to respond with instead of an actual solution to yours, and who knows how many hundreds of others', relatively minor technical difficulty.
Pro tip: If you want to try and keep your data/pictures/messages etc., try and flash the *CSC_HOME*.tar.md5 package for the CSC section as opposed to the plain-Jane *CSC*.tar.md5, it will preserve your userdata.
Yea dont listen do that dochebag. I got EXACT same error yesterday because I just opened Download Mode and did no mods at all. When I rebooted it gave me this error at doesnt boots. I have given it do the dealer to get it fixed. My phone was already moded to change single sim to dual mode. It was G935S BTW. I factory reset it but it didn't help so dont bother, try what rick said to perhaps save data if you want? But it can be fixed by flashing stock firmware, I just don't wanted to do because my internet sucks and I dont wanted to kill it as I am new to this device, bought 4 days back. Gl to you!
Long story short I'm working on loading a new (has not been used) LG V20 with Lineage OS and obviously have to pre-root the phone but I'm having problems and any help would be appreciated.
I'm currently working on trying to get DirtySanta working but in the command line when I run "run-as con" during ./step1.sh I get, "run-as: unknown package: con"
My questions are...
What am I missing?
Are there step by step instructions for completely re-loading these phones to LineageOS from factory to fully running?
The phone has the factory Android 8.0.0 and has NO data on it that needs to be saved. FastBoot is NOT working, I've tried many times.
Enable OEM unlock is not a option in the developer options on the phone.
Visseroth said:
Long story short I'm working on loading a new (has not been used) LG V20 with Lineage OS and obviously have to pre-root the phone but I'm having problems and any help would be appreciated.
I'm currently working on trying to get DirtySanta working but in the command line when I run "run-as con" during ./step1.sh I get, "run-as: unknown package: con"
My questions are...
What am I missing?
Are there step by step instructions for completely re-loading these phones to LineageOS from factory to fully running?
The phone has the factory Android 8.0.0 and has NO data on it that needs to be saved. FastBoot is NOT working, I've tried many times.
Enable OEM unlock is not a option in the developer options on the phone.
Click to expand...
Click to collapse
If you took the time to the dirty santa thread then you'd know that your phone's security patch date is date where ds has been patched, you need to be on a security patch date prior to Dec 2016
Sent from my LG-H910 using XDA Labs
Now I remember why I didn't post on these threads much. People just assUme that the posting person is a COMPLETE idiot.
This is a HELP forum where people come to get HELP and information, there's no reason to point fingers. A simple, "BTW that version you're running is a patched version, you'll need to roll it back to a prior, follow these links..." version would have done just fine.
With that I'd reply........
I realized I needed a older firmware last night when I was fighting with it for hours. I rolled it back to a firmware, dated 12-24-2016 and managed to get BadSanta to work but it caused my phone to go into a non-stop vibrate, it wouldn't complete boot and was basically bricked. I then found from another site that explained EXACTLY how to put the phone in download mode and then re-flashed the ROM (BTW, for those that don't know, you power off, hold the volume up and then plug in your data cable) but then put Android 7.0 Build number NRD90M.
The problem I am running into is everyone's information isn't is sync.
Some say how to proceed but don't say on what build number to proceed.
Some say to roll back to Android 7 Naugut but don't say which version because there are many versions of that version.
Personally I don't understand why a ROM can't be flashed via the download mode but then again I'm not a programmer.
So with that, after many hours I've made some progress but I am disappointed in how complicated and time consuming it is. I'm seriously considering a Pinephone for me and this phone (once completed) for my wife.
Right now I'm in the process of following this thread....
https://forum.xda-developers.com/v20/how-to/lgv20-vs995-verizon-aio-post-06-19-2017-t3624326
Later, after I get some work done.
Thanks for the reply though.
Well seems the BadSanta isn't working on my phone, as soon as I get past step3 and it reboots the screen is all scrambled and the vibrate motor runs continuously.
I've managed to get into TWRP once and followed the instructions but it bricks the phone at the LG startup screen.
Reloading the fastboot image doesn't do any good.
So seems I'm stuck with the stock firmware.
Can't say I didn't try.
Instructions I followed are here...
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
Visseroth said:
Well seems the BadSanta isn't working on my phone, as soon as I get past step3 and it reboots the screen is all scrambled and the vibrate motor runs continuously.
I've managed to get into TWRP once and followed the instructions but it bricks the phone at the LG startup screen.
Reloading the fastboot image doesn't do any good.
So seems I'm stuck with the stock firmware.
Can't say I didn't try.
Instructions I followed are here...
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
Click to expand...
Click to collapse
The vibration is normal if it's the VS995, which I'm sure you are using, right?
And the phone is not bricked, it's normal to see that warning at the start-up screen (about the device being corrupt....). Just be patient and give it time to boot.
The scrambled screen (static on boot) is also normal, just flash lineage 17.1, afaik it doesn't have static on the vs995
On a side note: double check the dirtysanta thread, you'll find most of these there
Really? I tried for many hours, multiple times and no go.
Yes it is the VS995, I guess I forgot to post that.
I did at one point get to a point where I could see a image behind all the garbled corruption on the screen and I did know that the corrupt notification was normal, that's how I made it to the TWRP once but I just couldn't get the screen fuzzy corruption to go away and the phone was still stuck vibrating non-stop.
Maybe I'm missing something?
And I only managed to get to the TWRP bootloader once.
Are all the features on the phone working on LineageOS 17.1?
I really wanted to get the phone not only up to date but limit the spying as much as possible with a device already designed to spy.
This phone is really for my wife, I'm thinking of ordering myself a PinePhone and giving that a whirl.
Visseroth said:
Really? I tried for many hours, multiple times and no go.
Yes it is the VS995, I guess I forgot to post that.
I did at one point get to a point where I could see a image behind all the garbled corruption on the screen and I did know that the corrupt notification was normal, that's how I made it to the TWRP once but I just couldn't get the screen fuzzy corruption to go away and the phone was still stuck vibrating non-stop.
Maybe I'm missing something?
And I only managed to get to the TWRP bootloader once.
Are all the features on the phone working on LineageOS 17.1?
I really wanted to get the phone not only up to date but limit the spying as much as possible with a device already designed to spy.
This phone is really for my wife, I'm thinking of ordering myself a PinePhone and giving that a whirl.
Click to expand...
Click to collapse
On stock, after it is done booting, press the power button once to turn off the main screen, then cover the upper left corner with your hand till the second screen turns off (abt 5 - 7 sec). Turn the screen back on and use your phone.
About lineage,