[Q] Am I being SCAMMED with this M919 purchase? - T-Mobile Samsung Galaxy S 4

Hi:
I bought a Galaxy S4, SGH-M919 (Supposingly from T-mobile?).
When I unboxed it and power on, it appears to have a 4.2.2 ROM (M919 XXUAMC6) from another region (Great Britain or something?).
I can't flash any T-Mobile stock firmware (>=4.3) back into the phone with Odin (always showing failed security check: sbl2 ....).
Also the custom rom install counter is 10 ...
The seller was selling this phone as brand new, also it came with all original packaging.
Just wondering how is that possible?
Am I being scammed?
:cyclops:
Thanks!

Maybe. Or maybe they shipped the wrong phone.. Get Samsung phone info from playstore and check what bootloader it has

serio22 said:
Maybe. Or maybe they shipped the wrong phone.. Get Samsung phone info from playstore and check what bootloader it has
Click to expand...
Click to collapse
Thanks for the reply.
But I believe my phone is soft bricked when I valiantly(blindly) flashed a wrong ROM into my phone.
Now I just want to get my original firmware back.
However it appears that I'm the only one with M919XXUAMC6 rom on the internet.
Is this real life, lol.

guruqu said:
Thanks for the reply.
But I believe my phone is soft bricked when I valiantly(blindly) flashed a wrong ROM into my phone.
Now I just want to get my original firmware back.
However it appears that I'm the only one with M919XXUAMC6 rom on the internet.
Is this real life, lol.
Click to expand...
Click to collapse
You shouldn't have tried to mess with it.. Anytime you see something abnormal in a purchase you should investigate and contact seller but ok, what did you flash and did you factory reset?

I followed an instruction and did a full wipe on my device, data and cache. And I realized Odin can't flash in the room. That's when I got stuck. But I can still boot into cwm and download mode though.

Under the battery, what does it have for a model number there?

Model: SGH-M919
FCC: A3LSGHM919

Post your bootloader. There has been a wave of franken S3's lately with parts from different S3's claiming to be another S3 model. Hopefully that is not the case with your device

Wait, but mine is M919 which should be a S4 right?
Also since I'm semi-bricked already, how do I get bootloader information?
I could try to mount boot block in TWRP and pull up something?
Any suggestion on how to do this?

Try to flash CM, the one for jflte, since its universal it may get you booted
Edit: also don't forget to factory reset

No good. Tried cm-11-20140804-SNAPSHOT-M9-jflte.zip .
When I install the file, it gave me
set_metadata_recursive: some changes failed
E: Error executing updater binary in zip '/xxx/xxx'
Error flashing zip 'xxx/xxx'
Click to expand...
Click to collapse

Try downloading again

Tried the same Rom, redownloaded, same message.
I also tried using this Rom from this thread (Stock Deodexed + Rooted ROM (v1.3))
http://forum.xda-developers.com/showthread.php?t=2679913
Installing the Rom from TWRP appeared to be successful, however, when I try to restart TWRP still shows me "There's no OS installed".
And the boot hangs on Samsung Logo.

Are you using latest twrp? If so try CWM and latest cm nightly

I'm using TWRP and CWM provided here
http://galaxys4root.com/clockworkmodtwrp-recoveries/
But nope, it is still the same thing.
Symlink: some symlinks failed.
Installation Abort
Click to expand...
Click to collapse
Is there a way to see the actual installation log? At least i can know which symbolic link is down.
Also whenever I tried to flash using Odin something other than recovery, it gives me "Secure Check Fail: xxx".
Is this because of the boot loader is locking down custom rom?

Those are really old recoveries.. Download twrp from their official site, flash, and try cm again

OMGOMG, it appears it is indeed an outdated recovery.
Gotta love you serio22.

So it works now?

Yup. I still think this is a factory refurbished device though. There is no way to explain custom bin counter was 9 and on custom bin out of the box though. It is really impressive how they come with all the boxes plastic seals etc. Definitely the most well disguised used device I've ever seen.

Don't know, still seems odd to me I've never heard of MC6 firmware

Related

Impossible to flash bootloader

Dears,
I finally decide to post here after strugguling for 3 days...
I'm living in China and I've just purchased a GN2 7100. As I did for my transformer prime, I hurried to flash a custom ROM to get rid of the suck Chinese ROM which doesn't allow to do anything. Therefore, a tablet is not a phone... I flashed omega v16 and I met the problem of: not registered on the network. All is fine on operator side, it works like a charm on my iphone. On my GN2, they can see I'm connected but I cannot call!
I've seen it could come from the modem and that's when I started to understand that there were more than one firmware for the kernel and modem. I could flash the modem to the original version but not the bootloader. I could downgrade to XxDLJ2 (instead of xxdll7), but I cannot flash the chinese bootloader: ZHDCM1. It seems the bootloader goes together with the modem but I don't succeed to do so.
I've tried to flash the stock rom through Odin, but it crashes at the sboot.bin (I suceeded through mobile odin but it doesn't update the bootloader version and I'm still not registered on the network).
Even if I flash chinese custom roms through CMW, it keeps XXDLJ2 bootloader...
I'm really desprate... I cant even reset the countdown since it'll always be 1 due to the wrong bootloader...
I don't know whatelse to do...
Maybe a guru here can give me hope... I've tried anything I could do on my own...
Thanks
Make sure it's not a clone.
Sent from my GT-N7100 using xda premium
Hello Gupta
I could register it on Samsung's website so I think it's a real one don't you think?
I've noticed something weird...
My bootloader should be here: dev/block/mmcblk0p1
I've tried to replace it manually through the custom recovery, but it didn't do the trick. I got pissed off and deleted it to see if it couldn't boot and it did... When I check in dev/block, mmcblk0p1 is back there... Is it pulled from another location?
Another weird thing: even if I do full wipe from system/factory reset/ dalvik and cache, I noticed that my default network speed (2G or WCDMA) remained setup as 2G (by default it was both of them when I loaded the phone for the first time). Is there anything which is not reset properly and could make something not working well?
The thing is that I didn't try to put my SIM at the beginning to see if it was working with the factory build so I'm unable to say if it comes from my flash to Omega or from the phone...
Any idea about those 2 weird points?
If your bootloader is messed up then how come you getting device in download mode
Another thing after exynos bug patched, samsung have black listed older botloader, so once you have newer bootloader, you can't flash any bootloader having black listed bootloader.
anyway try to flash same ROM which was came packed with device, and let's check if that works.
you can flash only modem, just extract ROM file 1 level depper and you will find modem.bin, now flash that modem.bin with 'phone' tab of odin.
There is a way to still downgrade if you want.
Sent from my GT-N7100 using xda premium
Yeah I think in android development as 9000 have posted tool to downgrade, but here too much work still needs to sort out exact issue.
Sent from my GT-N7100 using xda premium

[Solved] Status 7 Error

I'm not sure if my issue is complex or not. It's just a matter of me not being able to update my phone. Well, my phone was and is still working fine, but after an update, I believe it was CM 10.1 april 20th nightly build, or near that day. I started getting issues with my phone, where it would randomely reboot, and do it much more often when music was playing. That's when i guess i did the stupid thing, I went and downloaded the April 11 Experimental M3 update and updated using that, which worked fine. After that my phone was good as new. And still is right now, not really having any issues. But ofcourse, usually newer nightly builds come with bettered features, so i thought i would update. Here's the problem, when i update, I would get an assert failed and three lines of getprop ("ro.bootloader") T999UVDLJA and the 2 other versions the T999 models, then my model number i believe, followed by Status 7 installation aborted. Any help would be greatly appreciated.
Dantenios said:
I'm not sure if my issue is complex or not. It's just a matter of me not being able to update my phone. Well, my phone was and is still working fine, but after an update, I believe it was CM 10.1 april 20th nightly build, or near that day. I started getting issues with my phone, where it would randomely reboot, and do it much more often when music was playing. That's when i guess i did the stupid thing, I went and downloaded the April 11 Experimental M3 update and updated using that, which worked fine. After that my phone was good as new. And still is right now, not really having any issues. But ofcourse, usually newer nightly builds come with bettered features, so i thought i would update. Here's the problem, when i update, I would get an assert failed and three lines of getprop ("ro.bootloader") T999UVDLJA and the 2 other versions the T999 models, then my model number i believe, followed by Status 7 installation aborted. Any help would be greatly appreciated.
Click to expand...
Click to collapse
You will need to update to the latest bootloader (which is different from modem).
If you're on T-Mobile, you'll want UVDMD5: http://forum.xda-developers.com/showthread.php?t=2282603
If you're on WindMobile (or SGH-T999V), you'll want VLDLL1: http://forum.xda-developers.com/showthread.php?t=1949687 (you'll have to ODIN)
re: error 7 - odin flash
Dantenios said:
I'm not sure if my issue is complex or not. It's just a matter of me not being able to update my phone. Well, my phone was and is still working fine, but after an update, I believe it was CM 10.1 april 20th nightly build, or near that day. I started getting issues with my phone, where it would randomely reboot, and do it much more often when music was playing. That's when i guess i did the stupid thing, I went and downloaded the April 11 Experimental M3 update and updated using that, which worked fine. After that my phone was good as new. And still is right now, not really having any issues. But ofcourse, usually newer nightly builds come with bettered features, so i thought i would update. Here's the problem, when i update, I would get an assert failed and three lines of getprop ("ro.bootloader") T999UVDLJA and the 2 other versions the T999 models, then my model number i believe, followed by Status 7 installation aborted. Any help would be greatly appreciated.
Click to expand...
Click to collapse
This guide will get your phone back up and running properly, doing anything else will just prolong your problem.
Easy and sure way to fix error 7 and other issues or problems - Here is the step by step guide:
After doing this you will end up with a stock-pre-rooted T999 Tmobile Touchwiz 4.1.2 rom which works properly.
You will not loose any of your pictures, videos or music by doing this.
Download the newest pre-rooted Samsung Galaxy S3 T999 Jellybean v4.1.2 rom: T999_UVDMD5
After downloading make a folder on your computer's desktop and unzip the
file using Winzip or 7zip so the .TAR file is in the new folder you just made.
Download and extract Odin into the same folder you made containing the TAR file
Here is the link for Odin: http://d-h.st/Q14
Download ODIN which is required for flashing the stock rooted firmware (a windows app)
Download the Odin Flash firmware for T999 Tmobile then copy it to the same folder as Odin
Run Odin by double clicking the Odin.exe within the same folder as the TAR file you extracted
Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)
Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
You should now see a COM** port listed toward the top-left of Odin (under ID:COM)
Click on the PDA button in the middle-right area of Odin.
Browse to and select the Firmware you downloaded (TAR file)
Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.
TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
Click Start to begin the flash. This will take a while, so be patient!
Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
You may unplug the phone and close Odin if you wish.
Wait at least 5-10 minutes for the system to boot the first time and then build its cache!
(It may seem to hang during boot, this is normal and you must be patient!!!)
Good Luck!
to Be honest, I'd rather keep using CM 10.1 and not the TouchWiz JB. And what would be the latest bootloader? Apologies, i'm some what new to this.
re: jellybeans
Dantenios said:
to Be honest, I'd rather keep using CM 10.1 and not the TouchWiz JB. And what would be the latest bootloader? Apologies, i'm some what new to this.
Click to expand...
Click to collapse
I never said you should be running JB Touchwiz roms, all I was trying to explain is the best and easiest way to get
your phone back up and running whichever way you like it to run.
If you follow the step by step instructions and the phone is working normally then you can re-flash whichever rom
CM10.1 or any others without any issues unless their is something wrong with the rom you are trying to flash.
The main thing is that it's best to start fresh when someone is having issues like you are having with your phone.
Doing anything else besides what I suggested will only prolong all those issues you are having now.
People will be telling you that your cwm or twrp recovery is not the latest one and you need to update it,
other people will tell you that you must have had some error downloading the cm10.1 rom and they will
tell you to re-download it, then others will tell you to check the MD5 checksum of the download and all
kinds of other things which will just prolong the problems you are having.
None of those things I just wrote will help you to fix the error 7 and other issues you are having.
That's why I posted the step by step which works each and every time to fix errors such as yours and
give you or anyone else a clean and fresh start.
Good luck!
*please ignore*
re: you are right
GenericAsianGuy said:
You need to ODIN the latest TouchWiz JB in order to update all the inner-parts of your phone.
I did this yesterday:
ODIN to the latest pre-rooted firmware (DLL1 in my case (SGH-T999V), MD5 for SGH-T999)
Let it boot into TouchWiz
Install Android Terminal Emulator and the latest ClockworkModRecovery
Boot into Recovery
Factory Reset
Install the latest CM 10.1 Nightly
Reboot
Profit (and spend a few hours re-installing and re-configuring everything again).
Click to expand...
Click to collapse
U R so right! I could not have said it better!
---------- Post added 19th May 2013 at 12:00 AM ---------- Previous post was 18th May 2013 at 11:18 PM ----------
Dantenios said:
to Be honest, I'd rather keep using CM 10.1 and not the TouchWiz JB. And what would be the latest bootloader? Apologies, i'm some what new to this.
Click to expand...
Click to collapse
I forgot to mention, since you are kind of new to this you should not even think of or mention anything
about bootloaders if don't want to end up with a shiny brick.
This has happened hundreds of times in these XDA forums when people mess around with bootloaders.
Flashing bootloaders intentionally or by trial and error is the number one way to end up with a bricked phone.
Alright, I understand now, thank you. Just curious, this will probably trip the flash counter right? Or does following that method allow to reset the flash counter? Or is that just something i need to worry about if i'm going to send the phone in for repairs (which i hope I wouldn't need to)
re: flash counter
Dantenios said:
Alright, I understand now, thank you. Just curious, this will probably trip the flash counter right? Or does following that method allow to reset the flash counter? Or is that just something i need to worry about if i'm going to send the phone in for repairs (which i hope I wouldn't need to)
Click to expand...
Click to collapse
The odin flash to stock rooted will trip the flash counter, but then each time you flash any rom trips the flash counter too.
You can get the "Triangle away" app to reset the flash counter at the play store.
Actually there is no need to reset the flash counter at all unless you need to
exchange a defective phone which is still under warranty.
Good luck!
Apologies but one more thing, your post was a link to a pre-rooted JB for T999, My phone is the T999V, if you'd happen to have the pre-rooted version for that would be greatly appreciated.
Dantenios said:
Apologies but one more thing, your post was a link to a pre-rooted JB for T999, My phone is the T999V, if you'd happen to have the pre-rooted version for that would be greatly appreciated.
Click to expand...
Click to collapse
All of these roms are stock pre-rooted roms, I am not certain which one is for your
T999v phone. Perhaps the "V" stands for videotron so select that one.
Mobililicity_VLDLL1
Updated JB Firmware
Mobililicity_VLALH2
Updated ICS Firmware
Wind_VLDLL1
Updated JB Firmware
Wind_VLALH2
Updated ICS Firmware
Videotron_VLDLL1
Updated JB Firmware
Videotron_VLALH2
Updated ICS Firmwar
Misterjunky said:
Mobililicity_VLDLL1
Updated JB Firmware
Wind_VLDLL1
Updated JB Firmware
Videotron_VLDLL1
Updated JB Firmware
Click to expand...
Click to collapse
Great post Misterjunky!
One of these; it depends on what carrier you're with.
I just finished using Odin to the Mobilicity VDLL1 with the pre-rooted JB. Just waiting on my phone to boot up. I have the tab open to install CWM Touch via the terminal emulator. After that I can install the latest CM 10.1 update correct?
re Ok
Dantenios said:
I just finished using Odin to the Mobilicity VDLL1 with the pre-rooted JB. Just waiting on my phone to boot up. I have the tab open to install CWM Touch via the terminal emulator. After that I can install the latest CM 10.1 update correct?
Click to expand...
Click to collapse
Yes, once odin is done and you flash custom recovery the phone will be ready to be flashed any compatible cwm/twrp custom rom zipfile.
You would be much better off if you go to the playstore and download "Goomanager" which is a free app.
After its installed, open it and press the menu key and select "installopenrecoveryscript".
Doing that will flash the latest TWRP recovery.
When Goomanager is done flashing, reboot the phone into recovery mode and go from there.
TWRP has a built-in file manager and terminal, plus an option for ADB sideloading.
It has all the options which CWM has and more.
Give it a try, you can always flash the cwm back if you like.
Sure, though i'm having a new issue now haha My phone has been stuck on the Samsung loading screen ever since after Odin said pass. How long does this usually take, right now for me it's been almost half an hour...And i know i followed the instructions to the T
re: reboot
Dantenios said:
Sure, though i'm having a new issue now haha My phone has been stuck on the Samsung loading screen ever since after Odin said pass. How long does this usually take, right now for me it's been almost half an hour...And i know i followed the instructions to the T
Click to expand...
Click to collapse
reboot the phone into recovery and do a "Factory reset" then restart the phone.
Chances are excellent that it will boot normally if you flashed the correct rom.
Don't wipe anything in recovery.
Good luck!
Thanks a Bunch, It worked! Now to install the recovery, then i may try using Touchwiz JB for a bit, but to be honest, I still think i like CM 10.1 better haha this one feels..some what clunky to me.
Dantenios said:
Thanks a Bunch, It worked! Now to install the recovery, then i may try using Touchwiz JB for a bit, but to be honest, I still think i like CM 10.1 better haha this one feels..some what clunky to me.
Click to expand...
Click to collapse
It would probably be best to edit your title with SOLVED in italics or something so other users are aware and can revert to this thread for assistance rather than starting up a whole new one
Sent from my SGH-T999 using xda premium
Done. I just wanted to ask, I installed the latest CM 10.1 update, and wondering, when i facotry reset it, it didn't take me through the welcome procudure and under my Mobile network options, i didn't see any LTE options, just EvDO and Global and other GSM/WCDMA ones which even after selecting didn't change the one selected by default.
Dantenios said:
Done. I just wanted to ask, I installed the latest CM 10.1 update, and wondering, when i facotry reset it, it didn't take me through the welcome procudure and under my Mobile network options, i didn't see any LTE options, just EvDO and Global and other GSM/WCDMA ones which even after selecting didn't change the one selected by default.
Click to expand...
Click to collapse
If you don't see the Gmail app (and other Google apps) installed, you may need to flash the latest Gapps: http://goo.im/gapps/gapps-jb-20130301-signed.zip

[Q] Trouble flashing to stock. Help!

To start i belive my OS was deleted previous to the attempt to flash to stock.
Using L900PALJC md5 file from samsung-updates.com
Running odin3v3.07 as admin.
Drivers are uptodate
Com id is light blue in color
Where messages prompt it reads:
<ID:0/009>Firmware update start..
"Boot.img
"NAND Write Start!!
"cache.img
"hidden.img
"modem.bin
"param.bin
"recovery.img
"sboot.bin
"FAIL!!
<OSM> All threads completed. Succeed 0 / failed 1
Thanks in advanced and thanks to come
Jjpuerto58 said:
To start i belive my OS was deleted previous to the attempt to flash to stock.
Using L900PALJC md5 file from samsung-updates.com
Running odin3v3.07 as admin.
Drivers are uptodate
Com id is light blue in color
Where messages prompt it reads:
<ID:0/009>Firmware update start..
"Boot.img
"NAND Write Start!!
"cache.img
"hidden.img
"modem.bin
"param.bin
"recovery.img
"sboot.bin
"FAIL!!
<OSM> All threads completed. Succeed 0 / failed 1
Thanks in advanced and thanks to come
Click to expand...
Click to collapse
Are you able to get into your recovery? If so, from what I see here it should let you into the stock recovery. If you get something different or nothing at all let me know. Have you tried flashing back to stock with any other files (i.e. something provided here on XDA, or an older file on the Samsung website)? I've run into issues with ASUS post bad software on their site when trying to return to stock. May I ask why you are flashing back to stock? You said that you believe your OS was deleted? I may have some links I can pass on to you to help you find what you need, but a bit more information would help. I looked on the Verizon NII forums and have seen a few people with similar issues.
Killa357 said:
Are you able to get into your recovery? If so, from what I see here it should let you into the stock recovery. If you get something different or nothing at all let me know. Have you tried flashing back to stock with any other files (i.e. something provided here on XDA, or an older file on the Samsung website)? I've run into issues with ASUS post bad software on their site when trying to return to stock. May I ask why you are flashing back to stock? You said that you believe your OS was deleted? I may have some links I can pass on to you to help you find what you need, but a bit more information would help. I looked on the Verizon NII forums and have seen a few people with similar issues.
Click to expand...
Click to collapse
I have not tried flash to stock with any other files, i did attempt to flash the CF Auto root file becuase i was at a lose. I tried that yesterday morning the result i got was loosing my twrp recovery and binary count up to two. I deleted my os while tring to flash macksrom v5 2 weeks ago. I was attempting to flash to stock in effort to reclaim my OS. I would like end game to be macksrom v5. Previous to deleting os, 2 months ago i tried flashing macksrom planejane to no avali, using files from diffrent locations but all seem to be unable to unzip. The only successfull in flashing was a perseus kernle.
Jjpuerto58 said:
I have not tried flash to stock with any other files, i did attempt to flash the CF Auto root file becuase i was at a lose. I tried that yesterday morning the result i got was loosing my twrp recovery and binary count up to two. I deleted my os while tring to flash macksrom v5 2 weeks ago. I was attempting to flash to stock in effort to reclaim my OS. I would like end game to be macksrom v5. Previous to deleting os, 2 months ago i tried flashing macksrom planejane to no avali, using files from diffrent locations but all seem to be unable to unzip. The only successfull in flashing was a perseus kernle.
Click to expand...
Click to collapse
Try pushing TWRP to your phone using ODIN. From there you can try putting that ROM on your phone. I would try a different ROM first just to see if you are able to flash anything.
Killa357 said:
Try pushing TWRP to your phone using ODIN. From there you can try putting that ROM on your phone. I would try a different ROM first just to see if you are able to flash anything.
Click to expand...
Click to collapse
So will flashing a ROM install an OS too? Any ROM suggestion for this task?
Jjpuerto58 said:
So will flashing a ROM install an OS too? Any ROM suggestion for this task?
Click to expand...
Click to collapse
Are you new to modding phones? Not trying to sound rude, you just seem a little confused is all. When we say we are flashing a "ROM" we mean we are installing a different OS on the phone. It all depends on what you are looking for. If you want something smooth and close to original android, you could try Cyanogen mod, AOKP, Liquid smooth and a few others. If you want one that is a modded stock ROM (one advantage there is that you will still have access to all of the Samsung Applications for the S-Pen, though there are plenty of suitable replacements for these) you could try something like Synergy... Not sure what all else there is as it has been a while since I've tried out different ROMs. What all are you looking for in a ROM?
same problem but much further along than him
Killa357 said:
Are you new to modding phones? Not trying to sound rude, you just seem a little confused is all. When we say we are flashing a "ROM" we mean we are installing a different OS on the phone. It all depends on what you are looking for. If you want something smooth and close to original android, you could try Cyanogen mod, AOKP, Liquid smooth and a few others. If you want one that is a modded stock ROM (one advantage there is that you will still have access to all of the Samsung Applications for the S-Pen, though there are plenty of suitable replacements for these) you could try something like Synergy... Not sure what all else there is as it has been a while since I've tried out different ROMs. What all are you looking for in a ROM?
Click to expand...
Click to collapse
ok so yes i was trying to root and flash to verizon. bought the phone on craigslist. it had a bad esn so i decided to flash it. I rooted it and installed twrp just fine. being a dumb @$$ took hold of me and i decided to partition and format the phone. in the end I bricked it. so i through the phone into download mode. and tried to use the custom LJC rom. (no dice). so I tried the VZW variant. (failed at cache). So I tried to replace the the stock rom. got down to sboot.bin and failed. it turns out the bootloaders get locked so i cant use a boot image to recover. in the process of replacing with stock i deleted twrp. unintentionally. so no more twrp. so i found a thread that had a stock rom that doesnt use sboot.bin. fails at cache every time. I have tried everything I know to do and there isnt much on the note 2 yet. so im looking for answers. I feel as if im close but im just missing something. if i could find a combination kies file with no sboot.bin for SPH-L900 it may work. I dont know how to compile it myself or i would so here I am. any help would be appreciative.
Thanx
edub251 said:
ok so yes i was trying to root and flash to verizon. bought the phone on craigslist. it had a bad esn so i decided to flash it. I rooted it and installed twrp just fine. being a dumb @$$ took hold of me and i decided to partition and format the phone. in the end I bricked it. so i through the phone into download mode. and tried to use the custom LJC rom. (no dice). so I tried the VZW variant. (failed at cache). So I tried to replace the the stock rom. got down to sboot.bin and failed. it turns out the bootloaders get locked so i cant use a boot image to recover. in the process of replacing with stock i deleted twrp. unintentionally. so no more twrp. so i found a thread that had a stock rom that doesnt use sboot.bin. fails at cache every time. I have tried everything I know to do and there isnt much on the note 2 yet. so im looking for answers. I feel as if im close but im just missing something. if i could find a combination kies file with no sboot.bin for SPH-L900 it may work. I dont know how to compile it myself or i would so here I am. any help would be appreciative.
Thanx
Click to expand...
Click to collapse
Download one of my zips here and put it on your micro sd card. http://forum.xda-developers.com/showthread.php?t=2086769
Then
Place the phone in download mode and flash this in PDA slot. http://www.androidfilehost.com/?fid=23060877490001700
It will get you into twrp recovery. From there factory reset and flash the zip you downloaded from the first link
billard412 said:
Download one of my zips here and put it on your micro sd card. http://forum.xda-developers.com/showthread.php?t=2086769
Then
Place the phone in download mode and flash this in PDA slot. http://www.androidfilehost.com/?fid=23060877490001700
It will get you into twrp recovery. From there factory reset and flash the zip you downloaded from the first link
Click to expand...
Click to collapse
OMG thanks man your a life saver 3 weeks of hell and headaches are over. IF I could paid you for this i would have....not to mention i checked the ESN on swappa and sprint must have cleared it for usage so dont need to flash it anymore.....thanks a million :good::laugh::highfive::victory::cyclops:
Killa357 said:
Are you new to modding phones? Not trying to sound rude, you just seem a little confused is all. When we say we are flashing a "ROM" we mean we are installing a different OS on the phone. It all depends on what you are looking for. If you want something smooth and close to original android, you could try Cyanogen mod, AOKP, Liquid smooth and a few others. If you want one that is a modded stock ROM (one advantage there is that you will still have access to all of the Samsung Applications for the S-Pen, though there are plenty of suitable replacements for these) you could try something like Synergy... Not sure what all else there is as it has been a while since I've tried out different ROMs. What all are you looking for in a ROM?
Click to expand...
Click to collapse
Yes, i am green. i liked what i saw with macksrom bloat remove, tether, mutilwindow mod, volume boost. i will look into synergy thx.
billard412 said:
Download one of my zips here and put it on your micro sd card. http://forum.xda-developers.com/showthread.php?t=2086769
Then
Place the phone in download mode and flash this in PDA slot. http://www.androidfilehost.com/?fid=23060877490001700
It will get you into twrp recovery. From there factory reset and flash the zip you downloaded from the first link
Click to expand...
Click to collapse
Will post results monday.
Looking for you expert advice
I am trying to take my Boost Mobile S3 and flash it to my Sprint Samsung Galaxy Note 2. I use to have the note 2 flashed with my old donor (Boost Mobile Incognito)... I LOVE the Note 2 but hated that I could only get 3g. I love the 4G on my S3 (night and day difference). I am green but I am getting pretty savoy from all the info I get here. And I read, read and then read some more... I miss my note 2.. Easy on the eyes! lol... I love the bigger screen and the s-pen feature, Simply put, after reading your thread here, I was so impressed with your knowledge that I thought I'd ask you for your help. I just want to use the S3 as a donor. How to I donor the S3? What programs do you suggest to use to read the info on the S3 and write (flash) to the Note 2? Thank you so much for any help you can give...
I finnaly got to flash the lastest suggestion billard412 you are right on the money. Thanks a billion and where is your donation button!?
Jjpuerto58 said:
I finnaly got to flash the lastest suggestion billard412 you are right on the money. Thanks a billion and where is your donation button!?
Click to expand...
Click to collapse
Glad it worked for you. Button is in my sig. \/\/ T.I.A for the contribution

[Q] I think I may have jacked my phone up

I had previously tried to root my phone and decided to flash it back to factory. I downloaded last nights OTA 4.3 update and after it installed, now my ATT S3 SGHi1747 gets stuck at the ATT logo AFTER the Samsung logo appears then disappears. My pc is no longer recognizing the device nor do I know how to get in there to at least get it up and running to try and flash it back to factory THEN download 4.3.
Any suggestions on how to get this fixed would be appreciated!
'Sider said:
I had previously tried to root my phone and decided to flash it back to factory. I downloaded last nights OTA 4.3 update and after it installed, now my ATT S3 SGHi1747 gets stuck at the ATT logo AFTER the Samsung logo appears then disappears. My pc is no longer recognizing the device nor do I know how to get in there to at least get it up and running to try and flash it back to factory THEN download 4.3.
Any suggestions on how to get this fixed would be appreciated!
Click to expand...
Click to collapse
ODIN back to stock.
Question
Did you try using ODIN or did you find a factory ROM to flash?
'Sider said:
I had previously tried to root my phone and decided to flash it back to factory. I downloaded last nights OTA 4.3 update and after it installed, now my ATT S3 SGHi1747 gets stuck at the ATT logo AFTER the Samsung logo appears then disappears. My pc is no longer recognizing the device nor do I know how to get in there to at least get it up and running to try and flash it back to factory THEN download 4.3.
Any suggestions on how to get this fixed would be appreciated!
Click to expand...
Click to collapse
Try booting into recovery and factory resetting, this usually fixes this problem.
polobunny said:
ODIN back to stock.
Click to expand...
Click to collapse
Downloaded ODIN, still a little fuzzy on how to operate it
Cadle said:
Did you try using ODIN or did you find a factory ROM to flash?
Click to expand...
Click to collapse
Im not too tech savvy obviously lol, can you point me in the direction of a factory ROM
dntesinfrno said:
Try booting into recovery and factory resetting, this usually fixes this problem.
Click to expand...
Click to collapse
Tried this twice, no luck.
Im assuming once I get this thing flashed back, I can download that app that will reset the counter?
'Sider said:
Downloaded ODIN, still a little fuzzy on how to operate it
Click to expand...
Click to collapse
If you google for "odin flash rom" there's lot of good tutorials out there, many on this forum alone. As for stock, i'm not sure where to find it since I flashed custom the day after I got my phone and never looked back...can't stand stock touchwiz. You could also try flashing any custom ROM you happen to have layin around...worth a shot until you find a custom one. I use BeanStalk ROM, which has 4.3 and 4.4 versions out now.
Best of luck to ya!
goombah88 said:
If you google for "odin flash rom" there's lot of good tutorials out there, many on this forum alone. As for stock, i'm not sure where to find it since I flashed custom the day after I got my phone and never looked back...can't stand stock touchwiz. You could also try flashing any custom ROM you happen to have layin around...worth a shot until you find a custom one. I use BeanStalk ROM, which has 4.3 and 4.4 versions out now.
Best of luck to ya!
Click to expand...
Click to collapse
I suggest here that everyone here read some of the other threads here on XDA, and see all the problems people are having flashing and rooting after taking this latest 4.3 OTA before advising the next person on how to make ANOTHER paper weight.
As for Sider,
You might be out of luck here, as there is no official 4.3 firmware yet available to flash back to stock, and also AT&T has done something with the new software update, where trying to downgrade it back to a previous version is going to either fail or brick phones.
Also, I haven't read yet where anyone has been successful flashing a custom recovery to fix any issues, but the posts are going up so fast right now that I might have easily missed it.
Edit: OK, someone was able to get TWRP installed, but is also having issues with root.
polobunny said:
ODIN back to stock.
Click to expand...
Click to collapse
DO NOT ODIN after last update (OTA 4.3) installed on phone. You will brick your phone.
norbarb said:
DO NOT ODIN after last update (OTA 4.3) installed on phone. You will brick your phone.
Click to expand...
Click to collapse
You're right. I completely forgot about that.

Post Chainfire Root Issues 5.1.1

I attempted to root my phone using the Chainfire Auto-root method today and somehow managed to use the 925p edge MD5 file instead of 920p. This caused a few issues, the X-axis was inverted, no service, and a continual automatic reboot after about 30-60 seconds of the phone being on. In an attempt to fix it, I have tried a few things. in many combinations. I have reflashed the stock tar file, cleared cache, factory reset, and flashed the PIT file found in post 12 of this thread http://forum.xda-developers.com/sprint-galaxy-s6/help/operating-smg920p-t3263325/page3. Unfortunately all attempts have been for fruitless. Obviously the first issue to be tackled is the constant rebooting. Any help would be appreciated.
Maybe flashing unikernel will help, it can be found here: https://www.androidfilehost.com/?fid=24269982087012055
Just flash it in Odin, if that does not work you may want to try bringing it to where you bought it for warranty.
No luck, unfortunately.
offthatwall said:
No luck, unfortunately.
Click to expand...
Click to collapse
Idk, @koop1955 any suggestions?
1619415 said:
Idk, @koop1955 any suggestions?
Click to expand...
Click to collapse
Posted this in the other thread: http://forum.xda-developers.com/showpost.php?p=64735692&postcount=19
That is all that I have for you.
offthatwall said:
I attempted to root my phone using the Chainfire Auto-root method today and somehow managed to use the 925p edge MD5 file instead of 920p. This caused a few issues, the X-axis was inverted, no service, and a continual automatic reboot after about 30-60 seconds of the phone being on. In an attempt to fix it, I have tried a few things. in many combinations. I have reflashed the stock tar file, cleared cache, factory reset, and flashed the PIT file found in post 12 of this thread http://forum.xda-developers.com/sprint-galaxy-s6/help/operating-smg920p-t3263325/page3. Unfortunately all attempts have been for fruitless. Obviously the first issue to be tackled is the constant rebooting. Any help would be appreciated.
Click to expand...
Click to collapse
Koop's stock firmware didn't fix mine for some reason either...heres the stock version that fixed mine
mediafire.com/download/c55xaeb7geq0i2d/G920PVPU3BOJ7_G920PSPT3BOJ7_SPR.zip
Hope it helps!
x1xmadex1x said:
Koop's stock firmware didn't fix mine for some reason either...heres the stock version that fixed mine
mediafire.com/download/c55xaeb7geq0i2d/G920PVPU3BOJ7_G920PSPT3BOJ7_SPR.zip
Hope it helps!
Click to expand...
Click to collapse
The firmware posted above is OJ7, which seems to be an earlier version than the OL1 firmware. I have no idea why OJ7 would work for you when OL1 wouldn't. (Unless you got a bad download of OL1, which is why I recommend checking MD5.)
If you are still on OJ7, can you try system update and see if that takes you to OL1?
koop1955 said:
The firmware posted above is OJ7, which seems to be an earlier version than the OL1 firmware. I have no idea why OJ7 would work for you when OL1 wouldn't. (Unless you got a bad download of OL1, which is why I recommend checking MD5.)
If you are still on OJ7, can you try system update and see if that takes you to OL1?
Click to expand...
Click to collapse
I have already re-rooted my device and installed twrp...it wont let me install a system update due to custom and not official...Also I downloaded the OL1 three occasions..and MD5 passed
x1xmadex1x said:
I have already re-rooted my device and installed twrp...it wont let me install a system update due to custom and not official...Also I downloaded the OL1 three occasions..and MD5 passed[/Q
Im have the constant reboot now. Im gonna try another pb6 6.0.1 tar file only one ive tried was the sprint worker one said revo in in it. That didnt not fix my constant rebooting issue. So far any rom even after odin stock still rebooting every 2 minutes.
Click to expand...
Click to collapse
will get that logcat
Saafir said:
Note the time and grab a logcat.
Ok i left the phone at home but i did look at the log cat about the first ten lines all had emmc in them im not quite sure. Well I cant read it lol. when i get home il flash twrp and restore a back up let reboot a few times get a log cat and post it will twrps log cat work? If im lucky i might get a app installed to do it. I no longer got adb and fastboot on my computer but will download if needed.
im waiting for a replacement to get to the sprint store. i flashed stock and took it in rebooting sprint guy tried factory resetting it and clearing cache which got it stuck in the pre load starting or optimizing apps before itd finish it it would reboot and if i kept going id beable get to start up settings thats it. now i can flash twrp still it does restores my back ups and after that itl boot the system i can uninstall or install something or what not maybe 1 min after im able to get into it it reboot. only wifi connects though.
Again i had about all roms we got on sprint forum on that phone worked awesome loved it til the time i restored the efs on 6.0.1 with a twrp thats a unofficial build modded to work on 920p.
Click to expand...
Click to collapse
Sounds good thanks man.
Seems as maybe a somewhat common issue unfortunately thats happening for s6 as well as sprint note 5 as there are a few threads regarding the same issue. Theres a thread for s6 on this issue and on 2nd page appears as if someone found a fix having something to do with letting it die completely etc.. http://forum.xda-developers.com/sprint-galaxy-s6/help/constant-rebooting-t3287213
I figured my rebooting issue was corrupted data becausr i was transferring from phone to pc to phone and no md5 check. Though now i will use it. Good luck

Categories

Resources