Develop Bugs

tmobile sgh-t999 s3 wont boot completely need help

Hello everyone. I have a tmoble s3 that was once rooted and then updated with kies and ran on stock firmware. The phone was updated to the latest firmware but I had lost root. I left it alone and all was well for many months. The other day after charging the phone it was unable to complete the boot. I can boot to recovery and to download mode but it wont safe boot or normal boot it hangs up at the last phase. I took the phone in to a samsung rep and he tried to load the firmware on the phone he did a home recovery but the phone still doesnt complete the boot. I had already tried factory reset before taking it in and it failed. I am not sure how to fix it since it isnt rooted any ideas on how to fix the phone? Is it possilbe to fix this phone or is it just a paperwieght now? Can you odin a pre rooted rom on a phone that isnt rooted and wont boot in order to enable usb debugging or developer options? I have no idea how to proceed so any advice would be appreciated. Thanks in advance

To quickly check the phone's functionality, I suggest the following:
1) download Odin 3.07 from here: https://www.google.ca/url?sa=t&rct=j...07763241,d.dmo
2) download the tar version of TWRP 2.8.6.0 from here: https://dl.twrp.me/d2tmo/
3) download the latest cm12.1 for the phone from here ( http://www.cmxlog.com/12.1/d2tmo/) and save it to a micro SD card;
4) download the version of cm12.1 gapps you want from here (https://wiki.cyanogenmod.org/w/Google_Apps) and save it to the same sd card where you saved CM12.1;
5) place the micro SD card into the phone;
6) boot the phone into download mode;
7) open Odin 3.07 and uncheck everything except f. reset time;
8) click on PDA and browse to the tar TWRP file and select it;
9) connect the phone and it should show up as a com port in Odin;
10) flash TWRP;
11) when you see the word RESET in the status window, remove the USB cable, remove the battery, replace the battery, use the button combination to get into recovery which should now be TWRP;
12) perform a full wipe of system, data, and cache;
13) flash CM12.1 and gapps from the micro SD card;
14) reboot and enjoy

Undo Virtual Repartition - INVALID PARTITION SELECTION

I have followed the instructions to return to stock, but they just do not work at all. Modified TWRP can see internal storage, but standard TWRP can not.
I shouldn't have to Odin back to stock, that seems ridiculous.
Currently running CM13 with the Virtual Repartition, all is working fine, although slow.
Here is what I have tried so far.
Attempt 1:
Flash newest TWRP image via Heimdall.
Boot intro standard TWRP.
WIPE-->ADVANCED WIPE-->REPAIR OR CHANGE FILE SYSTEM-->INVALID PARTITION SELECTION, and the only thing visible is Dalvik Cache.
Attempt 2:
Boot back into CM rom to test. It works.
Flash back to modified TWRP via Heimdall. Recovery works and can see the file system.
WIPE-->ADVANCED WIPE-->REPAIR OR CHANGE FILE SYSTEM-->CHECK INTERNAL STORAGE-->INVALID PARTITION SELECTION, and my check mark disappears from the INTERNAL STORAGE checkbox.
Wipe internal sdcard.
Try again WIPE-->ADVANCED WIPE-->REPAIR OR CHANGE FILE SYSTEM-->CHECK INTERNAL STORAGE-->INVALID PARTITION SELECTION. Same result as above.
Flash back to standard TWRP.
Same behavior as Attempt 1.
I'm going around in circles and getting nowhere. Odin seems like overkill for what should be very simple. What am I missing?
Any help would be appreciated! I am following the guides and it's just not working. I've been doing this since 2009 so I'm not a complete noob.
Thanks!

same issue here, I'm right now downloading stock firmware hoping that will solve this issue, then root - install custom recovery & re-do the re-partition.

I have downgrade the twrp to the previous version, and all the partitions were visible again. Please do the same.

Confirmed, that was indeed the issue.

So there's no need to use Odin to get back to stock partitioning? Which twrp are you using?

nawlage said:
So there's no need to use Odin to get back to stock partitioning? Which twrp are you using?
Click to expand...
Click to collapse
hey...
same pb on me.. invalid partition selection.. i used the recovery-twrp-3.0-hercules.tar..which twrp previous version r u talking about..?

Galaxy Note 8 (GT-N5110) PC Connection Problems - Boot Loop - SOLVED by ME

NO ONE?????
ODIN --> Flash Stock Recovery (AP) with NAND Erase All Option Checked (because it seemed to make sense) + Auto Reboot + F. Time Reset --> Reboots to Stock Recovery (did not work before) --> Reboot into Recovery --> Wipe Data/Cache and Dalvik just to be safe (this crashed it before) --> Reboot. THE END
TL/DR: I am currently stuck on recovery/update mode. Any attempt to wipe data or clear dalvik crashes it. any attempt to access data through TWRP crashes it. Flashing stock rom or custom rom does not help. Somethings wrong with /data? It thinks it has root from the CF Auto Root, but does not really? Something wrong with partitions? Should I wipe the nand with ODIN 3.10? Repartition? ugh ... Please help ...
I have searched the forums and found nothing that describes this issue precisely. I have also tried to apply various suggestions to repair, which, for the most part seems to have made it worse. I am hoping that people still look at this forum.
PC - Windows 7
Initially @4.2.2 ---> Touchwiz debloated stock ROM which I rooted. It worked for a couple years, but the device crashed frequently. I do not recall much about the installation, but believe that I used CWM/TWRP at the time. After installing the ROM, I ran triangle away (out of the box, it had 4.1.2, i recall)
I decided to upgrade to the most recent stock ROM (4.4.2). In order to do so, I used an easy installer I found else where on XDA. (http://forum.xda-developers.com/showthread.php?t=2773712 ---ODIN One Click exe). The device was not initially recognized, so I reinstalled the official driver package (said that they already existed, but I installed again anyway). Ran 1-click and it appeared to work.
Initially, the device booted (long startup) and seemed to function. It also preserved all data and programs (presumably did not touch the internal memory - 16 GB) and possibly root /data.
I then tried to root through most recent ODIN with CF auto root. This appeared to work and rebooted (again, showing the updating android apps screen before fully booting).
The only thing that i could find that had changed was the wallpaper (showed on lock screen but not on home screen). I could no longer find the image, so tried to go to /data/data to find it with root explorer equivalent. This is where it started to act weird.
NOTE: I did not clear anything (system cache, etc. at any point)<--a lie (see below)
It showed the root folder fine, but when I clicked on /data it took a while and could not access it. It either rebooted itself or I rebooted, but this time it was stuck in a boot logo loop. I entered download mode and flashed TWRP through ODIN. I set it to not reboot automatically so that the bootloader was not overwritten automatically (thus losing recovery). TWRP came up. The computer recognized it as a Media Device after I mounted USB storage. Just in case, I copied all of the important files from the internal SD Card to my computer. I then tried to go to the file explorer to copy the wall paper and it forced a reboot. At this point it was stuck on a logo screen boot loop again. I was able to enter Download mode and reflash TWRP. This allowed me to enter recovery again, however, now it would only boot directly into recovery (or Download mode if I did the button combo). The interesting thing was that it would reboot two or three times before successfully entering TWRP.
I believe I tried to reflash the stock ROM at this point, which might have worked but made no difference.
I was also having a lot of problems getting Windows to properly recognize the device. I had to reinstall the drivers a couple times. I tried Kies after the problems started and it tried to connect by failed. The diagnose connection did not work either. I was not able to get Kies to connect though I tried several times throughout the attempted repair
I downloaded a stock-rooted 4.4.2 ROM from here and tried to flash it. It failed.
I also tried to flash via Heimdall, but initially could not find any stock ROMs for Heimdall for the Galaxy 8. (The driver utility that is included helped to get the phone recognized by Windows sporadically).
I decided to switch over to CWM touch recovery, which I flashed via ODIN (I was having issues with TWRP again and also could not get windows to recognize the device as a media device when I mounted USB storage). This worked after a couple tries and I was able to enter CWM. I attempted to flash the stock ROM but it failed. Either at that point or when I tried to mount data it returned an error that device did not have root. Again, it would only boot into CWM (on its own) or Download mode (with key combo). At some point around here I cleared the cache and dalvik (error) after it returned an error saying insufficient space when trying to flash ROM.
I dissected the .exe from the autoflash used in the beginning (stock unrooted 4.4.2) and used the contents (system.img, cache.img, hidden.img, tz.img, recovery.img and one other I do not remember) in Heimdall to create a Heimdall package. At this point I figured out I did not need to create the package, but just specify the individual files. I flashed. It appeared to complete System.img successfully and then failed. Tried again with the same result.
Now when I rebooted, it would enter download mode with the Key combo, but otherwise it booted instantly to an error screen to the effect that a firmware installation had failed and to use the repair function in Kies to fix. Kies still did not recognize it.
At this point, I figured I should stop. Currently I can get to the download screen or the error screen. The computer recognizes it but intermittently fails to install driver. Zadig.exe sees it as Gadget Serial. Sometimes Windows just sees it as SAMSUNG_Android, in which case drivers fail. Once or twice I got it to recognize it as Samsung USB Composite Device, but Kies would still not work.
That's all i have for now. If more information is needed, let me know and I will update the post when I get home from work tonight (this is from memory).
Thank you
UPDATE: last night I went home and was able to get it back to the point where I could flash TWRP or CWM recovery. If I try to flash Stock Recovery, it fails. A minor problem is that I cannot turn it off - it just turns it self on again, so the battery keeps running down.

SM-T320 is rooted, but no "advanced" in recovery mode

I apologize if this has been covered before, but several searches haven't turned it up.
I'm trying to upgrade my Galaxy Tab Pro 8.4 to Android 7.1 and I'm running into a roadblock in the recovery mode. I have options for Wipe data/factory reset and Wipe cache partition, but there's no Advanced option, so I can't wipe the Dalvik cache.
The tablet is rooted -- I checked it after running Odin, and even ran Odin once more to be sure -- and I had Debugging checked under Developer Options, so I think I should be seeing the Advanced option, but it's not there.
I tried installing the new OS anyway, but I got failure messages, and then the tablet rebooted itself to 4.4.2, still rooted. I've restarted Developer Options and re-checked Debugging.
I must be missing something, but I can't see it. Thanks in advance.

This is driving me insane. Every time I think I'm making progress I run into a roadblock. At this point I'm just trying to load/install TWRP recovery so I can do a thorough wipe, including the Dalvik cache, but although I can find the flash file in my file manager, TWRP doesn't see it.
On the tablet's own storage TWRP starts its search at emulated/0, but I can't find folders in the file manager called emulated or 0. It will also look in sdcard, but even though I've copied the file there, TWRP doesn't see it, although it seems to be looking for "extsdcard." It also doesn't see zip files I've downloaded to the sd card, if that matters. It seems that TWRP can only find folders, not files.
I uninstalled and reinstalled TWRP, but it's the same. So I uninstalled TWRP again and tried to go with CWM, but it's not compatible with my tablet.
Part of me knows there must be a solution somewhere, but this has just about reached the point of "life's too short." If anyone can offer any help, it would be greatly appreciated.

I've finally had some success! I found instructions for installing TWRP with Odin, and they worked. And so, I expect, did the TWRP backup of the tablet's OS. All I need now is a Nougat 7.1 download that works; the one I have now:
Galaxy Tab Pro 8.4 Lineage OS 14.1 [mondrianwifi] [Android 7.1.1 Nougat]
...isn't working. TWRP attempted the zips I downloaded (OS and GAPPS?) but the verification failed. So at this point I can only boot to TWRP. If I just start the tablet normally, it hangs at the Samsung logo screen, and while I can turn it off, it starts itself again after 10 seconds or so, requiring a boot to TWRP and shut down from there.
I'm hopeful I'll find downloads that work, but some of the links I've found appear to have expired. I should be able to go back to 4.4.2 from the backup, but since I've gotten this far I'd like to follow through. It looks like I have more searching ahead of me.

More success! I found the following link to the OS and downloaded the Pico GAPPS as that author suggested, and it worked! My thanks to Marc0601!
https://forum.xda-developers.com/ga...m-resurrection-remix-5-8-5n-02-09-18-t3837764

Installation zip-file e-0.19-n-20211023142427-dev-i9305 android to Samsung Galaxy S3 gt I305

Hello
I cannot install new android system to my phone Samsung Galaxy S3 gt I305. Can someone advise what to do?
What I have done is following.
1. Installed TWRP version 3.7.0_9-0, After entering the TWRP I follow the procedure of istallation.
2. Wipe and Swipe to Factory Reset.
3. Advance Wipe: Dalvik/Cache/System/Vendor and swiped to wipe.
4. Went to Install: Selected storage: Internal Storage.
5. Choosing the file e-0.19-n-20211023142427-dev-i9305 and Swipe to confirm Flash.
Now the phone seems to installaing the zip-file e-0.19-n-20211023142427-dev-i9305.
6, Reboot System.
7. After the system reboots it looks like the android is installing on the Samsung phone. However a letter e with a jumping dot below it is displayed and this goes for hours without any success of installation. I have waited 8 hours and nothing happens.
Is there something that I have missed to do?
Attached picture of the last step that I have reached in the installation process.
Please help.
Best regards
User: samsung1979

Hi!
Standard troubleshooting answers are:
1. You did not unlocked your phone's bootloader, enabled USB debuggind, USB debugging(security) and enabled OEM(bootloader) unlock in the phone's settings.
2. You did not flash vbmeta from your current ROM, to disable verity.
3. You did not flash a good bootloader before flashing.
4. Your SD card is corrupted.
5. You did not fix the File System from the recovery
6. You didn't allow modifications and left the recovery in read only mode.
7. The ROM is unsuitable for your phone. Sometimes this happens even if you were told it is for your ROM and it was written on some forum.

Hi
Following question, is it possible to troubleshoot these steps if there is not any android anymore installed and no backup file created?
Meaning that the phone only has access to the TWRP settings and all other phone data is deleted.

If all other data is deleted, please re-install an original ROM, This can normally be done from the manufacturers software, like a PC suite.
Before reinstalling the original ROM, please try flashing the bootloader with ADB and fastboot.

Downloaded it reinstalled and installed android 13 and it is working!
Thank You!