Database Users

[Q] i9505 (jgedlte) fails to boot system after installing ROM

I'm trying to install CM via TWRP.
First I had to unlock the bootloader, so I did, and since then I could not boot to my stock Android (although, correct me if I'm wrong, unlocking the bootloader should NOT delete the OS), it just sent me to recovery.
So I went along, flashed TWRP and got cm 10.2.1 for jfltexx. At first it didn't install well, because my data partition was not formatted correctly. So I formatted it, now TWRP sees it correctly and is able to mount it, enable MTP and everything. When I try to install now, everything seems fine and TWRP's log shows "Updating partition details..." and gives me the "Successful" message, offering to wipe cache/reboot system. (I did wipe cache and dalvik cache before, of course).
If I choose "Reboot System", it just boots back to recovery. The same happens if I power it off and boot normally, even if I pull out the battery and retry that way.
What can I do about it?

Jon-G said:
I'm trying to install CM via TWRP.
First I had to unlock the bootloader, so I did, and since then I could not boot to my stock Android (although, correct me if I'm wrong, unlocking the bootloader should NOT delete the OS), it just sent me to recovery.
So I went along, flashed TWRP and got cm 10.2.1 for jfltexx. At first it didn't install well, because my data partition was not formatted correctly. So I formatted it, now TWRP sees it correctly and is able to mount it, enable MTP and everything. When I try to install now, everything seems fine and TWRP's log shows "Updating partition details..." and gives me the "Successful" message, offering to wipe cache/reboot system. (I did wipe cache and dalvik cache before, of course).
If I choose "Reboot System", it just boots back to recovery. The same happens if I power it off and boot normally, even if I pull out the battery and retry that way.
What can I do about it?
Click to expand...
Click to collapse
First I'd try a newer version of CM. That's an old one. It might not work and play well with a newer version of TWRP. Plus the newer version is a little more polished.
Second, if you must use that CM version, redownload it. You wouldn't be the first person who got a corrupted install file that causes screwball issues like this.
Third, if all else fails use Odin to reset back to stock and start over. Something might have gotten all borked up when you first modified the device that isn't letting the install work. A full restore to stock should correct that.

Skipjacks said:
First I'd try a newer version of CM. That's an old one. It might not work and play well with a newer version of TWRP. Plus the newer version is a little more polished.
Second, if you must use that CM version, redownload it. You wouldn't be the first person who got a corrupted install file that causes screwball issues like this.
Third, if all else fails use Odin to reset back to stock and start over. Something might have gotten all borked up when you first modified the device that isn't letting the install work. A full restore to stock should correct that.
Click to expand...
Click to collapse
Thanks for the reply.
Regarding the versions of CM and TWRP, I deliberately picked these versions due to their high download count (A sign I can trust these builds, being not too buggy). I'll try a newer CM version and another TWRP version if that didn't help.
I will also verify the MD5 for the downloaded file this time.
If I restore to stock via Odin, wouldn't that override the recovery? I've looked on some tutorial on how it's done, and it seems like the stock recovery is flashed, then used to restore the stock. Is there any way to use Odin to flash other ROMs?
EDIT: Nope cm-11-20140210 also failed, and I did verify the MD5 now. My TWRP is the newest available for jgedlte in the download page (2.8.0.1).
I did manage getting into some sort of a boot loop (The initial "Reboot System" brought back the recovery, but after a full power off and a reboot, the screen remains black and the phone vibrates every 4 seconds or so.)
EDIT 2: I tried to flash the stock back, following this tutorial. I downloaded the Open European version, flashed the AP but it failed during the write of system.img.ext4, saying that the image is invalid. I tried again with the PIT file, but it failed too (secure check fail while repartitioning...).

i9505 doens´t boot after flashing stock firmware

Hello
I was trying to update my friend´s i9505 to the latest AntaresOne CM12 build, but forgot to flash gapps, and since i coulnd´t for some reason enter CWM (the phone just reboots), i had to flash stock firmware over again so i could start over.
But now the phone isn´t booting even on stock firmware. That usually did the trick.
The wierd thing is that Phils Touch Recovery was working before, but ever since i used Triangle Away to reset binary counter, the recovery won´t boot up anymore.
The only way that i could get into Phils Recovery was to install the TWRP recovery installer, and throught the app i would tell it to flash, and it would reboot into Phils Recovery
Now since system isn´t booting, i can´t install and use the TWRP installer to reboot into recovery mode for me.
Tried to flash stock recovery, the same thing happens: the phone just black screens, vibrates and reboots.
Any ideas of why this might be happening?

Go to stock recovery if you can and wipe data/factory reset. Install stock ROM then.

@guguts
As clearly wrote in 1st post of my thread, you need to do "format /system" before installing ROM's builds starting from 26/11 one and latest ones, including 3/12 and the ones that will come in the future.
I strongly suggest you to take a look again at installation instructions, but this time carefully.
If you need anything else, write directly in its Q&A thread (you can find it in this section) where surely you can be helped more and better
Inviato dal mio GT-I9505

Flash a custom recovery with Odin. Uncheck auto-reboot before flashing.
Then boot into the recovery using the botton combo. Keep holding it as long as it takes to enter recovery.

Hey guys, i managed to work it out.
It was probably a loose vol up or home button, because i didn´t do anything but a few moments later i tried to enter stock recovery and it went fine.
The issue was not with the custom rom (which by the way is great, my friend says its running smooth).
The issue happened because i forgot to do i data wipe after installing the rom and prior to installing the stock rom.
So the stock ROM was trying to load using lollipop data and cache, and thats why it got stuck in the samsung logo.
As soon as i managed to enter stock recovery again, and made a data wipe, the stock room booted fine.
So i tried again, but this time didn´t forget to flash gapps, and even better, now Phils Recovery is booting up normally (go figure...)
So i formated /system and /data, flashed AntaresOne ROM and gapps, and everything went fine.
Just posting here in case anyone in the future goes througyht the same hassle.
Thank you so much for your work Antares.
Its people like you, quarx and pawtip (and many others top developers) that makes this community great.

[Q] ODIN fails while installing TWRP, stuck at boot

I was trying to upgrade from CM11 to CM12, which went smooth except for GAPPS closing constantly. I read online that this was caused by an old version of the recovery, so I tried to update TWRP to 2.8.4.0. I first tried using the TWRP app from the Play Store (after recovering my Nandroid backup), which locked the phone where it would only try booting into recovery, but couldn't get there. Holding the power button to turn it off would result in a reboot right back into recovery, which of course never went anywhere. Now I am trying to re-install TWRP using ODIN but It fails every time [Complete(Write) operation failed.] I have an early S4 from AT&T and it has never had an official update. I can't remember which firmware it is using, but it is the original so I shouldn't have any problems there. Can anybody help me get this thing up and running with either TWRP or CWM and CM12 please?!
Update: I have been able to get the phone to boot by first booting into Download mode, then hitting the Volume Down button to cancel. This has twice booted it back into the OS. Still no recovery though.

Solved
I was able to install TWRP 2.8.4.0 from the app after getting the device to boot. It worked correctly this time and all appears to be well. Odd that ODIN didn't work though.

[Q] Attempted to install TWR & SuperSU - T330 won't boot past Samsung Logo

I decided to finally root my Wifi only Galaxy Tab 4, 16 gig. To my understanding it is the T330. It had the latest OTA - 5.1.1 I believe?
After installing TWRP and trying to flash SuperSU it won't boot past the Samsung logo.
I did the following:
Prior to today I have had the USB drivers installed
Downloaded and extracted ODIN 3.0.9
Downloaded TWRP 2.8.7 Tar file for the T3xx series
Downloaded SuperSU zip file for version 2.46
I opened up ODIN, unchecked the "Auto Reboot" box (after seeing elsewhere that it was needed when flashing the recovery), checked the box for "AP" and selected the .tar file for TWRP. I clicked start, everything went correctly, I removed the USB cable and manually restarted the device by holding the power button. Once it was off I then held the power button, volume up, and home button to boot into recovery, and to my excitement I was greeted with TWRP. So far it looked like it was going according to plan. A screen came up saying that the system was currently read only, and it was giving me the choice to allow the recovery to change it. I swiped to allow it to change it so the system partitions were not read only. I went to the install option, and selected the SuperSU zip file. Installed it, it said that it installed correctly. I went back to the main menu and rebooted the device. That's when things did NOT go according to plan. It played the nice little boot sound, the animated Samsung logo came up, and I waited. I waited some more. I continued to wait. After 10 minutes of the Samsung animation repeating I assumed that trouble was afoot and turned the tablet off and attempted to get back into recovery, which it did. I then turned it off and checked to see if I could still get into Download Mode: and it can and the PC can see it as connected when I load up ODIN.
So I have the tablet soft bricked. My goal was to have it rooted with custom recovery to install roms.
If that's not possible, I assume my best bet would be to use ODIN to push the Samsung files over and flash it back to factory that way, undoing what I have done?
Any advice would be greatly appreciated. I tried to be as detailed as possible to assist anyone who may be willing to help.

SebringTech said:
I decided to finally root my Wifi only Galaxy Tab 4, 16 gig. To my understanding it is the T330. It had the latest OTA - 5.1.1 I believe?
After installing TWRP and trying to flash SuperSU it won't boot past the Samsung logo.
I did the following:
Prior to today I have had the USB drivers installed
Downloaded and extracted ODIN 3.0.9
Downloaded TWRP 2.8.7 Tar file for the T3xx series
Downloaded SuperSU zip file for version 2.46
I opened up ODIN, unchecked the "Auto Reboot" box (after seeing elsewhere that it was needed when flashing the recovery), checked the box for "AP" and selected the .tar file for TWRP. I clicked start, everything went correctly, I removed the USB cable and manually restarted the device by holding the power button. Once it was off I then held the power button, volume up, and home button to boot into recovery, and to my excitement I was greeted with TWRP. So far it looked like it was going according to plan. A screen came up saying that the system was currently read only, and it was giving me the choice to allow the recovery to change it. I swiped to allow it to change it so the system partitions were not read only. I went to the install option, and selected the SuperSU zip file. Installed it, it said that it installed correctly. I went back to the main menu and rebooted the device. That's when things did NOT go according to plan. It played the nice little boot sound, the animated Samsung logo came up, and I waited. I waited some more. I continued to wait. After 10 minutes of the Samsung animation repeating I assumed that trouble was afoot and turned the tablet off and attempted to get back into recovery, which it did. I then turned it off and checked to see if I could still get into Download Mode: and it can and the PC can see it as connected when I load up ODIN.
So I have the tablet soft bricked. My goal was to have it rooted with custom recovery to install roms.
If that's not possible, I assume my best bet would be to use ODIN to push the Samsung files over and flash it back to factory that way, undoing what I have done?
Any advice would be greatly appreciated. I tried to be as detailed as possible to assist anyone who may be willing to help.
Click to expand...
Click to collapse
Have you tried wiping dalvik and cache through recovery? If that doesn't help maybe do a factory reset before restoring the factory image?
Sent from my SM-T330 using Tapatalk
Edit: I think this might be what you need
http://forum.xda-developers.com/showthread.php?t=3176668

I tried to wipe cache and dalvik - still gets stuck at the Samsung logo... Tried to do a factory reset from TWRP and after rebooting from recovery it continues to get stuck. I'll try flashing the kernel but I don't understand why that would have gotten messed with from flashing the recovery and installing the SuperSU part.

Okay I take back my statement... flashed the kernel, after flashing did a cache and dalvik wipe and boom... it boots!!! You are officially my hero! Thank you!

SebringTech said:
Okay I take back my statement... flashed the kernel, after flashing did a cache and dalvik wipe and boom... it boots!!! You are officially my hero! Thank you!
Click to expand...
Click to collapse
You're very welcome. Good luck.
Sent from my SM-T330 using Tapatalk

Custoom ROM installation failed (stuck on pre-boot screen)

So I've installed TWRP onto my S8 and have wiped it completely, though I did have to change and then change back the file formats so that TWRP would register them correctly
I downloaded renovate ice 1.1, copied it onto my sd card and then flashed it everything installed well
When I then reboot it doesnt get past the first screen as in showing (not sure if it freezes at this point but have left it for 2 hours so Im guessing so)
Samsung Galaxy S8 POWERED BY android
Then the only thing I can do is get the phone back into recovery mode (then when I go to reboot it says there is no OS)
Before I installed the custom ROM I had an error message stating that the integrity verification had failed, I pressed on believing that this would be fixed once I had installed renovate
I know that my phone is a exynos variant, is there any way to check exactly what variant withing TWRP
The download mode is still working

Extra Information
and also when I go into TWRP it asks me about if it should be only system read each time it starts up
it also prompts for me to install the app when I try to reboot through TWRP though I believe that is normal

thegasovi said:
So I've installed TWRP onto my S8 and have wiped it completely, though I did have to change and then change back the file formats so that TWRP would register them correctly
I downloaded renovate ice 1.1, copied it onto my sd card and then flashed it everything installed well
When I then reboot it doesnt get past the first screen as in showing (not sure if it freezes at this point but have left it for 2 hours so Im guessing so)
Samsung Galaxy S8 POWERED BY android
Then the only thing I can do is get the phone back into recovery mode (then when I go to reboot it says there is no OS)
Before I installed the custom ROM I had an error message stating that the integrity verification had failed, I pressed on believing that this would be fixed once I had installed renovate
I know that my phone is a exynos variant, is there any way to check exactly what variant withing TWRP
The download mode is still working
Click to expand...
Click to collapse
should I try to reinstall TWRP and see what happens

thegasovi said:
should I try to reinstall TWRP and see what happens
Click to expand...
Click to collapse
I've tried to install the Batman ROM but to the same avail,
still prompting me to install the TWRP official app (but not always)
am going to try reinstalling twrp using odin
could it have anything to do with knox values changing (need to research)

installed batman rom after using Odin to BL some new firmware(think that's what its called) onto the device
now am stuck on the next boot loading screen
will wait for some time to see if its my phone
-so 1 problem was due to the previous stuff on the device hopefully this means that the integrity verification thing is fixed (not sure how to check
-still havent re-'downloaded' a new twrp via odin, may try next
-could also try reinstalling batman as it was installed before the firmware, may be worth it
-could try to use default rom (need to find download page)
not sure about next step

reinstalled renovate and booted up and got back to the verification failed screen, may have something to do with me selecting knox when I installed it
-niw will try to solve integrity verification problem as when I try to reset it wont work w/ twrp

Maybe too many little things that are causing issues, maybe rather just use Samsung Switch and do a recovery and it will reinstall as per stock, then try the rooting, custom ROM thing from scratch. I know I battled with mine, got TWRP installed but coult get passed samsung boot screen. So i did used Samsung Switch recovery function and got phone back to stock, now I just use package disablers to kill stuff and all is well.

at first, why did you choose renovate 1.1 when 2.2 is availiable?
i would start from scratch again...
flash stock rom via odin. boot and test device. there should be no problem, after this, flash twrp again and put latest renovate rom on memory or external usb device.
with aroma installation you can choose to full wipe your phone. this should make no problems.

Tim Niklas said:
at first, why did you choose renovate 1.1 when 2.2 is availiable?
i would start from scratch again...
flash stock rom via odin. boot and test device. there should be no problem, after this, flash twrp again and put latest renovate rom on memory or external usb device.
with aroma installation you can choose to full wipe your phone. this should make no problems.
Click to expand...
Click to collapse
looking back on it I guess I just didnt realise that that version was available
could you give me a link to where I can download the stock rom from, that would be great

Jostian said:
Maybe too many little things that are causing issues, maybe rather just use Samsung Switch and do a recovery and it will reinstall as per stock, then try the rooting, custom ROM thing from scratch. I know I battled with mine, got TWRP installed but coult get passed samsung boot screen. So i did used Samsung Switch recovery function and got phone back to stock, now I just use package disablers to kill stuff and all is well.
Click to expand...
Click to collapse
I tried to open samsung switch earlier but it believed that my phone was no longer supported and I guessed that this was due to the rooting, what mode where you in to be able to connect to samsung switch

not sure now but atm I cant get into TWRP anymore

Put phone into download mode, then use recovery option on switch.

thegasovi said:
looking back on it I guess I just didnt realise that that version was available
could you give me a link to where I can download the stock rom from, that would be great
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s8/how-to/official-stock-firmware-update-odin-t3598172
take a look here,
there is described, how you can download stock rom with the tool samfirm.
keep this rom safe you may need it once or twice again.
---------- Post added at 11:05 AM ---------- Previous post was at 11:04 AM ----------
thegasovi said:
not sure now but atm I cant get into TWRP anymore
Click to expand...
Click to collapse
and again...
as long as you are abel to go into download mode, everything is fine.
flash stock again -> twrp -> custom rom with full wipe in aroma installer

reverted back to stock os using odin
checked that all is well and there was no lasting damage (knox was still working fine)
reinstalled twrp, same problem happened again with twrp not recognising the internal storage so had to reset the file format
flashed the batman rom, now am back at the second boot screen and cannot get past

thegasovi said:
reverted back to stock os using odin
checked that all is well and there was no lasting damage (knox was still working fine)
reinstalled twrp, same problem happened again with twrp not recognising the internal storage so had to reset the file format
flashed the batman rom, now am back at the second boot screen and cannot get past
Click to expand...
Click to collapse
with internal storage you mean data partition?
sorry, i forgot. thats a common known issue with twrp , wipe data partition in twrp menu, after that you are able to install custom roms