Database Users

[Q] Can't flash recovery zip

Hi,
I'm at my wits end. I had SlimRom installed for a week and all was fine, but I was curious about what new ROMs were out there so I backed up my phone using ROM Manager and did all the usual stuff to get a new ROM. I installed Gummy, but didn't like it; I installed one other ROM that I can't remember its name, but also didn't like that. I realized my comfy home of SlimRom was where I wanted to be, so I tried to flash the backup.zip that I had created but it kept saying installation aborted (Status 0).
After hours of countless attempts and just weird behaviour (sometimes boot loops, sometimes not booting into recovery, etc.) I finally got my phone back to stock.
I downloaded the latest SlimRom file 3 times to make sure it wasn't a corrupt zip (twice from my PC and once from my phone directly). Both the zip directly from Slim as well as the backup.zip that I made with ROM Manager give me the same installation aborted. The other error it gives is "E: Error in /data/media/0/slim....zip". I'm wondering if somehow my partition is screwed up. I tried using Odin's repartition, which just erased my recovery partition, but I got that back thankfully! When I wipe data/factory reset it says wipe complete (and the ROM does reset to factory) but it also says "E:unknown volume '/sdcard/.android_secure' "...I'm wondering if that relates to why the backup.zip file won't read properly. Maybe the partition got screwed up somehow?
I can flash a SU zip so it's not a flashing problem, per se. And thankfully Odin always works!
I think I may need the stock PIT file for the Telus S4 l337m

UPDATE:
I think I found the proper pit (SGS-I337_16GB) but my phone says "secure check fail: pit".

[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...).

HELP! Phone stuck in boot cycle, cannot flash rom

Hi everyone! Surfed the forums in the past for some minor help but never needed to register till now. I've tried everything and can't get my phone to boot.
So last night while camping my phone started boot cycling out of nowhere. I let it try a few times and then removed the battery and went to sleep. This morning I woke up and tried a few more times, replaced the battery with a non-stock double-capacity one I have, and still cycled. Sometimes it restarts on the Galaxy Note 4 logo, and sometimes on the Sprint logo. It will do this indefinitely. At one point It finally booted and said it was updating apps (like from an Android update, not the regular app updates.) Before I could do anything else with it though, the battery wiggled loose and it started power cycling again. Because of this one boot I think the root cause is related to an Android update that decided to run without my permission.
So I gave up and drove hoe from camping. Tonight I had tried everything I could find from factory reset to the toolkit to Odin and nothing has had any effect. The toolkit didn't see the device, and Odin failed to flash. Can anyone help me? I can boot to recovery and I can get into download mode, but nothing seems to work. The phone isn't hard bricked, but everything I can find on soft brick solutions hasn't worked. Thanks in advance!
~Evan

Oh also, when I boot into recovery mode it says "installing system update" with the android open chest logo, and then goes to a dead android and says "no command" before getting into the recovery mode menu.

ekuest said:
Oh also, when I boot into recovery mode it says "installing system update" with the android open chest logo, and then goes to a dead android and says "no command" before getting into the recovery mode menu.
Click to expand...
Click to collapse
If you able to go download mode then flash twrp recovery in odin and go to twrp recovery for your specific model and do clean wipe system then flash any rom for your model.then wait 10 to 15 minuts until phone boot.

Trex888 said:
If you able to go download mode then flash twrp recovery in odin and go to twrp recovery for your specific model and do clean wipe system then flash any rom for your model.then wait 10 to 15 minuts until phone boot.
Click to expand...
Click to collapse
Ok thanks that worked! I got into TWRP by setting Odin to not reboot. If I let it reboot then it just restarted after the TWRP flash and kept power cycling like before. If I uncheck auto reboot in Odin then after the flash I can pull the battery (can't figure out any other way to turn the phone off) and then when I restart in recovery mode it goes into TWRP. From there I tried a factory reset (wipe data, cache, and dalvik) and that didnt fix the power cycling. Do I have to flash TWRP and then immediately flash a rom right after? Or should I try an advance wipe in TWR, or maybe "repair or change file system" from the advanced wipe menu?

Bump? I still can't boot my phone. Got into TWRP but no idea what to do from there. I can't flash any rom successfully in Odin and I can't get the phone to boot. Now it just hangs on the "Samsung Galaxy Note 4" splash screen, doesnt even go to the "Samsung" screen or the "Sprint" screen like it used to.

Trex888 said:
If you able to go download mode then flash twrp recovery in odin and go to twrp recovery for your specific model and do clean wipe system then flash any rom for your model.then wait 10 to 15 minuts until phone boot.
Click to expand...
Click to collapse
how do you do the "then flash any rom" part? i have no idea how to do that since Odin doesn't seem to work.

ekuest said:
how do you do the "then flash any rom" part? i have no idea how to do that since Odin doesn't seem to work.
Click to expand...
Click to collapse
1,Flash twrp recovery in odin
2,press volume up+home+power button and boot into twrp
3,in twrp go to wipe/advance wipe and wipe system/cache/data/dalvik cache
4,Flash any custom rom for your model from twrp recovery
If you allready have twrp installed then skip 1 and download any rom like cm12 and gapps
Then flash from twrp

Trex888 said:
1,Flash twrp recovery in odin
2,press volume up+home+power button and boot into twrp
3,in twrp go to wipe/advance wipe and wipe system/cache/data/dalvik cache
4,Flash any custom rom for your model from twrp recovery
If you allready have twrp installed then skip 1 and download any rom like cm12 and gapps
Then flash from twrp
Click to expand...
Click to collapse
Do I just go to install in TWRP and then select the zip file on my microSD card? I tried that with N910PVPU3BOF5_N910PSPT3BOF5_SPR.zip and if says "Could not find 'META-INF/com/google/android/update-binary' in the zip file. Error installing zip file '/external_sd/N910PVPU3BOF5_N910PSPT3BOF5_SPR.zip'" Then I tried with a CM called cm-12.1-20161016-NIGHTLY-trltespr.zip and it seemed to work, and showed a little blue android face but then it still wouldnt boot. Now when I try to start the phone it says "KERNEL IS NOT SEANDROID ENFORCING Set Warranty Bit: Kernel" in tiny text on the top right of the Galaxy Note 4 splash screen, then boots to the blue android face and then powers off after about 2 seconds. After that, I cant even recovery boot the phone until I remove and reinstall the battery. Then the same thing happens, boot to blue android face and then shut down. I'll try some more android zips I found but I think there is a deeper problem with the phone here.

ekuest said:
Do I just go to install in TWRP and then select the zip file on my microSD card? I tried that with N910PVPU3BOF5_N910PSPT3BOF5_SPR.zip and if says "Could not find 'META-INF/com/google/android/update-binary' in the zip file. Error installing zip file '/external_sd/N910PVPU3BOF5_N910PSPT3BOF5_SPR.zip'" Then I tried with a CM called cm-12.1-20161016-NIGHTLY-trltespr.zip and it seemed to work, and showed a little blue android face but then it still wouldnt boot. Now when I try to start the phone it says "KERNEL IS NOT SEANDROID ENFORCING Set Warranty Bit: Kernel" in tiny text on the top right of the Galaxy Note 4 splash screen, then boots to the blue android face and then powers off after about 2 seconds. After that, I cant even recovery boot the phone until I remove and reinstall the battery. Then the same thing happens, boot to blue android face and then shut down. I'll try some more android zips I found but I think there is a deeper problem with the phone here.
Click to expand...
Click to collapse
Which android version you ware running last time before this issues start happning ? 5.1.1 or 6.0.1 ?
And i think you are trying to flash firmware file from twrp thats not possible you will require a custom rom.
If you are on 5.1.1 then try any lojjipop n910p based roms like cm 12
If you are on 6.0.1 then try n910p marshmallow based rom like cm13

Trex888 said:
Which android version you ware running last time before this issues start happning ? 5.1.1 or 6.0.1 ?
And i think you are trying to flash firmware file from twrp thats not possible you will require a custom rom.
If you are on 5.1.1 then try any lojjipop n910p based roms like cm 12
If you are on 6.0.1 then try n910p marshmallow based rom like cm13
Click to expand...
Click to collapse
I always run the updates so I'm pretty sure I was on 6.0.1. I tried again with CM13 with and without GApps and same thing always happens. No matter what I do, the phone always hangs and shuts off when it gets to the CM splash screen. I will upload a video soon. Do you know why the phone says that SEANDROID thing?
I am using CM13 from here: https://www.androidfilehost.com/?w=files&flid=44727
I am using GApps from here: http://opengapps.org/?download=true&arch=arm&api=6.0&variant=pico

ekuest said:
I always run the updates so I'm pretty sure I was on 6.0.1. I tried again with CM13 with and without GApps and same thing always happens. No matter what I do, the phone always hangs and shuts off when it gets to the CM splash screen. I will upload a video soon. Do you know why the phone says that SEANDROID thing?
I am using CM13 from here: https://www.androidfilehost.com/?w=files&flid=44727
I am using GApps from here: http://opengapps.org/?download=true&arch=arm&api=6.0&variant=pico
Click to expand...
Click to collapse
Seandroid thing is normal if you are running custom rom. Cuz any custom comes with root and custom kernel so nothing to worry.
Did you tried another battery?
And how long did you wait to phone boot after flashing cm13 ?
Go to sprint note 4 xda forum and try different roms and be patient and wait atleast 20min to phone boot
You cannot flash cm13 without gapps and make sure gapps is for 6.0.1 marshmallow.
Once your phone boot normal go to download mode and flash 6.0.1 firmware in odin and after finish flash immediately go to stock recovery and do factory reset your phone will be normal.
Make sure your battery is not damaged maybe it is causing shut off. Issue.

Well since I can't flash CM13 with TWRP and I can't flash a stock rom with Odin, what other options do I have? Is there any way to get a bcakup file that someone else has made on their Note 4 in TWRP and try restoring from that? I've also read about ADB sideloading and another recovery called CWM or something and I don't know if those will be any different or just more failed flashes. I think the problem is deeper in the phone since it wouldn't boot with the stock rom and now it won't boot with CM13.
EDIT: Just saw your last post. I have 2 batteries, one samsung stock and one aftermarket TechOrbits double capacity. The phone does the same thing with either one so I ruled out the battery a while ago. Think there's any chance theyre both bad and I should order a new one? I don't really want to invest more money into a dead phone. I don't think I waited that long after installing CM13. I'll try it again and give it a half hour. I doubt that will change anything though.
EDIT2: Also when I go to download mode (says "ODIN MODE <HIGH SPEED>" at the top) it has some red text at the bottom I think might mean something. Does this mean anything to you or is it typical?
UDC START
SW REV CHECK FAIL : [aboot]Fused 4 > Binary 1
[1]eMMC write fail: ABOOT

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

Note 4 N910VVRU2BOG5 stuck on android system recovery 3e

hi yesterday i was trying to install a custom rom but because im new in this kind of stuff i did something wrong so all in detail:
first i rooted my phone and downloaded rom of resurrection (nougat) and downloaded the opengapp
Then downloaded the official twrp from play store and that's where i did wrong
i opened the twrp and even though i didn't really know how to use it i tried to do stuff on my own without any idea i dont really remember what i did but i clicked on twrp flash and chose my device and downloaded both .tar and .img files both downloaded successfuly
after installing files i clicked on reboot from menu and there was boot system and boot recovery i dont remember which one i clicked exactly but probably the system one so the phone turned off
and the Android system recovery 3e came up where at the bottom it says dm-veriety vertification failed and i tried to reboot system now and tried all the stuff on this screenapplying update from ADB and external storage is disabled and from cache is deprecated
so i found some stuff online about odin and how to install with it tried but it gave error complete(write) failed
i didn't open the USB debugging i dont know if the odin problem occurs because of that
i know i should have watched how to use twrp properly but i didnt
i know the whole thing is messy but please someone help me