Database Users

[HOW-TO] Flashing RotoHammers ROM on Out of the Box AT&T Galaxy TAB

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!

[Q] I have a semi-bricked Vibrant and CANNOT FIX!!! HELP!!

I have been on this forum for 3 days going through many fixes for this problem.
NONE of them have worked.
I have been able to get into download mode, and the phone is recognized via com3 in odin.
I have re-flashed it with Eugenes no-brick version, then re-flashed it with tons of different stock and non-stock roms. It gets to various stages but does NOT work.
Any ideas or fixes will be a lifesaver!! Thanks in advance!

If you can still get into download mode and Odin recognizes your phone, flash it with these two files, they work:
http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/
DO NOT check the re-partition checkbox in odin.

why not repartition as long as you put pit file in pit field repartitoin like crazy if you like .
and repartition would be required if you coming from vodoo based kernel or if you ran anyother partiton than rfs .

Thanks for the quick response.
I tried these files again (I have tried them before) both with and without checking the re-partition box.
It boots then says Vibrant Samsung, then crashes. When I turn it back on it again crashes and turns itself off after the initial splash screen.
Any other ideas? It says that I passed in Odin

charge your phone ?

bartek25 said:
charge your phone ?
Click to expand...
Click to collapse
Hahaha ya I wish it was something so simple (maybe it is!) but it isn't that!

download this ! http://forum.xda-developers.com/showthread.php?t=734475
put JFD in to PDA
also downlaod PIT from the same lik i gave you and seriously charge your phone , and when you odin with the files i gave you from the link check rapartition . check phone efs clear and f.reset time and auto reboot .

come back report resoults if not we help more .

also by any chance u didnt play with ROM MANAGER when your wibrant was working and didnt play with repartiton while there right ?

The same crashing loop has happened with the latest advice. I checked Phone efs clear, re-partition, auto-reboot, and f.reset.time.
I used tVhe T959UJFD PDA, and the 512 Pit.
This phone has been plugged in for days I really doubt the battery is dead.
It just is a constant loop of crashing,h whether at te "off battery" logo or the vibrant splash screen.
The ONLY flash that has given me any different results is the "eugene no brick froyo" which takes me to the Android Recovery screen but does not allow me actually select any of the options.
I am starting to think there may be a hardware issue.

To be completely honest, I got this phone from a friend who had bricked it. If I can get it working then I have a galaxy on the cheap.
On the downside I have no idea what he did to brick it, and he is not tech-savvy enough to know himself.
I come from an original G1 and Cliq, so this is a tad different then I am used to.

from my point of view your phone is fried (it happends) or you are not doing something right or someone is more tech savy to help more , did you pull battery out for at least a min and let it sit and try again to boot ...

Ohhh i know whats wrong with the phone ........if your friends gave it to you broken i think good advice is ,download a program that can repartition hard drive from windows like any program that can do format of anydrive from windows i recomend PARAGON PARTITION MANAGER , find your phone while in the program and u need some skills lol for it but find the phone and click delete partiton after you do that click apply 2. after deletion and applaying the actions click on the phones formated drive in the program i recomended you and click submenu wher you will see create partiton click FAT32 apply 3. click again on the disk you created and click format . 4 done , its easy just get to hang of it

Good advice, I will work on this and get back to you later tonight.
Thanks again!

sounds like your friend bricked his phone from ROM MANAGER by creating EXT4 partion in phones memmory not on SD thats why phone cant find a drive to install the system , happend to me by my own mistake but i got it to work so if that help you You have free vibrant so try hard if not u have paper weight toy

if u dont want the phone i buy back from you for 20 bucks so i cant smash it against the wall , always want it to do that

Intim said:
The ONLY flash that has given me any different results is the "eugene no brick froyo" which takes me to the Android Recovery screen but does not allow me actually select any of the options.
Click to expand...
Click to collapse
Just so you know when you get to this point you need to make sure you had ADB set up on your pc and then plug in the phone and do adb reboot and that will boot the phone up, then you can shut it down and go into DL and flash back to stock. if you read the directions from Eugene's no brick it stated you need to do a adb reboot to get it to work, so you can fix it if your getting to the recovery of that flash.

Ok so for the paragon partition manager it does not recognize my phone's harddrive. Unsure how to fix that as it is just a wizard type program.
I have been able to recognize the phone in ADB, although I cannot push any files to the phone (access denied) and have not been able to get SU access either as I am assuming he did not have root when he bricked it.
Any ideas?

you dont need to push any files to the phone with the adb, after you flash the eugene rom and it boots into recovery you just need to load up your adb and type this
adb reboot
thats it, and it should reboot your phone and if it does boot up fine then you can flash back to stock with odin from there.

Did you perchance happen to have installed the Team Whiskey DOW kernel on this phone?
Your symptoms match the symptoms of quite a few others.
http://forum.xda-developers.com/showthread.php?p=11704550&posted=1#post11704550
http://forum.xda-developers.com/showthread.php?p=11680374#post11680374

[GUIDE] Upgrading and modding NTT DoCoMo SC-01C (Japanese P1000)

Kind of a niche guide, but at least non-Japanese people owning an SC-01C have some sort of guidelines.
Before we begin
The SC-01C is the rebranded Japanese version of the P1000, locked exclusively to NTT DoCoMo. If you have this model and want to upgrade and/or flash custom ROMs with it, this guide may be able to help you.
Before beginning, you have to check your firmware version. What you'll have to download will depend on it. If you have Android 2.2 Froyo, read on, otherwise, if you're already running Android 2.3 Gingerbread skip to the Gingerbread Users section.
Also, based on experience, if you want to upgrade to other ROMs in the future you will have to keep your stock GB ROM file, your gt-p1000_mr.pit, the dbdata.tar and the entire Overcome kit (kernel and ROM). You will need all of them in the future because I've found that to install a new ROM you have to repeat the entire process of restocking to GB, then installing Overcome Kernel and ROM, then installing whatever ROM you want. It sucks, but it's the only way I've seen so far.
Froyo Users
If you're planning to install a custom ROM, you can't do it on Froyo straight away, at least not on a stock ROM with a protected bootloader. If you don't know if your bootloader is protected or not, the safest thing to do is to first upgrade your firmware to the stock Japanese Android 2.3 Gingerbread. Then you can follow the Gingerbread guide afterwards.
Froyo Users Will Need
Stock Japanese GB ROM (you can get it from here or from SamFirmware.com). The ROM is a .tar archive file, so you will also need 7-Zip or another file extracting utility to extract files from the tar file.
Odin 1.7 (higher versions will likely not hurt either)
Heimdall (in case Odin doesn't work or you aren't running Windows)
Upgrading to Gingerbread
Make sure your PC has the drivers for your Tab. If you've already connected your PC to the Tab before, you already have them. Otherwise, plug your Tab into your PC and let the drivers install automatically. This works even if you're in Download Mode. If they don't install automatically, you might need to download Samsung Kies or just the Samsung USB Driver for Mobile Phones to get the driver to install.
[FOR HEIMDALL USERS]
You will need to plug in your Tab and run zadig.exe for your drivers, which is found either in the same folder as your Heimdall.exe or in the Drivers folder in that same folder, depending on which version you have. From there, select Options -> List All Devices, then select Gadget Serial or Android USB Composite Interface, then click Install Driver.
After getting the drivers, unplug your Tab (you can keep the PC end plugged in). Turn off your Tab and plug your USB Interface cord into your PC (not the Tab just yet), then put your Tab into Download Mode. You can do this by either holding down the Power and Volume Down keys while the Tab is off, or simply holding down the Volume Down key while plugging in the cord to your Tab. If done correctly, you should see a screen with a yellow Android with a shovel, together with the words "DOWNLOAD MODE, DO NOT TURN OFF TARGET!"
If you're running Windows and using Odin, extract the gt-p1000_mr.pit from the .tar archive into the same folder as the archive. Otherwise, if you're running Heimdall, extract the entire archive into the same folder as your Heimdall.exe.
Plug your Tab back in if you haven't already. The next step will vary for Odin and Heimdall users.
[FOR ODIN USERS]
Open Odin and check if there is a yellow box amongst all the white ones which says [COM4] or something like that, it doesn't matter as long as the box is yellow.
Click PIT and select the gt-p1000_mr.pit you extracted from the stock Japanese GB .tar file, then click Start. This will re-partition the device, and it is absolutely critical that this is done first, as missing this step can cause a brick.
After the PIT flashing is successful, click Reset, then click PDA and select the stock Japanese GB .tar file, and click Start. You will have to wait for a few minutes while the ROM flashes. Progress bars will appear both on the Tab screen and Odin.
NOTE: If after flashing you boot into Recovery Mode and you get the following error:
Code:
E: part(1) DATA Checksum Error
E: part(1) Checksum Error
Internal MMC checksum verify failed.
Then you will have to download and flash dbdata.tar as PDA (Google "P1000 dbdata.tar"; it's about 1.25MB or so). That should solve it.
[FOR HEIMDALL USERS]
Since you already extracted the contents of the stock Japanese GB .tar file into the same folder as your Heimdall.exe, all you have to do is run the following command from a Terminal window (or Command Prompt if you're running Windows):
Code:
heimdall flash --repartition --primary-boot boot.bin --cache cache.rfs --dbdata dbdata.rfs --factoryfs factoryfs.rfs --pit gt-p1000_mr.pit --modem modem.bin --param param.lfs --secondary-boot Sbl.bin --kernel zImage --verbose
Wait a few minutes while Heimdall flashes the ROM. It should inform you when the flashing is successful.
After the flashing is successful, you should now be running stock Android 2.3 Gingerbread. You can stop here or continue on to the Gingerbread Users section for flashing a custom ROM.
Gingerbread Users
Since you're already on Gingerbread, which is the latest stock Android version you have, you're probably reading this guide to find out how to install custom ROMs. Personally I've found, after bricking my Tab a couple of times, that trying to flash custom ROMs from the stock Japanese GB ROM doesn't work unless you flash the Overcome kernel and ROM first.
Hence, the first step to getting a custom ROM running on an SC-01C is to flash the Overcome kernel. For instructions on how to do this, go to the guide thread at the end of the paragraph. You can skip the restocking part, as you're already running stock GB. Instead, follow the instructions from Step 7 of the guide, found on Page 10. After following the instructions there and flashing the Overcome kernel and ROM, you should now be able to flash any other custom ROM you want, following the instructions for the regular P1000.
Getting the Overcome kernel and ROM: http://forum.xda-developers.com/showthread.php?t=1881981
Questions, Answers and Possible Issues
My SC-01C is stuck at boot logo after trying (and failing) to flash custom ROM.
Solving this issue depends on your firmware version and whether or not you can still get into Download Mode. If you can, just follow the instructions in this guide exactly and the problem should be solved.
My SC-01C is stuck at phone-exclamation mark!-computer screen.
This is also likely because of a failed ROM flashing or firmware upgrade. In that case, you can use Heimdall OneClickUnbrick to fix it. A guide to do so can be found here.
My SC-01C isn't detected by Odin, and/or Heimdall produces a "Claiming interface failed" error.
Your drivers aren't being detected and either need to be installed or reinstalled. To force a driver reinstall on Windows, plug in your Tab, go to the System Tray, right-click Safely Remove Hardware and Eject Media, then select Open Devices and Printers. Find your Tab's device name from there, then right-click it and select Remove Device, then unplug your Tab and plug it in again. The drivers should reinstall automatically. If they still don't reinstall, download Samsung Kies or the Samsung USB Driver for Mobile Phones and try again.
For other possible questions or concerns, please reply to this thread.

After successful repair, No Network/ No service
I followed the first method and recovered a bricked P1000 docomo
But No network/service
Any ideas ?

dannyogolo said:
I followed the first method and recovered a bricked P1000 docomo
But No network/service
Any ideas ?
Click to expand...
Click to collapse
You'll need to modify it further to get it to work with other providers. I'm personally not sure if it's a hardware or a software hack, because I paid someone to unlock my Tab back when I didn't know jack **** about modding. If it was already unlocked prior to being bricked, try to flash a new ROM over it. Either way, please hit back if you find the answer so I can add it to the FAQ section.

Hi! I just got the SC-01C & it was already loaded with a custom ICS firmware. Would it be ok to flash another custom firmware DIRECTLY? or Do I still need to flash the GB first?

only root
how to root without change stock rom?
It is possible ?
Thank you

zmeus said:
how to root without change stock rom?
It is possible ?
Thank you
Click to expand...
Click to collapse
Yes it's possible, just Google "how to root galaxy tab". There's a few methods, so just pick one.
Sent from my GT-P1000 using xda app-developers app

Thank you
This it will help me for sure.
Sent from my GT-I9100 using Tapatalk 4

"Hi im a noob and i hate myself"
finally found a thread that that covers japanese p1000.
I have a one it was given to me and still on android froyo 2.2 it is been unlocked by software and i don't know if its been rooted or not.
for the past days i've been looking over the net for this particular device to be upgrade to the latest jellybean rom.this will be very helpful for me since i dont know anything about flashing. been reading threads over and over bec i dont want to brick this device for i use it as a secondary phone
Will flashing to the original docomo GB 2.3... stock firmware make the tab in an locked state again? and is the new rom like the cyanogenmod 10.1 or 10.2 have a built in unlock?

joevinz said:
"Hi im a noob and i hate myself"
finally found a thread that that covers japanese p1000.
I have a one it was given to me and still on android froyo 2.2 it is been unlocked by software and i don't know if its been rooted or not.
for the past days i've been looking over the net for this particular device to be upgrade to the latest jellybean rom.this will be very helpful for me since i dont know anything about flashing. been reading threads over and over bec i dont want to brick this device for i use it as a secondary phone
Will flashing to the original docomo GB 2.3... stock firmware make the tab in an locked state again? and is the new rom like the cyanogenmod 10.1 or 10.2 have a built in unlock?
Click to expand...
Click to collapse
No, 2,3 has an unlocked bootloader. Just follow the guide carefully step by step and you should be fine.

geno93n0 said:
No, 2,3 has an unlocked bootloader. Just follow the guide carefully step by step and you should be fine.
Click to expand...
Click to collapse
ok that's good to know, i'll prep up first before having a go. just be patient with me pls. bec from time to time i'll be asking you alot if i mess up. . thank in advance. thank button has been used.:good:

joevinz said:
ok that's good to know, i'll prep up first before having a go. just be patient with me pls. bec from time to time i'll be asking you alot if i mess up. . thank in advance. thank button has been used.:good:
Click to expand...
Click to collapse
No problem, ask away. I made a lot of mistakes by experimenting on my own, so I made this guide to make the process easier for people with our model.

Hi i have a problem with SC-01C Gingerbread OMKE2, ive been stuck in boot.bin and it fails to flash the overcome using ODIN, what should i do? pls help

Help I think I am bricked
I have a sc-01c bought in japan...I tried flashing and now all i get is the docomo screen...I think i may have deleted everything on the tab...I can get into dl mode but whether flashing with odin or heimdall i get errors...Is there a way to wipe totally and reinstall from scratch....

WILLIEFRANCE said:
I have a sc-01c bought in japan...I tried flashing and now all i get is the docomo screen...I think i may have deleted everything on the tab...I can get into dl mode but whether flashing with odin or heimdall i get errors...Is there a way to wipe totally and reinstall from scratch....
Click to expand...
Click to collapse
What are you Trying to do? and what errors?

SC-01C
rence.slvdr said:
What are you Trying to do? and what errors?
Click to expand...
Click to collapse
I am trying to install the stock rom using odin. I flash the pit then reboot go back to dl mode and flash the tar(stock) i think i hosed the device...Odin says it passed and it reset...but all i get is docommo screen then after the samsung galaxy screen and it keeps blinking ever few minutes like it cant reboot...I ALSO tried flashing the newer Stock 2.3? and the same issue...
I think I may have mucked up the software but can get into DL mode...any ideas?
I followed the directions but still no joy....Perhaps I am dense...
But basically
Flash pit
reboot
Flash stock
Blinking samsung
Odin says reset and no errors...

WILLIEFRANCE said:
I am trying to install the stock rom using odin. I flash the pit then reboot go back to dl mode and flash the tar(stock) i think i hosed the device...Odin says it passed and it reset...but all i get is docommo screen then after the samsung galaxy screen and it keeps blinking ever few minutes like it cant reboot...I ALSO tried flashing the newer Stock 2.3? and the same issue...
I think I may have mucked up the software but can get into DL mode...any ideas?
I followed the directions but still no joy....Perhaps I am dense...
But basically
Flash pit
reboot
Flash stock
Blinking samsung
Odin says reset and no errors...
Click to expand...
Click to collapse
This happened to me as well, it's why I wrote this guide. Try the Overcome method that I posted in the guide, or search for it in this forum. Also, are you using the stock Japanese GB ROM or just a normal stock ROM? You need to use the stock Japanese Gingerbread ROM. I provided links in the guide.

rence.slvdr said:
Hi i have a problem with SC-01C Gingerbread OMKE2, ive been stuck in boot.bin and it fails to flash the overcome using ODIN, what should i do? pls help
Click to expand...
Click to collapse
Don't flash them all at once. Look at the Overcome guide carefully.

pls help
hi.. im new here and i have a problem with modding my sc01c tab. im already running on official gingerbread SC01COMKE2 firmware and im also rooted. i followed all the steps but always ended up with a soft brick. heres what i did.. i downloaded overcome files from http://forum.xda-developers.com/showthread.php?t=1881981 and followed step by step guide. i flashed Overcome_Kernel_v4.0.0.tar and boot into recovery mode.. then flashed Overcome_7_Series_v4.1.0_Wipe.. but it says cannot open BAD FILE. i redownload even the no wipe version but same happens. i tried to restock using GB-Stock-Safe-v5 but it failed in odin.. whats weird is that when i flashed my tab with official firmware it succeeded without a problem.. can you guys help me here? what did i miss or do wrong? pls dont hate me much im just a noob.

geno93n0 said:
No problem, ask away. I made a lot of mistakes by experimenting on my own, so I made this guide to make the process easier for people with our model.
Click to expand...
Click to collapse
ah finally had the time to modd my docomo tab, heres what happened, fashing the pit file went ok, but flashing the rom went haywire ended up brick. i did everything to the letter but to no success. i manage to unbrick the tab and redo the whole thing but i always end up bricking it. rom fails to flash. any ideas? should i be rooted in froyo before doing this?

ah finally after countless trial and error finally updated my tab to gingerbread, now next step is to root and install clockwork recovery mod. i will not rst until my tab gets the lates jellybean rom hahahah,

[Q] How bricked is my I9505? (reward offered for successful salvage!)

Hello friends.
I installed Xposed (http://forum.xda-developers.com/showthread.php?t=1574401) and now my shiny new S4 won't boot (stuck at Samsung logo).
According to the docs, I need only copy /system/bin/app_process.orig back to /system/bin/app_process but alas I cannot because my stock recovery is not letting me adb shell, reporting the device is offline. Note that adb devices shows the device as connected but offline.
Since there's no working TWRP or CWM (yet!!) I think I'm stuck.
If someone else can unlock me in the mean time. I'll buy you a beer or TWENTY. That's a promise.

Don't know whether it still works, but other SS phones have a save mode boot.
To enter it, you have to power off your phone first. Next, turn it on while holding the menu button and keep menu pressed until you see your homescreen.
hope it works.

Thanks for the reply! Nope. Tried the home button and the menu button. No cigar.

can you enter download mode?

Try and find something like the nexus root tool kit.....maybe there is one like it for Galaxy phones.
Its a great tool for such a thing, it helps you root, un root, lock, unlock, flash and re flash stock, it aslo lets you pick if phone is working as normal or is it soft bricked., and thats what saved my nexus 7 and 10 lol was stuck with bootloops and not able to get into recovery mode.
Anyway have a look see if there is something like that but for Samsung Galaxy.
Have a look at this, used it to flash s3 in the past, unsure what it can do s4 way though. http://forum.xda-developers.com/showthread.php?t=1703488

Thanks for replies.
Yes! I can get into download mode.
There is an S4 toolkit but it's early days and apparently doesn't actually work. I figure with time, a custom recovery will emerge and that will save the day. I'm sure I don't need to explain that I would like this fixed NOW without waiting tho!

bonstio said:
Hello friends.
I installed Xposed (http://forum.xda-developers.com/showthread.php?t=1574401) and now my shiny new S4 won't boot (stuck at Samsung logo).
According to the docs, I need only copy /system/bin/app_process.orig back to /system/bin/app_process but alas I cannot because my stock recovery is not letting me adb shell, reporting the device is offline. Note that adb devices shows the device as connected but offline.
Since there's no working TWRP or CWM (yet!!) I think I'm stuck.
If someone else can unlock me in the mean time. I'll buy you a beer or TWENTY. That's a promise.
Click to expand...
Click to collapse
Download firmware for Odin from Samsung-Updates or use Pre-Rooted OFFICIAL Rom from here
Turn OFF your phone, press&hold POWER+HOME+VOL_DOWN to enter Odin/Download Mode.
Connect your phone to the computer, use Odin3 v3.04 , load firmware as PDA, make sure that ONLY AutoReboot&F.Reset Time is ticked and click START.
After 5 minutes, all done, it should be back to life...
enjoY

Just flash a Official stock firmware and you will boot normally again.
Download a stock firmware
Download odin
Enter download mode in you unit by pressing power and volume down and home button.
Connect the device to your pc, wait for drivers to install.
Select your unzipped firmware (yeah the .md5 file) in the PDA section
Now start flashing and wait...your phone should boot as normal.
That is about it
no donation required btw...

download mode is great news. now get odin + stock firmware and flash your s4 back to life be aware, that all your data is most likely to be lost in the process.
a small price to pay if you ask me.

As others said, if you can get to download mode then be ready to have babies and fall in love with Odin, another life saver.

voodoochild2008 said:
As others said, if you can get to download mode then be ready to have babies and fall in love with Odin, another life saver.
Click to expand...
Click to collapse
Thanks guys. On the download. Server seems slow. Great to know that it's recoverable. I'll update when I'm up and running again.

djembey said:
Download firmware for Odin from Samsung-Updates or use Pre-Rooted OFFICIAL Rom from here
Turn OFF your phone, press&hold POWER+HOME+VOL_DOWN to enter Odin/Download Mode.
Connect your phone to the computer, use Odin3 v3.04 , load firmware as PDA, make sure that ONLY AutoReboot&F.Reset Time is ticked and click START.
After 5 minutes, all done, it should be back to life...
enjoY
Click to expand...
Click to collapse
SORTED. Thanks to everyone for jumping on board! djembey, mail me your PayPal for your reward or alternatively a shipping address and what color your S4 is. Which ever you prefer.
Thanks again.

bonstio said:
SORTED. Thanks to everyone for jumping on board! djembey, mail me your PayPal for your reward or alternatively a shipping address and what color your S4 is. Which ever you prefer.
Thanks again.
Click to expand...
Click to collapse
I'm happy for you! Next time be more careful with your new Baby
I've got white i9505 and love it to the bits (my first white phone...)
Under my avatar you'll see "DONATE TO ME" ..... if you want to....
Did you try my Pre-Rooted Rom?? If not, you should

djembey said:
I'm happy for you! Next time be more careful with your new Baby
I've got white i9505 and love it to the bits (my first white phone...)
Under my avatar you'll see "DONATE TO ME" ..... if you want to....
Did you try my Pre-Rooted Rom?? If not, you should
Click to expand...
Click to collapse
You just got a donation my friend!
Didn't try the prerooted... didn't see it for I9505XXUAMDF. Still, I'm used Chainfire's root and I'm back in business. No apps or data were wiped after the flash either, much to my surprise.
Waiting now for a working recovery and a decent ROM, like a Paranoid Android or CM10.1 port. In the mean time, I'm putting up with the TouchWiz jank + 320 DPI in spite of the odd scaling of some apps.
Cheers.

bonstio said:
You just got a donation my friend!
Didn't try the prerooted... didn't see it for I9505XXUAMDF. Still, I'm used Chainfire's root and I'm back in business. No apps or data were wiped after the flash either, much to my surprise.
Waiting now for a working recovery and a decent ROM, like a Paranoid Android or CM10.1 port. In the mean time, I'm putting up with the TouchWiz jank + 320 DPI in spite of the odd scaling of some apps.
Cheers.
Click to expand...
Click to collapse
Thanks a LoT! ) Appreciated
There's XXUAMDF on the list but it will give you just basic root permissions, no access to the system... In your case better use CF as it will give you full access..
Anyway, be more careful in future and enjoy it

S4 i9500 (I9500XXUAMDK with root) has soft brick
Dear friends. I would like your help, if possible! Please!
I did the actualization on my S4 i9500 (I9500XXUAMDK, with root) and after this, I was trying to put more space in sdcard (editing vold fstab files to try to change extSdCard into sdcard).
During this process, appeared a message on the phone about one error there is in sdcard and it suggested me to unmount the sdcard to try solve the problem. So, when I click yes, the phone froze and then I turned it off, but it stock now in Sangung Logo and go to recovery mode. In recovery mode I tryed to clear/mount/unmount any file, but it returns with error to mount any directories.
I think the phone has the files or some partition corrupted!!! . I can access it through ODIN and adb shell as well. There is (in adb commands) a command to fix the partition? How can I do?
With ODIN, I tried to re-install the original FW. It did well (complete the re-install perfectly), but the phone cant finish the instalation after this, because it cant mount anything, and goes to recovery mode with many messages about that it cant mount directories (list a vary directories that wasnt mounted correct).
Everything I try to do, the phones (in recovery mode) returns "cant mount... or error to mount something". I cant too clear cache, format /sdcard or other directory, or reset it to the factory data as well (because I think, the system cant mount any directories).
Somebody had this problem? or could help me to solve it, please!!!
Tks in advance!
Barros

[FIX] Cannot make calls or receive them and no sound on I9505

Hi all,
If you change ROM quite often and baseband too, most of the time everything goes smoothly, however, if you choose the wrong combination, you might encounter a very annoying issue: lost of the system sound, no ability of calling nor receiving phone calls.
I finally found a way to make my mobile sound working again (as it should) and I am able to call and receive phone calls as well. No reboots either.
When I started my investigation I had the following on my mobile:
ROM: [AOSP] Official 4.4.2 - S4 Google Edition - Final-R1.1 by jamal2367
Baseband: baseband XXUFNA1
Recovery: TWRP
Let me make the point. It is not because of the above settings that I had problems, but because of a combination of changing ROMs and baseband, probably only baseband.
When I was receiving a phone call only the vibration was working, no sounds, I couldn't slide the screen to answer properly, which means that I was able to slide, but the round icon of the slide could not catch the phone green icon. I could play no sound at all on videos, spotify, alarm, etc.; at the beginning I thought it was the current ROM, then
- I add to install Kies to try to restore the original firmware
- I changed it to another one
- I changed to CyanogenMod (and changed recovery to the default that comes with it: CWM)
- I rolled back to Samsung Stock edition (thank God I made a backup with TWRP months ago, before rooting)
Same damn issue and since I was there, I kept changing baseband with what I thought was the best for that particular (current) ROM. It is easy, you ask Mr. Google and he will tell you or you can try with http://www.sammobile.com/firmwares/2/
How can you fix it?
a. Download I9505XXUEMKF_I9505OXXEMK3_I9505XXUEMKF_HOME.tar.md5 and I9505XXUEMK8_I9505OXAEMK8_I9505XXUEMK8_HOME.tar.md5
b. Untar them in different directories
c. Use Heimdall - http://glassechidna.com.au/heimdall/ to flash all files in I9505XXUEMKF_I9505OXXEMK3_I9505XXUEMKF_HOME
c1. On Heimdal, click on the second tab _flash_, then browse your pit file, click on the button _add_ and choose the right partition. Do this for all the files inside the directory. Inside the _partitions (files)_ window you will have as many items as you have in the directory, in the example I put only 3, but you should have 12 of them in total (see image below)
- Under the partition ID, there is also a label/text that suggest you what file to choose.
- A note, MDM is for the modem, do not use MODEMST1 or MODEMST2
- If you do not have a pit, you can google it or as I did, use the forth tab _Utilities_, detect your device, and save as...under Download PIT.
c2. Then click on start to flash.
d. reboot in recovery and let CWM install unrecognized packages if asked. You might also find some red lines on the top left of the screen, but do not worry too much.
You might also find other red text _unable to unmount this or that_, after pressing start, but do not worry.
I tried to restart my mobile, but I was not able to restart it; in case you can, your stock Samsung ROM still has no sound. So
e. reboot in download and flash NON-HLOS.bin from the other folder I9505XXUEMK8_I9505OXAEMK8_I9505XXUEMK8_HOME. Use Partition Name _APNHLOS_ from partition Details in Heimdall.
f. the sounds is back
g. re-install your favourite recovery back
h. re-install your favourite ROM
I put back TWRP and [AOSP] Official 4.4.2 - S4 Google Edition - Final-R1.1 by jamal2367
Current baseband XXUEMKF. I will leave it as it is for a while, without changing it.
You can use Heimdall on windows too, but in case of driver problems use this to resolve the issue http://zadig.akeo.ie/
LTE and WiFi will work too.
You can get the two folders from this zip file: https://mega.co.nz/#!GARWHLDY!d2hrbCaVMKMLOXdNG6VfgkFMcjZclXJHTxe6amz0TNM
Note:
- When you flashed NON-HLOS.bin it might get the message stuck on _Rebooting device..._ and it does not give the impression that it finished. If you manual reboot and sometimes it means _remove the battery_, it will work.
- At the reboots note how the text on the top left changes during and after flashing.
At the booting now I get a warning text on the top-left (small text), it is something I can cope with or fix it later.
You can read in some posts that if _my phone number_ in unknown, under _status_ then you have problems with phone calls. I always had that one and still have it and it is working, so I wouldn't pay too much attention.
- if you have problems with heimdall, remove Kies (actually you can just remove it directly) and on mac, to remove some dependencies, run
sudo sh -
kextunload -b com.devguru.driver.SamsungComposite
kextunload -b com.devguru.driver.SamsungACMData
kextunload -b com.devguru.driver.SamsungACMControl
the uninstaller seems like it is working ok, so you might not need the above lines.

Or just flash the right non-hlos/wifi fix and that should fix your problem ...if you have a newbootloader just flash any latest non-hlos, but if you are still in oldbootloader feel free to flash a BMH1 non-hlos/wifi fix.. have a nice day.
Sent feom Hell ?

haven't really understood Step c1 Please @racoonlab

I cant find The pit File

Hi m_beek,
m_beek said:
I cant find The pit File
Click to expand...
Click to collapse
Have you tried the 4th tab of heimdall, utilities?
a. detect
b. save as
c. download
If you do not detect it, use the Zadig drivers first.
You can also try to have a look at http://forum.xda-developers.com/showthread.php?t=999097

What about getting "ERROR: Claiming interface failed!" after Clicking Start ?

m_beek said:
What about getting "ERROR: Claiming interface failed!" after Clicking Start ?
Click to expand...
Click to collapse
Do you have the Kies software installed? If yes, uninstall it and see also the last few lines of my post, to remove potential dependencies.
EDIT
Restart your machine too after the uninstall
R

Since I'm on W8 , I have never Installed Kies

m_beek said:
Since I'm on W8 , I have never Installed Kies
Click to expand...
Click to collapse
i. did you manage to get the pit?
ii when did you get that message, when flashing?
R

I couldn't get my Pit from _Utilities_ because of that, So I Googled "GT I9505 Pit" and download a Pit file, The After Managing Pit and Start flashing That What it's sayed
"This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
ERROR: Claiming interface failed!"

m_beek said:
I couldn't get my Pit from _Utilities_ because of that, So I Googled "GT I9505 Pit" and download a Pit file, The After Managing Pit and Start flashing That What it's sayed
"This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
ERROR: Claiming interface failed!"
Click to expand...
Click to collapse
Have you tried the Zadig drivers? To me it helped to:
- start the program
- see the list of the usb in used
- while the program was showing me the list, I unplugged the cable from one usb and attached to another one.
- run the program.
R

racoonlab said:
i. did you manage to get the pit?
ii when did you get that message, when flashing?
R
Click to expand...
Click to collapse
Ps. Odin Works, Can I Flash it with Odin ?

m_beek said:
Ps. Odin Works, Can I Flash it with Odin ?
Click to expand...
Click to collapse
probably with the latest yes.
http://www.xda-developers.com/android/mobile-odin-updated-to-version-4-new-features-and-devices/

racoonlab said:
probably with the latest yes.
http://www.xda-developers.com/android/mobile-odin-updated-to-version-4-new-features-and-devices/
Click to expand...
Click to collapse
Finally works
Ps. Its normal to get "Invalid Percent of Drawing progress Bar1"

Repulsa said:
Or just flash the right non-hlos/wifi fix and that should fix your problem ...if you have a newbootloader just flash any latest non-hlos, but if you are still in oldbootloader feel free to flash a BMH1 non-hlos/wifi fix.. have a nice day.
Sent feom Hell
Click to expand...
Click to collapse
Currently I have this one instaled I9505VJUHOK1. It was working fine with the stock ROM from SamMobile (http://www.sammobile.com/firmwares/download/61139/I9505VJUHOK1_I9505ZTOHOK1_ZTO/).
There is no sound at all on calls when using CM13.
What would you recommend?