Ok so I'm no dev by any means but I've been tinkering with flashing, and ROM's and mods I know my way around a build.prop, etc... I had my laptop on me when I bought my SG4 and I was rooted w/ no issues before I was even half way home. Now I've read countless forums but I can't flash a custom rom to save my life! EVERYTIME I try I keep getting the "You cannot use customer firmware or take to Verizon customer service blah, blah blah" I can easily reboot recovery and the backups work flawlessly. Know how to use the yellow triangle app (I think)still doesn't work... I don't get it. What am missing?
There is a reason that you're given two eyes, two ears, two hands and only one mouth.
If you are flashing custom roms especially the Verizon that has a locked bootloader, you would flash the rom you want, and before you boot, FLASH THE LOKI VERIZON KERNEL, it will boot.
Now for Triangle Away, yes it DOES work on G4's, you must be on a stock rom made for your device, run it, it will ask 2 times if the model # shown is your device, in my case att, say yes, and follow the instructions on the screen, if you run it, and it is the wrong device, you will brick your device...
Again, it works, I have used Triangle Away numerous times.. on my G4.
TheAxman said:
If you are flashing custom roms especially the Verizon that has a locked bootloader, you would flash the rom you want, and before you boot, FLASH THE LOKI VERIZON KERNEL, it will boot.
Now for Triangle Away, yes it DOES work on G4's, you must be on a stock rom made for your device, run it, it will ask 2 times if the model # shown is your device, in my case att, say yes, and follow the instructions on the screen, if you run it, and it is the wrong device, you will brick your device...
Again, it works, I have used Triangle Away numerous times.. on my G4.
Click to expand...
Click to collapse
Wouldn't it just be easier to flash a custom recovery, which will let you easily install ROMs?
Speaking of recoveries does it matter which one I use and if so do you know why? On a side note thank you for your help. If you had a link to Lori I'd love your life.
There is a reason that you're given two eyes, two ears, two hands and only one mouth.
Nope its all preference really. However if you make a backup with twrp then u cant restore it say using cwm if you switch down the road. I prefer cwm myself. Have been using it for close to 3 years if not more, on 4 devices currently, and havr nevet had a single problem with it.
SCH-I545 using Tapatalk 2
igacek said:
Wouldn't it just be easier to flash a custom recovery, which will let you easily install ROMs?
Click to expand...
Click to collapse
I actually answered 2 questions in that post...sorry.
yes,you can flash a custom rom, but it will re-appear.
Related
First off, sorry if this has already been covered somewhere and I'm just not finding it.. I've been searching and reading a lot and l am learning a ton, I just cant seem to find an answer for sure..
Note - I am mostly a 'noob'. I have had other sammy phones (a Galaxy S and a Gnex) and have rooted them and put CWM and TWRP on em, and flashed many kinds of custom roms and stuff,, soft bricked em several times,, had to use ODIN to flash em back to stock and start over, followed instructional threads to hack around using ADB and Fastboot commands for different things, etc..Basic playing around with stuff like that. So I sorta know my way around the basics of playing with at least Sammy brand phones.
I recently bought a nice used S4 to play with. I immediately start looking at root instructions and bootloaders and roms,, and ran dead into the brick wall of it already having the ME7 devil on it and thus me being locked out beyond rooting. Since I wanted an S4 specifically for playing with ROMs, I sold that stock ME7 S4 and bought a different one that someone had already put TWRP on and a custom ROM. So now I should be good to go flashing away.
So my question is, if I ever do want to try running a stock ME7 rom sometime, is there one I can flash while playing around flashing trying out different roms that would NOT somehow lock the bootloader? I'm not talking about accepting a Verizon OTA update, I know better than that. I'm talking about manually flashing roms (I am assuming if I flashed a 100% stock Verizon rom it might screw myself and lock the bootloader,, maybe I am mistaken on that assumption idk). I'm seeing the "bonestock me7" rom here on XDA, would that be safe to try for a stock ME7 experience?
ok i'll shut up now,, sorry for the long post.
You're good to go. Just look in the dev section for one to your liking. I've been running BoneStock but there are others including one from andybones which completely stock. Stay clear of any ROM requiring you to Odin as I'd worry about that.
Sent from my SCH-I545 using xda app-developers app
Cool. Thanks much for the help!
Basic operations
sohead said:
First off, sorry if this has already been covered somewhere and I'm just not finding it.. I've been searching and reading a lot and l am learning a ton, I just cant seem to find an answer for sure..
Note - I am mostly a 'noob'. I have had other sammy phones (a Galaxy S and a Gnex) and have rooted them and put CWM and TWRP on em, and flashed many kinds of custom roms and stuff,, soft bricked em several times,, had to use ODIN to flash em back to stock and start over, followed instructional threads to hack around using ADB and Fastboot commands for different things, etc..Basic playing around with stuff like that. So I sorta know my way around the basics of playing with at least Sammy brand phones.
I recently bought a nice used S4 to play with. I immediately start looking at root instructions and bootloaders and roms,, and ran dead into the brick wall of it already having the ME7 devil on it and thus me being locked out beyond rooting. Since I wanted an S4 specifically for playing with ROMs, I sold that stock ME7 S4 and bought a different one that someone had already put TWRP on and a custom ROM. So now I should be good to go flashing away.
So my question is, if I ever do want to try running a stock ME7 rom sometime, is there one I can flash while playing around flashing trying out different roms that would NOT somehow lock the bootloader? I'm not talking about accepting a Verizon OTA update, I know better than that. I'm talking about manually flashing roms (I am assuming if I flashed a 100% stock Verizon rom it might screw myself and lock the bootloader,, maybe I am mistaken on that assumption idk). I'm seeing the "bonestock me7" rom here on XDA, would that be safe to try for a stock ME7 experience?
ok i'll shut up now,, sorry for the long post.
Click to expand...
Click to collapse
Writing the nand memory on this handset is nearly impossible through conventional means, suggest a maintenance jig for the board.
heyazzo said:
Writing the nand memory on this handset is nearly impossible through conventional means, suggest a maintenance jig for the board.
Click to expand...
Click to collapse
Whats the "nand memory"? the area of memory where the recovery/bootloader code is stored? and what do you mean by conventional means? like using CWM or TWRP I assume? what about ODIN? from prior experience ODIN has written over a custom bootloader that I had loaded with a stock one (if I remember right anyway, I think I've lost my custom CWM or TWRP bootloaders by flashing a stock rom via ODIN,, back on the Gnex, I have never tried that with an S4 but assume it would be the same deal). And whats a "maintenance jig"?
lol sorry for so many questions,, warned ya I was a NOOB
No such thing as a dumb question.
sohead said:
Whats the "nand memory"? the area of memory where the recovery/bootloader code is stored? and what do you mean by conventional means? like using CWM or TWRP I assume? what about ODIN? from prior experience ODIN has written over a custom bootloader that I had loaded with a stock one (if I remember right anyway, I think I've lost my custom CWM or TWRP bootloaders by flashing a stock rom via ODIN,, back on the Gnex, I have never tried that with an S4 but assume it would be the same deal). And whats a "maintenance jig"?
lol sorry for so many questions,, warned ya I was a NOOB
Click to expand...
Click to collapse
I was always curious about things that I didn't understand. First, try to understand the security that's already on this device, then decide if an update really did kill one qfuse out of say 10-12 on the board depending on the lifecycle they gave this particular set of commo gear. Search MSM 8960 security, then get back to me via PM, I want to help you any way I can.
So, I have the i545, it was updated to the newest firmware when I got it. Lucky!
I first tried all the old stuff like the noob I am. Bricked it a couple times, blah blah, fixed it.
I tried the newer stuff, and was successful in getting into the recovery, but all I can do is wipe personal data and cache, its not CWM. When I do, it gets locked into download odin section and says its broken essentially.
Any bootloader bricks it, and any attempt to do the newer stuff like Loki has bricked it. I have the original Rom saved, so I just have to push it through odin each time.
I want Hyperdrive rom, I am rooted, and I can't get the common "working" ways to work. What am I doing wrong? I just tried the loki method and it locked into odin download when it restarted.
I'm not frustrated at anyone here by any means, I know the big companies are jerks, and....I need help side stepping them...
Any suggestions?
Again, i545, 32gb, Verizon Galaxy s4. It is rooted. And I want Hyperdrive rom.
Thanks!
EDIT.
If there is a way through odin or something to push Hyperdrive, I dont need the CWM. Im just a simple custom rom user, nothing crazy. And if there is no way to go from the ME7 update, be it downgrade and then root and flash, be it odin, be in CWM or Loki method, etc., where do I go to add to the bounty?
Excessumcarcer said:
So, I have the i545, it was updated to the newest firmware when I got it. Lucky!
I first tried all the old stuff like the noob I am. Bricked it a couple times, blah blah, fixed it.
I tried the newer stuff, and was successful in getting into the recovery, but all I can do is wipe personal data and cache, its not CWM. When I do, it gets locked into download odin section and says its broken essentially.
Any bootloader bricks it, and any attempt to do the newer stuff like Loki has bricked it. I have the original Rom saved, so I just have to push it through odin each time.
I want Hyperdrive rom, I am rooted, and I can't get the common "working" ways to work. What am I doing wrong? I just tried the loki method and it locked into odin download when it restarted.
I'm not frustrated at anyone here by any means, I know the big companies are jerks, and....I need help side stepping them...
Any suggestions?
Again, i545, 32gb, Verizon Galaxy s4. It is rooted. And I want Hyperdrive rom.
Thanks!
Click to expand...
Click to collapse
Your stuck at the moment there is no custom recovery for me7. Theres been about 100 posts/threads about it. Hashcode a member here is working on a safestrap for me7 so custom roms can be flashed I advise checking it out. Its in the general section.
http://forum.xda-developers.com/showthread.php?p=45185924
Sent from my SCH-I545 using Tapatalk 2
---------- Post added 2nd September 2013 at 12:07 AM ---------- Previous post was 1st September 2013 at 11:53 PM ----------
No way to downgrade or flash rom through odin. Like I said your stuck for moment on stock me7. In the thread I linked there is a donation link for hashcode with the safestrap. There is also a bounty page for unlocking the bootloader in the general section as well.
Sent from my SCH-I545 using Tapatalk 2
Excessumcarcer said:
So, I have the i545, it was updated to the newest firmware when I got it. Lucky!
I first tried all the old stuff like the noob I am. Bricked it a couple times, blah blah, fixed it.
I tried the newer stuff, and was successful in getting into the recovery, but all I can do is wipe personal data and cache, its not CWM. When I do, it gets locked into download odin section and says its broken essentially.
Any bootloader bricks it, and any attempt to do the newer stuff like Loki has bricked it. I have the original Rom saved, so I just have to push it through odin each time.
I want Hyperdrive rom, I am rooted, and I can't get the common "working" ways to work. What am I doing wrong? I just tried the loki method and it locked into odin download when it restarted.
I'm not frustrated at anyone here by any means, I know the big companies are jerks, and....I need help side stepping them...
Any suggestions?
Again, i545, 32gb, Verizon Galaxy s4. It is rooted. And I want Hyperdrive rom.
Thanks!
EDIT.
If there is a way through odin or something to push Hyperdrive, I dont need the CWM. Im just a simple custom rom user, nothing crazy. And if there is no way to go from the ME7 update, be it downgrade and then root and flash, be it odin, be in CWM or Loki method, etc., where do I go to add to the bounty?
Click to expand...
Click to collapse
It would have helped you greatly to have research GS4 with ME7....it can ONLY be rooted at this time.
decaturbob said:
It would have helped you greatly to have research GS4 with ME7....it can ONLY be rooted at this time.
Click to expand...
Click to collapse
The first time it bricked itself I did some research. Found that the ME7 was a punk, found guides where people claimed to have gotten around it, which all failed. I presumed it had been cracked if there were ways posted, but after they failed I came here.
Excessumcarcer said:
The first time it bricked itself I did some research. Found that the ME7 was a punk, found guides where people claimed to have gotten around it, which all failed. I presumed it had been cracked if there were ways posted, but after they failed I came here.
Click to expand...
Click to collapse
It bricked "itself" pretty amazing. You should do a little research before you mess with your phone.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
It bricked "itself" pretty amazing. You should do a little research before you mess with your phone.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
Ugh, I could explain everything in detail and not joke around, but then I'd just be a jerk. I've rooted, installed bootloaders, roms, etc., on many phones, not just mine. I know what I'm doing so generally I don't have to research how to do it. I upgraded from a galaxy S3 with MOAR (rom) installed, also did paranoid rom right before, jumped in and hoped that the S4 would play nice. It didn't. And you won't find a post from me asking how to unbrick it. The original Rom was backed up, so nothing to fear. I understand that bricking a phone is part of the risk, and unbricking it is part of the knowledge one needs to jump in comfortably. I did it 8 times yesterday. I tried 5 methods, one I tried a couple times because I could get into the bootloader but it would freeze on removing the cache. After each different combo, it killed it. Once I felt defeated for the day I came here. Believe me, Im not the person who turns on their phone and posts for help about what to do after its on. ^_^
Well, all I can say is you're learning the s4 the hard way
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
ME7 =no custom recovery =no custom ROMs.
Read the thread about SafeStrap being worked on by hashcode
Sent from my Nexus 7 using Tapatalk 2
jd1639 said:
Well, all I can say is you're learning the s4 the hard way
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
Thats the only way I learn. : ) Following the 50 million different articles and blogs and tutorials is the only way I ever find anything. Rarely do I get a piece of equipment that just works the first time with the common used method for it. That's never my luck. There's always something stupid that stops it. This is the same with everything in truth, cars, computers, phones, etc. Nothing has ever just worked for me. So, now I just throw things at it until something goes through. People say there's no way, well...if that's the case then all the DEV's should stop trying. lol. There is a way, we just have to find it.
Well, every phone is different and just jumping in on a new phone without knowing the issues and pitfalls because you rooted other phones being naive imo. I've rooted maybe a half dozen phones and countless roms but when i got my S4 i still waited a few days and just read. The point is no matter how many times you do something whenever you get something new/updated, be a phone or anything else, you should always take the time to read and read.
Edit:
Also because of these locked down bootloaders (like the sammy knox) i would if i were you do A LOT of reading before buying new phones in the future to make sure you CAN root and slap a custom recovery on it. The root and custom recoveries may be a thing of the past pretty soon and we'll be purchasing Developers and Google Play editions if we want custom stuff.
I apologize in advance if this question has already been asked but I was just wondering if it were possible to completely wipe the gs4 to stock like it come straight from Samsung and load your own kernels and roms. Or even load a dev edition or Google play edition load out so that the phone could be customizable. I mean isn't that all vzw does anyway is take the Samsung and Google packages add there own twist and apps to it and lock it down.? Sorry if this seems like a waist of time but it's just a question I keep asking myself but don't have the know how to test it for myself. Any input or further ideas would be appreciated.
cnall09 said:
I apologize in advance if this question has already been asked but I was just wondering if it were possible to completely wipe the gs4 to stock like it come straight from Samsung and load your own kernels and roms. Or even load a dev edition or Google play edition load out so that the phone could be customizable. I mean isn't that all vzw does anyway is take the Samsung and Google packages add there own twist and apps to it and lock it down.? Sorry if this seems like a waist of time but it's just a question I keep asking myself but don't have the know how to test it for myself. Any input or further ideas would be appreciated.
Click to expand...
Click to collapse
Here.. http://forum.xda-developers.com/showthread.php?t=2606501
Take some time and read through what's on that thread.
To answer your question though, unless your S4 is an MDK build or a Developer Edition you aren't going to be able to have a true custom recovery that allows for AOSP ROMs or custom kernels.
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Mistertac said:
Here.. http://forum.xda-developers.com/showthread.php?t=2606501
Take some time and read through what's on that thread.
To answer your question though, unless your S4 is an MDK build or a Developer Edition you aren't going to be able to have a true custom recovery that allows for AOSP ROMs or custom kernels.
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
I have read through many many forums hoping someone has found away to bypass the bootloader and nothing so far. Im not asking if i can revert it to an early kernel. I merely suggested to take the s4 and revert it to basically it's shell and find the packages that come for the dev edition or google play edition and load it up. That doesn't sound to crazy does it?
cnall09 said:
I have read through many many forums hoping someone has found away to bypass the bootloader and nothing so far. Im not asking if i can revert it to an early kernel. I merely suggested to take the s4 and revert it to basically it's shell and find the packages that come for the dev edition or google play edition and load it up. That doesn't sound to crazy does it?
Click to expand...
Click to collapse
Ohh OK gotcha! Hey to me that sounds like a great plan lol just I'm in way over my head when it comes to fully understanding what's needed to make something like that really happen.
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Mistertac said:
Ohh OK gotcha! Hey to me that sounds like a great plan lol just I'm in way over my head when it comes to fully understanding what's needed to make something like that really happen.
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
You and me both buddy. But hopefully someone with the know how will see this and give it a try. Who knows it could be the answer we have all been waiting for.
cnall09 said:
I have read through many many forums hoping someone has found away to bypass the bootloader and nothing so far. Im not asking if i can revert it to an early kernel. I merely suggested to take the s4 and revert it to basically it's shell and find the packages that come for the dev edition or google play edition and load it up. That doesn't sound to crazy does it?
Click to expand...
Click to collapse
You can't just revert to the original Google-supplied Android files as that operating system shell doesn't have drivers for the specific hardware devices in your phone - it has to be modified to add drivers for the screen, radio, cameras, touchpad, and so forth. That's files provided in the Kernel, so in the end you're asking to revert to an earlier kernel.
You can't install a Google Edition ROM image without customizing it for the specific phone, which is what some people have done. That is, to take the stock ROM and replace bits with those from the GE phone to try to get closer to the original; however, you can't go very far with this without having to change the kernel to make it compatible with GE, so you're stuck.
It's not a horrible situation as we can still use Safestrap to boot a custom ROM as long as it's compatible with the touchwiz kernel. If we could replace that kernel, we'd be able to run a lot more ROMs, but since the locked bootloader will reject a non-Samsung kernel, we're stuck.
k1mu said:
You can't just revert to the original Google-supplied Android files as that operating sysm shell doesn't have drivers for the specific hardware devices in your phone - it has to be modified to add drivers for the screen, radio, cameras, touchpad, and so forth. That's files provided in the Kernel, so in the end you're asking to revert to an earlier kernel.
You can't install a Google Edition ROM image without customizing it for the specific phone, which is what some people have done. That is, to take the stock ROM and replace bits with those from the GE phone to try to get closer to the original; however, you can't go very far with this without having to change the kernel to make it compatible with GE, so you're stuck.
It's not a horrible situation as we can still use Safestrap to boot a custom ROM as long as it's compatible with the touchwiz kernel. If we could replace that kernel, we'd be able to run a lot more ROMs, but since the locked bootloader will reject a non-Samsung kernel, we're stuck.
Click to expand...
Click to collapse
I understand all of that. I am currently running hyper drive installed through safestrap but it still feels governed apposed to a Google rom. We are still stuck on 4.3 and everywhere else has a later version. I still don't understand why you can't completely erase the internals to reload with a different loadout. Isn't it the same phone regardless of where you get it rather it be samsung or verizon or google?whenever we download updates it installs new cameras and radios I'm not talking about reverting I'm talking about completely shipping the phone down to nothing but download mode and install new kernels drivers and software. Just like the developers at any of the companies do except we won't have to do any testing or development
cnall09 said:
I understand all of that. I am currently running hyper drive installed through safestrap but it still feels governed apposed to a Google rom. We are still stuck on 4.3 and everywhere else has a later version. I still don't understand why you can't completely erase the internals to reload with a different loadout. Isn't it the same phone regardless of where you get it rather it be samsung or verizon or google?whenever we download updates it installs new cameras and radios I'm not talking about reverting I'm talking about completely shipping the phone down to nothing but download mode and install new kernels drivers and software. Just like the developers at any of the companies do except we won't have to do any testing or development
Click to expand...
Click to collapse
Short answer - no, you can't do that...it doesn't work that way. Depending on the bootloader your phone came with you cannot downgrade. You can try erasing everything and starting over but that's one thing you cannot change.....your stuck.
cnall09 said:
I understand all of that. I am currently running hyper drive installed through safestrap but it still feels governed apposed to a Google rom. We are still stuck on 4.3 and everywhere else has a later version. I still don't understand why you can't completely erase the internals to reload with a different loadout. Isn't it the same phone regardless of where you get it rather it be samsung or verizon or google?whenever we download updates it installs new cameras and radios I'm not talking about reverting I'm talking about completely shipping the phone down to nothing but download mode and install new kernels drivers and software. Just like the developers at any of the companies do except we won't have to do any testing or development
Click to expand...
Click to collapse
Feel free to do what you want...but you may end up with a $600 door stop. ..
Sent from my SCH-I545 using XDA Premium 4 mobile app
cnall09 said:
I understand all of that. I am currently running hyper drive installed through safestrap but it still feels governed apposed to a Google rom. We are still stuck on 4.3 and everywhere else has a later version. I still don't understand why you can't completely erase the internals to reload with a different loadout. Isn't it the same phone regardless of where you get it rather it be samsung or verizon or google?whenever we download updates it installs new cameras and radios I'm not talking about reverting I'm talking about completely shipping the phone down to nothing but download mode and install new kernels drivers and software. Just like the developers at any of the companies do except we won't have to do any testing or development
Click to expand...
Click to collapse
You can totally do this, you can replace the kernel and everything. The phone won't boot, and you'd have a hard brick though. The problem isn't replacing the kernel, the problem is getting the phone to boot after doing so. Download mode operates through aboot, aboot has protections and conditions set that regulate what kernel and recovery partitions you can boot. If these are replaced with a "non-allowed" version the phone simply won't boot, in other words it would be hard-bricked at this point.
Sent from my SCH-I545 using XDA Premium 4 mobile app
cnall09 said:
I understand all of that. I am currently running hyper drive installed through safestrap but it still feels governed apposed to a Google rom. We are still stuck on 4.3 and everywhere else has a later version. I still don't understand why you can't completely erase the internals to reload with a different loadout. Isn't it the same phone regardless of where you get it rather it be samsung or verizon or google?whenever we download updates it installs new cameras and radios I'm not talking about reverting I'm talking about completely shipping the phone down to nothing but download mode and install new kernels drivers and software. Just like the developers at any of the companies do except we won't have to do any testing or development
Click to expand...
Click to collapse
"Shipping the phone down to nothing but download mode" - yes, you can wipe the internal ROM and strip it down to download mode.
Then you have a brick which runs just the downloader. OK, it's not quite dead, because you can flash stuff. But what can you flash?
OK, so you want to "install new kernels drivers and software". That's not always possible. You flash kernels and and software using the bootloader, but the bootloader won't allow you to flash a kernel that's not pre-approved by Samsung. If you're rooted, the rest of the phone storage can be overwritten with whatever custom software you want, but there's a hitch. You can install whatever software you want EXCEPT for the kernel. (If not rooted, you can't even do that without a custom recovery, which the bootloader won't allow.)
The software that you flash depends on the kernel to drive the hardware, so you can't flash base software that requires services that the stock kernel doesn't provide. This is why only certain ROMs are available for Safestrap - you can't flash CyanogenMod on a Safestrapped i545 because CM isn't compatible with the Touchwiz kernel. It's theoretically possible to modify CM to make it work with a TW kernel, but nobody has done that (unsurprising, as it would be a lot of work that would have to be repeated each CM release.)
The bootloader chain is the way Samsung enforces the restrictions on what you can and can't do with your phone. With a locked bootloader (like ours), you're very limited. Until the bootloader protections are breached, what you propose can't be done.
decaturbob said:
Feel free to do what you want...but you may end up with a $600 door stop. ..
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
well thank you so much for your permission to do what I want I was so afraid you wouldn't approve. and I have geek squad protection with unlimited replacements and no deductable so it doesn't hurt my feelings in the least bit if things don't go as planned. I know i ain't as seasoned as some of yall on here but thats how things get done by asking questions and trial/error.
k1mu said:
"Shipping the phone down to nothing but download mode" - yes, you can wipe the internal ROM and strip it down to download mode.
Then you have a brick which runs just the downloader. OK, it's not quite dead, because you can flash stuff. But what can you flash?
OK, so you want to "install new kernels drivers and software". That's not always possible. You flash kernels and and software using the bootloader, but the bootloader won't allow you to flash a kernel that's not pre-approved by Samsung. If you're rooted, the rest of the phone storage can be overwritten with whatever custom software you want, but there's a hitch. You can install whatever software you want EXCEPT for the kernel. (If not rooted, you can't even do that without a custom recovery, which the bootloader won't allow.)
The software that you flash depends on the kernel to drive the hardware, so you can't flash base software that requires services that the stock kernel doesn't provide. This is why only certain ROMs are available for Safestrap - you can't flash CyanogenMod on a Safestrapped i545 because CM isn't compatible with the Touchwiz kernel. It's theoretically possible to modify CM to make it work with a TW kernel, but nobody has done that (unsurprising, as it would be a lot of work that would have to be repeated each CM release.)
The bootloader chain is the way Samsung enforces the restrictions on what you can and can't do with your phone. With a locked bootloader (like ours), you're very limited. Until the bootloader protections are breached, what you propose can't be done.
Click to expand...
Click to collapse
yes sir i did mean stripped down. sorry for the typo. and ok im not talking about stripping it down just to boot a custom rom or kernel. i want authentic samsung/google software and kernels. so the samsung wouldn't even accept its on software. I apologize for seeming argumentative thats not my intent at all. im just trying to get a good idea and handle on how some of this works. i appreciate your input and help on this matter and your patience.
cnall09 said:
yes sir i did mean stripped down. sorry for the typo. and ok im not talking about stripping it down just to boot a custom rom or kernel. i want authentic samsung/google software and kernels. so the samsung wouldn't even accept its on software. I apologize for seeming argumentative thats not my intent at all. im just trying to get a good idea and handle on how some of this works. i appreciate your input and help on this matter and your patience.
Click to expand...
Click to collapse
Yeah it's a good idea for someone like yourself who seems fairly new to this stuff, because what you're proposing is kind of what were trying to do to unlock the boot loader. The problem basically is that the very base software contains checks to make sure you're using Samsung approved software.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
joshm.1219 said:
Yeah it's a good idea for someone like yourself who seems fairly new to this stuff, because what you're proposing is kind of what were trying to do to unlock the boot loader. The problem basically is that the very base software contains checks to make sure you're using Samsung approved software.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i know how to permanently unlock it without bricking it. Hit it with a hammer smoke a whole lot n watch in amazement as the bootloader flies out of this phone, able to be replaced of course. Just kidding dont do that, although ive been tempted
cnall09 said:
well thank you so much for your permission to do what I want I was so afraid you wouldn't approve. and I have geek squad protection with unlimited replacements and no deductable so it doesn't hurt my feelings in the least bit if things don't go as planned. I know i ain't as seasoned as some of yall on here but thats how things get done by asking questions and trial/error.
Click to expand...
Click to collapse
reading helps too my friend....also I wouldn't jump to the conclusion that geek squad warranty coverage applies to the the misuse or negligent use of a product....you best read the fine print again.
any way good luck
So I was getting really frustrated with ROMS not working right so I followed someones advice and used ODIN to upgrade to NC5. I got my phone right after launch and rooted it the day I got it, installed TWRP and I have always had an icon on the Samsung screen that is a little lock with the word custom under it and that is the only thing I have retained after upgrading. I can no longer flash a custom recovery via GooManager, the phone simply won't let me. I am guessing when I updated it put me on the latest bootloader and locked it. Is this the case? I really don't like the idea of safestrap, but if I have to use it now I guess I will. If it did indeed upgrade my bootloader, wouldn't the "Custom" icon have disappeared from my lock splash screen?
So what exactly have I done to my phone? Can anyone help me figure out where to go from here?
Custom splash screen only represents that the phone's flash counter has been triggered. Means nothing.
I can't believe you updated from an MDK phone man. If you want to continue to use custom rom's you'll have to use towel root and AT&T's 3.72 safestrap. And get comfortable with Odin. Unfortunately there's no way to get a true custom recovery back on your device.
TB13 said:
So I was getting really frustrated with ROMS not working right so I followed someones advice and used ODIN to upgrade to NC5. I got my phone right after launch and rooted it the day I got it, installed TWRP and I have always had an icon on the Samsung screen that is a little lock with the word custom under it and that is the only thing I have retained after upgrading. I can no longer flash a custom recovery via GooManager, the phone simply won't let me. I am guessing when I updated it put me on the latest bootloader and locked it. Is this the case? I really don't like the idea of safestrap, but if I have to use it now I guess I will. If it did indeed upgrade my bootloader, wouldn't the "Custom" icon have disappeared from my lock splash screen?
So what exactly have I done to my phone? Can anyone help me figure out where to go from here?
Click to expand...
Click to collapse
what you did wrong is not research what you were doing.......I can;t believe you followed someone's advice to rid your phone of MDK...
.
this thread contains links and info you best read before proceeding any further
http://forum.xda-developers.com/showthread.php?t=2606501
Another one bites the dust. That's too bad. Sorry nothing can be done now
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Another one bites the dust. That's too bad. Sorry nothing can be done now
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
if we had a dollar every time we see same or similar post....the aversion to reading and research is compelling
Aaaannnnddddd idiot of the day award goes to me. It had been so long since I had messesd with my phone that I didn't even know I still had an MDK device, I will miss it and I will be shunned for killing it, but life goes on.
I wish I had the power to sticky the threads that people should look at before attempting something like this instead of having useless, unupdated threads stickied in every subforum.
Have a Verizon SCH-I535 running android 4.4.2 I have been trying in vain for two days now to root this phone and replace the stock recovery. I'm aiming for running clockworkmod recovery and cyanogenmod. I've followed their instructions using terminal and heimdall which DOES WORK and communicate with device.
Problem is EVERY TIME I boot to recovery and try to run anything...a stock zip to downgrade it says "failed to verify whole-file signature" and "signature verification failed."
The only thing I can do is run towelroot.apk, install superSU.apk, and use the stock ROM. Using ODIN is a waste of time and fails every file every time. At this point I'm honestly kinda amazed I don't have a brick I've done so many transfers! I also always wipe data/cache before I install zips off SDcard.
I'm out of answers. Oh! At one point my counter was too high and it was also saying, "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help. " I downloaded TriangleAway and it reset the counter back to zero and the error went away, but there for a while I couldn't even get to recovery (take battery out and cancel out of download mode FYI to boot back into device).
Samsung Kies is the closest glimmer of hope I've gotten. Twice now it has returned my phone back to stock; so I don't think its a hardware issue ie. bad ram or ROM memory...
I've rooted a couple older Galaxy S3's running 4.3 with no issue. It's been a couple years but that was a simple ODIN flash and I kept standard ROM/recovery as I was flashing carriers and didn't want to risk breaking anything.
I'd like to think I'm not an idiot, but what the hell am I missing. I've watched dozens of youtube videos and read hundreds of guides that all seem to work. It's something with this phone and kies or some type of heightened security...
Thanks in advance! You can also email me at [email protected]
Anyone? Even a, "Yeah, that's weird man! Sounds like you did everything right!" Would make me feel better...
Yes I've tried it and it worked make sure u have the unofficial safestrap the one for your phone and do the busy box and terminal emulator thing and it works if you try to install safestrap without the other things you will brick I did it twice but it very easy to unbrick so download busybox terminal emulator and the correct safestrap for you device and also I'm on 4.4.2 also and there is only one rom i have found that works and its called superliter there ya go hope I help would provide download links but I'm not home
Also I forgot to mention your bootloader won't be unlocked it'll be bypassed and you will have a custom recovery
androidforums.com/threads/verizon-verizon-bootloader-unlock.856221/page-2[/url]
forum.xda-developers.com/showthread.php?t=2605648
device specific safestrap recovery and image
4.4.2 has a 'locked bootloader' courtesy of Verizon! This is what has been giving me fits... Going to try to go back to totally stock 4.4.2 (right not my bootloader is the international version and locked out), then towelroot to root, then install root explorer/supersu, then I'll try safestrap and hopefully its the miracle cure!
schmitey said:
Have a Verizon SCH-I535 running android 4.4.2 I have been trying in vain for two days now to root this phone and replace the stock recovery. I'm aiming for running clockworkmod recovery and cyanogenmod. I've followed their instructions using terminal and heimdall which DOES WORK and communicate with device.
Problem is EVERY TIME I boot to recovery and try to run anything...a stock zip to downgrade it says "failed to verify whole-file signature" and "signature verification failed."
The only thing I can do is run towelroot.apk, install superSU.apk, and use the stock ROM. Using ODIN is a waste of time and fails every file every time. At this point I'm honestly kinda amazed I don't have a brick I've done so many transfers! I also always wipe data/cache before I install zips off SDcard.
I'm out of answers. Oh! At one point my counter was too high and it was also saying, "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help. " I downloaded TriangleAway and it reset the counter back to zero and the error went away, but there for a while I couldn't even get to recovery (take battery out and cancel out of download mode FYI to boot back into device).
Samsung Kies is the closest glimmer of hope I've gotten. Twice now it has returned my phone back to stock; so I don't think its a hardware issue ie. bad ram or ROM memory...
I've rooted a couple older Galaxy S3's running 4.3 with no issue. It's been a couple years but that was a simple ODIN flash and I kept standard ROM/recovery as I was flashing carriers and didn't want to risk breaking anything.
I'd like to think I'm not an idiot, but what the hell am I missing. I've watched dozens of youtube videos and read hundreds of guides that all seem to work. It's something with this phone and kies or some type of heightened security...
Thanks in advance! You can also email me at [email protected]
Click to expand...
Click to collapse
Verizon spends a pretty penny when it comes to making sure their devices................. stay theirs i guess you can say when it comes to the boot-loader! To my knowledge their isn't a way of getting around that with a permanent recovery flash that completely replaces Verizon's stock recovery. I can almost guaranteeing you that your problem is Verizon locked boot loader. Stock recoveries are solely only their for their technicians, so unless someone somehow has leaked a program that they use to get around that stuff without screwing it up, we the general public will never be able to flash anything permanent with any phones stock recovery unless we have their "secret" software! Every once in a while you do find a leaked one. I got lucky and found one for the T-mobile galaxy S6 Edge. As far as Odin I've noticed that the new versions seem to be very particular. Meaning if a dot or a space is misplaced anywhere in the zip or what not it will always fail. With my t-mobile S6 I spent two days figuring out I had to take a letter out of the name of the file i was trying to Odin. One letter that was it and once I did that it went flawlessly. Otherwise man i really don't know what to tell you, seems like ya followed the lines as described. Just remember its a Samsung Galaxy in my opinion Galaxies are unbrickable. Ive even pulled the cord in the middle of a Odin flash to see if i could brick it for good and was still able to go right into download mode and flash stock back onto it and everything working. So don't be afraid of bricking it. It will be way easier (sorry to say) for you to re-flash stock right now! Good luck bro wish you the best!
---------- Post added at 08:25 PM ---------- Previous post was at 08:18 PM ----------
schmitey said:
4.4.2 has a 'locked bootloader' courtesy of Verizon! This is what has been giving me fits... Going to try to go back to totally stock 4.4.2 (right not my bootloader is the international version and locked out), then towelroot to root, then install root explorer/supersu, then I'll try safestrap and hopefully its the miracle cure!
Click to expand...
Click to collapse
Are you able to disable Signature verification in the recovery?
Are you able to disable Signature verification in the recovery?
You can once I flash to say clockworkmod recovery. Stock I don't know of a way to...hence the Catch 22 there's no going forward and no going back...you're stuck with stock ROM/recovery but at least its rooted.
Well ****. Take my word for it you CAN brick a galaxy s3.
I used KIES to restore back to factory stock recovery etc etc.
I then used towelroot to root phone and install supersu. I then installed safestrap which totally worked! I was able to bypass the stock recovery and everything was running smoothly...I got overzealous and tried to install the cyanogenmod vrale6 bootloader zip through safestrap. I currently have a brick. It won't boot, no led's, no screen, no vibrate. I have another galaxy s3 charging batteries and swapped it out...removed sim and micro sd. I should have just installed the cyanogenmod app and done it that way...
So close and now I bricked it...
OK got my brick back by writing image to microSD card...pretty happy about that little trick. And that's utter nonsense about needing the same size card as your internal memory! I used a 32gig card on a 16gig phone...
Still trying but this locked 4.4.2 bootloader is BULL****. Going to try to downgrade but I'm not sure I'm going to end up with anything but a rooted stock rom...
So does anyone know of a way to downgrade or change recovery on Verizon 4.4.2?
I have s3 Verizon I-535 & clockworkmod recovery is not gonna work cuz of the locked bootloader, I used safestrap that's the only recovery for 4.4.2
slimcyril said:
I have s3 Verizon I-535 & clockworkmod recovery is not gonna work cuz of the locked bootloader, I used safestrap that's the only recovery for 4.4.2
Click to expand...
Click to collapse
Thanks for the reply. But with safestrap its a step in the right direction but every zip fails...so I don't see what it really does for us. Don't see myself ever running cyanogenmod at this rate unless you know something I don't...
schmitey said:
Thanks for the reply. But with safestrap its a step in the right direction but every zip fails...so I don't see what it really does for us. Don't see myself ever running cyanogenmod at this rate unless you know something I don't...
Click to expand...
Click to collapse
Well no zip has ever failed on my end using safestrap, does your device have init.d support?
No point me to it! I'm basically stock rom running safestrap atm. If you can walk me through this I'd be grateful.. Just remember I'm locked Verizon bootloader...
And may I say I finally got the I535 switched to selectel (was on a flashed sprint L710) and holy cow 4G LTE is fast...faster than my home internet!
schmitey said:
No point me to it! I'm basically stock rom running safestrap atm. If you can walk me through this I'd be grateful.. Just remember I'm locked Verizon bootloader...
And may I say I finally got the I535 switched to selectel (was on a flashed sprint L710) and holy cow 4G LTE is fast...faster than my home internet!
Click to expand...
Click to collapse
Go to mount on safestrap & see if your system partition is checked(mounted) e.t.c & go to playstore install universal init.d app
Note; uncheck verify signature checks if you're trying flash anything via recovery or else it will definitely fail
slimcyril said:
Go to mount on safestrap & see if your system partition is checked(mounted) e.t.c & go to playstore install universal init.d app
Note; uncheck verify signature checks if you're trying flash anything via recovery or else it will definitely fail
Click to expand...
Click to collapse
system partition is NOT checked within safestrap. Installed universal init.d but I'm out of my league on it... Init.d says stock kernel does not have support...