Does anyone have or can make a 4.4.2 debrick file for a gs3 r530u and r530?
Please someone help us
Sent from my LG-D855 using XDA Free mobile app
what service provider model is that?
Is the same as the i535 for Verizon
Sent from my LG-D855 using XDA Free mobile app
3izz said:
Is the same as the i535 for Verizon
Sent from my LG-D855 using XDA Free mobile app
Click to expand...
Click to collapse
I've waited for almost 2 years to have R530C debrick image, no one have that file. I almost give up, and then my stupid idea came up... ( You'll need linux terminal, and basic linux command knowledge )
1.) Download odin package for your device ( make sure it's the same version with your latest firmware before got bricked )
2.) Extract the .tar.md5 file ( WinRar / 7zip will give error message, just ignore it )
3.) Grab debrick image for your device, or at least the same variant ( R530C / U / M ) firmware version doesn't matter.
4.) Clone the debrick image to your microSD card.
5.) Now back to extracted folder of your firmware, copy these files :
sbl1.mbn
sbl2.mbn
sbl3.mbn
aboot.mbn
rpm.mbn
tz.mbn
to your working directory
6.) List your debrick microSD partition using parted ( mine was /dev/sdb, make sure you have the right partition before doing these commands )
I forgot the command, but it's something like
Code:
parted /dev/sdb
Code:
(parted) print
7.) Now you can see the partition list (sbl1,sbl2,etc)
8.) And then do this :
sudo dd if=sbl1.mbn of=/dev/sdbX
sudo dd if=sbl2.mbn of=/dev/sdbX
sudo dd if=sbl3.mbn of=/dev/sdbX
sudo dd if=aboot.mbn of=/dev/sdbX
sudo dd if=rpm.mbn of=/dev/sdbX
sudo dd if=tz.mbn of=/dev/sdbX
9.) After finishing all the command, remove your microSD from card reader, cross finger.. and Good Luck.
Sorry for my "not-so-easy" tutorial, I wish I could explain it a little easier to understand.. but my english sucks
Related
Ok, so I am trying to flash a new splash image onto my G2. The image is on the root of my SD card like this /sdcard/new_splash.img
I open the mobile terminal and get this:
$ su
# cd /sdcard
# flash_image splash1 new_splash.img
failed with error: -1
Any ideas??
Are you sure you have the flash_image script on your phone?
Sent from my HTC Vision
Yes, because I flashed CWM Recovery with flash_image.
Sent from my HTC Vision using XDA App
troby86 said:
Ok, so I am trying to flash a new splash image onto my G2. The image is on the root of my SD card like this /sdcard/new_splash.img
I open the mobile terminal and get this:
$ su
# cd /sdcard
# flash_image splash1 new_splash.img
failed with error: -1
Any ideas??
Click to expand...
Click to collapse
Try
$ su
# flash_image splash1 /sdcard/new_splash.img
This method still fails with error -1
Sent from my G2 using XDA App
Ops Dobbel post ..
Be very careful with this method and check that you typed everything correctly so you do not accidentally brick your phone
Code:
$ Su
# dd if=/mnt/sdcard/splash.img of=/dev/block/mmcblk0p19
(Copy and past it)
(Splash.img = the name of your splash.img )
Worked perfect! Thanks
Sent from my HTC Vision using XDA App
troby86 said:
Worked perfect! Thanks
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
No problem . Happy to help.
Will this work on the backflip?
stian230 said:
Be very careful with this method and check that you typed everything correctly so you do not accidentally brick your phone
Code:
$ Su
# dd if=/mnt/sdcard/splash.img of=/dev/block/mmcblk0p19
(Copy and past it)
(Splash.img = the name of your splash.img )
Click to expand...
Click to collapse
I want to be extra sure your method isn't device independent before I try it; especially since I'm not sure where it's pointing too...
To be a sharin, heres what I've tried and got so far...
I was able to pull the M splash screen and convert it to BMP on my backflip (s-on) with:
adb
su
cat /dev/mtd/mtd6 > /sdcard/splash.img
nbimg -h 480 -w 360 -F splash.nb
but now I can't get the new one back... any suggestions? Tried:
cat /sdcard/splash.img > /dev/mtd/mtd6
...and...
flash_image splash /sdcard/splash.img
to no effect.
can I...:
dd if=/sdcard/splash.img of=/dev/mtd/mtd6
? I'm fairly new to linux, I don't fully understand the mount process...
-----------------------------------------------------------------------------
I've been playing around, I don't have mmcblk0p19, I only have mmcblk0 and mmcblk0p1. My next task is to pull these off and see if I can't figure out what they are.
This is a new device and the development is starting quickly. Many user that haven't the device is starting to develop some stuff for it also if they don't have the phone ( like me ).
Kernel testing can cause softbrick that can be easy fixed flashing again the stock kernel. The following steps explain how to do a backup of your current kernel so you can use it to restore your device.
It's a very simple guide.....
IMPORTANT You need to use adb ( also terminal emulator is good) and you need to be root!
Code:
su
dd if=/dev/block/bml7 of=/sdcard/boot.img
tar cvf /sdcard/kernel-backup.tar /sdcard/boot.img
IMPORTANT: Write the commands exactly like i wrote and put attention that in the second command. I wrote "BML7" not "BM17" but you have to write without capital letter so "bml7" OK?
After this you'll have a file called kernel-backup.tar in your SDcard. Save it and, in case of softbrick testing a new kernel, put your phone in download mode and flash it with odin (PDA field).
Wish this can help you...
Bye
I got
Code:
su
# dd if=/dev/block/bml7 of=/sdcard/boot.img
dd if=/dev/block/bml7 of=/sdcard/boot.img
# tar cvf /sdcard/kernel-backup.tar /sdcard/boot.img
tar cvf /sdcard/kernel-backup.tar /sdcard/boot.img
tar: removing leading '/' from member names
sdcard/boot.img
#
Nvm.. my bad
noobwithgalaxyy said:
I got
Code:
su
# dd if=/dev/block/bml7 of=/sdcard/boot.img
dd if=/dev/block/bml7 of=/sdcard/boot.img
# tar cvf /sdcard/kernel-backup.tar /sdcard/boot.img
tar cvf /sdcard/kernel-backup.tar /sdcard/boot.img
tar: removing leading '/' from member names
sdcard/boot.img
#
Click to expand...
Click to collapse
check your sd card root. the files are there.
it creates two files..."boot.img" and "karnel-backup.tar"...
which one should I flash with Odin??
amlanpaira said:
it creates two files..."boot.img" and "karnel-backup.tar"...
which one should I flash with Odin??
Click to expand...
Click to collapse
The tar file
The problem is that odin wont flash it i guess !
Sent from my GT-S5360 using XDA App
It doesn't.. I checked..
Sent from my GT-S5360 using XDA App
noobwithgalaxyy said:
It doesn't.. I checked..
Sent from my GT-S5360 using XDA App
Click to expand...
Click to collapse
As i expected !!!we have big problem with odin ...
Sent from my GT-S5360 using XDA App
Yeah we do have a problem.. but Skin did make it work(flashing CWM was successful, even though it didn't work)
If he can let us know how and why other single file flashes do not work..
@ skin1980 can we convert somehow this tar file to update.zip so we can flash it from CWM recovery?
get back up ...
Thank you ..
now and discover how to use it if you need
I wonder if it has the backing of the baseband
Here in Brazil is put another baseband .... we are unsigned operators: /
Code:
C:\Users\hubert>adb shell
$ su
su
# dd if=/dev/block/bml7 of=/sdcard/boot.img
dd if=/dev/block/bml7 of=/sdcard/boot.img
# tar cvf /sdcard/kernel-backup.tar /sdcard/boot.img
tar cvf /sdcard/kernel-backup.tar /sdcard/boot.img
tar: not found
#
what am I doing wrong?
Preterer said:
Code:
C:\Users\hubert>adb shell
$ su
su
# dd if=/dev/block/bml7 of=/sdcard/boot.img
dd if=/dev/block/bml7 of=/sdcard/boot.img
# tar cvf /sdcard/kernel-backup.tar /sdcard/boot.img
tar cvf /sdcard/kernel-backup.tar /sdcard/boot.img
tar: not found
#
what am I doing wrong?
Click to expand...
Click to collapse
both the files are now on your sd card check them...........
rohit589769 said:
both the files are now on your sd card check them...........
Click to expand...
Click to collapse
You are wrong, there is only boot.img .
Preterer said:
Code:
C:\Users\hubert>adb shell
$ su
su
# dd if=/dev/block/bml7 of=/sdcard/boot.img
dd if=/dev/block/bml7 of=/sdcard/boot.img
# tar cvf /sdcard/kernel-backup.tar /sdcard/boot.img
tar cvf /sdcard/kernel-backup.tar /sdcard/boot.img
tar: not found
#
what am I doing wrong?
Click to expand...
Click to collapse
You have to install busybox!
look for busybox installers on Market!
I've created a tar and flashed it with odin. It works fine.
I'm currently working on a replacement for heimdall that will support this phone and some others. So if you make a backup you will be able to restore it later.
s0unds said:
I've created a tar and flashed it with odin. It works fine.
I'm currently working on a replacement for heimdall that will support this phone and some others. So if you make a backup you will be able to restore it later.
Click to expand...
Click to collapse
Keep us updated please for anything new!
Sent from my GT-S5360 using XDA App
Is the boot.img and kernel-backup.tar only sized 5MB?
Sent from my GT-S5360 using XDA App
qtu said:
Is the boot.img and kernel-backup.tar only sized 5MB?
Sent from my GT-S5360 using XDA App
Click to expand...
Click to collapse
It's a really small file, cause it's only Kernel, not whole sys.
Preterer said:
It's a really small file, cause it's only Kernel, not whole sys.
Click to expand...
Click to collapse
I see! Thanks a lot! Now, my kernel is backed-up.
Quick and dirty guide on how-to delete bootloader stuff that contain Knox from stock rom ( only works on Jelly Bean ) . On KitKat we have Knox 2.0 which is more harder to conquer
Only use it if u do not have KNOX WARRANTY in download mode
U need : a virtual machine or any linux environment . I use Vmware player + Linux Mint 16 x64
First download the rom from Sammobile and place it on your Desktop in a folder called work in linux
Let`s say we download Russia one for I9192
I9192XXUBMK4_I9192SERBMJ3_SER.zip
U can use this guide on other versions of this phone I9190/I9195
Firmwares that contain MK4/MK5/ML1/ML2/ML4/NA1/NA2 and so on from here have Knox bootloader inside
Only the name will be different but what is inside is the same
Only latest versions of firmware contain Knox Bootloader ( usually the ones released in late november/december 2013 )
Open terminal and type
Code:
cd Desktop
cd work
Now we need to extract it
Code:
unzip *.zip
U will get 2 files
First: I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar.md5
Second: SS_DL.dll
Now again in terminal type:
Code:
rm -rf SS_DL.dll
tar -xvf *.tar.md5
After it will finish to extract we can delete the files we do not need
Code:
rm -rf aboot.mbn - bootloader ( knox included )
rm -rf sbl1.mbn - part of bootloader
rm -rf sbl2.mbn - part of bootloader
rm -rf sbl3.mbn - part of bootloader
rm -rf *.tar.md5
Now we can place it back in an archive. Choose any name u want i had chosen original name for reference only.
Code:
tar -H ustar -c rpm.mbn tz.mbn boot.img recovery.img system.img.ext4 NON-HLOS.bin cache.img.ext4 hidden.img.ext4 > I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar
After comes md5 stuff
Code:
md5sum -t I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar >> I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar
mv I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar.md5
Now transfer it to your windows pc and flash it with Odin Make sure u do not rename the file at this stage or md5 checksum will fail
Double check it before u flash, look inside the archive that u don`t have those files u just deleted Maybe u did not move the correct file
Video of "How to" credit to @Mitko
SilviuMik said:
Quick and dirty guide on how-to delete bootloader stuff that contain Knox from stock rom
Only use it if u do not have KNOX WARRANTY in download mode
U need : a virtual machine or any linux environment . I use Vmware player + Linux Mint 16 x64
First download the rom from Sammobile and place it on your Desktop in a folder called work in linux
Let`s say we download Russia one
I9192XXUBMK4_I9192SERBMJ3_SER.zip
Open terminal and type
Code:
cd Desktop
cd work
Now we need to extract it
Code:
unzip I9192XXUBMK4_I9192SERBMJ3_SER.zip
U will get 2 files
First: I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar.md5
Second: SS_DL.dll
Now again in terminal type:
Code:
rm -rf SS_DL.dll
tar -xvf I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar.md5
After it will finish to extract we can delete the files we do not need
Code:
rm -rf aboot.mbn
rm -rf sbl1.mbn
rm -rf sbl2.mbn
rm -rf sbl3.mbn
rm -rf I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar.md5
Now we can place it back in an archive. Choose any name u want i had chosen original name for reference only.
Code:
tar -H ustar -c rpm.mbn tz.mbn boot.img recovery.img system.img.ext4 NON-HLOS.bin cache.img.ext4 hidden.img.ext4 > I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar
After comes md5 stuff
Code:
md5sum -t I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar >> I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar
mv I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar.md5
Now transfer it to your windows pc and flash it with Odin Make sure u do not rename the file at this stage or md5 checksum will fail
Double check it before u flash, look inside the archive that u don`t have those files u just deleted Maybe u did not move the correct file
Click to expand...
Click to collapse
Is this BMK4 firmware different from previous versions by introducing Knox and improvement of battery? Can we transfer the rpm bootloader to previous version and enjoy the battery consumption improvement?
hobbya said:
Is this BMK4 firmware different from previous versions by introducing Knox and improvement of battery? Can we transfer the rpm bootloader to previous version and enjoy the battery consumption improvement?
Click to expand...
Click to collapse
I think u can yes But i also think some improvements were made in Modem/Kernel
That rpm.mbn file gets flashed in a special partition and does not get overwritten only if u flash a new one from a firmware that contain it. As i mentioned in other forum only last ones does contain it Russia, Brazil, Trinidad MK4
allows downgrade?
Once flashed this firmware without knox, would can move back to a previous version?
I ask that flashing the stock rom of samsung knox is no longer possible downgrade.
Thanks and regards,
Trepanator56 said:
Once flashed this firmware without knox, would can move back to a previous version?
I ask that flashing the stock rom of samsung knox is no longer possible downgrade.
Thanks and regards,
Click to expand...
Click to collapse
Yes u can downgrade as long as u don`t flash new bootloader
Use the tutorial and remove the files from stock rom before flashing. If u already have the new bootloader on phone u are out of luck
SilviuMik said:
Yes u can downgrade as long as u don`t flash new bootloader
Use the tutorial and remove the files from stock rom before flashing. If u already have the new bootloader on phone u are out of luck
Click to expand...
Click to collapse
One question, I flashed the stock thing via Heimdall and my wi-fi is not working. I think it didn't flash the tz.bin, since I saw you say on other thread that it was important for wifi to work in Brazil...
Is there anyway to fix it? Or I got myself screwed?
Dijinn said:
One question, I flashed the stock thing via Heimdall and my wi-fi is not working. I think it didn't flash the tz.bin, since I saw you say on other thread that it was important for wifi to work in Brazil...
Is there anyway to fix it? Or I got myself screwed?
Click to expand...
Click to collapse
Flash it with Odin that tz file and u are good to go
Same procedure as making an kernel from stock or modem
tar -H ustar -c tz.mbn > name.tar
md5sum -t name.tar >> name.tar
mv name.tar name.tar.md5
SilviuMik said:
Flash it with Odin that tz file and u are good to go
Same procedure as making an kernel from stock or modem
tar -H ustar -c tz.mbn > name.tar
md5sum -t name.tar >> name.tar
mv name.tar name.tar.md5
Click to expand...
Click to collapse
Well, we got another problem... Here... I'm on a MAC right now, so my only flashing thingy is Heimdall or ADB...
I tried flashing the tz.mbn file 3 times via Heimdall, it doesn't even open the recovery after I flash it... And wi-fi is never back...
I got ur version of the files and flashed everything again, still, no wi-fi, probably because of the tz.mbn
The funny thing is that Heimdall himself says the file was uploaded to the phone, but it seems it's not "installing" it if u understand what I mean...
Dijinn said:
Well, we got another problem... Here... I'm on a MAC right now, so my only flashing thingy is Heimdall or ADB...
I tried flashing the tz.mbn file 3 times via Heimdall, it doesn't even open the recovery after I flash it... And wi-fi is never back...
I got ur version of the files and flashed everything again, still, no wi-fi, probably because of the tz.mbn
The funny thing is that Heimdall himself says the file was uploaded to the phone, but it seems it's not "installing" it if u understand what I mean...
Click to expand...
Click to collapse
Sorry mate then flash an older file that does not contain Knox Hope u get your Wifi back
SilviuMik said:
Sorry mate then flash an older file that does not contain Knox Hope u get your Wifi back
Click to expand...
Click to collapse
I solved the problem!
If someone else has trouble fixing the Wi-Fi after the flash via Heimdall, here goes!
Flashing TZ partition only won't do anything...you upload the file, but it doesn't seem to get flashed...
The solution is to flash both MODEM and TZ partitions... It seems that when you reflash the modem, the cellphone tends to check for TZ again and TADA! Now it will be there!
Do you think that I could do the same for i9195 ?
Darktitor said:
Do you think that I could do the same for i9195 ?
Click to expand...
Click to collapse
Yes of course Is the same for all 3 models 9190 9192 9195
Great
My friend will be happy
Envoyé de mon GT-I9195 en utilisant Tapatalk
Apparently the contents of S4 (I9505) is same ... I made the change with Ubuntu, it does.
Before to flash, I would like to be sure.
Think it should do as correctly as your model?
franzyroy said:
Apparently the contents of S4 (I9505) is same ... I made the change with Ubuntu, it does.
Before to flash, I would like to be sure.
Think it should do as correctly as your model?
Click to expand...
Click to collapse
I have no ideea about S4 Maybe knox is in other places too like modem or no ideea. I can`t guarantee. On S4 mini is in aboot.mbn sbl1 sbl2 sbl3 ( bootloader )
Thanks for answer!
So, that's the reason you removed the modem.bin file?
What is the risk to try? Except to have the new bootloader.
franzyroy said:
Thanks for answer!
So, that's the reason you removed the modem.bin file?
What is the risk to try? Except to have the new bootloader.
Click to expand...
Click to collapse
I did not remove modem file
modem is named NON-HLOS.bin i keep it
If u have old bootloader ( no knox in download mode ) yes risk is to get new bootloader with knox
Pls check on S4 forums maybe someone did the same as me with S4 and knows more
SilviuMik said:
I did not remove modem file
modem is named NON-HLOS.bin i keep it
If u have old bootloader ( no knox in download mode ) yes risk is to get new bootloader with knox
Pls check on S4 forums maybe someone did the same as me with S4 and knows more
Click to expand...
Click to collapse
On the S4 (I9505), I also have NON-HLOS.bin, but I also have modem.bin file.
Not seen on the S4 forums a subject on that!
---------- Post added at 03:17 PM ---------- Previous post was at 03:15 PM ----------
SilviuMik said:
If u have old bootloader ( no knox in download mode ) yes risk is to get new bootloader with knox
Click to expand...
Click to collapse
Except this risk... This one, I'll have it certainly with the SAV!!
---------- Post added at 03:21 PM ---------- Previous post was at 03:17 PM ----------
Otherwise, I followed your tuto and like I didn't see the modem.bin file, I removed it. At worse, I could flash it after.
franzyroy said:
On the S4 (I9505), I also have NON-HLOS.bin, but I also have modem.bin file.
Not seen on the S4 forums a subject on that!
---------- Post added at 03:17 PM ---------- Previous post was at 03:15 PM ----------
Except this risk... This one, I'll have it certainly with the SAV!!
---------- Post added at 03:21 PM ---------- Previous post was at 03:17 PM ----------
Otherwise, I followed your tuto and like I didn't see the modem.bin file, I removed it. At worse, I could flash it after.
Click to expand...
Click to collapse
Yes of course , better to try then flash all the files and see after
Btw, S4 Mini Knox firmware contains:
sbl1.mbn - part of new bootloader , safe to delete
sbl2.mbn - part of new bootloader , safe to delete
sbl3.mbn - part of new bootloader , safe to delete
aboot.mbn - New Knox bootloader , DELETE
rpm.mbn - Resource power Management link
tz.mbn - Trusted zone ( Wifi won`t work if u don`t flash it together with new Modem )
boot.img - Kernel
recovery.img - Recovery/Download mode
system.img.ext4 - your apps/framework/android
NON-HLOS.bin - modem
cache.img.ext4 - CSC / APN settins / What bloat is to be installed depending on zone / carrier
hidden.img.ext4 - Another "system" part of apps that are too big for /system ( for now almost empty ) on S2 was full of apps
Try and see
Thanks ... I know for the S4(I9505), when we have old bootloader, we must put this (GSM_Modem_XXUEMJ5_and_LTE_Modem_XXUBMH1.zip ) modem for that all works.
Perhaps, I can replace modem.bin and NON-HLOS.bin by those in the zip.
SM-T705, CF-Autoroot:
cf-autoroot changes recovery. So after rooting I want to restore the correct recovery.img from my stock firmware package.
- Can this be done with dd (no sure because it is a sparsed image) or by flashify ?
ODIN:
Recovery must be converted to .tar first, http://forum.xda-developers.com/showthread.php?t=2281287&page=5, http://forum.xda-developers.com/showpost.php?p=45629177&postcount=1) what Variant will work for W7,8.1.
One suggest file format for tar = ustar and the other one gnu ... waht is right for Odin ?
and how to under Linux ?
- I tried Odin with the help of the attached files ... seems to work ? How can the .img>tar conversion be done under Linux ?
- what about dd (must the stock.img be processed before in any ways (beacause ist sparsed) ?
- also flashify seems to work
- what about dd - must the stock.img be processed before in any ways (because ist sparsed) ? In any case it's smaller than a backup from Flashify or dd ...
In my case (Tab S, SM-T705) the partition has 10240 blocks. I did a dd from the partition and this file contains $1000000 Bytes. File size is 10MB = 10485760 Bytes.
Is the only way to fill every Byte from the end of the stock recovery with 00 by a hex editor ?
Would be super nice to get commands for Windows and Linux.
Hello guy, i have a S3 SCH-R530C hard bricked(pls don't ask me how i hard bricked it!).
A guy from xda sent me a tutorial how to unbrick it without JTAG(Will post the tut at the end), but when i download the package the sbl1.mbn is missing.
Does anyone have it ?
Or maybe you have a better tutorial for debrick ? Anything will help. Thank you
Copy past tutorial, all credits goes to "robbiejobs"
First part:
You'll need these files :
1.) R530U debrick img https://app.box.com/SCH-R530U
2.) R530C stock image ( I guess the version doesn't matter, but you better try with 4.3 first ) http://terafile.co/88b027e65750/R530...RICMK3_CRI.zip
---
Extract R530CVVUCMK3_R530CCRICMK3_CRI.zip you'll get some .tar.md5 file, extract that file too and then grab these files
sbl1.mbn
sbl2.mbn
sbl3.mbn
aboot.mbn
rpm.mbn
tz.mbn
Second part:
I've waited for almost 2 years to have R530C debrick image, no one have that file. I almost give up, and then my stupid idea came up... ( You'll need linux terminal, and basic linux command knowledge )
1.) Download odin package for your device ( make sure it's the same version with your latest firmware before got bricked )
2.) Extract the .tar.md5 file ( WinRar / 7zip will give error message, just ignore it )
3.) Grab debrick image for your device, or at least the same variant ( R530C / U / M ) firmware version doesn't matter.
4.) Clone the debrick image to your microSD card.
5.) Now back to extracted folder of your firmware, copy these files :
sbl1.mbn
sbl2.mbn
sbl3.mbn
aboot.mbn
rpm.mbn
tz.mbn
to your working directory
6.) List your debrick microSD partition using parted ( mine was /dev/sdb, make sure you have the right partition before doing these commands )
I forgot the command, but it's something like
Code:
parted /dev/sdb
Code:
(parted) print
7.) Now you can see the partition list (sbl1,sbl2,etc)
8.) And then do this :
sudo dd if=sbl1.mbn of=/dev/sdbX
sudo dd if=sbl2.mbn of=/dev/sdbX
sudo dd if=sbl3.mbn of=/dev/sdbX
sudo dd if=aboot.mbn of=/dev/sdbX
sudo dd if=rpm.mbn of=/dev/sdbX
sudo dd if=tz.mbn of=/dev/sdbX
9.) After finishing all the command, remove your microSD from card reader, cross finger.. and Good Luck.
Sorry for my "not-so-easy" tutorial, I wish I could explain it a little easier to understand.. but my english sucks
This forum is for the GSM/LTE version of the s3. Try posting your question here: http://forum.xda-developers.com/galaxy-s3-verizon
audit13 said:
This forum is for the GSM/LTE version of the s3. Try posting your question here: http://forum.xda-developers.com/galaxy-s3-verizon
Click to expand...
Click to collapse
I was not sure where to post it, since there is no cricket , but thank you.