Develop Bugs

[MOD] FuguRoot: root _any_ stock SGS ROM safely (froyo, GB)

Hello,
I created a kernel (based on fugumod) which supports all filesystems and has only one purpose, rooting any SGS stock ROM.
It installs:
- busybox
- su
- SuperUser
It also removes annoying boot and shutdown sounds.
Is it safe to use
It is safer than rooting using speedmod or whatever other all purpose kernel as it does not try to start android after rooting, so there is no fs corruption possible. It works even for very new leaks.
How to use:
1: Flash the stock rom
2: Download the image for Heimdall or for Odin
3: Flash it with either Odin or Heimdall
4: Boot once, it will install root and crash/shutdown (it is preferred to let the phone connected to usb so it does not loop boot)
5: Reflash the original kernel
How to reflash the original kernel on windows using Odin
1: install 7zip if don't have it already. It has been reported that IZarc or PeaZip may be more reliable.
2: unpack zImage which is in the PDA tar or tar.md5
3: with 7zip, IZarc or PeaZip create a new tar which contains only zImage and save
4: flash the the new tar using Odin
Does it work on ROM XXXXX?
It should work on every ROM since it recognizes all filesystems and does not try to start android.
Busybox was not installed on my device
Please download the updated version and retry, it will work fine.
Odin flashable stock kernel zImages
Ginberbread
JVB
Froyo
no image available yet, use samfirmware or google to get one

jvk?

runedrune said:
jvk?
Click to expand...
Click to collapse
I suppose "Even for very new leaks." includes JVK
Thanks for any excellent piece of work, nikademus!

runedrune said:
jvk?
Click to expand...
Click to collapse
Of course, I created it after JVK. It should support _all_ ROMs

Thanks, tested and working on JVK

Whoop!
I was worried that I'd have to wait for Samsung to do their OS code drop before I could switch to JVK, now I won't have to!
Thanks muchly.

thanks for your great work...
I just wanna know would recovery change to 2e???

radiohead_apple said:
thanks for your great work...
I just wanna know would recovery change to 2e???
Click to expand...
Click to collapse
No, it just roots your device, but once it's rooted you should be able to install another recovery.

Can someone upload JVK original kernel? I try to delete files in 7zip, it pop up an error message say "Not implanted"

tanjiajun_34 said:
Can someone upload JVK original kernel? I try to delete files in 7zip, it pop up an error message say "Not implanted"
Click to expand...
Click to collapse
You may want to try to create a new tar containing only zImage in this case

here u go

runedrune said:
here u go
Click to expand...
Click to collapse
You have been faster than me, I was just about to upload it.

Doesnt work for me. Flashed the fugu mod kernal easily but when trying to return to default kernal Odins log just says:
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> zImage
and stays at that until i unplug it.
Settings:
no pit or any other files just zimage.tar as PDA
no repartition
autoreboot.
Edit: worked using the kernal runedrune posted. Not sure why mine didnt. Extracted and packed into a tar archive using 7zip.

Sorry, but in Odin I have to flag reboot?
Example I have to flash your kernel as speedmod kernel?
Tanhks.

tonymacc said:
Sorry, but in Odin I have to flag reboot?
Example I have to flash your kernel as speedmod kernel?
Tanhks.
Click to expand...
Click to collapse
You will have to boot once into my kernel, so it's easier if you tell Odin to just reboot.

Also it didn't install busybox. had to install it myself. Just letting you know.

mcmac7 said:
Also it didn't install busybox. had to install it myself. Just letting you know.
Click to expand...
Click to collapse
busybox should have been installed in /system/xbin
Can somebody else confirm?

nikademus said:
busybox should have been installed in /system/xbin
Can somebody else confirm?
Click to expand...
Click to collapse
I don't have busybox either

I confirm it works very well, thanks !!
Just have to download busybox from market

radiohead_apple said:
I don't have busybox either
Click to expand...
Click to collapse
Ok, so could someone do a list of what is inside /sytem/xbin before installing busybox from the market?

[UPDATED 9/27] [ODIN] MetroPCS - M919N (UVUAMF2) STOCK ODIN Flashable

Hey there,
I know some people have been requesting this for quite some time! This couldn't have been possible without @techguy1214 so a huge thanks goes out to him!
This is the absolute STOCK M919N Firmware. (THIS IS NOT ROOTED!)
EXPERIMENTAL: This is UNTESTED by me, I compiled this ODIN tar file using the same structure the T-Mobile ODIN File has. I do not have the MetroPCS version of this phone, I have the T-Mobile version. But I figured enough people wanted it so I would try to make it happen.
CONFIRMED WORKING!
I will not be help responsible if you brick your device or flash this incorrectly and your phone ends up blowing up. You have been warned.
Click to expand...
Click to collapse
NOTE: Because this is not officially signed by Samsung, I believe your flash counter will go up, use Triangle Away to reset your counter!
Huge thanks goes out to @danyvw for picking up my slack, new instructions posted.
Link: https://docs.google.com/file/d/0BxJFwkvU-C2McW5zU0RWQ01hM2s/edit?usp=sharing
1. Download the above .zip file and extract the .tar file in the archive and save it somewhere
2. Reboot your phone to download mode.
To get download mode shut down the device. After it shuts off completely simultaneously press the Down volume key+ Home button + press the power button .
3. Start Odin
4. Click on the PDA button and browse to the .tar file that you extracted in step 1 and select it
5. DO NOT PUT .PIT FILE AND DO NOT TICK REPARTITION
6. Connect the USB cable and wait for the ID:COM section to turn blue
7. Click start to flash
8. Do not disconnect the cable or turn off the device once the flash has started, it’s going to take some time to flash, when finish exit Odin and disconnect USB.
9. Let the phone start and Voila!!!!!!

theexel said:
Hey there,
I know some people have been requesting this for quite some time! This couldn't have been possible without @techguy1214 so a huge thanks goes out to him!
This is the absolute STOCK M919N Firmware. (THIS IS NOT ROOTED!)
EXPERIMENTAL: This is UNTESTED by me, I compiled this ODIN tar file using the same structure the T-Mobile ODIN File has. I do not have the MetroPCS version of this phone, I have the T-Mobile version. But I figured enough people wanted it so I would try to make it happen.
AGAIN.. THIS MAY NOT WORK.
If it doesn't use the T-Mobile ODIN, it will work, but of course, you will have the T-Mobile Baseband and whatnot, but if it does not work, I will try to work on it again soon!
NOTE: Because this is not officially signed by Samsung, I believe your flash counter will go up, use Triangle Away to reset your counter!
Download the TAR file: https://copy.com/lyMNNbzjaNYm
Click to expand...
Click to collapse
i tired it it worked 100% thanks

techguy1214 said:
i tired it it worked 100% thanks
Click to expand...
Click to collapse
No, thank you @techguy1214.
Without you, we wouldn't have these files! :highfive:

What is STOCK M919N ?
Can you elaborate more about the different between this M919N & M919V (as an example):
Can we flash without root ?
Compatibility with what ROM or firmware ?
Report log or advantages...etc.?
Anything more...?

itzik_man said:
Can you elaborate more about the different between this M919N & M919V (as an example):
Can we flash without root ?
Compatibility with what ROM or firmware ?
Report log or advantages...etc.?
Anything more...?
Click to expand...
Click to collapse
M919N is the MetroPCS variant of the Galaxy S4.
M919V is the Wind / Mobilicity / Videotron variant of the Galaxy S4, I believe.
This is for people that maybe messed up flashing a ROM or simply want to go back to barebone OFFICIAL MetroPCS stock firmware due to any reason. (Most likely they broke something and want to send it to warranty, lol.)

techguy1214 said:
i tired it it worked 100% thanks
Click to expand...
Click to collapse
any 1 else confirm this....??

djlucklu said:
any 1 else confirm this....??
Click to expand...
Click to collapse
Seems not...

arocker said:
Seems not...
Click to expand...
Click to collapse
Did not work for me. I jumped the gun and flashed a tmo stock rom to see if I could unlock my phone for free. I am unable to flash back to this rom now and can't unlock using a tmo rom.
Can anyone confirm that the pit files are different between the M919 and M919N? I tried a lot of different things last night and I think I flashed the M919 pit file as well as the rom, which is most likely my problem. Odin fails as soon as it tries to write.

Doesn't work
I tried to flash many times with different downloads and always get the same flash error:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NON-HLOS.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

I get the exact same error.

downloading now ill let you know

fatalfury said:
downloading now ill let you know
Click to expand...
Click to collapse
Any update fatalfury?

people with errors making sure kies is not open right ? also try the USB port on back of computer and test again

krazierokz said:
people with errors making sure kies is not open right ? also try the USB port on back of computer and test again
Click to expand...
Click to collapse
Is not with Kies, its with Odin. Kies does not have firmware support for the SGH-M91N.

Understood just stating that Odin and kies open together conflicts and Odin won't run right that's all I'm saying
sent from my t mobile S4

Fixing Issues an PLEAS!!!
zbennett15 said:
I get the exact same error.
Click to expand...
Click to collapse
For this you are going to need mobile Odin To Flash an you will need to flash twice after you flash it the first time!:laugh::fingers-crossed:

techguy1214 said:
For this you are going to need mobile Odin To Flash an you will need to flash twice after you flash it the first time!:laugh::fingers-crossed:
Click to expand...
Click to collapse
Same error with PC odin, and when trying to open with mobile odin - partition could not be found.
---------- Post added at 07:20 PM ---------- Previous post was at 06:50 PM ----------
techguy1214 said:
i tired it it worked 100% thanks
Click to expand...
Click to collapse
Hey! how you flashed it? Thanks in advance.

I made some changes to techguy file.Is Working flawlessly with Odin, posted on androidforums:
http://androidforums.com/metropcs-g...t/773372-unofficial-m919nuvuamf2-working.html

danyvw said:
I made some changes to techguy file.Is Working flawlessly with Odin, posted on androidforums:
http://androidforums.com/metropcs-g...t/773372-unofficial-m919nuvuamf2-working.html
Click to expand...
Click to collapse
Updated OP, thank you.

Exel said:
Updated OP, thank you.
Click to expand...
Click to collapse
Thank you! Without your file I wouldn't have done anything. :good:

Flash Modem from Stock FW

Hi Guys,
i got some signal problems with my S4 mini (gt-i9195 android 4.4.2 (CM11))
So i decided to flash the newest modem.
I downloaded the newest firmware from samdownloads.com and extracted the tar file.
But i can´t find any modem.bin, theres only the NON-HLOS.bin
The tar file contains the following files:
- cache.img.ext4
- hidden.img.ext4
- system.img.ext4
- boot.img
- recovery.img
- aboot.mbn
- rpm.mbn
- sbl2.mbn
- sbl3.mbn
- tz.mbn
- NIN-HLOS.bin
Is the modem.bin packed in one of these files? Can i extract it?

Backup the entire your CM11. Flash newest stock firmware via Odin. Install CWM. Restore your CM11 via CWM. You'll have latest modem.

ladislav.heller said:
Backup the entire your CM11. Flash newest stock firmware via Odin. Install CWM. Restore your CM11 via CWM. You'll have latest modem.
Click to expand...
Click to collapse
Okay thanks fort your reply, i thought there would be a way to extract the modem file via cygwin.
But that workaround should also work for me.

hannes22 said:
Okay thanks fort your reply, i thought there would be a way to extract the modem file via cygwin.
But that workaround should also work for me.
Click to expand...
Click to collapse
You can extract NON-HLOS.bin via Total Commander. Bigger question is, how to repack it to Odin format
But yes, the answer is Cygwin.
Here are the commands:
Code:
tar -H ustar -c NON-HLOS.bin > modem.tar
md5sum -t modem.tar >> modem.tar
mv modem.tar modem.tar.md5

ladislav.heller said:
You can extract NON-HLOS.bin via Total Commander. Bigger question is, how to repack it to Odin format
But yes, the answer is Cygwin.
Here are the commands:
Code:
tar -H ustar -c NON-HLOS.bin > modem.tar
md5sum -t modem.tar >> modem.tar
mv modem.tar modem.tar.md5
Click to expand...
Click to collapse
i hope i dont get this totally wrong, but is the modem.bin inside the "NON-HLOS.bin" ?
Cause i already flashed the "NON-HLOS.bin" via odin (phone) but that didnt change the baseband version..
Anyway i think i will flash the whole firmware tomorrow to make sure theres nothing missing..

hannes22 said:
i hope i dont get this totally wrong, but is the modem.bin inside the "NON-HLOS.bin" ?
Cause i already flashed the "NON-HLOS.bin" via odin (phone) but that didnt change the baseband version..
Anyway i think i will flash the whole firmware tomorrow to make sure theres nothing missing..
Click to expand...
Click to collapse
Yep NON-HLOS is the modem file
Flash it more times, like 2 3 times and it will work Baseband will change
Phone in Odin 3.07 CP in 3.09

Sorry to inrupt but if i have an odin tar and i delete all its contents except the 3 files including non-hlos im gonna get the baseband right?? .. note that the the 2 other files came where i saw on s4mini archive an bna1 flashable odin tar modem only so check its contents there is non hlos img and 2 other files ... hope u understood and i helped
Sent from my GT-I9192 using XDA Premium 4 mobile app

SilviuMik said:
Yep NON-HLOS is the modem file
Flash it more times, like 2 3 times and it will work Baseband will change
Phone in Odin 3.07 CP in 3.09
Click to expand...
Click to collapse
I unchecked the auto reboot and flashed it 3 times and the baseband version changed!
THANK YOU VERY MUCH!

rrgrrg said:
Sorry to inrupt but if i have an odin tar and i delete all its contents except the 3 files including non-hlos im gonna get the baseband right?? .. note that the the 2 other files came where i saw on s4mini archive an bna1 flashable odin tar modem only so check its contents there is non hlos img and 2 other files ... hope u understood and i helped
Sent from my GT-I9192 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
sorry mate but i dont really understand you
but my problem is solved now!

rrgrrg said:
Sorry to inrupt but if i have an odin tar and i delete all its contents except the 3 files including non-hlos im gonna get the baseband right?? .. note that the the 2 other files came where i saw on s4mini archive an bna1 flashable odin tar modem only so check its contents there is non hlos img and 2 other files ... hope u understood and i helped
Sent from my GT-I9192 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This will not work because the TAR also has a checksum included and Odin will check it first. You need to repack NON-HLOS.bin file.

ladislav.heller said:
This will not work because the TAR also has a checksum included and Odin will check it first. You need to repack NON-HLOS.bin file.
Click to expand...
Click to collapse
Oh i see :/

Galaxy Note II Stuck on System in Odin

<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img
My Galaxy Note II has been stuck on this for a while. I was trying to recover it via kies but it never worked so i tried out the Odin and this happened..
Please show me to any tutorial or post below a tutorial.

Katrxc said:
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img
My Galaxy Note II has been stuck on this for a while. I was trying to recover it via kies but it never worked so i tried out the Odin and this happened..
Please show me to any tutorial or post below a tutorial.
Click to expand...
Click to collapse
You working???
Lots of info is missing for anyone to help you....
Who is your network carrier? What did you try to flash? What version of ODIN....
If you are on ATT this may help
http://forum.xda-developers.com/showthread.php?t=2589891

Redownload the rom file. The cheesy sites developers use to host their roms are sketchy at best, and at worst they give you an incomplete file.

rangercaptain said:
Redownload the rom file. The cheesy sites developers use to host their roms are sketchy at best, and at worst they give you an incomplete file.
Click to expand...
Click to collapse
But he's using ODIN.... So he's flashing firmware.

Every ROM is firmware amigo. If the firmware is in a zip file set up for TWRP or CWR, good. If its in the tar format we use Odin3.
If you look inside the zip file it has a tar file in it.

rangercaptain said:
Every ROM is firmware amigo. If the firmware is in a zip file set up for TWRP or CWR, good. If its in the tar format we use Odin3.
If you look inside the zip file it has a tar file in it.
Click to expand...
Click to collapse
:
Uh yea,,,,
Senior Member
Thanks Meter 682
Posts: 1,584
Join Date: Sep 2010
I may be slightly familiar with the process and the difference.
I was pointing out the fact that it is failing while flashing with ODIN...
So your comment that
"The cheesy sites developers use to host their roms are sketchy at best, and at worst they give you an incomplete file."
was probably not relevant in this case, since 99.969% of the free ROMs that devs freely build and graciously host on free sites, are not flashed in ODIN.

Only 682? Thats pretty weak amigo. Since 2010? You're so new you glow! I don't know what your malfunction is.
Samsung is a ROM/firmware developer. And Samfirmware.com (or whatever its called) is a sometimes spotty site.
The advice is still the same:
1. Redownload
2. Use the factory cable
3. Use the powered usb port
4. Use another version of Odin3.

rangercaptain said:
Only 682? Thats pretty weak amigo. Since 2010? You're so new you glow! I don't know what your malfunction is.
Samsung is a ROM/firmware developer. And Samfirmware.com (or whatever its called) is a sometimes spotty site.
The advice is still the same:
1. Redownload
2. Use the factory cable
3. Use the powered usb port
4. Use another version of Odin3.
Click to expand...
Click to collapse
No problem here slick. Yep having a life is rough.
I guess I would have to agree that a download of the stock ROM firmware from sammobile.com (which is not actually associated with the ROM/firmware developer Samsung) (http://www.sammobile.com/about-us/) would be a good idea, and then flash via ODIN.
Vice a download of a Dev ROM that perhaps an XDA developer posted on a cheesy site, which I mistaken thought you were implying.
That is why I posted the simple glowing statement, but it's an ODIN flash. Didn't expect a ROM flash 101 class.

Attack the OP's problem, not members who contribute solutions.
All you have done here was try to show everyone you're the smartest guy in the room.
Run along now.

rangercaptain said:
Attack the OP's problem, not members who contribute solutions.
All you have done here was try to show everyone you're the smartest guy in the room.
Run along now.
Click to expand...
Click to collapse
Respectfully, that's what I was trying to do, by asking questions. Like what were they trying to flash.
Then you jumped in and suggested to redownload, Without ensuring they were even flashing the right thing.
I have seen you give out great advice. That's why this seemed odd.

99% of the times a flash fails in Odin3 or recovery its because of a file error. If it was the wrong file for the phone it would flash and brick or it would stop immediately. But since he got most of the way through the process, I concluded correct file but likely corrupt download.
But you already know this.
---------- Post added at 01:49 PM ---------- Previous post was at 01:44 PM ----------
I actually made up the 99%, but its most of the time.

Flashing DOl1 Issues

Ok i know there are some threads or posts that are trying to solve this problem, or they already solved this problem but i cannot find a real solution for my phone. When i flash the latest built DOl1 with odin i get stuck on Samsung Logo. I can pass that when i flash a custom kernel, but i just want my phone to be fully stock.
So i have extracted .tar.md5 and than i have compressed .tar on Linux all the files excluding cache.img. Because it seems that cache.img is causing the firmware from booting after flashing with odin. But without cache.img i missed some features like: keyboard word suggestion and some other things and i feel that the phone is not working as it should, it always have problems.
i have done tons of test yesterday by spliting the tarball into two packages bl.tar and ap.tar but still nothing. Even when i flash separatly cache.img or boot.img i get stuck.
Is there any solution for these ? Does anybody know anything ?

What version of Odin are you using? And where did you down the tar?
Sent from my SM-G925T using Tapatalk

Was your phone rooted? Flash the unikernel and it will boot.

nappent said:
What version of Odin are you using? And where did you down the tar?
Sent from my SM-G925T using Tapatalk
Click to expand...
Click to collapse
Iv used odin 3.10.6 and 3.10.7 both of em. The tar is downloaded from sammobile and samsung-firmwares just tried out two different sites

atinder said:
Was your phone rooted? Flash the unikernel and it will boot.
Click to expand...
Click to collapse
I know it will boot with a costum kernel. I just want it all the way stock. Thank you anyway

I just recently flashed back to stock DOI1 in preperation for JUMPing to the note 5 and I've had no problems. I used ODIN 3.10.7 and the tar that @Alex9090 posted in another thread. Maybe try that one and see if it works.
It's weird that it'll only boot with a custom kernel though. I was on UniKernel v9 and flashed stock without issue.

caspernetherlands said:
I know it will boot with a costum kernel. I just want it all the way stock. Thank you anyway
Click to expand...
Click to collapse
Please make sure you have oem unlocking on before flashing anything. I have paper weight with me because of that

atinder said:
Please make sure you have oem unlocking on before flashing anything. I have paper weight with me because of that
Click to expand...
Click to collapse
Yes sir OEM Unlocking is on

caspernetherlands said:
Yes sir OEM Unlocking is on
Click to expand...
Click to collapse
are you stuck on samsung boot logo? i am unploading custom ap and bl. if you know how to compile its easier as uploading will take time.
C:\windows\system32>cd c:\users\atinder\desktop\tartool
c:\Users\Atinder\Desktop\tartool>cd bin
//copy files to folder for eg - cm.bin and sboot.bin to pack as Bl.tar
//order entered would be the order they are being flashed
c:\Users\Atinder\Desktop\tartool\bin>tar -H ustar -c cm.bin sboot.bin > BL.tar
//copy files to folder eg - boot.img system.img to AP.tar
//order entered would be order they are being flashed
c:\Users\Atinder\Desktop\tartool\bin>tar -H ustar -c boot.img system.img > AP.tar
c:\Users\Atinder\Desktop\tartool\bin>

atinder said:
Please make sure you have oem unlocking on before flashing anything. I have paper weight with me because of that
Click to expand...
Click to collapse
can you unlock the bootloader/ oem unlocking in any other ways without booting up system such as adb, odin, download mode?

Install recovery and wipe all and then installs DOI1