I was following the directions seen here for rooting from stock EE4.
CWM install via Odin seemed to work fine but when I booted into recovery mode, I did not see the option "install zip from sdcard" (from which point I would have navigated to my kernel.zip file). Instead, I selected "update from.sdcard.zip" or something to that effect. The result is an exclamation point in a triangle and zero responsiveness.
What now? Thanks.
Can you reboot into recovery? If yes, then select update from sdcard this time and you should be good to go.
If no, the do an ODIN flash of CWM again, then select update from sdcard this time and you should be good to go.
Yes, elucid, I did get booted into recovery. I have the same options as before including the one you suggest I execute (and which froze me last time) "apply sdcard:update.zip."
Is the absence of ""install zip from sdcard"" from the menu evidence that I somehow screwed up the CWM installation?
It sounds like you may have the stock recovery instead of CWM. The second option should be:
Apply update from sdcard
It should also say ClockworkMod Recovery (not Samsung Recovery). What color is the screen in recovery?
Try using ODIN to flash CWM again.
Uncheck auto-reboot when flashing CWM and boot direct to recovery when it is finished and flash the rooted kernel. Booting the phone w/ the stock kernel overwrites the recovery you just flashed.
Yep, I'm in (blue) Samsung recovery. I had reboot unchecked but may have mindlessly rebooted normally post-Odin.
1. Make sure you have the latest ZIP file for CWM on your SD Card.
2. Make sure you have the zip for the kernel you want on your SD Card.
Then try the following...
What I would try is to download the third package from this post.
1. Use Odin to flash this package.
2. Disconnect the phone from the computer, put in the battery and try to boot up. It will usually boot into recovery after an Odin flash. No worries if it does or does not. This particular package will probably have yellow text when in CWM.
3. Either let the phone boot normally if it does it, or select reboot now from CWM.
4. Once the phone boots up (confirming that it works, in other words, not soft bricked) shut it down.
5. Reboot into recovery (3 button combo).
6. Install the updated CWM from the SD Card.
7. Reboot the phone back into recovery.
8. Install the new kernel you want.
9. Reboot the phone to the OS and make sure the Superuser App works.
10. Reboot into recovery and install whatever ROM you want.
And now you should be golden.
The instructions that you linked to in your OP are good. I read through them and its a solid guide.
Related
I was trying to root an infuse 4g.
So I followed the you tube video to install the modded 3e recovery and CMW.
Once I was in 3e and did reinstall packages, it loaded into CWM.
I then flashed the CWM zip from the following thread. 100% working ClockworkMod Recovery for Infuse 4G [GTG465x]
Then I went to flash CM7. I went to reboot the phone and constantly just boots into CWM and never boots CM7.
I can't get into download mode, so I'm not sure what I can do from here.
Anyone got any suggestions.
The phone does power up, but I just can't ADB or get it into download mode..
Get into recovery. There you go to mounts and storage, format /system, then reflash CM7 and gapps. That's how you flash CM7, you have to flash, format, then reflash.
hmm that didn't work.
The phone shows the Samsung splash, then loads CWM (v5.0.2.6)
Sword.Zero said:
hmm that didn't work.
The phone shows the Samsung splash, then loads CWM (v5.0.2.6)
Click to expand...
Click to collapse
When you flash CM7, it gets stuck on the Samsung splashscreen, you pull the battery, boot into CWM, then format/reflash. What did you do?
from the beginning this is what I did:
1. I used SuperOneClick to root the Infuse
2. Followed the youtube video to install the 3e recovery.
3. Continued with the video and used ROM Manager to install CWM.
4. In ROM Manager, used "Reboot into Recovery"
5. Phone rebooted, and I was in the 3e recovery.
6. Selected "reinstall packages" (performed this twice).
7. Once I was in CWM 2.5.1.2, I flash the zip in "100% working ClockworkMod Recovery for Infuse 4G [GTG465x]" thread and rebooted recovery.
Somehow I was loaded into CWM v5.0.2.6. (not I'm not sure if this is the correct version)
8. I went to flash CM7 and gapps.
9. Rebooted phone.
10. Phone shows "Samsung" splash, then jumps right into CWM. I don't even tell the phone to boot into recovery.
Now I been trying to get into download mode, but i can't get the phone to be picked up by Odin or into download mode to start over...
Pull battery plug in USB cord hold volume buttons while put battery back in this will put you in download mode
Sent from my SGH-I997 using XDA App
Thanks! that did it...
Well, I've been trying to work my way through this one, but I'm unable to find an answer. I tried to flash the UCLD2 firmware ICS leak on my SR and it didn't work, and now the phone goes on an endless boot loop. My phone was rooted with stock ROM (Gingerbread 2.3.6) and I had clockworkmod installed. I did a full back up with Titanium Backup as well. I saw a page in android authority detailing how to flash it using clockwork mod and followed the clockworkmod method:
Flashing via ClockworkMod Recovery
NOTE: You will be needing a rooted Samsung Galaxy S2 Skyrocket with ClockworkMod Recovery (CWM) installed. Check out our guide on how to root your Samsung Galaxy S2 skyrocket. You can also refer to this guide on how to root your phone running Android 4.0.3 UCALC4 firmware. For ClockworkMod Recovery, check this guide on how to flash ClockworkMod Touch Recovery to your phone.
Download the following to your computer:
Download the CWM-flashable UCLD2 package from here (skyrocket-ucld2-ics-leak.zip, md5sum: 5cb721bcacdadf7de2b0b9f041acc114).
Download the root fix file from here (su-bin-3.0.3.2-efghi-signed.zip, 164 kB).
Download the Facebook and Samsung keyboard fix here (UCLD2FontHotfix.zip, 226 kB).
Copy the skyrocket-ucld2-ics-leak.zip, su-bin-3.0.3.2-efghi-signed.zip, and UCLD2FontHotfix.zip to the root of your phone’s SD card.
Switch off your mobile phone.
Reboot your phone into ClockworkMod Recovery. To do that, press the Volume Up key, Volume Down key, and Power button simultaneously until Recovery Mode boots. NOTE: Once in Recovery Mode, use the Volume keys to navigate and Power button to select an option.
Perform a full wipe by doing the following:
Go to Wipe Data/Factory Reset and confirm the action on the next screen.
Select Wipe Cache Partition and confirm the action on the next screen.
From the main menu, select Advanced. From there, select Wipe Dalvik Cache and confirm the action on the next screen.
Go to Mounts and Storage and select Format /system on the next screen. Select Yes on the next screen to begin formatting your system.
Go back to the main menu and select Install ZIP from SD Card. Select Choose ZIP from SD Card and highlight the skyrocket-ucld2-ics-leak.zip. Confirm the action on the next screen to begin flashing the ZIP file to your phone.
Repeat step 6 but this time flash su-bin-3.0.3.2-efghi-signed.zip to your phone. You will meet an error message after flashing this file. Just ignore the error message.
NOTE: Ignore the error after flashing this file. Just go to Superuser and make an update after booting your phone.
Flash the UCLD2FontHotfix.zip file in the same manner as in step 6.
After installing the 3 files, go back to the main menu and select Advanced. From there, select Fix Permissions.
Go back to the main menu and select Reboot system now to restart your mobile phone.
Once your phone has rebooted into Normal Mode, launch the Superuser app and update the su binaries.
Congratulations! You have successfully updated your Samsung Galaxy S2 Skyrocket SGH-I727 to the leaked Android 4.0 Ice Cream Sandwich firmware UCLD2.
I did everything detailed in the clockworkmod method, was very careful and checked everything multiple times. Once I did those steps when I tried to reboot the system it goes on an endless boot loop. Sometimes it gets to the splash screen, sometimes it doesn't. No error messages are displayed, it just keeps booting. I am able to access clockworkmod, but I'm not sure what to do at this point. I've re-downloaded the three files listed in the article and I've redone all the steps, with the same results (obviously...). Not sure what my next step is at this point. Any help would be greatly appreciated.
Use a 1 click release...
Hello.
Your solution:
Put the phone into Download mode, and install the leak from the original 1 click odin release by DesignGears.
How to do it?
1st, search in the forums the location of the firmware, be sure to use the 1 click release, there are 3 leaks, for me the second was the best, probably for you the 3rd will be better, use one of those 2.
Be sure to have all drivers for your phone installed, and be sure Kies wont start when you connect the phone.
Power the phone off, by removing the battery.
Press, Vol up and Down at the same time, while keeping them pressed, connect the USB cable, then, run the 1 click binary.... wait some minutes while it says it is done and enjoy!!!!
Hope it helps, if any problems arise, let us know. I will check the thread later today and tomorrow.
Thank you! Working on it right now. I'll update you on how it goes.
Hope it ends fine for you!
Worked like a charm! Not sure why it didn't work the other way. Regardless, thank you so very much.
Nice!!!
Nice!!!!!!!!!!!!!!!!!!!!
I tried to use the search and google but didn't really find anything helpful. Almost 2 years ago, I unlocked the bootloader back on honeycomb and did custom recovery, root, and custom rom. Then a little while after ICS came out, I did the OTA update.
Today, I reset the xoom back to stock ICS and tried to unlock the bootloader again...thinking nothing of it. The process was taking a few minutes so I decided to get a snack and when I came back it was rebooting.
I assumed that it worked and continued to try and fastboot a recovery image. The recovery image installed and I did another reboot but was greeted with the android welcome screen. Anyways I went through the menus and then tried to enter recovery and it gave me an android laying on its back with and exclamation point above his open chest.
I hard rebooted and can still get into my device, but adb cannot seem to find my xoom anymore. I have tried it on a 64bit desktop and laptop with no luck.
Have I messed up? Or is there a simple fix that I am missing? Thanks in advance for any help!
Can you get into fastboot mode? The second time you unlocked did you have to go through the questions on your xoom again?
dfib1 said:
Can you get into fastboot mode? The second time you unlocked did you have to go through the questions on your xoom again?
Click to expand...
Click to collapse
Yes, I can get into fastboot by holding the volume down key and the power button. That's fastboot, right?
Yes, I had to go through the menus the second time I unlocked.
sounds like the recovery you try to fastboot did not take or the rom was corrupt.. Which recovery was it? Do you want to be rooted and run a custom rom or completely stock? what xoom do you have(wifi, 3g, 4g)
dfib1 said:
sounds like the recovery you try to fastboot did not take or the rom was corrupt.. Which recovery was it? Do you want to be rooted and run a custom rom or completely stock? what xoom do you have(wifi, 3g, 4g)
Click to expand...
Click to collapse
I want to flash this ROM
http://forum.xda-developers.com/showthread.php?t=1997434
With whichever recovery is best. I tried flashing this recovery:
http://forum.xda-developers.com/showthread.php?t=1074979
I am on a 4G xoom on 4.0.4 but I don't use my data plan. I would like to be on a nice stable build of 4.2.
Download your rom choice, gapps and put them on the root of your sd card. If they are already there skip this step
I like TWRP Recovery the best. Easy to use and lots of options.
download this Twrp 2.4 img to the folder you hve fastboot in
open a cmd prompt in that o that folder
type fastboot flash recovery TWRPv2.4.1.0.img
Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery.
You should be in twrp 2.4
select backup/restore and backup your current system
select install and find your rom select asnd then swipe to flash
when done then select home
select install again and find the gapps package and install
when done select wipe dalvick/cache
when done select reboot
select system
you should be good to go.
Well I got through all of the steps, but when I try to boot I get stuck in a loop of the roms boot logo. Is it okay to flash a wingray rom over a stingray device?
dfib1 said:
Download your rom choice, gapps and put them on the root of your sd card. If they are already there skip this step
I like TWRP Recovery the best. Easy to use and lots of options.
download this Twrp 2.4 img to the folder you hve fastboot in
open a cmd prompt in that o that folder
type fastboot flash recovery TWRPv2.4.1.0.img
Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery.
You should be in twrp 2.4
select backup/restore and backup your current system
select install and find your rom select asnd then swipe to flash
when done then select home
select install again and find the gapps package and install
when done select wipe dalvick/cache
when done select reboot
select system
you should be good to go.
Click to expand...
Click to collapse
Well I got through all of the steps, but when I try to boot I get stuck in a loop of the roms boot logo. Is it okay to flash a wingray rom over a stingray device?
I think it is fine just the 3g/4g won't work.
I can get you going again but you are going to be starting with a locked honeycomb device. You will then have to either let it update to ICS or JB or unlock, root, install custom recovery and flash a rom. What xoom do you have 3g or 4g?
dfib1 said:
Download your rom choice, gapps and put them on the root of your sd card. If they are already there skip this step
I like TWRP Recovery the best. Easy to use and lots of options.
download this Twrp 2.4 img to the folder you hve fastboot in
open a cmd prompt in that o that folder
type fastboot flash recovery TWRPv2.4.1.0.img
Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery.
You should be in twrp 2.4
select backup/restore and backup your current system
select install and find your rom select asnd then swipe to flash
when done then select home
select install again and find the gapps package and install
when done select wipe dalvick/cache
when done select reboot
select system
you should be good to go.
Click to expand...
Click to collapse
Okay I restored it again but this time i did a factory reset and wipe dalvick before flashing the rom and gapps. It works! Thank you for your help!
However, could I ask how to root this thing?
since you have a custom recovery on it already and are unlocked.
Download this file Universal xoom root place it on the root of your sd card and flash it. Then reboot and try a root required app such as root checker
dfib1 said:
since you have a custom recovery on it already and are unlocked.
Download this file Universal xoom root place it on the root of your sd card and flash it. Then reboot and try a root required app such as root checker
Click to expand...
Click to collapse
Thanks! Got it!
g;lad to hear it.
Hey guys, I'm fairly new to this but I have my One S, H-Boot 1.18, Radio 1.08, unlocked, rooted, TWRP2.4.4.0 and S-Off...
I have successfully installed CM10, and have since restored it to the Stock RUU.
I have tried loading the Viper 2.1.0 5 times now and keep getting stuck on the "white "T-Mobile screen" with the red text on it. I have a few questions about the instructions that are posted.
1. Download the Boot.img Flash Script from http://androidfilehost.com/?fid=9390275921635705217
2. Download the Rom
3. Extract the Boot.img Flash Script on your PC
4. Connect your One S to the PC (USB Disk Mode), copy ViperOneS_xx.zip (the ROM) to your HTC One S
5. Connect your One S via USB and ensure you have HTC Sync installed, you need the drivers to be able to use fastboot
6. Uncheck fastboot in Settings->Power, then shut down your HTC One S completely (don't reboot, shut it down).
7. Press and hold volume down, then press power (keep holding volume down!) until your screen shows the hboot menu, navigate to recovery (use volume keys)and press the power button once to jump into recovery mode.
8. In Recovery choose install zip from sd -> choose zip file and navigate with your volume buttons to the downloaded Rom and hit power and confirm with yes.
I am using TWRP 2.4.4.0 which is supposed to be problem free (something about they fixed the .lib issue from the previous version that the new JB created), I have been wiping System and recovery.
9. Now the Aroma installer should show, if you have the touch recovery installed you can use your screen to navigate through it, otherwise use the volume buttons and confirm with the power button.
I'm confused on the Kernel prompt during the installation, doesn't the boot.img file that we install in the next step have a new Kernel in it? So do I sellect a custom Kernel or not?
IMPORTANT: if you come from another Rom, pls choose FULLWIPE
10. After you configured it, reboot to your bootloader in fastboot mode
11. Now go to your extracted Boot.img Flash Script folder:
Depending on your OS of your PC you need to run the file like normal:
Windows: flash-boot-windows.bat
MAC: flash-boot-mac.sh
Linux: flash-boot-linux.sh
12. When the commands were successful, press power again to go back to the hboot
13. Navigate with your volume button to "Recovery" and reboot or reboot via cmd with "fastboot reboot"
14. Finally we highly recommend specifically for One S to boot again in recovery and wipe cache. Please do that also, whenever you flash any addons or mods – always boot your device first, then boot again in recovery and wipe cache.
15. Recommendation - with "Flash Image GUI" from joeykrim you can alternatively flash boot.img on your device, no need to fastboot anymore - http://forum.xda-developers.com/show...1954121&page=2
This recommendation Should be in the beginning right? Doesn't this flash the Kernel and then tell you to install the ROM directly afterwards? So shouldn't this be step one?
Any advice, appreciated, I'm not stopping until this thing is a brick or I figure it out...
thanks ahead of time, and I have tried to read through there are almost 600 posts so if I missed something I apologize ahead of time.
I know exactly how you feel..I went through the same issues as you did. Below are my feedback on what I did, however as I found through other posts, instructions may work for some, but not all phones. So please be careful if you were to follow what I did. I put my feedback in blue and my own direction list on what I did that finally made viper one s work for me.
1. Download the Boot.img Flash Script from http://androidfilehost.com/?fid=9390275921635705217
2. Download the Rom
3. Extract the Boot.img Flash Script on your PC
4. Connect your One S to the PC (USB Disk Mode), copy ViperOneS_xx.zip (the ROM) to your HTC One S
5. Connect your One S via USB and ensure you have HTC Sync installed, you need the drivers to be able to use fastboot
6. Uncheck fastboot in Settings->Power, then shut down your HTC One S completely (don't reboot, shut it down).
7. Press and hold volume down, then press power (keep holding volume down!) until your screen shows the hboot menu, navigate to recovery (use volume keys)and press the power button once to jump into recovery mode.
8. In Recovery choose install zip from sd -> choose zip file and navigate with your volume buttons to the downloaded Rom and hit power and confirm with yes.
I am using TWRP 2.4.4.0 which is supposed to be problem free (something about they fixed the .lib issue from the previous version that the new JB created), I have been wiping System and recovery.
Alright, seems like it's good then, I used CWM to make mine work but I'm pretty sure that you'll be fine with that one.
9. Now the Aroma installer should show, if you have the touch recovery installed you can use your screen to navigate through it, otherwise use the volume buttons and confirm with the power button.
I'm confused on the Kernel prompt during the installation, doesn't the boot.img file that we install in the next step have a new Kernel in it? So do I sellect a custom Kernel or not?
This is what I figured out, as I had the same question when I was going through the installer.
-Yes: Means that you come from a kernel that is not the normal kernel, such as ElementalX.
-No: Means you are using the stock kernel.
Selecting yes will skip the new flashing of the boot.img kernel, while selecting no will flash the boot.img
IMPORTANT: if you come from another Rom, pls choose FULLWIPE
Actually this part was the game changer for me, instead of following this, I wiped the system using my recovery, then selected install without wiping. (As I already wiped it via recovery)
10. After you configured it, reboot to your bootloader in fastboot mode
Even though I have seen numerous posts saying that once the One S is S-off you don't need to boot-flash-script..I clicked restart on the aroma installer and pressed the volume down button and the power, went into boot loader, went into fast boot USB and installed the boot-flash-script anyways..doesn't hurt
11. Now go to your extracted Boot.img Flash Script folder:
Depending on your OS of your PC you need to run the file like normal:
Windows: flash-boot-windows.bat
MAC: flash-boot-mac.sh
Linux: flash-boot-linux.sh
12. When the commands were successful, press power again to go back to the hboot
13. Navigate with your volume button to "Recovery" and reboot or reboot via cmd with "fastboot reboot"
14. Finally we highly recommend specifically for One S to boot again in recovery and wipe cache. Please do that also, whenever you flash any addons or mods – always boot your device first, then boot again in recovery and wipe cache.
15. Recommendation - with "Flash Image GUI" from joeykrim you can alternatively flash boot.img on your device, no need to fastboot anymore - http://forum.xda-developers.com/show...1954121&page=2
This recommendation Should be in the beginning right? Doesn't this flash the Kernel and then tell you to install the ROM directly afterwards? So shouldn't this be step one?
For me, I ignored that, because of that I have no knowledge for this question. :/
I am going off knowledge of what I did, as I had the same trouble you did. I tried to flash the rom countless times, almost bricked my phone, but after a stressful trial and error, I found the bugs that gave me my problems.
My Directions
1. Make nandroid (Just in case rom doesn't work)
2. Backup all apps as wiping phone will wipe all data and apps
2. Put viper 2.1.0 on device folder (I made a folder called roms)
3. Go to recovery
4. Wipe cache, system, and dalvik
5. Start the installer
4. Run through the desired checklists
-Select continue without wipe
-If on normal kernel select no when prompted on the kernel checklist
5. Once complete, click restart
6. Press and hold volume down and power to go to boot loader
7. Install boot-flash-script
9. Start Phone
10. It will be wiped, so go through the HTC start-up instructions
11. Once all that is done and the phone is fullyloaded, boot phone to recovery
12. Wipe Cache (to lessen lag)
13. Reboot again and done!
Don't use twrp 2.4.4.0, there are known problems flashing with it. Go for 2.3.3.0
First Thanks to both of you for the help.
So I down graded to TWRP 2.3.3.0...
Backed up my phone
Restarted phone, mounted and deleted the old back up
Began following the modified instructions
It appeared to work a little better this time ie... The installation screen colors seemed to be right and not all in a blue hue, and when it loaded it went all the way to 100% instead of hanging at 7% and then saying done.
I want to make sure this is correct also when I run the fastboot script, that this is what it should look like...
C:\htc_one\One_S_All-In-One_Kit_v3.4\Data>fastboot flash boot boot.img
< waiting for device >
sending 'boot' (6124 KB)...
OKAY [ 0.850s]
writing 'boot'...
OKAY [ 1.475s]
finished. total time: 2.328s
Alas this is still a "no joy" situation.
only good news is that I'm not stuck at the T-Mobile screen any more, the screen goes away after 5 seconds and now I'm sitting on a black screen.
What this has led me to think is that either the rom did not install correctly (duh) or you just downloaded the update for viper one s instead of the whole rom.
So just for clarification, now instead of on the t mobile screen it now goes to a black screen?
-Have you gone back into recovery and wiped cache again?
-Do you have a custom kernel or the stock kernel?
On another note.. Yes, the fastboot script was correct.
Sent from my HTC One S using xda app-developers app
So, I got it working, it seems that because I have my phone in S-Off, I didn't need to run the script. I just let it reboot after reinstalling it and it came up just fine.
I really appreciated the help guys, great support here... Maybe this post itself will help someone. :good:
Howdy I have a older AT&T Galaxy Tab 2 10.1 GT-P5113 SGH-i497 Android 4.2.2
I followed the steps on forum thread Samsung Galaxy Tab 2 Development -->(ODIN + CWM 6 + ROOT + Stock) ATT / TMOBILE Galaxy Tab 2 10.1 {} {SGH-T779} by Childofthehorn
Well I made it through step 5, at least! (Odin displays green “Passed!”)
But the following steps:
6. Backup your existing image
7. Flash SuperSu from SDcard
8. WInning.
here's where I'm at:
(see attached)
strangely there is no button for attachment on the Editor Are attachments allowed on this forum? Peculiar!
Only choices on the Recovery screen are
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
Don't know how to "back up your existing image"
or "Flash SuperSU from SDcard."
(but I do have the SuperSU apk on the SDcard though; do I select "apply update from external storage"?)
How do I know I have root? Odin said "Passed!" in green, but I'm not sure what that entails. -- I don't want to use any of those root checkers on Google Play because they all appear to ad-filled junk.*
Do I have CWM 6 by this process? How can I tell?
Is it possible to upgrade to KitKat? or is the P5113's processor not capable of it (or something else prevents having KitKat)
Not sure what I should do next.
Thanks everyone!
After Odin says Passed did you let the tab reboot to the ROM? If so the ROM probably replaced CWM with stock recovery (stock ROMs tend to do this), so what you need to do is flash the recovery again via Odin, but once it completes immediately reboot to recovery using the key combination, do not let the ROM boot. Once the recovery has loaded it should automatically disable the recovery replacement system in the ROM, and you'll be able to proceed to step 6.
putr4s said:
After Odin says Passed did you let the tab reboot to the ROM? If so the ROM probably replaced CWM with stock recovery (stock ROMs tend to do this), so what you need to do is flash the recovery again via Odin, but once it completes immediately reboot to recovery using the key combination, do not let the ROM boot. Once the recovery has loaded it should automatically disable the recovery replacement system in the ROM, and you'll be able to proceed to step 6.
Click to expand...
Click to collapse
Do you uncheck Auto Reboot and F. Reset Time? With those enabled all Odin said was Reset! in blue.
For the 3rd step:
Childofthehorn says:
3. Open Odin (as administrator) and hit the "PDA" button, remember to uncheck the reset
I assume he means F. Rest Time in the Odin options tab
Seems to reboot immediately after Odin finishes, happens too fast; there's no time to reboot into recovery mode with the power+vol.
Cabbagestack said:
Seems to reboot immediately after Odin finishes, happens too fast; there's no time to reboot into recovery mode with the power+vol.
Click to expand...
Click to collapse
Just follow what the instructions said, but uncheck Auto Reboot. Then, once Odin is done, force reboot the tab by holding both power and vol button down for about 10 secs (until it reboots), then release the power button while still holding the vol button.