MAKE SURE USB DEBUGGING IS ENABLED! go to [settings]-[applications]-[development] and usb debugging, check the box. Thanks to side_road for pointing this step out!!!
Droidroidz, for the sake of simplicity, i reuploaded your kernel to my min.us account, so that all the download links look the same (except for the samsung usb drivers). Thanks everyone for all the help. Especially sickin. this is essentially the guide he made for FB14 many moons ago.
As usual, by following this guide you agree that you are an adult acting on your own free will with the understanding that any modification of software on your smartphone could potentially cause irreparable damage including but not limited to: soft brick, hard brick, universe imploding, etc, etc. and that you will not hold me liable for any and all damages or undesireable consequences of following this guide. That being said, this is pretty harmless and difficult to mess up.
So, without further ado...
1. Download droidroidz’s kernel located HERE
2. Download Odin located HERE and extract to your desktop.
3. Depending on your phone, download FF18 stock kernel located HERE or FF24 stock kernel HERE
4. Power off phone, make sure it is completely off.
5. Press and hold power + volume down, (PRESS THE VOLUME DOWN BUTTON FOR A FEW SECONDS THEN PUSH AND HOLD THE POWER BUTTON) release when the odin screen comes up
6. Press volume up to accept their conditions or whatever they want.
7. Open odin, click on the “PDA” button, and select the droidroidz-v0.2.tar.md5
8. Connect your phone to your computer.
9. Make sure that odin shows a yellow com # in the ID:COM box on the left. If it doesn’t, you need to install drivers for your phone. These can be found HERE. (bottom of page, Manuals & Downloads tab, under Software, it’s the USB driver. 25.31MB in size)
10. Click start, this will flash the kernel to your phone.
11. Once it is finished, it will automatically reboot. Disconnect your USB cable
12. After it finishes booting, open the market and search for superuser. There should be a listing that needs to update. Install the update.
13. Search again for busybox installer. Download and install that app
14. Open the busybox installer app, close or ignore all the popups and crap. We just want to hit that button that says install busybox, all the drop boxes and options are set by default and do not need changing.
15. Once it has completed, power off your phone again.
16. Press and hold power + volume down again, release when the odin screen comes up
17. Press volume up to accept
18. Open odin, and this time under PDA, browse to SCH-R760_STOCK_KERNEL.tar
19. Reconnect your USB cable, make sure that odin sees your phone again (the yellow COM port on the left)
20. Click start, this will flash the stock kernel back.
21. Once it is finished, the phone will reboot.
22. After it finishes booting, you should be golden, but to confirm you can go to the market and search for an app called root checker, this will test and make sure you have root.
23. Congratulations, was that so hard?!
I did not write this, just sharing the info. Thanks to Bru_1 for these instructions and a HUGE THANKS to mcdader for the FF24 Kernel.
thanks for posting this for everyone.
I have an Alltel S2, and since you say this is for generic CDMA non US cellular. I can safely assume my phone falls under that category. I just have a few questions. I imagine the answers are very simple, but I want to make sure before I do anything.
1. Where did you find the stock kernel? I found one for Alltel, but I am unsure if it is the right one. Will the kernel that you have posted work on my phone? I read another thread here http://forum.xda-developers.com/showthread.php?p=31653888#post31653888 I looked, and the kernel that was there is the same one as in my phone. So, I guess that means I can use the stock kernel that you have provided. Am I correct in that assumption?
2. "5. Press and hold power + volume down, (PRESS THE VOLUME DOWN BUTTON FOR A FEW SECONDS THEN PUSH AND HOLD THE POWER BUTTON) release when the odin screen comes up" Is the phone already plugged into the computer at this point?
3. I keep reading about some sort of triangle. Does this method get rid of that triangle?
Thank you for your help.
Stricken66 said:
I have an Alltel S2, and since you say this is for generic CDMA non US cellular. I can safely assume my phone falls under that category. I just have a few questions. I imagine the answers are very simple, but I want to make sure before I do anything.
1. Where did you find the stock kernel? I found one for Alltel, but I am unsure if it is the right one. Will the kernel that you have posted work on my phone? I read another thread here http://forum.xda-developers.com/showthread.php?p=31653888#post31653888 I looked, and the kernel that was there is the same one as in my phone. So, I guess that means I can use the stock kernel that you have provided. Am I correct in that assumption?
2. "5. Press and hold power + volume down, (PRESS THE VOLUME DOWN BUTTON FOR A FEW SECONDS THEN PUSH AND HOLD THE POWER BUTTON) release when the odin screen comes up" Is the phone already plugged into the computer at this point?
3. I keep reading about some sort of triangle. Does this method get rid of that triangle?
Thank you for your help.
Click to expand...
Click to collapse
1. FF24 will work for your phone The stock kernel in the link you posted is the same as in step 3. (there are 2 listed, FF18 and FF24, my phone has FF24) FF18 is generally the U.S. Cellular version and FF24 is the "generic" version. I got the Stock ROM from mcdader (post #2 in this thread and the OP in the link you listed, also the link you posted is a conversation between myself and mcdader, lol). The FF24 is talking about the underlined part in the kernel (2.6.35.7-SCH-R760.XARFF24-CL1125314 [email protected] #2)
2. It will take you a few tries to get it into recovery mode, try pushing both at the same time if you can't get it to work. No the phone is not plugged into the computer until step #8
3. This method DOES NOT have the triangle. You will see it once during the rooting process but it gets removed when you flash back to the stock ROM.
Ok I thank you for your reply, and answering my questions. I will most likely try this tomorrow, and report back with how things go.
Sent from my SCH-R760 using xda app-developers app
So, it worked without a hitch. Now to find a way to install clockwork, and another ROM.
Sent from my SCH-R760 using xda app-developers app
so after i rooted my phone how can i cwm and install rom for this model?
I've been wondering the same thing, and can't get a good answer.
Sent from my SCH-R760 using xda app-developers app
Links
turner78 said:
MAKE SURE USB DEBUGGING IS ENABLED! go to [settings]-[applications]-[development] and usb debugging, check the box. Thanks to side_road for pointing this step out!!!
Droidroidz, for the sake of simplicity, i reuploaded your kernel to my min.us account, so that all the download links look the same (except for the samsung usb drivers). Thanks everyone for all the help. Especially sickin. this is essentially the guide he made for FB14 many moons ago.
As usual, by following this guide you agree that you are an adult acting on your own free will with the understanding that any modification of software on your smartphone could potentially cause irreparable damage including but not limited to: soft brick, hard brick, universe imploding, etc, etc. and that you will not hold me liable for any and all damages or undesireable consequences of following this guide. That being said, this is pretty harmless and difficult to mess up.
So, without further ado...
1. Download droidroidz’s kernel located HERE
2. Download Odin located HERE and extract to your desktop.
3. Depending on your phone, download FF18 stock kernel located HERE or FF24 stock kernel HERE
4. Power off phone, make sure it is completely off.
5. Press and hold power + volume down, (PRESS THE VOLUME DOWN BUTTON FOR A FEW SECONDS THEN PUSH AND HOLD THE POWER BUTTON) release when the odin screen comes up
6. Press volume up to accept their conditions or whatever they want.
7. Open odin, click on the “PDA” button, and select the droidroidz-v0.2.tar.md5
8. Connect your phone to your computer.
9. Make sure that odin shows a yellow com # in the ID:COM box on the left. If it doesn’t, you need to install drivers for your phone. These can be found HERE. (bottom of page, Manuals & Downloads tab, under Software, it’s the USB driver. 25.31MB in size)
10. Click start, this will flash the kernel to your phone.
11. Once it is finished, it will automatically reboot. Disconnect your USB cable
12. After it finishes booting, open the market and search for superuser. There should be a listing that needs to update. Install the update.
13. Search again for busybox installer. Download and install that app
14. Open the busybox installer app, close or ignore all the popups and crap. We just want to hit that button that says install busybox, all the drop boxes and options are set by default and do not need changing.
15. Once it has completed, power off your phone again.
16. Press and hold power + volume down again, release when the odin screen comes up
17. Press volume up to accept
18. Open odin, and this time under PDA, browse to SCH-R760_STOCK_KERNEL.tar
19. Reconnect your USB cable, make sure that odin sees your phone again (the yellow COM port on the left)
20. Click start, this will flash the stock kernel back.
21. Once it is finished, the phone will reboot.
22. After it finishes booting, you should be golden, but to confirm you can go to the market and search for an app called root checker, this will test and make sure you have root.
23. Congratulations, was that so hard?!
I did not write this, just sharing the info. Thanks to Bru_1 for these instructions and a HUGE THANKS to mcdader for the FF24 Kernel.
Click to expand...
Click to collapse
The Droidz and Odin links above did not work for me. Do you have a new link?
Click to expand...
Click to collapse
Cspire Galaxy S2
timmons98 said:
The Droidz and Odin links above did not work for me. Do you have a new link?
Click to expand...
Click to collapse
Droidz link is now working and Odin I grabbed from another post.
I wanted to let all the CSpire customers out there with the Galaxy SII "SCH-R760" that is looking to root. These steps above work. Be sure that you that you do the following steps above with the FF24 stock flash NOT the FF18.
Click to expand...
Click to collapse
Timmons98 do you have any information on installing a custom recovery, and a ROM that will work for the generic CDMA model?
Sent from my SCH-R760 using xda app-developers app
All the links seem to be dead in the post for rooting
Sent from my SCH-R760 using xda app-developers app[/QUOTE]
All of the links are fixed now.
Stricken66 said:
Timmons98 do you have any information on installing a custom recovery, and a ROM that will work for the generic CDMA model?
Sent from my SCH-R760 using xda app-developers app
Click to expand...
Click to collapse
No, I have been looking for a version of CWM to install but do not know which one to use.
CWM for SCH-R760
Firstly, thanks for this excellent & clear rooting guide for this phone.
Secondly I'd like to second those asking about where to go from here - to install CWM and from there a custom ROM - for me that'll be cyanogenmod if possible...
If I understand rightly we would need to install a modified version of the "2.6.35.7-SCH-R760.XARFF24-CL1125314 [email protected] #2" kernel, that has CWM in it?
I've not had to do this on previous phone: the Desire rooted and CWM'd like a dream; my Milestone X2 was more like a nightmare and due to locked bootloader I had to use a bootstrap CWM that came in on the tail of the charging animation & so would only work when the phone was plugged into the wall and rebooted - and also it had to be reflashed every time a factory reset was done, something that became my downfall in the end...
So why can't CWM just be flashed - why does it concern the kernel?
I guess I don't understand the diff between bootloader - kernel - and the rest of the ROM...
thanks!
Jon
is this thread dead? im after a recovery aswell. i have the root access done with no problem but do i need to flash back to a different kernel through odin or what to get CWM access?
I hope it's not dead. I just don't think a lot of development happens for this version of the S2. I do think that a different kernel with CWM will have to be flashed, but that doesn't really do anything without a ROM to install. Yeah you could do backups, but you'd be backing up the custom kernel. I do know that some of the hardware drivers are stored in the kernel. So, some stuff on the phone may not work with that other kernel.
Sent from my SCH-R760 using xda app-developers app
How will I know which ff to flash for alltel in u.s.?
sent from my toroplus galaxy nexus using xda-app- developers app
It's 24 if I remember right. The links on the original post show you.
Sent from my SCH-R760 using xda app-developers app
Any answers about CWM or roms ? im getting tired of looking this up
Related
i have been doing alot of rom upgrade via clockwork and this is the first time my phone brick.
i tried the vol up, vol down and power button at the same time and it just brings me to "vibrant samsung" screen.
i also tried removing battery, hold vol up, vol down and insert battery, it goes to a screen where it says downloading. but didnt move for hours.....
and if i switch on normally, it just keep restarting on vibrant screen.
how do i solve this problem?
You have to use odin to flash back to stock....
That's what the download screen is for.
From that downloading mode screen you can odin it back to stock.
http://forum.xda-developers.com/showthread.php?t=734475
lazylilsnoop said:
i have been doing alot of rom upgrade via clockwork and this is the first time my phone brick.
i tried the vol up, vol down and power button at the same time and it just brings me to "vibrant samsung" screen.
i also tried removing battery, hold vol up, vol down and insert battery, it goes to a screen where it says downloading. but didnt move for hours.....
and if i switch on normally, it just keep restarting on vibrant screen.
how do i solve this problem?
Click to expand...
Click to collapse
removing battery, hold vol up, vol down and insert battery, Have Odin up and running then plug in your cable. Then let go of the button
yea, i found that page too. but anyone can get the link working?
thanx!!!
lazylilsnoop said:
yea, i found that page too. but anyone can get the link working?
thanx!!!
Click to expand...
Click to collapse
can't see the page?
here i quoted the OP
justanothercrowd said:
T959 (US T-Mobile version of the Galaxy S) Firmware that can be flashed through Odin to restore all partitions to the way your phone was shipped to you.
WARNING!!! THIS WILL WIPE ANY DATA ON YOUR DEVICE, IT WILL REPLACE YOUR BASEBAND, KERNEL, RECOVERY AND OS.
JFD ODIN Images from Samsung (PDA)
www.justanotherdev.slackdev.com/T959UVJFD.tar
MD5:632730f6b637f53e5b10e5cbc8b966a7
512 PIT File (PIT Extract first!)
www.justanotherdev.slackdev.com/s1_odin_20100512.rar
MD5:b5628c8e183fdd8f4c703321ca40e33a
ODIN
www.justanotherdev.slackdev.com/Odin3.rar
ALL 3 Files plues the root update.zip
http://tinyurl.com/2bc5b6r
thx to KopyKatKiller
INSTRUCTIONS!
1.Your Device must be in DOWNLOAD mode to use ODIN.
2.Get your phone into Download mode by holding vol down and power.
3.THEN connect your phone to the USB. (some folks have had luck doing it in reverse..connecting the USB then Power and vol down)
4.Open Odin and load each file with it's corresponding field..PIT,PDA,CSC etc. (In this case we just use the PDA and PIT)
5.Don't check anything else, the other two boxes should be checked by default (Auto Reboot and Reset Time)
6.Hit "start"! be patient!
NOTE: COM3 worked fine for me. COM should not matter as long as you are using the correct drivers.
Finally we get some U.S love from samsung firmwares.
For those looking the Nandroid method it is in the post below but only recovers ,system, data, cache and datadata. Not your kernel/recovery or BASEBAND/RADIO (Modem.bin)
Thx to all helping work on the Vibrant. Especially Youneek, Scepterr, MS_Guru, Wes Garner, rhcp0112345, and anyone I may have forgot.
Twitter
Click to expand...
Click to collapse
sorry, what i meant was the link to download odin.
all link by "justanothercrowd" is not working
Get in download mode like you have before then..
Use the Vibrant Toolkit and then click Flash to Stock and then press "Reboot into Download + Start ODIN" (ignore the "Check that USB debugging mode is enabled" because you're already in download mode), it'll open up ODIN and then follow the instructions for using ODIN.
http://forum.xda-developers.com/showthread.php?t=954509
From bay_wolf's post, some information about setup of odin,
When you select the PIT and PDA files, it should default to the installed location and if not then browse to where you installed AIO Vibrant Toolbox as the files are in there.
Click to expand...
Click to collapse
Note: there are instructions on how to use odin on the Flash To Stock screen. All the files you'll need will be downloaded with the download for the vibrant toolkit.
I've had this problem and freaked when i couldn't find a download to Odin, so I used the vibrant toolkit and it worked.
Here's the download link from his thread (credit to bay_wolf): http://www.multiupload.com/G3LUINMUE0
THANX ALOT GUYS!!!!!!!
now gonna start to update it to http://forum.xda-developers.com/showthread.php?t=1021383
just another quick question, which rom are you guys using? i came from bionix rom to the simply galaxy v3.0, it doesnt seem to b fast and smooth. any other recommended rom?
Try some EDT roms...beast...Malice, Trigger, or Bi Winning.
Flash back to stock too.
I use simply Galaxy with Crysis Sensation theme (TWiz 4.0 + tweaks) & DamianGTO Gold v2.0 kernel (not available on XDA). Then use an app called Blade buddy to set up all Stagefright tweaks (under advanced settings) and debug.sw.hf then menu > apply > save. Quadrant scores 2200+.
Trigger is really good (2.2) and there's a cool new theme called Vibrant HD for it.
Haven't tried CM7 but it looks cool, lots of themes with it.
A big thanks to RoboBear, tphillips, Lorddeff07, and anyone else that has helped make this happen.
I try to make my guides simple and straightforward so that the average user can root their device. I show every detail and walk you through the process. This guide is a complete video walkthrough on how to root the Galaxy Tab 10.1 WiFi with edits based on the issues that some may run into with previous guides. Without further ado, let's get started!
LINK TO MOD EDITutdated links
◄●REQUIRED DOWNLOADS●►
Just download, do not install or run anything yet.
◄●Instructions●►
This method is done on Windows. I recommend this way as its the easiest. If you don't have Windows, borrow from a friend.
◄●Downloading Files and Installing Drivers●►
Download the I have linked.
Extract the zip file by right clicking and selecting "Extract All," or by using an extracting program of your choice.
Open the folder and double click the driver file labeled "GT-p7510_USB_Driver_v1_3_2360_0-Escape.exe"
Install the driver. Its pretty much just Next, Next, Install, and Exit when its done.
◄●Connecting the Device●►
Turn on USB Debugging by going to Settings>Applications>Development and checking USB debugging. Click Okay to confirm
Power off the device by holding the power button and selecting Power off
Put the device into Downloading mode
Hold the Vol Down button (the left Volume button) and then hold the Power button as well.
Keep holding until you see two icons. First you'll see the Samsung Galaxy Tab 10.1 logo and then the icons will show up. Let go.
Press the Vol Up button (the right Volume button) to select Downloading mode.
Connect the device to your computer with the USB cable.
◄●Flashing a Custom Recovery●►
Go into the same root folder as before.
Double click the root application named "Odin3_v1.85.exe"
Select PDA
Double click the clockworkmod recovery file labeled "recovery-cwm_4.0.0.4-sam-tab-10.1.tar.md5" to select it.
Click Start
Once it is complete, you can close the program
◄●Completing the Root●►
Disconnect your USB cable
On your device, turn off USB Debugging by going to Settings>Applications>Development and unchecking USB debugging
Plug your USB cable back in
On your computer, go to the same root folder as before and transfer the zip file labeled "Samsung_Galaxy_Tab_10.1_root.zip" to your device. Don't put it inside any folder.
Confirm that it was transferred by clicking inside the device folder
Power off the device by holding the power button and selecting Power off
Put the device into Recovery mode
Hold the Vol Down button (the left Volume button) and then hold the Power button as well.
Keep holding until you see two icons. First you'll see the Samsung Galaxy Tab 10.1 logo and then the icons will show up. Let go.
Press the Vol Down button (the left Volume button) to highlight the left icon.
Press the Vol Up button (the right Volume button) to select Recovery mode.
You should see that you are in ClockworkMod Recovery. If not, start over
Use the volume buttons to highlight "Install zip from SD card" and hit the Power button to select it.
Use the volume buttons to highlight "Choose zip from SD card" and hit the Power button to select it.
Use the volume buttons to highlight "Samsung_Galaxy_Tab_10.1_root.zip" and hit the Power button to select it.
Use the volume buttons to highlight "Yes - Install..." and hit the Power button to select it.
When it finishes, the last line should say "Install from sdcard complete."
Use the volume buttons to highlight "*****Go Back*****" and hit the Power button to select it.
Hit the Power button to select "reboot system now"
Your device will reboot
You're now rooted!
Excellent Guide.
Thank you.
This one is Noob-Safe
I love how you have proper grammar and punctuation skills. Spacing is good, fonts are bold where they need to be, this is how a guide should look!
All guides should be written like this, can u offer classes for the uneducated?
EyeAndroid said:
I love how you have proper grammar and punctuation skills. Spacing is good, fonts are bold where they need to be, this is how a guide should look!
All guides should be written like this, can u offer classes for the uneducated?
Click to expand...
Click to collapse
Would there be a higher demand for that than my guides? lol. But thanks a lot, I appreciate it Just trying to make it easy for everyone.
Wow. A guide that is easy to follow, in plain and understandable English, and thorough!
Thanks a lot! I'll be following this when I get my Tab this week.
perfect instructions! Thanks!
just rooted this way. It was the easiest root I have ever done!
I have rooted two different androids and the rooted process took really long on my other phones. This took me the same amount of time as your video.
Very good guide.
1,000,000 points for not hosting your files on one of the uber-annoying file hosting sites. I used your video to root my EVO phone as well, have been waiting for your guide for the 10.1. great job....
All done, started after posting my thanks and now I am all rooted..(sp?) Just need an Easy Button boot screen after the root.
Perfect guide
Does this work with 16GB WIFI UEKME 3.1 tab?
djR3Z said:
A big thanks to RoboBear, tphillips, Lorddeff07, and anyone else that has helped make this happen.
I try to make my guides simple and straightforward so that the average user can root their device. I show every detail and walk you through the process. This guide is a complete video walkthrough on how to root the Galaxy Tab 10.1 WiFi with edits based on the issues that some may run into with previous guides. Without further ado, let's get started!
Click to expand...
Click to collapse
Thanks for the detail root instruction, it is very clear easy to understand (I have clicked the thank button).
Question: Just want to confirm whether this root method only applied to wifi only tab or applied to all wifi and 3G tab and with different version.
bdejong11129 said:
1,000,000 points for not hosting your files on one of the uber-annoying file hosting sites. I used your video to root my EVO phone as well, have been waiting for your guide for the 10.1. great job....
Click to expand...
Click to collapse
Haha yeah I hate that too, which is why I will always host files myself. But thanks a lot man, I really appreciate the support.
yongck7 said:
Thanks for the detail root instruction, it is very clear easy to understand (I have clicked the thank button).
Question: Just want to confirm whether this root method only applied to wifi only tab or applied to all wifi and 3G tab and with different version.
Click to expand...
Click to collapse
Unfortunately this is just for the Wifi only version. I could probably make a written guide for the others, but I don't have the devices to support that. Sorry dude.
Moderator, please make this sticky !!!
Thx.
MagicOnline said:
Moderator, please make this sticky !!!
Thx.
Click to expand...
Click to collapse
Ohhh, that'd be nice Hopefully I can get my hands on a 3G and 4G version. Someone PM'd me that this worked on their 3G but their gtab is now unlocked so hopefully I can figure that out blind
Sticky this thread!
Boot loop and no recovery mode ability
Sorry in advance for the long thread.
Great documentation. I hope you can help me. I posted the below at the stickied root thread but I haven't received any responses. It seems I blew away recovery mode. My tablet consistently boot loops. I have the option to choose recovery but when selected the screen goes blank for several seconds then reboots. I can get into download mode but my PC doesn't recognize the hardware and will not install the proper Samsung drivers. After reading your thread I'm wondering if this is because I didn't set debugging mode properly.
"Hi all I need some help. Verizon LTE 10.1 tab is boot looping after attempting bone head maneuver. Attempted root per Lorddeff07's method. Installed recovery file, system rebooted. Installed kernel file, system rebooted. Installed clockwork mod premium from market. Installed clockwork mod recovery for galaxy tab. Initiated backup via cwm, system rebooted and started boot looping. I can get into downloading mode but when I try to access recovery mode the tablet starts to boot loop.
I tried odin but the USB drivers are not installing properly. If I force the driver to install as Samsung ADB the tablet will display "start odin" when in downloading mode. However the odin app does not recognize the tablet. I'm running W7 pro Sp1 x64.
I also tried to use nvflash per shep211's tutorial but that didn't work. I get to section 2 step 17 when the command fails and the tablet will disconnect from the PC.
I know there has to be a way to fix my fUP. can anyone asist?"
FIXED: Removed the Verizon SIM card. Booted into download mode. Manually added the unrecognized driver as Samsung Mobile USB Serial Port. Opened odin flashed the ltecwm.tar.md5 file. Rebooted. All is good. Rebooted into recovery and installed root using Samsung_Galaxy_Tab_10.1_root.zip. Everything is up and running.
Thank you so much nice eay guide just rooted my tab thanks to you!!1 I pass you a beer sir
jobless said:
Sorry in advance for the long thread.
Great documentation. I hope you can help me. I posted the below at the stickied root thread but I haven't received any responses. It seems I blew away recovery mode. My tablet consistently boot loops. I have the option to choose recovery but when selected the screen goes blank for several seconds then reboots. I can get into download mode but my PC doesn't recognize the hardware and will not install the proper Samsung drivers. After reading your thread I'm wondering if this is because I didn't set debugging mode properly.
"Hi all I need some help. Verizon LTE 10.1 tab is boot looping after attempting bone head maneuver. Attempted root per Lorddeff07's method. Installed recovery file, system rebooted. Installed kernel file, system rebooted. Installed clockwork mod premium from market. Installed clockwork mod recovery for galaxy tab. Initiated backup via cwm, system rebooted and started boot looping. I can get into downloading mode but when I try to access recovery mode the tablet starts to boot loop.
I tried odin but the USB drivers are not installing properly. If I force the driver to install as Samsung ADB the tablet will display "start odin" when in downloading mode. However the odin app does not recognize the tablet. I'm running W7 pro Sp1 x64.
I also tried to use nvflash per shep211's tutorial but that didn't work. I get to section 2 step 17 when the command fails and the tablet will disconnect from the PC.
I know there has to be a way to fix my fUP. can anyone asist?"
FIXED: Removed the Verizon SIM card. Booted into download mode. Manually added the unrecognized driver as Samsung Mobile USB Serial Port. Opened odin flashed the ltecwm.tar.md5 file. Rebooted. All is good. Rebooted into recovery and installed root using Samsung_Galaxy_Tab_10.1_root.zip. Everything is up and running.
Click to expand...
Click to collapse
Glad you got it fixed! Did you use the Samsung_Galaxy_Tab_10.1_root.zip in my pack or from the LTE section in lord's thread?
I used the Samsung_Galaxy_Tab_10.1_root.zip that you provided.
Edited May 16 2012
Hi all,
Due to confusion and scared people I have decided to post simple instructions on how to unlock the bootloader on GB 2.3.4. I just received my Bell Atrix 4G, unlocked it for rogers and then rooted and unlocked the bootloader. I was confused by the pudding instructions, so I decided to recreate them In my own wording.
I take no responsibility for anything that happens to your phone or your heart stopping while you wait for your phone to reboot or if it is stuck on moto screen etc...
Credit for original tutorials go to the2dcour, romracer, Nottach, Faux123 and the others for all of their hard work.
Requirements:
1.Create a folder on your desktop named motounlock
2.Go here: forum.xda-developers.com/showthread.php?t=1136261
Scroll down to where it says "RSDLite/Windows Drivers/Sbf_flash"
UPDATE: Download RSDLite from here : http://www.multiupload.com/T6NOEBKKLO . If you need x64 bit Drivers use the other link. thanks AnguishedEnd!
download the first two files for windows (RSDLite 5.5 link, x64 Windows drivers)
download the third file for linux/mac
3.Scroll until you see the big word "Unlock"
where it says "Unlocker only SBFs" download the second file UNLESS you are on ATT.
4. Scroll down to the word "Root" and download 'Fastboot' for your OS
5.unzip all of the files you just downloaded into the motounlock folder on your desktop
6. open the folder, install RSDLite, and afterwards install the Drivers.
Then follow these instructions
Power Down your atrix
Take out your microSD card and SIM card for the flashing process
While turning the phone on, hold the Volume Up button until it acknowledges RSD. Your device will say “Starting RSD protocol support”
Run “RSD Lite” on your computer
Press the “. . .” button next to the box labeled “Filename”
Navigate to your desktop and open the motounlock folder and select the file named intl-fix-try1.sbf ( IT WILL BE DIFFERENT IF U ARE DOING THIS FOR ATT)
Plug your device into your computer. RSD Lite should recognize your device and say “Model: NS Flash Olympus” and “Connected…” The acronym 'NS' may be different for your device people!!
Press the “Start” button. The Flash actually failed for me, wait for it to complete to 100% it may FAIL or PASS! just make sure it gets to 100% leave your phone sitting for about 10 minutes AFTER RSD SAYS FAIL/SUCCESS.
If nothing is happening after 10mins, perform a battery pull. Power the phone on while pressing vol-down. “Fastboot” Will show up on screen. DONT PLUG IT IN YET. Press volume up and let your phone sit. You will see “Starting Fastboot protocol support" LEAVE IT UNPLUGGED
press the windows key + R on your computer, type cmd and press enter
command prompt will open. type cd C:\users\YOURNAME\desktop\motounlock press 'enter'
Plug your device back into usb now
back in your command prompt window type "fastboot oem unlock" no quotes
You will now receive a warning along with a unique device ID
Type the following commands using your unique device ID (the numbers in the command prompt) in place of the ####
fastboot oem unlock ####
fastboot reboot
your moto will reboot. UNLCOKED!!!!!!!!!!!!!
Proper Recovery:
1. After your bootloader unlocked go to this link http://forum.xda-developers.com/showthread.php?t=1204500
2. Scroll down to where it says "ALL USERS" and download your favourite colour. (NOT THE ZIP VERSION) Place it in the motounlock folder that you have on your desktop.
3. Press the windows key + R on your computer, type cmd and press enter
4. A Command prompt will open. type cd C:\users\YOURNAME\desktop\motounlock press 'enter'
5. type "fastboot devices" Press Enter.
5b. type "fastboot erase recovery" Press Enter.
5c. type "fastboot flash recovery recovery-atrix5.img" Press Enter.
Wait for the command prompt to say : "writing 'recovery'... OKAY ['The amount of seconds it took here']"
5d.type "fastboot reboot"
DO NOT FORGET TO DO THIS PART: After the install of RomRacers recovery boot up your phone. Open up your favourite file browser (I used Astro file manager to do this ) and navigate to /system/etc/ and delete the file called 'install-recovery.sh'
You will be set 100% !
Installing a custom ROM (Any custom rom will work as long as it has unified kernel/Faux Kernel)
MOST ROMS WILL COME PRE-ROOTED! Just saying, to avoid confusion.
I will be using Nottach's Darkside ROM as an example, because Cyanogenmod does not have features included with original moto rom (this one is way more NOOB friendly) But this is COMMON PROCEDURE for almost every rom so be sure to follow this for whatever ROM you want to use.
1. Go here http://forum.xda-developers.com/showthread.php?t=1222108
2. Scroll down to where it says 'DOWNLOADS' and download the most current version.
3. When it is finished downloading you will have a ZIP file named something like "TheDarkSidev2.8.0-Wipe.zip"
4. Plug your phone in to your computer and transfer that file to your INTERNAL MEMORY.
5. MAKE SURE YOUR PHONE HAS DECENT CHARGE! I would say at least 50 percent. 70+ is recommended, I have done it with 40 + though.
6. Power Down your Phone.
7. Hold The POWER Button + VOL DOWN. DONT PRESS VOLUME UP WHEN YOU SEE FASTBOOT! Instead...
8. After fastboot shows up click volume down until " Android Recovery " shows up, about 7 down clicks. THEN press volume up.
9.
***FIRST TIME ROM FLASHERS ONLY!!!!!!***
WE ARE GOING TO BACKUP YOUR ORIGINAL ROM SO THAT IF YOU EVER DERP YOU WIL ALLWAYS HAVE A SOLID BACKUP
Press VOLUME DOWN and go to backup and restore. Press the POWER BUTTON
Press the POWER button on backup
Select where you want to put your backup (internal or external memory)
Backup INCLUDING WEBTOP! (if you ever think you will use it)
Wait for it to finish.
***********************************
10. Ok now that you are in android recovery you have to do a few things before flash.
a. Scroll down to "wipe data/factory reset" PRESS POWER. say yes to EVERYTHING until it goes back to the main screen.
b. scroll down to "wipe cache partition" PRESS POWER. say YES. Wait for return to main menu
c. Scroll down to"advanced", click "wipe dalvik cache" Go back to "advanced", "wipe battery stats
11. At the main menu, Scroll to "install Zip from SDcard" Press POWER.
12.scroll down to "choose zip from internal sdcard"
13. select the ZIP file that you saved to your INTERNAL memory. If you're using darkside the file name is "TheDarkSidev2.8.0-Wipe.zip"
14. Scroll down to "YES - install TheDarkSidev2.8.0-Wipe.zip" Press POWER
15. Let your phone work its magic!
16. When it is finished installing, you will be returned to the recovery main menu.
17. click "reboot system now"
18. Let it boot! This can take anywhere from 10 seconds to 5+ MINUTES! if you dont see it move from the "unlocked" screen after 10 minutes Perform a battery pull and power on again. If it hangs then all you have to do is go into recvoery click "backup and restore" and restore your original ROM. Or like me, have one of every kind of ROM on your storage in case I feel the need to change it on the go!
19. YOUR PHONE HAS BEEN SUCCESSFULLY TURNED INTO A FULLY OPEN DROID Pat yourself on the back and have a drink to your accomplishments . We on XDA knew you could do it!
Some solutions to issues:
As ar31791 said,
Anyone having issues not being able to boot into CWM recovery after flashing it (such as seeing android guy with exclamation mark):
Delete or rename /system/etc/install-recovery.sh AND /etc/install-recovery.sh I renamed mine to bkup.install-recovery.sh in case i ever wanted to use them again for some reason.
/etc/install-recovery.sh will automatically be placed in /system/etc if /system/etc/install-recovery.sh is not found on boot.
So, you must delete or rename both, THEN INSTALL CWM recovery.
rename the files using ROM Toolbox's root explorer as some file explorers will not give you the proper access levels to delete or rename the files correctly.c
Hope this helps it worked for me. I was afraid of a brick because nobody clarified the steps that were involved in RSDLite. It may be nerve racking, but it does work!! Enjoy and thanks again to the2dcour, romracer, Nottach, Faux123 and anybody else who has helped in the scene that I didnt have a chance to mention. PM me if I forgot you!
Oh, and just to let everybody know when your bootloader is successfully unlocked it will say unlocked at the top left of your screen everytime you turn it on. just wait, this is normal.
OMG thank you so much tayshun!! I just spent 2 hours reading through that pudding post mess trying to figure out how to do this for a 2.3.4 bell atrix....
I was very nervous about trying something without clear directions in case I brick my phone. You're a lifesaver
noobler said:
OMG thank you so much tayshun!! I just spent 2 hours reading through that pudding post mess trying to figure out how to do this for a 2.3.4 bell atrix....
I was very nervous about trying something without clear directions in case I brick my phone. You're a lifesaver
Click to expand...
Click to collapse
I understand your grief hahaha. Feel free to press the thank you button at the bottom of my post. I'm trying to get a good reputation around here as I am going to school for programming and I will probably be in these dev forums daily to get help cooking Roms!
Has anybody else had success with my simplified instructions? Results?
this instructions seem simple
http://forum.xda-developers.com/showthread.php?t=1182871
what do you think?
sanriver12 said:
this instructions seem simple
http://forum.xda-developers.com/showthread.php?t=1182871
what do you think?
Click to expand...
Click to collapse
Are you sure it works on a Bell/Int'l Atrix?
Thanks heaps for the instructions Just used them to unlock a Telstra Atrix which I updated to 2.3.4 this morning! Worked a treat.
---------- Post added at 12:06 PM ---------- Previous post was at 11:58 AM ----------
Maybe i spoke to soon...I just noticed it has reset to factory defaults. Not a big deal as I already backed everything up but i certainly wasn't expecting it!
What about android version 2.2.2 and system Version.4.2.11.MB860.Retail.end.FR
Build: OLYEM_ U4_2.1.1
IT'S bell phone atrix 4g unlocked and running on Rogers
In just afraid of ruining it,, I've bricked a vibrant by just updating it from Samsung utility which is weird.
Thanks
Sent from my HTC-A510a using xda premium
timfoote said:
Maybe i spoke to soon...I just noticed it has reset to factory defaults. Not a big deal as I already backed everything up but i certainly wasn't expecting it!
Click to expand...
Click to collapse
you would have expected this if you had informed yourself as you should, before performing this kind of procedure on your phone.
Worked perfectly for me. My phone wouldnt complete the flash, so I went into CMD and unlocked it.
I've been trying to do this before, and many failed attempts.
So thank you.
worked
Fantastic summary.
Worked like a charm.
Bell Atrix with retail updates.
Thanks a million!
...Damnit, still can't remove Kobo; wtf!
Super guide
Thanks for the very clear instructions. Worked first time. The one thing that always seemed ambiguous to me was the memory fix. Do we need to apply it?
xeidy said:
What about android version 2.2.2 and system Version.4.2.11.MB860.Retail.end.FR
Build: OLYEM_ U4_2.1.1
IT'S bell phone atrix 4g unlocked and running on Rogers
In just afraid of ruining it,, I've bricked a vibrant by just updating it from Samsung utility which is weird.
Thanks
Sent from my HTC-A510a using xda premium
Click to expand...
Click to collapse
I also have an unlocked bell atrix 4g on rogers. If you dont have 2.3.4 you would have to update your phone with the bell original software. It wont take away your unlock as unlocks are permanent. after you upgrade follow this guide to unlock the Bootloader and feel free to use custom roms!
nabicat said:
Thanks for the very clear instructions. Worked first time. The one thing that always seemed ambiguous to me was the memory fix. Do we need to apply it?
Click to expand...
Click to collapse
well after I unlocked my bootloader I installed romracers CWM and DarkSide v2.1 to my phone. No issues with ram so far. I dont know if you intend on installing customs ( I assume so because what other reason would you have to unlock the bootloader? lol) but after the install my ram readouts seemed correct
Yes, you're correct. I checked available memory and its over 800 mb, so the fix must be in there.
Cheers
Working very well with Bell Atrix.
Thanks for big help.
Wondering if this instruction works with Hong Kong's ME860 2.3.4 also?
I'd love to try this!
MrJcc said:
Wondering if this instruction works with Hong Kong's ME860 2.3.4 also?
I'd love to try this!
Click to expand...
Click to collapse
I'm not sure if it works with hong kong version. If you check the link that I posted, it leads to a thread on here called international house of pudding. in that thread at the beginning it says that " China version ??: DANGER: Brick after OTA 2.2.2" So you would definitely have to ask someone around the forums or search to see if somebody has done it successfully
It is possible to remove the unlocked during the boot?
Sent from my MB860 using XDA App
Soft bricking often happens in when you try to install a ROM which is not optimized for your phone e.g:Installing i9100 SII ROM on your i9001.
Here is a basic tutorial on how to unbrick a i9001.
Requirements:
For unbricking your phone you are going to need these:
1.An official Samsung firmware
2.ODIN downloader
3.AriesVE.ops for ODIN usage.
4.USB cable
5.Samsung KIES drivers installed
6.Patience!!!
OK.first of all you need to check things above and make sure you have them all.
Fortunately when your phone is soft bricked(when soft bricked your phone doesn't boot into the OS And instead of that you'll see picture of a phone connected to a computer and on the connection line there's a warning sign) can get yo the download mode. So first get your phone in download mode by pressing this button combination: volume down+ home key+ power button
So then get set to use ODIN.
Connect your phone to the PC and make sure you have installed drivers and also killed every KIES process.(If you have done well till now you can see one black gets yellow and in Terminal you'll see 2 lines "detected","added") So start ODIN and place AriesVE.ops as the ops file then use your official firmware (extension should be like this |..... .tar.md5|).To get your firmware working tick "one package" and place you "MD5" file in "one package" location. Then after MD5 checking start the process and go grab a beer.
Wait about 7 to 10 minutes to see PASS on the block.
Then your phone would automatically reboot into your android OS. Then you can start rooting, Tweaking and other stuff again.
At least one you have your phone and your warranty back.
FAQs:
1.my phone gets stuck at setup connection. what should I do?
Chill out! Don't panic! Simply remove your battery for 10 seconds then do these things all again and proceed!
2.my phone boot loops what do I do?
Simply reboot your phone in the Recovery mode "volume down+ power" and wipe cache/dalvik cache if you can.
(Once I installed FOTA from stock recovery and that worked for me)(I suggest you install the official TWRP recovery from SDcard to have more options)
3.you tell me your questions!I'll edit the topic later!
At last feel free to ask any dumb question. Dumb questions are muck more valuable than dumb mistakes!
Please hit thanks button if I helped you out!
Sent from my GT-I9001 using xda premium
[GUIDE/FIX] {S4-MULTI} No Sound &/ WiFi &/ Bluetooth After Unbrick/Update? Read Me!
THIS GUIDE CAN APPLY TO ANY MODEL, PROVIDED YOU ENSURE TO GET THE PROPER FILES FOR YOUR VERSION!
I've had success myself flashing stock firmware from the M919V for Wind Mobile onto my I337M with no issue. This shouldn't be an issue. However, for the purpose of this guide, it is important that you get the firmware that was intended FOR YOUR DEVICE!
---
First head over here >> http://forum.xda-developers.com/showthread.php?t=2559693 >> and check out the original thread that helped me get to this resolution. Thank you to all the lovely people there!!
Before my softbrick occurred, I had flashed the NE1 modem through ODIN. I found that the same modem remained regarldess of the firmware I flashed. So I thought to match them up and give it another go. This worked great. This will work even if it was a regular S/W upgrade or install that caused the no sound and/or WiFi and/or Bluetooth issue.
Quick note before we begin: this guide assumes that you already went through a softbrick and have successfully come back from it, or went through a software update/firmware install which resulted in the same issue. Some of the steps in this guide may be able to be applied to some parts unbricking a phone, but this is NOT the intention. The intention is to help recover sound, WiFi and Bluetooth AFTER a successful unbrick or failed update/install otherwise.
DISCLAIMER: I am not responsible for your phone melting, imploding, turning into maple syrup or dying. Follow at your own will!
PRE-GAME CHECKLIST:
- Determine the ORIGINAL FIRMWARE that came on your device (this one was important for me, not sure how crucial it may be for others) - to be honest, I'm not 100% sure how to figure this out other than looking at the phone's box. It should notate which software version (SW-VER) it is. Before doing this, I was soft bricked, and had to use the very original 4.2.2 software for my carrier to recover from THAT. So maybe this part wasn't as important as I think, but I wanted to mention it anyway.
- The ORIGINAL USB cable for the phone - I suspect any high quality ones would work, but the one that came with the phone is a no-brainer
- ODIN 3.xx (I used 3.09)
- Samsung USB Drivers installed properly
- NO SD CARD (to be safe - this is optional as it should not be touched throughout the process)
- DO NOT, under any circumstance, use a USB hub for this procedure. Make sure it's direct into your computer with no extensions. I also recommend a cable that is 6ft or shorter if possible, but the quality of the cable is the most important
DO IT:
1) Download the ORIGINAL firmware that came with your phone (if you weren't able to determine this, I'd say the most recent one should be safe to flash, unless you softbricked while on 4.2.2 or 4.3 - in that case I would stick with the corresponding version, though I'm not sure how it would be affected since I didn't run into this)
2) Extract the file (I use 7Zip) and ensure there is one .tar.md5 file as a result - do not extract again
3) Boot up the phone into Download Mode (PWR off completely, then hold VOLDOWN + HOME + PWR together until the warning appears on the screen - click VOLUP to accept and proceed)
---PHONE WIPE---
This part is optional but I highly, highly recommend it.
4a) Flash Philz CWM (you can find the file and instructions on how to flash it through ODIN very easily)
4b) After flashing, it usually reboots into recovery. If it does not, do so manually: turn off the phone completely (hold the power button until the screen goes black) then quickly press the VOLUP + HOME + PWR buttons. When you feel a vibration, release the PWR button but KEEP HOLDING VOLUP + HOME. Keep holding those two until you see the phone turn off and come back on.
4c) Make sure you close ODIN once confirmed the flash is done
4d) Tap factory reset and confirm it
4e) Once done, choose the clean ROM install option and confirm that as well
4f) Reboot the phone and continue on with the steps
NOTE: if there is anything to backup, now would be a good time to do this.
---
5) Open ODIN (IMPORTANT: In Windows, right-click and choose "Run as administrator" - this helped avoid an error for me)
6) Connect your phone directly to a USB on your PC and confirm that ODIN recognized it (it should highlight the first box and have "COM#" listed)
7) Click the second section (AP / PDA) and choose the .tar.md5 file you got in Step 1
***NOTE: ODIN may look like it's freezing or hanging here - IT IS NOT, BE PATIENT - it is a large file and it will take a bit of time to verify the MD5 for it
8) Click Start and sit back - it should take 8-10 mins or so (8:55 for me) with KitKat, and 5-7 mins or so with JB.
9) Your phone should have rebooted into a fresh Firmware. If you hear the Samsung boot sound, GREAT! You should be good (test WiFi and Bluetooth if possible) and you're done. Assuming that's not the case, which is why you're here, proceed to the next step
***If it's stuck in a bootloop, you need to force Recovery mode and do a factory reset. To do this, turn off the phone completely (hold the power button until the screen goes black) then quickly press the VOLUP + HOME + PWR buttons. When you feel a vibration, release the PWR button but KEEP HOLDING VOLUP + HOME. Keep holding those two until you see the phone turn off and come back on. Use the VOL buttons to scroll to the factory reset option, and choose PWR to select. Then confirm on the next screen. Once that's done, wipe cache in the same way. Then, reboot, again in the same way. Now your phone should boot up
10) Go through setup and then go into Settings > More > About device. Observe the "Baseband version" section, and see if it matches the "Build number" section (starting from I337 and onwards). IF THEY MATCH, then repeat steps 5-10. IF THEY DO NOT MATCH, continue.
11) Download the matching modem file - ENSURE that the version of the modem you download MATCHES EXACTLY with the "Build number" in your phone's settings. Flash the file in ODIN in the AP / PDA section (if you need detailed instructions on this, it's a snap to find in XDA or Google)
12) Once done, reboot into the regular OS and verify that the "Baseband version" and "Build number" sections MATCH. If not, try to flash the modem again. After this has been verified, go ahead and follow steps 5-10 as many times as necessary until you hear that beautiful boot noise! It took me twice.
All the best and happy flashing guys! I'm not too much of an expert, just very good at explaining things, but I'll try to help as I can with any questions!
THANKS:
- All the great help thanks to input from around XDA in this thread (also listed in the beginning of this one): http://forum.xda-developers.com/showthread.php?t=2559693
- All the devs that work hard for us Canadian and AT&T guys over here