Related
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.
Thought maybe by now someone would make a workable flashable zip to flash basically stock vibrant firmware with the nand fix (the real method, not with 130 mb limit). If it is out there I apologize, but i'm almost sure I haven't seen it on here. And I'm referring to flashing via clockwork recovery. I've come from a G1 and really never had to do anything but download and hit the "flash any zip" option from recovery, and its a method i'm most comfortable with. Thanks for any direction you might provide.
This ROM doesn't use the NAND, it uses an EXT2/EXT3 partition on your SD card.
http://forum.xda-developers.com/showthread.php?t=743506
javacody said:
This ROM doesn't use the NAND, it uses an EXT2/EXT3 partition on your SD card.
http://forum.xda-developers.com/showthread.php?t=743506
Click to expand...
Click to collapse
How is it working for you?
joe.kerwin said:
Thought maybe by now someone would make a workable flashable zip to flash basically stock vibrant firmware with the nand fix (the real method, not with 130 mb limit). If it is out there I apologize, but i'm almost sure I haven't seen it on here. And I'm referring to flashing via clockwork recovery. I've come from a G1 and really never had to do anything but download and hit the "flash any zip" option from recovery, and its a method i'm most comfortable with. Thanks for any direction you might provide.
Click to expand...
Click to collapse
..since there is no way to magically make nand bigger than 128 megs (without soldering new chips on) I suspect "the real method" is the apps2sd method..
Disconn3ct said:
..since there is no way to magically make nand bigger than 128 megs (without soldering new chips on) I suspect "the real method" is the apps2sd method..
Click to expand...
Click to collapse
Both Methods require ROOT*
*Method 1 limits the space of app data, which can possibly cause issues*
*Method 2 requires writing a new Kernel, which comes with it's own possible issues*
I'm just getting irritated. I have a 1ghz phone with lag/gps problems. It seems whenever I need to whip out my phone for something quick those are always the times it screws up too, so i get 10x more frustrated but I didn't want this to become a phone i'm constantly flashing and its already happening because it wasn't made right in the first place. Anyone with lag fix able to post a backup they might have made? I'm just looking for solutions, and easier ways to get there.
Plus maybe i'm just biased but creating an EXT? I thought those days were over when I cashed in my G1. I just dont understand how using an ext on your SD can be faster than storing the data internally.
joe.kerwin said:
Plus maybe i'm just biased but creating an EXT? I thought those days were over when I cashed in my G1. I just dont understand how using an ext on your SD can be faster than storing the data internally.
Click to expand...
Click to collapse
Read the linked thread above and you'll learn. It's pretty simple.
MTC44 said:
Read the linked thread above and you'll learn. It's pretty simple.
Click to expand...
Click to collapse
So I need to create an EXT partition first before flashing the above mentioned ROM? What are the recommended settings if any for size? And I partition through clockwork orrrr? I know there's probably an answer for all these questions but between people using UK firmware/unfamiliar terms I don't want to jump into anything without missing a step.
Just go to the userinit thread and apply it... No need to flash a whole rom... Just partition your sd and flash the zip...
I ran jf rom on my g1 for like 2 months before a rom that dramatically changed anything...
We were so gracious for just that... Be patient this is new hardware.. Look at the international development section... We have made a lot of progress in 3 weeks..
Sent from my SGH-T959 using XDA App
Why waste time asking questions when you can answer them yourself?
All~G1 said:
Why waste time asking questions when you can answer them yourself?
Click to expand...
Click to collapse
I dunno, why waste time posting that question when you can simply read on if you have no advice? The strange things we do. And yes it is new hardware, hence why I ask these questions before I dive into something I'm unfamiliar with. Id rather ask questions and wait than waste hours trying to get my phone to turn on again after jumping the gun. My question that still stands is with the partitioning. With my g1, it was cut and dry on Amon Ra, did it right in recovery, so is there anything like that for us vibrant owners? I've never used ADB or anything of that nature, so I come from a download and flash world, so excuse my unfamiliarity and please dont take it as me complaining that it's not easy enough to do.
Look how long it took for the g1 to get where it is at now? Eventually it will come. You think your the only who would like to have a lag free rom? If you would have done some reading on the development side, you would have noticed there were a couple of fixes and also some progress. Ask questions on those threads over there as far as the speed and if it will suit your needs.
joe.kerwin said:
I dunno, why waste time posting that question when you can simply read on if you have no advice? The strange things we do. And yes it is new hardware, hence why I ask these questions before I dive into something I'm unfamiliar with. Id rather ask questions and wait than waste hours trying to get my phone to turn on again after jumping the gun. My question that still stands is with the partitioning. With my g1, it was cut and dry on Amon Ra, did it right in recovery, so is there anything like that for us vibrant owners? I've never used ADB or anything of that nature, so I come from a download and flash world, so excuse my unfamiliarity and please dont take it as me complaining that it's not easy enough to do.
Click to expand...
Click to collapse
Learn ADB if you want to hack a Vibrant. Without a keyboard, we can't do shells in recovery without it. There are tutorials, so I won't repeat them. Logcat is also very useful and low level devs won't be able to help you if you run into problems and can't provide a log.
Partitioning. DO NOT USE CLOCKWORK/ROM MANAGER. Right now it will partition the phone's INTERNAL flash, which is cause boot loops and you will have to Odin flash the phone back to stock to make it boot again. Use a computer and a card reader with Paragon, Gpartd, etc.. Or a G1 with Amon RA, or adb shell into clockwork recovery and use fdisk.
EXT size, doesn't really matter. You don't need a ton. I use 1GB and it's using about 180MB. For EXT type, use ext3 with the stock kernel, or, if you install JACs kernel, ext4 is faster and more reliable.
Note that partitioning on the phone in recovery via fdisk won't format the partitions. Flash my e2fsprogs ZIP file in JACs kernel thread for the versions that support ext4.
Before you start messing with this stuff, download the stock Odin flash files from the thread in development. If you mess something up, you can get back to stock. You should also get ADB and the Samsung drivers installed. Then get Titanium backup and make backups. When you install Clockwork, do a nandroid as well. Backups are GOOD.
Keep in mind, we are in the early stages of learning how to hack on these phones. We won't get to the level the G1 is at for a while. Go read the threads in the G1 dev forum from a year ago and you will see a lot of recommendations for learning adb, partitioning manually, and all the other stuff we are doing here on the Vibrant. It's a process. If you want flash and forget, you need to wait a while still. We're working on it, but we aren't there yet. This is new hardware and a whole new way of doing things.
ttabbal said:
Learn ADB if you want to hack a Vibrant. Without a keyboard, we can't do shells in recovery without it. There are tutorials, so I won't repeat them. Logcat is also very useful and low level devs won't be able to help you if you run into problems and can't provide a log.
Partitioning. DO NOT USE CLOCKWORK/ROM MANAGER. Right now it will partition the phone's INTERNAL flash, which is cause boot loops and you will have to Odin flash the phone back to stock to make it boot again. Use a computer and a card reader with Paragon, Gpartd, etc.. Or a G1 with Amon RA, or adb shell into clockwork recovery and use fdisk.
EXT size, doesn't really matter. You don't need a ton. I use 1GB and it's using about 180MB. For EXT type, use ext3 with the stock kernel, or, if you install JACs kernel, ext4 is faster and more reliable.
Note that partitioning on the phone in recovery via fdisk won't format the partitions. Flash my e2fsprogs ZIP file in JACs kernel thread for the versions that support ext4.
Before you start messing with this stuff, download the stock Odin flash files from the thread in development. If you mess something up, you can get back to stock. You should also get ADB and the Samsung drivers installed. Then get Titanium backup and make backups. When you install Clockwork, do a nandroid as well. Backups are GOOD.
Keep in mind, we are in the early stages of learning how to hack on these phones. We won't get to the level the G1 is at for a while. Go read the threads in the G1 dev forum from a year ago and you will see a lot of recommendations for learning adb, partitioning manually, and all the other stuff we are doing here on the Vibrant. It's a process. If you want flash and forget, you need to wait a while still. We're working on it, but we aren't there yet. This is new hardware and a whole new way of doing things.
Click to expand...
Click to collapse
Thank you very much. Now this is a respectable response. i'll find some time next week to learn this ADB stuff.
joe.kerwin said:
I dunno, why waste time posting that question when you can simply read on if you have no advice? The strange things we do. And yes it is new hardware, hence why I ask these questions before I dive into something I'm unfamiliar with. Id rather ask questions and wait than waste hours trying to get my phone to turn on again after jumping the gun. My question that still stands is with the partitioning. With my g1, it was cut and dry on Amon Ra, did it right in recovery, so is there anything like that for us vibrant owners? I've never used ADB or anything of that nature, so I come from a download and flash world, so excuse my unfamiliarity and please dont take it as me complaining that it's not easy enough to do.
Click to expand...
Click to collapse
No one is asking you to take a chance on bricking your phone hard or soft. I was implying more that you could learn or develop your knowledge of what others have placed in front of you. Everything takes time, rather "wasting" it on a procedure you don't understand, "waste" it on learning it, then do it. You have everything you want to know right in front of you. If you searched and read hard enough you'd now be able to "answer the questions yourself" to where you understand it.
Oh and just to let you know there is a flashable "lag-free" Rom in the Dev forum. While its bare, it is still doing wonders on this phone!
@ttabbal- You're the man!!! Don't know how you do it... lol
could someone that doesn't mind walking me through the correct partitioning method and getting this rom to work at it's max.. send me a private message so we can talk through gtalk tonight?. Im a fast learner, just purchased an 8gb class 4 sd card. I want to be safe.
Pm sent
Sent from my SGH-T959 using XDA App
All~G1 said:
@ttabbal- You're the man!!! Don't know how you do it... lol
Click to expand...
Click to collapse
I'm glad my stuff has been useful to the community. I'm a little shocked to see it integrated into a ROM and a kernel so far.
As for how I do it, what's the quote about standing on the shoulders of giants? I learned a ton reading posts and scripts from Cyanogen, Firerat, Eugene, and many others. Combine that with running Linux boxes for a few years, and you pick up enough to contribute a bit. Most of what I'm doing is adapting G1 hacks to work on the Vibrant, but I'm glad people like them.
Now if we could just get Samsung to give us decent GPS and compass drivers, maybe a tasty Froyo?
joe.kerwin said:
How is it working for you?
Click to expand...
Click to collapse
Haven't tried it yet, my friend.
I'm using the patch mentioned above.
I am also using ADW instead of TouchWiz, which seems to help quite a bit.
junkdruggler said:
Pm sent
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
How beneficial is it to do this? Should I wait for better ROMs? I am nervous about rooting my device as many are defective after a week or two and need shipped back.
Not sure if this somehow can help in any form of development for the Bravo but I'll post it up. Just read on Android Central that Motorola is looking for 1,000 users to test Android 2.2 for Bravo owners. It does require you to register on their forums first and then fill out a registration form. My younger brother has a Bravo so I'm going to register with his device and maybe it will somehow help some developers on here. Here is the link to the info https://supportforums.motorola.com/thread/47978?tstart=0
thanks for the heads up. I missed the last one.
Thanks for the notification. I'm already registered for the MFN tho, doesn't look like there's more I can do.... Hopefully I'm not missing something.
Wow this is the best news. Lets hope att doesn't delay this one like the last one. I'm all signed up so just gonna keep an eye on my email from them. Thanks for the heads up!
Thanks for posting. Spread the word on this, let's make sure they get all 1000 slots filled asap! More testers = better final product.
Sent from my MB520 using XDA App
The already sent a response. Im in! No eta for anything yet.
Sent from my MB520 using XDA App
unroot
Is there a way to unroot for this phone? I'm just waiting on my notification, I'm afraid root will not allow the OTA update.
I got in! Received the email saying in a few days I'll get a download link where I can get the update. I was also wondering about unrooting.
Wouldnt the update unroot your phone for you? If we wanted we would root it again after the update.
Sent from my MB520 using XDA App
I have a Droid Incredible and from being in those forums I believe, and I can be wrong so don't quote me, we will still be able to update. What usually blocks the update is have Clockwork Recovery. Hopefully we can root after the update. Knowing Motorola they are probably going to patch it up. Then don't want people rooting their phones. I'm just hoping someone here can possible use this info and hopefully can port CWM for us.
zachthepack said:
Is there a way to unroot for this phone? I'm just waiting on my notification, I'm afraid root will not allow the OTA update.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=803682
Thank you
Sent from my MB520 using XDA Premium App
2.2.1 downloaded
I got the message from motorola this morning to download 2.2.1. 15 minutes later up and running. Did a quadrant check and I'm at 1190. Much faster and a lot smoother. The best thing, I was able to move 95% of my apps to the SD card. Freed a bunch of space.
71lemans1 said:
I got the message from motorola this morning to download 2.2.1. 15 minutes later up and running. Did a quadrant check and I'm at 1190. Much faster and a lot smoother. The best thing, I was able to move 95% of my apps to the SD card. Freed a bunch of space.
Click to expand...
Click to collapse
Where you rooted when you ran the update? I got the update but it keeps aborting. Trying to figure it out before contacting motorola
TPR300C said:
Where you rooted when you ran the update? I got the update but it keeps aborting. Trying to figure it out before contacting motorola
Click to expand...
Click to collapse
After it fails, touch the lower right corner of your screen, should show some text that might help you figure out what's going wrong.
heydabop said:
After it fails, touch the lower right corner of your screen, should show some text that might help you figure out what's going wrong.
Click to expand...
Click to collapse
It tells me but it shows error for /cache/Blur_Version...etc so its from their update. I see you on the MOTO forums heydabop
@heydabop the error you stating you are getting even after unrooting might be if you modified the phone to allow non-market apps. Did you leave that on? I'm trying to see if I can reverse that by going through the steps and changing the value again. Maybe that would work. I get a different error though
I get the same error message. I think it is because I have custom boot animation installed. I didn't save the original boot animation zip file like I should have. I have factory data reset and went and checked the field for non market apps and changed them back. "E: error in /cache/blur_version3.5.350.MB520.ATT.en.us.zip (status 7)". So if anyone has the original boot animation zip file they can give me I would appreciate it. You can pm me or email me. thanks
TPR300C said:
It tells me but it shows error for /cache/Blur_Version...etc so its from their update. I see you on the MOTO forums heydabop
Click to expand...
Click to collapse
There is probably an error above the the zip error, that points to a specific file. Don't mind the zip error, it's caused by the verification error, and doesn't actually indicate a problem with the zip.
MCFarmfresh said:
I get the same error message. I think it is because I have custom boot animation installed. I didn't save the original boot animation zip file like I should have. I have factory data reset and went and checked the field for non market apps and changed them back. "E: error in /cache/blur_version3.5.350.MB520.ATT.en.us.zip (status 7)". So if anyone has the original boot animation zip file they can give me I would appreciate it. You can pm me or email me. thanks
Click to expand...
Click to collapse
I'm making a copy of my boot animation including sound. My problem is that I deleted all at&t branded apps and didn't back them up. So can someone be kind enough and back them up and send them to me please
FIRST TRY... Edited system.img (KERNEL 2.6.36.3 only!!!)
WARNING: ONLY USE THIS IF YOU HAVE A BACKUP OF YOUR /DEV/BLOCK/MMCBLK0P3 IF YOU DONT HAVE ONE YET, MAKE ONE BY USING THIS:
IF FROM ADB:
ADB SHELL
SU
IF=/DEV/BLOCK/MMCBLK0P3 OF=/SDCARD/SYSTEM.IMG
IF FROM TERMINAL EMULATOR:
SU
IF=/DEV/BLOCK/MMCBLK0P3 OF=/SDCARD/SYSTEM.IMG
THIS IS A FUNCTIONAL FILE SYSTEM, I AM WORKING ON A CUSTOM ROM WITHOUT HAVING TO HAVE THE BOOTLOADER UNLOCKED.
THE ONLY THING THAT HAS CHANGED ON THIS SYSTEM.IMG IS THE BOOT ANIMATION (INSTEAD OF "ANDROID" IT HAS THE HONEYCOMB BEE) AND THE FONT HAS CHANGED ALSO...
AGAIN, THIS IS JUST A TEST, IT IS THE FULL FILE SYSTEM TO BE USED ON A DAILY BASIS BUT DOES NOT HAVE ANY OPTIMIZED FILES AT THIS TIME.
Alright, now that you have read the warning... download this file here:
LINK = http://www.megaupload.com/?d=1YZSDVZI = LINK
You can then push the file through ADB by typing:
dd if=/sdcard/blk0p3_sys.img of=/dev/block/mmcblk0p3
Post if it worked for you or if it did not, this will help me troubleshoot...
PLEASE MAKE SURE THAT YOU MAKE A BACKUP OF YOUR FILES FIRST!!! THIS FILE IS BASED ON USA MODEL 1.104.05_GEN1 ACER A500. I RECOMMEND TO TRY ONLY IF YOU HAVE HAD TO UNBRICK YOUR TABLET BEFORE. I DONT WANT TO MESS UP YOUR TABLET!!! YOU HAVE BEEN WARNED!!! JEJEJE
Please post if it has worked for you or if it glitched, I am currently in trial and error so... my tablet gets bricked 1-3 times a day because I am testing different things on the system images... hopefully, I can find a way to have root on the image or at least include:
1. File manager
2. ROOT or at least the Gingerbreak.apk already installed.
3. Terminal emulator
4. Custom background upon boot
As stated, it works for me but I have only 1 tablet so if you are daring enough, please dont hessitate to help me in getting this up and running...
I AM NOT A DEVELOPER SO PLEASE BARE WITH ME AS I AM TRYING TO LEARN AS I GO... JEJEJE
props to you!
u crazy.
I don't see any attachment or link...
Euclid's Brother said:
I don't see any attachment or link...
Click to expand...
Click to collapse
Sorry about that, i've updated the post... jejeje
Beta Rom
Applied your image & got the honeybee and very small print. no other changes notes, moving back to previous system image. still can not get updates due to Chinese ROM unbricking, but that will come in time.
tomlogan1 said:
Applied your image & got the honeybee and very small print. no other changes notes, moving back to previous system image. still can not get updates due to Chinese ROM unbricking, but that will come in time.
Click to expand...
Click to collapse
THANKS!!! this is what I am needing... at this time, there is NOTHING ELSE that has been changed on the file system... I am just testing making sure that my changes stick... I am hoping to be able to change some more things... As long as its working... I will continue changing things ... Until I can get an image that is worthy of "Custom ROM" status... jejeje
tomlogan1 said:
Applied your image & got the honeybee and very small print. no other changes notes, moving back to previous system image. still can not get updates due to Chinese ROM unbricking, but that will come in time.
Click to expand...
Click to collapse
Did you fix your issue if you haven't I'm on gtalk if you want help I pulled my hair out for 2.5 days before I fixed it
Sent from my A500 using XDA Premium App
cant figure out how to multiquote as clicking the buttons dont do anything.
but just look at "Crsdr37"'s post in general with the imgs and update zip to get back to stock and updates!!!
and to the person who made the IMG keep up the good work. im not gonna flash it and im happy with being stock and getting updates now ;D
Have you figured out how to apply the incremental updates to the img?
I suspect it's just replacing files, I'll look at it when I get to a PC.
Ive been away from my tablet today. I put the post up and went out tonight... jejeje
Thank you guys that tested my image... if it worked for you, THANKS!!! if ou didnt, then let me know what did not work...
THIS IS NOT NOT NOT AN UPDATED IMAGE, IF YOU CHECK THE DESCRIPTION, THIS IS A TEST IMAGE TO GET A CUSTOM ROM OVER TO THE ACER A500... I AM TESTING SO I WILL NOT ANSWER QUESTIONS ABOUT UPDATES... THAT IS FOR MY OTHER POST... SORRY PEOPLE.
Never did. Am back now on the EMEA version and going to wait until someone cracks the code. I have reflashed so much I can do it with my eyes closed.
i am going to try it as well nice thing you guys do
Great
Cheers man, !
So, pulling your system image from /DEV/BLOCK/MMCBLK0P3, then modifying it, then pushing it back works?
Let me try and understand here:
I thought the whole locked bootloader thing checked signatures on the images that are about to be loaded into memory, such as the image in /system.
According to this:
http://www.reddit.com/r/Android/comments/hkbf3/so_you_want_to_know_about_bootloaders_heres_the/
It says:
What does a bootloader do with digital signatures?
It uses them to check any update that passes through it.
So: dd any partition we want to modify, back it up in a safe place, mount the img we get from that, make changes within the img, and dd it back, = all good?
ie: signed bootloaders only have to do with installing update.zips on the sdcard?
Can someone clear this up for me?
Thanks!
Unfortunately, I don't know how to answer that... I have to make my changes through the tab and then pull the system.img. Everytime I make edits externally, my tablet crashes... That's why I'm in testing right now.
sorry guys, I'm not a developer so there are going to be some things I can't answer but if someone is willing to explain it, please do as it is a learning experience for us all... jejeje
Sent from my WP7 []D[][]V[][]D ARRIVE using Board Express
If you'd read my question before making an all-caps rude response you'd see that I was asking if you've made any headway into applying the updates, not if you had already done them.
netham45 said:
If you'd read my question before making an all-caps rude response you'd see that I was asking if you've made any headway into applying the updates, not if you had already done them.
Click to expand...
Click to collapse
Dude, chill man... You are right, your question does ask about headway for the updates but here are the facts:
You are asking about updates on a BETA Rom that is just in testing...
I took your question to be if the ROM file had the updates (My fault for sure). I was not yelling per say nor trying to be rude but rather making sure that people are aware this is in no way an updated image and should not be treated as such... THIS IS A TEST ROM and since your question was posted within its thread, I took it as if it was directed to the image itself and not toward me and my development...
Look, as stated, im not a developer man, this stuff is a little hard for me to do. I do apologize because I did not answer your question correctly/completely but as far as the comment... Its what I meant. jejeje
tomlogan1 said:
Never did. Am back now on the EMEA version and going to wait until someone cracks the code. I have reflashed so much I can do it with my eyes closed.
Click to expand...
Click to collapse
Have restored to complete US stock. Had a lot of problems related to SD cards, had to swap them out to avoid errors on the actual update.zip file, but am back to normal. Now if I can just keep my hands off until the 3.1 update comes out, or there is custom ROM...
mapaz04 said:
Unfortunately, I don't know how to answer that... I have to make my changes through the tab and then pull the system.img. Everytime I make edits externally, my tablet crashes... That's why I'm in testing right now.
sorry guys, I'm not a developer so there are going to be some things I can't answer but if someone is willing to explain it, please do as it is a learning experience for us all... jejeje
Sent from my WP7 []D[][]V[][]D ARRIVE using Board Express
Click to expand...
Click to collapse
That's what I've doing for a while now....I guess I should have shared xD
been installing custom fonts and trying to change some of the system settings from other customized roms directly from the tablet.
Instead of reflashing wouldn't it be easier to just provide the files to push into the tablet? just my 0.02
Yeah, I can provide files for you guys to install but what I was going for was an image that contained everything already setup so you can just flash it over ur old one allowing the "customization" to appear upon install/pushin the file... jejeje
Sent from my WP7 []D[][]V[][]D ARRIVE using Board Express
Here was my situation: when trying to boot the phone, it would go to the splash screen for a few seconds, then go to a black screen and vibrate 5 times. Had to pull the battery to escape. However, when booting after a battery pull with the charger in it booted just fine, but with no sd card recognition or usb/adb functionality. A factory reset and both htc's and verizon's tech support didn't fix it at all. I had this problem and there seemed to be no good guide on how to fix it so I decided to gather all the right sources in one place.
The reason it's messed up comes from the usb problem, which is why plugging it in lets it boot sometimes. So, contrary to all of tech support, fixing the usb is all you need to do to get it working same as usual again. I've outlined the steps below in the way I think makes the most sense, but read all of what I wrote to understand what you're doing before you start. The links are the specific instructions for each piece written by people smarter than me. I only take credit for figuring out what I needed to do and bringing all of their minds together in one place.
The Process
First thing is to see if you can get it booted. Best bet is to take out the battery and charger, hold down the power button for 10 seconds, then connect the charger and battery and boot. If you can't do that then your only option would be to try some fastboot adb trickery (which is over my head) or flash the stock rom in hboot from http://www.droidforums.net/forum/droid-incredible-hacks/95406-how-correctly-unroot-incredible.html. Note which radio you have (listed in settings -> about phone somewhere or on top of hboot) to get the right file. If you can get it booted then move to the next step.
To fix the sd card and usb go to http://forum.xda-developers.com/showthread.php?t=695243.
Fastboot is in the tools folder of the android sdk, not platform-tools like adb. To get the drivers working go to http://www.flexjunk.com/2010/05/01/installing-htc-incredible-android-sd-drivers/
UPDATE: To clarify: fastboot is a completely separate (although closely related) piece of software from adb. If you do not have "fastboot.exe", download it from http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/ and follow the instructions there. Or, you can just download the full sdk from google which should include adb and fastboot. I recommend the second option, but my hard drive can take the hit. (thanks BonzTM)
UPDATE: If you get an error saying "The Program can't start because AdbWinApi.dll is missing from your computer" you need to copy that file from platform-tools to tools, then it should work (thanks Jester1614).
If you had to reflash and lost root download z4root from http://forum.xda-developers.com/showthread.php?t=833953 and do a temporary root to be able to run the commands to fix the usb.
Once the sd card and usb are fixed then it should reboot with or without the charger plugged in. Now your phone is stable and will work with unrevoked again and you should be good to go!
Disclaimer
Note: This is what I experienced with my amoled incredible; in no way do I take responsibility for anything you do. If you try to blame me for bricking your phone I will enjoy a hearty laugh while salting my soup with your tears.
Worked great for me and saved me from the hassle of needing a new phone.
THANK YOU!
goblue13579 said:
here was my situation: When trying to boot the phone, it would go to the splash screen for a few seconds, then go to a black screen and vibrate 5 times. Had to pull the battery to escape. However, when booting after a battery pull with the charger in it booted just fine, but with no sd card recognition or usb/adb functionality. A factory reset and both htc's and verizon's tech support didn't fix it at all. I had this problem and there seemed to be no good guide on how to fix it so i decided to gather all the right sources in one place.
The reason it's messed up comes from the usb problem, which is why plugging it in lets it boot sometimes. So, contrary to all of tech support, fixing the usb is all you need to do to get it working same as usual again. I've outlined the steps below in the way i think makes the most sense, but read all of what i wrote to understand what you're doing before you start. The links are the specific instructions for each piece written by people smarter than me. I only take credit for figuring out what i needed to do and bringing all of their minds together in one place.
the process
first thing is to see if you can get it booted. Best bet is to take out the battery and charger, hold down the power button for 10 seconds, then connect the charger and battery and boot. If you can't do that then your only option would be to try some fastboot adb trickery (which is over my head) or flash the stock rom in hboot from http://www.droidforums.net/forum/droid-incredible-hacks/95406-how-correctly-unroot-incredible.html. Note which radio you have (listed in settings -> about phone somewhere or on top of hboot) to get the right file. If you can get it booted then move to the next step.
To fix the sd card and usb go to http://forum.xda-developers.com/showthread.php?t=695243.
Fastboot is in the tools folder of the android sdk, not platform-tools like adb. To get the drivers working go to http://www.flexjunk.com/2010/05/01/installing-htc-incredible-android-sd-drivers/
if you had to reflash and lost root download z4root from http://forum.xda-developers.com/showthread.php?t=833953 and do a temporary root to be able to run the commands to fix the usb.
Once the sd card and usb are fixed then it should reboot with or without the charger plugged in. Now your phone is stable and will work with unrevoked again and you should be good to go!
disclaimer
note: This is what i experienced with my amoled incredible; in no way do i take responsibility for anything you do. If you try to blame me for bricking your phone i will enjoy a hearty laugh while salting my soup with your tears.
Click to expand...
Click to collapse
u saved my life/phone i love u son
Perfect Solution!
Thanks Thanks Thanks +1
So...question: Does this mean if you had to reflash and are currently unrooted, that you have to wait for z4root to show up in the market. Because it seems there is no way to root aside from that, and without root no usb, and no usb no adb
sofocused715 said:
So...question: Does this mean if you had to reflash and are currently unrooted, that you have to wait for z4root to show up in the market. Because it seems there is no way to root aside from that, and without root no usb, and no usb no adb
Click to expand...
Click to collapse
Actually you can download it from the link I provided in my post to the xda page for it (http://forum.xda-developers.com/showthread.php?t=833953). Scroll to the bottom of the first post and in the attached files there is a version that works. That's what I did, and then you can run the usb fixing commands. Then it's just reboot, re-root, and restore.
Hope this helps.
This thread needs more attention.
This needs to be stickied(sp?) and maybe added to the Development section where it would most likely be looked for first.
If I've helped you, hit the thanks button!
As you can see by my post count I can't put anything anywhere, so if someone wants to move it feel free.
goblue13579 said:
As you can see by my post count I can't put anything anywhere, so if someone wants to move it feel free.
Click to expand...
Click to collapse
I re-worded your OP and posted it on another forum. I did credit you though. You are now famous.
Cool, thanks!
I wish I would have known this back in March when this happened to me! But then again my phone was S-ON and to get the USB fix to work you said you need root so I might have still been SOL.
brando56894 said:
I wish I would have known this back in March when this happened to me! But then again my phone was S-ON and to get the USB fix to work you said you need root so I might have still been SOL.
Click to expand...
Click to collapse
That is what the z4 root is for. You dont need s-off, just root. The things are going to s-on by themselves when something is trying to write to the misc, thus the misc brick. PITA brick if ya ask me.
doug piston said:
That is what the z4 root is for. You dont need s-off, just root. The things are going to s-on by themselves when something is trying to write to the misc, thus the misc brick. PITA brick if ya ask me.
Click to expand...
Click to collapse
Glad yall were able to make something of this. This is gonna save some people since warranties are finally running out. Hey Doug, I seen your thread over on AF. You did a very good job of writing that up.
Oh and thanks for the tiny little peace of credit, heh. Glad I could help 'point' the late and great dougpiston in the right direction on something, lol
wildstang83 said:
Glad yall were able to make something of this. This is gonna save some people since warranties are finally running out. Hey Doug, I seen your thread over on AF. You did a very good job of writing that up.
Oh and thanks for the tiny little peace of credit, heh. Glad I could help 'point' the late and great dougpiston in the right direction on something, lol
Click to expand...
Click to collapse
Late and great is an over statement. I am just a user like most here. I appreciate you taking the time to reply to my PM. I have been out of the Inc game for some time now so a little direction was very helpful.
Like I said I knew what had to be done but ADB kept ****ting itself, as soon as I read the OP and to use a terminal emulator I slammed my head on my desk.
So simple, I was spending all my time trying to get ADB to run that the idea of the usb being borked hadn't even crossed my mine.
This thread really does deserve more credit and to OP good on ya son. Well done.
Thank you goblue13579, wildstang83 and Doug Piston! My phone is totally functional once again.
Odd timing how the problem happened only 2 days ago on my phone, and coincidentally, a fix was hashed out in the same time period after all this time of it being unfixable.
I owe you all a beer! Thanks again!
doug piston said:
Late and great is an over statement. I am just a user like most here. I appreciate you taking the time to reply to my PM. I have been out of the Inc game for some time now so a little direction was very helpful.
Like I said I knew what had to be done but ADB kept ****ting itself, as soon as I read the OP and to use a terminal emulator I slammed my head on my desk.
So simple, I was spending all my time trying to get ADB to run that the idea of the usb being borked hadn't even crossed my mine.
This thread really does deserve more credit and to OP good on ya son. Well done.
Click to expand...
Click to collapse
Yea bud, even I use adb so much that I keep forgetting that there's emulators to use. Its just one of those things we never think about.
Even though it was really more dumb luck and excessive googling that got me to this solution, thanks! I'm glad my compilation has helped so many people. And honestly, it's the least I can do for all the help and goodies I've gotten from these forums and developers.
Happy modding!
What if the devise isn't rooted?
Let the phone sit for an hour with the battery out. Put the battery in after that, should be good
Sent from my 2.3.5 Incredible Obsession