Well, I've asked a mod to lock the other root status thread. It was getting kind of out of hand. After about page 80, people stopped looking at what we had done so far, and trying to help by putting ideas out that already failed.
This is what we know:
Fastboot is locked down in everything but oem-78 mode. You can get to this mode by typing "reboot oem-78" at an adb shell. Fastboot is essentially unlocked, allowing fastboot boot and fastboot flash, only the .img images we try to boot or flash NEED TO BE SIGNED.
Goldcards no longer allow non signed firmware to be loaded, only signed firmware with a different SID.
All known flashing methods require the .img files to be signed by HTC. We do not have the privatekey, nor do we have any way to decrypt the key as it is RSA. Meaning this is a NO GO.
All previous known exploits (asroot2, g1 telnetd, DROID update.zip method) have been patched. They won't work. And there isn't a way around this.
All the partitions except /data are mounted as read only. Meaning, without root access, there is NO way to modify them. In the init.rc file, they are mounted rw, and directly after that mounted ro. We can read and write to /data as we wish, but NOTHING important is here.
The only folder anything can run as root out of is /system/bin. Every other partition is mounted with the nosuid option, meaning code CANNOT be run as root. Simple enough. We can't run anything as the user root, or the group root.
Lets try to stay a little more on topic this time. Please don't let this become another 40 pages of complete crap. And please keep this thread about root access, any other problems should be posted in the appropriate forum.
Thanks, and lets get this root done!
I'm currently comparing superboot.img in a hex editor to the vanilla boot.img for that phone so I can better understand what he did, and how. I'll see what I can turn up, maybe we can make one for the eris.
EDIT: It seems it's not going to be so easy. There's a lot of things changed. It appears he changed something at the top of the file right after the header, and then there is some sort of (SHA1?) hash right below that, but I don't know what it's calculated from. This is beyond my skills at the moment, I think.
Are any of the fields changed from the original boot.img show up in our boot.img? Chance of searching for each field in our img and replacing with possibly what he did?
is it possible that the guy who made superboot has htc signature, or somehow decrypted it???? 8-O
Yes I guess anything is possable but I think their is a better chance of monkeys flying out of my butt.
well i guess it was time to lock the other thread as some people could not play nice..... so i guess we will use this one now..... next idea anyone, and i am guessing jman will no longer be joing us, so it looks like we are on our own.
im ready to get this done what have we got so far?
About 140 pages of failed attempts.
well i know that much i have been sitting back following from the begining now im ready to get my hands dirty, though i have no clue what im doing
binny1007 said:
well i guess it was time to lock the other thread as some people could not play nice..... so i guess we will use this one now..... next idea anyone, and i am guessing jman will no longer be joing us, so it looks like we are on our own.
Click to expand...
Click to collapse
Ok, I missed something I think. Thats what I get for not refreshing every 10 seconds What happened to jman? Or is it better off that I not ask
punk.kaos said:
Ok, I missed something I think. Thats what I get for not refreshing every 10 seconds What happened to jman? Or is it better off that I not ask
Click to expand...
Click to collapse
I don't think I'll be following these threads anymore. I try to help you guys, but in the end some of you just don't appreciate the help.
I don't claim to be an expert, and I never promised anybody that I could root their phone. I simply have information to share that I think has brought you guys to a greater understanding of your phones and the Android system. Most of you are thankful, but I really don't need to be attacked personally in these threads that don't even have anything to do with my phone.
I'd like to thank the moderator for locking down the other forum, I'd also like to thank whichever moderator deleted the message that was quite insulting to me.... I only happened to see it because it came into my email. Yes, I subscribed to the thread via email to try to keep up with you guys and offer any help I could as quickly as I could.
I'm sorry guys, I wish you luck, but I just don't need to be berated in open forum like that for trying to help the Eris owners out, so I won't be keeping up with your rooting efforts.
There are a couple of you that have been very appreciative, and please feel free to PM me.
Thanks jman and I understand, if I was in your shoes I would do the same and I reported that post almost right after it was posted hoping you would not see it. But I know for me I have a greater understanding of my phone and like I have said before Thank you very much for your help. It's a shame to see you go but we understand.
Binny
doubt this will help, its all that htc tech support would throw up at me.
http://developer.htc.com/
contains hero and adp but nothing about eris.
jmanley69 said:
I don't think I'll be following these threads anymore. I try to help you guys, but in the end some of you just don't appreciate the help.
I don't claim to be an expert, and I never promised anybody that I could root their phone. I simply have information to share that I think has brought you guys to a greater understanding of your phones and the Android system. Most of you are thankful, but I really don't need to be attacked personally in these threads that don't even have anything to do with my phone.
I'd like to thank the moderator for locking down the other forum, I'd also like to thank whichever moderator deleted the message that was quite insulting to me.... I only happened to see it because it came into my email. Yes, I subscribed to the thread via email to try to keep up with you guys and offer any help I could as quickly as I could.
I'm sorry guys, I wish you luck, but I just don't need to be berated in open forum like that for trying to help the Eris owners out, so I won't be keeping up with your rooting efforts.
There are a couple of you that have been very appreciative, and please feel free to PM me.
Click to expand...
Click to collapse
Thanks for sticking through with us. You've been extremely helpful since day one, and I would like to say thanks and basically say what Binny said above.
I haven't had a lot of time to follow the thread, but, I too, am happy that it was locked. Hopefully the Eris owners can regroup in a day or so after we all chill out. Sigh. Fingers are still crossed for root.
Has anyone been able to actually BOOT any of the images extracted from the rom.zip via fastboot in oem-78 mode? If so, and you could post how, I might have access to an image with root access. I've tried repeated times to perform "fastboot boot recovery.img" but it sends it and then sticks on "booting..." I have moved forward with the RUU at this point, but the device never actually boots into the img.
Unfortunately, I cannot not upload the image due to my job.
Also, if anyone can help with goldcard downgrading, I might be able to downgrade to an old version with root access. My downgrade continues to fail due to the bootloader version being too high. I created the goldcard per the appropriate thread and it appeared to work as the Cell South thread indicated, but still no dice on the downgrade.
If your gold card is made right it should work.... are you putting the .zip on you gold card and renameing it PB00IMG.zip?
binny1007 said:
If your gold card is made right it should work.... are you putting the .zip on you gold card and renameing it PB00IMG.zip?
Click to expand...
Click to collapse
Yes, but it still fails with error 43, I believe. "Main version check"
Did you run the simlock option in the bootloader, and it passed
binny1007 said:
Did you run the simlock option in the bootloader, and it passed
Click to expand...
Click to collapse
Yes. Perhaps goldcard doesn't work on this device like it's supposed to.
I have been reading and attempting two flash anything for 2 days. I am new as I have stated in some threads and need baby steps unfortunately like im
sure some others do. I have been able to unlock, root, and get into recovery but after that no dice. I get everything Im suppose to do but... I am not able
to flash anything and I have looked for help in threads and have had some help and success but more importantly all detail is not clear to me all the time. I
am on here because I want the most out of my phone and all the goodies and appreciate the work of everyone. Coming from Windows to Android is
different and I understand will take sometime to gain the knowledge needed but it seems as you/we are supposed to know everything already or if you/we
dont understand what to do then you/we shouldnt be flashing some say. I disagree with that because I started the same way on my HD and eventually
was able to help new ppl to the forum. We all have been there at some point trying to learn and being clueless then finally getting it. For instance I was
looking at a theme thread and there was no instruction from the author am I just suppose to know what to do with the file being that Im not a week into
this and have never dealt with android? Also what to write in some command prompts is not the same for everyone different and thats not always clear.
With that being said this being a new device I would hope that things will be more written out to help and if its not at least be able to get help. This is just
in some cases not all . Again I am thankful for everyones work on here.
Now with the files I have trouble with are pretty much every file I have placed on my sd card not being recognized except Modocas rom until I renamed it
update.zip. Until then in recovery nothing would be recognized and even still the rom failed to install in which I have no clue why and have been seeking an
answer and so have others. If anyone has any suggestions it would be greatly appreciated for me and others and also to give detail on what to do with
what we are given. Thanks to everyone who contributes on here and make the experience that much better.
Every one of the instructions that are on this forums (in the dev area) are explained in detail. You must have some core understanding of basic linux commands and android file system. Those we are not going to teach you here. There are many documents on android itself (search on google) and HTC also has a lot of documentation on flashing.
However with that said, rooting instructions were to the point and should be able to follow without issues. thefallen has written it instructions for windows/dos and I've recapped them for linux/osx. To be honest, commands are the same for adb and fastboot.
Amon_Ra also has a good instructions on how to update his recovery. Pretty much if I should recap, I'd say boot phone in boot loader and fastboot flash recovery new_recovery_image.img
As for the themes and most of the updates, always run a nandroid first and update. What do I mean by that? Nandroid is the backup utility in Amon_Ra's recovery. If you ran it, you can restore to that. Call it a restore point but it's more than that (read on that so you know what it actually does). Why nandroid? So you can restore if you don't like the effects of what you just done. Now you can just update via zip that you download.
I think it's very simple. What do you need explained in detail? Most of the stuff you are requesting is simple knowledge. I am not saying I am holier. I am just saying I am used to the commands. Once you flash it a few time, it'll come to you too. But please do read up on how to restore an image from HTC. Go to HTC Global, and support and pull up google ION.
Read thru the instructions. If you are still confused, feel free to PM me.
If recovery is only recognizing update.zip, are you sure you have Amon_Ra's recovery on there? Have you tried to reflash his recovery image?
Thank you guys. I figured out what I was doing wrong.
Hi guys i know Brian117 originally posted this and sc2k helped him fix hes tablet i apologize for not continuing the thread
but its been almost 8 hours since i bricked my tablet. i can't take it anymore i tried alot of things i search Google for answers until i gave up.
Im not a pro but im not new to flashing roms so i originally installed CWM from the "it's Magic" post from sc2k i did it successfully then installed
Dexter's primee rom successfully aswell no problem. Once i discover Virtous picasso rom, Honey Villain rom i decided to test them out aswell
see witch one fit my liking so i did successfully. After seeing Virtous galaxy i decided to check it out i did i got an error at boot so after posting
my error some suggested i update my CWM so i was able to boot into galaxy rom loved it then i downloaded "update-recovery-thor2002ro-rev1.3.4"
from the instruction i gathered im suppose to just flash it through CWM so i did and it said that i succesfully flashed it now reboot into CWM to see
the changes so at this point i thought heck yeah!! then to my surprise i reboot it the tablet and was greeted to " secure boot: image SOS checksum fail!" so i then tried a normal reboot the ACER logo just stood there hanging looking back at me laughing.
Before i originally installed CWM i followed all instruction so i have all my back ups and UID saved on my PC. i Already pm sc2k about see if he can help me
but i thought i post the whole processed of what i did to avoid others bricking their tablet aswell and hopefully in the mean time if any of you guys have any suggestions, tips i gladly welcome them since i cant return it to staples anymore i have to deal with Acer if i cant get it to work. Also I fully understand this is a risk i took and not blaming no one for my error all im asking is for help
u done one wrong step, u didnt run its magic before installing thor recovery i think..
I am pretty sure that thor explains in his thread that you should flash his "update-recovery-thor2002ro-rev1.*.*" files only if you allready have his version of recovery installed.
So you should have installed the full "recovery-thor2002ro-rev1.3.4.rar" as described in 1st post of his thread and not just try to flash the update-recovery file.
Maybe thor or sc2k can help you now..
I think the problem was that your original cwm was an older version that did not run itsmagic automatically on startup and the update package doesn't run it either. I'm so glad to see someone who has backups!
Don't know if this will help.. The hang at the logo is usually an indication of needing to do a data wipe after installing a custom rom. Was the tablet booting normally before flashing the cwm update?
Anyway, this thread from sc2k demonstrates a method to wipe data. You can see if that will help get you past the logo screen. If it does, great.. run itsmagic, then you should be able to get back into recovery.
If it doesn't help, you'll need to ask sc2k how to unbrick via nvflash (that's what mcblk0_start file is for).
Edit: aw man..I just realized I forgot the link.... ah well
Update: with help from sc2k i was able to fix my tablet it worked great.
and im currently installing a custom rom through Thor2002ro CWM.
Thousand thank you's to sc2k and everyone in the Development comunity
for the advice i knew if you guys couldnt help me no one could.
thank god for the XDA forums.
babyboy8100 said:
Update: with help from sc2k i was able to fix my tablet it worked great.
and im currently installing a custom rom through Thor2002ro CWM.
Thousand thank you's to sc2k and everyone in the Development comunity
for the advice i knew if you guys couldnt help me no one could.
thank god for the XDA forums.
Click to expand...
Click to collapse
How do I PM SC2K. I have the same issue with my a500. LNX Checksum error. I Need Help!!! Please Help.
Can someone suggest another forum where I can go for help?
The last 5 or 6 times I've posted questions here, I've gotten no answers at all. I really need help. My tablet was bricked because I lost ADB connection while updating the system partition. I know there is a way around this - I have a custom recovery and an unlocked bootloader - but I need help from someone who knows more than I do. No one here is going to help me, I know. Where do I go? Where can I find someone knowledgeable and helpful?
permutations said:
Can someone suggest another forum where I can go for help?
The last 5 or 6 times I've posted questions here, I've gotten no answers at all. I really need help. My tablet was bricked because I lost ADB connection while updating the system partition. I know there is a way around this - I have a custom recovery and an unlocked bootloader - but I need help from someone who knows more than I do. No one here is going to help me, I know. Where do I go? Where can I find someone knowledgeable and helpful?
Click to expand...
Click to collapse
Have you tried booting to recovery from bootloader and regaining an ADB connection? This should be all you need.
permutations said:
Can someone suggest another forum where I can go for help?
The last 5 or 6 times I've posted questions here, I've gotten no answers at all. I really need help. My tablet was bricked because I lost ADB connection while updating the system partition. I know there is a way around this - I have a custom recovery and an unlocked bootloader - but I need help from someone who knows more than I do. No one here is going to help me, I know. Where do I go? Where can I find someone knowledgeable and helpful?
Click to expand...
Click to collapse
The more information you provide, the better. Please provide more information regarding your device so that your thread can be placed in the correct forum.
Magnum_Enforcer said:
The more information you provide, the better. Please provide more information regarding your device so that your thread can be placed in the correct forum.
Click to expand...
Click to collapse
I was updating my Nexus 10 tablet - had gotten to the system partition - when I lost the ADB connection. I've since learned that's a problem with newer Macs (I was connected to Windows through Parallels). Here's a link to a thread about that:
https://code.google.com/p/android/i...Stars Reporter Opened&groupby=&sort=&id=65301
Because of the lost connection, the system partition did not flash and my tablet is bricked. There is no operating system so it can't boot into Android, but it can boot into the Bootloader and Recovery mode. All the other partitions are fine.
I have a custom recovery (TWRP) and an unlocked bootloader, but I'm at a loss to figure out how to flash the system.img file. I can't boot to Android so I can't connect through ADB in Fastboot mode to flash the ordinary way. I am connected through ADB when I'm in Recovery mode, but I can't use the flash command in Recovery mode. Nor can I figure out a way to make TWRP flash the partition by running it as a zip file - mainly because I can't figure out what the update.zip file should consist of. There was an OTA update file on my device when I started the manual update (manual updates fail), but I didn't look at it and didn't save it.
I tried pushing the system.img file to the Nexus 10 using the Linux dd command, but that doesn't work with the system partition, which uses a special format. The details are explained here, but I don't fully understand it:
http://www.modaco.com/forums/topic/327661-how-to-backup-the-systemimg-bootimg-and-recoveryimg/
After spending about 8 hours on this last night, I believe the only way I can fix it is to create an update.zip file that uses a Linux script to flash the system partition, but this is way beyond my skill set and I can't find a model for how to do this anywhere. All tutorials I've found for creating zip files for flashing are for installing apps, not flashing a system partition - which is even more complicated than flashing, say, a boot partition. Nor can I find an update.zip file from someone's cache (sure wish I'd saved mine) to use as a model. I'm looking for someone with this kind of high level knowledge who can give me guidance - or someone who can refer me to someone who has this kind of knowledge.
I solved this problem.
hi everyone,
i have a couple of questions and i favor i would like to ask from anyone who sees this.
i currently own the sony xperia e4 phone which as of right now , doesnt have any development for it since there is no custom recovery yet.
the problem is that the device doesnt have a stock recovery (and no recovery partition).Secondly it has a non-standard boot.img so mkvendor.sh script doesnt work.i am able to get the info myself (base adress, kernel adress etc.) but i dont have a pc atm so i cant compile it and it doesnt have a
recovery partition so i t cant be flash that way. i read something about flashing xperia recoverues on the fotakernel but im not sure if some modifications are needed to do so.
if anyone with a build enviroment and time would like to compile the recovery themself (i will provide files such as the boardconfig myself)pm me.
any help is much appreciated.
Mod edit:
Thread closed as the cross-dev section is not the place for this
Try asking here
https://forum.xda-developers.com/t/xperia-e4