Hello, there are some devs for the sprint version of this phone who can use this. Our rooted sprint phones are missing a few features such as Wi-Fi calling, FM, PRL updates, HD calling and a voicemail program are just a few of the missing features on the US996 rom that rooted sprint users are on.
Can someone post directions on how someone with a stock sprint device be able to upload their files?
VZW users have already uploaded their file and already have other roms made.
I don't but FYI there is an update today for this model
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my LG-LS997 using Tapatalk
Do not install the update if you want to root
me2151 said:
Do not install the update if you want to root
Click to expand...
Click to collapse
Thanks but with unlimited data and hotspot at no extra charge along with themes. I really don't have a reason to root.
Sent from my LG-LS997 using Tapatalk
EROMITLAB said:
Thanks but with unlimited data and hotspot at no extra charge along with themes. I really don't have a reason to root.
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
How did you get hotspot for free?
osva said:
How did you get hotspot for free?
Click to expand...
Click to collapse
Both my sprint lines are unlimited high speed data and 5 gig hotspot for each line free with Plan. It's in the contract.
Sent from my LG-LS997 using Tapatalk
---------- Post added at 02:15 AM ---------- Previous post was at 01:58 AM ----------
Sent from my LG-LS997 using Tapatalk
---------- Post added at 02:16 AM ---------- Previous post was at 02:15 AM ----------
2 lines unlimited data high speed free 5 gig hotspot each 100 bucks
Sent from my LG-LS997 using Tapatalk
Is there anything that can be done with the update that would give us more sprint features for us rooted folks?
MANDROIDS said:
Is there anything that can be done with the update that would give us more sprint features for us rooted folks?
Click to expand...
Click to collapse
The update is not why I made this post. @Tilde88 is making and others can possibly make roms with the system.img and boot.img of a stock sprint LG V20. The thing is I don't know how that can be done. roms for the US996 at&t and verizon are already made. A custom rom for just the sprint variant should restore all those lost features. That is the hope at least.
I doubt that a rom can be made out of the updated files anyway.
esqueue said:
The update is not why I made this post. @Tilde88 is making and others can possibly make roms with the system.img and boot.img of a stock sprint LG V20. The thing is I don't know how that can be done. roms for the US996 at&t and verizon are already made. A custom rom for just the sprint variant should restore all those lost features. That is the hope at least.
I doubt that a rom can be made out of the updated files anyway.
Click to expand...
Click to collapse
I just need the boot.img for the ramdisk, i have the source to make the kernel.
I need /system of sprint so i can have all the sprint apks and features.
Tilde88 said:
I just need the boot.img for the ramdisk, i have the source to make the kernel.
I need /system of sprint so i can have all the sprint apks and features.
Click to expand...
Click to collapse
How does one obtain said files?
@Tilde88 don't we have to take a complete backup of the rom before flashing the US996 rom? Wanted to make sure before I go about rooting and getting this for you.
fogame said:
@Tilde88 don't we have to take a complete backup of the rom before flashing the US996 rom? Wanted to make sure before I go about rooting and getting this for you.
Click to expand...
Click to collapse
We are instructed to take a backup with twrp but if twrp is installed, it's already "not stock". I have those backups but they were taken from "Flashing TWRP and Fixing Varient Issues" Step 3 in the thread below.
http://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410 They are backups of the boot.img and system.img. the system is 5gb if I am correct. I'll look into uploading them if they will help but I think that they are modified and will not help you.
Dr Professor Sad said:
How does one obtain said files?
Click to expand...
Click to collapse
The best way would be, once you have ADB root, you open up an adb shell and do a DD command to pull the images. However, if you have already flashed TWRP and flashed the deODEX US996 ROM, you will not have the correct files.. You would have to restore your original backup that you made before you flashed the different ROM. I don't know about the bootloader/conversion hack, so I don't know if you can even do that. But if you have ROOT access, and you see your Sprint apps installed, you can get me the files I need.
IT IS IMPERATIVE THAT YOU DO NOT MIX UP THE if= and of=. Please copy and paste ONLY
Code:
adb shell
Code:
su
Code:
dd if=/dev/block/bootdevice/by-name/system of=/data/media/0/ls997system.img
Code:
dd if=/dev/block/bootdevice/by-name/boot of=/data/media/0/ls997boot.img
fogame said:
@Tilde88 don't we have to take a complete backup of the rom before flashing the US996 rom? Wanted to make sure before I go about rooting and getting this for you.
Click to expand...
Click to collapse
If you have not yet rooted, you are the perfect candidate. I believe that your root hack still uses a temporary root shell to flash TWRP. If that is the case, follow my instructions above. If you have flashed the US996 ROM, the files will be of no use to me. You will need to restore the Sprint ROM.
esqueue said:
We are instructed to take a backup with twrp but if twrp is installed, it's already "not stock". I have those backups but they were taken from "Flashing TWRP and Fixing Varient Issues" Step 3 in the thread below.
http://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410 They are backups of the boot.img and system.img. the system is 5gb if I am correct. I'll look into uploading them if they will help but I think that they are modified and will not help you.
Click to expand...
Click to collapse
Yes, if the backup you made was prior to flashing the US996 ROM, that will work.
Tilde88 said:
The best way would be, once you have ADB root, you open up an adb shell and do a DD command to pull the images. However, if you have already flashed TWRP and flashed the deODEX US996 ROM, you will not have the correct files.. You would have to restore your original backup that you made before you flashed the different ROM. I don't know about the bootloader/conversion hack, so I don't know if you can even do that. But if you have ROOT access, and you see your Sprint apps installed, you can get me the files I need.
IT IS IMPERATIVE THAT YOU DO NOT MIX UP THE if= and of=. Please copy and paste ONLY
su
dd if=/dev/block/bootdevice/by-name/system of=/data/media/0/ls997system.img
dd if=/dev/block/bootdevice/by-name/boot of=/data/media/0/ls997boot.img
@Tilde88 don't we have to take a complete backup of the rom before flashing the US996 rom? Wanted to make sure before I go about rooting and getting this for you.
If you have not yet rooted, you are the perfect candidate. I believe that your root hack still uses a temporary root shell to flash TWRP. If that is the case, follow my instructions above. If you have flashed the US996 ROM, the files will be of no use to me. You will need to restore the Sprint ROM.
Yes, if the backup you made was prior to flashing the US996 ROM, that will work.
Click to expand...
Click to collapse
Sweet. Haven't rooted yet so I can make it so. I'll see what I can do to ight.
Tilde88 said:
The best way would be, once you have ADB root, you open up an adb shell and do a DD command to pull the images. However, if you have already flashed TWRP and flashed the deODEX US996 ROM, you will not have the correct files.. You would have to restore your original backup that you made before you flashed the different ROM. I don't know about the bootloader/conversion hack, so I don't know if you can even do that. But if you have ROOT access, and you see your Sprint apps installed, you can get me the files I need.
IT IS IMPERATIVE THAT YOU DO NOT MIX UP THE if= and of=. Please copy and paste ONLY
Code:
adb shell
Code:
su
Code:
dd if=/dev/block/bootdevice/by-name/system of=/data/media/0/ls997system.img
Code:
dd if=/dev/block/bootdevice/by-name/boot of=/data/media/0/ls997boot.img
If you have not yet rooted, you are the perfect candidate. I believe that your root hack still uses a temporary root shell to flash TWRP. If that is the case, follow my instructions above. If you have flashed the US996 ROM, the files will be of no use to me. You will need to restore the Sprint ROM.
Yes, if the backup you made was prior to flashing the US996 ROM, that will work.
Click to expand...
Click to collapse
I've started uploading them to google drive. While I get fast downloads The upload is crap. it will be done in a little under 2 hours.
esqueue said:
I've started uploading them to google drive. While I get fast downloads The upload is crap. it will be done in a little under 2 hours.
Click to expand...
Click to collapse
If you are uploading the TWRP files, I won't be able to use that. You would first have to restore it in TWRP, boot the phone to make sure it works, and then pull those files.
Tilde88 said:
If you are uploading the TWRP files, I won't be able to use that. You would first have to restore it in TWRP, boot the phone to make sure it works, and then pull those files.
Click to expand...
Click to collapse
Ok, I'm cancelling the upload. I'll have to do this when I have some down time.
esqueue said:
Ok, I'm cancelling the upload. I'll have to do this when I have some down time.
Click to expand...
Click to collapse
Someone else in this thread has yet to root. He is going to try and get the files for me, before he flashes the US996 ROM
Tilde88 said:
Someone else in this thread has yet to root. He is going to try and get the files for me, before he flashes the US996 ROM
Click to expand...
Click to collapse
Yep. Just got to wait until I'm at a computer that isn't government owned lol.
Tilde88 said:
The best way would be, once you have ADB root, you open up an adb shell and do a DD command to pull the images. However, if you have already flashed TWRP and flashed the deODEX US996 ROM, you will not have the correct files.. You would have to restore your original backup that you made before you flashed the different ROM. I don't know about the bootloader/conversion hack, so I don't know if you can even do that. But if you have ROOT access, and you see your Sprint apps installed, you can get me the files I need.
IT IS IMPERATIVE THAT YOU DO NOT MIX UP THE if= and of=. Please copy and paste ONLY
Code:
adb shell
Code:
su
Code:
dd if=/dev/block/bootdevice/by-name/system of=/data/media/0/ls997system.img
Code:
dd if=/dev/block/bootdevice/by-name/boot of=/data/media/0/ls997boot.img
If you have not yet rooted, you are the perfect candidate. I believe that your root hack still uses a temporary root shell to flash TWRP. If that is the case, follow my instructions above. If you have flashed the US996 ROM, the files will be of no use to me. You will need to restore the Sprint ROM.
Yes, if the backup you made was prior to flashing the US996 ROM, that will work.
Click to expand...
Click to collapse
Quick Questions because i truly don't know. Will my boot img contain personal info? Is this safe? IE not going to brick my device. Just don't want to give my personal info unknowingly. I would like to root in the future but am waiting for all the kinks to get sorted. Being able to help the cause would be great.
Related
Hello All,
DISCLAIMER! I AM NOT RESPONSIBLE FOR ANY DAMAGE THAT MAY OCCUR THROUGH THE USE OF THIS GUIDE!!! YOU FOLLOW THIS AT YOUR OWN RISK WITH THE KNOWLEDGE THAT THIS MAY/WILL VOID YOUR WARRANTY
I wanted to make this post because I was such a little girl about rooting my phone and installing a custom recovery ever. I’m creating a step by step guide with PICTURES/VIDEOS to help anyone else do the rooting AND flashing custom recovery.
ALL INSTRUCTIONS WERE DONE USING THE LG G2 VERIZON VERSION WITH THE OTA UPDATE. That is I rooted it when it was VS98011A.
PLEASE READ THE INDIVIDUAL THREADS TO MAKE SURE YOUR SPECIFIC VERSION IS SUPPORTED.
I would first like to give credit where credit is due to everyone who has helped my sorry butt do this. All specific questions/problems should be directed to the proper threads as I cannot accurately answer them (sorry).
First of all the two guides I used:
Rooting: thecubed
http://forum.xda-developers.com/showthread.php?p=45692679#post45692679
Flashing TWRP: WACOMalt
http://forum.xda-developers.com/showthread.php?t=2449670
Personal help I received via my own thread:
Paranoid Android User: djraimondi
http://forum.xda-developers.com/showthread.php?p=46779203#post46779203
Thank you “jrgilbert79” for all of your responses.
NOTE: I AM NOT PROVIDING LINKS TO THE FILES ON THIS PAGE. PLEASE GO TO THE GUIDE PAGES TO GET THE ROOT FILES AND THE TWRP AND LOKI FILES. THE RESPECTED THREAD POSTERS ARE USUALLY GOOD AT KEEPING THE MOST UPDATED FILES IN THEIR POSTS.
Now for the instructions:
1.Ensure you have the proper USB drivers installed, and your phone is in the proper mode (For Verizon, use Ethernet mode on the PC settings menu)
2.Enable Developer Mode on your phone and enable USB Debugging
3.Extract this zip file somewhere on your PC. (I recommend making a folder on the desktop named “root” and extract everything into that folder.)
4.Run root.bat
5.The phone will ask you to disconnect USB, disable USB debugging, then re-enable it and plug the phone back in, do so when prompted
6.You will then be asked if you would like to have a superuser package installed, which you can accept or decline (I recommend accepting).
If the text instructions scare you please use this video (I did). Follow along exactly as said.
http://www.youtube.com/watch?v=Y45SXPRb31o
BAM! You should be rooted. To check do what the video says:
Go back into the command promp (shift right click inside the “root” folder (if you created it) “open command prompt here”). Type “adb shell”, “su”, “id”.
It should show identical information to this image.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Restart your phone.
Now installing TWRP can be a little more confusing. The actual guide gives you 3 options. It is easiest to use just the first one. What you are going to want to do is download the require files. The .img and the loki_flash file. Now unless you have adb installed you will need to put these files in a certain location. (If you do not know if you have adb installed you probably don’t, it’s okay the root folder has a way around this).
So now you should have downloaded the loki zip and extracted it to get the loki_flash file and your specific twrp disk image. Place both these files inside the folder that contained all the root information, like so:
Note: The files in the black box are what allow you to do the adb commands such as “adb devices”, “adb push”, etc. That is why you must shift click and “open command window here”. If you are afraid you did it wrong always test that windows can see your device by typing “adb devices” and verify it sees your LG.
Once you have the command window open and both files inside the same folder you use to root your device you are ready to flash the twrp recovery. It’s actually pretty simple, just like the root method. Essentially you are just copying two files over onto your device.
I’d figure I will add a little information as to what exactly is going on here. These are kind of a sudo linux language commands. I always liked knowing what was actually going on when I did stuff. You can skip this part if you want…
________________________________________________________________________________________________
“adb push” essentially copies a file over to the given location, in these instances /data/local/temp.
Cd means “change directory” it is a way of navigating through folders and sub folders. Windows has the same command.
Chmod pronounced “change mod” is giving rights to the file. Linux has a way of allowing rights to files. You have 3 groups “user” “group” “global/world” and 3 premissions “read” “write” “execute”. Basically all you need to know is “777” gives read write and execute commands to EVERYONE.
./ essentially runs a program or file or whatever. (This is what flashes the custom recovery).
_________________________________________________________________________________________________
Enter the commands as shown: THESE ARE FOR VERIZON. YOU MUST CHANGE THE FILE NAMES IF YOU ARE USING ANY OTHER CARRIER.
Code:
Code:
adb push loki_flash /data/local/tmp/loki_flash
adb push openrecovery-twrp-2.6.3.2-g2vzw.img /data/local/tmp/openrecovery-twrp-2.6.3.2-g2vzw.img
adb shell
(IF YOU DONT SEE A # prompt, type su to get it.)
cd /data/local/tmp
chmod 777 loki_flash
./loki_flash recovery /data/local/tmp/openrecovery-twrp-2.6.3.2-g2vzw.img
exit
adb reboot recovery
It will look something similar to this (I had already previously pushed the loki file that is why you do not see that here). When you are done if you don’t want to create a backup right away and just want to turn your phone back on go into “Reboot” -> “System”. It will boot your phone normally.
Now this is also something I wanted to show ya’ll. To get into TWRP recovery using the key combo you have to turn off your phone. Wait 5 seconds. Turn it on while holding the VOLUME DOWN and POWER key. Once the LG logo appears let go and instantly press and hold the VOLEUME DOWN and POWER key again. This scared me at first but it takes you to a factory reset screen. Mind you I took this video with my Droid RAZR HD, excuse the bad quality haha. (Also I was watching the CMA’s don’t hate… Yes it was Taylor Swift Preforming. You don’t need the sound anyway). Of course you can reboot into recovery using the adb command like the second video as well.
http://youtu.be/8EC29byGOvg
http://youtu.be/jLqBC7uWhyI
To create a backup I just did the default suggested by TWRP. This is from their websites:
http://teamw.in/whattobackup
The default backup options in TWRP are system, data, and boot. For most cases, this is sufficient for backing up a ROM. (Note that in some rare cases, boot isn't available for backup on certain devices). If your device has the option, backing up android_secure and/or sd-ext may be a good idea. There's usually no reason to back up cache or recovery (recovery not available for backup on some devices).
Some devices have "special partitions" like WiMAX, pds, efs, etc. These partitions almost never need to be included in a normal backup. It's usually a good idea to make a single backup of these partitions and hang on to them just in case. Make use of TWRP's keyboard feature and name your backup of these special partitions accordingly.
You just swipe you create a backup. It takes some time (took my device about 5 minutes). I did not compress it I did that afterwards. My file in side was relatively large (4GB approx.). Here is a screenshot of the folder with the backup and then the zip file I made of it. You should probably imo keep a copy on your phone for flashing back and a copy on your computer in case something goes horribly wrong and you lose the file (that way you can adb push the file).
Saved for the flashing of a future ROM.
Sent from my VS980 4G using xda app-developers app
Thanks for taking the time to write this, I got stuck in the TWRP loop when I tried to install it a couple weeks ago.
Did you get stuck doing the button combo or through adb. I believe the older version just had a boot loop problem.
Also I never boot to system from twrp recovery. I always turn it off and turn it back on.
Sent from my VS980 4G using xda app-developers app
Easiest Way To Flash TWRP
OP, Easiest way to do this is head to this thread, download YOUR PHONE'S version of TWRP recovery, put it on your SD card, download Flashify and Quickboot via the Play Store, open Flashify, select recovery, find the recovery.img that you placed on your sd card, flash, open quickboot and reboot into recovery. VOILAH! TWRP is now installed I did this on my AT&T D800, but I assume it should work with all other variants. I am not responsible if something goes wrong. This was just the easiest and fastest thing for me! Press thanks if it worked:good:
P.S. make sure you are ROOTED and BUSYBOX IS INSTALLED.
I used 2.6.3.2 but I probably mucked it up because I used flashify. I ended up flashing back to stock.
wizzcap said:
I used 2.6.3.2 but I probably mucked it up because I used flashify. I ended up flashing back to stock.
Click to expand...
Click to collapse
Do you have the At&t version? Also, make sure you are rooted and busybox is installed.
I do not recommend using flashify. Just my opinion. Have heard of so many problems using flashify.
If you read the guide I explain a little in detail what the actual commands to flash twrp actually do. I'm not sure how the internals of flashify flash the recovery. I'm not sure if the app has the equivalent of the "./" command.
Also when booting into recovery I recommend "adb reboot recovery" or using the volume down and power button method. I feel these ways avoid the least amount of problems. But that's just my two cents. I am by no means an expert. Not by any stretch of the imagination.
Sent from my VS980 4G using xda app-developers app
Great guide for any other girls out there. Lots of pictures and hand holding, they usually need that...
djraimondi said:
I do not recommend using flashify. Just my opinion. Have heard of so many problems using flashify.
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
Wonder why? Worked fine for me.
jellybear456 said:
Do you have the At&t version? Also, make sure you are rooted and busybox is installed.
Click to expand...
Click to collapse
Yea I'm rooted on verizon. I used the root method OP posted. All I did was put the file on the SD card and flashed the .img with flashify, but I didn't have any of the other apps installed you mentioned. The phone started back up in twrp, but that's all it would do other than download mode. I'll try the tutorial OP made this weekend when I have some time.
If you have any questions just let me know.
Sent from my VS980 4G using xda app-developers app
help
Hey there just started reading through your thread good job. Im pretty new to android and this was the first time i rooted my phone. Worked out great but seeing how my device is the D803 (canadian device) and theres no version of TWRP for mine so should I just wait it out? Plus after I root am I suppose to have some backup program or what? I'm kinda lost right now and hope someone can guide me into the right direction.
I'm not positive if there is twrp for the D803. Rooting just allows you to access all the files and folders on your device. Twrp is called a custom recovery. It is what allows you to create a backup of your current system (see my last two screenshots) and it also allows you to flash new versions of android.
Sent from my VS980 4G using xda app-developers app
djraimondi said:
I'm not positive if there is twrp for the D803. Rooting just allows you to access all the files and folders on your device. Twrp is called a custom recovery. It is what allows you to create a backup of your current system (see my last two screenshots) and it also allows you to flash new versions of android.
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
ok so since theres no twrp version for the d803 shoulld I just continue on and not worry or is twrp important?
You technically don't need a custom recovery but I wouldn't flash any Roms without one. A custom recovery is basically your "oh ****" situation. If for instance you flashed a ROM and something went wrong the recovery would allow you to fix it. If you didn't have a recovery you would essentially be screwed.
I wouldn't do any flashing until twrp is available.
If you want more information about twrp and custom recoveries I recommend going to the twrp thread as they can answer better then me.
Sent from my VS980 4G using xda app-developers app
ok I'll definitely wait till a twrp version comes out for me. Since I already successfully rooted my phone im ok for now right as long as I dont flash anything ?
Yeah root won't hurt. You can actually do a lot of neat things with just root. I will try to find a list of them. One of them is an app which removes all ads. I forget what it is called though.
Sent from my VS980 4G using xda app-developers app
djraimondi said:
Yeah root won't hurt. You can actually do a lot of neat things with just root. I will try to find a list of them. One of them is an app which removes all ads. I forget what it is called though.
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
yea that would be cool if you get get me a list of stuff to have. So far I only have Xposed and using titanium backjup to get arrid of some bloat.:fingers-crossed:
To OP, thanks for taking the time to do this. Yes, I don't mind a bit of handholding as I've never rooted a phone before so I really appreciate it. Installed root and TWRP w/out issue. Was a little surprised at how much space TWRP took up. Anyway now I just need to decide which ROM to flash.
I've been at this for about 5 hours now, and I can't seem to get CWM installed.
I decided to flash to stock fw (4.2.2) so I could carrier unlock my phone. After I flashed to stock, I used the CASUAL tool to do this.
After I had root, I tried getting CWM back so I could restore my backup, prior to this whole process, however every time I have attempted to flash CWM the phone reboots to TWRP.
I thought I knew about this kind of stuff, but now it's just starting to get to me
Has anyone encountered this or know of a fix?
Thanks.
tasiv said:
I've been at this for about 5 hours now, and I can't seem to get CWM installed.
I decided to flash to stock fw (4.2.2) so I could carrier unlock my phone. After I flashed to stock, I used the CASUAL tool to do this.
After I had root, I tried getting CWM back so I could restore my backup, prior to this whole process, however every time I have attempted to flash CWM the phone reboots to TWRP
I thought I knew about this kind of stuff, but now it's just starting to get to me
Has anyone encountered this or know of a fix?
Thanks.
Click to expand...
Click to collapse
You messed up. You have an i337 and are now on mf3 firmware. You can't put on a custom recovery. Safestrap is you're only option
Sent from my Nexus 5
jd1639 said:
You messed up. You have an i337 and are now on mf3 firmware. You can't put on a custom recovery. Safestrap is you're only option
Sent from my Nexus 5
Click to expand...
Click to collapse
I'm currently running JDQ39.I337UDUAMDB (galaxy s4 stock FW v4.2.2). I came from the latest Google Edition rom posted by Danvdh.
When I run CASUAL that flashes a recovery. If I now have a mf3 device, how could I have flashed TWRP with CASUAL?
I have somehow managed to get another recovery installed using the following instructions:
download the two files in the instructions
su
cd /data/local/tmp
chmod 755 *
./lok_flash recovery recovery.lok
reboot recovery
That allowed me to change the recovery, but I really have no idea what that did.
I don't think I have an mf3 device now. Is there any way to verify this?
Check your baseband. You probably still are on mdb. Are you flashing a zip to get back to cwm? Which one
Sent from my Nexus 5
jd1639 said:
Check your baseband. You probably still are on mdb. Are you flashing a zip to get back to cwm? Which one
Sent from my Nexus 5
Click to expand...
Click to collapse
baseband = I337UCUAMDB
I'm not flashing a zip, it's apparently a (IMO) bastardized version of clockwork mod. Hell, it could be a zip, but I know I'm running a terminal command to write the recovery. I don't think I can paste links...
I have no problem flashing the google edition firmware or AOSP based firmware when I have TWRP installed. It's just trying to get rid of TWRP and go back to CWM that I want to do (because I backed up my phone in CWM and now I can't get back).
tasiv said:
baseband = I337UCUAMDB
I'm not flashing a zip, it's apparently a (IMO) bastardized version of clockwork mod. Hell, it could be a zip, but I know I'm running a terminal command to write the recovery. I don't think I can paste links...
I have no problem flashing the google edition firmware or AOSP based firmware when I have TWRP installed. It's just trying to get rid of TWRP and go back to CWM that I want to do (because I backed up my phone in CWM and now I can't get back).
Click to expand...
Click to collapse
Flash this in your current twrp, it'll replace twrp and put in cwm 6.0.4.7
Edit, PS to carrier unlock I think you need to be on mdl firmware
jd1639 said:
Flash this in your current twrp, it'll replace twrp and put in cwm 6.0.4.7
Edit, PS to carrier unlock I think you need to be on mdl firmware
Click to expand...
Click to collapse
OK, so I have TWRP right now, and I ran that utility you created for me. It failed.
here's what I can make out of the log:
assert failed: package_extract_file("orecovery-clockwork-6.0.4.7-jflteat
E:Error executing updater binary in zip '/sdcard/Download/jjd-recovery-c
Error flashing zip "/sdcard/Download/jjd-recovery-clockwork-6.0.4.7-jflt
updating partition details...
it's cut off on the right, but I think you can tell that...
tasiv said:
OK, so I have TWRP right now, and I ran that utility you created for me. It failed.
here's what I can make out of the log:
assert failed: package_extract_file("orecovery-clockwork-6.0.4.7-jflteat
E:Error executing updater binary in zip '/sdcard/Download/jjd-recovery-c
Error flashing zip "/sdcard/Download/jjd-recovery-clockwork-6.0.4.7-jflt
updating partition details...
it's cut off on the right, but I think you can tell that...
Click to expand...
Click to collapse
Sorry, I had a typo in it try this
jd1639 said:
Sorry, I had a typo in it try this
Click to expand...
Click to collapse
I feel useless.... Now It's giving me the "system software not authorized by AT&T has been found on your phone" I attempted to flash lokidoki, but I think that's just for the rom...
tasiv said:
I feel useless.... Now It's giving me the "system software not authorized by AT&T has been found on your phone" I attempted to flash lokidoki, but I think that's just for the rom...
Click to expand...
Click to collapse
Does your baseband and build number both say your on mdb firmware?
Sent from my SAMSUNG-SGH-I727
jd1639 said:
Does your baseband and build number both say your on mdb firmware?
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
currently my baseband = I337UCUAMDB
and my build number = JDQ39.i337UCUAMDB
so, yes
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
tasiv said:
currently my baseband = I337UCUAMDB
and my build number = JDQ39.i337UCUAMDB
so, yes
Click to expand...
Click to collapse
Idk, what to say now. I'm thinking it's because you're on mdb and not mdl. Mdb is really old. You might try flashing mdl. You'll still be able to put on a custom recovery and flash roms just like you currently are. Just don't flash mf3 or higher. If you go that route you'll want to make sure to freeze the update.apk so the ota didn't work.
Sent from my Nexus 5
jd1639 said:
Idk, what to say now. I'm thinking it's because you're on mdb and not mdl. Mdb is really old. You might try flashing mdl. You'll still be able to put on a custom recovery and flash roms just like you currently are. Just don't flash mf3 or higher. If you go that route you'll want to make sure to freeze the update.apk so the ota didn't work.
Sent from my Nexus 5
Click to expand...
Click to collapse
I appreciate the help you've given me.
I think I may try that, I'll just have to find a copy of it somewhere. I've got my phone back into a state where I (almost) left it thanks to titanium backup and the ROM I've been using. I really liked CWM, but the features of TWRP seem promising. I've been having a little trouble backing up the phone though (I think I'm exceeding max file size of backup?) but I'm sure it'll eventually work.
We're all in the process of receiving and installing this update, and there are many questions about recoveries, rooting, etc. This is a thread to gather all the info we know so people don't have to be searching through tons of posts.
(I'm in the process of installing now, so I'll answer as many of these questions as I can. I will also update the OP with info from other users. If anything I state is untrue, please post and let me know.)
Can I take the update while rooted?
Yes! If you are on 4.2 and rooted but on STOCK RECOVERY, you can take the OTA and keep root.
Can I take the update with TWRP installed?
No! You will bootloop into recovery.
Is there an alternative/manual/TWRP method of installing?
Yes, see below post.
How am I supposed to update if I installed TWRP?
See below post, "README if you are currently on JB4.2.2"
Alternative method: "download flashify from the play store, backup twrp, then flash the recovery.img from OP. No pc needed & 100% pain free." Thank you to 86shelby. Then take the OTA.
Can I root the 4.4 version?
As of 8/26, yes! Stumproot works with the Bruteforce method. http://forum.xda-developers.com/show....php?t=2850906
Can I downgrade from 4.4 to 4.2?
Yes
If anyone else has questions they'd like posted, please let me know, and I'll put them in.
NOTE: If you want root/twrp in KK4.4.2, you'll need to pre-root in JB4.2.2 before OTA update(towelroot works in JB4.2.2, but not in KK4.4.2)
Looks like Stumproot works with KK4.4.2
README if you have a non-booting device
If you tried OTA update with TWRP recovery and get stuck in a bootloop for TWRP
Do one of the options below:
A) If you still want 4.4.2 via Verizon OTA, flash stock recovery
Go into TWRP, restore stock recovery via link below
http://forum.xda-developers.com/showpost.php?p=52975059&postcount=65
B) If you want to stop the bootloop, and flash 4.4.2 via TWRP backup from below...
Go into TWRP, wipe OTA partition (which signals the device to keep going into recovery)
http://forum.xda-developers.com/showthread.php?p=51749086#post51749086
Click to expand...
Click to collapse
If I mess everything up and device doesn't boot
Restore (B) the entire device back to 4.2.2 using the kdz file(more complicated and you lose all your settings/files/apps)
README if you are currently on JB4.2.2
If you already have TWRP, you can flash 4.4.2 via the TWRP backup below (probably can just flash over 4.2.2 without factory reset... do factory reset only if something goes wrong)
http://forum.xda-developers.com/showthread.php?p=53043541#post53043541
If you want to apply update via Verizon OTA, READ below first
If you have TWRP installed, you'll need to flash stock recovery. Either (A)
restore stock recovery only, or restore (B) the entire device back to 4.2.2 using the kdz file(more complicated and you lose all your settings/files/apps)
NOTE: some people have problems with OTA even after restoring stock recovery. You'll have to restore using the (B) method, and lose everything
[*]If you want root in 4.4.2, you'll need to apply root BEFORE OTA (via towelroot, ...?). root is allowed during OTA, will be maintained after OTALooks like stumproot works
Apply OTA, hope nothing goes wrong
Yay!
Click to expand...
Click to collapse
README if you are currently on KK4.4.2
Splitwindow/multiwindow on 4.4.2
http://forum.xda-developers.com/lg-...10-splitwindow-multiwindow-stock-4-4-t2837326
Root on 4.4.2: Use Stumproot
TWRP on 4.4.2
Root ? (Towelroot isn't working though)
Flash 4.2.2 aboot.img and TWRP.img
A) Upload aboot.img from 4.2.2 to device, then do
Code:
adb shell
su
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
B) Follow steps in TWRP thread to install TWRP
Click to expand...
Click to collapse
4G LTE does not work on 4.4.2?
Flash modem from 4.2.2 -> http://forum.xda-developers.com/showpost.php?p=54584896&postcount=5
Going from 4.4.2 back to 4.2.2
Install TWRP (see section above)
Get 4.2.2 TWRP backup from here and restore
or restore (B) the entire device back to 4.2.2 using the kdz file(more complicated and you lose all your settings/files/apps)
Click to expand...
Click to collapse
Guess I got lucky - never got around to installing the custom recovery. I MEANT to do that....
https://pvzwmdmcdn.vzw.motive.com/firmware/LG_VK810_11A_TO_22B.bin
in case you want to poke around
Verizon LG G2 users say it's okay to be rooted, just need stock recovery for OTA update... let's see what happens..
yeah, 0x136 error when it tries to update. people say 0x136/0x13E errors are because of unlocked bootloaders... i guess we need to flash completely stock via KDZ file, then take ota, then use stuff like towelroot
So this is what I get when I check for update. I'm stock unrooted I even did a FDR. Any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my XT1080 using Tapatalk
Towelroot doesn't work yet with the new update. I took the update completely stock and unrooted and I'm not able to root now.
modus81 said:
Towelroot doesn't work yet with the new update. I took the update completely stock and unrooted and I'm not able to root now.
Click to expand...
Click to collapse
have you tried other root methods?
ioroot, or this root below? (
http://forum.xda-developers.com/showthread.php?t=1886460&highlight=4+2+2
paperWastage said:
https://pvzwmdmcdn.vzw.motive.com/firmware/LG_VK810_11A_TO_22B.bin
in case you want to poke around
Verizon LG G2 users say it's okay to be rooted, just need stock recovery for OTA update... let's see what happens..
yeah, 0x136 error when it tries to update. people say 0x136/0x13E errors are because of unlocked bootloaders... i guess we need to flash completely stock via KDZ file, then take ota, then use stuff like towelroot
Click to expand...
Click to collapse
How do I install this?
Sent from my VK810 4G using Tapatalk
gfullwr70 said:
How do I install this?
Sent from my VK810 4G using Tapatalk
Click to expand...
Click to collapse
you don't. go through Settings-> System update
paperWastage said:
you don't. go through Settings-> System update
Click to expand...
Click to collapse
Ok thanks. Check my above post and pic. I get that everyone I try there check for update.
Sent from my XT1080 using Tapatalk
gfullwr70 said:
Ok thanks. Check my above post and pic. I get that everyone I try there check for update.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
Same here
Flashing comletely stock via .kdz file
I'm getting the 0X13E error. Does anyone have the the process for this? I saw a different thread that directed to a droidreviews.com website but one of the files it said to download, my Chrome browser scanned as malicious so I stopped pursuing that route.
ssinn said:
Same here
Click to expand...
Click to collapse
gfullwr70 said:
Ok thanks. Check my above post and pic. I get that everyone I try there check for update.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
you could try forcing the update (manually place the file and the start the apk)
see if the steps below can help you
http://forum.xda-developers.com/showthread.php?t=2699123
paperWastage said:
you could try forcing the update (manually place the file and the start the apk)
see if the steps below can help you
http://forum.xda-developers.com/showthread.php?t=2699123
Click to expand...
Click to collapse
Thanks this is what I was looking for. I'll give it till tonight to see if the ota shows up then I'll try this method.
Sent from my XT1080 using Tapatalk
paperWastage said:
you could try forcing the update (manually place the file and the start the apk)
see if the steps below can help you
http://forum.xda-developers.com/showthread.php?t=2699123
Click to expand...
Click to collapse
So is this only if you can't download the ota update or if you get an error while trying to install it after downloading it?
prana22 said:
So is this only if you can't download the ota update or if you get an error while trying to install it after downloading it?
Click to expand...
Click to collapse
first one.... my tablet wasn't able to find an OTA on 4G LTE (on t-mobile's network), but wifi works fine
Mine prompted me yesterday and I was not sure I wanted to yet (wait for other victims...). It would only let me delay it up to 24 hours, so it was going to annoy me. I let it update today and it looks fine. I did not unlock or change my recovery, but had used towelroot to gain root.
After update, it appears that root is still there.
The only glitch I have noticed is that my Mobile Hotspot (wifi name/pass) were reset to defaults.
rjkmadison said:
Mine prompted me yesterday and I was not sure I wanted to yet (wait for other victims...). It would only let me delay it up to 24 hours, so it was going to annoy me. I let it update today and it looks fine. I did not unlock or change my recovery, but had used towelroot to gain root.
After update, it appears that root is still there.
The only glitch I have noticed is that my Mobile Hotspot (wifi name/pass) were reset to defaults.
Click to expand...
Click to collapse
That's interesting, and good to know. Can anyone else verify this? I didn't think the update would go through if you were rooted. Now I might downgrade through kdz again and root before I take the OTA.
rjkmadison said:
Mine prompted me yesterday and I was not sure I wanted to yet (wait for other victims...). It would only let me delay it up to 24 hours, so it was going to annoy me. I let it update today and it looks fine. I did not unlock or change my recovery, but had used towelroot to gain root.
After update, it appears that root is still there.
The only glitch I have noticed is that my Mobile Hotspot (wifi name/pass) were reset to defaults.
Click to expand...
Click to collapse
go flash TWRP, make backup of stock and share it please?
How can I revert to stock recovery in OSX? All I see is the LG Mobile tool for windows?
ROGERS H812 v10h ROOTED SYSTEM IMAGE
Here ya go, gents!
I know there are some Rogers users here, and most of us don't have easy access to Ubuntu to inject root.
I got Ubuntu up and running via VM, so I thought i'd root the new Rogers version 10h for us.
Thanks to greganka for the system image for me to root.
The instructions for how to flash it can be found in hackarchive's "Root ANY LG G4 Variant 100% Success Directives | Root Injection | Less Bricks" thread. Thanks to him for that.
The correct strings can be found in autoprime's thread HERE.
As usual, I will not be held responsible if you happen to brick your phone flashing this image, by picking the wrong command, etc.
ROGERS 10h Rooted System Image.
Enjoy!
Been looking around for this. Thank you so much!
If I'm currently on the rooted 10b update can I just flash the system image and call it a day?
spartan268 said:
If I'm currently on the rooted 10b update can I just flash the system image and call it a day?
Click to expand...
Click to collapse
Yep. It will be a day...a day of fixing all the issues you will have, lol.
You need to flash the full 10h KDZ first, THEN the rooted System Image, or you will have tons of issues.
If I'm currently on the 10f Telus rooted firmware, and wanna get my Rogers rooted 10h firmware back, how do I go about it?
Do I just follow the same steps I did to update to the Telus? 10h KDZ then flash new image?
850T5m said:
If I'm currently on the 10f Telus rooted firmware, and wanna get my Rogers rooted 10h firmware back, how do I go about it?
Do I just follow the same steps I did to update to the Telus? 10h KDZ then flash new image?
Click to expand...
Click to collapse
Yep! I recommend a factory reset after though. I know it's a pain, but VoLTE isn't working for some of us after using the Telus 10f then going to the Rogers 10h.
I tried everything to figure it out. I finally did a factory reset, and VoLTE and video calling is working again. I think since Telus doesn't support it, their software breaks it on Rogers phones, even after you flash a Rogers KDZ again.
Just FYI. You can dirty flash the Rogers 10h KDZ and then my rooted system image, and if VoLTE works (and you are actually with Rogers), then leave it. If it doesn't, try a factory reset.
GibMcFragger said:
ROGERS H812 v10h ROOTED SYSTEM IMAGE
Here ya go, gents!
I know there are some Rogers users here, and most of us don't have easy access to Ubuntu to inject root.
I got Ubuntu up and running via VM, so I thought i'd root the new Rogers version 10h for us.
Thanks to greganka for the system image for me to root.
The instructions for how to flash it can be found in hackarchive's "Root ANY LG G4 Variant 100% Success Directives | Root Injection | Less Bricks" thread. Thanks to him for that.
As usual, I will not be held responsible if you happen to brick your phone flashing this image, by picking the wrong command, etc.
ROGERS 10h Rooted System Image.
Enjoy!
Click to expand...
Click to collapse
Thanks a lot! I downloaded it.
I am wondering though, if I were to root after backing up stock system image, how can I restore my phone to stock without root to take OTAs? Can I simply flash stock system image? or do I really need to flash the kdz?
You should just be able to use the "full unroot" option in Supersu, but yes, flashing your original image would also do it.
I work in Burnaby you wanna root it for me haha jk
10h better be worth it for the trouble we have to go through
spartan268 said:
I work in Burnaby you wanna root it for me haha jk
10h better be worth it for the trouble we have to go through
Click to expand...
Click to collapse
Lol it's easy to root if you read the instructions in the root thread. As long as you have windows. I did the hard work already for you by installing Ubuntu and actually injecting root into the system image. All you have to do is flash it.
As for the update, it fixes the touchscreen and the lag. Definitely worth it.
GibMcFragger said:
ROGERS H812 v10h ROOTED SYSTEM IMAGE
Here ya go, gents!
I know there are some Rogers users here, and most of us don't have easy access to Ubuntu to inject root.
I got Ubuntu up and running via VM, so I thought i'd root the new Rogers version 10h for us.
Thanks to greganka for the system image for me to root.
The instructions for how to flash it can be found in hackarchive's "Root ANY LG G4 Variant 100% Success Directives | Root Injection | Less Bricks" thread. Thanks to him for that.
As usual, I will not be held responsible if you happen to brick your phone flashing this image, by picking the wrong command, etc.
ROGERS 10h Rooted System Image.
Enjoy!
Click to expand...
Click to collapse
Should we rename the system image to to the current update or do we just use "rootedsystem" as the img. name in the send command?
boywithabeard said:
[/HIDE]
Should we rename the system image to to the current update or do we just use "rootedsystem" as the img. name in the send command?
Click to expand...
Click to collapse
Nope. Leave it as is. The flash command is already set to flash it with that name. Just copy it to your internal SD, put your phone in download/send command mode, then copy/paste the correct string for the H812.
It's all in that thread I mentioned above. Just make sure you use the correct string for the H812, or you will create a nice leather backed door stop.
GibMcFragger said:
Nope. Leave it as is. The flash command is already set to flash it with that name. Just copy it to your internal SD, put your phone in download/send command mode, then copy/paste the correct string for the H812.
It's all in that thread I mentioned above. Just make sure you use the correct string for the H812, or you will create a nice leather backed door stop.
Click to expand...
Click to collapse
I think I understand the question of the person who posted before you. I'm about to root and need to know the following:
Should the command be this:
dd if=/data/media/0/rootedsystem.img bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
or this:
dd if=/data/media/0/system.rooted.rogers.v10b.img bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
Also, what is the command to RESTORE the stock image over rooted one? I want to document all of that on my PC.
I'm not at home to verify if that is the correct H812 string, but the image should be called "rootedsystem.img".
If you get look at the thread I mentioned in the first post, it has the EXACT string you need, just copy and paste it. That way there is no mistyping. bottom line, DO NOT RENAME THE ROOTED SYSTEM IMAGE FILE. It's all in that thread. Read it, and everyone's questions will be answered!
The restore string is the same, with the exception of the file name (system.img vs rootedsystem.img).
Again, all in that thread.
Ramsey said:
I think I understand the question of the person who posted before you. I'm about to root and need to know the following:
Should the command be this:
dd if=/data/media/0/rootedsystem.img bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
or this:
dd if=/data/media/0/system.rooted.rogers.v10b.img bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
Also, what is the command to RESTORE the stock image over rooted one? I want to document all of that on my PC.
Click to expand...
Click to collapse
http://forum.xda-developers.com/g4/...l-variants-soon-root-lg-t3164765/post62028523 This is the thread for injecting root and backing-up sytem .img on various g4 models. your first string is for rooting. but it is wise to backup your system.img first just in case the root flashing is not successful. the command to back-up your phone (h812)is all there just copy and paste. the command for flashing your backup, just erase the "rooted" line just put in "system.img" on the string command and you can flash your system.img backup.
GibMcFragger said:
I'm not at home to verify if that is the correct H812 string, but the image should be called "rootedsystem.img".
If you get look at the thread I mentioned in the first post, it has the EXACT string you need, just copy and paste it. That way there is no mistyping. bottom line, DO NOT RENAME THE ROOTED SYSTEM IMAGE FILE. It's all in that thread. Read it, and everyone's questions will be answered!
Click to expand...
Click to collapse
I did follow the thread in your first post but it tells us to go to another page to get the string and that string actually has the old "system.rooted.rogers.v10b.img" instead of rootedsystem.img!
That's why I wanted to confirm.
Thanks though, it worked fine.
The link posted by gerby has the correct string. Lots of strings online lol.
Um...I used that one too. The link it takes you to is HERE, and it's rootedsystem.img for all the models. I don't know where you read "system.rooted.rogers.10b.img", but it's not where it links you.
GibMcFragger said:
Um...I used that one too. The link it takes you to is HERE, and it's rootedsystem.img for all the models. I don't know where you read "system.rooted.rogers.10b.img", but it's not where it links you.
Click to expand...
Click to collapse
great job
tyfoxx
Oh wow. Thanks a ton! Not looking forward to downloading the whole 4.2gb though
Actually, now that I'm seeing that it's gotten to about 34MB in 5 minutes, it doesn't look like I'm going to be able to do this.
Thanks for doing it though!
Edit: After a router reset, it's going a bit quicker. Still gonna take a long while.
If someone can help with a debrick image.
You need to be rooted and have busybox installed!
Simply run this command as root and upload the image.
Code:
busybox dd if=/dev/block/mmcblk0 of=/sdcard/200MB.img bs=4096 count=50000
This will dump the first 200MB which includes bootloaders and such. No personal info, imei or other sensitive info will be contained in the dump. Greatly appreciate any help.
We can bring them back to life
Thanks.
Can it not be recovered by flashing the full NB1 using Odin?
Sent from my A0001 using Tapatalk
jmjoyas said:
Can it not be recovered by flashing the full NB1 using Odin?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Nope wont turn on, and this method works for the s3, s5, and the notes, maybe even all samsungs
any chance we can get anyone to help with this?
Would this ROM from an i337m help? If it does, I could try to flash it and run the command.
http://www.sammobile.com/firmwares/download/26591/I337MVLUFNC1_I337MOYAFNC1_TLS/
audit13 said:
Would this ROM from an i337m help? If it does, I could try to flash it and run the command.
http://www.sammobile.com/firmwares/download/26591/I337MVLUFNC1_I337MOYAFNC1_TLS/
Click to expand...
Click to collapse
it would help anyone that has a hard bricked i337m, but would not help me on att carrier
I thought it would help because the phone would be booting off the sdcard, not the internal memory like the ATT s3.
I guess the idea is to get the phone booted in order to flash the bootloader and modem to the phone's internal memory? I'm not sure as I haven't dealt with a hard bricked Samsung phone before.
audit13 said:
I thought it would help because the phone would be booting off the sdcard, not the internal memory like the ATT s3.
I guess the idea is to get the phone booted in order to flash the bootloader and modem to the phone's internal memory? I'm not sure as I haven't dealt with a hard bricked Samsung phone before.
Click to expand...
Click to collapse
yea its the booting from sd card. I mean if you are willing to make the file. Ill take it and try.
this phone died with nc1 on it, soo anything would help
Okay, I'll try. Do I run the busybox command from a command prompt on my computer or from a terminal app on the phone? Do I need an sd card in the phone?
Edit: http://www.filedropper.com/200mb
audit13 said:
Okay, I'll try. Do I run the busybox command from a command prompt on my computer or from a terminal app on the phone? Do I need an sd card in the phone?
Edit: http://www.filedropper.com/200mb
Click to expand...
Click to collapse
thank you will try it when i get next to the phone...
edit:
no i think bootloader version might be playing a roll... probably need someone with att nc1.....
I assume it didn't work? Did it attempt to boot at all?
[FIXED] Bricked my AT&T S4 SGH-I337
I bricked my S4 i337 two days ago while looking for a custom recovery. However, I flashed the stock 4.4.2 firmware using odin and it worked like a charm. However it is bootloader locked and you can't install custom recovery like TWRP or CWM except Safestrap.
janshermarri said:
I bricked my S4 i337 two days ago while looking for a custom recovery. However, I flashed the stock 4.4.2 firmware using odin and it worked like a charm. However it is bootloader locked and you can't install custom recovery like TWRP or CWM except Safestrap.
Click to expand...
Click to collapse
did you get your phone working with that img?
can you root and install busybox, then run the command and upload the 200mb.img from your ATT s4?
audit13 said:
I assume it didn't work? Did it attempt to boot at all?
Click to expand...
Click to collapse
nope, didn't boot at all. i had a friend with a busted s3 the same way. looking back on how i fixed it, it was carrier defined on the img and android version
mcmellens said:
did you get your phone working with that img?
can you root and install busybox, then run the command and upload the 200mb.img from your ATT s4?
Click to expand...
Click to collapse
Yeah, I got my phone working again. I have rooted it using towelroot and installed busy box pro.
Tell me which command to run and upload which img file from S4 i337.
janshermarri said:
Yeah, I got my phone working again. I have rooted it using towelroot and installed busy box pro.
Tell me which command to run and upload which img file from S4 i337.
Click to expand...
Click to collapse
in mobile terminal
su
busybox dd if=/dev/block/mmcblk0 of=/sdcard/200MB.img bs=4096 count=50000
This will dump the first 200MB which includes bootloaders and such. No personal info, imei or other sensitive info will be contained in the dump. Greatly appreciate any help.
Yeah. I would gladly do it for you. Just tell me where the dump file is saved.
---------- Post added at 09:19 PM ---------- Previous post was at 09:10 PM ----------
mcmellens said:
in mobile terminal
su
busybox dd if=/dev/block/mmcblk0 of=/sdcard/200MB.img bs=4096 count=50000
This will dump the first 200MB which includes bootloaders and such. No personal info, imei or other sensitive info will be contained in the dump. Greatly appreciate any help.
Click to expand...
Click to collapse
It says applet not found in terminal.
janshermarri said:
Yeah. I would gladly do it for you. Just tell me where the dump file is saved.
---------- Post added at 09:19 PM ---------- Previous post was at 09:10 PM ----------
It says applet not found in terminal.
Click to expand...
Click to collapse
take the busybox part out.. my bad. it should save to the root of sdcard
mcmellens said:
take the busybox part out.. my bad. it should save to the root of sdcard
Click to expand...
Click to collapse
I got this. Where is it located?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
janshermarri said:
I got this. Where is it located?
Click to expand...
Click to collapse
should be on /sdcard