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
Related
Hey guys. Sorry if this has been answered before. I've looked and didn't see it in here so I figured I'd ask. I really don't want to set my phone into "custom" status in case I drop it or break it somehow Anyway, my question is will installing TWRP recovery from GooManager get me a "custom" status? Also, if I install a custom ROM, is there anyway to "trick" it into saying "Official" when I have ROMs and TWRP installed? I really wanted to install ROMs, but I'm too afraid of dropping it or something while the ROM is installed. Thanks!
I believe the "Custom" shows up periodically if you have a custom ROM installed. But really, it shouldn't bother people so much. It's pretty easy to tell if a custom ROM is installed without rebooting the phone. If Verizon cared that much, they could find out. FWIW, I didn't see "Custom" with the open padlock at boot when running stock rooted (aside from during the root process using the pre-release kernel.) It was only after installing a custom ROM that I see it periodically now.
Tortuga said:
I believe the "Custom" shows up periodically if you have a custom ROM installed. But really, it shouldn't bother people so much. It's pretty easy to tell if a custom ROM is installed without rebooting the phone. If Verizon cared that much, they could find out. FWIW, I didn't see "Custom" with the open padlock at boot when running stock rooted (aside from during the root process using the pre-release kernel.) It was only after installing a custom ROM that I see it periodically now.
Click to expand...
Click to collapse
Thanks for your reply But the reason I'm asking is because I wanted to know if there's any way to install a recovery or custom ROM while keeping the "official" status for warranty reasons. Is there?
Dark_Spark said:
Thanks for your reply But the reason I'm asking is because I wanted to know if there's any way to install a recovery or custom ROM while keeping the "official" status for warranty reasons. Is there?
Click to expand...
Click to collapse
If you were to physically damage it, you would likely still be able to boot to download mode and Odin back to 100% stock. In that case you'd have what you are asking for. I don't believe there is a way to spoof the phone into thinking it's fully official. Like I said, if Verizon/Asurion/etc care enough, they should be able to find out unless you flash back to pre-root stock. Someone else can correct me if I'm wrong.
Tortuga said:
If you were to physically damage it, you would likely still be able to boot to download mode and Odin back to 100% stock. In that case you'd have what you are asking for. I don't believe there is a way to spoof the phone into thinking it's fully official. Like I said, if Verizon/Asurion/etc care enough, they should be able to find out unless you flash back to pre-root stock. Someone else can correct me if I'm wrong.
Click to expand...
Click to collapse
Sorry to ask a million questions, but I used to have my GS4 on the stock ROM but rooted but with TWRP recovery. The statuses everywhere read as Samsung Official. I mean even in ODIN mode too. Is that what they check for in the warranty process? Or can they detect if it was just rooted or have a custom recovery and deny a warranty claim? Thanks for your patience with me.
Dark_Spark said:
Sorry to ask a million questions, but I used to have my GS4 on the stock ROM but rooted but with TWRP recovery. The statuses everywhere read as Samsung Official. I mean even in ODIN mode too. Is that what they check for in the warranty process? Or can they detect if it was just rooted or have a custom recovery and deny a warranty claim? Thanks for your patience with me.
Click to expand...
Click to collapse
Happy to help...but I really don't know what Verizon or the insurance provider would check. Some individuals within those places will probably check more thoroughly than others. But I've heard several stories of people taking their phone to Verizon, the tech seeing that it's rooted/fully custom, and replacing it anyway.
If you ever need to take it in for a warranty claim (hardware issue) I'd go back to stock first, but that's my personal opinion.
Edit: Even if it's just stock w/ root, a decently savvy tech could tell just by looking into your app list and seeing "SuperSU" or "SuperUser" or any other root-required apps.
Dark_Spark said:
Hey guys. Sorry if this has been answered before. I've looked and didn't see it in here so I figured I'd ask. I really don't want to set my phone into "custom" status in case I drop it or break it somehow Anyway, my question is will installing TWRP recovery from GooManager get me a "custom" status? Also, if I install a custom ROM, is there anyway to "trick" it into saying "Official" when I have ROMs and TWRP installed? I really wanted to install ROMs, but I'm too afraid of dropping it or something while the ROM is installed. Thanks!
Click to expand...
Click to collapse
No ,there is no method published till now. Possibility to do that is less then 20% since we cant access the hidden scripts for analysing binary counts..
Sent from my GT-I8552 using xda app-developers app
Tortuga said:
Happy to help...but I really don't know what Verizon or the insurance provider would check. Some individuals within those places will probably check more thoroughly than others. But I've heard several stories of people taking their phone to Verizon, the tech seeing that it's rooted/fully custom, and replacing it anyway.
If you ever need to take it in for a warranty claim (hardware issue) I'd go back to stock first, but that's my personal opinion.
Edit: Even if it's just stock w/ root, a decently savvy tech could tell just by looking into your app list and seeing "SuperSU" or "SuperUser" or any other root-required apps.
Click to expand...
Click to collapse
Thank you!
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.
I'm just stepping over to the big-dog conversation for a hot minute because there's just not much goin' on for sch-l435 yet (Verizon S4 Mini).
Really, I'm wanting to install ClockworkMod recovery so that I can create full backups. Some of you will get a good laugh out of this next bit ...
I bought my brand new mini, pulled it from the box, rooted, tweaked, designed, froze some bloat (TB) and then thought "I gotta back this baby up properly".
So, I downloaded a recovery install image from here: http://www.clockworkmod.com/rommanager - the version that reads Samsung Galaxy S4 (Verizon)
... but installed it using LINUX COMMANDS FOR THE WRONG DEVICE and NUKED my internal memory hahaha. I was tired. I literally copied/pasted linux commands for some obscure tablet. Total fail on my part.
She's fully repaired, courtesy of these guys: http://mobiletechvideos.mybigcommerce.com/
So, here I am and I still would like to have software that reliably clones/zips/contains an extractable backup with all of the settings and cache intact. TWRP just doesn't feel right. Something about it seems off/unreliable.
Questions I have for you, great owners of the larger, superior device
(a) is my phone formatted in the very same way as yours in terms of directories and volume info?
(b) will your version of Clockwork recovery work with the Mini?
(c) If not, is there an alternative solution that will *reliably* compress a cloned copy of my phone into a singular zip file that can later be extracted should my phone get wonky?
Shanks!
Just trying to help here .. I think people will need to know much more about the device in order to help you. I'm no dev just trying to get you closer to where you want to be.
Good luck! Hope your bootloader is unlocked
Sent from my SCH-I545 using xda app-developers app
Oh, I think there's plenty of information in my initial post to start off with, ie: what phone I'm using, what I'm intending to do, the yet-to-be-explored development status of said model (sch-l435) and my reasoning for questions to the owner's of it's big brother.
I'm game to provide further *specific* information upon request.
Whatever it takes.
RobinDean said:
Oh, I think there's plenty of information in my initial post to start off with, ie: what phone I'm using, what I'm intending to do, the yet-to-be-explored development status of said model (sch-l435) and my reasoning for questions to the owner's of it's big brother.
I'm game to provide further *specific* information upon request.
Whatever it takes.
Click to expand...
Click to collapse
don't expect alot here as this is the S4 forum...sooner or later a forum should be set for the mini
I respectfully appreciate that and should anyone know anything regarding my issue off-hand, feel free to PM me. I'll bow-out of the topic here so as to keep my intrusion to a minimum.
RobinDean said:
I respectfully appreciate that and should anyone know anything regarding my issue off-hand, feel free to PM me. I'll bow-out of the topic here so as to keep my intrusion to a minimum.
Click to expand...
Click to collapse
most likely the bootloader is locked in same manor as S4 is and you can't load a recovery on it like you tried to do.
I used linux commands initially, which is what fried the phone (got it back, good as new).
Are rooted S4 users able to install CWM Recovery independently in any way or are you guys forced to flash a ROM that happens to include it?
RobinDean said:
I used linux commands initially, which is what fried the phone (got it back, good as new).
Are rooted S4 users able to install CWM Recovery independently in any way or are you guys forced to flash a ROM that happens to include it?
Click to expand...
Click to collapse
Can't do either. ...since bootloader is totally locked down since mdk. Our only Avenue is safestrap and a few compatible roms
safestrap enabled, Hyperdrive driven
Hi guys so today I got my art unlocked m8
I tried to update but tells me there is no update and to it will check in the next 48hours
I 've been told to get rid of art room and get HTC official room but I have no idea how I've been looking over the forums and I didn't understand a thing with all the techi talking could anyone help me please kinda clueless
ibma said:
Hi guys so today I got my art unlocked m8
I tried to update but tells me there is no update and to it will check in the next 48hours
I 've been told to get rid of art room and get HTC official room but I have no idea how I've been looking over the forums and I didn't understand a thing with all the techi talking could anyone help me please kinda clueless
Click to expand...
Click to collapse
They pulled the AT&T update. Soooo....just gotta wait.....
ibma said:
I 've been told to get rid of art room and get HTC official room but I have no idea how I've been looking over the forums and I didn't understand a thing with all the techi talking could anyone help me please kinda clueless
Click to expand...
Click to collapse
I'm just guessing this is a case of autocorrect, and you mean "custom ROM" and not "art room"?
How did the custom ROM get on your phone, did you buy it that way or did someone do it for you?
The update won't install with a custom ROM, its true (at least if any system files have been altered, which is usually the case). Also, it won't install with a custom recovery. Might even send you into a bootloop and render the phone unusable.
If you want to return to a stock condition and get the update, you can either read up and learn, or run the RUU to return to stock (bootloader must be locked or you need S-off). In either case, we can help you, but need specifics on how you want to approach it.
redpoint73 said:
I'm just guessing this is a case of autocorrect, and you mean "custom ROM" and not "art room"?
How did the custom ROM get on your phone, did you buy it that way or did someone do it for you?
The update won't install with a custom ROM, its true (at least if any system files have been altered, which is usually the case). Also, it won't install with a custom recovery. Might even send you into a bootloop and render the phone unusable.
If you want to return to a stock condition and get the update, you can either read up and learn, or run the RUU to return to stock (bootloader must be locked or you need S-off). In either case, we can help you, but need specifics on how you want to approach it.
Click to expand...
Click to collapse
oh the lousy autocorrect got me.
I have no idea what im doing lol, im following a tut to install revolution hd rom and so far everything is working perfect lets see what happens after system reboot.
Can I unroot and relock bootloader after custom rom install done ?
Update: restoring old content phone seems faster with better signal, but before custom rom it had 4g signal now seems only 3g
Now that sucks boomsound enable/disbale in settings is gone!
So is extreme power saving gone from status bar
also 4g signal
Signal will not show 4g or 4glte like AT&T [email protected] [email protected]
You could relock and unroot,but then no reason to flash a custom rom.
Those two settings are in settings. And on the m8 443 euro builds some are reporting lesser [email protected]
There are AT&T ROM's available that are tailored to us AT&T/GSM networks
ibma said:
oh the lousy autocorrect got me.
I have no idea what im doing lol, im following a tut to install revolution hd rom and so far everything is working perfect lets see what happens after system reboot.
Can I unroot and relock bootloader after custom rom install done ?
Update: restoring old content phone seems faster with better signal, but before custom rom it had 4g signal now seems only 3g
Click to expand...
Click to collapse
ibma said:
Now that sucks boomsound enable/disbale in settings is gone!
So is extreme power saving gone from status bar
also 4g signal
Click to expand...
Click to collapse
ibma said:
Hi guys so today I got my art unlocked m8
I tried to update but tells me there is no update and to it will check in the next 48hours
I 've been told to get rid of art room and get HTC official room but I have no idea how I've been looking over the forums and I didn't understand a thing with all the techi talking could anyone help me please kinda clueless
Click to expand...
Click to collapse
Just use this guide to flash the ruu for 4.4.3. It only works on att m8. MAKE SURE YOU READ THE DIRECTIONS! You just need to relock your boot loader if you are not s-off
http://forum.xda-developers.com/att...-2-23-502-3-bootable-ruu-pc-required-t2860486
ibma said:
I have no idea what im doing lol, im following a tut to install revolution hd rom
Click to expand...
Click to collapse
This is the exact reason I highly discourage following step-by-step tutorials; and/or using toolkits. You are modding the phone with apparently very little understanding of what you are actually doing. Not only is this very risky, as it might result in damage to you phone. But it also leaves you completely unequipped to handle any problems.
My suggestion is to spend a few hours reading the basic information that the folks here have taken the time to compile. This isn't "techie" stuff, this is the basic information and concepts that should be understood before doing any modding of the phone. Quite simply IMO if you don't understand the basics, you have no business rooting/modding the phone.
exad's excellent guide: http://forum.xda-developers.com/showthread.php?p=52484527
FAQs: http://forum.xda-developers.com/showthread.php?t=2711073
Index of AT&T M8 resources: http://forum.xda-developers.com/showthread.php?t=2751432
Index of "international" M8 resources (most apply to AT&T version): http://forum.xda-developers.com/showthread.php?t=2694600
redpoint73 said:
This is the exact reason I highly discourage following step-by-step tutorials; and/or using toolkits. You are modding the phone with apparently very little understanding of what you are actually doing. Not only is this very risky, as it might result in damage to you phone. But it also leaves you completely unequipped to handle any problems.
My suggestion is to spend a few hours reading the basic information that the folks here have taken the time to compile. This isn't "techie" stuff, this is the basic information and concepts that should be understood before doing any modding of the phone. Quite simply IMO if you don't understand the basics, you have no business rooting/modding the phone.
exad's excellent guide: http://forum.xda-developers.com/showthread.php?p=52484527
FAQs: http://forum.xda-developers.com/showthread.php?t=2711073
Index of AT&T M8 resources: http://forum.xda-developers.com/showthread.php?t=2751432
Index of "international" M8 resources (most apply to AT&T version): http://forum.xda-developers.com/showthread.php?t=2694600
Click to expand...
Click to collapse
What i did is i unocked, rooted, then installed twrp, took nanodroid backup and installed custom rom, would it cause any issues if i factory reset the phone ?(will it reset to at&t room that came with the device)
ibma said:
What i did is i unocked, rooted, then installed twrp, took nanodroid backup and installed custom rom, would it cause any issues if i factory reset the phone ?(will it reset to at&t room that came with the device)
Click to expand...
Click to collapse
Again, you need to learn and research more before doing anything. This is another perfect example. Factory reset doesn't do anything to the ROM. All it does is wipe the user data partition, and isn't going to help your case in any way. And trying to make up your own solutions is not a good idea (but at least you thought to ask before trying it).
If the intent is to simply be on the latest 2.23 stock software, just run the RUU. You will need to relock the bootloader before RUU if you are s-on. Also, back up any personal data, as user data will be wiped by RUU.
redpoint73 said:
Again, you need to learn and research more before doing anything. This is another perfect example. Factory reset doesn't do anything to the ROM. All it does is wipe the user data partition, and isn't going to help your case in any way. And trying to make up your own solutions is not a good idea (but at least you thought to ask before trying it).
If the intent is to simply be on the latest 2.23 stock software, just run the RUU. You will need to relock the bootloader before RUU if you are s-on. Also, back up any personal data, as user data will be wiped by RUU.
Click to expand...
Click to collapse
I restored stock recovery and got bavk to att rom RUU is giving me usb error dunno why.
ibma said:
I restored stock recovery and got bavk to att rom RUU is giving me usb error dunno why.
Click to expand...
Click to collapse
Not enough info. What exactly does the error say?
S-on or S-off. Did you relock the bootloader?
Any response if you type (using adb):
adb devices
Improper HTC/ADB drivers or using Microsoft USB 3.0 drivers on USB 3 port on Windows 8.x instead of Intel USB drivers would be my first two guess. The ladder of the two issues would be most likely scenario if RUU communicates with device while booted into Android OS but fails to connect when the device is in fastboot/boot loader mode.
-Sent from a payphone...
Hello, from some what site, I heard that Safestrap 3.75 allowed to install Cyanogen Mod. I installed Safestrap 3.75, made a back up, and installed a nightly version from Cyanogen Mod
After installing CM from safestrap and rebooting, I got the yellow sign with "System Software Not Authorized By Verizon Wireless". I couldn't even go back to Safestrap to restore back. I used the NC5 build rooted with Towelroot.
From some websites, I found that I could just flash the stock firmware using Odin_v3.07 but even installing the correct "I545VZWFNC5" md5 file, I get an error saying
"Can't open the specified file. (line 1949)"
Is there a way I could apply my back up made using safestrap or just clean wipe my phone so that I can make my phone functioning? Thanks!
-Edit
I am trying again using Odin_v1.83 since I saw some posts that Odin_v3.07 had problems on my phone.
-Edit
lol Using Odin_v1.83 solved the issue. Thanks myself XD
coreymu said:
Hello, from some what site, I heard that Safestrap 3.75 allowed to install Cyanogen Mod. I installed Safestrap 3.75, made a back up, and installed a nightly version from Cyanogen Mod
After installing CM from safestrap and rebooting, I got the yellow sign with "System Software Not Authorized By Verizon Wireless". I couldn't even go back to Safestrap to restore back. I used the NC5 build rooted with Towelroot.
From some websites, I found that I could just flash the stock firmware using Odin_v3.07 but even installing the correct "I545VZWFNC5" md5 file, I get an error saying
"Can't open the specified file. (line 1949)"
Is there a way I could apply my back up made using safestrap or just clean wipe my phone so that I can make my phone functioning? Thanks!
-Edit
I am trying again using Odin_v1.83 since I saw some posts that Odin_v3.07 had problems on my phone.
-Edit
lol Using Odin_v1.83 solved the issue. Thanks myself XD
Click to expand...
Click to collapse
I don't know if you figured it out but safestrap and CM(and pretty much all other aosp roms) aren't compatible, sorry to break it to you
Quite Sad :S
Raymondlikesroot said:
I don't know if you figured it out but safestrap and CM(and pretty much all other aosp roms) aren't compatible, sorry to break it to you
Click to expand...
Click to collapse
Ahh, That's unfortunate :S
I've been so fond with CM ever since I used it on my old GS3.
I bet the smart developers are working on it right? I gotta cheer for them
coreymu said:
Ahh, That's unfortunate :S
I've been so fond with CM ever since I used it on my old GS3.
I bet the smart developers are working on it right? I gotta cheer for them
Click to expand...
Click to collapse
Unfortunately, not really. A dev called surge was making great progress but he has since left the s4. Really, our hope is some dude on the s5 forums claiming to have a universal root and bootloader unlock. However, it is becoming more and more likely that it is just hoax.
coreymu said:
Ahh, That's unfortunate :S
I've been so fond with CM ever since I used it on my old GS3.
I bet the smart developers are working on it right? I gotta cheer for them
Click to expand...
Click to collapse
Not really.
CM requires its own kernel (or at least a kernel designed to work with what ever custom features it has), safestrap is loaded AFTER the kernel so it cannot load a different one. There has been work done on this, but nothing really came of it and its closer to abandoned then working at this point.
Would there then be a way to install a lower version bootloader, which is unlockable, using safestrap so that I could install CM's kernel? Or is that impossible since NC5 is still locked?
Thanks for the information!
coreymu said:
Would there then be a way to install a lower version bootloader, which is unlockable, using safestrap so that I could install CM's kernel? Or is that impossible since NC5 is still locked?
Thanks for the information!
Click to expand...
Click to collapse
In a word - NO. Even going back to the MDK bootloader is not possible once you have taken the OTAs. And even then, MDK is still locked. The likelihood of the bootloader getting unlocked is slim and none. Kexec is the next choice and even its development has slowed as it is very hard to crack the bootloader issue.
As is often repeated, read the FAQs and search topics before posting.