I have run 3 different one click roots with 3 different zImage files.
I have never had an issue until now. The clockwork recovery won't flash.
Running the stuff manually to put it on it tells me:
failed to read from /data/local/tmp/zimage (Bad file number)
any ideas on how I can get this working? This is from a fresh odin install and OTA updates to di18.
I am far from a linux/android/bash/adb noob - I have never had this happen before and this is probably the 6th time I have rooted this phone.
Any ideas?
http://forum.xda-developers.com/showthread.php?t=1316769
was trying to follow above thread, unfortunately i keep getting hung up on actually installing any update.zip.
i have my wifes continuum its been rooted, i used odin to install recovery bin tar file. it took me a while but i finally installed the update.zip, then i flashed the clean ec07 rom. all it wants to do after the boot animation disappears is vibrate every so often. anyone have any ideas where to go
i figured it out, seems in the stock recovery bin the use of the soft buttons is necessary to activate the red recovery. and more importantly the ec07 radio/kernel needs to be flashed via odin to complete rom switch. always fun figuring it out
Sup you guys,
I may be in a new predicament for myself, so I would like to ask a few questions before I tackle this task. It seems that I've flashed a JB rom on the stock slot of SS, and I thought that I had the NC2 kernel intact to do so. However, all I get is a black screen and then a botched up system partition, a soft brick if you will, on the stock slot. Couldn't mount the system, so wiping anything is out the window. In order to make my phone usable for now, I had to install a rom on Slot 1. All is fine, but the battery drain is a killer, so I would like recover the system partition of the stock slot. Now, I've read a few threads that kind of pertains to my situation and I learned that a pit file flash can recover it back to normal. Can I just flash only the pit through Odin, or are there other steps that I have to do to get this back on track? Any help and guidance would be greatly appreciated.
I need help too
krazyg said:
Sup you guys,
I may be in a new predicament for myself, so I would like to ask a few questions before I tackle this task. It seems that I've flashed a JB rom on the stock slot of SS, and I thought that I had the NC2 kernel intact to do so. However, all I get is a black screen and then a botched up system partition, a soft brick if you will, on the stock slot. Couldn't mount the system, so wiping anything is out the window. In order to make my phone usable for now, I had to install a rom on Slot 1. All is fine, but the battery drain is a killer, so I would like recover the system partition of the stock slot. Now, I've read a few threads that kind of pertains to my situation and I learned that a pit file flash can recover it back to normal. Can I just flash only the pit through Odin, or are there other steps that I have to do to get this back on track? Any help and guidance would be greatly appreciated.
Click to expand...
Click to collapse
I just got into ROMs and safeatrap and such. I started by trying to load them to the stock slot, which failed every time. I then made slots and had 3 ROMs, but the battery life was not good.
So I wanted to put a ROM on the stock slot. This is with nc2 on kitkat. When I went to load a ROM in stock slot, safestrap failed saying it couldn't mount /system. I tried wiping, but there too it said fail to mount /system.
I did "Fix Permissions" and rebooted. I was greeted by the Samsung boot screen, but it froze there. No safestrap, nothing. I recovery booted and the stock recovery says "E:failed to mount /system (Invalid argument)"
So now it seems that no part of my phone can get to /system. I will look into a .pit file and would appreciate guidance as well.
Seems like you have the problem that I had a week ago. I fixed it by flashing a stock tar and the pit file through Odin. Though I wasn't too sure if just flashing pit would repair the system partition (though, I think it would've been fine; I should've just done it with no questions asked), but in my situation, I got a bit more desperate as my problem got sort of worse. Yea, running any rom on any slot other than the stock slot will kill your battery quick. So a reminder, if you have a messed up system partition, do not let the battery die because your phone will be soft bricked and you won't be able to boot up to anything other than Download mode. At that point, I just flashed the stock tar and the pit file just to be on the safe side and start over. After I rooted and installed SS, I went and checked if it was working properly. It did for the most part, but I remember that I was still on slot 1 before my battery died and SS was highlighted that I was still on that slot. I think because of that, it gave me certain errors on some of things I was testing out, but you will be able to install normally on the stock slot again. There are some other issues I have because of that ordeal, but it's not game breaking, so make sure that you're on the stock slot before flashing the files through Odin.
krazyg said:
Seems like you have the problem that I had a week ago. I fixed it by flashing a stock tar and the pit file through Odin. Though I wasn't too sure if just flashing pit would repair the system partition (though, I think it would've been fine; I should've just done it with no questions asked), but in my situation, I got a bit more desperate as my problem got sort of worse. Yea, running any rom on any slot other than the stock slot will kill your battery quick. So a reminder, if you have a messed up system partition, do not let the battery die because your phone will be soft bricked and you won't be able to boot up to anything other than Download mode. At that point, I just flashed the stock tar and the pit file just to be on the safe side and start over. After I rooted and installed SS, I went and checked if it was working properly. It did for the most part, but I remember that I was still on slot 1 before my battery died and SS was highlighted that I was still on that slot. I think because of that, it gave me certain errors on some of things I was testing out, but you will be able to install normally on the stock slot again. There are some other issues I have because of that ordeal, but it's not game breaking, so make sure that you're on the stock slot before flashing the files through Odin.
Click to expand...
Click to collapse
Thanks for the reply. I flashed a stock tar last night since the stock bootloader couldn't mount /system. Not sure which slot was selected in safestrap, I couldn't get back in because it would freeze before safestrap.
I did not use a .pit file (FYI), and am now back on stock ROM.
What I woluld like isto flash a custom ROM, say a debloated, rooted ROM with ODIN. I see they are all zips with folders, not .tar. Maybe I could take out the recovery.img and put it into a ROM's zip and save the zip as a tar and flash it? Would this possibly break my device if it tried to flash a wrong recovery? I don't know.
If anyone has some knowledge of these things, I would appreciate tips.
Why wouldn't you towel root, install SS, and install a ROM?
xdadevnube said:
Why wouldn't you towel root, install SS, and install a ROM?
Click to expand...
Click to collapse
Because I have only been able to get ROMs working on slots 1-4 of SS and not stock slot, so the battery life is terrible. Also, it would be faster and easier just to flash a ROM with ODIN and not have to worry if my version of android has a working root method (thankfully towelroot v3 worked).
I have tried everything I can find on the internet. Various Odin versions, and a bunch of stock roms from sammobile and other websites. I have been trying to follow everything to the dot, but I keep getting the same error: FAIL (AUTH) seconds after I press start. I have turned on USB debugging on my phone and I honestly don't know what do to. I just want to unroot and be done with this already. Please, someone help!
have you tried supersu to unroot? lol
No I haven't and I haven't even heard of that program yet, let me try and see. I'll post back the results.
Everything ran smoothly but I still have the "Custom" with the unlocked lock icon on my phone's start up. Also, my phone still can't update its software. It boots like it's going to but the installation is stalled at 25% until it just reboots and gives me a message that the update was interrupted. Please help!
what rom are you on? maybe the rom your on removed the update apks from the rom? the custom lock will be there until you manage to flash a full stock odin tar successfuly..
theres no reason the odin tar isnt unrooting the device if youre using the full odin tar.. this should put original rom/kernel/modem and wipe device completely
elliwigy said:
what rom are you on? maybe the rom your on removed the update apks from the rom? the custom lock will be there until you manage to flash a full stock odin tar successfuly..
theres no reason the odin tar isnt unrooting the device if youre using the full odin tar.. this should put original rom/kernel/modem and wipe device completely
Click to expand...
Click to collapse
See, I think that's the problem too. I had this phone rooted once before and I intalled a rom (that i forgot the name of) and then i installed the supposedly official ROM for SM-G900A and I think that's where it got messed up. What should I do now?
So my brand new SD care went corrupt while I had a lot of programs running from it... By means of Link2SD app I put system files on there too and now I get
E:failed to mount /system (Invalid argument)
I can't seem to fix this problem and it doesn't seem that this problem arises very often because I have found nothing in searching. Any help would be great... I don't want to have to put a hammer to it and then call Asurion for a replacement..... but that does sound fun lol.
I have tried to Odin everything I have in my backups but not sure if any of those are actually the original rom. I have been trying to figure out how to Odin CM or TWRP on to it... or get them install in some form with out the APK. I saw something about them being able to fix the issue.
Have you tried using ODIN and flashing back to a fresh, stock ROM?
I forgot to put all that. I have tried to Odin everything I have in my backups but not sure if any of those are actually the original rom. I have been trying to figure out how to Odin CM or TWRP on to it... or get them install in some form with out the APK. I saw something about them being able to fix the issue.
Our phones do not support CM or TWRP because we have a locked bootloader. You are on a Verizon G900V, right?
Here's a link to a post with stock ROMs you can Flash via Odin. Choose the appropriate one for the version you want and Flash. Make sure you back up anythibg you want to save.
http://forum.xda-developers.com/showthread.php?t=2784880
It doesn't matter what I flash I get the same error. The other things I have found say that the system and/or EFS needs to be re-made so to speak. TWRP has a command that does it and CM allows you to go in though ADB and do it..... That is the best I have found for answers so far. I don't see anything for FlashFire or SuperUser.
Flash using ODIN not FlashFire or anything else.
I have flashed with Odin.... I get no where.... doesn't matter what kernel I use or ROM or anything.... I was saying that the people that have solved this porblem before are using CW or TWRP to access the ADB to send commands for the phone to re-setup the system/EFS
Did you Flash the pit file on the page I linked earlier? That should repartition everything.
Still the same problem
So I just kept flashing tar files from the post above and finally the NI2 took along with the pit file. Thanks for your help @btonetbone
Eventually the NI2 + .pit file being flashed together fixed the problem.