Related
MY ORIGINAL QUESTION:
Does Flashing Straight to RotoHammers ROM on AT&T Tab Add Phone Capabilities?
I''m confused between this posting
http://forum.xda-developers.com/showthread.php?t=895827
and this one
http://forum.xda-developers.com/showthread.php?t=847273
Whats the most current way to get phone capabilities on the AT&T Tab?
Also what is a bootstrapper?
'===========================================================
UPDATE:
For any newbies out there here is the procedure
1. Download Android Sideload Wonder Machine, enable debugging mode, & Sideload z4Root on your AT&T out of the box device. (no ADB knowledge required)
2. Run z4Root Permanent Root
3. Download Root Explorer & Zip System/efs folder , mount your device to USB and keep the zip file on your PC in a safe place
4. Follow the quick tutorial on how to flash the ROTOHAMMER.
http://forum.xda-developers.com/showthread.php?t=895827 ( Just Flash RotoHammer's JME v4 Full .tar via the PDA instead of the file name shown in the screenshot)
http://forum.xda-developers.com/showthread.php?t=894763
6. Once you've reboot your at&t device should now have the Rotohammer Firmware.
7. Enable debugging on the device again.
8. Run RotoHammers script to unlock
http://forum.xda-developers.com/showthread.php?t=843323
You are in Business. If you have any questions shoot me a PM I'll be glad to help.
The only side effect I have right now is that for some reason when I boot my device I do not see the Samsung Boot Screen or Recovery Mode
9. To fix this side effect flash with odin (PDA and NO Repartition) the JJ4 Bootloaders posted by Rotohammer here: http://forum.xda-developers.com/attachment.php?attachmentid=496999&d=1295722186
Flash Roto-JME version 4 following the steps. You will have a phone icon. The best At&t modem is the bell i900. Besides Roto's pit, pda, and phone files, you will need Odin3 1.7.
I also unlocked it using Roto's instructions, so I can use a t-mobile sim card for EDGE data and voice.
I rooted it with z4root.
It was very easy.
Just read everything a few times, and come back here if you're not sure. Good luck.
Yes. I had a basically stock att tab, I followed the first url you put in your post, it just worked.
After the flash, voice service was working as was 3g/3.5g data.
If you review several of the related posts and watch the video, and review the first url, you'll see they are all doing a very similar thing. I started 'simple' by doing the super one click root thing followed by a rotoBAK just to learn abit and develope some confidence. After a day or two, I flashed away.
http://en.wikipedia.org/wiki/Booting#History
Love that reference, but here's the good part:
Wikipedia said:
The computer word boot is short for "bootstrap" (itself short for "bootstrap load"). The term bootstrap derives from the idiom pull oneself up by one's bootstraps. The term refers to the fact that a computer cannot run without first loading software but must be running before any software can be loaded, which seems as impossible as to "pull yourself up by your own bootstraps."
Click to expand...
Click to collapse
i am still not following when it comes to taking a tab and using a tmobile sim card on an att network. edge is att, right? How would you get a SIM card from tmobile?
I am looking to buy a tmobile tab and am trying to figure out the best way of getting phone service. I NEED it to work as a phone, so working out the logistics is paramount. I am still learning, so any info would help.
Can someone repeat the step by step for both unlocking the device & adding ATT voice calling capabilities, with the latest and most current files.
thanks
Jeepsdaddy said:
Can someone repeat the step by step for both unlocking the device & adding ATT voice calling capabilities, with the latest and most current files.
thanks
Click to expand...
Click to collapse
Not necessary! Just take your time to read and learn. Doing these things without doing your own studying is dangerous!
rangercaptain said:
Not necessary! Just take your time to read and learn. Doing these things without doing your own studying is dangerous!
Click to expand...
Click to collapse
I am all set. Unlock + Rooted + Roto Hammer...
For any newbies out there here is the procedure
1. Download Android Sideload Wonder Machine, enable debugging mode, & Sideload z4Root on your AT&T out of the box device.
2. Run z4Root Permanent Root
3. Download Root Explorer & Zip System/efs folder , mount your devide to USB and keep the zip file on your PC in a safe place
4. Follow the quick tutorial on how to flash the ROTOHAMMER.
http://forum.xda-developers.com/showthread.php?t=895827
5. The screen will turn black. Dont Worry. Go back into download mode uncheck Re-Partition & Flash RotoHammer's JME v4 Full .tar via the PDA
http://forum.xda-developers.com/showthread.php?t=894763
6. Once you've reboot your at&t device should now have the Rotohammer Firmware.
7. Enable debugging on the device again.
8. Run RotoHammers script to unlock
http://forum.xda-developers.com/showthread.php?t=843323
You are in Business. If you have any questions shoot me a PM I'll be glad to help.
The only side effect I have right now is that for some reason when I boot my device I do not see the Samsung Boot Screen.
Glad to see the flash worked for you! Your directions seem good. You did do a lot of steps that could be streamlined. I did the partition and firmware application in one step in odin. And using the v4 rotojme; it was rooted upon reboot. I did root the stock firmware, to get a backup. But I don't think this a prerequsite to the jme flash.
I too am missing the samsung startup screen.
But good to see it worked for you.
Question: does the protected bootloaders issue affect this process? I'd like to flash my tab (stock Rogers) to enable the phone capabilities.
You can avoid the whole sideload wonder machine by just using this command in adb: adb install z4root.apk
Also, you should be able to do the entire flashing process in one go - not two.
Your probably right about only need to flash straight to V4.
As per this post:
http://forum.xda-developers.com/showthread.php?t=894763
NO -- JMEv4 has no boot loader.
fwelland said:
I too am missing the samsung startup screen.
Click to expand...
Click to collapse
On another Roto thread this was discussed. Usually you have a black screen and a very thin white line. You wait a few minutes and everything is normal. The cause was given as going from stock to Roto Firmware, with the full wipe and re-partition.
fwelland said:
As per this post:
http://forum.xda-developers.com/showthread.php?t=894763
NO -- JMEv4 has no boot loader.
Click to expand...
Click to collapse
Uh what are you talking about? I went from stock to JMEv4 just fine.
Can I flash it using heimdall ?
fcarmona said:
Can I flash it using heimdall ?
Click to expand...
Click to collapse
I try this:
[email protected]:~/Roto$ heimdall flash --repartition --pit P1_add_hidden.pit --factoryfs factoryfs.rfs --cache cache.rfs --dbdata dbdata.rfs --param param.lfs --kernel zImage --modem modem.bin
and respond this:
If you wish to repartition then factoryfs, cache, dbdata, primary and secondary
bootloaders, param, kernel and a PIT file must all be specified.
which files do I need use in primary, secondary and bootloaders
Fixed boot screen & missing recovery mode issue. See opening post. These files are from the trusted Rotohammer.
Thanks
Thanks for the detailed procedure to flash...
and thanks Roto for the packaging!
I successfuly flashed my Bell Galaxy Tab from stock with the V4 Full!
No problem regarding the boot screen for me!
Great job guys!
I have been at this for a week now. I've tried Heimdall 1.1.1, 1.3.2, AND Odin3 v1.83, v1.85, to reflash the stock Verizon firmware on my Galaxy Tab SCH-i800. I was an idiot and flashed U.S. Cellular firmware, which changed the boot animation and the cell service text. I've scoured the internet on how to do this and everything I've tried has failed. With Heimdall, whenever I plug in the stock files to the program (in 1.1.1 only, I can't figure out 1.3.2 for the life of me) and hit Start, I get "Failed to access device. Error: -12" I'm getting my files from SCH-I800_VZW_stock.zip, it's been extracted. When trying to flash a .tar file with Odin, it works successfully, then my phone goes into bootloop. I can get back to Download mode, but every time I try flashing a stock .tar, I get the same results. I'm starting to go crazy. Anyone help?
maybe you have missed with your partions? if so, i think you need a specific pit file for this stock rom, i dont know where it is, but you might start looking for it.
edit : look in this thread, you might find it useful http://forum.xda-developers.com/archive/index.php/t-940046.html
and this is also important http://theunlockr.com/2012/06/28/ho...axy-tab-sch-i800-back-to-stock-and-unroot-it/
last one http://gizmoninja.com/2011/04/how-to-root-latest-samsung-galaxytab-verizon-update-ec02/
best regards ^_^
Sifou
chrispysaid said:
....With Heimdall, whenever I plug in the stock files to the program (in 1.1.1 only, I can't figure out 1.3.2 for the life of me) and hit Start, I get "Failed to access device. Error: -12"
Anyone help?
Click to expand...
Click to collapse
Did you properly install the Samsung drivers on your PC using the heimdall utility? And you put your Tab in download mode?
The Problem may lie with youe Heimdall setup.
Make sure you have Keis installed. Then make sure you activate the drivers for Heimdall.
This is a great rom to flash to your VZW Tab. follow this thread http://forum.xda-developers.com/showthread.php?t=1325469
It looks like I got myself in a pickle. I have a GS4 running 4.2.2. I picked up my phone today and successfully rooted it with instructions from DroidView using files from chainfire. I then installed CWM recovery with ROM Manager and backed up my ROM with it. I decided to replace chainfires SU with the one fom CWM like I had on my S3. After rebooting from recovery mode I noticed I had lost root so I used the same method to root it again because I thought it had reset itself. Before the reboot occurred there was option to prevent the possibility of the ROM flashing itself to stock. I went to select the Yes option but bumped the power button which selected No. While trying to reroot and failing, the phone displayed the message "Invalid percent of drawing download progress bar." On reboot the error “Firmware upgrade encountered an issue“ along with a cone and a couple of other pics. I have tried to get into recovery mode several times but repeatedly get this error. I can get into download mode and have tried to flash the stock ROM for this phone but it fails in Odin 3.0.7. Odin sees my phone and verifies the md5 but fails very quickly upon clicking start. I tried this with KiesPDLR running in the background and disabled. I have not tried anything else out of concern for messing it up further. Attached are screenshots and log from ODIN along with the text that is being displayed in download mode. (I will have to post these later as the attachments option will not work properly on my wife's S3).
Two other notes. 1) I used ODIN 1.85 to root as that was what was included in the chainfire download. But I used ODIN 3.0.7 to try and unroot because that's what the DroidView directions said. Would it make any difference to use ODIN 1.85 to try and flash the stock firmware? It sees my phone as well but the F. Reset Time option is unchecked and grayed out and the directions says it needs to be checked. Don't know if that really makes a difference. 2) My phone is actually with US cellular but there is not a forum for this carrier. I chose this forum because my previous phone the Mesmerize had an identical model number as the Fascinate. Please do not pass over my request for help because of this as I am in dire need.
apel69 said:
It looks like I got myself in a pickle. I have a GS4 running 4.2.2. I picked up my phone today and successfully rooted it with instructions from DroidView using files from chainfire. I then installed CWM recovery with ROM Manager and backed up my ROM with it. I decided to replace chainfires SU with the one fom CWM like I had on my S3. After rebooting from recovery mode I noticed I had lost root so I used the same method to root it again because I thought it had reset itself. Before the reboot occurred there was option to prevent the possibility of the ROM flashing itself to stock. I went to select the Yes option but bumped the power button which selected No. While trying to reroot and failing, the phone displayed the message "Invalid percent of drawing download progress bar." On reboot the error “Firmware upgrade encountered an issue“ along with a cone and a couple of other pics. I have tried to get into recovery mode several times but repeatedly get this error. I can get into download mode and have tried to flash the stock ROM for this phone but it fails in Odin 3.0.7. Odin sees my phone and verifies the md5 but fails very quickly upon clicking start. I tried this with KiesPDLR running in the background and disabled. I have not tried anything else out of concern for messing it up further. Attached are screenshots and log from ODIN along with the text that is being displayed in download mode. (I will have to post these later as the attachments option will not work properly on my wife's S3).
Two other notes. 1) I used ODIN 1.85 to root as that was what was included in the chainfire download. But I used ODIN 3.0.7 to try and unroot because that's what the DroidView directions said. Would it make any difference to use ODIN 1.85 to try and flash the stock firmware? It sees my phone as well but the F. Reset Time option is unchecked and grayed out and the directions says it needs to be checked. Don't know if that really makes a difference. 2) My phone is actually with US cellular but there is not a forum for this carrier. I chose this forum because my previous phone the Mesmerize had an identical model number as the Fascinate. Please do not pass over my request for help because of this as I am in dire need.
Click to expand...
Click to collapse
Try odin 1.85 I use that to odin back to stock and dont worry about the other ones just make sure auto reboot is checked.
Also are you sure the phone you have is the sprint gs4 sph l720 jfltespr?? Cause odin a tar file not for the phone could potentially brick the phone.
Sent from my SPH-L720 using xda app-developers app
I would try to download the stock rom from a different source if you can. These tar files are so large for this phone that the possibility of a bad download is pretty high. Also, make sure you don't have to extract the actual .tar file first from the archive you download. Lots of these stock roms are repackaged into a zip file and you need to extract the tar file for use in Odin before installing.
I am back in business. I have my phone and home internet back now. Yeah. I used the same stock ROM I had since it was the same as sammobile which was also a zip file and I already had it on my system. I just used Odin 1.85 instead. I guess I could have done this earlier and prevented a near stoke but everything else I had done seemed to get me deeper in a hole. These large zip files have always made me a bit nervous but I haven't found where to get one otherwise.
I have some follow up questions.
1) Why would it flash with Odin 1.85 and not with 3.0.7?
2) Is CWM's SU not compatible with the S4? Everything was working fine until I switched this from chainfire to CWM using ROM Manager.
3) Is there a good source with unzipped ROM's?
Chainfires SuperSU is much better with JellyBean than cwm SU. For some reason most people that try to switch to SU from SuperSU have the same problem you had.
Sent from my icrap 2 using Tapatalk HD
Okay. I decided to go with chainfires after this fun little ordeal. The few small things I preferred from CWM is not worth it. Besides it looks like chainfire made some upgrades since I last looked at it. I guess I was lucky with my S3 because I converted several times.
Thanks for all the help everyone.
Searched but and found similar posts but with different phones or different firmware, so the file references were of no help.
Basically I had safestrap working, had flashed google play edition ROM and it was working great with the exception of the play store not wanting to connect. I was in the process of messing with that and read (here) that I needed 4.3 edition of that app, I checked and I had 4.2, so I loaded 4.3 to the Sdcard and installed it..
Phone rebooted and just stays on the samsung custom splash screen indefinitely . I can get to ODIN on the phone, soI tried using https://builds.casual-dev.com/jodin3/ to get access and see what I could do, but it keeps telling me to unplug and plug in the phone, and gives an error that it cant mount the device.
So, im kinda stuck, I didn't use ODIN to do anything previously, But considering its the only thing I currently have access to, I guess its my only hope.
Been fighting this a few hours and getting pretty dejected, I had almost everything PERFECT.. and now back to WORSE than where I started.
Wingnutt said:
Searched but and found similar posts but with different phones or different firmware, so the file references were of no help.
Basically I had safestrap working, had flashed google play edition ROM and it was working great with the exception of the play store not wanting to connect. I was in the process of messing with that and read (here) that I needed 4.3 edition of that app, I checked and I had 4.2, so I loaded 4.3 to the Sdcard and installed it..
Phone rebooted and just stays on the samsung custom splash screen indefinitely . I can get to ODIN on the phone, soI tried using https://builds.casual-dev.com/jodin3/ to get access and see what I could do, but it keeps telling me to unplug and plug in the phone, and gives an error that it cant mount the device.
So, im kinda stuck, I didn't use ODIN to do anything previously, But considering its the only thing I currently have access to, I guess its my only hope.
Been fighting this a few hours and getting pretty dejected, I had almost everything PERFECT.. and now back to WORSE than where I started.
Click to expand...
Click to collapse
The 4.3 edition of SS doesn't work on 4.2. Does it stay on the splash or does it go to the actual boot animation? Also, you don't need to boot into the phone to use odin, it's a PC program. You can google "mf3 tar files" and you'll find the thread with the ODIN files, use them to get back to stock.
DeadlySin9 said:
The 4.3 edition of SS doesn't work on 4.2. Does it stay on the splash or does it go to the actual boot animation? Also, you don't need to boot into the phone to use odin, it's a PC program. You can google "mf3 tar files" and you'll find the thread with the ODIN files, use them to get back to stock.
Click to expand...
Click to collapse
It sits on the Samsung custom screen, that's it.
And how do I use the ODIN files.. When the ODIN program won't do anything except tell me over and over to in plug and plug in the phone?
How do I "use the Odin files" ??
Wingnutt said:
It sits on the Samsung custom screen, that's it.
And how do I use the ODIN files.. When the ODIN program won't do anything except tell me over and over to in plug and plug in the phone?
How do I "use the Odin files" ??
Click to expand...
Click to collapse
Did you install the Samsung USB Drivers? Google that and install them, then plug in the phone and run the program.
DeadlySin9 said:
Did you install the Samsung USB Drivers? Google that and install them, then plug in the phone and run the program.
Click to expand...
Click to collapse
I *think* I already have installed them but I'll double check just in case, I have android file transfer installed, it does the same, I'll try it under windows in instead of Mac as well.
Ok, ODIN sees the phone, under windows, Downloading a MF3 TAR file as seen here http://forum.xda-developers.com/showthread.php?t=2504311
(1.5gb?!) once thats done Ill see what we have![/QUOTE]
Well, im a little stuck
I downloaded a the MF3 TAR file from here:http://forum.xda-developers.com/show....php?t=2504311
Flashed the bootloader: BOOTLOADER_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.mp5
That went through properly, the phone rebooted..
No change..
what am i supposed to do next?
I flashed the CSC file: CSC_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5
That went through as well, after reboot no change.
Tried flashing the phone file: PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5
but nothing happens, no error message... it just doesent do anything :silly:
a little help?
Wingnutt said:
Well, im a little stuck
I downloaded a the MF3 TAR file from here:http://forum.xda-developers.com/show....php?t=2504311
Flashed the bootloader: BOOTLOADER_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.mp5
That went through properly, the phone rebooted..
No change..
what am i supposed to do next?
I flashed the CSC file: CSC_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5
That went through as well, after reboot no change.
Tried flashing the phone file: PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5
but nothing happens, no error message... it just doesent do anything :silly:
a little help?
Click to expand...
Click to collapse
You put platform tar in the PDA slot right? Also, you might have to restart between flashes or just load them in all at once.
There's a picture on this post with what options you should have: http://forum.xda-developers.com/showpost.php?p=46955352&postcount=7
DeadlySin9 said:
You put platform tar in the PDA slot right? Also, you might have to restart between flashes or just load them in all at once.
There's a picture on this post with what options you should have: http://forum.xda-developers.com/showpost.php?p=46955352&postcount=7
Click to expand...
Click to collapse
Yep, ive read that thread stem to stern, everything is in the correct slots, I can flash everything EXCEPT the platform file
have tried it by itself, and as added with the rest, either way it same result.
Wingnutt said:
Yep, ive read that thread stem to stern, everything is in the correct slots, I can flash everything EXCEPT the platform file
have tried it by itself, and as added with the rest, either way it same result.
Click to expand...
Click to collapse
Make sure the file you download was full and that it extracted the whole platform file. Other than that i'm not sure why it wouldn't work..
DeadlySin9 said:
Make sure the file you download was full and that it extracted the whole platform file. Other than that i'm not sure why it wouldn't work..
Click to expand...
Click to collapse
Ive downloaded it twice, Ive tried flashing it under windows 7 and OSX. Same result.
I would be happy to try a different platform file, but I cant find any others.
One oddity, the ONLY Odin program that can see the phone is Jodin3, the web based version.
Ive downloaded 1.85 and 3.07 (windows) have updated the samsung USB drivers, have updated the heimdall software... they cant see it.
Wingnutt said:
Ive downloaded it twice, Ive tried flashing it under windows 7 and OSX. Same result.
I would be happy to try a different platform file, but I cant find any others.
One oddity, the ONLY Odin program that can see the phone is Jodin3, the web based version.
Ive downloaded 1.85 and 3.07 (windows) have updated the samsung USB drivers, have updated the heimdall software... they cant see it.
Click to expand...
Click to collapse
Seems like it's not installing the drivers right. I'd try installing again: http://forum.xda-developers.com/showthread.php?t=2038555 or just manually go into device manager and point it to where you installed the drivers. Also, you might have to wait a while on any version of ODIN (even the we version) for it to finish checking the file.
OHHHH ****!
You were right, it was the USB drivers, I had to do it via method 3, I.E. manually select them.. for some odd reason the installer DID install the drivers but the device showed up as someting totally different than when doing it manually.
flashing now... will see what happens:laugh:
ITS ALLLLIIIVVVEEEE!!!!!!!
Ok. so, now I cant start over lol!
Thanks for all your help, everyone!!
Should have enough posts to include links now.
These are the stock files I purchased from a persian site for 12$ since nobody had them posted on the forums. Flashed with the latest unmodded Odin. I also had the benefit of suddenly getting data toggle with it after flashing the AP file. Not sure if everyone else will get it too.
https://drive.google.com/open?id=0B0vffDY5Mf5sY1JpY3ViWlV1OVU
I can also confirm that root works with this.
And thanks for the hookup.. lol
i got it recently and going to flash this firmware and will try root.. will reply
Obies said:
i got it recently and going to flash this firmware and will try root.. will reply
Click to expand...
Click to collapse
It works. However, you REALLY need to run the V15 fix script.. The older builds ran like crap, even with the fix script, however with APK1, my phone runs normal and doesn't overheat. However, if you don't run that script with APK1, your phone will run sluggish and hot.
yeah i do aware abt bad lagging after rooted.. anyways my phone is on rooted with Fixes V15 and xposed install with XtouchWiz module so i can use tethering for my laptop/tablet while i am away from home. but no Toggle Data for me.. maybe bad luck but i did odin 4 files and factory reset..
Thanks for this files!
Is this the Stock AT&T PK1 that I have on my phone with the last OTA dated Nov. 1
I downloaded all these files, deleted .rar off the end so Odin would recognize the files (did i do that right?), plugged all 4 files in to the right spots and tried to flash them. I’ve used Odin plenty of times and haven’t had any problems before but I am far from an Odin master. This time I just get stuck at file analysis after i click the start button. Any idea what i could be doing wrong?
jermo said:
I downloaded all these files, deleted .rar off the end so Odin would recognize the files (did i do that right?), plugged all 4 files in to the right spots and tried to flash them. I’ve used Odin plenty of times and haven’t had any problems before but I am far from an Odin master. This time I just get stuck at file analysis after i click the start button. Any idea what i could be doing wrong?
Click to expand...
Click to collapse
You need to decompress the RAR files first using something like 7-Zip (it will extract files with a tar.md5 extension). Those are the files you use in Odin.