Related
MyTouch 4g, perm-rooted, S-OFF. I pushed a custom kernel (for overclocking). The device is fine. T-mobile tried to push an update (which kept nagging me), so I eventually applied it. When I did it failed to reboot. Good job, T-mobile.
That would have been fine except that I also had to return the computer I did this all on to work. I've created a new system and ADB only appears to detect the device when it's in recovery mode. I'm running gentoo, so I had to hack the udev rules myself. The identifiers match lsusb, but recovery is the only time I don't get a blank console under "List of devices attached".
/etc/udev/rules.d/50-android.rules
SUBSYSTEMS=="usb, ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0c94", OWNER=="poseidon1157" #Normal
SUBSYSTEMS=="usb, ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0c96", OWNER=="poseidon1157" #Recovery
SUBSYSTEMS=="usb, ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0fff", OWNER=="poseidon1157" #Fastboot
lsusb:
Bus 001 Device 018: ID 0bb4:0fff High Tech Computer Corp.
OR
Bus 001 Device 018: ID 0bb4:0c94 High Tech Computer Corp.
OR
Bus 001 Device 018: ID 0bb4:0c96 High Tech Computer Corp.
In recovery mode:
List of devices attached
HT0... recovery
else
List of devices attached
So wtf?
Ultimately I want to push cyanogenmod to the phone, but I can't do that very well if it's not detecting the phone.
Please help. I really need that thing. Both for work and for my personal life.
I forgot that you use a separate fastboot binary. Looking for that now. Did they remove that from the default sdk?
poseidon1157 said:
MyTouch 4g, perm-rooted, S-OFF. I pushed a custom kernel (for overclocking). The device is fine. T-mobile tried to push an update (which kept nagging me), so I eventually applied it. When I did it failed to reboot. Good job, T-mobile.
Click to expand...
Click to collapse
Um, you blame T-Mobile for hacking your phone and then f***ing it up by applying a stock update to a non-stock phone? What was the update, 2.2.1? What kernel did you have on it? Anything other than a custom kernel?
Try applying this in Recovery.
This is T-Mobile's fault how? You failed, not them. Thumbs down to you.
Part Four said:
This is T-Mobile's fault how? You failed, not them. Thumbs down to you.
Click to expand...
Click to collapse
+ Juan to this post.
if you can get into recovery just do a nandroid restore.
if you can still get into Bootloader store the PD15IMG and start over fresh.
Wow most ppl complain about tmo not sending out updates! This is a first!
Sent from my HTC Glacier
lisap006 said:
Wow most ppl complain about tmo not sending out updates! This is a first!
Sent from my HTC Glacier
Click to expand...
Click to collapse
Lmfao so so tru
CM7 wtf else....
lisap006 said:
Wow most ppl complain about tmo not sending out updates! This is a first!
Sent from my HTC Glacier
Click to expand...
Click to collapse
Good point! another reason to rename this thread "Damnit, my own hands..."
Figures. I post a technical problem and everyone chimes in on something I said while frustrated. Not the problem. Thank you very much setzer for the recommended fix.
Personally, I would greatly appreciate it if none of the rest of you replied to my posts. Ever. Again.
And for the record you're right, I shouldn't have applied the update. Repeated attempts to find the update file failed, the notification stayed there, and my clockworkmod backup apparently disappeared with my photos and media and so I was stuck with a system I couldn't recover.
So did it work? I am not sure why you applied it in first place as most do warn and why would people accept stock OTA on custom setup is beyond me. Hopefully it works by restoring the PD15IMG or you have to social TMo to get replacement.
Sent from my HTC Glacier
Hey guys, is there a way to turn off system updates so this doesn't happen to me when my girlfriend had my phone lol.
Sent from my HTC Glacier using XDA App
Essenar said:
Hey guys, is there a way to turn off system updates so this doesn't happen to me when my girlfriend had my phone lol.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
honestly wait till after the update has been pushed to mess with the phone.
just call T-Mobile, tell them you haven't seen the update and they can push the update to you.
the other option you have is do a nandroid back up of the OS in the rooted stated, then unroot and turn s=on Do the update, re-root then flash the nandroid back up. and you are good to go.
I called T-Mobile and they cannot prevent the system from pushing the update notification to your phone.
poseidon1157 said:
Figures. I post a technical problem and everyone chimes in on something I said while frustrated. Not the problem. Thank you very much setzer for the recommended fix.
Personally, I would greatly appreciate it if none of the rest of you replied to my posts. Ever. Again.
And for the record you're right, I shouldn't have applied the update. Repeated attempts to find the update file failed, the notification stayed there, and my clockworkmod backup apparently disappeared with my photos and media and so I was stuck with a system I couldn't recover.
Click to expand...
Click to collapse
hold on there slick, i did provide insight full information. It's a simple mistake to make, but it's not 100% T-Mobile fault. infact it's not that fault at a 1% level.
Flashed recovery
For other idiots besides myself who think that custom stock-based kernels could be compatible with the update: they are not.
I did get this fixed. Personally I'm more comfortable with fastboot than I am with adb (no command-line completion, and imho it's the appropriate tool). After flashing clockwork recovery:
fastboot erase recovery&&fastboot flash recovery ${fastboot_location};
You can subsequentially mount it as a usb device (through recovery > mount... > USB). Copying a zip is necessary because (to my knowledge) tools to package the directories directly into a .img for fastboot have yet to be written.
Running a relatively stable cyanogenmod 7 nightly #18 with IMT/BT/GPS/SCCP. 801.11 drivers aren't working just yet. I might check through the git to see if there are pertinent commits.
Agreed
Hopefully you got it to work....
Sent from my HTC Glacier using XDA App
poseidon1157 said:
Figures. I post a technical problem and everyone chimes in on something I said while frustrated. Not the problem. Thank you very much setzer for the recommended fix.
Click to expand...
Click to collapse
Yeah, I guess your right, everyone did focus on that part, but it was the first thing you said. And you have to admit that the way your wrote your post you blamed TMO for messing up your phone. To most, that just seems stupid as it wasn't TMO that did anything wrong. All they did was try to push an update.
I'm sorry you had an issue, but you should have started out saying YOU messed something up. It's like having someone else root your phone and they say, "I'll try but there is a chance it will brick". And you saying, "it's cool dude, just give it a shot". Then when it bricks you blame them even after the warning.
Sorry, just trying to point out why everyone here thinks your post is lame. Please don't take offense to everyone, just realize that you blamed someone else for your OWN mistakes and then expect everyone to 'read your mind' and KNOW it was because you were frustrated.
I've just done a cleanup of the thread and had to remove half of the posts. I suggest if you have nothing helpful to say, please don't post at all.
Hi All,
OK, bootloader is unlocked, I am working on recovery, so the next challenge is....................S-OFF!!! Aw, f%@ck, I thought i had my life back...
I invite all users with ideas and/or knowledge to jump in and tell me what they think I am doing right and what makes me a moron. I have no pride, so lay it on me.
I will post progress reports in Post #2.
Anyway, here's to getting this done quickly.
Steve
Moderator Edit
This Thread has been moved back to the development section in an effort to put an end to the off topic discussion.
Given the size of this thread I'm going to suggest that you USE the Search thread feature located at the top to make sure your suggestion or idea has not been attempted already.
ANY OFF TOPIC POSTS WILL BE DELETED!
Progress Reports
Just starting out...
One More
This is just in case...
Excellent.
JSLEnterprises said:
Excellent.
Click to expand...
Click to collapse
Thought I'd get out of your thread and the root thread....
sk806 said:
Thought I'd get out of your thread and the root thread....
Click to expand...
Click to collapse
I had to send another message to red not to reopen the think tank thread (title would have been edited obviously), but to still go ahead with the cleanups... lol
Sorry if I'm totally off base here but I do believe reading on XDA somewhere that with the HTC One series phones when you unlock the bootloader it locks the phone from being able to flash recoverys.
This is the reason why I have waited to do the bootloader unlock I didnt want to screw myself from ever being able to flash custom roms.
you have to use this unlock method for the bootloader so why would it screw anything else up? It opens up all possibilities, not close them.
killathenoob said:
Sorry if I'm totally off base here but I do believe reading on XDA somewhere that with the HTC One series phones when you unlock the bootloader it locks the phone from being able to flash recoverys.
This is the reason why I have waited to do the bootloader unlock I didnt want to screw myself from ever being able to flash custom roms.
Click to expand...
Click to collapse
Nope. I have flashed CWM recovery at least 4 times on an international One X AFTER unlocking the bootloader. I wish that were it....
I think you may be thinking of firmware, which is a real mess, because unlocking your bootloader can set your CID to "none", and thus, you can't flash different firmware (i.e., an EU firmware on an Asian phone)...not that that would matter for these carrier-branded phones...
Good job and great progress. Unfortunately, none of us AT&T users can join in on the fun.
killathenoob said:
Sorry if I'm totally off base here but I do believe reading on XDA somewhere that with the HTC One series phones when you unlock the bootloader it locks the phone from being able to flash recoverys.
This is the reason why I have waited to do the bootloader unlock I didnt want to screw myself from ever being able to flash custom roms.
Click to expand...
Click to collapse
If that was completely true, then the Tegra 3 model's would not have cwm recovery... yet they do.
We just havent figured out a working method for ours.
JSLEnterprises said:
If that was completely true, then the Tegra 3 model's would not have cwm recovery... yet they do.
We just havent figured out a working method for ours.
Click to expand...
Click to collapse
i think what Killathehnoob is trying to say is that its only the ROGERS version of the ONE X that when unlocking the BLer HTC has somehow lock the other partitions so that custom recoveries and kernels are not able to be flashed to the phone...which essentially could be the case because all they said they will "unlock" the BLer...BUT they never said they would NOT do anything else in the process. maybe its a possibillity that has been over looked...just THINK TANKING is all
LNKNPRKFN said:
i think what Killathehnoob is trying to say is that its only the ROGERS version of the ONE X that when unlocking the BLer HTC has somehow lock the other partitions so that custom recoveries and kernels are not able to be flashed to the phone...which essentially could be the case because all they said they will "unlock" the BLer...BUT they never said they would NOT do anything else in the process. maybe its a possibillity that has been over looked...
Click to expand...
Click to collapse
I understand what you mean
I wonder if the fact that its new proprietary qualcomm chip is the reason why its being 'limited'... so we may have to rethink the whole initialization process.
we cant even get to the point that the logcat is able to start logging. So we're flying blind.
We've extended the time between loading to the soft reboot after the flash... but that doesnt tell us much.
I found the artice I read check it out
http://mobilesyrup.com/2012/05/02/i...bootloader-unlock-tool-on-one-series-devices/
killathenoob said:
I found the artice I read check it out
http://mobilesyrup.com/2012/05/02/i...bootloader-unlock-tool-on-one-series-devices/
Click to expand...
Click to collapse
Interesting. I think the lack is fastboot boot is what they are referring to. This would prevent custom kernel development on an s-off device, but should still allow flashing of insecure stock boot images, as with the int. HOX, althoug i read it again, anf maybe they are talking about more than that. I am not sure that the article is saying that there is something different with the Rogers version vs other versions, but it seems like there may be, and obviously with the Att version. I think I will spend a day just reading, trying to pick other devs' brains, and start fresh...thanks for the input.
Steve
sk806 said:
Interesting. I think the lack is fastboot boot is what they are referring to. This would prevent custom kernels being flashed on an s-off device, but should still allow flashing of insecure stock boot images, as with the int. HOX. I am not sure that the article is saying that there is something different with the Rogers version, but it seems like there may be, and obviously with the Att version. I think I will spend a day just reading, trying to pick other devs' brains, and start fresh...thanks for the input.
Steve
Click to expand...
Click to collapse
The 'fastboot boot' command works however, its how we got root in the first place.
... delegated to a Nigerian prince. Send money.
killathenoob said:
I found the artice I read check it out
http://mobilesyrup.com/2012/05/02/i...bootloader-unlock-tool-on-one-series-devices/
Click to expand...
Click to collapse
Here is the actual rootzwikk article
http://rootzwiki.com/news/_/articles/dear-htc-can-we-have-our-phones-back-r709
JSLEnterprises said:
The fastboot boot command works however, its how we got root in the first place.
... delegated to a Nigerian prince. Send money.
Click to expand...
Click to collapse
Whoa, very interesting. I was certain it did not on the Int one x.
JSLEnterprises said:
The 'fastboot boot' command works however, its how we got root in the first place.
... delegated to a Nigerian prince. Send money.
Click to expand...
Click to collapse
Just to be clear, you are not referring to fastboot flash boot, right?
Edit, nevermind, jut looked at Paul's post, it is fastboot boot. Wow.
killathenoob said:
I found the artice I read check it out
http://mobilesyrup.com/2012/05/02/i...bootloader-unlock-tool-on-one-series-devices/
Click to expand...
Click to collapse
Again thanks for this. Back to the drawing board!!!!
since we know that (locked bootloader on AT2) that doesn't allow us to flash custom kernels,but we know also that we can unpack/repack boot images to boot.img-kernel and boot.img-ramdisk,and we can flash radio.img,and we can flash non-signed system images (via CWM).
i can not figure the problem with bootloader!
we can flash repacked boot (ramdisk and kernel) and radio images,so we have an unlocked bootloader.
or maybe the Efuse problems?
correct me if i'm wrong.
sad_but_cool1 said:
since we know that (locked bootloader on AT2) that doesn't allow us to flash custom kernels,but we know also that we can unpack/repack boot images to boot.img-kernel and boot.img-ramdisk,and we can flash radio.img,and we can flash non-signed system images (via CWM).
i can not figure the problem with bootloader!
we can flash repacked boot (ramdisk and kernel) and radio images,so we have an unlocked bootloader.
or maybe the Efuse problems?
correct me if i'm wrong.
Click to expand...
Click to collapse
You know there's a Q&A Section, right? Also, this has been covered, like a gazillion times both by Jim, and others who have had this device since day one -- and still do own it!
You can flash a custom kernel but it will not boot. The stock kernel is signed by moto and the bootloader checks for this signature everytime at boot. No signed kernel no boot. Ask Jim, he's replaced several A2's trying to circumvent that check.
mtnlion said:
You can flash a custom kernel but it will not boot. The stock kernel is signed by moto and the bootloader checks for this signature everytime at boot. No signed kernel no boot. Ask Jim, he's replaced several A2's trying to circumvent that check.
Click to expand...
Click to collapse
i'll try to flash repacked/modified boot image (booting from SDCARD),
anyway,this is not the bootloader locked ! it's Efuse related !
sad_but_cool1 said:
i'll try to flash repacked/modified boot image (booting from SDCARD),
anyway,this is not the bootloader locked ! it's Efuse related !
Click to expand...
Click to collapse
Instead of getting angry, i would suggest that you read and then read some more. Believe it or not, this phone has not been cracked. So read and learn......if not then have fun making a paper weight! Don't come back and cry when your phone wont boot.
Sent from my MB865 using xda premium
sad_but_cool1 said:
i'll try to flash repacked/modified boot image (booting from SDCARD),
anyway,this is not the bootloader locked ! it's Efuse related !
Click to expand...
Click to collapse
Humm... not sure where you got this info, but it is 100% incorrect. I would also suggest a little attitude adjustment on your part.
We have tried it all... if you are such an expert than let us know once you have this unlocked.
I have been working on a method to boot from the sdcard with a root kit to flash an unlocked boot loader that we have for this phone, for some time.
Now do some research, read, post in the right section next time. If you keep up being a pain, I will have the thread locked.
Knock It OFF
Keep the thread "civilized".
Any more bickering and you'll get some early Christmas presents
The forums are open to anyone, so if you don't like replies, then don't post. And if you "Do" post, keep it civil.
Also, you guys have a filter option in your control panel, so you don't have to see each other's posts. I highly suggest you start using it.
MD
jimbridgman said:
Humm... not sure where you got this info, but it is 100% incorrect. I would also suggest a little attitude adjustment on your part.
We have tried it all... if you are such an expert than let us know once you have this unlocked.
I have been working on a method to boot from the sdcard with a root kit to flash an unlocked boot loader that we have for this phone, for some time.
Now do some research, read, post in the right section next time. If you keep up being a pain, I will have the thread locked.
Click to expand...
Click to collapse
whats the difference between locked bootloader and efuse protection?
wha you know about locked bootloader?
sad_but_cool1 said:
whats the difference between locked bootloader and efuse protection?
wha you know about locked bootloader?
Click to expand...
Click to collapse
OK, so an efuse is a switch that can be thrown (it is a switch on the cpu , as well as in several other locations on the board), that when thrown can render the phone useless. All these bricks people have been getting lately are because an efuse is thrown.
http://en.m.wikipedia.org/wiki/EFUSE
There are also several efuses that allow the device to be seen as an NS (Non-Secure) device, and will allow you to use the NS bootloader (it is unlocked), and we/I have been working getting all 6 efuse codes for a year now.
The bootloader in our case has three parts and several links in the security chain. Each step and/link has a cert attached to it and you can not move to the next part until the correct cert is handed off to next binary/loader in the chain.
This makes it so that we can not repack boot images or flash unsigned kernels or even some custom ROMs that require a custom kernel.
You need to realize that moto makes their boot loaders un-crackable. The bionic and RAZR are still locked, and the atrix HD just got root last week or the week before, and they are locked worse than the a2.
I also look at it like this if people like mbm, kohlk, hascode, etc. have not been able to crack the other moto devices they work with, then we are pretty SOL.
Does this mean I give up, hell no! It just means I am looking for alternative ways around the issue.
P.S. we can flash system images because the cert is in the filesystem code, and that is why we NEVER use format in an updater script, only erase.
as http://www.sourceconference.com/publications/bos12pubs/android-modding-source.pdf
and
http://tjworld.net/wiki/Android/HTC/Vision/BootProcess
and
http://www.droid-developers.org/wiki/Booting_chain
http://www.droid-developers.org/wiki/File:Boot_chrain_flow.png
where is the problem in our case , and how bootstrap (hijack) works?
sad_but_cool1 said:
as http://www.sourceconference.com/publications/bos12pubs/android-modding-source.pdf
and
http://tjworld.net/wiki/Android/HTC/Vision/BootProcess
and
http://www.droid-developers.org/wiki/Booting_chain
http://www.droid-developers.org/wiki/File:Boot_chrain_flow.png
where is the problem in our case , and how bootstrap (hijack) works?
Click to expand...
Click to collapse
Ok, so first I need to know a little background from you. Are you a developer? Are you an android dev? Have you done any android dev work at all?
What did you not understand in my last post, lets start with that, since I did explain it in good detail. Can you tell me the parts of our bootloader, before we go into any more detail?
The boot hijack allows us to hijack the boot process by using the logcat binary which has setUID privs, so it is prime to steal for perms and it has no FALCs or MACLs on it. What it does is it points (via a linux link), to another file that will allow us to boot to some form of cwm, but you still traverse through all the bootloaders before that binary file is executed, and the system image must be verified first, that is why if you bork your system image bad enough you can not get into cwm/bootstrap/bootmenu, etc.
Again, please ask me specific questions that you have about the bootloader. And understand that I am not a 5th grader, and that I do these things for a very, very, good living, so stop posting documents that explain the whole boot chain and cryptography to me.
Now I will say this one last time, I and others have posted a ton of information on the bootloader and processes over the last year, and please stop reading things like what you posted, those are outdated and or just plain incorrect, since motorola is whole different beast.
So one last time, please ask specific questions, and if this starts getting into how to unlock the bootloader, I will stop answering questions, as I have said a billion times in here that motorola does read this board, and they have thwarted my efforts with patches in the past.
Look, I am a little sorry for being frustrated, or terse, but this has all been covered so many times, and it sounds like you really do not know what you are doing, and I really do not want to explain this all over again, unless you really do know what I am talking about. So far you have not struck me as somone who understands our phones boot process, so I ask that you do a little more research first tear the bootloader and it parts apart, and come back with specific questions. I will use your earlier use of the efuse as a perfect example of what I mean by this.
I will leave you with a few last links to look at to get more familiar with a bootloader and why they are locked, and more:
http://androidforums.com/4657640-post1.html
http://www.tested.com/news/feature/1879-know-your-android-bootloaderwhat-it-is-and-why-it-matters/
Yes everyone, and to the MODS, I am sorry that link was to another forum, but it is very valid to the the point of this discussion.
Thanks man,i know that.
I can say that your AT&T AT2 is different from my AT2.
Cause i flashed a (repacked=not signed) stock boot image 4.766 kb successfully.
Sent from my MB865 using xda app-developers app
sad_but_cool1 said:
Thanks man,i know that.
I can say that your AT&T AT2 is different from my AT2.
Cause i flashed a (repacked=not signed) stock boot image 4.766 kb successfully.
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Which phone and region are you in? We all know the at&t version is a whole lot more locked down, than any international versions, and hence why we treat the at&t phones so differently here, It might have been good to start off your thread with some information about that, so that we did not go down this whole path. Your OP was quite sparse, so just think about that next time. In fact there are 5 different Atrix2 phones, even though there are only 2 model numbers, there are more differences between the regions the phones were released in, so those are also considered different versions even to motorola, and us devs in here.
Ok.
The topic was/is a question,not sparse.
I have MB865 with originally MEARET radio/firm,in middle east (jordan)
Sent from my MB865 using xda app-developers app
sad_but_cool1 said:
Ok.
The topic was/is a question,not sparse.
I have MB865 with originally MEARET radio/firm,in middle east (jordan)
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
But that info was/is very relevant to your question. It has been know for sometime now that the MEARET/SEARET version have a whole different bootloader and boot process than any of the other versions of the A2. The MEARET and SEARET can still fxz back, where the ME865 and the US versions can not.
Now you say you modified YOUR boot image right off your phone, or you took one from say the fxz and modified it, then flashed it, because those are two different situations, both still have the signatures, if they are extracted right. I was able to do this, as long as the kernel file/zimage was not touched, once I touched or played with that, it was all over on the US AT&T phones. The funny thing, is that the only reason to mess with the boot image on the A2 is for a different kernel and possibly to OC, but again I am pretty sure once you change the kernel in the boot image even on the MEARET/SEARET phones, to say an aosp kernel, you will not boot. It might be worth a shot, but keep in mind you have a huge chance of bricking by doing this.
And if you really want an unsigned kernel, why not just use kexec, and be done with it? It has less potential of bricking you, even if you are not completely locked.
jimbridgman said:
both still have the signatures, if they are extracted right.
Click to expand...
Click to collapse
this is the key-point
but i'm not flashing a repacked bootloader (needs RSA private keys from motorola),my work was in boot image.
sad_but_cool1 said:
this is the key-point
Click to expand...
Click to collapse
But only the image itself, not anything modified in the image, if you do mod it.... so if you stick and unsigned aosp kernel in place of the stock zimage, I am betting it will not boot, and might even brick the device. Just a theory, since I can not test with an MEARET phone, but when I have done it with my own compiled kernels with our kernel code, it does not pass the kernel signature check from the mbmloader and mbm.bin, and the device is bricked, on the AT&T phones.
---------- Post added at 12:02 PM ---------- Previous post was at 11:38 AM ----------
sad_but_cool1 said:
this is the key-point
but i'm not flashing a repacked bootloader (needs RSA private keys from motorola),my work was in boot image.
Click to expand...
Click to collapse
I never mentioned the bootloader, just the boot.img
what i want to say is:
boot.img = signing (compiled boot.img-kernel + compressed boot.img-ramdisk.gz )
the boot.img-kernel is signed , but the ramdisk is not,the repacking process doesn't contains signing routines/functions
so the repacked output will be unsigned!
i'll contact wkpark (http://forum.xda-developers.com/member.php?u=4414973) for more info
thanks all, MOD's you can delete this topic
sad_but_cool1 said:
what i want to say is:
boot.img = signing (compiled boot.img-kernel + compressed boot.img-ramdisk.gz )
the boot.img-kernel is signed , but the ramdisk is not,the repacking process doesn't contains signing routines/functions
so the repacked output will be unsigned!
Click to expand...
Click to collapse
The boot image is signed. The kernel is signed and the ramdisk/zimage is signed, on the ATT us version.
So, again the MEARET may be different. Be careful about blanket statements people may get all excited by that.
The thing is that the us version and the HK/TW and the ME versions are all setup the same with signatures at every step.
In the tests with unsigned ramdisk images on the ATT us version it has hard bricked every time.
This is my first post ever here so I'm sorry if I'm breaking some rule (read the forum rules so I don't think I am) or if it's in the wrong subforum (although this does seem like a help & troubleshooting topic to me).
A little backstory is probably necessary.
I rooted my s3 (latest OTA update) via CASUAL (thread: http://forum.xda-developers.com/showthread.php?t=2332825) and it seemed like it worked for the most part, although it didn't boot into twrp like it should have and instead booted into normal recovery. I just assumed that it was because something went wrong with the recovery installation so I just thought "ok whatever."
Root access was there, and I assumed the bootloader was unlocked since I read several places that when it's unlocked, the initial samsung boot logo appears for about a second as opposed to several seconds when it's locked. So I just assumed all i needed was to reinstall a custom recovery and I was golden.
Installed ROM Manager, flashed CWM through the app, and rebooted the phone, and as it was booting into recovery I was greeted with the infamous "NO CUSTOM SOFTWARE ALLOWED PLEASE ALERT PAPA VERIZON IMMEDIATELY" warning.
I was about to flash back to stock through odin (which i regretted since I've had bad experiences in the past using it) when I figured out I could get the device to boot normally by clicking cancel in the download mode confirmation window. I guess it kept trying to reboot to recovery after every unsuccessful boot, which made it seem like it was softbricked to me.
Phone is operating normally now, and it should after another reboot as long as it doesn't try to go into recovery again (though I'm kind of afraid to even do that).
Is there any way without Odin I can fix my recovery and/or bootloader? I'm not sure what the problem is here and I don't think this sort of thing is a common searchable issue. Google/XDA search didn't bring up anything that sounded like someone had 100% the same problem I do.
Also on a semi-related note, does EZ-Unlock still work with this latest OTA? And if my bootloader is potentially unlocked already, would unlocking it again through EZ-Unlock break something?
Sleix said:
This is my first post ever here so I'm sorry if I'm breaking some rule (read the forum rules so I don't think I am) or if it's in the wrong subforum (although this does seem like a help & troubleshooting topic to me).
A little backstory is probably necessary.
I rooted my s3 (latest OTA update) via CASUAL (thread: http://forum.xda-developers.com/showthread.php?t=2332825) and it seemed like it worked for the most part, although it didn't boot into twrp like it should have and instead booted into normal recovery. I just assumed that it was because something went wrong with the recovery installation so I just thought "ok whatever."
Root access was there, and I assumed the bootloader was unlocked since I read several places that when it's unlocked, the initial samsung boot logo appears for about a second as opposed to several seconds when it's locked. So I just assumed all i needed was to reinstall a custom recovery and I was golden.
Installed ROM Manager, flashed CWM through the app, and rebooted the phone, and as it was booting into recovery I was greeted with the infamous "NO CUSTOM SOFTWARE ALLOWED PLEASE ALERT PAPA VERIZON IMMEDIATELY" warning.
I was about to flash back to stock through odin (which i regretted since I've had bad experiences in the past using it) when I figured out I could get the device to boot normally by clicking cancel in the download mode confirmation window, rebooting the phone normally. I guess it kept trying to reboot to recovery after every unsuccessful boot, which made it seem like it was softbricked to me.
Phone is operating normally now, and it should after another reboot as long as it doesn't try to go into recovery again (though I'm kind of afraid to even do that).
Is there any way without Odin I can fix my recovery and/or bootloader? I'm not sure what the problem is here and I don't think this sort of thing is a common searchable issue. Google/XDA search didn't bring up anything that sounded like someone had 100% the same problem I do.
Also on a semi-related note, does EZ-Unlock still work with this latest OTA? And if my bootloader is potentially unlocked already, would unlocking it again through EZ-Unlock break something?
Click to expand...
Click to collapse
That is really weird...
I was reading it and was going to suggest easy unlock v1.2,you will not break anything using that app.
If that still doesn't work, try to flash TWRP through goo manager and see if it somehow fixes your recovery issue.
It sounds to me that your Bootloader is unlocked though... But give it a shot.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
That is really weird...
I was reading it and was going to suggest easy unlock v1.2,you will not break anything using that app.
If that still doesn't work, try to flash TWRP through goo manager and see if it somehow fixes your recovery issue.
It sounds to me that your Bootloader is unlocked though... But give it a shot.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick response.
That was going to be what I tried first, that's why I asked about it.
I'll wait for a little more input before trying it though if it's really that weird of an issue.
Sleix said:
Thanks for the quick response.
That was going to be what I tried first, that's why I asked about it.
I'll wait for a little more input before trying it though if it's really that weird of an issue.
Click to expand...
Click to collapse
It's just strange that you only get that message with recovery mode, it normally will not do that.
At the very worst, an odin back to stock is pretty easy. Just follow the same process, but use ez recovery instead of rom manager. It was made specifically for our phone, and never gives me any issues when installing recoveries.
I still think if you use ez unlock it'll probably fix the issue completely. Let me know if you figure it out. Good luck.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
It's just strange that you only get that message with recovery mode, it normally will not do that.
At the very worst, an odin back to stock is pretty easy. Just follow the same process, but use ez recovery instead of rom manager. It was made specifically for our phone, and never gives me any issues when installing recoveries.
I still think if you use ez unlock it'll probably fix the issue completely. Let me know if you figure it out. Good luck.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks. Used ez unlock to unlock the bootloader. It was previously labeled as "Unknown".
Downloading ez recovery right now. Do you think I need to reinstall my recovery just to make sure?
Sleix said:
Thanks. Used ez unlock to unlock the bootloader. It was previously labeled as "Unknown".
Downloading ez recovery right now. Do you think I need to reinstall my recovery just to make sure?
Click to expand...
Click to collapse
No, but it wouldn't hurt.
Use 1.2 of ez unlock, versions 1.3 and 1.4 will give an unknown message. There have also been lots of reports saying that version 1.4 did not unlock their bootloader.
These are the most recent recoveries, download and flash in the ez recovery app if you need to.
http://forum.xda-developers.com/showthread.php?t=2096735
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
No, but it wouldn't hurt.
Use 1.2, versions 1.3 and 1.4 will give an unknown message. There have also been lots of reports saying that version 1.4 did not unlock their bootloader.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Reflashed CMW (I used the version provided by ez recovery, please let me know if that's a problem) just in case and it worked like a charm. Thanks!
Also I did use version 1.2. I actually had it sitting on my phone's home screen before I made this thread.
It still showed up as "Unknown". Maybe that indicated the problem?
Regardless, this problem seems to have been fixed. Now it's time to do some research on verizon s3 roms.
Also another semi-unrelated note, it seems I tripped a flash counter somewhere along the line.
Is Triangle Away one of those apps that is just "open and press a button"? I've been kind of wary of using it since it has that huge warning in app's description.
Sleix said:
Reflashed CMW (I used the version provided by ez recovery, please let me know if that's a problem) just in case and it worked like a charm. Thanks!
Also I did use version 1.2. I actually had it sitting on my phone's home screen before I made this thread.
It still showed up as "Unknown". Maybe that indicated the problem?
Regardless, this problem seems to have been fixed. Now it's time to do some research on verizon s3 roms.
Also another semi-unrelated note, it seems I tripped a flash counter somewhere along the line.
Is Triangle Away one of those apps that is just "open and press a button"? I've been kind of wary of using it since it has that huge warning in app's description.
Click to expand...
Click to collapse
Glad to hear it's working! Strange issue but looks like you ironed it out.
Triangle away is the app you would use. You tripped it using the rooting method injecting your recovery through odin, it's a big warning because it messes with your boot partition. If it fails and borks your boot partition, then you'd have to jtag your phone to fix it.
I personally wouldn't use it unless I was turning in my phone for service or replacement. But the app has great reviews and not many reports of bricks.
Before flashing anything, use a newer recovery image. The one provided by ez recovery is from last year, the newer versions are better written to prevent possible errors that come up with jellybean.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Glad to hear it's working! Strange issue but looks like you ironed it out.
Triangle away is the app you would use. You tripped it using the rooting method injecting your recovery through odin, it's a big warning because it messes with your boot partition. If it fails and borks your boot partition, then you'd have to jtag your phone to fix it.
I personally wouldn't use it unless I was turning in my phone for service or replacement. But the app has great reviews and not many reports of bricks.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I'll keep that in mind, thanks again!
Any roms you'd recommend?
Sleix said:
I'll keep that in mind, thanks again!
Any roms you'd recommend?
Click to expand...
Click to collapse
Read through the op's and decide based on what you're looking for.
Mostly stock, very stable:
Clean rom, bonestock, darthstalker x1.
More modified stocks, more buggy but can run very well:
Hyperdrive, axis, goodness, moar
AOSP isn't my cup of tea, but they are fast and lag free.
Make sure you update your recovery image first, I edited my last post but think you missed it.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Read through the op's and decide based on what you're looking for.
Mostly stock, very stable:
Clean rom, bonestock, darthstalker x1.
More modified stocks, more buggy but can run very well:
Hyperdrive, axis, goodness, moar
AOSP isn't my cup of tea, but they are fast and lag free.
Make sure you update your recovery image first, I edited my last post but think you missed it.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Will do. Thanks for pointing that edit out.
Is there such thing as a guide like this one but that is up to date and with working links? I want to flash a new ROM onto my phone, but the guides I've found here and elsewhere have broken links, or use language that I don't understand, or skip vital steps. I've been working on this for four hours straight and I haven't gotten a single guide to work, or get stuck, or something else that's really dumb. For someone who has worked on computers for the last 17 years this is extremely frustrating. I'm very new to the android modding scene and apparently it's not just a community, but an entirely different culture and I'm feeling a bit shocked and confused. I have like 30 tabs open with guides, info, different ROMs, different ways to do it, etc and the more I learn the less I understand how to do this :/ I just want to get my phone working with a ROM that's very similar to stock Sense but without the crappy bloatware and memory issues. Miktouch is the one I thought I wanted, but apparently hasn't been updated in almost a year, and bulletproof/doubleshot is confusing. I can't even figure out how to root and get S-Of... Gah!
Please help.
This guide is confusing and skips steps or lacks real explanations.
Thank you.
First thing you want to do is root your phone, this is done by unlocking you bootloader through the HTC dev website. There is a tutorial that is stickyed in the developer section called something like root from any bootloader. I suggest to read that a bit.
Once you followed those steps and unlocked your bootloader you can decide if you want to remove all security flags (highly recommend this, but some find it difficult) in the same guide it explains what radio s-off is and links you to the jbear site to do the wire trick (needs Linux) (or find weekendstoshort for a way to do it in windows)
Feel free to ask more questions but all answers should be found in these xda threads and jbear site, no need to Google anything for this
Sent from my Nexus 4 using xda premium
I hope so...I'll give it another go tomorrow. I'm still quite frustrated at it. I wish I knew someone who had done it and could show me in person.
GiftigDegen said:
I hope so...I'll give it another go tomorrow. I'm still quite frustrated at it. I wish I knew someone who had done it and could show me in person.
Click to expand...
Click to collapse
MikTouch is optimized stock... So updating it farther would take it a direction we wasn't going with it.
Bulletproof is even older. We don't have much here... But what's here is solid
Sent from my Nexus 4 using Tapatalk 4 Beta
First timer here as well (although long time computer user/programming familiar so I might have a better understanding of some things than you) and I was able to fully unlock, S-OFF, and load up a JB rom to my phone using the guide right on this site (http://forum.xda-developers.com/showthread.php?t=1801106) and some help from some online friends that have done this kind of thing before. I found all links to be working, and pretty much all steps to be covered. The I guess hardest part was the permanent S-OFF using the wire trick. I had to burn an Ubuntu live cd and boot a laptop with it, but I was even able to get that step done. A little frustrating with the timing, I think it took me about 8 tries until it finally unlocked. The only thing I think I initially missed was wiping all 3 caches, so I did a dirty flash that got stuck on the boot screen. After I wiped and loaded again, no problems. If you'd like any additional help, I get pretty bored at work, so find me on aim or gchat, or just shoot me a PM here, I think I should get notified
Good luck, it's not as bad as I thought it would be
Also I haven't personally tried it, but feel free to peruse this thread as well: http://forum.xda-developers.com/showthread.php?t=1696373
Note you'll need to have already achieved HTCDev unlocked and be rooted to use this (covered in that first link)
Hope that helps!
PsychoPhreak said:
First timer here as well (although long time computer user/programming familiar so I might have a better understanding of some things than you) and I was able to fully unlock, S-OFF, and load up a JB rom to my phone using the guide right on this site (http://forum.xda-developers.com/showthread.php?t=1801106) and some help from some online friends that have done this kind of thing before. I found all links to be working, and pretty much all steps to be covered. The I guess hardest part was the permanent S-OFF using the wire trick. I had to burn an Ubuntu live cd and boot a laptop with it, but I was even able to get that step done. A little frustrating with the timing, I think it took me about 8 tries until it finally unlocked. The only thing I think I initially missed was wiping all 3 caches, so I did a dirty flash that got stuck on the boot screen. After I wiped and loaded again, no problems. If you'd like any additional help, I get pretty bored at work, so find me on aim or gchat, or just shoot me a PM here, I think I should get notified
Good luck, it's not as bad as I thought it would be
Also I haven't personally tried it, but feel free to peruse this thread as well: http://forum.xda-developers.com/showthread.php?t=1696373
Note you'll need to have already achieved HTCDev unlocked and be rooted to use this (covered in that first link)
Hope that helps!
Click to expand...
Click to collapse
I'm following the first guide you linked. So far it's working I just flashed CWmod on and I loaded it according to the instructions in the guide "After fastboot finishes, disconnect your MT4GS, go into bootloader, and go to “RECOVERY.” You should now be in ClockworkMod Recovery 5.0.2.7. The first thing I would do in CWM Recovery is make a backup of your stock ROM for safe keeping. "
But I forgot to d/c my phone. It still loaded CWmod and I navigated to backup/restore and clicked it. Right now my phone has the clockwork logo in the middle but it didn't give me any prompts after selecting backup/restore. What's it doing? It's been doing this for like 5 minutes. Should I be worried that I forgot to d/c the cable and whatnot?
Thanks
GiftigDegen said:
I'm following the first guide you linked. So far it's working I just flashed CWmod on and I loaded it according to the instructions in the guide "After fastboot finishes, disconnect your MT4GS, go into bootloader, and go to “RECOVERY.” You should now be in ClockworkMod Recovery 5.0.2.7. The first thing I would do in CWM Recovery is make a backup of your stock ROM for safe keeping. "
But I forgot to d/c my phone. It still loaded CWmod and I navigated to backup/restore and clicked it. Right now my phone has the clockwork logo in the middle but it didn't give me any prompts after selecting backup/restore. What's it doing? It's been doing this for like 5 minutes. Should I be worried that I forgot to d/c the cable and whatnot?
Thanks
Click to expand...
Click to collapse
I wouldn't worry, and I'm not entirely sure what it's trying to do, perhaps the possibility of USB storage is throwing it off. At this point I'd say just try to disconnect it, pull the battery, and start back up into recovery, but without the USB attached this time. I imagine then you'll be fine and able to backup the stock image like they say for safe keeping.
One more dummy question (tech support for many years, always check the simple stuff first...) you do have SOME SD card in there right?
PsychoPhreak said:
I wouldn't worry, and I'm not entirely sure what it's trying to do, perhaps the possibility of USB storage is throwing it off. At this point I'd say just try to disconnect it, pull the battery, and start back up into recovery, but without the USB attached this time. I imagine then you'll be fine and able to backup the stock image like they say for safe keeping.
One more dummy question (tech support for many years, always check the simple stuff first...) you do have SOME SD card in there right?
Click to expand...
Click to collapse
Yeah, 32gb =)
booted into recovery, clicked on bacup/restore...still just showing the logo in the middle.
(PS any mods out there listening, I'd love to have that 5 minute restriction removed =D )
Okay, so the select button changes from power to the scroll pad once in recovery...good to know.
GiftigDegen said:
booted into recovery, clicked on bacup/restore...still just showing the logo in the middle.
(PS any mods out there listening, I'd love to have that 5 minute restriction removed =D )
Okay, so the select button changes from power to the scroll pad once in recovery...good to know.
Click to expand...
Click to collapse
NVMD....You got it now.
strapped365 said:
MikTouch is optimized stock... So updating it farther would take it a direction we wasn't going with it.
Bulletproof is even older. We don't have much here... But what's here is solid
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Using CWM to flash Miktouch now. Hopefully it works... =D
Just remember, if you are "S-On" you're going to need to fastboot flash boot boot.img after your ROM is thru flashing or you will hang up at the boot animation.
strapped365 said:
MikTouch is optimized stock... So updating it farther would take it a direction we wasn't going with it.
Bulletproof is even older. We don't have much here... But what's here is solid
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
K. First impressions:
When I restart the phone, the first thing it does is force stop Gmail and Youtube several times. Is this supposed to happen?
Also, I'm extremely impressed with the speed of the restart. It's at LEAST twice as fast as stock.
And, Genius button doesn't work even after installing the patch linked to on your website (universal.zip).
WeekendsR2Short said:
Just remember, if you are "S-On" you're going to need to fastboot flash boot boot.img after your ROM is thru flashing or you will hang up at the boot animation.
Click to expand...
Click to collapse
Thanks Weekends. I did that and it's installed, though I fastboot flash boot boot.img before I used CWM to flash the rom. Does that make a difference? Do you think doing it that way will fix the force close mentioned above?
If there's not a fix for the gmail/youtube force closes, is it possible to do bulletproof with s-on? Thoughts? I really want to stick as close to stock MT4GS but with as solid a system as possible.
Flashing boot image before ROM will overwrite kernel
Wipe all
Flash ROM
Flash boot
Reboot
Sent from my Nexus 4 using xda premium
demkantor said:
Flashing boot image before ROM will overwrite kernel
Wipe all
Flash ROM
Flash boot
Reboot
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Another noob question. How do I wipe all?
Also, when I use CWM to install Mikrom it atuo restarts and loads up. Then do I restart again and go fastboot the new kernal?
Thank you all for how much help you have given me.
At the end of the updater-script there must be a reboot command, but being this ROM is based of stock you may not need to flash the kernel anyway.
Best methods for wiping is one of bluex's superwipe scripts or with fastboot
fastboot erase system -w
But being you are s-on that command may fail.
But always do a wipe data/factory reset, wipe cache, and wipe dalvik in recovery.
It also good practice to make a nandroid of current ROM before you flash anything
Sent from my Nexus 4 using xda premium
demkantor said:
At the end of the updater-script there must be a reboot command, but being this ROM is based of stock you may not need to flash the kernel anyway.
Best methods for wiping is one of bluex's superwipe scripts or with fastboot
fastboot erase system -w
But being you are s-on that command may fail.
But always do a wipe data/factory reset, wipe cache, and wipe dalvik in recovery.
It also good practice to make a nandroid of current ROM before you flash anything
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Mmkay, working doing this now.
Quick question, hopefully someone can give me a link, but I'd love the install the depaginated app drawer, genius fix and menu wake up mods for this, but the links are broken (dev-host times out). Any help?
See weekends mirror thread
Sent from my Nexus 4 using xda premium