Related
ROM for recovery G2X under the NVFLASH
This method necessary!
If the device is not loaded and not firmware in other ways! (If you downloaded the wrong firmware in the device)
I took the unpacked program files KDZ and added to them NVFlash and created BAT file!
Download ROM: http://www.mediafire.com/?wfokxjxi7rfoaey
Mirror: http://www.megaupload.com/?d=C5LBU3DS
Download APX driver: http://www.mediafire.com/?k559zgjlqkd5ted
Installation Instructions:
Download both files
Unpack it to the C drive to their respective folder
Remove the battery
Hold Vol Up/Down (and keep them held)
Insert the USB cable
Install APX driver from the your APX folder
For windows 7(and vista? please confirm):
Open Device Manager in Windows and you should see "APX Device" listed with an error
Right click on the APX device
Select 'Update driver software'
Select 'Let me pick...'
Select 'Have disk'
Browse to directory you extracted the APX Driver
Select the *entire* 'APX Driver' folder
Accept any warnings, including the big red alert (you may need to disable UAC)
Now in Device Manager under 'USB Controllers' you should have an 'NVIDIA USB Boot-recovery driver for mobile devices'
If not, uninstall the driver, reboot, rinse and repeat
Unplug everything
Hold Vol Up/Down (and keep them held)
Insert USB cable
open your ROM folder:
Run Flash.bat file and wait for the process
After the logo appears on the LG phone
Unplug USB cable
Insert the battery
enjoy!
After that, I recommend to firmware device with help programms KDZ or LG Mobile Update
I'm confused as to what this is? I'm guessing stock rom flash through nv flash? Kind of like odin for samsung phones?
Sent from my LG-P999 using XDA App
Can't wait to check this out when I get home later. Regarding the kdz file, what exactly were you able to unpack from it? I've been able to extract 2 files (a very large .wbd file and a .dll file) but I couldn't figure out how to unpack them further, specifically the .wdb file.
ILUHA_89 said:
I took the unpacked program files KDZ and added to them NVFlash and created BAT file!
Click to expand...
Click to collapse
Can you post the DLL for the G2X so we can use the LG Utilities to unpack KDZ files for this device please. So far we have been unable to get the proper DLL that enables us to unpack these files. If you unpacked the KDZ you must have the DLL unless you used another method to extract the files from the KDZ. Please elaborate on how you accomplished this. Both phburks and I have been working on this and so far we have had no success.
Smallsmx3 said:
I'm confused as to what this is? I'm guessing stock rom flash through nv flash? Kind of like odin for samsung phones?
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
It is for people that have mucked up their phones to the point where LG Updater and KDZ Flash are not possible. This can be caused by many issues including, but not limited to, people flashing the O2X baseband to a G2X device. This method is purported to flash the entire Gingerbread ROM at the lowest possible hardware level. Hopefully this method is legit, but nobody has confirmed they have done it yet with the exception of the OP. Yes it is similar to ODIN for the Samsung but operating at an even lower level. With the NVFlash capability Tegra2 devices are virtually unbrickable.
jboxer said:
Can you post the DLL for the G2X so we can use the LG Utilities to unpack KDZ files for this device please. So far we have been unable to get the proper DLL that enables us to unpack these files. If you unpacked the KDZ you must have the DLL unless you used another method to extract the files from the KDZ. Please elaborate on how you accomplished this. Both phburks and I have been working on this and so far we have had no success.
It is for people that have mucked up their phones to the point where LG Updater and KDZ Flash are not possible. This can be caused by many issues including, but not limited to, people flashing the O2X baseband to a G2X device. This method is purported to flash the entire Gingerbread ROM at the lowest possible hardware level. Hopefully this method is legit, but nobody has confirmed they have done it yet with the exception of the OP. Yes it is similar to ODIN for the Samsung but operating at an even lower level. With the NVFlash capability Tegra2 devices are virtually unbrickable.
Click to expand...
Click to collapse
You described it right!
This method has helped resurrect my device!
ZeroT| Demented said:
So the point of this utility if it works is to make the g2x un f***able like even if u do u can fix?
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Yes. It is almost as good as JTAG flashing the device. For Galaxy S devices using ODIN you still have to have the 'software download' mode working in the ROM and it is possible to brick a Galaxy S beyond the point of even getting this mode to be accessible leaving you the only way to fix the device through disassembling it and flashing via the JTAG pads. Using the NVFlash method you are flashing directly to the hardware through they Hynix flashing chip. I had another phone with a similar capability (I-Mobile i858 - Yuhua Touchstone device) and no matter how badly I F'd it up (I was developing custom roms for it) I had the similar low level flashing tool that could reflash the phone to stock so I could start over with a clean slate. If this method is legit, this is a big boon to the dev community for this device.
jboxer said:
Can you post the DLL for the G2X so we can use the LG Utilities to unpack KDZ files for this device please. So far we have been unable to get the proper DLL that enables us to unpack these files. If you unpacked the KDZ you must have the DLL unless you used another method to extract the files from the KDZ. Please elaborate on how you accomplished this. Both phburks and I have been working on this and so far we have had no success.
It is for people that have mucked up their phones to the point where LG Updater and KDZ Flash are not possible. This can be caused by many issues including, but not limited to, people flashing the O2X baseband to a G2X device. This method is purported to flash the entire Gingerbread ROM at the lowest possible hardware level. Hopefully this method is legit, but nobody has confirmed they have done it yet with the exception of the OP. Yes it is similar to ODIN for the Samsung but operating at an even lower level. With the NVFlash capability Tegra2 devices are virtually unbrickable.
Click to expand...
Click to collapse
After trying to firmware device with program KDZ or LG Mobile Update in folder C: \ ... \ Aplication Data \ folder appears "LGMOBILEAX" which contains the firmware files!
That's All
ILUHA_89 said:
After trying to firmware device with program KDZ in folder C: \ ... \ Aplication Data \ folder appears "LGMOBILEAX" which contains the firmware files!
That's All
Click to expand...
Click to collapse
So you got them after the LG Updater extracted the KDZ into its component files. phburks and I didn't get that far as we didn't want to connect our already updated devices to the updater. To get to the point you did where you could grab the individual files you would have had to click the start update button. Good work.
I have 7-zip on my computer but I am unable to open up the file I just downloaded. Can you put it in another format and upload to megaupload or mediafire please? I don't want to go through that Russian site again as I got an invalid download. Also, please post the baseband file as a separate download.
jboxer said:
So you got them after the LG Updater extracted the KDZ into its component files. phburks and I didn't get that far as we didn't want to connect our already updated devices to the updater. To get to the point you did where you could grab the individual files you would have had to click the start update button. Good work.
I have 7-zip on my computer but I am unable to open up the file I just downloaded. Can you put it in another format and upload to megaupload or mediafire please? I don't want to go through that Russian site again as I got an invalid download. Also, please post the baseband file as a separate download.
Click to expand...
Click to collapse
I downloaded the 7-zip file to the sdcard on my phone but I won't be home to try opening it for several hours because I'm at seaworld. Lol
Hopefully you guys can get this sorted out. Sounds promising so far.
phburks said:
I downloaded the 7-zip file to the sdcard on my phone but I won't be home to try opening it for several hours because I'm at seaworld. Lol
Hopefully you guys can get this sorted out. Sounds promising so far.
Click to expand...
Click to collapse
I won't be able to look at it until tomorrow as it is 11:31 p.m. here and time to go to bed. :-O ZZZzzzzz
How about posting a mirror???? the site will not let me download.... unless i visit a sponsor and purchase something... lol
i'll try it out and report back
........... Works like a charm
here mirror link
http://www.megaupload.com/?d=C5LBU3DS
What we really need is for someone to tell us how to create the config files for NVFlash so we can flash the baseband only. The new baseband is there and named 'P999_MDM.bin' if I am remembering correctly. No reason to flash an entire ROM when all someone wants is the updated baseband. If we can get the older baseband file also this tool could be used to revert the baseband also, if someone wanted to do that.
web_ninja said:
How about posting a mirror???? the site will not let me download.... unless i visit a sponsor and purchase something... lol
Click to expand...
Click to collapse
You don't have to buy anything. You just click on one sponsor site and it opens a new window. Thirty seconds later it will enable a download link. You need to click download two or three times if I remember correctly. I am at work now. I can mirror it in about ten hours if nobody else has done it yet. I looked at the files briefly and it looks legit.
Is this supposed to have a command interface? Or are you still typing in commands yourself?
I edited a cap!
Changed link to Mediafire
omarsalmin said:
Is this supposed to have a command interface? Or are you still typing in commands yourself?
Click to expand...
Click to collapse
Good question - that is what I am looking for rather then having to mess with the nvflash commands directly.
Update - this setup is similar to Paul's stock ROM recovery setup on modeco.com. As with his, you only have to "Run Flash.bat file and wait for the process". When I could not get off of the LGupdater screen by any other means, I ran this file from his post and it ran flawlessly - but of course I ended up with a 990's device. I tried to get back with other tools and firmware, but was never able to do it.
If this works OK, you would be able to restore your data, apps, or a nandroid and you are back in business.
I spent a week trying to restore my original (and best device as it turns out), so I am not going to fool with this right now myself. I did compare the config files from bot Paul's and this firmware and they are different - which looks real promising, as they are different.
HELP! I tried to use this and the tool failed, now I am getting ZERO response from the device. I can't even boot to APX. I'm freaking out right now!
EDIT: I managed to get the process restarted and the phone is in the process of rebooting. Hoping for the best.
EDIT 2: Phone booted up and it was all restored but for some reason the baseband was not updated :\
Did you run by using the flash.bat file? Did you hold volume up and down for the entire flash process?
Sent from my LG-P999 using Tapatalk
AimanF said:
HELP! I tried to use this and the tool failed, now I am getting ZERO response from the device. I can't even boot to APX. I'm freaking out right now!
EDIT: I managed to get the process restarted and the phone is in the process of rebooting. Hoping for the best.
EDIT 2: Phone booted up and it was all restored but for some reason the baseband was not updated :\
Click to expand...
Click to collapse
Did you have old of new baseband on before flashing? What was the state of your G2X before running this?
UPDATE: It appears that this works - but would like to 100% confirm. After all the disasters that occurred from running the LGupdater tool, this would be an important fix and should be stickied at some point. Current members know of the updater problems, but new buyers and member may not - so many may still have this problem down the road.
Therefore, I believe this is an important enough item to bring to closure and make readily available.
U saved my phone's life
THANK YOU THANK YOU
followed instructions restored completley to stock just like how i got phone out of box 2 weeks ago.
I was running eaglesblood v8 and had altered the vold.fstab file to switch mounts
from sdcard to internal and after that point i rebooted and media scanner said damaged sd card well i figured it just to be like an extension of a permission of sorts. and thought if formated it would the paths would switch no problem.
im actually kind of having a hard time rembering exactly what steps i did take to **** it up royally. but went into clockwork 5 to flash another rom from internal storage or same i cant rember now and did factory reset then all hell broke loose .
couldnt mount nothing except for system i tried formating sd card even though i dont have one probally ended up formating internal lol. formated system,
re flashed all recoverie versions including stock. i was getting so mad i called google HA by the way they got some pretty good music when u have to hold.
only thing i didnt try was to load up a rom on sd card and mount that but i really doubt it would have worked and plus i couldnt even use phone to do it lol
i need to go buy drive saved me some serious cash I would say this should be enough confirmation!!
I didn't want to clutter up the dev thread with these questions, but I've never used any CM build on any phone.
I unzipped Bryan's CM7 build to see what was inside and noticed it didn't seem to have a launcher and didn't seem to have any market app. Ok so does that mean you have to pre install Google apps from the SDcard to be able to access the market?
In reading the instructions, it seems like Bryan's CM7 build uses the same kernel as his regular beta kernel thread but that can't be right, can it, with the discussion on the thread....
I noticed that the Google apps were all modified for CM7, so does that mean that ordinary apps won't work unless they're modified?
Can I still use the TW4 launcher on CM7? Used to it.
The business about USB storage not working in Android. I assume that means you can't put anything on the SDcard using the USB cable after Android has booted up so that you have to push everything on there with ADB, is that it, in recovery mode?
1. It does contain a launcher; Its called ADW Launcher.
2. Yes, you would need to flash the google apps. I use this one
http://goo.im/gapps/gapps-gb-20110828-signed.zip
and this one http://goo.im/gapps/gapps-gb-20110828-newtalk-signed.zip​
3. You flash the gapps-gb-20110828-signed.zip file then the gapps-gb-20110828-newtalk-signed.zip google talk with video chat support.
4. Its a different kernel. CM7 is using the MTD version. While regular stock roms use BML.
5. I believe you can use the google apps on those files on any rom. But most roms already bring them integrated.
6. Apps developed for use on the Galaxy S phones like TWLauncher et al will not work as they hook onto some samsung specific programming.
7. As mentioned in 6, you cannot use TWLauncher on cm7.
8. Yes you would have to push everything through ADB in the meantime. Pushing/puling through adb does not require rebooting to recovery though.
Can someone make a video on how to install the rom?
Just follow the written instructions on the thread and you'll be fine
Sent from my SGH-T959V using xda premium
Honestly they confuse the crap outta me. A video would dumb it down for me and im sure a few others.
IDK how the heck I made my efs backup.
But if anyhow, you manage to make some sort of a tar file with your efs files, you should be fine.
After that,
do the erase_image
and mount /efs
and cd /efs
and tar xf anybackupname.tar
you will install. That is if you get your.
Donte21 said:
Honestly they confuse the crap outta me. A video would dumb it down for me and im sure a few others.
Click to expand...
Click to collapse
My suggestion is to wait until the install procedure is easier.
In the CM7 OP, Bryan said (twice) to re-read OP after updates.
Making a video will give you proper instructions for this build, but if Bryan updates the install procedure users following the video are going to have a mixed bag of results, and possible bricks.
Sent from my SGH-T959V using Tapatalk
when I try to Heimdall the boot.img I get a warning that says Tar header contained an invalid file size.
cybok0 said:
when I try to Heimdall the boot.img I get a warning that says Tar header contained an invalid file size.
Click to expand...
Click to collapse
Are you using the heimdall command prompt? Or the heimdall program?
Sent from my SGH-T959V using xda premium
Juls317 said:
Are you using the heimdall command prompt? Or the heimdall program?
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
Program, I just started reading the one click guide, I think I should of tried that first right?
---------- Post added at 09:58 AM ---------- Previous post was at 09:48 AM ----------
I will have to try this on my day off, a lot of reading and understanding to do.
cybok0 said:
Program, I just started reading the one click guide, I think I should of tried that first right?
---------- Post added at 09:58 AM ---------- Previous post was at 09:48 AM ----------
I will have to try this on my day off, a lot of reading and understanding to do.
Click to expand...
Click to collapse
You need to follow Bryan's instructions EXACTLY, a in use the heimdall command prompts
Sent from my SGH-T959V using xda premium
OK, I think I'll stick with VB, I'm not this tech savvy.
I'm going to make a video guide tonight hopefully, but of course I'm going to leave the explicit direction that noobs should not flash it
Sent from my SGH-T959V using xda premium
I have a question as well. Yes, I know that this isnt exactly high priority, but I'm wondering if later there will be a build with Wifi calling. I was trying to install it myself, but it kept force closing, and I don't wanna try anything that'll mess up my phone any worse than I have before.
Wifi calling is basically a must for me since I basically live in Smallville, KS. I get little to no service here, and without it, it usually takes forever to get anything. And yes, I've tried every modem I could, KG4 works best, since I can sometimes get one bar.
I'm trying to complain or anything, and I thank Team Acid for bringing us CM7.
Neo I'm sure at one point bryan will get that working.
Sent from my SGH-T959V using Tapatalk 2
elmejor183 said:
6. Apps developed for use on the Galaxy S phones like TWLauncher et al will not work as they hook onto some samsung specific programming.
Click to expand...
Click to collapse
So does that mean that NONE of the apps will work unless modified to run on CM7? Or are you just talking about certain Samsung issued apps? I'm in the middle of an old Tarzan novel on my e-reader program on the phone...
I have a question with the process flash boot.img with heimdall...when i open heimdall front end and put boot.img into the flash local package..i get a error the tar header contained an invalid file size..on the flash tab, it only takes pit files..also when i just use the heimdall ..a black screen happens similar like a command prompt and just exits..
how do i flash the boot.img with heimdall?
This is using fbs instructions that I am using and i am stuck on step 7. flash the latest boot.img from bryans op..
http://forum.xda-developers.com/showpost.php?p=25197350&postcount=279
Are you on windows? If so open command promt. Cd into the heimdall suite directory. Put your phone in DL mode and connect to usb. From command type "heimdall detect". Should say device detected. Then just put the boot.img in the same directory and follow the OP.
nazcalito said:
So does that mean that NONE of the apps will work unless modified to run on CM7? Or are you just talking about certain Samsung issued apps? I'm in the middle of an old Tarzan novel on my e-reader program on the phone...
Click to expand...
Click to collapse
That's just Samsung-specific stuff like TouchWiz that require Samsung's modified frameworks and extra libraries.
Just use FB's install guide instead. I was going to wait until it was installable through CWM, but this is essentially the same thing with a few extra steps.
Here are the files and instructions to get root and CWM on a Samsung Conquer 4G with the FC17 update. To enter Download Mode on the phone, make sure the phone is turned off and plugged into the wall charging. You should also make sure the phone has a good charge on it. Then turn the phone on by pressing the volume down and camera button and holding them while pressing the power button for a few seconds.
Here are the files you will need -
CONQUER-ROOT.zip
Unzip all the files on your computer and follow these steps.
1) Enter download mode on the phone and plug it into your computer. Open up the Odin program. Then press the OPS button and select the SPH-D600_FC17_CWM.ops file. Then press the PDA button and select the SPH-D600_FC17_CWM.tar.md5 file. The press the Start button, the images should install and the phone reboot. Congrats, your phone now has a stock FC17 image with a CWM Recovery.
2) Next, copy the Superuser-3.0.7-efghi-signed.zip and su-bin-3.0.3.2-efghi-signed.zip files to the root of your SD Card after booting up.
3) Once the phone boots up, go into settings, select Applications, then Development, then turn on USB debugging. Now you can restart the phone into recovery mode with adb. If you don't want to use adb, you can plug the phone into the wall and turn it on while holding the volume down and power button. Either way is fine, as long as you now get the phone into recovery mode.
4) The phone should now go into CWM recovery. Go to install zip from sdcard and select the Superuser-3.0.7-efghi-signed.zip file you put on the sdcard and install that. Next select the su-bin-3.0.3.2-efghi-signed.zip file from your sdcard and install that.
5) Congratulations, you now have a rooted phone with the FC17 update. If you had CWM installed before, you can now do an advanced back-up, and just restore the data from your most recent backup and get all your data back.
I've created a new custom ROM here - http://forum.xda-developers.com/showthread.php?p=29369141
You can just download the new files and follow those instructions if you haven't installed this yet.
it work like charm thank you very much sir very good job done..........
---------- Post added at 04:47 AM ---------- Previous post was at 04:38 AM ----------
there is any custom rom kool one ...
I know on the E4GT, sfhub is able to make tar's that do not wipe user data. The file difference between the 2 images are
removed: boot.bin, sbl.bin, param.lfs, cache.img, data.img
intact: recovery.bin, hidden.img, factoryfs.img(largest file) modem.bin and zImage(contains the kernel)
The Question I'm posing to you is which of the files in the conquer tar.md5 might be the counterparts to the above files, making them the ones to strip out in order to make it not wipe data?
My wife never wanted me to root her phone until recently, so no cwm backup that's pre-OTA, and there are some apps that don't work when re-installed (a security key-gen app)
Any help would be much appreciated.
AestenD said:
I know on the E4GT, sfhub is able to make tar's that do not wipe user data. The file difference between the 2 images are
removed: boot.bin, sbl.bin, param.lfs, cache.img, data.img
intact: recovery.bin, hidden.img, factoryfs.img(largest file) modem.bin and zImage(contains the kernel)
The Question I'm posing to you is which of the files in the conquer tar.md5 might be the counterparts to the above files, making them the ones to strip out in order to make it not wipe data?
My wife never wanted me to root her phone until recently, so no cwm backup that's pre-OTA, and there are some apps that don't work when re-installed (a security key-gen app)
Any help would be much appreciated.
Click to expand...
Click to collapse
Take out userdata.yaffs to retain your data, BUT you will have to rebuild the tar file and remake the OPS file by removing the line that reads -
Code:
9,userdata
If you need the Linux commands to rebuild the image, let me know.
brienj said:
Take out userdata.yaffs to retain your data, BUT you will have to rebuild the tar file and remake the OPS file by removing the line that reads -
Code:
9,userdata
If you need the Linux commands to rebuild the image, let me know.
Click to expand...
Click to collapse
Crap, and me with no Linux box lol
I'll figure something out, I have a live CD around here somewhere.
AestenD said:
Crap, and me with no Linux box lol
I'll figure something out, I have a live CD around here somewhere.
Click to expand...
Click to collapse
Just install Cygwin and use that and then extract all the files out of the .md5 file, it's just a regular tar file with md5 sums in it. WinZip, WinRAR, etc. will easily extract the files from it. Then use these commands to rebuild the image without the userdata.yaffs file.
tar -H ustar -c adsp.mbn amss.mbn appsboot.mbn boot.img cache.yaffs mibib osbl recovery.img system.yaffs > package_name.tar
md5sum -t package_name.tar >> package_name.tar
mv package_name.tar package_name.tar.md5
Click to expand...
Click to collapse
You can replace each package_name with whatever you want it called.
brienj said:
Just install Cygwin and use that and then extract all the files out of the .md5 file, it's just a regular tar file with md5 sums in it. WinZip, WinRAR, etc. will easily extract the files from it. Then use these commands to rebuild the image without the userdata.yaffs file.
You can replace each package_name with whatever you want it called.
Click to expand...
Click to collapse
Thanks for your help, took me a bit, because I mistakenly flashed the non-CWM image first, and the bootloader version just wasn't letting me in. Luckily I have a jig for my SGS2, and I'm up and running now. Hopefully just the fact that it's the full image, rather than OTA upgraded will fix some of the issues she's been having. If not, then having root gives me so many more troubleshooting options.
give me an error says the SPH-D600_FC17_CWM.tar.md5 is invalid image type please help
sromero619 said:
give me an error says the SPH-D600_FC17_CWM.tar.md5 is invalid image type please help
Click to expand...
Click to collapse
"known issue" just keep going, it'll work just fine.
Sent from my SPH-D710 using Tapatalk
sromero619 said:
give me an error says the SPH-D600_FC17_CWM.tar.md5 is invalid image type please help
Click to expand...
Click to collapse
It says this, even with an official Sprint Odin image. It will still work, like AestenD mentioned.
i did all the step but when i hit start on the odin it says please connect phones what can else can i do. loaded the drive from super one click because my laptop running windows seven wasn't reading my phone. Its reading my phone I downloaded the usb driver from this link http://r2doesinc.bitsurge.net/leaked/
now when i run odin now it say """an unnamed file was not found""" whats to do please help
brienj said:
It says this, even with an official Sprint Odin image. It will still work, like AestenD mentioned.
Click to expand...
Click to collapse
i got the phone to be read but now when i hit the start button a window pops out says "unnamed file is not found"
It worked for me.
Question
I have been reading up on this phone since I ordered it from my new provider. I should get the phone sometime later today and wanted to get everything ready to root it as soon as I get it. I've read JWhip804's tutorial on how to root the Conquer. I've also been keeping up with chrystal0925's efforts at making a working themed ROM.
My question is, if I want to have a recovery of my stock phone just in case I have to send it back to my carrier, should I use the method described in this thread or use JWhip804's thread?
I have a brand new Samsung Conquer SPHD600BKS on the Sprint network using a new provider to my area called Ting.
Android Version: 2.3.4
Baseband Version: S: D600.12 x.EG15
Kernel Version: 2.6.35.7-perf
Build Number: GINGERBREAD.EG15
Hardware Version: D600.12
Thanks.
roofus1812 said:
I have been reading up on this phone since I ordered it from my new provider. I should get the phone sometime later today and wanted to get everything ready to root it as soon as I get it. I've read JWhip804's tutorial on how to root the Conquer. I've also been keeping up with chrystal0925's efforts at making a working themed ROM.
My question is, if I want to have a recovery of my stock phone just in case I have to send it back to my carrier, should I use the method described in this thread or use JWhip804's thread?
I have a brand new Samsung Conquer SPHD600BKS on the Sprint network using a new provider to my area called Ting.
Android Version: 2.3.4
Baseband Version: S: D600.12 x.EG15
Kernel Version: 2.6.35.7-perf
Build Number: GINGERBREAD.EG15
Hardware Version: D600.12
Thanks.
Click to expand...
Click to collapse
Super-One-Click only works on EC15, and you can not do an OTA update to FC17 with root, and once you do update to FC17, Super-One-Click will no longer work to root your phone, so you must use the method I have made in this thread, or a similar one to it. You MUST get a stock FC17 image with the CWM recovery to push root onto your phone, as the OTA update has recovery updating scripts, etc. in it, and it's just easier to use the FC17 image and not bother with making the OTA able to be rooted. In order to get the phone back to a stock image, you can easily find the stock Odin image that is floating around, or change the recovery image in the Odin file I have in this thread, with a stock recovery image.
Finished
brienj said:
Super-One-Click only works on EC15, and you can not do an OTA update to FC17 with root, and once you do update to FC17, Super-One-Click will no longer work to root your phone, so you must use the method I have made in this thread, or a similar one to it. You MUST get a stock FC17 image with the CWM recovery to push root onto your phone, as the OTA update has recovery updating scripts, etc. in it, and it's just easier to use the FC17 image and not bother with making the OTA able to be rooted. In order to get the phone back to a stock image, you can easily find the stock Odin image that is floating around, or change the recovery image in the Odin file I have in this thread, with a stock recovery image.
Click to expand...
Click to collapse
I just finished backing up my Conquer using this guide. It was really easy. Thanks.
Hi guys. Anyone use tethering with this? I had tethering working on the old rom fine and another unrooted phone with the ota update. I got a replacement phone and tethering does not work. It only works for google sites - with any tethering app i tried. Is it the hardware or maybe its the stock fc17? I tried reflashing and clearing everything and the problem persists.
I tried using Odin today to root my Samsung Conquer and had a bit of trouble. When I attached the .tar file it gave me an error but as I read this thread I just kept going as if there was no issue. About half way through the Odin installation my phone just rebooted, I tried again and it rebooted it the same spot. I tried putting my phone back into download mode and continue the process, which it did, and I got a "Pass" message at the end. But I don't have CWM and I'm almost positive its still not rooted. Any suggestions?
Any chance of an update with the new OTA included?
Sent from my SPH-D710 using xda premium
There is a new ota fe17. Does anyone know if it will break root? Will it install?
Sent from my SPH-D600 using XDA
I managed to pull some files together including the .pit file from my now working tablet and make a fully working 4 file firmware and combo (all in one) firmware that CAN be flashed with Odin. I have tested it on my device and it does work. Since I know people are searching EVERYWHERE for this, I have released a download link for these files below.
Please, feel free to re-post this anywhere, just be sure to credit me.
DISCLAIMER (Obviously): I WILL NOT BE HELD RESPONSIBLE FOR ANY DAMAGE DONE TO YOUR DEVICE AFTER FLASHING. KEEP IN MIND THAT ANYTHING CAN GO WRONG, EVEN IF YOU'RE FLASHING FIRMWARE THAT IS MADE FOR YOUR DEVICE. THE FIRMWARE AVAILABLE BELOW HAS NOT BEEN MODIFIED, ENGINEERED, OR EDITED IN ANY WAY TO CHANGE THE FUNCTIONALITY OF YOUR DEVICE. IF YOUR DEVICE BRICKS AFTER FLASHING, IT'S ALL ON YOU.
Flashing instructions:
But first, the requirements:
1) SM-T337A, Obviously, but seriously, I can't stress how important it is that you check that your model number is matched with the model number in this thread before flashing anything.
2) A Windows pc (NOT A VIRTUAL MACHINE! Using a VM to flash your device has a high chance to hard-brick your tab, and make sure your computer is running Windows XP or newer.)
3) Your device's USB transfer/charging cable
4) A Brain (Obviously)
Now then, the actual steps (4 File Firmware):
1) Boot your tab into download mode (Shut the device down completely, then hold down the power, volume down, and home button at the same time until a warning message appears)
2) Download and open Odin on your pc
3) Grab the USB charging cable and plug your tab into your pc
4) If Odin does not show your device in the list (It will display an "Added" message if the device is detected) download the Samsung USB Drivers for Mobile Phones and install it to your pc. You may need to/and it is recommended to restart your computer after installing the drivers.
5) Extract the zip file you downloaded containing the firmware to your desktop or a memorable place on your computer.
6) If you wish to wipe your data and start from scratch, click on the 'PIT' tab and select the .pit file in the extracted folder. Then, click the 'OPTIONS' tab and select 'Re-Partition' and 'NAND Erase All'.
7) Insert the firmware files into Odin. Within Odin, for instance, Click on the 'BL' button, which is where the bootloader file goes. Select the extracted package that has 'BL' at the beginning, and vice versa.
Example:
BL: *directory*/BL_T337AUCU2BOH4...
AP: *directory*/AP_T337AUCU2BOH4...
CP: *directory*/CP_T337AUCU2BOH4...
CSC: *directory*/CSC_ ATT_T337AUCU2BOH4...
8) Once done, verify that you have correctly done all the steps above, click 'Start' in Odin and wait for Odin to output a "PASS" message before unplugging anything.
9) If you wish to flash the firmware, but keep your data, make sure that there is no .pit file in Odin, make sure that 'Re-Partition' and 'NAND Erase All' are unchecked, and make sure that there is no file inserted under the 'CSC' row.
Tutorial (Combo Firmware)
1) Boot your tab into download mode (Shut the device down completely, then hold down the power, volume down, and home button at the same time until a warning message appears)
2) Download and open Odin on your pc
3) Grab the USB charging cable and plug your tab into your pc
4) If Odin does not show your device in the list (It will display an "Added" message if the device is detected) download the Samsung USB Drivers for Mobile Phones and install it to your pc. You may need to/and it is recommended to restart your computer after installing the drivers.
5) Extract the zip file you downloaded containing the firmware to your desktop or a memorable place on your computer.
6) Within Odin, Select 'AP' and browse to the directory where you extracted the firmware, and select the .tar package in the directory. There should be nothing else under the other tabs, only 'AP' should have a firmware package in it.
7) Flashing this package (unless you perform the "Developers Tip" at the end of this thread) will wipe all of your data, so be sure that the proper .pit file that came with the firmware package is selected under the 'PIT' tab in Odin and make sure that 'Re-Partition' and 'NAND Erase All' are checked in Odin to ensure a complete wipe of all personal data on the device. If you perform the developers tip at the end of the thread, simply insert the new package you created under 'AP', make sure there is no .pit file under the PIT slot, and make sure that 'Re-Partition' and 'NAND Erase All' are unchecked in Odin.
8) Once done, verify that everything is set and ready-to-go, then click 'Start' and wait for Odin to output a "PASS" message before unplugging anything.
9) Enjoy!
WARNING: If you are seeing sites that charge you money for the files, DO NOT BUY IT. They are scams and I HIGHLY SUGGEST AVOIDING THESE SITES. I didn't have to buy anything. If you do buy the firmware from these scam sites, and your device becomes bricked or messed up in some way, don't say I didn't warn you.
4 File Firmware Download: https://mega.nz/#!n8Q3VIIS!OComhygeI5SL5R6n0EXEfiYMBtVn_aOAIcUuLgmYs-k
Combo Firmware Download: https://mega.nz/#!69oEwbBR!vBtHQnrdwAfdZB3iPeGb99Yp7W79efTQr7t6FZXrzIo
Odin 3.12 Download: https://mega.nz/#!KsZiHKTb!aEHdQgO7JAQeUwdJWqS0xoR3lyJH4ieJ6qTbVKce8Zk
If the link doesn't work or goes down for some reason or if you were confused by my instructions in any way, please let me know.
Developers Tip: If you want to flash firmware without wiping your data, make sure there is no pit file selected under the PIT tab in Odin, then extract your firmware package (extract everything into a separate folder for combo firmware, extract the CSC package for 4 file downloads) and remove cache.img.ext4 then repack as a .tar file. Applies to both combo and 4 file firmware packages. In 4 file packages, cache.img.ext4 is in the CSC file. However, in some cases this may put your device in a bootloop. If you wish to do this on an older device and the cache file doesn't have the .ext4 extension at the end, don't worry, it'll work the same way.
Now that you have the firmware, WHY NOT ROOT IT? Check out my thread on how to do so here: https://forum.xda-developers.com/tab-4/general/root-how-to-root-sm-t337a-supersu-t3553848
Cheers!
Does anyone know the process for extracting the files like this from an OTA update? I have some files I would like to extract from another OTA. Thank you
Sent from my SAMSUNG-SM-N910A using XDA-Developers Legacy app
dkmac said:
Does anyone know the process for extracting the files like this from an OTA update? I have some files I would like to extract from another OTA. Thank you
Sent from my SAMSUNG-SM-N910A using XDA-Developers Legacy app
Click to expand...
Click to collapse
I'll be honest and say its not easy. Making this firmware took me about 3 months. OTA update files are very different from actual Odin firmware files. If you want to extract the files from an OTA update, I just used 7Zip and went from there.
Lollipop 5.1.1 Root for SM-T337A
@KingOfTheNet - Great stuff. There are definitely some shady sites out there offering firmware for the T337A so thank you.
Not to be greedy but any recommendations on rooting 5.1.1 on SM-T337A. I am trying to remove all of the Samsung and AT&T bloatware and get my Tab 4 running lean and mean. I am pretty sure I went with your firmware - my build number is listed as LMY47X.T337AUC2BOH4.
Appreciate the support.
18Echo said:
@KingOfTheNet - Great stuff. There are definitely some shady sites out there offering firmware for the T337A so thank you.
Not to be greedy but any recommendations on rooting 5.1.1 on SM-T337A. I am trying to remove all of the Samsung and AT&T bloatware and get my Tab 4 running lean and mean. I am pretty sure I went with your firmware - my build number is listed as LMY47X.T337AUC2BOH4.
Appreciate the support.
Click to expand...
Click to collapse
Your welcome bro, happy to help! I have actually rooted my tab with SuperSU, fully working. The only thing is its temporary, and I avoid rebooting or shutting the device down at all because it's a system-less SuperSU (meaning temporary). I'll make a thread on how to achieve root on this tab later tomorrow when I get home from work, unless someone replies to this before I do (It's late where I'm at).
Cheers!
18Echo said:
@KingOfTheNet - Great stuff. There are definitely some shady sites out there offering firmware for the T337A so thank you.
Not to be greedy but any recommendations on rooting 5.1.1 on SM-T337A. I am trying to remove all of the Samsung and AT&T bloatware and get my Tab 4 running lean and mean. I am pretty sure I went with your firmware - my build number is listed as LMY47X.T337AUC2BOH4.
Appreciate the support.
Click to expand...
Click to collapse
Just made a thread for it here: https://forum.xda-developers.com/tab-4/general/root-how-to-root-sm-t337a-supersu-t3553848
Cheers!
Hello! ... First of all, thank you for all your hard work! But unfortunately that firmware does not seem to work for me. I'm a little newbie, so I'd appreciate if someone could explain the steps to follow specifically with Odin, as a tutorial or something ... so that I can distinguish what I'm doing wrong.
I uploaded a short video so you can see what I mean... If you could take the time to watch it and tell me what I'm doing wrong, that would be awesome.
Here it is: youtu.be/9JsLVJ-xHMA (I cannot post direct link since I'm new user)
I've downloaded some files with name ATT_T337AUCU2BOH4_T337AATT2BOH4.zip (1.19gb) put by poorusernamebychoice and their tar.md5 file is gone 404.
Now i need some help here, this zip contains:
AP_T337AUCU2BOH4_T337AATT2BOH4_HOME.tar
BL_T337AUCU2BOH4_T337AATT2BOH4_HOME.tar
CP_T337AUCU2BOH4_T337AATT2BOH4_HOME.tar
CSC_T337AUCU2BOH4_T337AATT2BOH4_HOME.tar
MILLETLTE_USA_ATT.pit
This is big file so now I'm stuck what to do or i start a fresh download from above links.
Sent from my SAMSUNG-SM-T337A using Tapatalk
darkcrazy75 said:
Hello! ... First of all, thank you for all your hard work! But unfortunately that firmware does not seem to work for me. I'm a little newbie, so I'd appreciate if someone could explain the steps to follow specifically with Odin, as a tutorial or something ... so that I can distinguish what I'm doing wrong.
I uploaded a short video so you can see what I mean... If you could take the time to watch it and tell me what I'm doing wrong, that would be awesome.
Here it is: youtu.be/9JsLVJ-xHMA (I cannot post direct link since I'm new user)
Click to expand...
Click to collapse
Sorry for the late responce, my internet has been down for a while now (2 weeks). I'll watch the video later today and edit this post with an explainatio n.
_SAM11_ said:
I've downloaded some files with name ATT_T337AUCU2BOH4_T337AATT2BOH4.zip (1.19gb) put by poorusernamebychoice and their tar.md5 file is gone 404.
Now i need some help here, this zip contains:
AP_T337AUCU2BOH4_T337AATT2BOH4_HOME.tar
BL_T337AUCU2BOH4_T337AATT2BOH4_HOME.tar
CP_T337AUCU2BOH4_T337AATT2BOH4_HOME.tar
CSC_T337AUCU2BOH4_T337AATT2BOH4_HOME.tar
MILLETLTE_USA_ATT.pit
This is big file so now I'm stuck what to do or i start a fresh download from above links.
Click to expand...
Click to collapse
Do you mean you need to re-download the files or you need help with flashing them? Dl links are at the middle of the thread.
KingOfTheNet said:
Do you mean you need to re-download the files or you need help with flashing them? Dl links are at the middle of the thread.
Click to expand...
Click to collapse
I hve these files i wrote above. So if they're working, i just need procedure
Sent from my SAMSUNG-SM-T337A using Tapatalk
_SAM11_ said:
I hve these files i wrote above. So if they're working, i just need procedure
Sent from my SAMSUNG-SM-T337A using Tapatalk
Click to expand...
Click to collapse
It's actually very easy, that's why I didn't put any instructions in the thread, I just assumed people knew how to do it by now. But I'm happy to provide instructions to those people who don't know how. Instead of posting said instructions right here, I'll update the thread with instructions.
Cheers!
KingOfTheNet said:
It's actually very easy, that's why I didn't put any instructions in the thread, I just assumed people knew how to do it by now. But I'm happy to provide instructions to those people who don't know how. Instead of posting said instructions right here, I'll update the thread with instructions.
Cheers!
Click to expand...
Click to collapse
That means alot after my last reply, i had been trying to flash with odin but i dnt kno why tablet isn't connecting laptop while other phones are. Not evn on media mode. So I'm downloading ota update.zip
Sent from my SAMSUNG-SM-T337A using Tapatalk
_SAM11_ said:
That means alot after my last reply, i had been trying to flash with odin but i dnt kno why tablet isn't connecting laptop while other phones are. Not evn on media mode. So I'm downloading ota update.zip
Sent from my SAMSUNG-SM-T337A using Tapatalk
Click to expand...
Click to collapse
This might take me a while, I can't edit the thread (kinda odd). I've gotta talk to admin about it but I'll try to get instructions up for ya asap (unless someone replies to you with instructions before I do).
Update: I managed updating to 5.1.1 update. Now i just need January update and root the device. I just need January zip update ota if u can manage me getting that please
Sent from my SAMSUNG-SM-T337A using Tapatalk
_SAM11_ said:
Update: I managed updating to 5.1.1 update. Now i just need January update and root the device. I just need January zip update ota if u can manage me getting that please
Sent from my SAMSUNG-SM-T337A using Tapatalk
Click to expand...
Click to collapse
I believe I have the file stored somewhere on my hard drive, I'll look and pm you a link if I can find it.
Cheers!
KingOfTheNet said:
I believe I have the file stored somewhere on my hard drive, I'll look and pm you a link if I can find it.
Cheers!
Click to expand...
Click to collapse
Sure Thanks for much help
Sent from my SAMSUNG-SM-T337A using Tapatalk
Guys no lollipop update for tab4 t230 ?
tab4map4 said:
Guys no lollipop update for tab4 t230 ?
Click to expand...
Click to collapse
No, this thread is for the Tab 4 8.0 AT&T. Please make sure you consult the relevant forums for your device model as doing anything meant to be done on different devices can be catastrophic.
Cheers!
_SAM11_ said:
Sure Thanks for much help
Sent from my SAMSUNG-SM-T337A using Tapatalk
Click to expand...
Click to collapse
Finally got the instructions up. You can check the very beginning of the thread for instructions on flashing. Just remember, I will not be held responsible if your device is bricked after the matter.
Cheers!
This really should be asked in the dev forum, But my post count is not high enough or worthy!
I have several Nexus Players I plan on selling with the oreo update pre installed, There are 2 addl non playstore apps I need to include as part of the package.
I'm trying to avoid "profiling" the devices to add the 2 extra apps. I have flashed the oreo upgrade to all 8 of them.
I cannot push the apks without profiling to enable adb nor can I seem to find a good zip template to make use the bootloader recovery adb function.
I have tested a few and they all fail with footer and signature failures? I'm only left with a few ideas. Please comment if you can help with any of the options below or suggest a better one..
1. Find a proper update.zip template that works with nexus player..Oreo 8.0 or can bypass the check..
2. Can apps installed in a profiled device be preserved thru a reset method that would allow the device to startup with the first run screens re-instated? Remote setup, WiFi, User account.. Out of the box experience?
3. Can an APK or ZIP be copied to a location on the Nexus Player that would allow it to be installed on first run? (I seem to think Youtube does this)
4. Least popular... Modify the Oreo upgrade img to have the 2 apps pre installed? <--This option looks messy..
Any suggestions appreciated!! Thanks
I suppose #2 is possible if you install as a system app.
Sent from my KFFOWI using Tapatalk
rufy93 said:
I suppose #2 is possible if you install as a system app.
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
After careful examination, #2 and #4 are really the same thing. Without root, I would have to mount the oreo system.img file in linux and add the 2 apks to root/system/app then repack the img file to re-burn the rom. Not exactly sure if that would be enough, I assume there is some checksum or signing in the image file to prevent guys like me from modifying it. Also what would happen after google hits it with an update? would these apps survive? Finding the answer to why the stock Oreo bootloader recovery adb fails to accept the typical update zip format will end up being the right solution.
If you wish to flash using the stock recovery, the update zip must be properly signed. This usually means by the oem private keys.
I haven't been following the modding scene for a long time, but I'm sure these are still inaccessible.
Sent from my KFFOWI using Tapatalk