I'm coming from a Sprint GSII where the kernal and recovery are on the same partition, which was very confusing when flashing ROM's and it would overwrite the recovery.
Is the recovery on a partition all by itself on this phone?
spencer88 said:
I'm coming from a Sprint GSII where the kernal and recovery are on the same partition, which was very confusing when flashing ROM's and it would overwrite the recovery.
Is the recovery on a partition all by itself on this phone?
Click to expand...
Click to collapse
Yes, and most Android devices follow the Android standard by making the recovery partition and the boot kernel partitions separate.
Not sure why the GSII still used that design as I first saw it used on the Samsung Moment, 2 yrs ago and it was very frustrating to deal with as a developer and user.
Hopefully Samsung stays away from that poor model and follows the Android standard other manufacturers such as HTC and Google devices such as the Nexus S and Galaxy Nexus use.
Hope that helps!
joeykrim said:
Yes, and most Android devices follow the Android standard by making the recovery partition and the boot kernel partitions separate.
Not sure why the GSII still used that design as I first saw it used on the Samsung Moment, 2 yrs ago and it was very frustrating to deal with as a developer and user.
Hopefully Samsung stays away from that poor model and follows the Android standard other manufacturers such as HTC and Google devices such as the Nexus S and Galaxy Nexus use.
Hope that helps!
Click to expand...
Click to collapse
Thanks for the reply and the clarification. Yeah coming from the EVO and the EVO 3D, that confused the hell out of me when I first went to flashing things. It was so weird I just stopped flashing things and just went to a stock, rooted ROM. Such a poor setup for such an amazing piece of hardware. I'm glad to know that this phone is set up properly.
Related
DONT ANY ONE ATTEMPT TO FLASH ANYTHING TALKED IN THIS THREAD IT WILL MESS UP UR PHONE only trying to pass info.....I know the thread isn't titled properly, that's because I wanted everyone to look at this post. I know we all want root. So I was looking in the Sprint gs3 section and noobnl of team epic, I believe has achieved root. now he says it's buggy.Now I posted in that thread they said we need the tar file for our phone. I don't have the device, here's the thread (2 of them)http://forum.xda-developers.com/showthread.php?t=1725395 http://forum.xda-developers.com/showthread.php?t=1726088
Youtube post showing how to dump firmware http://www.youtube.com/watch?v=UWs6PKnDtFk Adb commands used:
1.To dump system
dd if=/dev/block/stl6 of=/sdcard/factoryfs.rfs
2.To mount system in rw mode
mount -o remount,rw /dev/block/stl9 /system
or
mount -o remount,rw /dev/block/stl6 /system
guide to unpack http://www.haskell.org/haskellwiki/How_to_unpack_a_tar_file_in_windows
stock boot.img from sprint is compatible with t-mobile
If you (like me) bricked your perfectly working phone by flashing an international boot image. The stock boot.img file from the Sprint version: http://forum.xda-developers.com/showthread.php?t=1726088&page=3 works to bring it back from the dead.
All I can say is that next time I'm going to patiently wait for a complete root. I had a couple of panicked hours there.
I'm uploading a system dump of the t-mobile galaxy s3 for some one to find what they need for root. Should be done in 30 minutes.
thing12 said:
If you (like me) bricked your perfectly working phone by flashing an international boot image. The stock boot.img file from the Sprint version: http://forum.xda-developers.com/showthread.php?t=1726088&page=3 works to bring it back from the dead.
All I can say is that next time I'm going to patiently wait for a complete root. I had a couple of panicked hours there.
Click to expand...
Click to collapse
I'm looking in to this now to see if we can use this to flash our own recovery.
Here's the link to a system dump for t-Mobile's s3.
https://www.dropbox.com/s/uvtlbwh88zgrnyk/system dump.rar
I did a adb system pull to get this.
If you don't know what your doing with this i suggest not flashing anything to you phone or it might be bricked. It is for Dev's who don't have the phone yet to use.
sswb27 said:
Here's the link to a system dump for t-Mobile's s3.
https://www.dropbox.com/s/uvtlbwh88zgrnyk/system dump.rar
I did a adb system pull to get this.
If you don't know what your doing with this i suggest not flashing anything to you phone or it might be bricked. It is for Dev's who don't have the phone yet to use.
Click to expand...
Click to collapse
please create a new thread for this, i was trying to do the same but you beat me to it
AT&T, T-MOBILE, SPRINT, VERIZON have the same models and processor, s4 i figure the only different between all these 4 carriers is their radio, why wouldnt a rom from the gs3 from sprint work on tmobile gs3 and vise versa? if we can keep the same radio and kernel it should be fine. as on rooting method and recoveries
i understand if the hardware was different but we have the same chip and hardware in this case
gypsy214 said:
AT&T, T-MOBILE, SPRINT, VERIZON have the same models and processor, s4 i figure the only different between all these 4 carriers is their radio, why wouldnt a rom from the gs3 from sprint work on tmobile gs3 and vise versa? if we can keep the same radio and kernel it should be fine. as on rooting method and recoveries
i understand if the hardware was different but we have the same chip and hardware in this case
Click to expand...
Click to collapse
Well I'm new to samsung phones but my hunch would be they have different boot loaders. But I'm not sure if that would have any thing to do with it since the boot loader is unlocked.
View the development thread.
We have root!!
sswb27 said:
Well I'm new to samsung phones but my hunch would be they have different boot loaders. But I'm not sure if that would have any thing to do with it since the boot loader is unlocked.
Click to expand...
Click to collapse
Is kinda like the HTC sensation 4G (tmobile us) HTC sensation XE (international with beats) and the HTC sensation (international) same phone same hardware same processor different clocked and all roms works rooting method works and all the goods in development. as long you have the proper radio you were fine. in this case all us version are the same not the international one witch have the samsung exynos quadcore thats a hardware different there. In any case i might be wrong. as i see each of the us sgs3 have its own thread stead of a single one
i know this is stupid to ask as, they dont mean anything. Do you guys think you guys could throw me a bone, for bring this method to our attention if not its nbd. Ill catch em down the road ill be here a while
Boot image?
thing12 said:
If you (like me) bricked your perfectly working phone by flashing an international boot image. The stock boot.img file from the Sprint version: http://forum.xda-developers.com/showthread.php?t=1726088&page=3 works to bring it back from the dead.
All I can say is that next time I'm going to patiently wait for a complete root. I had a couple of panicked hours there.
Click to expand...
Click to collapse
Can you post the image you used or instructions on what you did? I have downloaded the boot.img from the Sprint thread but getting it loaded is a mystery. Thank you
thank you for the TMo firmware, it may come in handy
Hello, all i am quite new here. I have a kindle that i have successfully moded to ICS but i am having difficulty trying to load a different recovery option for the evo 4g
it is fully rooted, however when i attempt to go into the boot loaded, it just asks me if i want to update the PC36IMG-ENG.zip and not install it any idea on what im doing wrong here? just trying to load ics on here
thanks!
gbdavidx said:
Hello, all i am quite new here. I have a kindle that i have successfully moded to ICS but i am having difficulty trying to load a different recovery option for the evo 4g
it is fully rooted, however when i attempt to go into the boot loaded, it just asks me if i want to update the PC36IMG-ENG.zip and not install it any idea on what im doing wrong here? just trying to load ics on here
thanks!
Click to expand...
Click to collapse
What recovery are you trying to install? the -eng is unfamiliar to me.
gbdavidx said:
Hello, all i am quite new here. I have a kindle that i have successfully moded to ICS but i am having difficulty trying to load a different recovery option for the evo 4g
it is fully rooted, however when i attempt to go into the boot loaded, it just asks me if i want to update the PC36IMG-ENG.zip and not install it any idea on what im doing wrong here? just trying to load ics on here
thanks!
Click to expand...
Click to collapse
Did you press volume up to confirm the update?
Just make sure you rename the recovery file to PC36IMG.zip, put it on the root of your SD card, boot into bootloader, them press volume up to accept the update.
Hope this helped!
Sent from my Rooted Google Nexus 7 using XDA Premium HD
What is that "-eng" at the end of the op's PC36IMG? I've never seen that?!
It means English...no seriously it means English
You must mean unlocked. If you had rooted, you would already have a custom recovery because you flash from custom recovery to root
om4 said:
It means English...no seriously it means English
Click to expand...
Click to collapse
hmmm...I have never seen that, I was thinking perhaps it meant Engineering, as in hboot eng blah blah blah.
I learned something new today!
But---English??!! English what tho?
Some updates are regional, it happens but I've never seen it on with HTC. I've mostly seen it with Huawei and a few international phones that are for a specific region, think of it as a language pack on windows
gbdavidx you should read my guide Don't Panic, it has all the info you need. The link is in my sig
om4 said:
Some updates are regional, it happens but I've never seen it on with HTC. I've mostly seen it with Huawei and A few international phones that are for a specific region, think of it as a language pack on windows
Click to expand...
Click to collapse
Good to know...I just wonder what recovery the op is trying to install? I thought all recoveries installed via hboot just had to be renamed PC36IMG.zip...whether it be Amon, Smelkus etc....
Thanks for the answer tho!:good:
om4 said:
Some updates are regional, it happens but I've never seen it on with HTC.
Click to expand...
Click to collapse
Scratch that, I saw it once with my sister's GSM Evo 3D. When I told her I had never seen that before she was pretty pissed
om4 said:
Scratch that, I saw it once with my sister's GSM Evo 3D. When I told her I had never seen that before she was pretty pissed
Click to expand...
Click to collapse
And I just looked at your "Don't Panic" link...that is AWESOME info...I'll read more tomorrow...VERY informative...that should be stickied in this forum also (saw it was in the Evo LTE forum, but most, if not all applies to the OG Evo eh?):good::good::good: I bookmarked it!
Yeah it does, HTC has pretty much the same boot loader for these phones just different variations. I'm so tired I clicked into the wrong forums lol
om4 said:
Yeah it does, HTC has pretty much the same boot loader for these phones just different variations. I'm so tired I clicked into the wrong forums lol
Click to expand...
Click to collapse
Well, your tiredness led to me being more informed and I appreciate it...(btw the last couple sentences in that guide---HI-LARIOUS!)
Now, go to bed:silly:
I left to computer to hit the head and my gf added those last 2, I went ahead and left then there. She's absolutely brilliant!
Edit: I've been out of the game for about a year and a half but most of the relevant knowledge is there in regards to HTC Unlock method. It was originally more of a universal guide. I started aiming it towards LTE users since thats what I have now. You guys are free to take my guide and tailor it to the Evo 4G. I would love to do it myself, but like I said I've been out for a year and a half and trying to play catch up with a device I no longer even own will be very frustrating lol
Edit: the fact that I can even write a guide that applies to such a broad range like htc is because understanding the theory helps. Half of that guide could easily apply to Motorola, Samsung, lg. But like I said I began to aim it towards the EVOLTE
I've been looking for info about Sprints latest stock ROM but according to most of the info I've found I should still be on JRN84D but I'm on JRO03U. Since the update I lost my root but the boot loader is still unlocked. I've also lost Touchwiz but sounds like I need to go the CWM route anyhow.
Most of the stuff I find on here seems to be referencing Toroplus so I don't want to start adding a recovery that is incompatable or bricking it trying to root with the wrong files. I've also read many times that using the VZW files is a big no no but they are the only ones supporting my build. So any links or info where I can find the info I need would be greatly appreciated. Whats a boy to do?
This is the info you should have with latest rom
Sent from my Galaxy Nexus using xda app-developers app
You lost touchwiz? This isn't a mainstream galaxy phone....
Sent From My Toro+ via White Tapatalk
^^ Yea no Galaxy Nexus variants come with Touchwiz at all. I vaguely remember reading about an effort to bring it over but if I remember correctly it was pretty buggy. So unless you're running that specific custom ROM (and you would definitely know if you were), you never had Touchwiz on this phone.
Definitely don't download any Verizon ROMs or radios. That could brick you. You want "toroplus" builds. That's the sprint variant.
Maybe it wasn't touchwiz. Trying to remember but it was an alternate recovery to CWM that utilized the touchscreen. At any rate I'm back to the stock recovery that is completely useless giving me a droid with a red danger triangle above it.
gagb1967, that is exactly what my build version is. Thats why I'm hesitant to use any of the toroplus files because I know its a mysid build. I've been spending way too much time with my desktop and overclocking because I've forgotten most things about how to mess with my phone. Then again this GNex really doesn't need NEARLY as much alterations as the old Charge and Touch Pro 2 did LOL.
revwolf said:
Maybe it wasn't touchwiz. Trying to remember but it was an alternate recovery to CWM that utilized the touchscreen. At any rate I'm back to the stock recovery that is completely useless giving me a droid with a red danger triangle above it.
Click to expand...
Click to collapse
That's the stock recovery. It's not meant to offer you the same functionality as a custom recovery like TWRP or CWM.
that is exactly what my build version is. Thats why I'm hesitant to use any of the toroplus files because I know its a mysid build. I've been spending way too much time with my desktop and overclocking because I've forgotten most things about how to mess with my phone. Then again this GNex really doesn't need NEARLY as much alterations as the old Charge and Touch Pro 2 did LOL.
Click to expand...
Click to collapse
You have a Sprint model, you can only use Toroplus files.
martonikaj said:
That's the stock recovery. It's not meant to offer you the same functionality as a custom recovery like TWRP or CWM.
You have a Sprint model, you can only use Toroplus files.
Click to expand...
Click to collapse
Thanks all. Back to my good ole rooted stock phone. I can understand using ROM's on other phones because stock interfaces are usually so atrocious but I have yet to find anything wrong with Jelly bean that can't be fixed with an app. Yeah I'm strange LOL. Anyhow thanks again.
I wanted to start a discussion about one thing that I see as a drawback to Samsung development. I'd love to hear peoples thoughts about it and what their experience was on previous Galaxy devices.
I just got this incredible beast of a phone last Tuesday...and....I LOVE it.
This is my first Sammy device, coming from all HTC phones for the last several years. One major thing that has concerned me is the lack of cohesive development, simply due to the fact that Samsung releases so many variants of the GS4 (or do they?).
The one main thing HTC has going for them in regards to phones & development, is that there is usually only one main forum for all your needs. For instance, my old Sensation...all you have to do is SuperCID & have S-OFF and you can flash any ROM you want, regardless of carrier etc. Even though there were several varieties of the Sensation (XE etc), if you had SuperCID...your ROM options were endless. Look no further than the development forum for the One...quite frankly, it is incredible the amount of custom stuff that is available in that forum. Even before the phone was widely released, there were about 2 dozen of XDA's great devs, modders, themers, already pumping out ROM's & Kernels & Mods etc etc. All this with very little confusion or fuss on how to root and or what you can or can't flash etc.
I wish it were as simply as that for us. I can only imagine how amazing development would be for the S4, if it wasn't split up into 4-5 different forums.
Lastly...I would love to know if it will ever be possible to flash anything that's for the I9505 (for instance the ROM from Indie). If the GS4 can have SuperCID, or something similar...why would this not be possible?? Of course we've all heard that we should NEVER flash anything that's not specific to our Tmo GS4...and leaves me wondering just how involved development will be for the Tmo GS4. My question would be why is that not possible if the hardware is the same....regardless of carrier? What are the restrictions to flashing anything I9505 related...and will it ever be possible? Is there an actually hardware difference in the German Tmo I9505 and the US Tmo I9505??
I simply look at it from a perspective of less devs in one spot, means less development for each variant...and that kinda bums me out a bit.
Love to hear what you guys think about this...
Cheers! :good:
Blame the US carriers for split forums.
-Sent from my Samsung Galaxy Note II using Tapatalk 2
Hoggles said:
Love to hear what you guys think about this...
Cheers! :good:
Click to expand...
Click to collapse
The T-Mobile version is not the i9505, it is he M919. The i9505 is subtly different and is the only model of the GS4 to contain an FM radio.
The fragmentation is due in part to what the previous poster noted; us carriers; and LTE. The Sensation was not ever released on CDMA networks, it was GSM only and all models had the same hardware, including the actual radios. This is why the development was in one section, because all the devices were the same hardware, with only slight software differences depending on region/carrier.
The i9500 is the technological dream of the masterminds at Samsung flexing their muscles as a super power. The vast majority of the components are made directly by them including the revolutionary CPU and screen. I cannot think of any other company that does this. The entry model on these units is rarely catered to the us market (think original GS2, GS3, original Note) and usually sees a second generation to add support for CDMA and or LTE (Think carrier branded GS2, GS3, Note).
The I9505 & Carrier branded versions utilize a different SoC to accommodate for global demand. Most qualcomm chips these days are being mass produced and have LTE/CDMA worked out in their design initially. I makes it easy for sammy to push out more units in a quicker amount of time.
Hoggles said:
I wanted to start a discussion about one thing that I see as a drawback to Samsung development. I'd love to hear peoples thoughts about it and what their experience was on previous Galaxy devices.
I just got this incredible beast of a phone last Tuesday...and....I LOVE it.
This is my first Sammy device, coming from all HTC phones for the last several years. One major thing that has concerned me is the lack of cohesive development, simply due to the fact that Samsung releases so many variants of the GS4 (or do they?).
The one main thing HTC has going for them in regards to phones & development, is that there is usually only one main forum for all your needs. For instance, my old Sensation...all you have to do is SuperCID & have S-OFF and you can flash any ROM you want, regardless of carrier etc. Even though there were several varieties of the Sensation (XE etc), if you had SuperCID...your ROM options were endless. Look no further than the development forum for the One...quite frankly, it is incredible the amount of custom stuff that is available in that forum. Even before the phone was widely released, there were about 2 dozen of XDA's great devs, modders, themers, already pumping out ROM's & Kernels & Mods etc etc. All this with very little confusion or fuss on how to root and or what you can or can't flash etc.
I wish it were as simply as that for us. I can only imagine how amazing development would be for the S4, if it wasn't split up into 4-5 different forums.
Lastly...I would love to know if it will ever be possible to flash anything that's for the I9505 (for instance the ROM from Indie). If the GS4 can have SuperCID, or something similar...why would this not be possible?? Of course we've all heard that we should NEVER flash anything that's not specific to our Tmo GS4...and leaves me wondering just how involved development will be for the Tmo GS4. My question would be why is that not possible if the hardware is the same....regardless of carrier? What are the restrictions to flashing anything I9505 related...and will it ever be possible? Is there an actually hardware difference in the German Tmo I9505 and the US Tmo I9505??
I simply look at it from a perspective of less devs in one spot, means less development for each variant...and that kinda bums me out a bit.
Love to hear what you guys think about this...
Cheers! :good:
Click to expand...
Click to collapse
You're spot on. I had the HTC Sensation as well. I currently have the HTC One. I can def say that HTC retains the crown when it comes to consumer development. They even launched a website to unlock your device in response to so many requests for it.
What has Samsung done? Well, most recently they pushed an update that locked out root at the kernel level. Boo!
From what I've seen thus far (and yes I know it's still early) there has been a very weak response in the dev department for the T-Mobile variant of this device. It has been out for a couple of weeks now and we still don't have a PIT file posted anywhere. So if anyone hit a worst case scenario, they would be unable to fully wipe their phone and use an ODIN tar to return to stock. On that note, we don't even have a virgin untouched tar of the stock firmware (MDL that has tweaked kernel) for ODIN. A couple of the deodexed and zip-aligned flashable packages that were posted have slight changes made to them - we NEED untouched flashable zips. Don't post something as "stock" if you have modified the firmware.
All in all, we have had a very rocky start on this T-Mobile variant. I'm contemplating buying the device for a couple of the old Team Whiskey guys and starting our own team for this. There is a lot of work to be done, yet. And this device has a lot of potential.
Some of you may be offended by this and some of you may be rolling your eyes. That's fine. But these are my two cents.
On a brighter note... I'm hoping for a massive response once source drops.
luckyduck69 said:
You're spot on. I had the HTC Sensation as well. I currently have the HTC One. I can def say that HTC retains the crown when it comes to consumer development. They even launched a website to unlock your device in response to so many requests for it.
What has Samsung done? Well, most recently they pushed an update that locked out root at the kernel level. Boo!
From what I've seen thus far (and yes I know it's still early) there has been a very weak response in the dev department for the T-Mobile variant of this device. It has been out for a couple of weeks now and we still don't have a PIT file posted anywhere. So if anyone hit a worst case scenario, they would be unable to fully wipe their phone and use an ODIN tar to return to stock. On that note, we don't even have a virgin untouched tar of the stock firmware (MDL that has tweaked kernel) for ODIN. A couple of the deodexed and zip-aligned flashable packages that were posted have slight changes made to them - we NEED untouched flashable zips. Don't post something as "stock" if you have modified the firmware.
All in all, we have had a very rocky start on this T-Mobile variant. I'm contemplating buying the device for a couple of the old Team Whiskey guys and starting our own team for this. There is a lot of work to be done, yet. And this device has a lot of potential.
Some of you may be offended by this and some of you may be rolling your eyes. That's fine. But these are my two cents.
On a brighter note... I'm hoping for a massive response once source drops.
Click to expand...
Click to collapse
Wrong. There is already stock ODIN files on here and sammible. You do not need a .pit to flash an MD5 and the T-Mo Note 2 didn't have one either in the dev sections. Yes Samsung has included a new revision in their kernel to lock out root access, big deal. We are a group of developers here dedicated to outsmarting the man and doing things our own way. The i9500 already has the newest kernel built from source with the 1 flag (yes, it's one flag) circumvented. HTC doen't even have an official RUU available yet, and their HTC dev site records your IMEI to refuse you warranty service lol. I would suggest you read up some more before offering up your two cents, because based on what you stated they are without warrant, and worthless.
Here's a link to the stock ODIN file since you missed it, http://www.hotfile.com/dl/213469534/9ff06bd/M919UVUAMDL_M919TMBAMDL_TMB.zip.html
KillaHurtz said:
Wrong. There is already stock ODIN files on here and sammible. You do not need a .pit to flash an MD5 and the T-Mo Note 2 didn't have one either in the dev sections. Yes Samsung has included a new revision in their kernel to lock out root access, big deal. We are a group of developers here dedicated to outsmarting the man and doing things our own way. The i9500 already has the newest kernel built from source with the 1 flag (yes, it's one flag) circumvented. HTC doen't even have an official RUU available yet, and their HTC dev site records your IMEI to refuse you warranty service lol. I would suggest you read up some more before offering up your two cents, because based on what you stated they are without warrant, and worthless.
Here's a link to the stock ODIN file since you missed it, http://www.hotfile.com/dl/213469534/9ff06bd/M919UVUAMDL_M919TMBAMDL_TMB.zip.html
Click to expand...
Click to collapse
No... I don't think you understand.
Of course you don't "need" a PIT file. But do you understand what that is used for? I encourage you to try this.
1. Run the latest update. The virgin, str8 from kies, MDL update. You'll have the root-block kernel and everything.
2. Now try to ODIN back to the previous firmware using THIS MDB tar file.
I think you will find you are unable to successfully return to the fully stock MDB firmware. That tar file alone will not wipe anything. It will seem to flash via ODIN. But once you reboot... you'll still have your MDL firmware installed (sorta). You might suggest installing CWM or TWRP Recovery here. Well... you can try. I did. You will run into some interesting issues. LIke not being able to get into ANY recovery until you perform a full reset from within the system settings menu. Then suddenly finding your way into the stock android recovery. At which point you'll do a factory reset/wipe from the stock android recovery. Then you WILL be able to install CWM Recovery and flash... oh wait. There is no completely stock flashable firmware package. Those we do have are found HERE and have had things removed.
I'll give you another example. Let's say you soft brick your phone. You need to do a restore via ODIN. But you also need to wipe it completely. What are you going to do? You can't get to recovery. Can't load the system. You need to do a full wipe and factory restore. How are you doing to do that without the Partition Information Table and ODIN?
As for warranty... technically we're all void of warranty so why does it matter? We all void the warranty as soon as we start flashing. That is why all the devs put that disclaimer in their OPs.
Furthermore, while its kinda cool that you went straight into defensive mode, I wasn't bashing anyone. I'm just saying we need to pick it up and get the right files out there for the ppl who don't know how to fix things on their own and so forth. If I need to I'll take one of my computers off of Folding and turn it into a dev box so I can help out.
Love, Peace, and Chicken Grease :good:
All you need is the ODIN file I provided (MDL). After that you can enter the stock recovery and wipe the data as needed.
If you are completely bricked (cannot enter download mode) Samsung will warranty the phone for a new one.
It's not defensive that I am being. I could careless if you brick your phone lol, I am only providing facts that you seemed to miss.
The .pit file is usually used if you have borked the phone from all recognition and need to tell the device what to flash where as it sets the maps for the partitions.
Your original post said nothing of having to wipe or anything else you just disclosed which is still incorrect to an extent.
We all know that stock ODIN files do not wipe data, but with the files I posted you will not need to go back to a lower firmware in the 1st place and will not be locked out of the system or recovery....
If you are concerned with a stock .pit file, make one from Heimdall. Or, are you one of the ones "who don't know how to fix things on their own" ?
KillaHurtz said:
All you need is the ODIN file I provided (MDL). After that you can enter the stock recovery and wipe the data as needed.
If you are completely bricked (cannot enter download mode) Samsung will warranty the phone for a new one.
It's not defensive that I am being. I could careless if you brick your phone lol, I am only providing facts that you seemed to miss.
The .pit file is usually used if you have borked the phone from all recognition and need to tell the device what to flash where as it sets the maps for the partitions.
Your original post said nothing of having to wipe or anything else you just disclosed which is still incorrect to an extent.
We all know that stock ODIN files do not wipe data, but with the files I posted you will not need to go back to a lower firmware in the 1st place and will not be locked out of the system or recovery....
If you are concerned with a stock .pit file, make one from Heimdall. Or, are you one of the ones "who don't know how to fix things on their own" ?
Click to expand...
Click to collapse
Nah. Benji was cleaning up the code last night. But he did tell me that Heimdall 1.4 will be officially released in a few hours. And that he confirmed it working on his Sprint S4. Previous versions wont detect our snapdragon device.
As for your MDL ODIN file, you're still missing the point. But im going to drop it.
Sent from my S4 using Tapatalk 2
Now I'm a seasoned user I'm I'm blown away by the fact rooting and unlocking the boot loader required no computer and only took two minutes! This is my first nexus device and I was wondering, can I only use stuff from the LTE section or could I use kernels for the regular nexus 7? Don't want to make a noon mistake
@non4 said:
Now I'm a seasoned user I'm I'm blown away by the fact rooting and unlocking the boot loader required no computer and only took two minutes! This is my first nexus device and I was wondering, can I only use stuff from the LTE section or could I use kernels for the regular nexus 7? Don't want to make a noon mistake
Click to expand...
Click to collapse
You have to use roms and kernels built for the LTE model(deb)
jram0421 said:
You have to use roms and kernels built for the LTE model(deb)
Click to expand...
Click to collapse
Thought so cheers