Related
I was doing a stock restore on my phone (manually with fastboot as I was in Ubuntu.) and erased system and userdata and recovery, then flashed system (no need to do boot on my case) and tried recovery, but it kept giving me preflash validation failure. Now I have no stock recovery?!?! This could end up being a problem at some point, so How can I get it back. It wouldn't go as part of the stock restore scrip yet. Haven't tried RSDlite.
Bump, really need help here.
lkrasner said:
I was doing a stock restore on my phone (manually with fastboot as I was in Ubuntu.) and erased system and userdata and recovery, then flashed system (no need to do boot on my case) and tried recovery, but it kept giving me preflash validation failure. Now I have no stock recovery?!?! This could end up being a problem at some point, so How can I get it back. It wouldn't go as part of the stock restore scrip yet. Haven't tried RSDlite.
Click to expand...
Click to collapse
Dude did u try bpears one click method to restore? It works for me
Sent from my MB865 using XDA
daavvis said:
Dude did u try bpears one click method to restore? It works for me
Sent from my MB865 using XDA
Click to expand...
Click to collapse
yep, but it doesn't even try recovery at all
lkrasner said:
yep, but it doesn't even try recovery at all
Click to expand...
Click to collapse
Damn.... did u pm jim? Bet he knows... lol... no way to pull it from a different phone and push it to yours i bet either.....:/
Sent from my MB865 using XDA
Try rsdlite it might see your phone. Even if your screen is blank it still might be in fastboot mode. Rsdlite will tell you
Sent from my MB865 using Tapatalk 2
daavvis said:
Damn.... did u pm jim? Bet he knows... lol... no way to pull it from a different phone and push it to yours i bet either.....:/
Sent from my MB865 using XDA
Click to expand...
Click to collapse
all because we have a locked boot loader. now I'm even more pissed about it. I don,t think I can update to ics without it
Sent from my MB865 using xda premium
rdhoggattjr said:
Try rsdlite it might see your phone. Even if your screen is blank it still might be in fastboot mode. Rsdlite will tell you
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
my phone works fine. I just have no stock recovery on it, which may be a problem down the line. RSD does not try to flash recovery and it won't flash with manual fastboot, so I don't know how to get it back.
You mentioned manual "fastboot", now you are using the moto-fastboot utility, correct?
You might try both of these things, one at a time though:
1) Try and flash the device_tree.bin file with the moto-fastboot util, then try and flash them in this order - system.img, boot.img, recovery.img, radio.img, cdrom, preinstall.img, webtop (grfs.img)
2) Restore the backup that some others had to do to get going again after I think something similar.
http://forum.xda-developers.com/showthread.php?t=1493386
jimbridgman said:
You mentioned manual "fastboot", now you are using the moto-fastboot utility, correct?
You might try both of these things, one at a time though:
1) Try and flash the device_tree.bin file with the moto-fastboot util, then try and flash them in this order - system.img, boot.img, recovery.img, radio.img, cdrom, preinstall.img, webtop (grfs.img)
2) Restore the backup that some others had to do to get going again after I think something similar.
http://forum.xda-developers.com/showthread.php?t=1493386
Click to expand...
Click to collapse
I'll try the dev tree thing. I sort of tried the other one already, but I will do it completely too. Thanks.
jimbridgman said:
You mentioned manual "fastboot", now you are using the moto-fastboot utility, correct?
You might try both of these things, one at a time though:
1) Try and flash the device_tree.bin file with the moto-fastboot util, then try and flash them in this order - system.img, boot.img, recovery.img, radio.img, cdrom, preinstall.img, webtop (grfs.img)
2) Restore the backup that some others had to do to get going again after I think something similar.
http://forum.xda-developers.com/showthread.php?t=1493386
Click to expand...
Click to collapse
Lol..... called it!!! Lol
Sent from my MB865 using XDA
lkrasner said:
I'll try the dev tree thing. I sort of tried the other one already, but I will do it completely too. Thanks.
Click to expand...
Click to collapse
Now if you are flashing the 2.3.5 over 2.3.6 or even ICS, you still have to replace those files the same as you would for RSDlite.
Not sure if you knew that, so I thought I would just throw it out there.
daavvis said:
Lol..... called it!!! Lol
Sent from my MB865 using XDA
Click to expand...
Click to collapse
LOL!
Oh Jim, why must you know so much! If I do end up getting another phone you better join that forum t0o. I suppose I should fix this before I trade it away though.
jimbridgman said:
Now if you are flashing the 2.3.5 over 2.3.6 or even ICS, you still have to replace those image files the same as you would for RSDlite.
Not sure if you knew that, so I thought I would just throw it out there.
Click to expand...
Click to collapse
speaking of ics, and totaly off topic for here, do you think I can flash the boot.img that I got dumped from someone who had it working on my ATT phone or no. Will it hurt anything/can I get back to the original one.
lkrasner said:
LOL!
Oh Jim, why must you know so much! If I do end up getting another phone you better join that forum t0o. I suppose I should fix this before I trade it away though.
Click to expand...
Click to collapse
Let me know which phone you go to.... I am also looking for something else. I am keeping the A2, so that I can really tear it apart.
Right now it looks like the Galaxy S III will be out soon, so I might be looking into that. I will definitely NOT have another Moto phone though, after this... now if Google guts them and they actually produce a true open phone, then maybe.
jimbridgman said:
Let me know which phone you go to.... I am also looking for something else. I am keeping the A2, so that I can really tear it apart.
Right now it looks like the Galaxy S III will be out soon, so I might be looking into that. I will definitely NOT have another Moto phone though, after this... now if Google guts them and they actually produce a true open phone, then maybe.
Click to expand...
Click to collapse
I'm kind of broke so I will be trading plus maybe some cash. I have possible offers for an gs2 skyrocket and htc vivid. Both look pretty good. Development is pretty good for both but probably better for the skyrocket.
lkrasner said:
speaking of ics, and totaly off topic for here, do you think I can flash the boot.img that I got dumped from someone who had it working on my ATT phone or no. Will it hurt anything/can I get back to the original one.
Click to expand...
Click to collapse
I would say give it a try, but, I would have a computer ready that can run RSDlite.... My macbook pro has windblows 7 installed in bootcamp just for this purpose. Previous to this phone, I NEVER had a need to actually BOOT windblows (never had bootcamp working), I have it running in VMs on my ubuntu and my macs/hackintoshes, for other things.
YOU MUST NOT RUN RSDLITE IN VMWARE!!!! I tried and it was dismal, I had to exchange that phone it was so bad, that it would not even power on, and RSDlite said success.
jimbridgman said:
I am also looking for something else.
Right now it looks like the Galaxy S III will be out soon, so I might be looking into that. I will definitely NOT have another Moto phone though
Click to expand...
Click to collapse
Same here...was considering the HTC One X but man, the non-removable battery and lack of microSD slot are deal breakers for me since 12gb of useable space just won't cut it. So i'm holding out hope the SGS3 comes out here by July and is around the $250 price point on contract.
916x10 said:
Same here...was considering the HTC One X but man, the non-removable battery and lack of microSD slot are deal breakers for me since 12gb of useable space just won't cut it. So i'm holding out hope the SGS3 comes out here by July and is around the $250 price point on contract.
Click to expand...
Click to collapse
Hey, haven't seen you in a while...
I was thinking the exact same thing. The one x just is not doing it for me... all in the cloud.... LOL... that is the next crap carriers are going to sell us, cloud space and a more expensive data plan for that.
Yeah the gs III is it for me.. I hope it is 299 or less on contract.
Sent from my MB865 using xda premium
jimbridgman said:
Hey, haven't seen you in a while...
I was thinking the exact same thing. The one x just is not doing for me... all in the cloud.... LOL... that is the next crap carriers are going to sell us, cloud space and a more expensive data plan for that.
Yeah the gs III is it for me.. I hope it is 299 or less on contract.
Click to expand...
Click to collapse
Emotions were running high there for a bit so I had to take a break and let things simmer down. As popular as the SGS3 is, the dev for it should be awesome...especially with guys like you owning it It will be my first high end Android device so i'm hoping it lives up to the hype
Hey, so lkranser and I have made a great discovery tonight.
lkranser's recovery partition was erased due to some of my advice to him.
So I cat'd my recovery partition (/dev/block/mmcblk1p16) into a recovery.img file, and he was able to cat that recovery image file that I created into his recovery partition.
So now the question is how can we use this to our advantage and get CWM on /dev/block/mmcblk1p16, and get it to come up with holding both volume buttons and the power button, as this is the way it works on every other phone.
Idea guys, this thread is a place to throw out some serious ideas to get this to work. Please don't ask for any how-to's for this here.
jimbridgman said:
Hey, so lkranser and I have made a great discovery tonight.
lkranser's recovery partition was erased due to some of my advice to him.
So I cat'd my recovery partition (/dev/block/mmcblk1p16) into a recovery.img file, and he was able to cat that recovery image file that I created into his recovery partition.
So now the question is how can we use this to our advantage and get CWM on /dev/block/mmcblk1p16, and get it to come up with holding both volume buttons and the power button, as this is the way it works on every other phone.
Idea guys, this thread is a place to throw out some serious ideas to get this to work. Please don't ask for any how-to's for this here.
Click to expand...
Click to collapse
a few things.
1. it was not anything you did that made me wipe recovery, it was just me being a complete idiot
2. basically I think we need to figure out how to modify what you cat'd over. then we can pull an image from a similar device that has a true cwm recovery and edit what we need to like the specific partitions in order for it to work on our phone. then we can just cat it over and bingo! working full cwm.
3. why is it that stupid things I do always end up leading to great discoveries on here. this is like the 3rd time it has happened.
so any ideas on how to mount that file in a way we can actually look at it.
---------- Post added at 09:39 PM ---------- Previous post was at 09:22 PM ----------
Some more stuff I found: http://www.clockworkmod.com/rommanager
That has official cwm recovery builds for all supported devices. many have images, I think all the ones with unlocked bootloaders. those images would be flashed with fastboot, or probably could be cat'd over like we did.
others have flashable zips (all the moto devices) and i think those are all the ones with lockked bootloaders. I don't have tie to dig into what they really do right now, but i appears that they just copy some files for recovery to /etc and other places suggesting those devices have a different recovery method
I still think the biggest priority is figuring out how to see the contents of the images with our recovery stuff and those for other devices.
I can tell you what happened to me the other day, I was getting ready to to use RSD as I was bootlooped and went to boot into fastboot but accidentally booted into BP tools and when it booted it booted to CWM. So I tried it a couple of times with the same exact results. Fluke, IDK ??? Havent been in trouble since to try it again!
JRW 28 said:
I can tell you what happened to me the other day, I was getting ready to to use RSD as I was bootlooped and went to boot into fastboot but accidentally booted into BP tools and when it booted it booted to CWM. So I tried it a couple of times with the same exact results. Fluke, IDK ??? Havent been in trouble since to try it again!
Click to expand...
Click to collapse
what is BP tools even
Sent from my MB865 using xda premium
lkrasner said:
what is BP tools even
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I've wondered the same thing????
JRW 28 said:
I've wondered the same thing????
Click to expand...
Click to collapse
it never does anything for me. it just boots normally into the os. that is why it is going to cwm if you have it set on boot. it did that for me too
lkrasner said:
it never does anything for me. it just boots normally into the os. that is why it is going to cwm if you have it set on boot. it did that for me too
Click to expand...
Click to collapse
Yea but even on a normal boot I could never get past the red moto screen, tried several times hopi g to get into CWM and not have to RSD back.
Just wierd that normal boot wouldn't work but BP tools did?
The only difference I could see is an app called CQATest in the drawer. Has many different tests available. About 50+
Sent from my MB865 using xda premium
made a major breakthrough. my internet is down though so I can't really keep working on it or post details, but I should by tomorrow. stay tuned. stupid Comcast.
EDIT: I'm back up. So basically I figured out how to separate the kernel and ramdisk of both our boot and recovery images. it did not work to re-combine them, but it may still be useful for building cyanogenmod to be able to have our straight kernel. PM me if you wan't more detail.
That said, it did not do exactly what I wanted, but I think at this point we should be able to simply build cwm according to the guides for it. I am doing it right now, and it is in the final build process, so I will let you know how it all turns out.
So, I got it built successfully, but i won't boot. it seems to be the same problem I had before with the stock one. it is way smaller when It is all put back together. around 5 MB instead of 9.
Any ideas why? it appears motorola does not use the standard recovery stuff
lkrasner said:
made a major breakthrough. my internet is down though so I can't really keep working on it or post details, but I should by tomorrow. stay tuned. stupid Comcast.
EDIT: I'm back up. So basically I figured out how to separate the kernel and ramdisk of both our boot and recovery images. it did not work to re-combine them, but it may still be useful for building cyanogenmod to be able to have our straight kernel. PM me if you wan't more detail.
That said, it did not do exactly what I wanted, but I think at this point we should be able to simply build cwm according to the guides for it. I am doing it right now, and it is in the final build process, so I will let you know how it all turns out.
Click to expand...
Click to collapse
Yeah I already have a perl script to do all the separation, but it still puts the kernel into several files, and not just single kernel file with a few separate .ko files.... If you found something that I haven't, then that is awesome.
Here is the script that I use to pull it out of the boot.img:
https://dl.dropbox.com/u/45576654/unpack-bootimg.pl
lkrasner said:
So, I got it built successfully, but i won't boot. it seems to be the same problem I had before with the stock one. it is way smaller when It is all put back together. around 5 MB instead of 9.
Any ideas why? it appears motorola does not use the standard recovery stuff
Click to expand...
Click to collapse
I suspected that might be the case.
jimbridgman said:
I suspected that might be the case.
Click to expand...
Click to collapse
any ideas why.
Sent from my MB865 using xda premium
jimbridgman said:
Yeah I already have a perl script to do all the separation, but it still puts the kernel into several files, and not just single kernel file with a few separate .ko files.... If you found something that I haven't, then that is awesome.
Here is the script that I use to pull it out of the boot.img:
https://dl.dropbox.com/u/45576654/unpack-bootimg.pl
Click to expand...
Click to collapse
mine gave me a ramdisk.cpio.gz and a kernel.gz, I didn't extract that. it was also a pearl script, so probably the same one.
Sent from my MB865 using xda premium
I know I have posted here way to many times. But I want to get this to work.
It seems motorola has done more weird **** to their recovery partitions. Normally you can use certain scripts and binaries to separate a boot or recovery image (they follow the same format) into the ramdisk and kernel. That SHOULD be all that is in them. you can then modify the ramdisk to your liking, or use the kernel with cwm or the like to make it work. However it seems there is more to our image than just the ramdisk and kernel. when I extract them and repack them it seems to work fine, but the result is 5.5MB instead of 9.4MB with no modifications.
Does anyone have any idea what the deal is with that? I think if we can figure out that part we should be able to get a true custom recovery.
P.S. are you sure we cannot replace our boot.img with this same copying method? That is if we could even figure out how to modify it. Is there a hardbrick risk in trying? if so, Any volunteers?
EDIT: so our boot image will unpack and repack to the same exact size, so I think that means we could theoretically edit the ramdisk if that would do any good. the question still remains whether the phone checks its signature on boot or only upon flash
Anyway to test if it checks on boot or flash?
Sent from my MB865 using xda premium
Harrison85 said:
Anyway to test if it checks on boot or flash?
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I can make a small change that would make it un verified then someone could copy it over and see if it boots. the problem is I am not 100% sure we would be able to restore to the original if it would not boot. I am 99% sure we would be fine, but I don't want to risk bricking completely. My guess is jim will know if it is safe to test or even worth trying, but if you want to be the guinea pig just tell me and I'll send you instructions.
By all means throw Me instructions and I will give it a shot right now
Sent from my MB865 using xda premium
Nevermind. I was sort of wrong. Both images separate just fine and can be recombined, but extracting the ramdisk seems to not extract the whole thing, it is much smaller when it is repacked. therefor you cannot really edit it at all.
Any ideas why?? I think it is just Moto being a pain in the ass as usual.
lkrasner said:
Any ideas why?? I think it is just Moto being a pain in the ass as usual.
Click to expand...
Click to collapse
That is it in a nutshell. They pack their boot image in a different way from all other phone manufacturers, and not in a standard way for android. That is why Moto has their own "special" non-standard bootloader. They use a bitblast to package the boot image files, on top of the standard tgz, so the important files are "zip blasted" on top of the others in "superbit blocks", so there is not much we can do, unless we can de-a-line them, but that is not something I even want to start poking at.
This the only phone I've ever had a problem with, and I am asking for some help from the community.
I've got a Cricket HTC One SV. K2PLC_CL. Android 4.2.2, which should be Jellybean.
I just wanted to get root. I know there aren't any custom ROMs (what I wouldn't give to remove all the bloatware, though...)
I followed a few guides that I'm sure everyone's looked at. My bootloader IS unlocked. When I tried flashing a recovery (I have two or three to try, one's even labelled for Cricket. They're CWM, though), I was unable to boot into it to install Superuser. Since then, I've earned the "TAMPERED" flag.
Have I done something terribly wrong? Can someone please instruct me on how to get root, and to fix my recovery?
Since I somehow managed to fail, I would be extremely appreciative if someone would be so kind as to spell it out, or just give me step-by-step instructions.
Since booting into recovery, my phone freezes if I shut it down while it's plugged into the charger... Oddly enough.
It's not your fault, it's because the new hboot, which came with 422 update!
Follow the link in my singnature, you will find there a working recovery and a SuperSu.zip for 422.
old.splatterhand said:
It's not your fault, it's because the new hboot, which came with 422 update!
Follow the link in my singnature, you will find there a working recovery and a SuperSu.zip for 422.
Click to expand...
Click to collapse
Ahh, thank you so much.
I'm looking right now, and unfortunately, I noticed the TWRP recovery isn't for my SV. Is there a K2PLC_CL around, or am I able to use one of those?
AnalogConspiracy said:
Ahh, thank you so much.
I'm looking right now, and unfortunately, I noticed the TWRP recovery isn't for my SV. Is there a K2PLC_CL around, or am I able to use one of those?
Click to expand...
Click to collapse
it still works for your device, go ahead and use it
Sent from my C525c using Tapatalk
russellvone said:
it still works for your device, go ahead and use it
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Will do, thank you very much. I'll let you know how it goes!
And I can flash my superuser through their recovery, correct?
AnalogConspiracy said:
Will do, thank you very much. I'll let you know how it goes!
And I can flash my superuser through their recovery, correct?
Click to expand...
Click to collapse
use superSU.......but yes
Sent from my C525c using Tapatalk
russellvone said:
use superSU.......but yes
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Thanks everyone, my phone has now been rooted!
However, I'd like to use a couple of apps, and was promptly alerted that I need to obtain S-OFF. I've been looking at Rumrunner... Should I use it?
Plug phone in while it's charged on, USB debug is on, and let it do it's thing?
edit: I ran it, and it looked great... But at the end, it gave a line along the lines of.
[TTTTT*******] or something.
I booted into Hboot, it's still on.
AnalogConspiracy said:
Thanks everyone, my phone has now been rooted!
However, I'd like to use a couple of apps, and was promptly alerted that I need to obtain S-OFF. I've been looking at Rumrunner... Should I use it?
Plug phone in while it's charged on, USB debug is on, and let it do it's thing?
edit: I ran it, and it looked great... But at the end, it gave a line along the lines of.
[TTTTT*******] or something.
I booted into Hboot, it's still on.
Click to expand...
Click to collapse
Make sure its the universal one, and insure you do not have any password set on your phone. Any kind of lockscreen security needs to be disabled. Basically, you need to be able to access your phone without the hassle of something preventing it. This stuff will disrupt the process.
Sent from my C525c using Tapatalk
Modding.MyMind said:
Make sure its the universal one, and insure you do not have any password set on your phone. Any kind of lockscreen security needs to be disabled. Basically, you need to be able to access your phone without the hassle of something preventing it. This stuff will disrupt the process.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Also (I think) make sure the fast boot option in Settings > Power is unchecked
palmtree5 said:
Also (I think) make sure the fast boot option in Settings > Power is unchecked
Click to expand...
Click to collapse
Thank you for putting up with my ignorance thus far, guys.
However, I:
- Am running Universal Rumrunner.
- Have already un-checked the Fastboot option.
- Have no current lock on my phone. Security>Screen Lock>None
- Have USB debug enabled.
Edit: - Have HTC Sync removed.
- Have no firewall, granting access to sojo.
- Have granted superuser/root access to ADB.
In my previous post, I stated I ran Rumrunner. It was with the aforementioned settings.
I did make sure to do this before touching anything.
This is why I'm stumped.
Is there any information I can provide that might assist you guys?
AnalogConspiracy said:
Thank you for putting up with my ignorance thus far, guys.
However, I:
- Am running Universal Rumrunner.
- Have already un-checked the Fastboot option.
- Have no current lock on my phone. Security>Screen Lock>None
- Have USB debug enabled.
Edit: - Have HTC Sync removed.
- Have no firewall, granting access to sojo.
- Have granted superuser/root access to ADB.
In my previous post, I stated I ran Rumrunner. It was with the aforementioned settings.
I did make sure to do this before touching anything.
This is why I'm stumped.
Is there any information I can provide that might assist you guys?
Click to expand...
Click to collapse
use an unsecure kernel
Sent from my C525c using Tapatalk
russellvone said:
use an unsecure kernel
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
I'll have to look for one.
However, I managed to get Rumrunner working properly.
What did I do?
... I re-downloaded the same universal version that I have. Then, I ran it.
I don't know what wasn't making it function properly in the first place, but it has this time.
My HTC One SV from Cricket is officially S-OFF.
Thank you very much for your help, and contributing to the education of my phone.
Hi I'm new here to kind of been into rooting my phones since I heard if it I've always figured it out on my own but the HTC sv im stumped I'd like to root and unlock who knows what from there but I've had this phone for a while can anyone help?
Sent from my C525c using xda app-developers app
---------- Post added at 07:47 AM ---------- Previous post was at 07:43 AM ----------
And if anyone knows anything about LG optimous 9 I have one them never turned it on yet need a battery are they any better cause I like the HTC but I'd like to throw it as far as possible love the phone but needs to come unlocked
Sent from my C525c using xda app-developers app
wytaske34 said:
Hi I'm new here to kind of been into rooting my phones since I heard if it I've always figured it out on my own but the HTC sv im stumped I'd like to root and unlock who knows what from there but I've had this phone for a while can anyone help?
Sent from my C525c using xda app-developers app
---------- Post added at 07:47 AM ---------- Previous post was at 07:43 AM ----------
And if anyone knows anything about LG optimous 9 I have one them never turned it on yet need a battery are they any better cause I like the HTC but I'd like to throw it as far as possible love the phone but needs to come unlocked
Sent from my C525c using xda app-developers app
Click to expand...
Click to collapse
HTC One SV:
First off, make sure your bootloader is unlocked.
www.htcdev.com/bootloader/
You do have to make an account. Please do so, and follow their instructions to the letter.
Second. Flash TWRP recovery, as seen: http://forum.xda-developers.com/showthread.php?t=2292432 (This link is also in old.splatterhand's signature.)
Third, run Rumrunner Universal -- the latest version, and then you should be set.
As for the requirements -- you will see them as you seek these topics. Everything is literally on that XDA link I sent -- it's also in old.splatterhand's signature, again.
wytaske34 said:
Hi I'm new here to kind of been into rooting my phones since I heard if it I've always figured it out on my own but the HTC sv im stumped I'd like to root and unlock who knows what from there but I've had this phone for a while can anyone help?
Sent from my C525c using xda app-developers app
---------- Post added at 07:47 AM ---------- Previous post was at 07:43 AM ----------
And if anyone knows anything about LG optimous 9 I have one them never turned it on yet need a battery are they any better cause I like the HTC but I'd like to throw it as far as possible love the phone but needs to come unlocked
Sent from my C525c using xda app-developers app
Click to expand...
Click to collapse
You have a K2_CL. I see that in your comment signature. Make sure you DO NOT use anything that pertains to K2_PLC_CL, K2_UL, and/or K2_U! Their partitions are different and unless you know what you are doing you may bring about some serious issues down the road lol.
Ultimately, everything you need you can find in old.splatterhands index as already mentioned. The custom recovery must pertain to K2_CL or it will not work.
Step one: unlock bootloader
Step two: flash custom recovery
Step three: make a backup using custom recovery
Step four: flash a flashable.zip with supersu to gain root.
Step five: the rest is up to you based on your wants, needs, and desires.
If you are not sure of something, please ask!
Sent from my C525c using Tapatalk
I S-offed my device just to notice I have a dead pixel.
Is there an RUU I can flash to get S-On back or can I just do Fastboot OEM lock?
Thanks.
http://forum.xda-developers.com/showpost.php?p=51703697&postcount=14
I too am trying to figure out how to S-On my device. Like you, I noticed a defect after the fact.
Currently there is no RUU available. However there is a thread in the android development section that contains boot, recovery and hboot image files, along with a system dump which you could technically push back onto your device to get a stock system folder.
I'm currently trying to figure out if flashing hboot.IMG is a good or bad idea, or if it will even result in S-On.
Sent from my HTC6525LVW using Tapatalk
Div033 said:
I too am trying to figure out how to S-On my device. Like you, I noticed a defect after the fact.
Currently there is no RUU available. However there is a thread in the android development section that contains boot, recovery and hboot image files, along with a system dump which you could technically push back onto your device to get a stock system folder.
I'm currently trying to figure out if flashing hboot.IMG is a good or bad idea, or if it will even result in S-On.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
exactly. i now with the RUU i can get fully stock though. i am scared to go back to the verizon store with recovery installed on my device and all the phone people are telling me to go to the store. what i need is stock recovery but i dunno.
The people at the store aren't that intelligent lol... Most don't even know how to boot to recovery in the first place...
You will be fine if you go in and show them the dead pixel. They will replace it on the spot for you.
Sent from my HTC6525LVW using Tapatalk
---------- Post added at 12:51 AM ---------- Previous post was at 12:39 AM ----------
And look what I found...
This guy over here - http://forum.xda-developers.com/showthread.php?t=2710503 made a modified hboot that APPEARS as s-on so if you flash that then it will hide that fact that you are actually s-off and in the crazy chance that a vzw employee checks they will be tricked into thinking you are still s-on.
Sent from my HTC6525LVW using Tapatalk
http://forum.xda-developers.com/showthread.php?t=2475216
this is the command for s-on
fastboot oem writesecureflag 3
Div033 said:
I too am trying to figure out how to S-On my device. Like you, I noticed a defect after the fact.
Currently there is no RUU available. However there is a thread in the android development section that contains boot, recovery and hboot image files, along with a system dump which you could technically push back onto your device to get a stock system folder.
I'm currently trying to figure out if flashing hboot.IMG is a good or bad idea, or if it will even result in S-On.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
David 617 said:
The people at the store aren't that intelligent lol... Most don't even know how to boot to recovery in the first place...
You will be fine if you go in and show them the dead pixel. They will replace it on the spot for you.
Sent from my HTC6525LVW using Tapatalk
---------- Post added at 12:51 AM ---------- Previous post was at 12:39 AM ----------
And look what I found...
This guy over here - http://forum.xda-developers.com/showthread.php?t=2710503 made a modified hboot that APPEARS as s-on so if you flash that then it will hide that fact that you are actually s-off and in the crazy chance that a vzw employee checks they will be tricked into thinking you are still s-on.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
ive had bad luck with the store in my area... there is a jackass who knows about that kind of stuff... so im gonna have to go else where but im pretty sure im gonna do what your saying.
David 617 said:
The people at the store aren't that intelligent lol... Most don't even know how to boot to recovery in the first place...
You will be fine if you go in and show them the dead pixel. They will replace it on the spot for you.
Sent from my HTC6525LVW using Tapatalk
---------- Post added at 12:51 AM ---------- Previous post was at 12:39 AM ----------
And look what I found...
This guy over here - http://forum.xda-developers.com/showthread.php?t=2710503 made a modified hboot that APPEARS as s-on so if you flash that then it will hide that fact that you are actually s-off and in the crazy chance that a vzw employee checks they will be tricked into thinking you are still s-on.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
YMMV - verizon stores in my area are really stubborn when replacing a phone comes into question. One even tried to tell me i was still rooted on a phone that wasn't currently. And by 'on the spot' you mean you walk out with a new phone? I've never had that happen.
ElChibo said:
ive had bad luck with the store in my area... there is a jackass who knows about that kind of stuff... so im gonna have to go else where but im pretty sure im gonna do what your saying.
Click to expand...
Click to collapse
Abe21599 said:
YMMV - verizon stores in my area are really stubborn when replacing a phone comes into question. One even tried to tell me i was still rooted on a phone that wasn't currently. And by 'on the spot' you mean you walk out with a new phone? I've never had that happen.
Click to expand...
Click to collapse
Wow that sucks... I guess I'm just lucky then. I always make sure to schmooze them up before I ask for anything. (Same thing on the phone. I'm always super nice to them. The service reps have the power to do anything on your account. Last week I got a $100 credit on my acct just because I asked.)
Sent from my HTC6525LVW using Tapatalk
I just exchanged the phone today without relocking. It's going back to the mfr anyway so I'm sure they'll relock it or whatever. Had no issues but the people at the store I go to are really damn cool.
Sent from my HTC6525LVW using Tapatalk
David 617 said:
Wow that sucks... I guess I'm just lucky then. I always make sure to schmooze them up before I ask for anything. (Same thing on the phone. I'm always super nice to them. The service reps have the power to do anything on your account. Last week I got a $100 credit on my acct just because I asked.)
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
yeah. this guy is just a snob. like anyone who goes in there he goes into the bootloader or recovery to check if they have a custom recovery.
my friend who had a prepaid device had to freaking do that and that really pissed me off. but yeah. ill try go late in the day. i dont think he works that late.
So I've been working on this all night last night and all day today.
The issue- phone will boot, get to the red Verizon boot screen, sit there for approximately 45-60 seconds, then go to the lock screen. Within a couple of seconds, Then a message pops up that says process com.android.phone has stopped, then the phone reboots.
What I've tried- flashing various Vralec boot strings through Odin 3.2 and 1.3. Also tried five different stock ROMs and a CF Auto Root, in the hopes unlocking the bootloader would allow me to get a ROM to flash. Each and every one of these things has had an AUTH fail in Odin. Can anyone help me please?
I've also googled stuck red verizon screen, verizon s3 boot loop, process com.android.phone has stopped. None of the solutions I've found have been helpful, and are usually what led to the actions tried above. I believe I've encountered this before, but I checked my post history and wasn't able to find a thread, so I assume I found the solution on my own the last time.
Any assistance would be greatly appreciated!
What software version are you running? What baseband?
Sent from my SCH-I535 using Tapatalk
Hybridnoob said:
What software version are you running? What baseband?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
This is a warranty replacement from Verizon. Since I can't get it to boot, is there an alternative method to find those versions?
I have another S3, replaced less than a month ago, so I would assume they are the same software version and basebands, and that one is running 4.4.2 and I535OYUDNE1
The soft bricked, boot loop, S3 belongs to my girlfriend.
Flashing other ROMs on the S3 4.3 and newer will brick it. The bootloader was never unlocked. I'll try to find the thread describing the issue and post it here.
Sent from my SCH-I535 using Tapatalk
---------- Post added at 01:40 PM ---------- Previous post was at 01:37 PM ----------
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my SCH-I535 using Tapatalk
---------- Post added at 01:40 PM ---------- Previous post was at 01:40 PM ----------
I hope that helps.
Sent from my SCH-I535 using Tapatalk
Hybridnoob said:
Flashing other ROMs on the S3 4.4 and newer will brick it. The bootloader was never unlocked. I'll try to find the thread describing the issue and post it here.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Flashing the ROMS through Odin failed every time, and none of that was done until AFTER the phone went in to a boot loop. It was already soft bricked, so I tried various different methods. Now I know, for future reference, that attempting to flash ROMs without unlocking the bootloader will brick it. Good to know.
If I can work around the Odin failed authorization, I believe I can flash a stock ROM to the phone and be all right, OR if someone can tell me how to unlock the bootloader, I should be able to flash a custom ROM, correct? It seems that the boot partition permissions were changed and have now affected the boot process, from what I've been reading.
Hybridnoob said:
Flashing other ROMs on the S3 4.3 and newer will brick it. The bootloader was never unlocked. I'll try to find the thread describing the issue and post it here.
Sent from my SCH-I535 using Tapatalk
---------- Post added at 01:40 PM ---------- Previous post was at 01:37 PM ----------
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my SCH-I535 using Tapatalk
---------- Post added at 01:40 PM ---------- Previous post was at 01:40 PM ----------
I hope that helps.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Reading up on your link now, will let you know result. Thank you!
edit: ok, I looked at the download mode accessible link, and that is one I'd tried before. Flashed the ALL I535 .tar and ran in to the auth fail message on odin. Going to try the other method now.
No one has been able to unlock the bootloader since 4.3. I doubt anyone's really trying now because the phone is older. Sorry man.
Sent from my SCH-I535 using Tapatalk
Hybridnoob said:
No one has been able to unlock the bootloader since 4.3. I doubt anyone's really trying now because the phone is older. Sorry man.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I got towelroot to work to get my S3 to be able to install SuperSU and then Titanium Backup, but haven't found a bootloader unlock either. So, the phone is pretty much bricked?
jester369 said:
I got towelroot to work to get my S3 to be able to install SuperSU and then Titanium Backup, but haven't found a bootloader unlock either. So, the phone is pretty much bricked?
Click to expand...
Click to collapse
Bricked no, if your able to install apps it's far from bricked. He is correct however once the bootloader is locked your pretty much stuck. Replacements directly from verizon are coming back with 4.4.2 installed.
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Unless you can find a fully stock ROM to flash via Odin, you may be in trouble. Unlocking the bootloader isn't an option. Without seeing your phone, I won't say it's bricked though.
Sent from my SCH-I535 using Tapatalk
Hybridnoob said:
Unless you can find a fully stock ROM to flash via Odin, you may be in trouble. Unlocking the bootloader isn't an option. Without seeing your phone, I won't say it's bricked though.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
As I just stated in the post above yours if you can install apps the phone isn't bricked. Bootloader unlocking on the S3 with 4.3 or 4.4 is merely a possibility but probably unlikely
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Hybridnoob said:
No one has been able to unlock the bootloader since 4.3. I doubt anyone's really trying now because the phone is older. Sorry man.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
All right, tried the recover from computer, it's to recover a bricked bootloader. My bootloader isn't bricked, it's the actual ROM that's non functional. So that didn't help. Just need a stock ROM to flash to the phone, can still get to download mode, which connects to Odin, no problem, can also get to stock recovery, Volume Up, Menu, power. Just need a stock ROM that works, or a way to get whatever authorization Odin or the phone wants in order to flash a boot chain and stock ROM. (I do know now not to flash a custom ROM, thank you for that!)
ShapesBlue said:
Bricked no, if your able to install apps it's far from bricked. He is correct however once the bootloader is locked your pretty much stuck. Replacements directly from verizon are coming back with 4.4.2 installed.
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
Sorry, some clarification. I have TWO S3s, MY S3 is fine, and can install apps. The girlfriend's S3 is soft bricked and in a boot loop. Bootloader is fine, download mode is fine. Just hangs on red Verizon boot screen, when it gets to lock screen says process com.android.phone has stopped and reboots.
Hybridnoob said:
Unless you can find a fully stock ROM to flash via Odin, you may be in trouble. Unlocking the bootloader isn't an option. Without seeing your phone, I won't say it's bricked though.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Been trying to find a fully stock ROM and been unsuccessful. Any I've found have failed in Odin and failed to flash in stock recovery mode, something about a certificate failure.
jester369 said:
Sorry, some clarification. I have TWO S3s, MY S3 is fine, and can install apps. The girlfriend's S3 is soft bricked and in a boot loop. Bootloader is fine, download mode is fine. Just hangs on red Verizon boot screen, when it gets to lock screen says process com.android.phone has stopped and reboots.
Click to expand...
Click to collapse
I definitely would not call that soft bricked. Can you get into recovery and try clearing cache and reboot? Worst case, factory reset from recovery and you should be good to go.
Sent from my SCH-I535 using Tapatalk
Hybridnoob said:
I definitely would not call that soft bricked. Can you get into recovery and try clearing cache and reboot? Worst case, factory reset from recovery and you should be good to go.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I can get in to recovery, I've tried clearing cache, factory reset, no dice. Exact same thing.
have you tried using odin or kies to just flash the stock NE1 4.4.2? youll have to reroot with towelroot afterwards but atleast the phone will be functional. as for the bootloader, sounds like its locked anyways so it wont be no worse than the shape youre in already.
4.4 and 4.3 Sticky Roll-Up Thead
http://forum.xda-developers.com/showthread.php?t=2639337
TouchWiz 4.4 Download List
http://forum.xda-developers.com/gal...4-download-list-7-10-14-t2812189/post54062704
VRUDNE1 (Android 4.4.2 - Kit Kat) No-Wipe Factory Image
http://forum.xda-developers.com/showthread.php?t=2795659
-somebody- said:
have you tried using odin or kies to just flash the stock NE1 4.4.2? youll have to reroot with towelroot afterwards but atleast the phone will be functional. as for the bootloader, sounds like its locked anyways so it wont be no worse than the shape youre in already.
Click to expand...
Click to collapse
I have tried that, I believe I haven't been able to find a stock 4.4.2 ROM though. I'm fine with rebooting and re rooting, that's not my concern, even if I can't root, I don't care about that. Could you point me to a solid stock ROM image?
The images I've tried, numerous labeled stock ROMs, and, out of desperation last night, two custom ROMs. Through either recovery mode, or Odin, all failed, through recovery it was a certificate error, and through Odin it was an authorization error. AUTH FAIL, specifically.
jester369 said:
I have tried that, I believe I haven't been able to find a stock 4.4.2 ROM though. I'm fine with rebooting and re rooting, that's not my concern, even if I can't root, I don't care about that. Could you point me to a solid stock ROM image?
The images I've tried, numerous labeled stock ROMs, and, out of desperation last night, two custom ROMs. Through either recovery mode, or Odin, all failed, through recovery it was a certificate error, and through Odin it was an authorization error. AUTH FAIL, specifically.
Click to expand...
Click to collapse
that last link i believe is the actual tar file for NE1 if i remember correctly, i used kies when i updated mine and i didnt encounter any errors. did you delete the .md5 so it was just .tar (not .tar.md5) before trying it in odin? i know most people prefer odin over kies but if youre having this many problems kies is worth a shot.
worst case i can upload the one i have
-somebody- said:
that last link i believe is the actual tar file for NE1 if i remember correctly, i used kies when i updated mine and i didnt encounter any errors. did you delete the .md5 so it was just .tar (not .tar.md5) before trying it in odin? i know most people prefer odin over kies but if youre having this many problems kies is worth a shot.
worst case i can upload the one i have
Click to expand...
Click to collapse
I will try that and report back. Thank you!