Related
DISCLAIMER: I AM NOT RESPONSIBLE FOR YOUR ACTIONS. IF YOU BRICK OR DAMAGE YOUR DEVICE IN SOME WAY, IT IS YOUR RESPONSIBILITY. THERE ARE SOME STEPS THAT MIGHT NOT BE LEGAL IN SOME COUNTRIES (CHANGING IMEI NUMBERS), AND I WILL NOT BE HELD RESPONSIBLE FOR THAT EITHER. EVERYTHING YOU DO WITH YOUR DEVICE IS YOUR OWN RESPONSIBILITY AND IF YOU FOLLOW ALL THESE STEPS YOU ARE AGREEING TO THAT. THIS TUTORIAL IS DONE FOR EDUCATIONAL PURPOSES.
Thanks to clubtech, rotohammer, koush, ayman07 and everyone in xda that has worked hard to make this possible. I did not come up with any of this, I only gathered it all from different sources and smashed it all together in an easy-to-read guide. Credit is due to all of those listed above, if I missed anyone please do let me know and I'll gladly add you here.
You will need
- P1000XWJJ4 firmware (pass: samfirmware.com)
- P1000XXJK5 firmware (pass: samfirmware.com)
- Odin 1.3
- Koush's zImage for T-Mobile Galaxy Tab
- flash_image
- I900AOJP3.bin Modem from HERE
1) Put you tab into download mode (Turn it off, when it's off, Press VolDown+Power until you see a yellow android and it says downloading...) (WARNING: All your data will be lost in the next step! Everything, INCLUDING the internal memory! Make sure to back everything up to your computer!)
2) Use Odin: Flash P1000XWJJ4 (PDA button) with P1_add_hidden.pit and make sure "Re-partition" is SELECTED, press Start and wait for it to finish. The device will reboot and it will turn on again, probably in russian.
3) Turn it off and put it on download mode again.
4) Use Odin: Press the reset button, then make sure "Re-partition" is UNSELECTED and there's NO PIT file, then flash P1000XXJK5 under "PDA".
5) The device will reboot with the latest euro firmware in english. The modem will probably be undetected, the device will be working kinda crazy (It might be slow and whenever you use something that uses the vibrator it'll get worse, the vibrator won't probably work, don't worry about this, it will be fixed in the next few steps)
6) Make sure you have flash_image and the tmobile_zImage in hand and issue these commands:
Code:
adb push flash_image /data/local/bin/flash_image
adb push tmobile_zImage /sdcard/
adb shell
su (make sure to select "Allow" when the Superuser dialog pops up on the tab)
chmod 755 /data/local/bin/flash_image
/data/local/bin/flash_image boot /sdcard/tmobile_zImage
sync
exit
7) Now, the kernel should be flashed, a reboot should fix all the weirdness. However, instead of rebooting, turn it off, and put it on download mode again (VolDown+Power)
8) Use Odin: Press reset on Odin, make sure "Re-partition" is UNSELECTED, and on the Phone button, flash the modem I900AOJP3.bin.
11) Wait for it to reboot. At this point, the tab should work fine, and the modem should be detected by the system. However, you won't be able to make calls or use the internet because T-Mobile is blocking data. Now, we need to change the IMEI number (READ DISCLAIMER ABOVE!)
12) Now, we need to backup all the contents in the /efs folder, that way, the IMEI will be corrupted, we want this to happen because T-Mobile is blocking the IMEIs on all T-Mo Galaxy Tabs so that data doesn't work unless you have the right plan/contract (BAD MOVE T-MO! WE DIDN'T EXPECT THAT FROM YOU, AT&T MAYBE, BUT NOT YOU!)
13) Backup the /efs folder (Notice: you must have busybox installed, get busybox installer from the market)
Code:
adb shell
su
busybox tar zcvf /sdcard/efs-backup.tar.gz /efs
busybox cat /dev/block/stl3 > /sdcard/efs_dev-block-stl3.img
exit
back to the shell in your computer, now use these commands to put those files in your computer, and save them somewhere safe.
Code:
adb pull /sdcard/efs-backup.tar.gz .
adb pull /sdcard/efs_dev-block-stl3.img .
14) Delete all contents from /efs and reboot. Easiest way to do it is using root explorer from the market. DO NOT DELETE THE ACTUAL FOLDER, JUST IT'S CONTENTS.
15) Done, you will be able to browse the web, send/receive SMS, and send/receive voice calls. The only issue at this moment is that it will only work on EDGE, 3G is not possible, YET.
Enjoy.
This method was posted earlier and is much easier i'd say. Thanks.
LordLugard said:
This method was posted earlier and is much easier i'd say. Thanks.
Click to expand...
Click to collapse
Where exactly? Please link me to the post that makes your T-Mo Tab make calls, using the Euro firmware and vibrator works and the tab doesn't go crazy.
As I said, all the guides I found were missing a few pieces. One was for AT&T Tabs, but I didn't find one that was for T-Mo tabs in a single piece, everything was scattered all around.
Sent from my mobile
velazcod said:
Where exactly? Please link me to the post that makes your T-Mo Tab make calls, using the Euro firmware and vibrator works and the tab doesn't go crazy.
As I said, all the guides I found were missing a few pieces. One was for AT&T Tabs, but I didn't find one that was for T-Mo tabs in a single piece, everything was scattered all around.
Sent from my mobile
Click to expand...
Click to collapse
The exact link i posted is how i got my Tmo Tab flashed to Euro firmware with calls and 2G data. Much easier steps. Not berating your method.
http://forum.xda-developers.com/showthread.php?t=886714
EDIT** Didn't realize i didn't post link in first reply.
LordLugard said:
The exact link i posted is how i got my Tmo Tab flashed to Euro firmware with calls and 2G data. Much easier steps. Not berating your method.
http://forum.xda-developers.com/showthread.php?t=886714
EDIT** Didn't realize i didn't post link in first reply.
Click to expand...
Click to collapse
Oh ok, didn't notice that also works for T-Mo tabs. Oh well.
Thanks.
Thanks for posting this guide. I followed the instructions and still cannot make phone calls. It seems to dial but the T-Mobile automated voice operator says "The phone you are using does not allow outgoing calls."
I removed all /efs files and rebooted, then verified that the IMEI was corrupt afterwards.
Any ideas? Maybe T-Mobile is blocking the corrupt IMEI number now?
Thanks in advance!
Are you able to use the market ok with your imei corrupted?
droooid said:
Thanks for posting this guide. I followed the instructions and still cannot make phone calls. It seems to dial but the T-Mobile automated voice operator says "The phone you are using does not allow outgoing calls."
I removed all /efs files and rebooted, then verified that the IMEI was corrupt afterwards.
Any ideas? Maybe T-Mobile is blocking the corrupt IMEI number now?
Thanks in advance!
Click to expand...
Click to collapse
I don't think so. Are you using a SIM card with a plan that has phone calls or are you using the same SIM card? Your Tab has a webConnect plan that does not allow phone calls, so you need to put in a SIM card that has data and calling plan.
They are blocking the IMEI for data, as far as I know, so if you use your tab to go online (without using Wifi), and it goes to my.t-mobile.com even if you try to go to xda-developers.com then they are blocking it, but in your case, it's just probably the calling plan.
calebchosen said:
Are you able to use the market ok with your imei corrupted?
Click to expand...
Click to collapse
Yes sir, Market works, it even updated itself to the latest version.
T-Mobile usa modem
sorry voice failed 3 times. sorry again will update if i can figure out why I lost voice after getting it to work.
the attached file is the original t-mobile galaxy tab modem. NO VOICE but 3G on EUROFIRMWARE
hi zdentist now m use Tmobile with EURO ver all work fine
but i can get 3G data what can i do Enable 3G service ??
this MODEM.BIN work my Tmobile euro ver?
Why make this so difficult? Just flash modaco's custom rom and kernel for Tab with Odin and its done...
USED TMOBILE TAB WITH EURO VER CALLING WORK FI9 BUT CANT USE INTERNET WITH SIM DATA
AND ALSO CONFORM THAT THIS IS POSSIABLE I USE 3G DATA IN TMOBILE?
m using this tab ver
fahadz said:
USED TMOBILE TAB WITH EURO VER CALLING WORK FI9 BUT CANT USE INTERNET WITH SIM DATA
AND ALSO CONFORM THAT THIS IS POSSIABLE I USE 3G DATA IN TMOBILE?
m using this tab ver
Click to expand...
Click to collapse
Did you get your answer from the modem switcher thread? PM me if you're still stuck.
fahadz said:
hi zdentist now m use Tmobile with EURO ver all work fine
but i can get 3G data what can i do Enable 3G service ??
this MODEM.BIN work my Tmobile euro ver?
Click to expand...
Click to collapse
sorry for the late reply. yes but you won't be able to make voice calls with this modem.bin file only DATA unfortunatley
Reference http://www.samfirmware.com/WEBPROTECT-p1000.htm
Saw under the Asia Firmware 'P1000DXJM4 ## ODIN 1.7 | P1.PIT | Version 2.2 | 2010 December' is available and to be cautious, i seek seniors' opinion before i go ahead and flash mine ^^
Any recommendation on how to proceed is appreciated, esp with ODIN (dont know what it is even read so much about this word)!
I already backup with TB
edit: Connect to Kies and says 'This device's version cannot be updated.' Stating PDA: JK2 / Phone: JJ2 / CSC: JJ2. now even more confused
edit update after flashed JME instead of JM4 (long story short):
"i will write down the event by event of recovery as reference:
1. flash the JVJL1 (no problem on reboot) by mistake then flash JM4 (missing dbdata.rfs) tar file downloaded from samfirmware.com and failed to reboot due to the missing file.
2. did some silly step and resulted in (phone .. ! .. pc) icon
3. run odin 1.7 and plug the usb and odin show is connected with tab
4. flash JM4 (yes with missing dbdata.rfs) and able to bring the tab back to download mode but unable to reboot into tab
5. flash Roto's dbdata.rfs file (http://forum.xda-developers.com/show...91&postcount=1) and able to reboot right after but missing pda & csc info (*#1234#)
6. tried the hard reset (http://forum.xda-developers.com/show...&postcount=106) but no help
7. download Roto's pre-rooted JME 3 files as mentioned (http://forum.xda-developers.com/showthread.php?t=895827) and finally boot the tab with full *#1234# details.
* So if you see the (phone .. ! .. pc) icon dont panic. like KChauJen said, able to solve with enough reading. i listed my route to recovery as reference to give you positive hope to retry.
TB's backup in Internal SD and before flashing JME, i copied the TB folder to my hdd during the missing pda & csc boot and did a backup on JME reboot, copy paste back to TB folder under internal sd and the restore work flawlessly."
cant be updated? er, i was from jk2 to jm4. did you applied oclf? if you did, try undo it b4 anything.
Hi fastcx, thanks for replying and sharing your experience. I did some further reading in some singapore forum saying have to run the kies patch (http://forum.xda-developers.com/showthread.php?t=835628) and spoof firmware version in order to update. i have yet to try due to somewhere in the same forum also said that once updated:
1. cant go back version
2. z4root wont work (which i am already using)
may i know have you rooted your SGT? need more solid info before taking the route to update the firmware as already using SGT as my primary device. I havent OCLF yet
rooted, since day 1, after every update (jj1>jj2>jk2) able to root with z4root till jm4 which requires SOC(SuperOneClick). To use kies, switch back to samsung default launcher b4 u connect using kies. I do not have any issue there. Another note is that after root, i always go back to /system/app to check n remove any apps that I do not need using adb shell.
The interface changed, to darker color, dlna client really working now, oclf performance improvement might not be obvious this time around. I suspect they really optimized it, everything is more stable now. Over protective I would say, cause any previous flashlight apps isnt going to sustain the led light for over 2sec. Default browser is a wee bit smoother now.
SuperOneClick is very easy to use anyway, so give it a try, oclf is useful only when u have over 400mb apps + loads of sms & contacts..anything related to I/O will have improvement.
The worse case scenario is just if kies still do not allow u to update, just use odin..what did you do previously? How do you update previously?
VNPython said:
Reference http://www.samfirmware.com/WEBPROTECT-p1000.htm
Saw under the Asia Firmware 'P1000DXJM4 ## ODIN 1.7 | P1.PIT | Version 2.2 | 2010 December' is available and to be cautious, i seek seniors' opinion before i go ahead and flash mine ^^
Any recommendation on how to proceed is appreciated, esp with ODIN (dont know what it is even read so much about this word)!
I already backup with TB
edit: Connect to Kies and says 'This device's version cannot be updated.' Stating PDA: JK2 / Phone: JJ2 / CSC: JJ2. now even more confused
Click to expand...
Click to collapse
Yeah... I'm in your case.
Thinking does it would be updated or not???
1. cant go back version
2. z4root wont work (which i am already using)
Click to expand...
Click to collapse
Just look at inside of tar file, and according to the Chainfire's Warning, the three files:
* boot.bin
* Sbl.bin
* zImage > 7,000K
So, this firmware would be has the protected boot loader. It would give us a lot of trouble in the future of updating and downgrading.
I think, this firmware can be updated with the help from Roto, eliminate the three files above and just take the PDA part.
I was using CSC: XEV (Vietnam) then to SIN (Singtel) and feel good and when Nov'10 update came, updated via Kies wihtout any trouble. When Dec'10 update came, tried with SIN resulted unable to update, switch back to XEV also resulted unable to update. I havent try XSO which the singapore forum stated successful for those with that CSC.
So i have to try to switch to XSO and report in later. be it protected boot loader or not, as long as we want stable and more 'juice' to service our daily SGT needs, no choice but to follow. I do believe as days goes, seniors like Roto alike will crack the nut for us to appreciate further.
on other note, my default email (not gmail) app seem got problem whenever you click reply or forward any email will result in force close. do not know if this bug related to after i switch from SIN to XEV (to try update) then switch back to SIN and follow up by restore using TB.
anyone has similar force close on the default email app?
backing up with TB now should we (those yet to update jm4) wait for Roto to do his magic for this update?
edit: tried with XSO and also unable to update... that really puzzle me.
edit 2: unroot with z4root and try still unable to update... now looking at ODIN route
perhaps odin route is the best solution for your case, but from jk2 > jm4 not sure if pit file is needed? repartitioning needs it tho, perhaps its good that u do back up of everything, let us know ur flashing result. Odin will definitely able to do the job
oh no... T_T somehow i downloaded P1000JVJL1 (Arabic) by mistake and Odin 1.7 with Auto Reboot & F. Reset Time, selecting the mistaken Arabic firmware (PDA) and flash it without any problem (JVJL1 / JXJK3 / JVJK4) and able to reboot itself.
After notice the wrong firmware, downloaded the right one (P1000DXJM4) from samfirmware.com and using Odin 1.7. Repeating the above steps but the phone briefly flash and came back the 'download mode' and nothing happened although Odin stated passed without any error.
I able to hold the power to shutoff and turn on again and the screen shows the samsung logo screen and stay flashing the word 'samsung' with 1 then 2 quick vibrate (like force close) and didnt boot into the main screen!
what should i do next?? is it bricked?? T_T
edit: the downloaded filename is 'P1000DXJM4_P1000DXJM2_P1000OLBJM1_HOME.tar' and anyone know if correct one?
edit 2: now i am downloading DXJK2 and see if i am able to revert the flash of JM4 T_T
edit 3: is over T_T saw the (phone .. ! .. pc icon)
This is due to dbdata.rfs missing. Please refer to the guide of flashing JMC/D/E series.
BTW, I have a problem is Camera Faulty error when start the camera app. Somebody mentioned that the LCD density can't set too small, but I have reverted it back to default 240, the problem still there. Any clue about it?
Sent from my GT-P1000 using XDA App
thanks dahuzi, i wonder if i choose to flash eu rom by Roto, would his rooted bring my tab back to operation? appreciate any help to bring back my tab.
i am able to bring my (phone .. ! .. pc icon) to the download mode. flashing anything before JM4 wont work anymore (fail at odin 1.7 and 1.3) and i am able to go back to hard reset option (holding vol up and power up). now i need to get the TB backup from the int SD before i try anything new. possible to retrieve in download mode?
edit: where to find the dbdata.rfs for this JM4? can anyother dbdata.rfs from other firmware able to fill it in? help ~ T_T
Hi VNPython,
Your case is complecated one, take it easy and read the thread from Chainfire "WARNING! Do not flash ... ", in there, a lot people has solved with different path.
Be patient, Bro. At that moment, your TAB is not Brick yet, but be careful because it's on the way of the End.
Wish you luck.
Take care.
ha.. i hope to win this war ^^ and learning the way of android!!
edit: just a quick question - does TB backup all user and app data in internal SD or External SD? i got bunch of files in my ext SD folder '.android_secure' and inside have files like 'com.keramidas.TitaniumBackup-1.asec' can any senior confirm is a valid TB backup files and can be used to restore my user & app data? many thanks!
TB (TitaniumBackup) file in the internal SD (in my case is the default), please double check.
Please give us your detail of winning as I'm scare of Samsung flash. My history is, 4 years ago, I bricked my Omnia phone Samsung after I flashed the rom from SIN to AUS. And, this's my second device on Samsung but this is Android and I want to learn the new OS.
Take care, Bro.
hey guess what? i managed to get a file for dbdata.rfs from Roto and got the tab back live but missing PDA and CSC field (checking with *#1234#). tried the reset to get the pda and csc back but failed.
learned quite a few things along the way and will update this thread after completing my mission to update my tab to JM4.
windows seem cant extract and tar file for android tar files. i tried to extract jm4 files and add dbdata.rfs into it but when flashing, it fail.
worst come to worst, flash the JVJL1 to get the working tab again
i hope Mr. Roto could let me know what software to install on windows that able to 'untar' and 'tar' properly with android (linux) files. tried 7z and winrar both cant untar without error.
try using winrar to do the add on of dbdata.rfs, anyway, good luck next time, double check what you downloading
fastcx said:
try using winrar to do the add on of dbdata.rfs, anyway, good luck next time, double check what you downloading
Click to expand...
Click to collapse
Wow... another Maitre!!! What's your winrar???
Look and read:
.....i hope Mr. Roto could let me know what software to install on windows that able to 'untar' and 'tar' properly with android (linux) files. tried 7z and winrar both cant untar without error.
Click to expand...
Click to collapse
Thanks
sorry for the late update as yesterday too late to post anything after able to get my tab back to life! the learning curve is nice and not stressing since many time i see the icon of (phone .. ! .. pc) yet i am able to bring the download (digging) icon back again always.
i will write down the event by event of recovery as reference:
1. flash the JVJL1 (no problem on reboot) by mistake then flash JM4 (missing dbdata.rfs) tar file downloaded from samfirmware.com and failed to reboot due to the missing file.
2. did some silly step and resulted in (phone .. ! .. pc) icon
3. run odin 1.7 and plug the usb and odin show is connected with tab
4. flash JM4 (yes with missing dbdata.rfs) and able to bring the tab back to download mode but unable to reboot into tab
5. flash Roto's dbdata.rfs file (http://forum.xda-developers.com/showpost.php?p=9305891&postcount=1) and able to reboot right after but missing pda & csc info (*#1234#)
6. tried the hard reset (http://forum.xda-developers.com/showpost.php?p=9482192&postcount=106) but no help
7. download Roto's pre-rooted JME 3 files as mentioned (http://forum.xda-developers.com/showthread.php?t=895827) and finally boot the tab with full *#1234# details.
* So if you see the (phone .. ! .. pc) icon dont panic. like KChauJen said, able to solve with enough reading. i listed my route to recovery as reference to give you positive hope to retry.
TB's backup in Internal SD and before flashing JME, i copied the TB folder to my hdd during the missing pda & csc boot and did a backup on JME reboot, copy paste back to TB folder under internal sd and the restore work flawlessly.
after 1 days usage, the trouble found is email app still being force close whenever you reply or forward any email. any senior have similar force close on original email app?
KChauJen said:
Wow... another Maitre!!! What's your winrar???
Look and read:
Thanks
Click to expand...
Click to collapse
My bad. How polite of you.
Back to topic, VNPython everything there is a first time it's good info here. Perhaps you can edit your 1st post with info from your last post?
EDIT: 1 thing though, do you have any issue regarding using samsung apps?
samsung app can use, checked my CSC and its KOR. Apps: Vlingo words to action, Vietnamese Dictionary application & blinkx Beat. didnt try any of them. just *#272*IMEI# and there's no SIN or XEV or XSO or Asian Sales Code in the Roto JME (EU) multiCSC. maybe will try to download multicsc with asian sale code.
* on the email app force close, i delete the email account and re-setup them, and the force close is gone. could be due to TB's restore? anyway, is solved ^^
I wonder will i be able to flash DXJM4 if there is a full tar file?
VNPython said:
....
I wonder will i be able to flash DXJM4 if there is a full tar file?
Click to expand...
Click to collapse
Please consider it carefully, Bro.
What I looked inside of the tar file, and according to Chainfire's Warning, it has the protected boot.
If we can eleminate the three files:
* Boot.bin
* Spl.bin
* zImage
and put back to the tar file with the encrypted code by Samsung (maybe we can ask Roto) then we can flash this modified firmware JM4.
FYI.
first..im sorry if my english so bad..i hope u know waht i mean...i'm try to change banner pulldown from SPRINT to my name via DFS 4.0.2 but after reboot my signal gonna blank and i check the about device baseband and hardware version unknown/blank...then i check status meid, imei, iccid is unknown and device status was modified...i dunno how to fix it...i hope somebody could help me...this toatally my bad...
wifi okay, bluetooth okay, nfc okay, just phone, data, and signal bar missing....
1. Download the stock recovery here and put it on your internal sdcard (inside no folders): http://forum.xda-developers.com/showpost.php?p=33850881&postcount=88
Use this command using the app Terminal Emulator (or use adb on your computer) to flash that stock recovery image:
Code:
su
dd if=/sdcard/l900.img of=/dev/block/mmcblk0p9
2. Flash the stock LJ1 package (through odin) here: http://forum.xda-developers.com/showthread.php?t=1968136
You phone should now be fixed.
More discussion on your problem here: http://forum.xda-developers.com/showthread.php?t=1997150
if you're rooted all you need to do is change the build prop to make it say whatever you want.
weehooherod2 said:
1. Download the stock recovery here and put it on your internal sdcard (inside no folders): http://forum.xda-developers.com/showpost.php?p=33850881&postcount=88
Use this command using the app Terminal Emulator (or use adb on your computer) to flash that stock recovery image:
Code:
su
dd if=/sdcard/l900.img of=/dev/block/mmcblk0p9
2. Flash the stock LJ1 package (through odin) here: http://forum.xda-developers.com/showthread.php?t=1968136
You phone should now be fixed.
More discussion on your problem here: http://forum.xda-developers.com/showthread.php?t=1997150
Click to expand...
Click to collapse
Not working...but thanks man...
having the exact same problem- did you get it fixed and if so, how?
this same thing happened to me.
i downloaded odin mobile (i lack a pc)
i downloaded a file called SPH-L900_LJC_ROOT_Restore.exe
(cant remember where i found it but all i used is google so im sure you can find it too)
i unzipped it
i flashed it
my phone works now
hope this helps
Hello, this is really weird. In fact, when I insert the SIM to my Note 2 N7100 and turn it on, it allows me to make emergency call, but I cannot use it to make any others and it doesn't show the carrier name (it shows Emergency call only). And when I try to use it to make normal phone calls, it says that I am not registered to a mobile network. I try to factory reset my phone, but the problem remains. I then try to remove the SIM card, and it says that I need to insert a SIM card (that means that it is not a hardware problem since it recognizes the card). I then try to go to the mobile network setting to try to connect to the network manually, it connects me but it shows me a warning which says that the mobile network service is not available (and the Emergency call only label remains). However, I am sure that this is not the problem of the card neither since when I insert the card to my Moto MB860, I can make calls as usual. So, what is the problem ??? It seems to me that the problem happens spontaneously since it works perfectly until yesterday. And all other wireless function works fine including wifi , Bluetooth and GPS and the only thing goes wrong is 3g and 2g.
Additional information:
ROM: Omega v.16
Carrier: Fido Canada (as you can see)
Thanks.
First of all, check whether you can see the IMEI of the device. If you can see.
1. Contact your network operator and check whether your IMEI is blacklisted or not.
If you cannot see the IMEI
1.Restore the efs and persist backups (if you have one)
2. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site or from here)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you.
For this, you’ll need root. If you have a root-enabled kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC: enter *#272*imei# on the phone tab.
Try this . I'm not sure it works. Just give it a try on yourself.
Trying the above mentioned methods could be vulnerable to your phone if it not done properly. So do it carefully. If you have any doubts feel free to ask me or search elsewhere. But, don't blame me for a fully dead phone. I am not at all responsible for any...
Noob 1st post......have had similar problems with koodo CDN
Not gonna give such an in depth suggestion as above.....he's something simple to try.
I live in a dead zone and often my phone ( galaxyAce) will switch to no service. Even after refreshing and selecting network under settings, it says it's connected, but isn't. A simple apk that always fixes the problem for me is Network Signal Booster @ theplaystore
jabrif said:
First of all, check whether you can see the IMEI of the device. If you can see.
1. Contact your network operator and check whether your IMEI is blacklisted or not.
If you cannot see the IMEI
1.Restore the efs and persist backups (if you have one)
2. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site or from here)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you.
For this, you’ll need root. If you have a root-enabled kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC: enter *#272*imei# on the phone tab.
Try this . I'm not sure it works. Just give it a try on yourself.
Trying the above mentioned methods could be vulnerable to your phone if it not done properly. So do it carefully. If you have any doubts feel free to ask me or search elsewhere. But, don't blame me for a fully dead phone. I am not at all responsible for any...
Click to expand...
Click to collapse
I tried a simple way which is format everything and flash another ROM but the problem remains.
TRS_80 said:
Noob 1st post......have had similar problems with koodo CDN
Not gonna give such an in depth suggestion as above.....he's something simple to try.
I live in a dead zone and often my phone ( galaxyAce) will switch to no service. Even after refreshing and selecting network under settings, it says it's connected, but isn't. A simple apk that always fixes the problem for me is Network Signal Booster @ theplaystore
Click to expand...
Click to collapse
I don't know that we are in the same situation since at home I often got a good signal and this happened to me only since yesterday.
jabrif said:
First of all, check whether you can see the IMEI of the device. If you can see.
1. Contact your network operator and check whether your IMEI is blacklisted or not.
If you cannot see the IMEI
1.Restore the efs and persist backups (if you have one)
2. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site or from here)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you.
For this, you’ll need root. If you have a root-enabled kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC: enter *#272*imei# on the phone tab.
Try this . I'm not sure it works. Just give it a try on yourself.
Trying the above mentioned methods could be vulnerable to your phone if it not done properly. So do it carefully. If you have any doubts feel free to ask me or search elsewhere. But, don't blame me for a fully dead phone. I am not at all responsible for any...
Click to expand...
Click to collapse
Some updates;
- IMEI is checked.
- I do not have any efs backup
- nv_data.bin has been deleted and recreated
- trying to register for the firmware
- My phone is always rooted.
Dan Law 001 said:
Some updates;
- IMEI is checked.
- I do not have any efs backup
- nv_data.bin has been deleted and recreated
- trying to register for the firmware
- My phone is always rooted.
Click to expand...
Click to collapse
Results..??
Sent from my GT-I9001 using xda premium
jabrif said:
Results..??
Sent from my GT-I9001 using xda premium
Click to expand...
Click to collapse
I need to get the firmware first... since I already passed the download quota for today... need to wait until tomorrow...
Mmm... I heard that you mentioned clearing the EFS in your given procedure, but I do not think that I modified that folder... However, about few days ago, since I want to gain better control on the volume on my headphone remotes, I did modify the file called Generic.kl in system/usr/keylayout, but I restore it after since it didn't work. However, I don't think that this modification will trigger something in the efs folder since it has different directory. By the way, I did some research online and they say that the efs contains information about the carrier on the phone, so will there's a greater chance that the problem is caused by the possible modification on the efs than any other factor and will there also something else that possibly trigger the similar effects?
Sent from my GT-N7100 using xda premium
Still nothing
FINALLY!
We Present To You
SamPWND!
Root for the USA Variants of the S8 & S8 Plus Devices!
(This thread will focus only on the S8+)
This thread had been closed/locked until further notice. The thread and links should remain active and the thread has served it's purpose. You will need to search the thread if you have any questions pertaining to root or any errors/issues that you are facing. The other reason I have decided to close the thread is because it has gone off topic one too many times, people like to argue and debate and MODS have had to come in here 1 too many times to clean it up so as to make life easier, I will just shut it down. Please do not bombard me with PM's for root assistance because if it has been answered in this thread already (and it most likely has) I will just direct you to search in the thread if I am able to respond at all.
ALSO, please do not utilize our firmware/root files/method without gaining permission first or I will ask for the thread to be removed/locked. Just because the thread gets closed does not mean we didn't spend a lot of time to get to this point.
Thank you and enjoy SamPWND root!
DISCLAIMER:
We are not responsible for any damage done to your device as no one is "forcing" you to root your phone! If you are not sure of how to follow instructions or use ADB then I would suggest waiting for someone to help you or that you read up on how these things work before diving head first. The ENG system is not very stable when it comes to root as well as it has a ton of tools and binaries not available on stock devices so we are not responsible if you break something while on any firmwares but especially while on the ENG firmware.
DISCLAIMER 2:
Please do not take our work and post it elsewhere. We spent a lot of time on this for people to take it and use it as if it is their own. With that being said, if you have a better process for something or find any issues/errors, please PM myself or one of the listed contributors of this root method, do NOT post it directly in the thread because it causes confusion. We know with 100% certainty the files and method presented WORK. If it is not working for someone there are a number of possible reasons why. If users start modifying our files/scripts and posting them and you decide you are going to use someone else's files/scripts, do not post in our threads asking for us to help you because we will have no idea what was modified or changed and will just tell you to use the original files.
Returning to Stock:
- It is possible to return to 100% stock and it is very EASY to do.
- This is the reason why I provide both Normal, and Comsey ODIN's.
- All you need is a full stock 4 files firmware of your choice.
- Extract those files. Open ODIN and select the 4 files in their respective slots.
* IF YOU GET ERRORS such as model mismatch, start with 1 partition at a time to find out which one is throwing the error. (In my experience, it is the BL file that causes the error.) Once you find the culprit, throw that partition into the other ODIN. (For example, the BL file is giving an error in Comsey ODIN, throw the BL file in NORMAL ODIN and flash it by itself.)
* Typically you might have to throw individual partitions into either of the ODIN's but in the end you will be back on full stock firmware.
What doesn't work while rooted?
- On ANY ROOTED device, anything that utilizes "SafetyNet" will NOT work.
- Magisk and/or SuHide will NOT work. Our bootloader is still locked and these two modify the boot.img which would cause our devices to not boot up and having to start the root process over again, you have been warned!
- Systemless root also does NOT work. Again, this patched the boot.img which we cannot do because of our locked bootloader.
- Battery currently only charges to 80%. There are a few that feel it legit doesn't charge fully but others are claiming they get the same amount of life as they did with a 100% battery so the 80% might just be a visual issue or "fake" when it is really at 100%. Either way, we are still looking into this.
Main Contributors:
@elliwigy
@Harry44
@akiraO1
@BotsOne
@GSMCHEN
@jrkruse (for uploading system.img.ext4 and his root zip for the part 2 instructions)
@V0idst4r (for help in creating a "1 click" method for part 1!)
Initial Description on the process:
We are essentially flashing a modified 4 file firmware package in ODIN and then utilizing a few binaries in conjunction with SU binary and a permissive kernel. We will then be running some ADB commands and in order to have a fully working, amazing root with all things working we will be utilizing a stock system.img & a root script in conjunction with Flashfire. If you want to know all the technical details, you can take apart the files if you would like. It is released, so it is no longer a secret!
PART 1 Instructions: NEW
Flashing SamPWND 4 Files Firmware:
1) Download the PART 1 FILES Listed Below (this includes SamPWND_Root.zip and Initial ODIN 4 Files FIRMWARE and ODIN's if you do not already have them.)
2) Extract the 4 Files ODIN Firmware Package (also extract the ODIN's if you do not have them already.)
3) Open Comsey ODIN and select each partition and then select the files from the 4 File Firmware Package you extracted (BL goes in BL slot, AP in AP, CP in CP & CSC in CSC.) The options you select in ODIN shouldn't matter but I typically select F. Reset Time, Auto Reboot, Re-Partition, Nand Erase All & Update Bootloader.
4) Press Start and Wait for it to Finish. Once it finishes, if it boots into stock recovery simply select "Reboot System"
Take a breather, the ODIN portion is done (unless you have to start over for some reason...)
Now the NEW Root Process:
1) Once the phone is booted up, make sure you have ADB Enabled and connected to your PC. It should have prompted you to accept USB debugging as soon as it booted up.
2) Unzip the SamPWND_Root.zip
3) Double click "step1"
4) Wait for it to finish and once it reboots and comes back on you will be rooted with SuperSU!
5) Continue to PART 2 for "EVEN BETTER ROOT"
* It is a Windows bat file so not sure if it works on MAC. If you can't run bat files, use the OLD instructions.
* The bat will take about 30 seconds to run it's course. This is due to giving enough time for the remount script to mount the system as RW.
PART 1 Instructions: OLD
1) Download the PART 1 FILES Listed Below (this includes Systemroot + ADB zip, Initial ODIN 4 Files FIRMWARE and ODIN's if you do not already have them)
2) Extract the 4 Files ODIN Firmware Package, Also extract the ODIN's if you don't have them already.
3) Open Comsey ODIN and select each partition and then select the files from the 4 File Firmware Package you extracted (BL goes in BL slot, AP in AP, CP in CP & CSC in CSC.) The options you select in ODIN shouldn't matter but I typically select F. Reset Time, Auto Reboot, Re-Partition, Nand Erase All & Update Bootloader.
4) Press Start and Wait for it to Finish. Once it finishes, if it boots into stock recovery simply select "Reboot System"
Take a breather, the ODIN portion is done (unless you have to start over for some reason...)
Now the ADB Process to actually Root:
1) Extract the Systemroot + ADB zip listed below in an easy to find directory.
2) Make sure phone is connected to PC and ensure USB Debugging is enabled.
3) In the folder you extracted, you should see a "cmd-here" file. Double click it and it should open up an ADB cmd window.
4) Now we will start with the ADB commands:
- Type
Code:
adb push systemroot /data/local/tmp
What it will look like:
C:\Users\Thomas\Desktop\Minimal ADB and Fastboot>adb push systemroot /data/local/tmp
/data/local/tmp/systemroot/: 8 files pushed. 0 files skipped. 10.0 MB/s (7072263 bytes in 0.673s)
- Type
Code:
adb shell chmod -R 7777 /data/local/tmp
What it will look like:
C:\Users\Thomas\Desktop\Minimal ADB and Fastboot>adb shell chmod -R 7777 /data/local/tmp
C:\Users\Thomas\Desktop\Minimal ADB and Fastboot>
- Type
Code:
adb shell setsid su
What it will look like:
C:\Users\Thomas\Desktop\Minimal ADB and Fastboot>adb shell setsid su
(It will be blank with the blinking cursor, move to next step)
- Type
Code:
id
(you should at this point see that your are in a root shell!)
What it will look like:
id
uid=0(root) gid=0(root) groups=0(root),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats),3009(readproc) context=u:r:shell:s0
- Type
Code:
echo /data/local/tmp/systemroot/remount2.sh > /sys/kernel/uevent_helper
What it will look like:
echo /data/local/tmp/systemroot/remount2.sh > /sys/kernel/uevent_helper
(Again, it will be blank with a blinking cursor after you type the command in, move to next step)
- WAIT ABOUT 30 SECONDS BEFORE MOVING TO THE NEXT COMMAND
- Type "
Code:
mount
" (you should now see rw next to rootfs and system partitions)
What it will look like:
mount
(After we type in mount, we are looking for the below two items to say rw like they do in the next two lines)
rootfs on / type rootfs (rw,seclabel,size=1586716k,nr_inodes=396679)
/dev/block/sda19 on /system type ext4 (rw,seclabel,relatime)
- Type
Code:
sh /data/local/tmp/systemroot/root.sh
What it will look like:
sh /data/local/tmp/systemroot/root.sh
rm: /system/bin/install-recovery.sh: No such file or directory
cp: /system/bin/.ext/.su: No such file or directory
chmod: /system/bin/.ext/.su: No such file or directory
chcon: /system/bin/.ext/.su: No such file or directory
touch: '/data/.supersu': Permission denied
/data/local/tmp/systemroot/root.sh[55]: can't create /data/.supersu: Permission denied
chmod: /data/.supersu: No such file or directory
C:\Users\Thomas\Desktop\Minimal ADB and Fastboot\NEWSAMPWNDFILES>
5) If you followed all of the above commands to the T, your device will reboot and you will have SuperSU installed.
6) Install Flashfire from the Play Store.
7) Up to this point, you are on an ENG system.img with root that doesn't function the way we would like it to. This means you will feel a vibrate every time you try to gain SU access as well as it will take quite a while for an SU prompt. You can stay on this root if you would like to experiment with the ENG system, but outside of that I would HIGHLY recommend you proceed to the STEP 2 PROCESS.
PART 2 Instructions:
1) Download the PART 2 FILES listed below (this includes the system.img.ext4 and the add CSC Systemroot zip both provided courtesy of @jrkruse , view post #195 for specifics on what these are but essentially they are stock QD2 system.img and the zip has multi CSC, root, and a bunch of other goodies!)
2) Extract the System.img.ext4 zip and place that actual "system.img.ext4" onto the Internal SD Card (might work from external but some users have reported issues with chainfires root.zip and FF with external sd cards, this is not a fault of the SamPWND files/process.)
3) Place the entire Add CSC Systemroot zip onto Internal or Externdal SD Card (THIS FILE DOES NOT NEED TO BE UNZIPPED, THROW THE WHOLE ZIP FILE ONTO SD CARD OR INTERNAL)
4) Open Flashfire and grant it root when it prompts you. IF FLASHFIRE IS NOT LOADING FILES AND YOU JUST SEE A CIRCLE OR LIKE ITS CONSTANTLY LOADING, PUT THE PHONE IN AIRPLANE MODE AND THEN GO BACK INTO FLASHFIRE AND THE FILES SHOULD NOW APPEAR.
5) Press the + sign and select "Flash Firmware Package" & navigate to where you placed the system.img.ext4 and select it
6) Press the + sign and select "Flash ZIP or OTA" & navigate to where you placed the Add CSC Systemroot zip and select it, select Mount System as r/w
7) Press the + sign and select "Wipe" and select System data, 3rd party apps, Dalvik cache, Cache partiton, Cache Partiton format
8) Now, long press on "Wipe" and make sure it is on the top by dragging it. The order should be Wipe, Flash Firmware Package & finally Flash ZIP or OTA
9) Make sure the "Everoot" is disabled!
10) Flash away!
If you followed all of PART 1, then followed all of PART 2, then you will be updated to QD2, rooted with busybox (and have some other goodies) and the phone will be running great! Root will be stable and snappy as ever. Adaway, Root Checker, V4A etc. etc. are now all possible.
XDA:DevDB Information
S8 Plus SamPWND ROOT, ROM for the Samsung Galaxy S8+
Contributors
elliwigy
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
ROM Firmware Required: Android 7.0, Any Current Firmware
Based On: Stock Touchwiz
Version Information
Status: Beta
Current Stable Version: 1
Stable Release Date: 2017-08-19
Current Beta Version: 1
Beta Release Date: 2017-08-19
Created 2017-08-19
Last Updated 2017-08-19
DOWNLOADS SECTION:
PART 1 FILES:
SamPWND_Root.zip
https://mega.nz/#!8YcgTSwI!hIfbdJZ466sr1AyfiHLdtr1p-To0QdthTPDmVwtv0dc
Initial ODIN 4 Files FIRMWARE
https://mega.nz/#!5cUjnCwK!Zgw5_CaINbES08gwDzl7yMN0N4nzm56Fa12ow-gppKA
Mirror: https://www.androidfilehost.com/?fid=961840155545589828
AFH MD5: 73720c409782b751355b9443a003a6e8
Normal + Comsey ODIN
https://mega.nz/#!cFN2DD4C!I7AT4TgNSzBp7Py0UhC7pHZ0M4WDQhEC5qj2xD_qluM
Systemroot + ADB zip - OLD
https://mega.nz/#!1MVDhZxQ!Wd4Umvju1sS1DAe-jBcTue9NKSJ4co0I2gwiyC3c2pE
PART 2 FILES: (Potentially will be providing a rom.zip soon that will have latest updated U1 with multi CSC pre-rooted with other goodies)
system.img.ext4
https://www.androidfilehost.com/?fid=817550096634794132
Add CSC Systemroot
https://www.androidfilehost.com/?fid=745425885120757028
For more info on these files please see @jrkruse post located here:
https://forum.xda-developers.com/showpost.php?p=73489978&postcount=925
THANK HIM WHILE YOU'RE AT IT!
@elliwigy @Harry44 @akiraO1 @BotsOne
These months these four people are very hard, and I very relaxed!! lol
Cool Job!
GSM CHEN said:
@[email protected]@[email protected]
These months these four people are very hard, and I very relaxed!! lol
Click to expand...
Click to collapse
haha but we know it wouldnt be possible without you man
Dam it, if I wasnt drunk, and tired, I eould vet myself out of bed and do this now, lol. Thanks for all your hard work.
One thing i would suggest would be to either put the commands that need to be typed in as bold face type or im not sure if its possible on here, as im on my phone atm, but there are Code/code tags avaiable that will make them easier to copy and paste.
Again, thanks for this......I did not think it was going to be possible. This will be my morning present when i wake up, feels like Xmas.......
theboz1419 said:
Dam it, if I wasnt drunk, and tired, I eould vet myself out of bed and do this now, lol. Thanks for all your hard work.
One thing i would suggest would be to either put the commands that need to be typed in as bold face type or im not sure if its possible on here, as im on my phone atm, but there are Code/code tags avaiable that will make them easier to copy and paste.
Again, thanks for this......I did not think it was going to be possible. This will be my morning present when i wake up, feels like Xmas.......
Click to expand...
Click to collapse
to be honest its late haha, threw it together lol ill try to tidy it up when i get time lol
Awesome can't wait to try this out soon!
elliwigy said:
to be honest its late haha, threw it together lol ill try to tidy it up when i get time lol
Click to expand...
Click to collapse
You are forgiven, lol. I figured it would be out in the morning, just not this early in the morning.
You guys should have gotten some sleep you may need it after this weekend.
What a nice thing to wake up to when I'm getting ready to head to work at 530 in the morning lol. Can't wait to give this a shot once I get off work 12 hours later. Thanks for everything devs.
S8 thread will be posted tomorrow, too late to do it tonight
You guys are the ****. Thanks for all of your hard work.
Just want to know if Knox will be triggered or not? Please also add this to the first post [emoji397]
Where's the best place to get the stock firmware we might need just in case? As far as best download speed etc.
Wow,. I honestly didn't think it was possible. Amazing accomplishment ellwigy.
Sent from my SM-G955W using XDA-Developers Legacy app
powerstroke said:
Where's the best place to get the stock firmware we might need just in case? As far as best download speed etc.
Click to expand...
Click to collapse
I got mine here... Took awhile to download... Someone gave me the link in the 955U1 thread
http://updato.com/firmware-archive-select-model?record=F6B451FD73EE11E7963AFA163EE8F90B
Also do we need to back up our EFS/Imei stuff? I know its recommended when flashing roms in recovery but our bootloader is locked.... Is there a way to back up without root?
Edit* I asked about the backup before in a previous thread but didn't get an answer.... Sorry to ask again
Techvir said:
Just want to know if Knox will be triggered or not? Please also add this to the first post [emoji397]
Click to expand...
Click to collapse
Knox is not triggered
Kjc99 said:
I got mine here... Took awhile to download... Someone gave me the link in the 955U1 thread
http://updato.com/firmware-archive-select-model?record=F6B451FD73EE11E7963AFA163EE8F90B
Click to expand...
Click to collapse
And this will work with Sprint S8+ Correct? Lastly, since the latest update which included Sprint LTE Plus calling. We will still manage to have that feature after root right? Because boy do I enjoy being able to browse the internet and being on a call at the same time again lol
powerstroke said:
And this will work with Sprint S8+ Correct? Lastly, since the latest update which included Sprint LTE Plus calling. We will still manage to have that feature after root right? Because boy do I enjoy being able to browse the internet and being on a call at the same time again lol
Click to expand...
Click to collapse
If you have the system.img for the latest update then correct, if not and you want those features with root you will have to download the AP and CSC from thw firmware you want
powerstroke said:
And this will work with Sprint S8+ Correct? Lastly, since the latest update which included Sprint LTE Plus calling. We will still manage to have that feature after root right? Because boy do I enjoy being able to browse the internet and being on a call at the same time again lol
Click to expand...
Click to collapse
I have the U1 model so I'm not sure...
Edit* Deleted