Tried searching a little bit but couldnt find anything. Everything was fine, rooted, unlocked bootloader. then went to go reboot into recovery to flash a rom but accidentally booted into odin mode.
screen says, volume up to continue, volume down to cancel(restart phone).
if i press volume down, it reboots to the same screen again.
any help?
Pull and reinstall the battery?
Sent from my SCH-I605
tried that first thing. no help.
thanks
DSMRyan said:
Tried searching a little bit but couldnt find anything. Everything was fine, rooted, unlocked bootloader. then went to go reboot into recovery to flash a rom but accidentally booted into odin mode.
screen says, volume up to continue, volume down to cancel(restart phone).
if i press volume down, it reboots to the same screen again.
any help?
Click to expand...
Click to collapse
did you use Adam's method or the toolkit?
adams method
DSMRyan said:
adams method
Click to expand...
Click to collapse
What I think is your bootloader isn't successfully unlocked, and you're bricked. You need to odin flash back to original and use mskip's tool kit...it's quickest and easiest way to root, unlock, and flash custom recovery.
dcdgoth said:
What I think is your bootloader isn't successfully unlocked, and you're bricked. You need to odin flash back to original and use mskip's tool kit...it's quickest and easiest way to root, unlock, and flash custom recovery.
Click to expand...
Click to collapse
But with a Verizon note 2, dont you have to unlock with adams method first?
from mskips thread
NOTE: You will need to unlock the bootloader using instructions/files from Adam Outler before using the Toolkit. His instructions are very good and he has stated he does not want redistribution of anything. There is more information in the Toolkit after you select your model.
Click to expand...
Click to collapse
DSMRyan said:
But with a Verizon note 2, dont you have to unlock with adams method first?
from mskips thread
Click to expand...
Click to collapse
sorry. I guess you're right. It doesn't. I apologize. well....if the toolkit doesn't have option to unlock the device, then it's pretty much useless......
ok then, why does it say that in his thread then?
DSMRyan said:
ok then, why does it say that in his thread then?
Click to expand...
Click to collapse
did you odin flash back to stock?
no not yet, i odined back to a stock rooted image. didnt help much. either can get into odin mode, or it sits at the "galaxy note 2" splash screen forever. cant seem to get into a recovery.
will the 100% stock image be different? still DLing it.
DSMRyan said:
no not yet, i odined back to a stock rooted image. didnt help much. either can get into odin mode, or it sits at the "galaxy note 2" splash screen forever. cant seem to get into a recovery.
will the 100% stock image be different? still DLing it.
Click to expand...
Click to collapse
no....you need to visit this thread.
http://forum.xda-developers.com/showthread.php?t=2040264
use the first link.....it will put you back to original unrooted state. Restart the whole thing from scratch.
OK I'm downloading that now. Thanks
DSMRyan said:
OK I'm downloading that now. Thanks
Click to expand...
Click to collapse
You're welcome.
Related
Okay so I used "Odin3 One-Click Downloader Stock I-777 UCKH7" rooted with success and when i go to into clockworkmod, it says E:failed to verify whole-file signature and E:signature verification failed.. any idea's?
I've only had the device for a week.
I just got my device today, and have the same error.
I used SGH-I777-ATTGalaxyS2RootStockZedomaxKernel.tar with odin
Can anyone chime in on this?
Stop using rom manager?
Pirateghost said:
Stop using rom manager?
Click to expand...
Click to collapse
Okay? That doesn't really help. I uninstalled it. I was on 2.3.6 but now I seem to be on 2.3.4 after using odin for root.
Are you holding power, vol up, vol down to get into CWM?
getbuzzin said:
Are you holding power, vol up, vol down to get into CWM?
Click to expand...
Click to collapse
I'll retry, I was on 2.3.6 it seemed to downgrade my device, used the odin in the thread that didn't say it wasn't working with 2.3.6
http://forum.xda-developers.com/showthread.php?t=1285894
for Windows
getbuzzin said:
Are you holding power, vol up, vol down to get into CWM?
Click to expand...
Click to collapse
I did that, It booted into android system recovery. applied multi-csc, installed multi csc, then said can't access system/csc/ATT/system/ then said sucessfully applied multi-csc
Ok got it working, thanks. By stop using rom manager I guess you mean, don't use the reboot into recovery feature
kLAcK107 said:
Ok got it working, thanks. By stop using rom manager I guess you mean, don't use the reboot into recovery feature
Click to expand...
Click to collapse
What did you do? How do I back up my stock rom after gaining root?
xamadeix said:
What did you do? How do I back up my stock rom after gaining root?
Click to expand...
Click to collapse
guys
this is all covered in the damn stickies.....please read
Pirateghost said:
guys
this is all covered in the damn stickies.....please read
Click to expand...
Click to collapse
Show me.. and I'm set. I'm just trying to be careful.
I started fresh again and didn't mess with rom manager, just boot directly into Clockwork.
how do i boot directly into clockwork without rom manager?
Like he said above, you hold down vol up, down and power. The recovery menu you were getting is the android recovery menu, not CWM.
Do your rooting over and try it again. You should see the CWM logo when going into recovery, it is noticeably different.
kLAcK107 said:
I started fresh again and didn't mess with rom manager, just boot directly into Clockwork.
Click to expand...
Click to collapse
how do i do this? and do i need to flash something?
xamadeix said:
how do i do this? and do i need to flash something?
Click to expand...
Click to collapse
once again......
READ THE STICKIES.....
you are asking us to hold your hand, this is not a help desk, you help yourself
Pirateghost said:
once again......
READ THE STICKIES.....
you are asking us to hold your hand, this is not a help desk, you help yourself
Click to expand...
Click to collapse
Aware, I prefer to have someone that's aware of the situation rather I do something wrong... I'm not familiar with the process...
1. I was on 2.3.6, Flashed with Odin to gain root.
2. It downgraded me to 2.3.4. With root.
3. Just asking what to do next so I can back up my stock rom and be able to flash away.
xamadeix said:
Aware, I prefer to have someone that's aware of the situation rather I do something wrong... I'm not familiar with the process...
1. I was on 2.3.6, Flashed with Odin to gain root.
2. It downgraded me to 2.3.4. With root.
3. Just asking what to do next so I can back up my stock rom and be able to flash away.
Click to expand...
Click to collapse
i refuse to partake in holding your hand....
Pirateghost said:
i refuse to partake in holding your hand....
Click to expand...
Click to collapse
lol. great support.
i am posting this for my father. he tried to flash a kernal from this post http://forum.xda-developers.com/showthread.php?t=1540840 but clicked on the wrong file and this bricked his phone after a spent a long time fixing it prior to this. now it is stuck on the white htc boot screen. i can get to bootloader and recovery but every rom i try and flash i get the same results. can anyone help me unbrick my fathers phone please?
You're not bricked. Go to dev sticky section. Amaze bible thread
Sent from my HTC_Amaze_4G using xda premium
glacierguy said:
You're not bricked. Go to dev sticky section. Amaze bible thread
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Look for the restore to stock option, follow that.
Dark Nightmare said:
Look for the restore to stock option, follow that.
Click to expand...
Click to collapse
maybe i'm just blind and i hate to sound like a noob cause i'm not if this was my phone i could have fixed this already, but i don't see anything that says restore to stock. any chance you can clarify?
fixed the phone
i fixed the phone by flashing a kernal using hansoon's one click root tool. still having wifi issues any suggestions?
What kinda wifi issues?
Dark Nightmare said:
What kinda wifi issues?
Click to expand...
Click to collapse
The phone won't connect to wifi and also I can not get busy box to install.
mc2821 said:
The phone won't connect to wifi and also I can not get busy box to install.
Click to expand...
Click to collapse
Try fixing permissions and rebooting always works for me. If it doesnt works maybe its the rom u are using cheq on its tread for buggs and fixes
Sent from my HTC_Amaze_4G using XDA
if you keep having problems you can always just flash one of the RUUs and start the unlock process over.
Busybox won't install if you don't have superuser, re-root via hasoon's tool then try installing busybox, the wifi issue on the other hand is gonna require you to most likely flash back a stock RUU, or just try flashing any rom, see if that solves it.
relock the bootloader.
Backup the microSD card
Put the stock rom on the root folder of the SD card.
reboot into bootloader and let it install the stock rom. (it will erase the SD card i think).
Then re-root/re-unlock bootloader....flash away
Dark Nightmare said:
Busybox won't install if you don't have superuser, re-root via hasoon's tool then try installing busybox, the wifi issue on the other hand is gonna require you to most likely flash back a stock RUU, or just try flashing any rom, see if that solves it.
Click to expand...
Click to collapse
I have superuser and root access confirmed with a root checker. I can't get any roms to install nor can I find good directions to flashing an ruu. Does flashing an ruu bring you back to stock?
mc2821 said:
I have superuser and root access confirmed with a root checker. I can't get any roms to install nor can I find good directions to flashing an ruu. Does flashing an ruu bring you back to stock?
Click to expand...
Click to collapse
Yes, flashing a ruu restores everything to complete stock, try rooting again, then install busybox, after that, get 4EXT recovery, should be able to install any rom from then.
Dark Nightmare said:
Yes, flashing a ruu restores everything to complete stock, try rooting again, then install busybox, after that, get 4EXT recovery, should be able to install any rom from then.
Click to expand...
Click to collapse
I am having a lot of trouble with finding an ruu that works. I have tried several threads followed the directions to a T. the most recent i took the files from here http://forum.xda-developers.com/showthread.php?t=1617644 and followed these instructions for s on device http://forum.xda-developers.com/showpost.php?p=25303667&postcount=782. anyone have any other suggestions to help me get back to stock?
mc2821 said:
I am having a lot of trouble with finding an ruu that works. I have tried several threads followed the directions to a T. the most recent i took the files from here http://forum.xda-developers.com/showthread.php?t=1617644 and followed these instructions for s on device http://forum.xda-developers.com/showpost.php?p=25303667&postcount=782. anyone have any other suggestions to help me get back to stock?
Click to expand...
Click to collapse
What network are you on? And what version of android are you using?
Xda member Football has them in his signature. Amaze = Ruby
I think Krook has a thread too... Just search
Sent from my HTC_Amaze_4G using xda premium
Dark Nightmare said:
What network are you on? And what version of android are you using?
Click to expand...
Click to collapse
t mobile and running ginger bread 2.3.4
mc2821 said:
t mobile and running ginger bread 2.3.4
Click to expand...
Click to collapse
Download this: http://d-h.st/OIC
Rename it PH85IMG, place it on your sd card.
Power off your device, hold the volume down button and power it on, when it ask if you wanna update, press the volume up button, let it install, it should reboot when it's done.
Dark Nightmare said:
Download this: http://d-h.st/OIC
Rename it PH85IMG, place it on your sd card.
Power off your device, hold the volume down button and power it on, when it ask if you wanna update, press the volume up button, let it install, it should reboot when it's done.
Click to expand...
Click to collapse
do i need to be locked on unlocked? every time i re-lock the bootloader the phone wont reboot to anything other then the bootloader screen
mc2821 said:
do i need to be locked on unlocked? every time i re-lock the bootloader the phone wont reboot to anything other then the bootloader screen
Click to expand...
Click to collapse
Unlocked or not doesn't matter, just leave it unlocked.
I just got this in the mail today. Does anyone have any insights on how to unlock the bootloader and inject root? I had assumed 'fastboot' would work, but this has ODIN. I'm sure I could follow the steps on the original S4, but I don't know what the downstream effects will be.
Thanks!
----------------------------------------------------------------------------------
Edit: Please see this post: http://forum.xda-developers.com/showpost.php?p=44322019&postcount=70
Ok, just got done rooting my gs4 vzw dev edition. It was really pretty simple.
Steps from my win8 laptop were...
Install samsung drivers,
get adb working (android sdk doesn't seem to work on win8.. but just the adb files are all you need, google adb platform-tools or just use win7)
dl and push your superuser zip to the sdcard or external sdcard
dl odin 3.07 and extract to pc
dl and make tar.md5 of your favorite recovery. ( i personally like cwm )
Then all I did was... reboot phone in to odin mode... while phone is powered off, hold vol down + power
Start odin.exe
uncheck auto-reboot
click pda button, select the recovery file.md5
press start and let it finish, only takes a few secs...
once done.. reboot in to recovery, and flash the superuser.zip u pushed over to it.
Vol up + power to boot in to recovery. for me i just booted the phone normally... used "adb reboot recovery" then flashed superuser.zip.
reboot your phone and done.
good idea to make a backup while ur in recovery
If someone has hosting, i can send the files needed.
-r4ph
Click to expand...
Click to collapse
Okay, so I couldn't wait!
I followed the steps here: http://forum.xda-developers.com/showthread.php?t=2290798 and was able to gain root access.
I have yet to take the plunge on a custom recovery, but I'm sure I'll do that soon.
Additionally, the boot screen now has a picture of an "unlocked" lock, and the words "Samsung" "Custom". I guess they know that this has been flashed.
How did you order this prior to it being available on the Samsung Web site?
Sent from my DROID RAZR using Tapatalk 2
equake said:
How did you order this prior to it being available on the Samsung Web site?
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
It became available yesterday, and I got overnight shipping.
tithefug said:
It became available yesterday, and I got overnight shipping.
Click to expand...
Click to collapse
Is it full of VW blot ware?
rcb929 said:
Is it full of VW blot ware?
Click to expand...
Click to collapse
Yes. The only difference is that this has an unlocked bootloader by default.
tithefug said:
Okay, so I couldn't wait!
I followed the steps here: http://forum.xda-developers.com/showthread.php?t=2290798 and was able to gain root access.
I have yet to take the plunge on a custom recovery, but I'm sure I'll do that soon.
Additionally, the boot screen now has a picture of an "unlocked" lock, and the words "Samsung" "Custom". I guess they know that this has been flashed.
Click to expand...
Click to collapse
Mine comes tomorrow or Monday. So, despite it being unlocked, you still had to go thru that kernel replacement root method? Hmmm. I would have thought there would have been an easier way, no?
markwebb said:
Mine comes tomorrow or Monday. So, despite it being unlocked, you still had to go thru that kernel replacement root method? Hmmm. I would have thought there would have been an easier way, no?
Click to expand...
Click to collapse
Probably. But, I knew that would work.
tithefug said:
Probably. But, I knew that would work.
Click to expand...
Click to collapse
Couldn't you have just skipped the kernel replacement steps and just run motochopper step in that tutorial?
I think we need more insight from our all powerful devs on the best/easiest way to root a Dev Edition phone.
markwebb said:
Couldn't you have just skipped the kernel replacement steps and just run motochopper step in that tutorial?
I think we need more insight from our all powerful devs on the best/easiest way to root a Dev Edition phone.
Click to expand...
Click to collapse
Maybe. Either way it worked for me.
That being said, when I flashed the latest CM10.1-Nightly, the screen went blank (no boot animation). I restored my backup, so I still have a working device.
tithefug said:
Okay, so I couldn't wait!
I followed the steps here: http://forum.xda-developers.com/showthread.php?t=2290798 and was able to gain root access.
I have yet to take the plunge on a custom recovery, but I'm sure I'll do that soon.
Additionally, the boot screen now has a picture of an "unlocked" lock, and the words "Samsung" "Custom". I guess they know that this has been flashed.
Click to expand...
Click to collapse
I ended up doing the same as you and had to do all the steps too in order for it to work. Now I keep getting a warning message "this device has detected an unauthorized attempt..." trying to get me to reboot though. Can the master devs find something for the developer edition phones to have an easier time rooting?
And I also bought my phone and ordered it for next day shipping, so worth it!
tithefug said:
Okay, so I couldn't wait!
I followed the steps here: http://forum.xda-developers.com/showthread.php?t=2290798 and was able to gain root access.
I have yet to take the plunge on a custom recovery, but I'm sure I'll do that soon.
Additionally, the boot screen now has a picture of an "unlocked" lock, and the words "Samsung" "Custom". I guess they know that this has been flashed.
Click to expand...
Click to collapse
The boot message you see when you power on your device means your device is rooted. I have the same exact thing when I rooted mine. I got mine from a Verizon store.
Sent from my SCH-I545 using xda app-developers app
tithefug said:
Maybe. Either way it worked for me.
That being said, when I flashed the latest CM10.1-Nightly, the screen went blank (no boot animation). I restored my backup, so I still have a working device.
Click to expand...
Click to collapse
What backup method are you using: CWM or TWRP?
cmmelton2 said:
I ended up doing the same as you and had to do all the steps too in order for it to work. Now I keep getting a warning message "this device has detected an unauthorized attempt..." trying to get me to reboot though. Can the master devs find something for the developer edition phones to have an easier time rooting?
And I also bought my phone and ordered it for next day shipping, so worth it!
Click to expand...
Click to collapse
Search for the phrase used in the notification. It had to so with SEAndroid. You have to delete/rename KNOXAgent.apk, KNOXAgent.odex from /system and com.sec.knox.seandroid from /data/data
Have fun!
markwebb said:
What backup method are you using: CWM or TWRP?
Click to expand...
Click to collapse
TWRP. I installed it using the GooManager app.
tithefug said:
TWRP. I installed it using the GooManager app.
Click to expand...
Click to collapse
OK, thanks. I am just noticing a thread on TWRP issues and am nervous about it. However, you were able to back up the stock out of the box ROM and then restore it w/o a hitch?
markwebb said:
OK, thanks. I am just noticing a thread on TWRP issues and am nervous about it. However, you were able to back up the stock out of the box ROM and then restore it w/o a hitch?
Click to expand...
Click to collapse
Yep. I'm going to try CM again in a little while. Now that the official camera/gallery is out, I have less reasons to. But the ridiculousness that is the notification pane might just send me over the edge.
tithefug said:
Yep. I'm going to try CM again in a little while. Now that the official camera/gallery is out, I have less reasons to. But the ridiculousness that is the notification pane might just send me over the edge.
Click to expand...
Click to collapse
Was just wondering if you tried CM yet?
markwebb said:
I think we need more insight from our all powerful devs on the best/easiest way to root a Dev Edition phone.
Click to expand...
Click to collapse
I would also like to see the best/correct way to root the Developer Edition.
markwebb said:
Was just wondering if you tried CM yet?
Click to expand...
Click to collapse
Not yet. It's going to have to wait until tomorrow. Sorry.
It's been 3 days I've been up and down the forums, was on CM11, dirty flashed over the nebulas, ran into a few problems decided to go back and make it a clean flash, got 4.1.1, couldn't find one CASUAL that worked, went to 4.1.2, same problem, Yes i tried other cables, other computers, no difference.
Then updated 4.3 boot looped all kinds of problems tried Nand Erase All, didn't work, one way or another root66 stopped working. nothing would flash, it would all fail or if it did say it worked it just boot looped,
I605VRUEMJ9_I605VZWEMJ9_I605VRUEMJ9_HOME.tar.md5
To work. So now I'm 4.3 Stock, with no root.
I want to get back to Nebulas,
I want to take this step by step because it's been a nightmare and I can't find any solutions to questions that have been asked before.
From what I research the next step is to flash:
sch-i605-16gb.pit file
+
KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.tar.md5
But when I try I get sboot.bin fail. Got a tip somewhere to flash the just the PIT, this actually fixed it without needing to flash anything else.
Now I know I'm down grading so it's going to boot loop because nothing is compatible. Boot into recovery and do a wipe to fix that. I boot into the OS just to make sure I'm doing 4.1.2. Which it is. and enable usb debugging.
Now to root and bootloader.
I try the newest verison of CASUAL R991b-JenkinsBuild
I get Error Failed to confirm end of pit file transfer
Pit Upladoing Failed
ok, so I pull battery and reboot. Trying R515b because that's the one in the tutorial:
I get Pit upload successful
Error: Bootloader upload failed!
This corrupt the bootloader and it will fail the boot, taking a step back and reflashing the mc3 fixes this.
Then I try this tip "most times you will need to delete and uninstall the Samsung Mobile usb from your Computer's device manager while ur device is connected already in download mode. i failed several times to execute casual successfully until i did this and it worked like charm!"
That didn't do anything, Tried verision 535 same results.
Said screw that I'll just flash some Root and recovery. But it always fails to flash recovery.img or if i put in the PIT and say repartition it will fail after the NAND Write Start. I've tried
openrecovery-twrp-2.6.3.1-t0ltevzw.img
CF-Auto-Root-t0ltevzw-t0ltevzw-schi605.tar.md5
philz_touch_6.07.9-i605.tar.md5
and none work.
Any idea what I should do at this point? Everything fails the only thing I can do is flash 4.1.2 and 4.3 reliable.
In the middle there you say at one point you were stock 4.3. If that is correct you are done. Currently you can not unlock 4.3. You can only root with Kingo.
Galaxy S4 way works on MJ(
TonikJDK said:
In the middle there you say at one point you were stock 4.3. If that is correct you are done. Currently you can not unlock 4.3. You can only root with Kingo.
Click to expand...
Click to collapse
Not true -- but it took me HOURS to find it:
http://forum.xda-developers.com/showthread.php?t=2565758
give the guy a thanks, huh?
TX_Jax said:
Not true -- but it took me HOURS to find it:
http://forum.xda-developers.com/showthread.php?t=2565758
give the guy a thanks, huh?
Click to expand...
Click to collapse
I must be missing it. I see that it roots, but I don't see where it unlocks a VZW bootloader.
TonikJDK said:
I must be missing it. I see that it roots, but I don't see where it unlocks a VZW bootloader.
Click to expand...
Click to collapse
That's correct -- so you are looking to unlock the phone? Have you tried the fee-for-service sites?
There is no unlock method on any 4.3 Samsung device that I'm aware of.
TonikJDK said:
In the middle there you say at one point you were stock 4.3. If that is correct you are done. Currently you can not unlock 4.3. You can only root with Kingo.
Click to expand...
Click to collapse
But right now I'm on 4.1.2, I flashed back to that. that's where i've been trying to find a way to get to the next step.
mavermc said:
But right now I'm on 4.1.2, I flashed back to that. that's where i've been trying to find a way to get to the next step.
Click to expand...
Click to collapse
You are unable to flash a recovery because your bootloader is locked, from when you flashed 4.3. That was game over. How you got part way back to 4.1.2 I don't know, but be careful. I would flash back to 4.3, root it and hope someone unlocks the bootloader for 4.3
TonikJDK said:
You are unable to flash a recovery because your bootloader is locked, from when you flashed 4.3. That was game over. How you got part way back to 4.1.2 I don't know, but be careful. I would flash back to 4.3, root it and hope someone unlocks the bootloader for 4.3
Click to expand...
Click to collapse
Well that really sucks, with this soft root, any chance I could atleast get back my NFC on while screen off?
u can. look for the exposed installer, I seen it on here somewhere. theres a option for nfc on with screen off on it. I'll try to remember where I seen it and post for ya.
mike7728 said:
u can. look for the exposed installer, I seen it on here somewhere. theres a option for nfc on with screen off on it. I'll try to remember where I seen it and post for ya.
Click to expand...
Click to collapse
I use the Wanam Xposed module for NFC with the screen off.
jcollier said:
I use the Wanam Xposed module for NFC with the screen off.
Click to expand...
Click to collapse
I got Xposed working so I'll be checking this out, thanks!
Any idea how to get the features from the other roms in this? like smart scrolling with your eyes and the other features that the [ROM] N3BULA [MJ9] has snuck in from the note 3?
So this is situation
I had rooted device and hyperdrive rom. I went back to stock using Odin. Then I rooted again using saferoot method. I flashed custom recovery. I didn't even check if it has been installed correctly. Then I used boot unlocker app to unlock bootloader. App name is EZ-Unlock something. It asked me to reboot, I did and I can't turn on my screen. I used all type of combination. I tired keeping battery out for few hours and nothing is happening. I can't turn on screen at all. Nothing means nothing. Any idea please? I don't want to waste money with out getting help from here. Thanks in advance.
lipitor25 said:
So this is situation
I had rooted device and hyperdrive rom. I went back to stock using Odin. Then I rooted again using saferoot method. I flashed custom recovery. I didn't even check if it has been installed correctly. Then I used boot unlocker app to unlock bootloader. App name is EZ-Unlock something. It asked me to reboot, I did and I can't turn on my screen. I used all type of combination. I tired keeping battery out for few hours and nothing is happening. I can't turn on screen at all. Nothing means nothing. Any idea please? I don't want to waste money with out getting help from here. Thanks in advance.
Click to expand...
Click to collapse
There is no "boot loader unlock" for the i545, just Loki for the MDK bootloader.
What bootloader did you start with? What build?
It sounds to me like whatever you used hosed your phone, which is pretty unusual. Normally you can at least get into bootloader mode.]
If you press the power button and plug in to your PC, what kind of device appears?
lipitor25 said:
So this is situation
I had rooted device and hyperdrive rom. I went back to stock using Odin. Then I rooted again using saferoot method. I flashed custom recovery. I didn't even check if it has been installed correctly. Then I used boot unlocker app to unlock bootloader. App name is EZ-Unlock something. It asked me to reboot, I did and I can't turn on my screen. I used all type of combination. I tired keeping battery out for few hours and nothing is happening. I can't turn on screen at all. Nothing means nothing. Any idea please? I don't want to waste money with out getting help from here. Thanks in advance.
Click to expand...
Click to collapse
Ok, first off you cannot unlock the bootloader on this phone. MDK build is the only build that has a bootloader workaround, but it is still not unlocked.
What you will need to do is to find out what build you are on, download that .tar file, boot into download mode, and flash it through Odin.
He used the gs3 ez unlock tool on his galaxy s4...complete brick no fix until we gain the necessary files for JTAG...device won't charge won't boot won't do anything whatsoever... Odin won't even recognize that anything is connected...hope you bought insurance or are within return period
jamesd1085 said:
He used the gs3 ez unlock tool on his galaxy s4...complete brick no fix until we gain the necessary files for JTAG...device won't charge won't boot won't do anything whatsoever... Odin won't even recognize that anything is connected...hope you bought insurance or are within return period
Click to expand...
Click to collapse
Ah, wasn't aware that tool would do that. Sorry OP!
a.demarco said:
Ah, wasn't aware that tool would do that. Sorry OP!
Click to expand...
Click to collapse
Reason why you research to death before jumping.
Sent from my SCH-I545 using XDA Premium 4 mobile app
jamesd1085 said:
He used the gs3 ez unlock tool on his galaxy s4...complete brick no fix until we gain the necessary files for JTAG...device won't charge won't boot won't do anything whatsoever... Odin won't even recognize that anything is connected...hope you bought insurance or are within return period
Click to expand...
Click to collapse
Lol. I didn't know that. I guess I am F***** up this time... I don't have insurance. Thanks everyone for your help.
lipitor25 said:
Lol. I didn't know that. I guess I am F***** up this time... I don't have insurance. Thanks everyone for your help.
Click to expand...
Click to collapse
That sucks !
Head over to swappa .. might as well see if u can get an mdk version...
Sent From My Verizon S4