Develop Bugs

[REPAIR] TeenyBin for LS970 - Soft Brick Fix. B/L Unlock. RPM/TZ Update {08/21/13}

LS970 TeenyBin for LGNPST
Don't give me all the credit. Just as much goes to artlan for figuring out the tables.
Be sure to show him some thanks.
Background
After seeing tons of soft bricks on both the forums and IRC we have decided to look into how LG .bin files work. We've "cracked the code" and have been able to rebuild the .bins.. making the repair process both faster and easier. Normally the user must download a large .tot/.bin file(1GB+) to repair the phone. After a long download and 5+ minute LGNPST flash the phone is then completely stock... requiring a "re-root" and running the FreeGee unlock again.
TeenyBins are meant to do the bare minimum... fix your soft bricked LG OG allowing you to boot into fastboot/bootloader and custom recovery. In recovery you can restore a backup or flash a custom rom zip. In Some cases TeenyBin will allow you to boot back into your rom without reflashing a zip but do not expect this. These new .bins are as small as 32MB depending on what we build into the .bin. This means smaller files, shorter download times and a phone that's back up and running within minutes.
Other perks include...
Unlocked bootloader.
SBL partitions safely flashed.
TWRP Recovery.
RPM/TZ partitions safely updated to supported the latest AOSP roms.​
Directions
1. Download TeenyBin then extract. The .bin you extract is used w/LGNPST. LGNPST can be found in the "Additional Info" section of this post.
2. Put phone into download mode. Flash TeenyBin. The flash should take about 20 seconds. The phone will reboot at 67% or 85%. Flash complete. All finished.. maybe...
3. Your phone may not boot up! If so you must power off the phone(hold power button for up to 60 seconds).. boot into fastboot. No fastboot still? Did you flash the Teenybin[SBL Unlock]? From fastboot, boot into recovery. In recovery you can restore a backup or flash a custom rom zip. All fixed.
Nothing working? You're doing it wrong(or have a weird/broken phone. Did you read this entire post... including everything under the "Additional Information" section at bottom? Last resort would be to flash the FULL STOCK bin for your exact model LG OG.
Download = Hold Volume up + down + power while plugging the USB cable into the phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Fastboot = Volume up + power
Recovery = once in fastboot.. press volume down, pause, volume down then power button
​
TeenyBins
These TeenyBins will repair a soft brick(allowing you into Fastboot/TWRP), unlock the bootloader, install custom recovery and upgrade rpm 'n' tz.
If you can't boot.. fastboot has to work. If you can't get to fastboot you're doing it wrong.
Fastboot = Volume up + power
Recovery = once in fastboot.. press volume down, *wait*, volume down then power button
DOWNLOAD:
LS970 TeenyBin - Contains stock SBL stack. Use TeenyBin SBL Unlock unless you need the default SBL stack for some weird reason.
LS970 TeenyBin[SBL Unlock] - Equivalent to the FreeGee SBL Unlock method (FreeGee > Menu button > SBL Unlock)
LS970 Original TeenyBin[ZVBin] - Use TeenyBin ZVBin if you were on ZVB with an LG based rom(not AOSP)before the softbrick.
Current included recovery: TWRP 2.6.0.0 - Thank you Dees_Troy!
​
Additional Files
Modem Links:
LS970 modems in flashable .zip format. These may or may not have to be flashed depending on the level of repair needed on your device.
LS970ZV7-M9615A-CEFWMAZM-2.0.12034
AU_LINUX_ANDROID_ICS_STRAWBERRY.04.00.04.19.130M9615A-CEFWMAZM-2.0.12034
QCTM9615A-FEHRMAZ-1.7.30
QCTA8064A-AAAANAAW-1.1.40010T
by QUALCOMM, Incorporated Sep 25 2012
ZV7 Modem .zip
LS970ZV8-M9615A-CEFWMAZM-2.0.12034
AU_LINUX_ANDROID_ICS_STRAWBERRY.04.00.04.19.130M9615A-CEFWMAZM-2.0.12034
QCTM9615A-FEHRMAZ-1.7.30
QCTA8064A-AAAANAZW-1.1.40017T
by QUALCOMM, Incorporated Oct 18 2012
ZV8 Modem .zip
LS970ZV9-M9615A-CEFWMAZM-2.0.12034
AU_LINUX_ANDROID_ICS_STRAWBERRY.04.00.04.19.130M9615A-CEFWMAZM-2.0.12034
QCTM9615A-FEHRMAZ-1.7.30
QCTA8064A-AAAANAZW-1.1.40017T
by QUALCOMM, Incorporated Nov 28 2012
ZV9 Modem .zip
LS970ZVB-M9615A-CEFWMAZM-3.0.10646
M9615A-CEFWMAZM-3.0.10690
QCTM9615A-FEHRMAZ-2.7.38
QCTA8064A-AAAANAAW-1.2.5002T
by QUALCOMM, Incorporated Feb 13 2013
ZVB Modem .zip
LS970ZVC-M9615A-CEFWMAZM-3.0.10646
M9615A-CEFWMAZM-3.0.10690
QCTM9615A-FEHRMAZ-2.7.38
QCTA8064A-AAAANAAW-1.2.5002T
by QUALCOMM, Incorporated Aug 21 2013
ZVC Modem .zip
Backup Partitions:
Backup All Partitions .zip
This is a flashable zip that backs up most of your partitions.. excluding data, system, grow and reserved.
Backup your partitions and store them in the cloud somewhere for safe keeping.
​
Additional Info
Q: I flashed the small bin and still can't boot back into my phone.
A: First of all... it's a TeenyBin... but anyway.. booting directly back up into the rom may not always be possible. Your /system or boot.img may be damaged. You were soft bricked remember... how do you think the soft brick happened? In this scenario you will have to reboot into fastboot.. then enter recovery... and reflash a rom .zip
Q: I don't have a rom .zip on my internal storage so how can I flash a .zip?
A: Use adb while in recovery mode to push a rom to the phone. Google is your friend... look into adb push.
Q: What is adb?
A: Get out!
Q: How do I know if I'm soft bricked or perm bricked?
A: For most soft bricks you will see a LG or Google logo and then a black screen. You can also still get into download mode. If you think download mode may not even work, connect phone to a Windows computer and check device manager... if the phone is detected in a "QHSUSB-DLOAD" then there's a good chance you're perm bricked. Otherwise.. you may just be a n00b and aren't doing download mode correctly.
Q: Where's that LGNPST info you mentioned?
A: Hit the Show Content button below
LGNPST Guide
DO NOT ASK HOW TO USE LGNPST OR A VIRTUAL MACHINE IN THIS THREAD.
THIS IS A TEENBIN THREAD. THE FILES AND GUIDES BELOW ARE A BONUS ONLY. RESEARCH. READ. APPLY.
Downloads + basic guide HERE
Update - added a virtual machine with pre-installed LGNPST to the link above. This will be for those that aren't on Windows.. or just having install issues. Thanks to k7raid for that! Some files may need a password to extract... PW = lgog
BELOW IS A MORE DETAILED GUIDE FOR THOSE CONFUSED OR STUCK.
READ IT ALL AND MOST QUESTIONS SHOULD BE ANSWERED
Notice at the top it says LGNPST ACG and not some other weird version? And notice the version numbers. If yours don't match up then you installed the wrong version!!
1. COM port will show up if phone is connected properly in Download Mode. LGNPST will switch and say Emergency Mode.
2. Press the DLL button towards the bottom of Emergency tab.
3. Press the BIN button towards the bottom of Emergency tab. You should now see both both file names scrolling in LGNPST like the screenshot.
4. Press that START button.
5. A windows will pop up saying you will lose data.. you will NOT lose any personal data.. hit OK.
6. If LGNPST is working properly it will take 20 seconds or so before LGNPST hits 67% and reboots your phone. DONE. After your phone reboots at 67% or 85% it's safe to unplug and use phone.
7. If you still can't boot up, try booting into fastboot. Can't get into fastboot.. try flashing the AltBin. Still can't get into fastboot? you're doing it wrong.
Q: LGNPST Won't open and says "usb dongle not detected"
A: In the lgnpst folder where u ran the .bat to install it should be a lgnpst_acg.exe file somewhere. Copy it to your program files > lg electronics > lgnpst folder overwriting the current exe in that folder. Should work now.
Q: There's no LGNPST_LS970/dll file to select in LGNPST.
A: The install.bat should have registered your dlls but something went wrong. Check the link in the next answer.
Q: I still can't install LGNPST... help?
A: Check out this link.
​
Code:
[B]My other LS970 threads..[/B]
[B][URL="http://forum.xda-developers.com/showthread.php?t=2161498"][GUIDE] Backup/Restore/Repair Your EFS Partition [LS970][/URL][/B]
[B][URL="http://forum.xda-developers.com/showthread.php?t=2049701"][HOW-TO] Enable DIAG mode without Service Code(MSL)[/URL][/B]
[B][URL="http://forum.xda-developers.com/showthread.php?t=2052816"][INFO] LS970 Hidden Dialer Codes[/URL][/B]
[B][URL="http://forum.xda-developers.com/showthread.php?t=2058506"][INFO] Optimus G AT Commands[/URL][/B]
Special thanks to xonar_ for his LG Bin Firmware Extractor and releasing his source code.
Thank you Shelnutt2 for everything you do for the entire LGOG community.
Thank you k7raid for testing the first bin with major SBL changes.
And last and also least.. ha ha.. sawdey21 for suggesting the "updated" name change.
Be sure to show them all thanks.
TeenyBin. Patent Pending. ​

*reserved*

autoprime said:
*reserved*
Click to expand...
Click to collapse
Holy crap this is freaking awesome!

Great job guys.
LROD'S OPTIMUS G

Thanks for this

Studmuffins
Sent from my LG-LS970 using Tapatalk 2

you sir are amazing. maybe one day you will show some ATT some love as well

sawdey21 said:
you sir are amazing. maybe one day you will show some ATT some love as well
Click to expand...
Click to collapse
AT&T bins are in the works

Thanks guys. I noticed that there are Mako RPM's in that post. Any idea if the Mako RPM for Key Lime Pie be backward compatible with our phone in the future? Of course, KLP isn't out yet, so there's no way to tell just yet, just trying to gauge whether or not you guys think its possible. I doubt like hell our phones will be officially updated to KLP by LG.

I knew it would be a matter of time until you guys firgured something out. Def thanks for this and the previous fix you guys gave me!

I am currently on ZVB (JellyBean 4.1.2)stock rooted. I am one of those unfortunate people that kept getting soft bricked (LG screen on boot straight to a black screen) and could not unlock the phone because this always occured.
I thank you all for those who worked on this project to help us out.
I have a couple of questions:
1) Im on ZVB but the TeenyBin is acutally ZV9 based. Do I have to revert back to ZV9 to use this method?
2) Is root needed to apply the teenybin in LGNPST? Or will the teenybin apply root and unlock feature?
3) If I use the teenybin will that wipe my data on my phone?
Sorry for all the questions, but I truly want to use this method to unlock my phone and flash CM10

EFEXR said:
I am currently on ZVB (JellyBean 4.1.2)stock rooted. I am one of those unfortunate people that kept getting soft bricked (LG screen on boot straight to a black screen) and could not unlock the phone because this always occured.
I thank you all for those who worked on this project to help us out.
I have a couple of questions:
1) Im on ZVB but the TeenyBin is acutally ZV9 based. Do I have to revert back to ZV9 to use this method?
2) Is root needed to apply the teenybin in LGNPST? Or will the teenybin apply root and unlock feature?
3) If I use the teenybin will that wipe my data on my phone?
Sorry for all the questions, but I truly want to use this method to unlock my phone and flash CM10
Click to expand...
Click to collapse
1 - if you kept getting black screens, you would need to use the Mako version of the TeenyBin
2 - Root is not needed to use TeenyBin - it will apply recovery and an unlocked bootloader. Recovery can/will re-root you (boot into recovery, wipe a cache, reboot. You will be prompted to re-apply root if needed)
3 - The bin will not wipe out data no - but if you on are a truly stock rom, you will get a black screen when rebooting. The reason for this is that the bin does not include a rom specific boot.img. You CAN however boot into Recovery and flash any custom rom (including one of the 'custom' stock ones if you wish to stay on ZVB) and will able to boot just fine w/ all data in tact afterwards.

*EDIT*
wow artlan beat me to everything in his post above. I had to delete my answers. I am slow!!! lol
adding to what artlan said above... I have given some ATT users so extra explaining as well... in regards to flashing TeenyBin on a 100% stock unrooted and locked phone. Please read the post here.. http://forum.xda-developers.com/showpost.php?p=40194191&postcount=7
I will be making a flashable zip for users who are on a 100% stock phone and cant boot up after using TeenyBin. You will still have access to fastboot/recovery even if you can't boot into the rom. So you will boot into recovery, adb push the zip to your phone and flash the zip. This will give you a proper boot.img and allow the stock rom to boot. This is only needed if you do not use custom roms... which I assume is very few of you.

I just did this in my second phone that I bricked back when we were trying to get a flashable JB zip, it works! I use the mako version, I had to disconnect the phone at 85% and connect the phone back for the process to finish, then I went to recovery and flashed the stock rom, make sure you have at least 30% charge. The only thing is that I get the google locked screen when booting up, then it goes to the lg bootanimation, everything else is working fine, prime, any ideas on the lockscreen?

Lrod0175 said:
I just did this in my second phone that I bricked back when we were trying to get a flashable JB zip, it works! I use the mako version, I had to disconnect the phone at 85% and connect the phone back for the process to finish, then I went to recovery and flashed the stock rom, make sure you have at least 30% charge. The only thing is that I get the google locked screen when booting up, then it goes to the lg bootanimation, everything else is working fine, prime, any ideas on the lockscreen?
Click to expand...
Click to collapse
Awesome Glad to hear it's working for you
As for the lock screen - I have it too, but it doesn't seem to effect anything. You get the Google Logo instead of the LG one because of the SBLs used (boot splash is contained in them and not really editable as of yet) I'm fully unlocked, rooted, and rocking roms

artlan said:
Awesome Glad to hear it's working for you
As for the lock screen - I have it too, but it doesn't seem to effect anything. You get the Google Logo instead of the LG one because of the SBLs used (boot splash is contained in them and not really editable as of yet) I'm fully unlocked, rooted, and rocking roms
Click to expand...
Click to collapse
No issues here as well, I was just wondering great job guys!
LROD'S OPTIMUS G

So because the download for the zvb tot was taking forever and I wanted to start fresh, I used the zv7 tot, followed by flashing the teenybin. I then flashed stock zvb to get a GPS lock and update my profile. Well, I found a problem. When ever the phone connected to 3G it would cause a reboot (more like a "hot boot" I think.) So every time I tried to update my profile it would reboot before it updated. I tried installing another ROM, redoing the entire lgnpst flash, tried both zv9 and zvb modems, and just flashing the teenybin again. Same results everytime. I eventually got it to update I guess cuz it started showing 3G in the status bar and rebooting a second later. Flashed CM and I do in fact have 3G, and no reboots. So seems to just be an issue with stock based ROMs.
Sent from my LG-LS970 using xda premium

TeenyBin Typical Sprint Edition
TeenyBin Special Sprint Edition
much better names

I updated my ZV9 to ZVB by flashing a zip (Shadow) then flashing radios. I've been flashing between Lifeless, Imperium and CM10 (last build was 3/30) since with no problems. Do I still need to go back and LGNPST to properly update?

HdMsTrTeCh said:
I updated my ZV9 to ZVB by flashing a zip (Shadow) then flashing radios. I've been flashing between Lifeless, Imperium and CM10 (last build was 3/30) since with no problems. Do I still need to go back and LGNPST to properly update?
Click to expand...
Click to collapse
Beyond a certain build yes - though which one I don't off hand remember.
If you flash a newer AOSP rom (like CM), and you get a black screen - you will need to flash a TeenyBin to be able to boot into the rom.

I need help with Galaxy s3 t999

I have a problem with a galaxy s3. the main problem with the phone was that it would not boot up to home screen and cant go to recovery mode. I tried odin flash 4.3 but it wouldnt work saying no pit file so what i did was i try looking for one but couldnt so i use the 4.3 debrick sd file and got it stuck upgrade firmware emergency. i tried to take a pit from another S3 and still no good now i try the SD debrick again and use odin to flash 4.3. when i turn on the phone with the SD card this what happen does anyone know what cause and how to fix.
BOOT RECOVERY MODE
CHECK BOOT PARTITIONS
BOOT RECOVERY
WRITE 159488 sectors
FLASH WRITE FAILURE
ODIN MODE
PRODUCT NAME: SGH-T999
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: NONE
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 0
bootloader ap swrey: 1

What caused it to stop booting to begin with?
Are you trying to flash the NC2 build? (Latest 4.3)?
Did you try PIT files from our thread in the General section? If not where did the one you used come from?
Have you recently flashed or changed anything?
Are you able to get download mode without the SD?
Sent from my SAMSUNG-SGH-T999 using Tapatalk

DocHoliday77 said:
What caused it to stop booting to begin with?
Are you trying to flash the NC2 build? (Latest 4.3)?
Did you try PIT files from our thread in the General section? If not where did the one you used come from?
Have you recently flashed or changed anything?
Are you able to get download mode without the SD?
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
my customer bring the phone here to get repair the problem was that it would be not boot up to the home screen it would get stuck at galaxy logo and reboot. I been doing basic flashing for a long time so the 1st thing i did was doing a hard reset and coudlnt get into recovery mode so I try to flashed it with odin since i don't know what android is on i just did a flash for the newest 4.3 which it didnt work it get stuck at nand write so I try different Tar file like T989UVMC6,LJ4,LH2,MJC none of them is working. I try using a 4.3 debrick sd card and it turn on, but it got stuck at upgrade firmware emergency and asking for the pit file. I try download different pit file for t999 on XDA and none of them work. I try again with the debrick SD card and try to flash it with NC3 afterward it wont boot and show that error in the 1st post.

Jimmyyy09 said:
my customer bring the phone here to get repair the problem was that it would be not boot up to the home screen it would get stuck at galaxy logo and reboot. I been doing basic flashing for a long time so the 1st thing i did was doing a hard reset and coudlnt get into recovery mode so I try to flashed it with odin since i don't know what android is on i just did a flash for the newest 4.3 which it didnt work it get stuck at nand write so I try different Tar file like T989UVMC6,LJ4,LH2,MJC none of them is working. I try using a 4.3 debrick sd card and it turn on, but it got stuck at upgrade firmware emergency and asking for the pit file. I try download different pit file for t999 on XDA and none of them work. I try again with the debrick SD card and try to flash it with NC3 afterward it wont boot and show that error in the 1st post.
Click to expand...
Click to collapse
If you get this fixed, let me know how. I have a similar issue with the phone I got on craigslist, except I can get i to ODIN through a USB jumper. It won't go into recovery or ODIN mode through keyboard combos. It was upgraded to 4.3 previously, so I can only flash 4.3+. I've tried following firmwares:
T999UVUENC2_T999TMBENC2_TMB
T999UVUEMJC_T999TMBEMJC_TMB
Initially it was loading user profile, which was locked, so I figured, I will use "erase NAND" option from ODIN to reset (since I couldn't go into recovery). Now it only loads past t-mobile 4g logo into "SAMSUNG" screen, but doesn't go past that. I wonder what can be done, if I could make it go recovery via ODIN or something like that

Jimmyyy09 said:
my customer bring the phone here to get repair the problem was that it would be not boot up to the home screen it would get stuck at galaxy logo and reboot. I been doing basic flashing for a long time so the 1st thing i did was doing a hard reset and coudlnt get into recovery mode so I try to flashed it with odin since i don't know what android is on i just did a flash for the newest 4.3 which it didnt work it get stuck at nand write so I try different Tar file like T989UVMC6,LJ4,LH2,MJC none of them is working. I try using a 4.3 debrick sd card and it turn on, but it got stuck at upgrade firmware emergency and asking for the pit file. I try download different pit file for t999 on XDA and none of them work. I try again with the debrick SD card and try to flash it with NC3 afterward it wont boot and show that error in the 1st post.
Click to expand...
Click to collapse
Ok, first thing, never try to flash anything not specifically intended for the model device you're working with.
Odin should prevent it, but otherwise it'd probably be a major hard brick.
Before anything else, take out the battery and out it back in. If it tries to turn on by itself, its a bad power button.
Check with your customer first, but you could try flashing twrp or cwm recovery with Odin, then try to boot recovery and factory reset.
If the device tries to turn on at all, the debrick sdcard method probably won't work. But try to flash NC2 firmware with Odin again, and if it fails, copy the text from Odin here.
galets said:
If you get this fixed, let me know how. I have a similar issue with the phone I got on craigslist, except I can get i to ODIN through a USB jumper. It won't go into recovery or ODIN mode through keyboard combos. It was upgraded to 4.3 previously, so I can only flash 4.3+. I've tried following firmwares:
T999UVUENC2_T999TMBENC2_TMB
T999UVUEMJC_T999TMBEMJC_TMB
Initially it was loading user profile, which was locked, so I figured, I will use "erase NAND" option from ODIN to reset (since I couldn't go into recovery). Now it only loads past t-mobile 4g logo into "SAMSUNG" screen, but doesn't go past that. I wonder what can be done, if I could make it go recovery via ODIN or something like that
Click to expand...
Click to collapse
Two things you can try. Flash with Odin again, but check the re-partition box.
Or flash twrp or cwm with odin, then try to boot recovery and factory reset.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

DocHoliday77 said:
Two things you can try. Flash with Odin again, but check the re-partition box.
Or flash twrp or cwm with odin, then try to boot recovery and factory reset.
Click to expand...
Click to collapse
Yeah, I think repartition is the last thing I have not done. Flash twrp and cwm already tried, does not work.
Talking about repartitioninig, is there a repository of PIT files? I found a few threads where PITs are mentioned, but in each one the links are broken. This is 16Gb T999 I am looking for

You may not need it if Odin can read it from your device. But otherwise there's a thread with all pit files in General. Look over last few pages for my links.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

my mistake i wrote it wrong last night since it was closing time. i meant NC2 not NC3. here is some screen shot.
I can only boot the phone up with the SD debrick card without it i cant boot and each time it only show this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this is what happen when i flash with odin
I try T-flash and this what happen

I'm afraid things aren't looking too good. In my experience, when all of this happens it usually turns out the memory had gone bad. Probably just from use and age. It is a fairly rare thing, but I have been seeing things like this more and more often the last couple of months.
If you have the ability, you could try JTAG, but I doubt it would give much different results.
It is possible to replace the memory on the motherboard, but its not something I'd recommend. The best option IMO is to buy a used device with broken screen, but good motherboard and imei off of eBay! Then swap the motherboard.
Since it's a customers device though, its up to them, but since you said before it would get to the logo screen, and now it does nothing, keep the sdcard handy so you can show them that you didn't make things worse, it was just dying to begin with.
Unless someone else here has another idea, I don't think there's much else you can do.
Sorry I couldn't help more...
Sent from my SAMSUNG-SGH-T999 using Tapatalk

I am somewhat experienced with Samsung phone since i use one myself and i repair a lot of software issues. I have a feeling after a few flash and it boot up like that with the SD card that memory is damage on the phone. I'll just explain to my customer . I think when they drop the phone it damage the memory. thank you. I do hope someone find a fix soon for the feature.

galets said:
Yeah, I think repartition is the last thing I have not done. Flash twrp and cwm already tried, does not work.
Talking about repartitioninig, is there a repository of PIT files? I found a few threads where PITs are mentioned, but in each one the links are broken. This is 16Gb T999 I am looking for
Click to expand...
Click to collapse
I figured out what was my problem with this phone. The Up/down buttons are not working.

Having trouble with recovery and download mode

I got a hand me down S3 since my old phone (ancient infuse 4g) recently broke. It works fine at the moment, but I can't seem to get anything to work properly in terms of roms/odin/any customization.
Booting into download seems to work, as I can flash things in ODIN, but it shows a black screen. I've been using adb boot download to make sure I'm going into the right mode. ODIN shows success when flashing stuff, but I'm not so sure.
Booting into recovery just shows a black screen. Flashing to stock recovery, cwm, or twrp doesn't seem to change anything.
I can't get any of the root methods to work since I can't get into recovery. I found a rooted stock image that's current but it's in zip form, and since you can only install zip files from recovery, I can't use it. I tried a convert to tar utility but that also didn't work.
I've done a factory reset, and managed to wipe everything the one time I got into stock recovery (when I first got the phone). After that, any attempts to root, get back to stock, or do anything really but turn it on and use it, aren't working. I also tried towelroot, which worked once, then I reset the phone and towelroot no longer worked- probably due to a kernel upgrade.
A lot of the posts I found, including one about Kies, all dealt with older versions and possible bricking when downgrading bootloaders so I wanted to make sure before I did anything dumb.
Oh, and using rom manager to try to install cwm just freezes at 'flashing'. the twrp utility whose name I forget (replaced goo manager) just freezes as soon as I open it. I've also tried multiple usb ports, and made sure to only use ones directly connected to the mother board.
I'm running ucufnj1. Maybe if I had an odin flashable version of that?
What do?

Did you try flashing a custom recovery in Odin? When it finishes flashing recovery, do not let it reboot. Just remove the battery and try booting into recovery.
I recommend using Philz Touch for the d2lte.

audit13 said:
Did you try flashing a custom recovery in Odin? When it finishes flashing recovery, do not let it reboot. Just remove the battery and try booting into recovery.
I recommend using Philz Touch for the d2lte.
Click to expand...
Click to collapse
I tried that with cwm and twrp, removing the battery and all, but I got a black screen with both. Just an unresponsive black screen.

Please help!

yoonietang said:
I tried that with cwm and twrp, removing the battery and all, but I got a black screen with both. Just an unresponsive black screen.
Click to expand...
Click to collapse
Are you checking auto-reboot in Odin?

audit13 said:
Are you checking auto-reboot in Odin?
Click to expand...
Click to collapse
I make sure auto reboot is unchecked, then I take the battery out and try to start into recovery. I'm also having trouble booting into download mode with the button combo (vol down, home, power) so I've been using adb reboot download to do it.

Can you use adb commands to enter recovery?
Have you tried flashing the latest Philz Touch doe thr d2lte? I highly recommend it.

audit13 said:
Can you use adb commands to enter recovery?
Have you tried flashing the latest Philz Touch doe thr d2lte? I highly recommend it.
Click to expand...
Click to collapse
Doesn't work =( Still getting the same black screen when I try to get into recovery.

If you can somehow manage to get into download mode, let me know what it says on the screen. The important thing is to make note of the model # and the presence of a warranty bit line.
If you can't get into download mode, try installing the Samsung Info App from the Play Store and use the app to find your bootloader and modem version.

audit13 said:
If you can somehow manage to get into download mode, let me know what it says on the screen. The important thing is to make note of the model # and the presence of a warranty bit line.
If you can't get into download mode, try installing the Samsung Info App from the Play Store and use the app to find your bootloader and modem version.
Click to expand...
Click to collapse
I honestly can't tell if I'm getting into download mode or not. I *think* I'm getting into download mode except with a black screen for some reason, as ODIN claims success when flashing stuff. I also used adb reboot download to eliminate any doubt about holding the right buttons to access it, so that helps narrow down the possible source of the problem. I believe my dad (previous owner) had the screen replaced at some point. Could this be a wobbly connection?
Phone model is sgh-i747rwbatt.
Bootloader, Baseband, PDA, and CSC versions are all UCUFNJ1 (csc is i747attfnj1).
I can't seem to find modem version- is that baseband? Modem model is MSM8960.

Weird but the AT&T S3 is the sgh-i747. There should not be any letters or numbers after the second 7.
In download mode, are you seeing the Android guy? Are you sing the button combination or fastboot commands to get into download mode? USB debugging must be on to use fastboot commands.

audit13 said:
Weird but the AT&T S3 is the sgh-i747. There should not be any letters or numbers after the second 7.
In download mode, are you seeing the Android guy? Are you sing the button combination or fastboot commands to get into download mode? USB debugging must be on to use fastboot commands.
Click to expand...
Click to collapse
just had to go there. 1st three google search results for sgh i747rwbatt pulled up a white S3. (?). never knew or heard of.
"all i can really do , is stay out of my own way and let the will of heaven be done"

audit13 said:
Weird but the AT&T S3 is the sgh-i747. There should not be any letters or numbers after the second 7.
In download mode, are you seeing the Android guy? Are you sing the button combination or fastboot commands to get into download mode? USB debugging must be on to use fastboot commands.
Click to expand...
Click to collapse
usb debugging is on. Download mode just shows a black screen, nothing at all, whether I use adb reboot download or the button combo to get into. Odin reports that it sees the phone though.

would like to get @audit13 opinion on this , but you can use flashify and mobile odin to flash with. i have no experience with mobile odin and have only used flashify for .img and not .zips. he might be more knowledgeable about these apps performance records.
"all i can really do , is stay out of my own way and let the will of heaven be done"

Since the LCD remains black when you boot into download mode, I assume you obtained the phone information using the Samsung Phone Info App.
Are you able to issue fastboot commands in download mode? In download mode, does fastboot devices return your phone?
Unfortunately, I know nothing about mobile Odin or Flashify. I have never used these tools and don't have an s3 anymore.

audit13 said:
Since the LCD remains black when you boot into download mode, I assume you obtained the phone information using the Samsung Phone Info App.
Are you able to issue fastboot commands in download mode? In download mode, does fastboot devices return your phone?
Unfortunately, I know nothing about mobile Odin or Flashify. I have never used these tools and don't have an s3 anymore.
Click to expand...
Click to collapse
Fastboot commands don't work. I tried installing the fastboot drivers, but I still get nothing returned when I try 'fastboot devices', so I couldn't try any of the other fastboot commands. I'm not 100% sure if it's the drivers on my PC or the phone that's the issue, since a lot of the samsung/google drivers seem a bit finicky, but I did install minimal adb and fastboot from this forum.
Yes, I used the samsung phone info app (it's not official, right? It's made by vndnguyen?).
In regards to odin mobile and flashify, when I googled flashify (someone else mentioned it on reddit when I asked there) it said it required root. Unfortunately, I still can't get root due to the recovery issues, or I'd be able to use any number of methods.

When you try to enter download mode, do you see the warning screen where you press the volume key to continue to download mode?
Since you can't issue fastboot commands, this leads me to believe that the phone may not be entering fastboot mode. In fastboot mode, you may be able to push a recovery image to the phone.
Could you post a screen shot of your Odin screen with the phone connected?

audit13 said:
When you try to enter download mode, do you see the warning screen where you press the volume key to continue to download mode?
Since you can't issue fastboot commands, this leads me to believe that the phone may not be entering fastboot mode. In fastboot mode, you may be able to push a recovery image to the phone.
Could you post a screen shot of your Odin screen with the phone connected?
Click to expand...
Click to collapse
When I boot into download or recovery, there is nothing but a black screen, nothing else at any point at all.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Again, nothing but a black screen when I boot to recovery or download. I do get the vibration to confirm the device turning on though.
Also a screenshot showing fastboot

When using the button combination for download mode, I believe the first screen you see is a warning screen, then you need to press the volume + key to enter download mode. Are you pressing the volume up key?
Open Odin, flash recovery, and then take a screen shot of the Odin screen after it finishes flashing recovery. This may provide more clues as to what's happening.

audit13 said:
When using the button combination for download mode, I believe the first screen you see is a warning screen, then you need to press the volume + key to enter download mode. Are you pressing the volume up key?
Open Odin, flash recovery, and then take a screen shot of the Odin screen after it finishes flashing recovery. This may provide more clues as to what's happening.
Click to expand...
Click to collapse
Same when I try twrp of philz touch. However, when I flashed philz and then booted into recovery, I get a vibration when I touch the screen. This leads me to believe that the recovery is active, but the screen is off for some reason. Maybe if someone could walk me through flashing an image from recovery, step by step, I could do it blind?
Also, it seems that booting into download via key press requires you to press the volume up button to active download mode but using adb reboot download does not (based on when odin/my PC detected the phone entering download mode). Regardless, I tried both ways.
Edit: I copied and pasted the OP from another forum, and didn't realize it cut something off- I believe that my dad at some point had the screen replaced. Could it be a loose connection? It seems unlikely since I managed to get into recovery once when I first received the phone.

Nokia N1, wiped system, stuck on splash screen (Powered by Android) (Update!)

Dear Xda,
This is my situation, i had a bootloop so i ran the temporary recovery method explained in the thread "Nokia N1 Rooted with Google Play!" in the general forum of the Nokia N1
But i accidentaly removed the system partition (which boots the system and shows the boot animation etc, after the splash screen)
I can however boot into the bootloader with volume down+power as well as going into the temporary recovery to wipe and flash stuff.
I figured a way to fix this, this is to push or copy a update.zip from my pc (with the original nokia n1 files) to my nokia n1,
but the problem is adb does not recognize this device in the cmd with the command adb devices, and the hardware id is having ???? in device manager (Windows).
Does anyone maybe know a way to push files to this device in either bootloader mode or temporary recovery or maybe another way, as i am stuck with this.
If something is not clear or if i need to post images of my situation of more information please say so,
also i have the taiwanese version not the chinese and i have also all the zip files for android 5.0.1 and 5.1.1 (latest) which 1 of the 2 i need to push to my device to restore the system partition.

Ok, so far i have not gotten an answer from someone,
so i went to look around other forums and identical devices, the closest being the zenphone 2, as they use the same intel processor the intel atom z3580.
I have also looked around alot in the nokia n1 forums on search for the original taiwenese firmware as i have found a way to custom flash the device if it is hard bricked (as in no adb, system or recovery)
I found out that the new intel phone flash tool required a flash.xml file to (re)flash firmwares in order to restore it, so i have been googling around for older phone flash tool programs as i have stumbled upon a nokia n1 thread somewhere where it showed a picture of a custom flash (without the flash.xml file)
I have managed to get a fastboot connection with an old intel phone flash tool program and been trying to flash chinese firmwares to it, but so far it keeps on failing for some reason
I have a feeling that it might be possible to resurrect a broken nokia n1 with the right firmware when you only have access to the fastboot (power up+volume down), we might as well use this method if succesfull to fix bootloops if no recovery is available (as it was with my taiwanese version for some odd reason)
I will attach screenshots of what i have so far, if anyone is interesting in helping me or have an idea please say so.
p.s. i keep on trying to do more research and fiddle more with it, as it cant be more broken than it is now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Sadly, i can not go on any further, i have tried and flashed to much files and the nokia bootloader has locked itself, neither does oem unlock commands work with a fastboot flash file, i feel like i was very close to recover the nokia n1, but now it will forever be paperweight, as i have no recovery, no system, no adb, and a locked bootloader so no fastboot anymore.
If anyone have a solution or advise i'm open for this, but until then i can not proceed to test further for people who have like me bricked their device and turned it into useless paperweight (and i feel like the nokia was really vulnerable for bricking) i kinda regret buying the nokia now though.

do you have any ROM for CN version ????? my tablet is stuck in logo, i don't know how to fix it

2111002640 said:
do you have any ROM for CN version ????? my tablet is stuck in logo, i don't know how to fix it
Click to expand...
Click to collapse
Yes i do have, do you perhaps know which CN version you had? if not i can attach/link you a CN version.

It is possible to install the same or newer Version of the Firmware, which was installed on your N1
You need a full Firmware package for your tablet (CN or TW Version).
Sent from my N1 using Tapatalk

do you have full ROM for N1 tw or cn, if you have this can you share for me plêas

i have a solution to fix this error, anybody want to fix this error may be contact me
my fb: https://www.facebook.com/hjxhjx.huhu
i had fix 2 devices to live every oke

2111002640 said:
i have a solution to fix this error, anybody want to fix this error may be contact me
my fb: https://www.facebook.com/hjxhjx.huhu
i had fix 2 devices to live every oke
Click to expand...
Click to collapse
I don't have a Facebook account. Could you post your solution on here please? Thank you

Hello there! I think I had a similar problem but I managed to unbrick my device after good 24 hours of stress and facepalming after getting it stuck in splash screen late last night. I found your thread and a few others that suggested trying Intel's Phone Flash Tool, but it didn't work for me. I thought I had no fastboot, but suddenly I managed to get it to fastboot with Power + Vol Down (releasing power shortly after pressing while holding vol down a tad longer). Turns out my device was locked, so I couldn't flash anything. I had previously flashed the recovery file of A5FMB19, but I thought it hadn't worked. Alas, again I was wrong and from fastboot I was able to get to recovery mode! From there I was able to factory reset, adb sideload the full version of A5FMB19 and now my N1 is happily running with Google Play.
So if somebody still has the same problem I guess what I'm trying to say is that even if it first seems that recovery mode is not reachable, it might still be there since the device seems to be very picky about the button presses. It was that in my case, and it suddenly worked tonight while earlier it did not... This is the post that I mainly followed https://forum.xda-developers.com/no...1-chinese-version-5-1-1-update-t3183529/page6 I guess the important thing is to find a matching ROM to your recovery image.

srsface said:
Hello there! I think I had a similar problem but I managed to unbrick my device after good 24 hours of stress and facepalming after getting it stuck in splash screen late last night. I found your thread and a few others that suggested trying Intel's Phone Flash Tool, but it didn't work for me. I thought I had no fastboot, but suddenly I managed to get it to fastboot with Power + Vol Down (releasing power shortly after pressing while holding vol down a tad longer). Turns out my device was locked, so I couldn't flash anything. I had previously flashed the recovery file of A5FMB19, but I thought it hadn't worked. Alas, again I was wrong and from fastboot I was able to get to recovery mode! From there I was able to factory reset, adb sideload the full version of A5FMB19 and now my N1 is happily running with Google Play.
So if somebody still has the same problem I guess what I'm trying to say is that even if it first seems that recovery mode is not reachable, it might still be there since the device seems to be very picky about the button presses. It was that in my case, and it suddenly worked tonight while earlier it did not... This is the post that I mainly followed https://forum.xda-developers.com/no...1-chinese-version-5-1-1-update-t3183529/page6 I guess the important thing is to find a matching ROM to your recovery image.
Click to expand...
Click to collapse
How did you manage to enter recovery after entering fastboot, i can enter fastboot just fine, but my device is in a locked bootloader state after to many flash attempts, and when i try to enter recovery in fastboot it just reboots the device back into fastboot, any suggestions or ideas?

defendos said:
How did you manage to enter recovery after entering fastboot, i can enter fastboot just fine, but my device is in a locked bootloader state after to many flash attempts, and when i try to enter recovery in fastboot it just reboots the device back into fastboot, any suggestions or ideas?
Click to expand...
Click to collapse
It's been a week and it was the first time I ever tried to flash anything, but I think that in fastboot I just selected recovery mode with the volume buttons and then pressed the power button to confirm the selection. Since I had previously managed to flash in a recovery image of the Taiwan version, it worked. My saviour was that the recovery image wasn't corrupted even though my Android itself was, so I guess there was no magic trick - I just managed to do the right things finally after wrong physical button presses. If you can't get to recovery then maybe you are truly bricked. Would these suggestions be of any help? forums.oneplus.net/threads/solved-stuck-in-fastboot-bootloader-is-locked-need-help.435522/

same boat bump!
accidently wipe data cant boot stuck on android logo
i can access fastboot but no adb (unauthorize)
on 5.0.2

Found my old note 10.1 and did something stupid... need help...

I haven't used it in many years. It powered up just fine. I apparently rooted it when I first got it, and forgot. So I tried to update using the system update - it failed because of the root, which is expected.
I opened the superuser root app and told it to permanently unroot. I mindlessly accepted the following prompts, and after rebooting, it's now stuck on the main samsung note 10.1 2014 edition logo for about 3 seconds, then repeats in a loop.
I am able to get to the recovery screen where I have options:
Reboot
apply update from adb
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to boot loader
power down
view recovery log
I attempted the wipe data/factory and cache. Same results.
If I attempt to do the bootloader (either through the recovery or with the power/vol+ button) I get the prompt to enter the download mode by pressing the up button. However, it then immediately returns to the bootloop.
I screwed the pooch because I don't recall any details on what version of ROM I had on there, or any other details.
Is there a way to get me back to a point where I can install something like lineage? All of the steps I'm finding presume I can get to a working OS.
Any help would be appreciated. I really don't want to toss this tablet. It was working just fine before I decided to "fix" it.
ETA: Connecting it to a PC provides no recognition at the device manager at all. I tried different cables, different ports, different PCs.

erkme73 said:
I haven't used it in many years. It powered up just fine. I apparently rooted it when I first got it, and forgot. So I tried to update using the system update - it failed because of the root, which is expected.
I opened the superuser root app and told it to permanently unroot. I mindlessly accepted the following prompts, and after rebooting, it's now stuck on the main samsung note 10.1 2014 edition logo for about 3 seconds, then repeats in a loop.
I am able to get to the recovery screen where I have options:
Reboot
apply update from adb
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to boot loader
power down
view recovery log
I attempted the wipe data/factory and cache. Same results.
If I attempt to do the bootloader (either through the recovery or with the power/vol+ button) I get the prompt to enter the download mode by pressing the up button. However, it then immediately returns to the bootloop.
I screwed the pooch because I don't recall any details on what version of ROM I had on there, or any other details.
Is there a way to get me back to a point where I can install something like lineage? All of the steps I'm finding presume I can get to a working OS.
Any help would be appreciated. I really don't want to toss this tablet. It was working just fine before I decided to "fix" it.
ETA: Connecting it to a PC provides no recognition at the device manager at all. I tried different cables, different ports, different PCs.
Click to expand...
Click to collapse
Why don't you try flashing stock firmware?
Check for drivers issue.

mvikrant97 said:
Why don't you try flashing stock firmware?
Check for drivers issue.
Click to expand...
Click to collapse
Thanks for the quick reply. I guess that's where I need a bit of hand holding. It's been so many years since I dabbled with rooting my devices, that I've forgotten more than I remember, and I'm hitting all sorts of dead ends.
I'm willing to learn so I'll take whatever advice you're willing to offer. I've installed the samsung USB drivers, but with too many variables to nail down, I'm not sure where to start.
I have Odin, and I THINK it's the p600 (without the cell radio), but odin or adb is not seen any device connected.

erkme73 said:
Thanks for the quick reply. I guess that's where I need a bit of hand holding. It's been so many years since I dabbled with rooting my devices, that I've forgotten more than I remember, and I'm hitting all sorts of dead ends.
I'm willing to learn so I'll take whatever advice you're willing to offer. I've installed the samsung USB drivers, but with too many variables to nail down, I'm not sure where to start.
I have Odin, and I THINK it's the p600 (without the cell radio), but odin or adb is not seen any device connected.
Click to expand...
Click to collapse
Your device should show up like this in device manager
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Flashing like this

erkme73 said:
Thanks for the quick reply. I guess that's where I need a bit of hand holding. It's been so many years since I dabbled with rooting my devices, that I've forgotten more than I remember, and I'm hitting all sorts of dead ends.
I'm willing to learn so I'll take whatever advice you're willing to offer. I've installed the samsung USB drivers, but with too many variables to nail down, I'm not sure where to start.
I have Odin, and I THINK it's the p600 (without the cell radio), but odin or adb is not seen any device connected.
Click to expand...
Click to collapse
It is P605. And from this post looks like you are not the only one https://forum.xda-developers.com/t/q-galaxy-note-10-1-2014-not-recognized-in-download-mode.2494886/

erkme73 said:
I haven't used it in many years. It powered up just fine. I apparently rooted it when I first got it, and forgot. So I tried to update using the system update - it failed because of the root, which is expected.
I opened the superuser root app and told it to permanently unroot. I mindlessly accepted the following prompts, and after rebooting, it's now stuck on the main samsung note 10.1 2014 edition logo for about 3 seconds, then repeats in a loop.
I am able to get to the recovery screen where I have options:
Reboot
apply update from adb
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to boot loader
power down
view recovery log
I attempted the wipe data/factory and cache. Same results.
If I attempt to do the bootloader (either through the recovery or with the power/vol+ button) I get the prompt to enter the download mode by pressing the up button. However, it then immediately returns to the bootloop.
I screwed the pooch because I don't recall any details on what version of ROM I had on there, or any other details.
Is there a way to get me back to a point where I can install something like lineage? All of the steps I'm finding presume I can get to a working OS.
Any help would be appreciated. I really don't want to toss this tablet. It was working just fine before I decided to "fix" it.
ETA: Connecting it to a PC provides no recognition at the device manager at all. I tried different cables, different ports, different PCs.
Click to expand...
Click to collapse
Also watch this video

erkme73 said:
I haven't used it in many years. It powered up just fine. I apparently rooted it when I first got it, and forgot. So I tried to update using the system update - it failed because of the root, which is expected.
I opened the superuser root app and told it to permanently unroot. I mindlessly accepted the following prompts, and after rebooting, it's now stuck on the main samsung note 10.1 2014 edition logo for about 3 seconds, then repeats in a loop.
I am able to get to the recovery screen where I have options:
Reboot
apply update from adb
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to boot loader
power down
view recovery log
I attempted the wipe data/factory and cache. Same results.
If I attempt to do the bootloader (either through the recovery or with the power/vol+ button) I get the prompt to enter the download mode by pressing the up button. However, it then immediately returns to the bootloop.
I screwed the pooch because I don't recall any details on what version of ROM I had on there, or any other details.
Is there a way to get me back to a point where I can install something like lineage? All of the steps I'm finding presume I can get to a working OS.
Any help would be appreciated. I really don't want to toss this tablet. It was working just fine before I decided to "fix" it.
ETA: Connecting it to a PC provides no recognition at the device manager at all. I tried different cables, different ports, different PCs.
Click to expand...
Click to collapse
Please try to get into download mode for odin to recognize your tablet

Ok, so using another PC and yet another cable, I was finally able to see this pop up on the device manager when in the "update with adb" option:
Unfortunately, I cannot get the tablet to stay in download mode. As soon as I confirm to go to download with the vol+ button, it immediately starts to boot loop.
On the other hand, when in the adb mode, the PC does recognize the device when it's attached and I can see it with "adb devices" command.
But unless there's a way to get it to go to download mode, I'm screwed, right?

mvikrant97 said:
Also watch this video
Click to expand...
Click to collapse
Yes, but that is my problem. I cannot get to the download screen. I can press up to select it, but then poof, it goes to cycle again. Unlike the guy in the video:

OMG!!! Pressing volume DOWN (cancel) actually put it into download mode!!

erkme73 said:
OMG!!! Pressing volume DOWN (cancel) actually put it into download mode!!
Click to expand...
Click to collapse
Now you are good to go. Odin will detect and you can flash it.

Thanks... doing it now. I'll let you know how great you are as soon as it starts working! Thanks...

Works perfectly. On "latest" 5.11 stock. No I remember why I rooted back in 2014... Now hunting for a simple root.

erkme73 said:
Works perfectly. On "latest" 5.11 stock. No I remember why I rooted back in 2014... Now hunting for a simple root.
Click to expand...
Click to collapse
That's great to see your device is working now.

erkme73 said:
Works perfectly. On "latest" 5.11 stock. No I remember why I rooted back in 2014... Now hunting for a simple root.
Click to expand...
Click to collapse
If you really wanna stay on stock you can use Chainfires Autoroot for this device.
Anyway, my P605 is on LOS17.1 running stable.