Related
I need help guys,
I used Odin to root the phone and did my first custom rom which is the clean rom...it went through the process and when it was about to reboot i got the system software not approved by verizon and take phone to store
I have been told to odin back to stock but it wont let me. The stock image on odin wont work it says fail
I tried the first method and used odin in download mode to flash the stock image
Failed:
This is what I get
added
Odin V3 engine
File Analysis
all threads completed (succeed 0 / Fail 1)
In the Odin Download mode on the phone the top left reads as follow
Odin Mode (Red Letters)
Product Name (SCH-I535)
Custom Binary Download : Yes (1 counts )
Current Binary Custom
System Status Custom
Qualcomm Secureboot: Enable
One thing I gotta mention is that when I got the phone last week it had an OTA update from Verizon which I did install and then a few days later I rooted the phone and when I tried to use Clean Rom it gave me the dreaded Verizon message
Sounds like you didn't unlock the bootloader.
Ya your bootloader is locked again ... unlock it and redo the steps everything should be fine after that
Guys I know that the bootloader is locked but i cannot get back to stock to unroot phone and then unlock the bootloader
Odin recognizes phone but the stock image goes into fail mode right away
I cannot get into recovery and the only thing I can do is go to download mode and Odin but nothing else
http://forum.xda-developers.com/showthread.php?t=1840030&highlight=jtag
http://forum.xda-developers.com/showthread.php?t=1798850
http://rootzwiki.com/topic/29256-tutorial-rootrecoverybootloader-unlockicsjb-verizon-galaxy-s-iii/
http://www.android.gs/fix-bricked-verizon-galaxy-s3/
one of these may be able to help you ... i lost the original link i had but saved these for bootloader issues hope they help they should
Stranger_84 said:
http://forum.xda-developers.com/showthread.php?t=1840030&highlight=jtag
http://forum.xda-developers.com/showthread.php?t=1798850
http://rootzwiki.com/topic/29256-tutorial-rootrecoverybootloader-unlockicsjb-verizon-galaxy-s-iii/
http://www.android.gs/fix-bricked-verizon-galaxy-s3/
one of these may be able to help you ... i lost the original link i had but saved these for bootloader issues hope they help they should
Click to expand...
Click to collapse
You are aware he can Odin flashed the latest OTA instead of that you have provided. Here it is :http://forum.xda-developers.com/showthread.php?t=2046439. This will also help fix his phone being that it is recent. Forgot this link to get him back on track: http://forum.xda-developers.com/showthread.php?t=1974114.
i thought thats what he already tried? but yes you can odin any ota file being that an unlocked bootloader isnt needed.
When I try the VRBLK3 chain it goes into set up connection for like 10 minutes on Odin with a fail at the end each time
I'm not sure being ive never had that issues ... im sorry and good luck
try flashing odin stock ROM, not bootchain
NYGiants4Natic said:
When I try the VRBLK3 chain it goes into set up connection for like 10 minutes on Odin with a fail at the end each time
Click to expand...
Click to collapse
Did you put the file in PDA in Odin they only work if you checked PDA.
NYGiants4Natic said:
When I try the VRBLK3 chain it goes into set up connection for like 10 minutes on Odin with a fail at the end each time
Click to expand...
Click to collapse
I had a similar issue once. This helpful post by h3llsdr0id eventually got me up and running. Took a total of like 4 hours though lol.
http://forum.xda-developers.com/showpost.php?p=30569324&postcount=26
Make sure you have the correct files. This is for the original root66 so it's ICS. Once I booted up and activated I took the Verizon OTAs all the way to JB and then rooted/unlocked bootloader.
edit: I actually had to go back to ICS to reprovision my SIM so not sure you have to go through all of this. Try to odin stock JB ROM like mentioned above.
Thank YOU so much guys you have made my day.
After trying all last night and today I got it back to stock with the OTA file through ODIN. That is all I needed and it went right back to brand new stock phone using 4.1.1
WOW.
I thought I was going to have a dead phone.
Thank you all
Glad you got it up and working!!!!!
Yea I had the same problem but all it needed was a handy flash back to stock. The good thing with making these mistakes is that if it happens again you know what to do.
Sent from my SCH-I535 using xda app-developers app
I'm having the same problem and can't get into download mode
Gatanater said:
Yea I had the same problem but all it needed was a handy flash back to stock. The good thing with making these mistakes is that if it happens again you know what to do.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Hi there,
Could someone please help me. I bricked my phone 3 days go and went through odin and root66 stock to unbrick it. I installed CWR and backed up everything, then i purchased triangle away to reset the flash counter. When I did that I got the software not authorized by verizon error screen. It won't let me get into download mode or recovery. Can I still try to use odin? What should I do? I'd really appreciate some help today is the 4th day I have been trying to fix my phone, only to make it worse.
Thank you in advance
You have to get into download mode to use Odin. It will go into download mode, if you will search, there are ways to pull battery along with button combo to get it there. After rooting, use EZ Unlock 1.2 and that will unlock your bootloader without then unauthorized message from Verizon. Make sure you use only that version, the others don't work.
Re: I'm having the same problem and can't get into download mode
mj76 said:
Hi there,
Could someone please help me. I bricked my phone 3 days go and went through odin and root66 stock to unbrick it. I installed CWR and backed up everything, then i purchased triangle away to reset the flash counter. When I did that I got the software not authorized by verizon error screen. It won't let me get into download mode or recovery. Can I still try to use odin? What should I do? I'd really appreciate some help today is the 4th day I have been trying to fix my phone, only to make it worse.
Thank you in advance
Click to expand...
Click to collapse
Pull battery, hold volume down+home+power keys while you put the battery back in. If that's too many buttons to fumble with at the same time you can try pulling battery, put it back, hold all three keys while plugging it into your computer. My old phone worked that way, idk about the s3. You SHOULD get the download triangle and it asking you if you want to continue. Hit volume up to continue then plug it in and odin should recognize it. Get the stock rom image to flash in the PDA slot of odin. Accept the OTA's until you're up to date then unlock bootloader, root, then flash custom roms/kernels AFTER you've done the appropriate reading. Theres a sticky in development takes you step by step on how to unbrick, then unlock and root. Those should help once you get into download. Hope this helps! :fingers-crossed:
flammablepez said:
Pull battery, hold volume down+home+power keys while you put the battery back in. If that's too many buttons to fumble with at the same time you can try pulling battery, put it back, hold all three keys while plugging it into your computer. My old phone worked that way, idk about the s3. You SHOULD get the download triangle and it asking you if you want to continue. Hit volume up to continue then plug it in and odin should recognize it. Get the stock rom image to flash in the PDA slot of odin. Accept the OTA's until you're up to date then unlock bootloader, root, then flash custom roms/kernels AFTER you've done the appropriate reading. Theres a sticky in development takes you step by step on how to unbrick, then unlock and root. Those should help once you get into download. Hope this helps! :fingers-crossed:
Click to expand...
Click to collapse
Thank you for your response. I tried pulling the battery out and holding volume down, home and power keys at the same time while putting battery in, even as i plugged it into my phone, but nothing but the unauthorized error screen comes up. I should note that my phone is note 2 not s3. I apologize for posting it here, but this thread seemed to be just like the problem i was having.
Hey Guys,
Total noob here. Today I rooted my S3 on 4.3 with saferoot. That worked fine. Then I got goomanger and installed a recovery thing. I was trying to figure out how to install Slim Bean, because there were so many conflicting tutorials. I booted into downloading mode only to get the Yellow Triangle; I simply turned my phone off then back on to go back to stock software. So I went into goomanager and booted into recovery mode through that app. Then I got the same Triangle Error. This time when I turned off and on, it just tried to boot right back into this with the Triangle Error. I tried to use Odin to fix, but it won't even recognize my device or allow me to check the boxes that I need to. Please Help to fix this, Thanks!
Jawn_ said:
Hey Guys,
Total noob here. Today I rooted my S3 on 4.3 with saferoot. That worked fine. Then I got goomanger and installed a recovery thing. I was trying to figure out how to install Slim Bean, because there were so many conflicting tutorials. I booted into downloading mode only to get the Yellow Triangle; I simply turned my phone off then back on to go back to stock software. So I went into goomanager and booted into recovery mode through that app. Then I got the same Triangle Error. This time when I turned off and on, it just tried to boot right back into this with the Triangle Error. I tried to use Odin to fix, but it won't even recognize my device or allow me to check the boxes that I need to. Please Help to fix this, Thanks!
Click to expand...
Click to collapse
You can try removing your battery, then put it back in and try booting up again. otherwise, you may need to follow the directions to reflash the stock firmware via odin and download mode. Honestly, I'm surprised you didn't read more. All over on this forum, there are plenty of posts exclaiming that you should not attempt to install a recovery on 4.3. READ, READ, READ, READ. And when you're done doing that, read more because you missed something.
ddog511 said:
You can try removing your battery, then put it back in and try booting up again. otherwise, you may need to follow the directions to reflash the stock firmware via odin and download mode. Honestly, I'm surprised you didn't read more. All over on this forum, there are plenty of posts exclaiming that you should not attempt to install a recovery on 4.3. READ, READ, READ, READ. And when you're done doing that, read more because you missed something.
Click to expand...
Click to collapse
I cannot use Odin to reflash. I read the tutorial on here for that. Odin won't even register my device or let me check the boxes that I need to. Pretty Stuck here
Jawn_ said:
I cannot use Odin to reflash. I read the tutorial on here for that. Odin won't even register my device or let me check the boxes that I need to. Pretty Stuck here
Click to expand...
Click to collapse
Are you able to get into download mode? When you boot up your phone in download mode, you should see a prompt about custom os yada yada yada and that pressing volume up will enter download mode and volume down will reboot - see here - http://www.android.gs/download-mode-galaxy-s3/
You have to be in download mode in order to use odin.
Read the entire op and follow every step exactly how it tells you to. Even if you think you can skip a step DO NOT! http://forum.xda-developers.com/showthread.php?t=2586319
---------- Post added at 03:03 PM ---------- Previous post was at 03:01 PM ----------
If you can't get into download mode try this http://forum.xda-developers.com/showthread.php?t=2581166
There are a couple other guides on here but they are mostly just links to videos or ad infested download links and none of them worked for me so this is how I ended up getting it to work. Everything I used is attached
For the more experienced readers it's simple, flash TWRP using Odin, boot into recovery and TWRP will prompt you to root.
For the only slightly experienced:
Boot into Download Mode (Hold Vol Down +Power to turn on the Device)
Unzip the TWRP Recovery Image after downloading it below.
Connect your tablet to your PC, unzip and run Odin, click the PDA button and select the TWRP md5 file you just unzipped.
Begin holding the Volume Up button on your Tablet and hit the start button in Odin (this will ensure you reboot into the new recovery)
Once in TWRP if you select the reboot option under advanced you should be prompted to root your device if it's not already rooted. If that doesn't happen for some reason you can use adb to sideload the SuperSU zip I've attached, or put it on an sd card and find the flash zip from sdcard option in TWRP to flash it.
Thanks Justin! Works great. Someone should sticky this.
Luckily I had a Windows computer I could use for this, but my main machine is a MacBook Pro. I wish someone would do a nice clear walkthrough like this one for using Heimdall on a Mac.
To start I have rooted many phones but am stumped on this tablet. After getting it to start with holding the volume down and power key it stops on the downloading screen. Once I can get it to reboot I held the volume up and power key and got into system recovery. If I am not mistaken I can boot from here also. Right??
Thanks it was very useful!
Will this trigger the Knox 0x1 problem? I just got this tablet and I want to be able to take it in to Sprint for repairs if I need to.
Thanks!!!
Justin Buser said:
There are a couple other guides on here but they are mostly just links to videos or ad infested download links and none of them worked for me so this is how I ended up getting it to work. Everything I used is attached
For the more experienced readers it's simple, flash TWRP using Odin, boot into recovery and TWRP will prompt you to root.
For the only slightly experienced:
Boot into Download Mode (Hold Vol Down +Power to turn on the Device)
Unzip the TWRP Recovery Image after downloading it below.
Connect your tablet to your PC, unzip and run Odin, click the PDA button and select the TWRP md5 file you just unzipped.
Begin holding the Volume Up button on your Tablet and hit the start button in Odin (this will ensure you reboot into the new recovery)
Once in TWRP if you select the reboot option under advanced you should be prompted to root your device if it's not already rooted. If that doesn't happen for some reason you can use adb to sideload the SuperSU zip I've attached, or put it on an sd card and find the flash zip from sdcard option in TWRP to flash it.
Click to expand...
Click to collapse
Thanks for the help! This is my first root I've done myself and it works like a charm. Now my next step is to flash it to any carrier. Does anyone know how to flash the sprint device to a different carrier? If anyone could help me out, that would be greatly appreciated.
Thanks for this. I finally got a couple Galaxy Tab 3's (One 210 and one 217) to upgrade my girls from their Kindle Fires.
Really needed this root to remove all the factory loaded crap.
Thanks.
colt223 said:
Thanks for this. I finally got a couple Galaxy Tab 3's (One 210 and one 217) to upgrade my girls from their Kindle Fires.
Really needed this root to remove all the factory loaded crap.
Thanks.
Click to expand...
Click to collapse
I just recently got this tablet from a deal sprint had. What version was your tablet on before rooting? Right now mine is on 4.2.2, but there is an update out. I dont want to update if it wont work with this root.
slickdealers said:
I just recently got this tablet from a deal sprint had. What version was your tablet on before rooting? Right now mine is on 4.2.2, but there is an update out. I dont want to update if it wont work with this root.
Click to expand...
Click to collapse
I believe it was on 4.2.2 when I rooted. I will have to double-check that when I get home tonight.
What model number do you have? I had to use a different TWRP download for each one of mine, meaning I had to find a different one for the 210.
colt223 said:
I believe it was on 4.2.2 when I rooted. I will have to double-check that when I get home tonight.
What model number do you have? I had to use a different TWRP download for each one of mine, meaning I had to find a different one for the 210.
Click to expand...
Click to collapse
My model number is T217S. I tried to do some extra googling and came up with a post saying that the update after 4.2.2 installed KNOX on their tablet, which made their tablet come up with errors when trying to root. Based on your answer and what I found, I'm assuming I'm alright to give it a try. I do have one other question though. After rooting do you know if it would be possible to unroot incase I have to go back to Sprint with a problem?
slickdealers said:
My model number is T217S. I tried to do some extra googling and came up with a post saying that the update after 4.2.2 installed KNOX on their tablet, which made their tablet come up with errors when trying to root. Based on your answer and what I found, I'm assuming I'm alright to give it a try. I do have one other question though. After rooting do you know if it would be possible to unroot incase I have to go back to Sprint with a problem?
Click to expand...
Click to collapse
I am honestly not sure about going back, but I have had no problems. In fact, when I booted after root, something (sorry I dont remember if it was during root, or after) asked me if I wanted to disable Knox. I said yes, and smooth sailing ever since. I think it might have been the super user app itself that disabled it for me.
colt223 said:
I am honestly not sure about going back, but I have had no problems. In fact, when I booted after root, something (sorry I dont remember if it was during root, or after) asked me if I wanted to disable Knox. I said yes, and smooth sailing ever since. I think it might have been the super user app itself that disabled it for me.
Click to expand...
Click to collapse
Just tried it and successfully rooted! I got the same message that you described about Knox. It appears when you go to update SuperSu. Thank you for the help!
For anyone else wondering about going back to stock, I found a thread to the stock firmware.
http://forum.xda-developers.com/showthread.php?t=2512172
I found the answer in another thread. Flashing TWRP will trip Knox.
Didn't work for me
I did the TWRP stuff and all it did was trigger that warranty bit. Still no root.
colt223 said:
I am honestly not sure about going back, but I have had no problems. In fact, when I booted after root, something (sorry I dont remember if it was during root, or after) asked me if I wanted to disable Knox. I said yes, and smooth sailing ever since. I think it might have been the super user app itself that disabled it for me.
Click to expand...
Click to collapse
Yeah, same story here. After flashing TWRP then installing SuperSU first via the TWRP option by booting directly to recovery before OS after flashing TWRP through odin.....then once I clicked the SuperSU app after the OS loaded I chose first the "play" option to update SuperSU then the TWRP option to install the binary update. When it next booted it informed me that Knox was installed and asked whether to disable or not..I said yes and haven't had any problems at all...just trying to find a good ROM now^^
awesome thanxs for the info..... now if we could only get cm11 on this puppy
Root Failure, odd case
I have twins - they are both, identically:
Software Version: T217VPUAMH9
Hardware Version: T217S.04
Model Number: SM-T217S
Android Version: 4.2.2
Baseband Version: T217SVPUAMH9
Kernel Version: 3.4.0-1458241
Build Number: JDQ39.T217SVPUAMH9
Jim Trotter III-style, I-DENTICAL!
I successfully rooted one with:
1: Enable debugging
2: Boot into Download Mode (from poweroff, hold Vol Down+Power)
3: terminal: sudo heimdall flash --RECOVERY ./T217S.TWRP2.7.0.0.flashable/recovery.img
4: poweroff ; boot to TWRP. From TWRP, wipe [factory reset], then install: ./root/SuperSU-v1.93.zip
With the second (apparently evil) twin, at the heimdall command, I get:
...
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
0%
ERROR: Failed to send file part packet!
ERROR: RECOVERY upload failed!
Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...
Re-attaching kernel driver...
On the device, the blue progress bar grows to about 2% and stops.
I even tried using a different cable in case one had gone wonky, to no avail.
I am at a total loss here.
... and SUCCEED, but via strangeways
...
So, mounting frustration.
I tried instead a slightly different version of TWRP:
$ sudo heimdall flash --RECOVERY recovery/T217S.TWRP.2.7.0.0.recovery/recovery.tar.md5
This time the result is different, but still no success:
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
... but it stuck at 100% and did not continue. Device also stuck.
^C, hard reboot of device.
Tried again to double check, same result - sticks at 100%, progress bar on device sticks at somewhere around 5%.
Aware of the possible futility, but bored, I tried first one again:
$ sudo heimdall flash --RECOVERY ./T217S.TWRP2.7.0.0.flashable/recovery.img
SUCCEED.
So, apparently it has to be "knocked loose"?
Dunno. I'm in. Hope this helps someone else.
Root NB8
This won't work with NB8 EDIT: I was wrong this does work on NB8
Apparently had to reinstall the drivers a few times to get it to take on Windows. Still no clue what the issue was with Heimdall.
Hello,
Can someone please help me to go back to stock recovery WITHOUT factory reset?
I've installed CF-Auto-Root v1.0 and then flashed to lollipop 5.0.1.
Now, whenever I try to enter bootloader from the Fastboot Mode menu (by the Recovery Mode option)
It doesn't do anything.
Thanks ahead,
You seem to be a little confused.
"Whenever I try to enter bootloader from the fastboot mode menu by the recovery mode option..."
First of all. The screen that let's you cycle through recovery mode, start, power off & bootloader (what you call fastboot mode) is actually the bootloader itself.
When you're on that screen that allows you to select the different option you are already in the bootloader so selecting bootloader will just take you back to that screen over and over and over.
If you want to go to recovery, you hit recovery. You'll see an android with a red exclamation mark that says "No command" or something to that effect. I forget exactly what it says off the top of my head. From there, you hold the power button and press volume up and release and it will take you to stock recovery.
Also, performing a factory reset will not magically install stock recovery for you.
I'd highly advise you to stop using any kind of toolkits or "auto" anything until you are comfortable doing it manually by yourself.
I recommend reading the entire roll up sticky guide by rootSU in the general section to learn what you're doing.
Here it is;
http://forum.xda-developers.com/showthread.php?t=2784527
Read the entire thread. Read every thread linked in that thread as well. All of them. Otherwise your time on XDA is going to be very frustrating while you try to figure out how to recover from a bootloop or a wiped OS when if you knew what you were doing, would have never happened. Crawl. Walk. Then run. Baby steps. Start from the bottom and work your way up. Learn the basics before doing other things. Best of luck.
RoyJ said:
You seem to be a little confused.
"Whenever I try to enter bootloader from the fastboot mode menu by the recovery mode option..."
First of all. The screen that let's you cycle through recovery mode, start, power off & bootloader (what you call fastboot mode) is actually the bootloader itself.
When you're on that screen that allows you to select the different option you are already in the bootloader so selecting bootloader will just take you back to that screen over and over and over.
If you want to go to recovery, you hit recovery. You'll see an android with a red exclamation mark that says "No command" or something to that effect. I forget exactly what it says off the top of my head. From there, you hold the power button and press volume up and release and it will take you to stock recovery.
Also, performing a factory reset will not magically install stock recovery for you.
I'd highly advise you to stop using any kind of toolkits or "auto" anything until you are comfortable doing it manually by yourself.
I recommend reading the entire roll up sticky guide by rootSU in the general section to learn what you're doing.
Here it is;
http://forum.xda-developers.com/showthread.php?t=2784527
Read the entire thread. Read every thread linked in that thread as well. All of them. Otherwise your time on XDA is going to be very frustrating while you try to figure out how to recover from a bootloop or a wiped OS when if you knew what you were doing, would have never happened. Crawl. Walk. Then run. Baby steps. Start from the bottom and work your way up. Learn the basics before doing other things. Best of luck.
Click to expand...
Click to collapse
Thanks! How would you recommend to root my device? I don't want a custom recovery.
ahiel2 said:
Thanks! How would you recommend to root my device? I don't want a custom recovery.
Click to expand...
Click to collapse
Read, read and then read some more. Rooting and custom recoveries are not tied together.
ahiel2 said:
Thanks! How would you recommend to root my device? I don't want a custom recovery.
Click to expand...
Click to collapse
All the questions you have are covered in-depth within the guide I linked you to. You can boot into custom recovery without installing it with fastboot boot recovery instead of fastboot flash recovery. Root from there.
I have a GT-P1500, and I flashed a ROM .zip to /system with heimdall before I really grasped how flashing these kinds of things on samsung devices really works. Now everything is terrible.
I can boot into download mode and heimdall and odin both recognize my device. When I flash a recovery, I'm not able to boot into it even when I do the right key combinations and it says "booting recovery" in blue text in the corner on the samsung logo screen. Also, for some reason my download screen says "qualcomm secureboot: enabled" at the bottom of the other stuff. This is normal, right?
I've tried flashing the .tar.md5 firmware files from sammobile, but odin fails to flash them. I've tried kies, but it doesn't recognize my device. I've tried different computers. I've tried different recovery builds. I've tried everything I can think of.
Please help?
brickythebrick said:
I have a GT-P1500, and I flashed a ROM .zip to /system with heimdall before I really grasped how flashing these kinds of things on samsung devices really works. Now everything is terrible.
I can boot into download mode and heimdall and odin both recognize my device. When I flash a recovery, I'm not able to boot into it even when I do the right key combinations and it says "booting recovery" in blue text in the corner on the samsung logo screen. Also, for some reason my download screen says "qualcomm secureboot: enabled" at the bottom of the other stuff. This is normal, right?
I've tried flashing the .tar.md5 firmware files from sammobile, but odin fails to flash them. I've tried kies, but it doesn't recognize my device. I've tried different computers. I've tried different recovery builds. I've tried everything I can think of.
Please help?
Click to expand...
Click to collapse
It looks, like a locked bootloader. Which firmware you flashed?
Will try when I get home tonight, thank you for your kindness.
brickythebrick said:
Will try when I get home tonight, thank you for your kindness.
Click to expand...
Click to collapse
No problem my friend, but I just saw you mentioned p1500 and this p5100 thread. Sorry, i missed that too.
http://forum.xda-developers.com/galaxy-tab-10-1
Your problems will be sorted out there better than here.
Although I don't see any help or advice in your case. Since I am pretty sure you are on a carrier locked bootloader, sorry to be the one to break this on you which means you can't go custom and the carrier company is the real owner who doesn't want you to leave them.
Ah, 1500 was a typo. I meant 5100
Also, I can't do anything to the bootloader to fix this? Not even go back to stock?
brickythebrick said:
Also, I can't do anything to the bootloader to fix this? Not even go back to stock?
Click to expand...
Click to collapse
There must be something, you got me mixed up with P1500 . well, lets put few confusions to rest
what else do you have, I will need more details
Are you using a carrier locked tab 2 p5100?
or did you flash a carrier locked firmware on your unlocked tab?
you mentioned you flashed a rom zip from heimdall. which one exactly?
is your device booting up or you are just stuck in download mode?
The tablet boots, but the screen is just black and I can only try rebooting it. I can boot into download mode by holding power and volume down.
I do not have a carrier locked version, and I have not flashed any firmware packages as something eventually goes wrong and heimdall or odin stops there.
The device was booting into stock properly before I flashed the ROM incorrectly. I flashed the 5100 version of the ROM here: http://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-cyanogenmod-13-cm13-0-t3303800
brickythebrick said:
The tablet boots, but the screen is just black and I can only try rebooting it. I can boot into download mode by holding power and volume down.
I do not have a carrier locked version, and I have not flashed any firmware packages as something eventually goes wrong and heimdall or odin stops there.
The device was booting into stock properly before I flashed the ROM incorrectly. I flashed the 5100 version of the ROM here: http://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-cyanogenmod-13-cm13-0-t3303800
Click to expand...
Click to collapse
Update your bootloader to jelly bean. Flash from odin.
http://forum.xda-developers.com/showthread.php?t=2642005
Refer to this. Will work, no need to worry.
Sorry for replying so late, I have been really busy lately.
I am unable to update my bootloader: odin either outright fails or hangs on SetupConnection forever. After weeks of recearch and attempts, I see no answer. I guess I really am bricked forever? Damn.