yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] royalflush5:
this is a bit of a stretch, but have you tried stopping the Google Services Framework? that's what a lot of people tried to update their nexus 7s

if you need the files off of a 4.1.2 phone and don't mind giving me some help, I'd provide them to you
[Android Q&A, Help & Troubleshooting] vermillion1:
I am elated to confirm kado01's process works on my SCH-i415 jellybean 4.1.2. Thanks to everyone that worked toward making this happen.

Two caveats:

On my /system there was one additional file I had to take from the sammobile firmware because it was unreadable as non-root (/system/etc/init.qcom.sdio.sh). I assume this file just wasn't present in Android 4.0.4 that the original instructions were made from.

Also, on my first try I forgot to put Superuser.apk in /system/app. Once I had su and Superuser.apk included, everything worked perfectly.

I took the su and Superuser.apk binaries from the supersu gs3 debugfs exploit package on my second attempt, if anyone is interested. On my first attempt, I used the old su binary from my stratosphere 1, which would hang and do nothing for a few seconds before eventually saying "permission denied". But, I believe in retrospect, this was just because the associated Superuser.apk was not installed in /system/app.

If people would like the android 4.1.2 system_rooted.tar file to flash with odin following this process, I can make this available somewhere. I assume it is totally stock, since I didn't have root before now and could not previously write to /system.

I tried to add a download link for my new system_rooted.tar but I'm apparently unable because I haven't posted before now. If you'd like a copy, PM me and I will provide a link (and feel free to repost here for others if they want)
[Android Q&A, Help & Troubleshooting] vermillion1:
I don't know if anyone else is interested, but now with root I was able to improve upon the physical key layout (bring back some important console keys to use in connectbot, mostly). Some of the keys required modification to connectbot source (I've actually been using a modified connectbot source and keymapping for this purpose since the stratosphere 1, which had a way worse original key layout than the strat 2).

The Strat 2 layout I'm using now redefines the magnifying glass key to be tab, the messaging key to be DPAD_CENTER (so it works as control in connectbot), the web key to be regular ascii =/+ key (my modified connectbot turns the +/= key into ascii escape - this indirection was required because the standard escape code did nothing for the connectbot terminal - it is used as the GUI back key instead), and the physical ? key to be the ascii slash and ? key (so ? requires a shift). I type / a lot and ? not so often so this is better for me. And, shift+slash is still pretty easy to type to get an occasional question mark. the original DPAD_CENTER (physical OK key on the keyboard) i've made another shift key because it is in the right place for one and I like a shift on both sides of the keyboard.

Anyway, most of you probably are not interested in this but if you use the terminal a lot and want this feel free to ask me for my sec_keypad.kl and connectbot modifications to use on a rooted stratosphere 2.
[Android Q&A, Help & Troubleshooting] RodimusConvoy:
Well, the only thing is most keyboards have the ability to type Spanish symbols (like ñ, é, etc), so that is most important to me. But the fact that you know how to do all of this is amazing. I'm guessing at the moment you are working on a way to do this through ODIN?
[Android Q&A, Help & Troubleshooting] royalflush5:
I can confirm that vermillion1's 4.1.2 image works flawlessly. Flashed that baby in odin and im all happy. I'd post the link to his image, but as of now I can't, so youll have to pm him for it.

good bye verizonware!
[Android Q&A, Help & Troubleshooting] vermillion1:
I don't know anything about international keyboards on android devices (I'm in the U.S.) How do you type these spanish keys? Is there a key combination?

In any case, if you adjust the key layout, it only changes the specific keys you modify. So, certain keys are just completely unnecessary. The search key, messaging key, web key, etc. So, if you had a different international version of sec_keypad.kl it should be straightforward to just change some of the same keys on the version you started with.

Changing the device key layout is fairly easy with root. It doesn't require ODIN (although, ODIN is still needed to get root initially). It is just a matter of editing a simple file located at /system/usr/keylayout/sec_keypad.kl. If your ADB is in secure mode, it is a bit inconvienent to do it. You have to copy the file to a temporary location, then su in a local terminal on the shell, mount -o remount,rw /system, then cp sec_keypad.kl /system/usr/keylayout, chmod 644 /system/usr/keylayout. The reason for this is apparently adb insecure mode doesn't work with the stock adb in jelly bean. I found a 3rd party insecure adb available in another thread which works well to replace the stock adb and simplify such adjustments, then you can just type 3 commands on your computer:

adb remount

adb push sec_keypad.kl /system/usr/keylayout

adb shell chmod 644 /system/usr/keylayout

sec_keypad.kl is the map for the physical keyboard (strat 1 uses the same name)

there is a generic file qwerty.kl that affects all input (i believe) including the soft keyboard, but I didn't have to edit this one.

There are a few different apps that tell you the scancodes when you press keys so you know what numbers to put in the sec_keypad.kl file.

As far as the connectbot modifications it is just a few small changes in the handling of keypresses and recompiling with the eclipse SDK. I don't have it currently setup, but the copy of connectbot I modified previously for my stratosphere 1 is still working well with my new key layout for my stratosphere 2.
[Android Q&A, Help & Troubleshooting] RodimusConvoy:
I'm in the US, too. :D No, you simply press and hold the regular key. For instance, press and hold "N" and a menu will pop up that will let you choose ñ as well as two other international types of n's (one with a grave mark (tiny forward slash) and one with a small V as a "hat", I don't recognize them but I'm sure one is for Portuguese). If its in uppercase, when you press and hold it the selection will be in uppercase, and the same for lowercase.
[Android Q&A, Help & Troubleshooting] vermillion1:
Oh, yes. I've noticed that now that you mention it. This still happens on my phone with the changed layout, since I didn't change any actual letters (even if I had remapped letters, the remapped letters should have behaved the same as the original).
[Android Q&A, Help & Troubleshooting] kado01:
I'm glad to successfully rooting on 4.1.2

here's some tips:

to backup your phone

dd if=/dev/block/mmcblk0p7 of=boot.img
dd if=/dev/block/mmcblk0p14 of=system.img.ext4
dd if=/dev/block/mmcblk0p18 of=recovery.img

system image is writable for odin3.

UPDATE:

The following method will only work on 4.0.4.

In case of 4.1.2: Look at http://xdaforums.com/showpost.php?p=41211420&postcount=86

to install custom recovery.

Take CWM for Relay 4G from Nardholio's post.

http://xdaforums.com/showpost.php?p=33323044&postcount=469

unzip it and extract cwm.tar.md5 for take recovery.img

Installation as follows:

dd if=recovery.img of=/dev/block/mmcblk0p18

Power on with holding volume up button. it appear recovery mode.

It have some minor issue. but no problem.
[Android Q&A, Help & Troubleshooting] vermillion1:
Thanks for this, I have the cwm recovery image working now.

EDIT: I spoke too soon. After installing the cwm recovery, it first displayed an error about unauthorized software when I tried to boot to recovery. After that, I was able to boot into recovery, and I thought at first it was fine, but I just realized, it's the basic android recovery, not the full featured cwm recovery. So, it looks like the phone detected something wrong and overwrote the new recovery with the original one. The title of my current recovery screen is "Android system recovery <3e>".

---------- Post added at 08:27 AM ---------- Previous post was at 07:52 AM ----------

kado01,

Is there any chance the cwm recovery would work if flashed with odin instead of dd, or do you think it is not compatible with this phone running 4.1.2 yet? Or, would flashing it with odin cause some other problem. I'd like the cwm recovery but it isn't critical for me right now so I don't want to take a chance of bricking my phone.
[Android Q&A, Help & Troubleshooting] kado01:
Hmm..

In my environment, CWM is start up normally.

(LJ2: 4.0.4 firmware)

I guess it seems to security enhancement with latest update.

(maybe on bootloader?)

However, as I have posted before, I'm not be able to download official updater.

Who can ripping updater itself on rooted 4.0.4 firmware?
[Android Q&A, Help & Troubleshooting] vermillion1:
In case anyone else gets the bad idea to try this, I already tried modifying my /system/build.prop ro.build.fingerprint line to identify as the old firmware and maybe download the OTA update again. Apparently there is a sanity check on bootup now and it prevents the phone from booting. It will stop at a black screen before the animated logo and flash the LED. I had to reflash my system img with odin to get the phone working again but it is fine now. Unfortunately I never had root before the OTA update so I never had any chance to save the OTA update previously. I think this is new behavior because in my stratosphere 1 I had to keep my ro.build.fingerprint modified all the time to prevent downloading new updates, and it never caused a problem on that phone.
[Android Q&A, Help & Troubleshooting] :
Just a suggestion, (in the absence of actually unlocking your bootloader) if 4.04 allows custom recoveries but 4.1 doesn't, if someone wants to risk bricking their phone you could try flashing the 4.04 bootloader files to see if that allows you to use custom recoveries. http://xdaforums.com/showpost.php?p=30055671&postcount=241 has a flowchart of the boot process so you can be familiar with it. While you could try dd the safest way to do it would be to take apart a Samsung Odin image from another device to see which partitions are needed. http://hotfile.com/dl/204016374/8aa...m-SGH-T699-TMB-T699UVBMC5-1363439562.zip.html as an example

I do not recommend actually using the partitions from another device since the signing key is probably different and you will end up with a brick.

At this point I would also contact Adam Outler about the possibility of him helping you unlock the bootloader.
[Android Q&A, Help & Troubleshooting] hairoun:
More details...

Thanks so much for this.

I am relatively new to android development so as many details as you can provide will be great for the community.

Thanks
[Android Q&A, Help & Troubleshooting] Illumin8ThaKid:
I tried this before and after the upgrade to 4.1.2 with no sucess
[Android Q&A, Help & Troubleshooting] vermillion1:
Are you just trying to root or do you want your bootloader unlocked. The former problem is solved, but not the latter (at least in 4.1.2; apparently the 4.0.4 bootloader had less protection against replacement)
[Android Q&A, Help & Troubleshooting] Illumin8ThaKid:
I was attempting to unlock the bootloader in 4.1.2 and root kado01 had some sucsess I belive, in any case im still trying to root and unlock with no sucess as of yet
[Android Q&A, Help & Troubleshooting] vermillion1:
I PM'd you the link to the file you can flash with odin on the stratosphere 2 with jelly bean 4.1.2 (MA3 release) to get root (my post count is too low to post the external link in the thread). I think replacing the bootloader after installing 4.1.2 hasn't been done yet.
[Android Q&A, Help & Troubleshooting] FinalCataclsym:
Been following this thread for awhile now as it seems you were the only ones trying to root this wonderful phone. Much appreciated if you could send me the file. (Also sent a PM in case you didn't see this..)
[Android Q&A, Help & Troubleshooting] vermillion1:
I'm just going to try to post this again in case my post count is high enough for it to be accepted, so people don't have to PM me for the link. EDIT: Finally, it accepted the link.

The link to the rooted system image to apply to a Samsung Stratosphere 2 phone running 4.1.2 (jelly bean / MA3) is here:

https://mega.co.nz/#!wZpSURaZ!E3EpjBAbw7KNCiKet2oYvzPmnH1jC0o_39HQyqwlWSs

Just make sure you're already running 4.1.2, because this only replaces the /system partition and I don't know if it would work otherwise.

Setup the usb drivers (same drivers adb uses)

Unzip the downloaded file (it will give you a tar file)

Put your phone in download mode (volume down+power to turn on, volume up to confirm)

Run Odin (I used Odin 3.07). It should detect your phone and say it is ready

Check PDA and supply the tar file for the PDA box.

Flash. It's a bit large and will take around 10 minutes to complete.

This uses the SuperSU version of su. I don't think you need to install SuperSU from the market (it is included in /system/app already) but it couldn't hurt and the market will let you get updates to it.
[Android Q&A, Help & Troubleshooting] royalflush5:
Since all you guys have stratospheres, I wanted to ask you a question while were here. Have you guys experienced a blue screen issue since you updated to 4.1.2? Since I updated mine (4.0.4 had no problems) my phone would work fine, then the screen would without warning turn blue, much like I'm familiar with in windows, and would be unresponsive, forcing me to pull the battery, and holding the power button wouldn't work. I'm just curious because I know of three other strats that have the same problem. Samsung told me to try a factory reset, but I haven't attempted one yet. What do you guys think?
[Android Q&A, Help & Troubleshooting] FinalCataclsym:
All of those instructions worked like a charm. You can truly add Stratosphere II with 4.1.2 to the list of phones with Root/SuperUser. (Going to work on customizing the sounds UI with some Metal Gear Solid stuff now that it is).

As for the blue screen, I only had it happen on one occasion and I believe it was after the OTA update. The thing that was bugging me though since the update is the time it takes to go from complete power off to the main menu. I was really pleased with how fast it was during ICS, but overall it is a minor thing considering I don't fully power it off all that often. I have also done a factory reset since then, plus rooted the phone now, so I won't be able to tell you if either of those things made it better. Not yet at least.
[Android Q&A, Help & Troubleshooting] vermillion1:
That sounds pretty strange. I've never seen a blue screen on mine, and I think it boots up faster than it did when I first got it with 4.0.4. I was actually recently wondering if something had been done in the update to speed the bootup, but to be honest I haven't timed it and I'm not sure at what point the boot time decreased in my case. There is a lot of variation in speed of micro sd cards, though, and I did upgrade mine awhile back with a nice newer-model 64gb sandisk one, which is faster than whatever I used to use before. You might want to check the boot time with no sd card installed to remove that as a variable (a sluggish one might slow during routine checks on startup). But, maybe my perspective is off and I'm just remembering my stratosphere 1 boot time being much, much slower than the stratosphere 2 in either firmware version.
[Android Q&A, Help & Troubleshooting] annoyingduck:
Do I smell a development page appearing soon.....
[Android Q&A, Help & Troubleshooting] royalflush5:
You need to post screenshots of the MGS themes, I'm a huge mgs fan :)

I'll try a factory reset, then re root it, thanks

That would be awesome!
[Android Q&A, Help & Troubleshooting] poppagenek:
Could someone post a link to the rooted system image for the Stratosphere still running 4.0.4?
[Android Q&A, Help & Troubleshooting] kado01:
4.0.4 rooted system image is here.

Only including xbin/su. It is necessary to install SuperSU at Google Play.

https://mega.co.nz/#!eN4TFAjY!Qf15sAndXHCTAoM1w4ZKzV4paqYUdhDRqEYGFMUyfcY

I would be glad if you can ripping OTA update file and sharing it.

I'm trying various now (installing 4.1.2 system image on LJ2 bootloader / modifying system service / etc.)

But I have not enough time now.

I report later.
[Android Q&A, Help & Troubleshooting] siapplebaum:
Link for Stock 4.1.2 Firmware?

Just in case we need the stock Firmware to get an OTA update (I've actually been having tons of problems with my phone since the recent 4.1.2/MA3 update, with keyboard issues, fairly consistent hangs, and random reboots), does anyone have a download link for that 4.1.2 firmware?

Thanks again to all who generated this rooted firmware.
[Android Q&A, Help & Troubleshooting] vermillion1:
I don't think you'll find a pristine copy currently because some generic init scripts / conf files were not readable as root. These had to be extracted from an alternate phone's firmware (They were probably essentially the same if not completely identical, but it isn't guaranteed). Also, it is a re-made ext4 filesystem, which shouldn't really matter at all, but technically various metadata or filesystem parameters could have minor differences that don't affect the running system, but which a future OTA update might possibly be able to check for if it tries to prevent updating a modified phone. We won't know for sure if this is an issue until the next OTA is released. Basically, the only way to get root was to replace the system tar with a slightly modified image. Now with root, it was possible to read the system image, but since you've already replaced it, you can't get the old one. If a new exploit becomes available, maybe it would be possible to root the original copy of the system. There is some new exploit called motochopper that has worked on some recent 4.1.2 phones. It also worked on an old an old Asus TF201 tablet of mine which had been stuck unrooted for several months after it was upgraded to JB before being rooted to begin with. I only mention that to show that the motochopper exploit might be fairly generic and work on a variety of devices. I haven't heard of anyone trying it on a Stratosphere 2, so I don't have any idea if it would work. But, if it did work on the strat 2, it might be a route to get a more correct copy of the original firmware. However, if you want to just remove all 'practical' differences from my image, it is as simple as running in a terminal on your phone:

mount -o remount,rw /system

rm /system/bin/su

rm /system/xbin/su

rm /system/app/Superuser.apk

This would essentially remove the root as best as possible without being able to extract the original firmware differently.
[Android Q&A, Help & Troubleshooting] :
Speaking of original firmware for your phone, if your phone is anything like the Verizon SGS III (and I think it is) with Kies even locked out the only way you're going to get original firmware and an unlocked bootloader is a leak from inside Samsung. You should contact Adam Outler, he couold probably assist you with this or in working his magic and getting the bootloader hacked a different way.
[Android Q&A, Help & Troubleshooting] poppagenek:
Thanks it worked lke a charm. The only tricky part for me was the download kept freezing at or below 36% using IE and Firefox. Once I tried chrome no freeze on the download. Next step is to figure out which files to freeze in order to keep the phone on ICS and prevent for now the update to jellybean.

It turns out that i needed to freeze or remove SDM. I used titanium pro to freeze it and no OTA firmware updates for now.
[Android Q&A, Help & Troubleshooting] oostah:
well i have bricked i can get to qpst mode only. any one have any files i can load in qpst mode. or any ideas to unbrick. thanks

i have another phone that is not rooted if there is a way i can pull the files from.
[Android Q&A, Help & Troubleshooting] royalflush5:
ouch... what were you doing, if you don't mind telling?

Maybe if someone could send you a clean nandroid backup from a phone? I dont have cwm on any of my phones because my linux box went south, so if you know a method for flashing cwm on this in windows I'd happily send you something you can flash on your phone
[Android Q&A, Help & Troubleshooting] oostah:
im running windows and the only thing that reads the phone is QPST. im willing to try any thing if you have to flash to the phone. im going to try using qpst tonight to see if i can pull anything off my wifes phone and flash it to mine.
[Android Q&A, Help & Troubleshooting] vermillion1:
Does QPST not use the same downloading mode as ODIN?
[Android Q&A, Help & Troubleshooting] oostah:
It only reads in QPST so im not sure

im trying to get my wifes phone in qpst mode not sure how
[Android Q&A, Help & Troubleshooting] vermillion1:
So what exactly did you do that caused the problem? Was it it from flashing in ODIN or something else you did after obtaining root? I'm not familiar with QPST or if it can backup or restore anything, but I assume it would require root if it does anything like that.

ODIN shouldn't have flashed anything but the system partition and the normal download mode shouldn't be affected by that so I don't know how that would brick it unless something randomly failed mid-flash (I flashed a non-working system myself and was able to reflash with ODIN again).

Did you verify that the drivers ADB drivers for odin didn't just break (you can still see other phones with ODIN)?
[Android Q&A, Help & Troubleshooting] oostah:
i was trying to unlock bootloader. yes all drivers are there. i made a back of my wifes phone with qpst. but it reads as in download mode not diagnostic so i can load that back up.
[Android Q&A, Help & Troubleshooting] 9lz:
Got my strat II here yesterday, as I am addicted to full qwerty phones, I had to import one from the US to get it (I am in Norway).

Got it rooted (thanks kado01).

But wondering about 2 things;

---Cannot get APN settings to work (used BuildProp Editor to get permission to add APN), all the settings are correct and triplechecked. (could be some other VZW lock I'm not aware of?)

---Would be nice to get mobile data working.

Got this working with APN Manager Pro.

Cannot get OTA update to 4.1.2, running 4.0.4 now. OTA update first said "service unavailable", but now it just says I am up to date.

Has anyone got a full 4.1.2 firmware for this that I can flash with Odin yet? (sadly kies does not support this phone atm)

Thanks for all the progress on this model, really saves my day :good:
[Android Q&A, Help & Troubleshooting] RodimusConvoy:
So Verizon basically has, well, booby traps when you try to get into the settings of the phone? I'm getting the impression that's what's making it difficult to root, but not impossible anymore. So, progress. :laugh::good:

Can you update through wifi?
[Android Q&A, Help & Troubleshooting] kado01:
I got able to update LJ2(4.0.4) to MA3(4.1.2), without OTA.

And I have confirmed that custom recovery will not boot on MA3.

I tryed downgrade to LJ2 bootloader. It seems to working well.

to install CWM (on MA3):

Get root on MA3.

Download LJ2 bootloader (attached) and cwm.tar.zip (http://xdaforums.com/showpost.php?p=33323044&postcount=469).

Unzip it and extract cwm.tar.md5 for take recovery.img

Install as follows:

su
dd if=I415LJ2_aboot_p5.img of=/dev/block/mmcblk0p5
dd if=recovery.img of=/dev/block/mmcblk0p18
mount -o rw,remount /system /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.org

Power on with holding volume up button. It appear recovery mode.

This process is very dangerous because reflashing bootloader.

Has worked in my environment (manually flashed boot chain / bootloader / baseband / kernel / system), but have not tried on environment that has been updated by OTA.
[Android Q&A, Help & Troubleshooting] bgoode2006:
Would it be possible to completely downdrade from 4.1.2 to 4.0.4 with this image?