Hi all -
Model SAMSUNG-SGH-1337
Baseband: 1337UCUAMF3
Build: JDQ39.1337UCUAMF3
First off, I have an Samsung Galaxy S4 ATT SGH-1337. I have lurked around these forums and have come to understand the rooting / recovery flash processes. Getting root on the phone is no problem using the following method: http://forum.xda-developers.com/showthread.php?t=2387577
Where my issue lies is within the recovery mode. I have tried GooManager / RomManager / CASUAL /ODIN and nothing I try seems to work. It short when I use CWM or GooManager or CASUAL everything works correctly and I receive no errors. When I first tried this i used GooManager and when it went to reboot into recovery mode It said COULD NOT DO NORMAL BOOT and put me in download mode - in short my stock recovery mode is gone/corrupted.
No matter what I try via (STOCK FW load for example) ODIN i always get a FAIL and can not get it to work. It should be noted that I have the correct USB driver installed also official USB cable and I've tried many versions of ODIN with the same result. It looks like it always fails on write. When I re-try the other methods to install a custom recovery they seem to work but I end up with the same COULD NOT DO NORMAL BOOT.
I thought I was stuck in this download mode until I rebooted the phone manually put in download mode and smashed VOL-DOWN. When I did this the phone booted up.
The strange part is that I have root, and can get into the OS, but all the recovery methods seem to fail. I have even tried the DD method via TWRP page with no luck.
I do not understand why this is the case, or why when I first did this with Goomanager it hosed my recovery mode. I am literally out of ideas, and have tired everything I can think of to get a recovery mode installed.
It should be noted that all the "gotya's" are enabled such as USB Debugging, and version verification. I do notice that when download mode appears, and i see COULD NOT DO NORMAL BOOT it does say "WRITE PROTECTION ENABLED". From my Googleing it would appear this is ok.
I have also made sure I was using the LOKI exploit; but it simply seems that my bootloader is locked no matter what I try.
If anyone has any ideas I would greatly appreciate it.
Thanks
-Ya5e
Ya5e said:
Hi all -
Model SAMSUNG-SGH-1337
Baseband: 1337UCUAMF3
Build: JDQ39.1337UCUAMF3
If anyone has any ideas I would greatly appreciate it.
Thanks
-Ya5e
Click to expand...
Click to collapse
One thing I could think of trying is taking a look at this video here on how to install CWM Recovery on the ATT Galaxy S4. As you watch the video make sure you've done everything exactly as he has done in the video, this way you can determine if you have overlooked or missed any steps.
Thanks for the video link. However it looks like this won't work due to the MF3 firmware.
Q6: I have a AT&T S 4 (OTA MF3) and I have rooted my device can I install a custom rom or a custom recovery?
The answer is "NO" you can not install a custom recovery or a rom at this moment.
Click to expand...
Click to collapse
I found the above in this thread http://forum.xda-developers.com/showthread.php?t=2413746&nocache=1
My phone came with MF3; I would assume this is the issue.
=(
Related
Hello Everyone,
Firstly, I need to say that as a previous owner of an original droid, I was able to root it with no problems on the first go around. However, as a new owner of a Samsung Galaxy SII I am finding root a real challenge.
I have no problems getting into download mode and so on....I have successfully placed the clockworks rom onto the phone with again no problems and I have all the drivers working properly. I guess this is where I am obviously an idiot....because I start the Super One Click and it gets to Step 6 and then stops. I unplug the USB....click the debugg off and then back on and reconnect my USB like directed by many posters. However, in my case it will not continue on and finish the install.....
I reboot and do get the small triangle on boot up ( not that I care too much about that really...do have a jig on order however) but I simply can't seem to get it to root.
Again I have followed all the posts and guides for unplugging, unchecking and rechecking the debugging and then plug back in the USB and still nothing.
Phone works fine....everything works...love the phone...just seems puzzling to me. I have Odin 1.82, I have SuperOneClick 2.1.1 and like I said installed the .tar fine to the phone with no worries....just cant get it to root.
Any advice?
i used (this) with no issues.
Does your phone currently have the new KJ1 update? I've read that this new update will not root with the usual methods.. (I could also be wrong...)
RE: Rooting
TheElectricalGuru said:
Hello Everyone,
Firstly, I need to say that as a previous owner of an original droid, I was able to root it with no problems on the first go around. However, as a new owner of a Samsung Galaxy SII I am finding root a real challenge.
I have no problems getting into download mode and so on....I have successfully placed the clockworks rom onto the phone with again no problems and I have all the drivers working properly. I guess this is where I am obviously an idiot....because I start the Super One Click and it gets to Step 6 and then stops. I unplug the USB....click the debugg off and then back on and reconnect my USB like directed by many posters. However, in my case it will not continue on and finish the install.....
I reboot and do get the small triangle on boot up ( not that I care too much about that really...do have a jig on order however) but I simply can't seem to get it to root.
Again I have followed all the posts and guides for unplugging, unchecking and rechecking the debugging and then plug back in the USB and still nothing.
Phone works fine....everything works...love the phone...just seems puzzling to me. I have Odin 1.82, I have SuperOneClick 2.1.1 and like I said installed the .tar fine to the phone with no worries....just cant get it to root.
Any advice?
Click to expand...
Click to collapse
Try this rooter "su-3.0-efgh-signed.zip".
Here is the link for it: http://www.megaupload.com/?d=LBTUWW1J
After downloading copy the zipfile to your sdcard and flash it in
CWM recovery just like you would flash a rom using the option
"Install zip from sdcard" in CWM.
When its done reboot the phone and it should be rooted.
Misterjunky said:
Try this rooter "su-3.0-efgh-signed.zip".
Here is the link for it: http://www.megaupload.com/?d=LBTUWW1J
After downloading copy the zipfile to your sdcard and flash it in
CWM recovery just like you would flash a rom using the option
"Install zip from sdcard" in CWM.
When its done reboot the phone and it should be rooted.
Click to expand...
Click to collapse
that file is in the link I posted above...just an FYI.
I tried using the "su-3.0-efgh-signed.zip" and it failed.
so I managed to root my device without bricking it
and now I needed the twrp recovery thing so I could install cm 10.2
now I followed some tut on youtube that told me to use flashify which I did and I then downloaded some old version of twrp with it
when I rebooted my device it said safe reboot error or something.. and now it does nothing (freaking out here)
it won't turn on even when I try to reboot into recovery when I put it in my pc it shows like 10 storage devices that I need to format
pleasse help me (I had this phone for less than a week now))))))
ipsmaxes said:
so I managed to root my device without bricking it
and now I needed the twrp recovery thing so I could install cm 10.2
now I followed some tut on youtube that told me to use flashify which I did and I then downloaded some old version of twrp with it
when I rebooted my device it said safe reboot error or something.. and now it does nothing (freaking out here)
it won't turn on even when I try to reboot into recovery when I put it in my pc it shows like 10 storage devices that I need to format
pleasse help me (I had this phone for less than a week now))))))
Click to expand...
Click to collapse
First step: Don't panic!
Second step: Tell us which version of the G2 you have (carrier) and which update you had on before things went south, and also which version of TWRP you have.
Third step: Please explain what you mean by it not turning on but plugging it into the PC shows odd things.
Does that mean you CAN still get into recovery? Can you get to download mode? But either way, just stay calm. I just helped my buddy with the ATT version fix his phone from a similar issue a couple of days ago and I have also played with the Sprint version quite a bit and am familiar with LGs in general. Lemme know these things and I can help get you back on the right track.
Can you get into recovery mode?
If you can, try the factory reset and reboot your device.
Does your phone connect to adb?
If so i guess you could flash a fresh rom from there.
Correct me if i'm wrong, i am a new user with slight experience.
Same Thing Happened to Me
I'm freaking out a bit as well. I tried the Flashify method of installing TWRP and got the error message followed by a blank unresponsive phone. Got there via a "Phone Tech Kid" video explaining how to install TWRP. Plugging it into my computer results in being able to open a "drive" with one folder titled "image". The image file that I flashed is 2.6.3.2-g2vzw obtained via a link from this video:
Has anyone come up with a solution?
alferdjeffers said:
I'm freaking out a bit as well. I tried the Flashify method of installing TWRP and got the error message followed by a blank unresponsive phone. Got there via a "Phone Tech Kid" video explaining how to install TWRP. Plugging it into my computer results in being able to open a "drive" with one folder titled "image". The image file that I flashed is 2.6.3.2-g2vzw obtained via a link from this video:
Has anyone come up with a solution?
Click to expand...
Click to collapse
Probably would be best to start your own thread. However, what update were you on? I'm hoping that you do have the Verizon version of the G2? What error is on the screen? But generally speaking, you should be able to boot to the software update mode and re-install the stock OS with the kdz file, for most G2 things. I haven't worked on a VZW one though, only Sprint and T-Mobile ones and they're all a bit different.
Hey guys... So I'm REALLY new at this whole rooting thing, so please forgive me if I am not aware of any terms related to rooting and such.
So basically what happened was this:
I decided to root my Galaxy S4 (sgh-i337 --- AT&T) using the towelroot method. I had to use this method because my phone is currently running Android 4.4.4 KitKat (TouchWiz) and it worked fine. SuperSU was installed, Root Checker said my phone was rooted, it was good. I tried to install CWM using Odin, and I got the "RESET" or "PASS" from Odin, which I thought that it meant that it worked. However, when I tried to go into Recovery Mode, it went into Stock Recovery Mode. I started to look at other tutorials, and I came across another one that involved flashing your phone's respective CWM .img file from your phone itself (transfer the .img to your phone's SD, and then flash it from your phone using the app, Flashify). But when I tried to go into Recovery mode to see if it worked, it gave me the yellow triangle with an error message, "System software is unauthorized by AT&T" or something like that. I tried to look at other posts, and there was a general idea that I needed to flash the stock Kernel. Now, the way I rooted the phone in the first place, I already had two different ones downloaded. One was flashed, towelroot was used, and then the second kernel (which was the one that originally on my phone before rooting) was flashed. After that, it was rooted. So me, being the complete noob I am at rooting, decided to re-flash both, in order, to see if that cleared up the error message when trying to get into Recovery Mode. This did not solve the problem either.
Again, I would like to apologize for my lack of knowledge on rooting and such, so please forgive me for my incompetence. And yes, I know that there are other threads on topics like this, but I have tried several things and it has not worked. Any help on how to fix this problem (and how to install CWM properly on my phone - since it is updated to 4.4.4 TouchWiz - or if I should use TWRP instead, because I intend on downloading the Kangapop GPE ROM(and how to install that for my specific model/software version)) is greatly appreciated, thanks!
i know this is a newer phone but i'm still pretty surprised i haven't been able to find anyone that's rooted it yet. i've been all over the internet it seems. this is the :
Samsung Galaxy J3(6)
SM-J320VPP
Android 6.0.1 Marshamllow
Verizon pre-paid plan/network
i see lots of videos and guides for other j320f or j320p (close but no cigar) and nothing works. what i've tried so far:
- Dev mode enabled, USB debugging and OEM unlocked.
- any/all 1 click root apps. none worked, and i'd like to avoid these anyway unless you know it works 100% for my version. at this point i'll try anything.
- recovery / flash superSU. only i haven't even gotten past flashing a recovery. i've tried several different versions of Odin with several different versions of recovery .tar's and for each combination i've tried Odin simply fails. big red FAIL button in upper left corner. sadness. this seems like what i need help with. i have SuperSU downloaded so if i can just get a custom recovery working for my phone i'm hoping it's a simple process from there of booting into the custom recovery and then installing the SuperSU. presto.
is there no hope? is there no tested, confirmed working recovery that i can flash to my phone using Odin? i've tried Odins 3.07, 3.09, and 3.11.1. various custom recovery .tars but the only one i know for sure is the J2 version official from TWRP's website (yes i know it says J2 but someone on another thread said it's similar enough to someone ELSE's model "j320f" or something so i gave it a shot) the other recovery .tars i tried are suspect since they had generic names "recovery.tar" and were downloaded from links provided in many different "guides" that i've googled.
internet, you have failed me. thus do i issue this challenge to all those mighty phone hackers of the land. come forth and slay the evil giant that is my phone's ludicrous security (seriosuly how is this even a thing still in 2016. my phone can do so much more, so much better but for these shenanigans).
thanks so much in advance!
EDIT: not sure about the bootloader. i may be a complete idiot. yes. ok. i'm onto something. gonna post this anyway for any other poor soul that has this version phone, but i think Odin's probably failing because the bootloader is still locked. and Samsung doesn't make this easy like motorola or HTC. T_T. once more into the fray! i'll see if i can't track down a method for unlocking the bootloader on my phone. should i return victorious i'll go ahead and share my steps with the rest of the class.
EDIT2: there is no waking from this nightmare. i dig and dig and dig and can find no root. *sigh*
-- i've got android studio installed. and the java SDK platform-tools which contains the adb.exe, fastboot.exe, etc.
-- something i should explain here: in all these guides whenever there's a step that requires the phone to be connected to the PC, it simply says to, you know...connect your phone. but MY phone by default only uses the cable for battery charging. i have to (on my phone) swipe down from the top, select the "connected for charging" message bringing up "Use USB For" options, then select "Transferring media files" option. THEN my phone shows up both in my windows explorer and displays as a device when i run "adb devices".
--when i run "adb reboot bootloader" this does the same thing as holding down pwr/home/vol down - phone boots up into a blue (teal?) background with a large down arrow in center, below that it says "downloading...do not turn off target". in the upper left are several lines of system font style text:
ODIN MODE
PRODUCT NAME: SM-J320VPP
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: OFF*
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, H1, R1, A1, P1*
SECURE DOWNLOAD: ENABLE
*the R's above may be A's or vice versa...hard to read font. sorry
--but as soon as i've rebooted into this mode, my phone disappears from adb devices' list of devices attached. regardless when i run the "fastboot oem unlock" command from the adb shell on my PC at this point i get the infamous "waiting for any device" message and then, of course, nothing....forever. i've also installed PDAnet but i think it's hitting the same road block where my phone is only using the cable for battery charging and i can't toggle that option from ODIN MODE. there's also a "USB Configuration" choice under development options on the phone that has the same options as "Use USB for" but this doesn't stick when booting into ODIN MODE. sadness. i need to retire my brain thoughts at this point. will post TL;DR. you're a saint of geeks if you've made it through my WoT to here.
EDIT3: just an observation - the only thing (so far) that will detect my phone in ODIN MODE is ODIN itself. is there a way to use ODIN to unlock the bootloader?
TL;DR: i think odin is failing when attempting to flash because of locked bootloader. need help with unlocking bootloader first? phone defaults to use USB cable for charging only so i CAN change that to MTP while phone is on normal and then run "adb reboot bootloader" but then phone vanishes from adb devices list once it reboots (and cable is then only charging). thus, cannot run "adb fastboot oem unlock" cuz it hangs displaying "waiting for any device" -- can i unlock the bootloader on this phone? or did i buy a phone that's IMPOSSIBLE TO ROOT!?!?
I have the same problem! I need to root it to install the Patch to change from CDMA to GSM! Because I tried without root and it tells me "E: Signature verification failed"
Thanks
Still nothing?
This is starting to look hopeless
we need the stock recovery.img to be able to mod it and flash it through odin. the recovery for the verizon version does not match so odin wont allow it. i asked on sammobile and they said verizon only releases ota on the device. so idk what to do. perhaps someone with knowledge on this will help.
so far what ive figured out our situation is:
we need root to get root.
more specifically we need root to pull the recovery and then mod that recovery with twrp and use twrp to gain root. The root methods that worked for the other variant SM-J320P dont appear to work for ours, probably due to having android 6.0.1
till we get root we are stuck. the rest is easyish
News?
There is nowbody that had been rooted his J3 Verizon yet?? We need help with this trouble!
In this forum (http://forum.xda-developers.com/android/help/galaxy-j3-sm-j320vpp-configuring-cdma-t3414049) Sergio said:
" try root with this root is only for Snapdragon 410 MSM8916
http://forum.gsmhosting.com/vbb/f723...t1994-1946985/ "
The J320VPP has a "1.2 GHz, Quad-Core". There is no place that sais it's a "Qualcomm Snapdragon 410 Msm:8916" processor. You think this suggestion could work?
NerdmastaX said:
we need the stock recovery.img to be able to mod it and flash it through odin. the recovery for the verizon version does not match so odin wont allow it. i asked on sammobile and they said verizon only releases ota on the device. so idk what to do. perhaps someone with knowledge on this will help.
so far what ive figured out our situation is:
we need root to get root.
more specifically we need root to pull the recovery and then mod that recovery with twrp and use twrp to gain root. The root methods that worked for the other variant SM-J320P dont appear to work for ours, probably due to having android 6.0.1
till we get root we are stuck. the rest is easyish
Click to expand...
Click to collapse
I think I've managed to get the recovery.img with KIES... However flashing the image I've extracted doesn't work but if anyone is ready to help me port a recovery I might try !
Whusky said:
I think I've managed to get the recovery.img with KIES... However flashing the image I've extracted doesn't work but if anyone is ready to help me port a recovery I might try !
Click to expand...
Click to collapse
im gonna try and do a reflash with kies and grab that file myself, ill work a bit on it because i love this phone but no basic root is driving me insane. if you can beat me to posting tell me how you got the file, otherwise ill post here once i find out. I'm not a top of the line developer but i can work my way around and try my best since nobody else is offering to help.
wish me luck.
sorry for the double post but got the files via the verizon software assistant no problem. it ended up in C:\Users\YOURNAME\AppData\Roaming\Verizon_AR\SM-J320VPP_J320VPPVRU1APC3_FACTORY for me, and even decrypted and unzipped itself for me, now we just need to mod a custom thingy into those files and we can work towards rooting. so as i sit here and watch my phone finish flashing back to factory i will look into how we can mod the recovery. if someone is capable of doing it faster i can upload the files very quickly as its only 1.4 gb
well turns out verizon locks the flashing with signature verfication. so unless verizon changes or root is found for marshmellow there will be zero possible root for this phone.
NerdmastaX said:
sorry for the double post but got the files via the verizon software assistant no problem. it ended up in C:\Users\YOURNAME\AppData\Roaming\Verizon_AR\SM-J320VPP_J320VPPVRU1APC3_FACTORY for me, and even decrypted and unzipped itself for me, now we just need to mod a custom thingy into those files and we can work towards rooting. so as i sit here and watch my phone finish flashing back to factory i will look into how we can mod the recovery. if someone is capable of doing it faster i can upload the files very quickly as its only 1.4 gb
Click to expand...
Click to collapse
Hi I'm currently rooted with TWRP 3.0.2 recovery and mabey this might help http://forum.xda-developers.com/general/help/samsung-galaxy-j3-sm-j320fn-how-to-root-t3369511
Sparko612 said:
Hi I'm currently rooted with TWRP 3.0.2 recovery and mabey this might help http://forum.xda-developers.com/general/help/samsung-galaxy-j3-sm-j320fn-how-to-root-t3369511
Click to expand...
Click to collapse
verizon blocks flashing of modified recoveries. so unless someone finds a root exploit for marshmallow we will have no luck.
Has the kingroot method worked for root on your device ??
NerdmastaX said:
we need the stock recovery.img to be able to mod it and flash it through odin. the recovery for the verizon version does not match so odin wont allow it. i asked on sammobile and they said verizon only releases ota on the device. so idk what to do. perhaps someone with knowledge on this will help.
so far what ive figured out our situation is:
we need root to get root.
more specifically we need root to pull the recovery and then mod that recovery with twrp and use twrp to gain root. The root methods that worked for the other variant SM-J320P dont appear to work for ours, probably due to having android 6.0.1
till we get root we are stuck. the rest is easyish
Click to expand...
Click to collapse
Hi to all, im new here and i am having the exact same problem! You say that there has to be a root specifically for the 6.0.. So i found that in the Chainfire page they have this https://download.chainfire.eu/986/CF-Root/CF-Auto-Root/CF-Auto-Root-j3lteusc-j3lteusc-smj320r4.zip already (i dont know if i can post links, so if i cant, sorry), it is marshmallow but the model is J320R4, so i was wondering if this could be the solution. i'll be waiting here for a response, i seriously love this phone :c
MetAJFA said:
Hi to all, im new here and i am having the exact same problem! You say that there has to be a root specifically for the 6.0.. So i found that in the Chainfire page they have this https://download.chainfire.eu/986/CF-Root/CF-Auto-Root/CF-Auto-Root-j3lteusc-j3lteusc-smj320r4.zip already (i dont know if i can post links, so if i cant, sorry), it is marshmallow but the model is J320R4, so i was wondering if this could be the solution. i'll be waiting here for a response, i seriously love this phone :c
Click to expand...
Click to collapse
No, this is not the solution. When using a utlity like CF Auto Root, it must be specific to your model / carrier. Trying to install that will do 1 of 2 things.
1) Just fail in Odin
or
2) Soft brick your device
Since VZW doesn't bother to put out the full firmware files to reflash the device, it's not worth attempting without having the backup plan of the original firmware to flash via Odin.
an twrp is already available for j320p u can try to root your device using it
es0tericcha0s said:
No, this is not the solution. When using a utlity like CF Auto Root, it must be specific to your model / carrier. Trying to install that will do 1 of 2 things.
1) Just fail in Odin
or
2) Soft brick your device
Since VZW doesn't bother to put out the full firmware files to reflash the device, it's not worth attempting without having the backup plan of the original firmware to flash via Odin.
Click to expand...
Click to collapse
Understood, thank very much you for clearing that out. Since all this is pretty much a kick in the butt, do you think there will be some kind of solution to this or should we just lose hope? :/
can Someone here help me with this.
someone wrote:
I have the same problem, I already got 4G LTE data with the correct APN and also I change to lte/gsm with the help of a network app and with commands in adb shell :
pm clear com.android.providers.telephony
settings put global preferred_network_mode 9
settings put global preferred_network_mode1 9
settings put global preferred_network_mode2 9
Click to expand...
Click to collapse
but i dont know how to initiate this adb mode in the phone. anyone?
anyone fix ?
i have few units J320VPP same problem .. searching for service .
That's a Verizon device with a locked bootloader, you cannot try twrp or modified files meant for 320f or other models on this one.
Sent from my SM-N920G using Tapatalk
So has anyone found any luck with this device? It's driving me crazy not having root
Hi, everyone. I've successfully rooted several Android phones in the past, but this one's got me stumped. Has anyone successfully rooted this specific model, and if so, how?
I have a J1 mini prime, specifically a J106M. It is running Marshmallow 6.0.1 with a pending update that I've paused. I was under the impression the bootloader would be unlocked since it's not tied to a carrier. I now assume it isn't because I've tried:
kingoroot, kingroot, iRoot, towelroot (doesn't work with modstring codes either), latest framaroot (device not vulnerable to exploits error), framaroot 1.5.3 (same error), chainfire (causes soft brick bootloop, but has since been restored).
I can't even figure out how to verify if the bootloader is unlocked for sure. I tried using ADB. cd fastboot command simplay restarts the phone, and fastboot oem unlock command my phone or just sits there saying "waiting for device."
When I boot the phone holding down the volume, home, and power buttons, it brings me to a blue screen that I believe is Odin mode. Others seem to get a different screen that has the bootloader info right there.
It's been a few weeks since I've had time to mess with this. I'm pretty sure that's everything I attempted.
To verify, I have developer mode on, OEM unlocking on, debugging on, allow unknown sources on.
Other specs:
Baseband version : J106MUBU0AQF1
Kernel: 3.10.65-11653963
Build: MMB29Q_J106MUBU0AQF2
Thanks in advance to anyone who can assist a semi-noob. I've never posted on a forum before, and I'm not usually one to ask for help, but I'm out of ideas here lol.
Hello Bahamut,
Are you familar with the Odin tool flashing Samsung firmware? If yes, there is a universal root method Magisk root. There are two ways to root using Magisk:
1. install a TWRP recovery (flash by Odin) & install Magisk Root using TWRP recovery
2. Extract boot.img from the firmware; modify it by Magisk apk; flash the modified img by Odin.
Both ways successfully rooted my Samsung J3 Pro. I've google search for a while & see firmware/TWRP are available for your device J106M.
You should study Odin, Magisk before you go ahead.
Thanks. Somewhat familiar, I was saving that as a last resort out of apprehension that I completely brick the device lol I used Odin when attempting the chainfire files.
I forgot I had downloaded TWRP at one point, but I must be missing something because it appears to be a catch 22 as TWRP was asking for root access in the first place to perform this function. Is there a work around such as using a PC version instead of the app or am I just way off base here?
If TWRP recovery has a problem, you could try method 2 which involve Odin flashing only.
chankk0101 said:
If TWRP recovery has a problem, you could try method 2 which involve Odin flashing only.
Click to expand...
Click to collapse
Unfortunately, the Odin flashing is how I wound up soft-bricking it twice and decided I'd need assistance on this model. I was hoping someone could walk me through it with the specifics, but I guess this isn't a very popular phone.: