Database Users

[Q] Problems restoring to 4.3 stock

Hello,
I've only yesterday rooted my phone for the very first time and followed a guide on how to flash PA. In the guide it told me to flash a radio and boot loader, which apparently I wasn't supposed to flash because I was on 4.3 already. So I didn't have service, someone told me to reflash 4.3 which I did using the stock rom downloaded from android dev page. But It won't flash the system it returns an error regarding the usb port. I flashed 4.2.2 which did flash the system but is apparently stuck on the loading screen (nexus X) for about 20 mins or so. Any help on how to reflash stock 4.3 and then reflash just PA 3.99 and Gapps?
cheers

RabbeV said:
Hello,
I've only yesterday rooted my phone for the very first time and followed a guide on how to flash PA. In the guide it told me to flash a radio and boot loader, which apparently I wasn't supposed to flash because I was on 4.3 already. So I didn't have service, someone told me to reflash 4.3 which I did using the stock rom downloaded from android dev page. But It won't flash the system it returns an error regarding the usb port. I flashed 4.2.2 which did flash the system but is apparently stuck on the loading screen (nexus X) for about 20 mins or so. Any help on how to reflash stock 4.3 and then reflash just PA 3.99 and Gapps?
cheers
Click to expand...
Click to collapse
Go into recovery and do factory reset, that should get u past the nexus X... Then just flash pa and gapps your done, flashing a radio and bootloader shouldn't have hurt anything unless u flashed wrong ones, recheck your versions on the files. U should be on a radio that ends in 84 (it works on 4 2.2 so dont worry... U dont need to be on 4.3 to flash pa, just factory reset first

drawde40599 said:
Go into recovery and do factory reset, that should get u past the nexus X... Then just flash pa and gapps your done, flashing a radio and bootloader shouldn't have hurt anything unless u flashed wrong ones, recheck your versions on the files. U should be on a radio that ends in 84 (it works on 4 2.2 so dont worry... U dont need to be on 4.3 to flash pa, just factory reset first
Click to expand...
Click to collapse
I wanted to do that but my sd had been wiped, but it's been solved

Nexus 4 stuck on boot animation

Guys I know there are a ton of threads with this problem but no matter what I try, i'm still stuck on a boot loop.
So basically I had PA Rom 3.99 RC2 on my nexus and everything was fine. I then tried to flash PA AOSP kit kat build
but my phone would not boot so I went with a factory image occam 4.3 Phone booted and all was good. I was liking the
stock experience and then about 4 days later after a reboot, phone got stuck on the boot animation X. It would not get out of it
so I decided to flash PA Rom 3.99 rc2 again via ADB push zip. factory reset, installed the rom and gapps, wiped caches and thought i was good to go. Well the phone again would not get past the boot animation of PA.
i then decided to go with the Factory image occam 4.3 via fastboot and installed it and everything. Again stuck on the X. So then I tried PSX rom 4.3 again via adb push, did my factory reset and flashed the rom and gapps and superSu. Also got stuck on the boot animation. Left it for over 2 hours bootlooping and nothing.
Going crazy I went and fastboot the 4.2.2 JDQ39 img and downgraded bootloader, baseband. Installed it and again, stuck on the X animation. just hangs there.
Any help? i don't know what else to try, currently using my HD2 and it is sooo slow :cyclops:

Make sure to use latest cwm recovery. Avoid using twrp recovery. Use the toolkit and flash stock image. It will wipe everything in the phone but it will fix it.
Sent from my Nexus 4 using Tapatalk

badboy47 said:
Make sure to use latest cwm recovery. Avoid using twrp recovery. Use the toolkit and flash stock image. It will wipe everything in the phone but it will fix it.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Thanks for the suggestion but still nothing. Updated CWMR to 6.0.4.3 and tried the 4.3 stock image. Still hangs on bootup. android file transfer recognizes the device is plugged in via usb but just gives me the error "could not connect to device"
Oh man I don't know what's wrong with my nexus

bump bump

I'm having this same issue, and it happened just like you. I flashed CM 10.2 nightly 20131114 this morning and I tested it to make sure everything was working. I decided to reboot the phone, and after that I keep getting stuck at the boot animation no matter what I did. To no avail, I reflashed a working zip, restored a backup, restored another backup, flashed the 4.4 factory image (wiping the entire phone), the 4.3 factory image, and then I read that the 4.2 baseband can fix it, so I flashed the 4.2 factory image. That 4.2 image gets it to boot, but without baseband. Right now I'm trying different radios just to see if I can get service again. If it matters, I was running the hybrid 33/84 radio for T-Mobile's LTE when this happened. Very, very peculiar situation here. I've never had anything like this happen, and especially remain an issue after wiping the entire device. I'm hoping it's not a sudden hardware issue.

i jst flash factory image of 4.4 n nw my phone is stuck o the boot animation screen plz help

Hmmy 4444 said:
i jst flash factory image of 4.4 n nw my phone is stuck o the boot animation screen plz help
Click to expand...
Click to collapse
just re-flash 4.2, it'll work. I've been doing that since Monday. but I want kitkat too!!

my device is stuck on the boot animation too. is there a way to reinstall the default 4.3 recovery and just rerun the update or something basic like that? my device was almost at stock before running the update. the only two things: twrp and rooted via recovery. so i thought everything will work fine and now there is no backup...

badboy47 said:
Avoid using twrp recovery.
Click to expand...
Click to collapse
Why?

Just fastboot flash all the image files (boot.img,recovery.img....) from the factory image.

SPH-L720T, rolled back from Cm 12.1 to stock OK3, lost all Recovery

I did a search and was not able to find a solution to this problem. Any help would be appreciated.
As stated in the title, I rolled my SPH-L720T from CM 12.1 back to stock Lollipop OK3 downloaded from Sammobile (I was careful to make sure that I download the correct FW for the L720T and not the L720). After the rollback, I am no longer able to access any recovery, not the stock recovery, or TWRP or CWM after installing them.
I want to do a Factory reset but can't find a way to do it other than in Recovery.
Any ideas?

I found this list of Sprint dialer codes, but it doesn't give a code for a full factory reset. Still can't access any recovery however, would still appreciate any help with that.
http://forum.xda-developers.com/showthread.php?t=2261538

doraville said:
I found this list of Sprint dialer codes, but it doesn't give a code for a full factory reset. Still can't access any recovery however, would still appreciate any help with that.
http://forum.xda-developers.com/showthread.php?t=2261538
Click to expand...
Click to collapse
Install recovery with Odin, be sure to uncheck Auto Reboot in Odin before installing.
{
"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"
}

bilgerryan said:
Install recovery with Odin, be sure to uncheck Auto Reboot in Odin before installing.
Click to expand...
Click to collapse
Thanks for your response! I did that...multiple times, still not able to access recovery, any recovery. No matter what I do it goes ahead and does a normal boot.

doraville said:
Thanks for your response! I did that...multiple times, still not able to access recovery, any recovery. No matter what I do it goes ahead and does a normal boot.
Click to expand...
Click to collapse
You're holding Power+Volume Up until it says Booting Recovery in blue right? If you still can't get any recovery you need to Odin OK3 again until you can at least get to stock recovery.

bilgerryan said:
You're holding Power+Volume Up until it says Booting Recovery in blue right? If you still can't get any recovery you need to Odin OK3 again until you can at least get to stock recovery.
Click to expand...
Click to collapse
Yes, VolumeUp+Power until blue text appears. Also VolumeUp+Power+Home just to be sure. Still always does a normal Boot. Have gone back and reloaded OK3 several times, same result.
I have several L720's, have done this with them no problem. This is the only 720T. I was very careful to make sure that I downloaded the correct FW from Sammobile. I had CWM recovery back when I was running CM12.1, it worked fine. After I rolled back to OK3 is when I lost all forms of Recovery. It's a mystery.
I'm wondering if I might have corrupted the recovery partition somehow. Has anyone heard of this and if there is a way to to repair it?

Well, I don't know what I did differently, but I went back and reloaded OK3 AGAIN (I had already done this three or four times) and I got back Recovery. I'm glad it got resolved but I wish that I knew what I did to fix it.
Anyway, thanks for the help bilgerryan!

OK, it appears that I have reproduced the problem. I had everything working, Recovery, Download, Boot on OK3 unrooted. Installed latest TWRP tar (2.8.4.0) and the problem returned. Reinstalled stock OK3 in Odin, same problem. Tried to Odin an earlier TWRP, same problem.
I'll just keep reinstalling OK3 stock until I (hopefully) get the stock Recovery back, then I'll try to isolate the step that caused the problem. I think next time I'll install CWM using Heimdall to see if that sidesteps the problem.

It appears that the phone will only boot into recovery about one time out of ten attempts, and even then it shows a red triangle while booting into recovery. This will make it impossible to install a custom recovery since you need to be able to be able to boot into recovery the first time after installing a custom recovery.
I've obviously got some sort of problem with the Recovery partition, not sure where to go from here.

Never did figure out why it doesn't reliably boot into Recovery. The only thing I was after on this particular phone was I wanted to enable the Native Hotspot. Was able to Root using Kingoroot, then enabled native Hotspot using SQLlite method. I'll save this recovery mystery for another day unless I stumble across the solution.

doraville said:
It appears that the phone will only boot into recovery about one time out of ten attempts, and even then it shows a red triangle while booting into recovery. This will make it impossible to install a custom recovery since you need to be able to be able to boot into recovery the first time after installing a custom recovery.
I've obviously got some sort of problem with the Recovery partition, not sure where to go from here.
Click to expand...
Click to collapse
The red triangle is simply stock recovery, it always shows that. Nothing wrong there. Don't use Kingo root. I've seen another person experiencing all kinds of problems after using it. Odin TWRP, it has a Root method that it implements when you reboot to system and then you just download SuperSU from the Play Store and you are rooted.

bilgerryan said:
The red triangle is simply stock recovery, it always shows that. Nothing wrong there. Don't use Kingo root. I've seen another person experiencing all kinds of problems after using it. Odin TWRP, it has a Root method that it implements when you reboot to system and then you just download SuperSU from the Play Store and you are rooted.
Click to expand...
Click to collapse
Yes, the problem is that when the phone will only boot into Recovery one out of ten tries it is very difficult (impossible?) to install a Custom recovery because you need to be able to boot into Recovery immediately after installing the Custom Recovery to prevent it from being overwritten with the stock recovery.
I haven't noticed any problems with Kingroot so far. This particular phone's only purpose is to serve as a Hotspot. As long as it will do that reliably I'll be happy with it.

doraville said:
to install a Custom recovery because you need to be able to boot into Recovery immediately after installing the Custom Recovery to prevent it from being overwritten with the stock recovery.
Click to expand...
Click to collapse
This statement is 100% false, stock recovery does not overwrite custom recovery ever unless you Odin stock. You don't have to immediately boot into Recovery either.

bilgerryan said:
This statement is 100% false, stock recovery does not overwrite custom recovery ever unless you Odin stock. You don't have to immediately boot into Recovery either.
Click to expand...
Click to collapse
Also make sure you uncheck Auto Reboot and F Time Reset in Odin before flashing recovery.

bilgerryan said:
This statement is 100% false, stock recovery does not overwrite custom recovery ever unless you Odin stock. You don't have to immediately boot into Recovery either.
Click to expand...
Click to collapse
I think that I am either misunderstanding you, or you are misunderstanding me, or both.
The installation instructions for both TWRP and CWM (see below) say the you must boot into Recovery immediately after installing the custom recovery, otherwise if you allow it to do a normal boot the stock FW will overwrite the custom Recovery IMG with the stock Recovery IMG. I'm pretty sure that I have witnessed this behavior so I don't think they made it up.
The problem that I have with this phone is that, for whatever reason, it will not boot into Recovery but maybe one out of every ten tries.
Not meaning to be argumentative here; I'm sure that we're just miscommunicating. I appreciate your trying to help.
CWM Instructions:
NOTE: Be sure to reboot into recovery immediately after having installed the custom recovery. Otherwise the custom recovery will be overwritten and the device will reboot (appearing as though your custom recovery failed to install).
TWRP Instructions:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.

doraville said:
I think that I am either misunderstanding you, or you are misunderstanding me, or both.
The installation instructions for both TWRP and CWM (see below) say the you must boot into Recovery immediately after installing the custom recovery, otherwise if you allow it to do a normal boot the stock FW will overwrite the custom Recovery IMG with the stock Recovery IMG. I'm pretty sure that I have witnessed this behavior so I don't think they made it up.
The problem that I have with this phone is that, for whatever reason, it will not boot into Recovery but maybe one out of every ten tries.
Not meaning to be argumentative here; I'm sure that we're just miscommunicating. I appreciate your trying to help.
CWM Instructions:
NOTE: Be sure to reboot into recovery immediately after having installed the custom recovery. Otherwise the custom recovery will be overwritten and the device will reboot (appearing as though your custom recovery failed to install).
TWRP Instructions:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
So your problem would be solved by not allowing the device to boot. If it doesn't boot into Recovery, pull the battery and try again. Yeah I definitely was thinking about something else, once recovery is installed and you have booted into it it won't revert back to stock. That's the point I was getting to get across. Then once you do that either flash my 5 Way Reboot mod or download a Reboot app from the Play Store that will allow you to boot directly into Recovery and you shouldn't have any problems after that.

bilgerryan said:
So your problem would be solved by not allowing the device to boot. If it doesn't boot into Recovery, pull the battery and try again. Yeah I definitely was thinking about something else, once recovery is installed and you have booted into it it won't revert back to stock. That's the point I was getting to get across. Then once you do that either flash my 5 Way Reboot mod or download a Reboot app from the Play Store that will allow you to boot directly into Recovery and you shouldn't have any problems after that.
Click to expand...
Click to collapse
After thinking about it, with enough patience I should be able to get a custom recovery in there eventually. Then I should be able to use your mod or a Reboot app as you said. Good idea, thanks.
Of course, this still begs the question of why the phone refuses to boot into Recovery. As long as I'm able to work around it one way another I'd rather not go spelunking into the Recovery partition to try to fix it.

random reboot and unstable after rooting with cf-root

Hello,
I got my Galaxy s4 which was running fine (no reboot at all since i got it 6 months ago)....since i decided to root it, because i wanted to use titanium backup (to freeze the samsung update warning evertime you boot). I got Android Kitkat 4.4.2 and i dont want to update at all. Now i just want to restore back my stability, because now that i've installed the cf-root kernel, i got a lot of random reboots during one day! (a shame). I've just installed this: http://download.chainfire.eu/316/CF-Root/CF-Auto-Root/CF-Auto-Root-jflte-jfltexx-gti9505.zip
The root itself was a success, but supersu ask about uninstalling knox, i told it to uninstall it and it's reported success too. What is causing the random reboots?
I've tried to disable the root, but it's the same.
My Android version number is:
KOT49H.I9505XXUGNJ6 (operator Orange stock ROM)
What should i do?

I don't think it deleted all knox apps.

GDReaper said:
I don't think it deleted all knox apps.
Click to expand...
Click to collapse
Why i have random reboot? What make it reboot? I dont understand. I have the right kernel version or not? This kernel version should be stable right? How can i restore my intial kernel?

Did you try removing supersu using the built-in uninstaller?
You could also re-flash a stock 4.4.2 ROM over the existing ROM. Re-flashing does not remove your data but it is always a good idea to back up your data using kies/smartswitch before re-flashing.

audit13 said:
Did you try removing supersu using the built-in uninstaller?
You could also re-flash a stock 4.4.2 ROM over the existing ROM. Re-flashing does not remove your data but it is always a good idea to back up your data using kies/smartswitch before re-flashing.
Click to expand...
Click to collapse
Yes, i have remove SuperSu with the integrated feature to uninstall itself. This morning i got a unwanted reboot when i used the power button to wake up the phone screen. I noticed it's often when i power/wake the phone that the reboot takes place. I got 2 times another symptom: instead of rebooting, i cannot use the touch screen, the screen is active but i cannot move and i can solve it by doing anoter power/ wake up button. Then it's magically working. I've never had the problem since i rooted the phone.

Could it be a problem with the power button? Try booting into recovery mode and leave the phone for about 5 minutes. After 5 minutes, use the volume buttons to move up and down and then press the power button to selection an option but not the reboot option to see if it reboots when you touch the power button.

audit13 said:
Could it be a problem with the power button? Try booting into recovery mode and leave the phone for about 5 minutes. After 5 minutes, use the volume buttons to move up and down and then press the power button to selection an option but not the reboot option to see if it reboots when you touch the power button.
Click to expand...
Click to collapse
I tried what you said, it's working as expected. It has nothing to do with my power button, it's a software issue with my rooted kernel or the SuperSu that has broke something when it has disabled Knox maybe.

Since it isn't a hardware issue, I would just re-flash a stock ROM using Odin after backing up.

audit13 said:
Since it isn't a hardware issue, I would just re-flash a stock ROM using Odin after backing up.
Click to expand...
Click to collapse
Ok, i've installed clockworkmod recovery and i did a backup into an external SD card. It took something like 2 hours (7GB of backup files). But now i have another issue with the backup from CWM: I cannot find the content of my camera inside the CWM backup. Where is it located into the CWM backup files? I can see browse the data partition backup when i browse the file "data.ext4.tar.a", but i cannot see any folder /data/media?

I forgot to mention somehting:
After doing your test under the stock recovery, i just did "reboot" under the recovery menu. And then i got the fabulous infinite "starting apps" screen. I cannot solve it now. Seriously, what the hell?

I thought the camera content was stored in the DCIM folder.
Personally, I do not use CWM as it has not been updated for a long time and many developers have moved to TWRP.
Looks like it stuck at the starting apps screen because a factory wipe may be required before the ROM will boot.

audit13 said:
I thought the camera content was stored in the DCIM folder.
Personally, I do not use CWM as it has not been updated for a long time and many developers have moved to TWRP.
Looks like it stuck at the starting apps screen because a factory wipe may be required before the ROM will boot.
Click to expand...
Click to collapse
TWRP can save the /data/media subfolder? Because it seems like CWM is not able to for some reason (that i'd like to know).
About my issue:
1)Ok i've solved the stuck at starting apps problem after hours of fight. Finally i could start again after i have flashed the original ROM file. I'd like to know how it solve the issue because i didnt wipe anything.
2)I still got random reboot and no touch screen sometimes. So it seems like the mess that was done by CF-ROOT kernel (maybe the Knox uninstall?) is still there, even after a ROM reflash. Oh MY GOD.
Is there an easy to way get back all my data after doing a factory reset? Because i think i'll have to do that because of that sucky CF-ROOT.

If you flash TWRP, you can boot into TWRP, mount the data partition, and copy files to the computer or insert a microSD card into the phone and copy it there.
Flashing a stock ROM flashes all partitions except the data partition and leaves all data intact. You could try wiping the only the cache from stock recovery to see if this resolves the reboot issue.
Could the reboot issue becaused by an app that was installed?
I have used CF autoroot a number of times and have never had it affect the touch or cause reboots.

audit13 said:
If you flash TWRP, you can boot into TWRP, mount the data partition, and copy files to the computer or insert a microSD card into the phone and copy it there.
Flashing a stock ROM flashes all partitions except the data partition and leaves all data intact. You could try wiping the only the cache from stock recovery to see if this resolves the reboot issue.
Could the reboot issue becaused by an app that was installed?
I have used CF autoroot a number of times and have never had it affect the touch or cause reboots.
Click to expand...
Click to collapse
I've tried 10x to wipe the cache.
How can an application could cause a reboot? How can i know what is the cause of the reboot?

What ROM was on the phone when you flashed cfautoroot? I assume it was a stock ROM and you flashed the correct version of autoroot.
Wiping cache works or doesn't work? Did TWRP install?

I flashed this kernel: http://download.chainfire.eu/316/CF-Root/CF-Auto-Root/CF-Auto-Root-jflte-jfltexx-gti9505.zip
And my ROM is my operator ROM, the last 4.4.2:
{
"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"
}
I didnt install TWRP. And wipe cache works but it doesnt solve the random reboot issue.
I just want to know where i can find logs of the reboots? My phone is less stable than Windows Millenium now!

Hmm, looks like the file you flashed was for 5.01.
https://autoroot.chainfire.eu
I normally root phones with supersu and twrp.

audit13 said:
Hmm, looks like the file you flashed was for 5.01.
https://autoroot.chainfire.eu
I normally root phones with supersu and twrp.
Click to expand...
Click to collapse
I just follow this:
http://www.ibtimes.com.au/how-root-...l-android-442-kitkat-xxugng4-firmware-1349050
You say that they put the wrong kernel lol? Are you serious?
Anyways, as i mentioned, i flashed my ROM again. So i dont have any root and modified kernel.
Still i got random reboot.

I looked at chainfire's website and I only see 5.01, not 4.4.2 so maybe the file is only for 5.01 but I am not 100% sure.
If the file is for 5.01 and it flashed the 5.01 kernel, it may have messed up some of the apps and probably needs a factory wipe using stock recovery to fully boot the 4.4.2 rom.

audit13 said:
I looked at chainfire's website and I only see 5.01, not 4.4.2 so maybe the file is only for 5.01 but I am not 100% sure.
If the file is for 5.01 and it flashed the 5.01 kernel, it may have messed up some of the apps and probably needs a factory wipe using stock recovery to fully boot the 4.4.2 rom.
Click to expand...
Click to collapse
You say that it's the wrong kernel file, but it's not. It's the file that you will find on every tutorial for the CF-ROOT on 4.4.2. If it would be a wrong kernel, i couldnt even start the phone, it would boot at all.
That said, what's the best way to migrate data to save them before doing a wipe data/factory reset?

Stuck on Bootloader

I feel like a super super noob here in this particular learning curve, my phone is a Samsung S5 G900T1UVU1ANE7.
It's currently stuck on the Samsung Boot screen thing and won't go any further even fully charged.
For this particular phone I want it streamlined just with no bloatware or the such tweak and optimized it's a great phone 16 MP and I wanna use it I just need to get it back working and would appreciate any help.
I have no problems answering any questions to what I've done so far or will do.
:cyclops:

Have you tried a factory reset (delete all data from phone) while in recovery (holding home + power + vol up while screen off)?
If that doesn't work, have you considered flashing the latest stock firmware via ODIN?

Saber said:
Have you tried a factory reset (delete all data from phone) while in recovery (holding home + power + vol up while screen off)?
If that doesn't work, have you considered flashing the latest stock firmware via ODIN?
Click to expand...
Click to collapse
Yes to both but not opposed to trying again if need be.

I would suggest first doing a odin flash with a fully stock rom just to get the phone back up and working. After that you might look into another rom, something de-bloated and maybe rooted. To do that you will likely need to flach twrp from download mode ( remember uncheck auto reboot in odin )then boot into recovery and move over the new rom / zip, wipe, then install and reboot ( dont forget gapps if its not in the rom ).
For whatever reason for me it seems like every time i install a new rom i need to first go back to factory stock rom first on my sprint s5.

Saber said:
Have you tried a factory reset (delete all data from phone) while in recovery (holding home + power + vol up while screen off)?
If that doesn't work, have you considered flashing the latest stock firmware via ODIN?
Click to expand...
Click to collapse
Just tried the above after I got TWRP on and when trying the factory reset it says E:Unable to mount ' /system'

Wdwaring said:
Just tried the above after I got TWRP on and when trying the factory reset it says E:Unable to mount ' /system'
Click to expand...
Click to collapse
Seems like the system partition got corrupted. Have you ensured that you have the latest TWRP version (3.1.0)? What happens when you try to factory reset using stock recovery (3e recovery)?

Saber said:
Seems like the system partition got corrupted. Have you ensured that you have the latest TWRP version (3.1.0)? What happens when you try to factory reset using stock recovery (3e recovery)?
Click to expand...
Click to collapse
Ok I have TWRP 3.1.0 on it now I try to install Reserection Remix rom and this is the error i get from TWRP
{
"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"
}

The system partition is borked. How did you achieve this feat? The only way to get it back up and running is by replacing the eMMC. No matter how many times you format it, no matter how many times you pray to it to work, it's half dead. And don't even dare think about re-partitioning because you'll probably end up damaging it even more than it is now. And hello there @Saber

Wdwaring said:
I feel like a super super noob here in this particular learning curve, my phone is a Samsung S5 G900T1UVU1ANE7.
It's currently stuck on the Samsung Boot screen thing and won't go any further even fully charged.
For this particular phone I want it streamlined just with no bloatware or the such tweak and optimized it's a great phone 16 MP and I wanna use it I just need to get it back working and would appreciate any help.
I have no problems answering any questions to what I've done so far or will do.
:cyclops:
Click to expand...
Click to collapse
what happens after flashing stock via odin. is it stuck on boot, it can take upto 15min sometimes to boot after flashing stock.
ts rom install:
Backup Both Sdcards To Pc
Remove External And Format Internal Fat32
Copy Fw To Internal & Check MD5
Put Phone In Download Mode.
Start ODINv3.10 And Uncheck Auto Reboot
Flash Stock 6.0.1 MM Fw For Your Phone Model Via Odin AP Button
When Install Is Complete Remove Then Reinstall Battery.
Boot To Stock Recovery
Then Wipe Data, Caches And Factory Reset Within "Stock Recovery" To Start Fresh.
u can try this custom stock superlite rom i made for some of the #7 twrp errors, takes only a few minutes(6min max) to install and boot and a fast way to see if phone can boot, need to be on 6.0.1 bl and mdm, tested w/Twrp 3.1.0-0. rom thread in my sig
https://www.androidfilehost.com/?fid=817550096634756035

vincom said:
what happens after flashing stock via odin. is it stuck on boot, it can take upto 15min sometimes to boot after flashing stock.
ts rom install:
Check MD5
Backup Both Sdcards To Pc
Remove External And Format Internal Fat32
Copy Fw To Internal
Put Phone In Download Mode.
Start ODINv3.10 And Uncheck Auto Reboot
Flash Stock 6.0.1 MM Fw For Your Phone Model Via Odin AP Button
When Install Is Complete Remove Then Reinstall Battery.
Boot To Stock Recovery
Then Wipe Data, Caches And Factory Reset Within "Stock Recovery" To Start Fresh.
u can try this custom stock superlite rom i made for some of the #7 twrp errors, takes only a few minutes(6min max) to install and boot and a fast way to see if phone can boot, need to be on 6.0.1 bl and mdm, tested w/Twrp 3.1.0-0. rom thread in my sig
https://www.androidfilehost.com/?fid=817550096634756035
Click to expand...
Click to collapse
NOTE: There needs to be a text chat option on the page so people could possibly chat live with ppl and get walked through the process some people learn better that way. Tryn your rom here,
Actually I need to be walked through step by step, you guys already know this stuff like the back of your hand, so far I have TWRP 3.1.0 on the phone thats it, whats the next step.
Ok I went ahead and grabbed the file you recommended and installed it, it rebooted twice now and is on the Samsung word blinking might take the 15 mins referred to as it takes sometimes, we'll see what happens.
Ok, looks like it may have worked will keep everyone informed after a bit

BOOTLOOP
im not sure what i did wrong but it went like this
1 recovery mode
2. wipe data/factory reset
3. wipe cache partition
after this phone stuck on logo at start up
4. hardware keys to enter recovrey mode
5. boot to bootloader
now stuck in download mode
6. back to rec mode, repeat fac reset
now back stuck to logo at start up
pls anybody help me