Related
[Edit: I've now resolved this issue. Thanks to all who helped. Please see end of thread for my solution. I've made some edits below too. When things looked bad, the solution was to remove the microSD card, copy and load a more reliable PC36IMG.zip (there are a huge number out there), and only then could I use adb when the red triangle was present. Note that just renaming stuff randomly or worrying about the USB cable isn't a proper way to come up with a solution even though I did it also (and that may be the case for some units but it can't be the general problem or solution). I'd guess there's a huge amount of misinformation out there and some people may have tried random stuff but it looks like from playing with all this, there is a method to the madness of how phone and the adb communicate, as well as how the phone loads, and once you UNDERSTAND HOW that process, all this stops being so much of a black magic.
Note that the problem I had was because I used an outdated set of instructions. Here are the ones that worked for me in the end:
http://forum.xda-developers.com/showthread.php?t=829045
Thanks to all who did reply to my message.
]
--------
I've tried literally everything I've read to get out of my red triangle situation so please help if you can. This is not your standard "hold volume up and power button" response.
I was trying to get to root using the method at evo4g.me.
And I got a red triangle after the first application of the PC36IMG.ZIP. I then held the volume up and power button and, I get a blue lettered screen with 4 options:
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
Well, I've seemingly tried everything but I can't seem to get past this screen. I've pulled the battery out and rebooted, I go back to the above screen. Option 1 above gets me back to the same spot. Option 2 says it can't find sdcard/update.zip. I did option 3 but it does that and turns off and on and comes back to this same position. Even when I try to hold the volume button down. When I try to access this using adb, I get "device offline".
I can take the battery out, hold the volume down button, and then power on, and it takes me the through the same steps as before and I don't seem to have control over the choice of whether it should load the PC36IMG.ZIP file or not (i.e., the menu I see before it doesn't to be controllable by me).
So I'm at a loss. I really would like to finish this process and get to root, which shouldn't be too hard in my view but here I am.
I could move the SD card elsewhere and put an update.zip file on there but I'm not sure what to do here exactly so I can recover (and hopefully with root). Is this the correct thing to be thinking about? Move the SD card to another device, replace the .ZIP file, and then go from there? Is there a way to do this without moving the SD card?
[Edit: this is indeed what I did in the end. I found the correct PCIMG.zip file by trial and error.]
Thanks a lot!
BTW, I backed up all my apps on my sdcard so I should be fine right? I'm not sure what I'd need to do reinstall them.
[Edit: I lost some public keys, etc. with app reinstalls but I just had too many apps doing backups in different places and wasn't matching the right app restore to the right location in part.]
--
Backgrround: I'm new to the Evo 4G and in general new to doing stuff like rooting phones and the like, so please forgive me if my questions (or actions) or too naive. I have been using Unix systems all my life and Linux when there were fewer than 100,000 users of it (back in 1992-1993) and am extremely comfortable with it and do all my science (work) exclusively with Linux.
ramdom said:
I've tried literally everything I've read to get out of my red triangle situation so please help if you can. This is not your standard "hold volume up and power button" response.
I was trying to get to root using the method at evo4g.me.
And I got a red triangle after the first application of the PC36IMG.ZIP. I then held the volume up and power button and, I get a blue lettered screen with 4 options:
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
Well, I've seemingly tried everything but I can't seem to get past this screen. I've pulled the battery out and rebooted, I go back to the above screen. Option 1 above gets me back to the same spot. Option 2 says it can't find sdcard/update.zip. I did option 3 but it does that and turns off and on and comes back to this same position. Even when I try to hold the volume button down. When I try to access this using adb, I get "device offline".
I can take the battery out, hold the volume down button, and then power on, and it takes me the through the same steps as before and I don't seem to have control over the choice of whether it should load the PC36IMG.ZIP file or not (i.e., the menu I see before it doesn't to be controllable by me).
So I'm at a loss. I really would like to finish this process and get to root, which shouldn't be too hard in my view but here I am.
I could move the SD card elsewhere and put an update.zip file on there but I'm not sure what to do here exactly so I can recover (and hopefully with root). Is this the correct thing to be thinking about? Move the SD card to another device, replace the .ZIP file, and then go from there? Is there a way to do this without moving the SD card?
Thanks a lot!
BTW, I backed up all my apps on my sdcard so I should be fine right? I'm not sure what I'd need to do reinstall them.
--
Edits based on trying to fix this: when I do `adb devices`, I get:
List of devices attached
HT0B6HL05287 offline
--
Backgrround: I'm new to the Evo 4G and in general new to doing stuff like rooting phones and the like, so please forgive me if my questions (or actions) or too naive. I have been using Unix systems all my life and Linux when there were fewer than 100,000 users of it (back in 1992-1993) and am extremely comfortable with it and do all my science (work) exclusively with Linux.
Click to expand...
Click to collapse
That is the stock recovery you are seeing there, does it let you do anything at all in the bootloader? If you can get it into fastboot mode you can fix it from there.
I rooted using regaw's instructions also, and also got that damn triangle, lol. Pretty sure all I did was reboot to bootloader and let it update the PC36.img again to get out of it.
xHausx said:
That is the stock recovery you are seeing there, does it let you do anything at all in the bootloader? If you can get it into fastboot mode you can fix it from there.
Click to expand...
Click to collapse
Yes, I believe so. I can let the PC36IMG.ZIP reload again and then AFTER that I can say "no" to the update and then "no" to reboot devices and I can get into a menu that says:
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
HSB USB
From there I can select FASTBOOT and head into another menu that says:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Trying BOOTLOADER gets me through the same HBOOT cycle where the PC36IMG.ZIP is reloaded and asked to be applied. Trying REBOOT gives me a white HTC screen (unless I need to wait a while).
Thanks! I assume I need to pull the SD card out, load it on my computer through another source, and then remove the PC36IMG.ZIP file and then replace it with something else that I can use to get rooted? Or will just removing the PC36IMG.ZIP file do it?
I'm also looking to achieve root so if I am going to the trouble of removing the SD card and putting it back, I'd like to know if if there's another PC36IMG.ZIP that'll let me have a nice version of the HTC evo that is rooted.
--Ram
I know a few people who have recently purchased EVOs and they still have Hardware version 3 and Hboot .97
what versions do you guys have on your phones?
If the hboot is still .97 you can used unrevoked forever for a full root and nand unlock.
if higher there is a tutorial on these forums for Hboot 2.02.
chris66 said:
I rooted using regaw's instructions also, and also got that damn triangle, lol. Pretty sure all I did was reboot to bootloader and let it update the PC36.img again to get out of it.
Click to expand...
Click to collapse
How did you do it?
Tuffgong4 said:
I know a few people who have recently purchased EVOs and they still have Hardware version 3 and Hboot .97
what versions do you guys have on your phones?
If the hboot is still .97 you can used unrevoked forever for a full root and nand unlock.
if higher there is a tutorial on these forums for Hboot 2.02.
Click to expand...
Click to collapse
I have:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.02-0000
TOUCH-PANEL-ATMELC-03_16ac
RADIO-2.15.00.09.01
Oct 14 2010, 19:14:47
I assume the tutorial you're referring to is here:
http://forum.xda-developers.com/showthread.php?t=829045
But I'm not sure how to get out of this particular PC36IMG.ZIP (gotten from evo4g.me) and replace it with the PC36IMG.ZIP posted in the above URL above easily, since I can no longer access this device using adb. Unless I am missing something obvious.
Well, I'm learning a lot! Thanks!
I do agree having root on these systems will be fantastic. I don't understand why it's not just a ready option. Things like tethering, etc. should be a given and built into the $10 cost or something else of the network. I'd like to port things like csh on there, and have a powerful terminal like I can get in the Mac OS X. Is there any way this is possible at all? We can get bigger and bigger microSD cards right? An entire stripped down Linux system can fit in a few gigs (but I want to be able to use it as a phone too).
--Ram
Went backward in the directions.
This the whole post that I used, pretty sure I just went backward and started again, it did take a seemingly HUGE amount of time the first time thru flashing the PC36.img
http://forum.xda-developers.com/showthread.php?t=765496
PULL THE SD CARD and put the image on the root? , lol
chris66 said:
Went backward in the directions.
This the whole post that I used, pretty sure I just went backward and started again, it did take a seemingly HUGE amount of time the first time thru flashing the PC36.img
http://forum.xda-developers.com/showthread.php?t=765496
PULL THE SD CARD and put the image on the root? , lol
Click to expand...
Click to collapse
The instructions at the above URL are what I used to get to this place with the red triangle that I can't seem to get out of. I can no longer access the phone using adb so I can't push anything. I can't access the phone through my computer right now once it has become stuck at the red triangle, this is my main issue. No access. Nothing. It just says "error: device offline" no matter what I try.
You don't think the SD CARD strategy will work?
This is where I scared the **** outta myself.....
"If this doesn't work (ie the PC36IMG.zip does NOT load) backup all of your sdcard contents onto your computer, reformat your sdcard to FAT32, redownload the PC36IMG.zip, and drag and drop it onto the sdcard, then reboot into the bootloader and try again. This should fix the issue."
It worked for me, but I don't know what hardware version and all you have.
ramdom said:
The instructions are the URL are what I used to get to this place with the red triangle that I can't seem to get out of. I can no longer access the phone using adb so I can't push anything. I can't access the phone through my computer right now once it has become stuck at the red triangle, this is my main issue. No access. Nothing. It just says "error: device offline" no matter what I try.
You don't think the SD CARD strategy will work?
Click to expand...
Click to collapse
just pull the sd card out of the evo (behind the battery) and put the new img on the root of the card.
chris66 said:
This is where I scaref the **** outta myself.....
"If this doesn't work (ie the PC36IMG.zip does NOT load) backup all of your sdcard contents onto your computer, reformat your sdcard to FAT32, redownload the PC36IMG.zip, and drag and drop it onto the sdcard, then reboot into the bootloader and try again. This should fix the issue."
It worked for me, but I don't know what hardware version and all you have.
Click to expand...
Click to collapse
Me too, but I pay for the extra warranty that's supposed to cover nearly everything, which I think should cover this.
So from the above instructions, am I to understand that I remove the sdcard out and clean it out in my computer and install a new PC36IMG?
Should I try the one from here? Even here, there are like 3 versions:
http://forum.xda-developers.com/showthread.php?t=829045
Sorry for all the questions. Normally I'd hack and figure this out without even googling it but after googling it, the amount of stuff out there is enormous which is throwing me off. I think I have like 10 versions of the PC36IMG and not sure which to go with next that'll not destroy everything and give me root! Crazy.
Tuffgong4 said:
just pull the sd card out of the evo (behind the battery) and put the new img on the root of the card.
Click to expand...
Click to collapse
Thanks a lot. Pulling the evo card was easier than I thought it would be. Which particular one? I'm looking here:
http://forum.xda-developers.com/showthread.php?t=829045
Should I just manually copy all these files over to the sdcard and then reboot and see what happens? I guess I'll try that. Thanks.
Thanks guys!
--Ram
Well, I solved this problem and am now enjoying root. Thanks to all who helped. I followed the instructions here:
http://forum.xda-developers.com/showthread.php?t=829045
But I still couldn't get past step 10. I even read the FAQ and followed the renaming suggestions (this wasn't the issue but I did it anyway) and it still didn't work. Basically the problem was that I wasn't even able to get to the shell even though I was able to use adb to push files (weird?).
So I was playing around with the EVO-recovery.zip (http://www.knowyourcell.com/htc/htc-evo-4g/evo-4g-guides/463925/how_to_root_the_htc_evo_4g.html) and ran the recovery-linux.sh script, which then put me into the green recovery screen. The rest was straight forward after that (as per the instructions at the URL above). So perhaps the difference of which adb to use was what it was, since that zip file comes with its own adb.
I am now rooted. Now what?
My wi fi doesn't seem to work, and neither does the google wireless tethering app, which is one of the reasons I wanted to root. When I run "adb shell" I now get a "#" instead of a "$" so I assume this (among other things, including the S-OFF) means I am rooted. So no wi-fi, did I trash something?
[Edit: I fixed this by installing the fresh ROM; thanks chris66 and others who helped!]
I'm just using the stock ROM provided from the URL above. Not sure what the best one to use is and how to use it.
[Edit: Stil no idea. Way too many ROMs out there. It's crazy. Fresh seems to have a good rep. It works pretty well, after one week.]
I also backed up all my apps on my sdcard, is there a way to restore them in one quick fell swoop instead of opening them one by one?
[Edit: I figured out how to do the multiselection option and apply it apps. A good file manager will do the backups for you. I went from ASTRO to ES File Explorer. Latter looks slightly cleaner. Probably better ones out there.]
Thanks to all who helped! I am excited about playing around with all this further. Only PITA is reconfiguring everything again the way I like it.
[Edit: Favourite apps are ConnectBot; Android Wireless Tether; AndroidVNC; DropBox; ES File Explorer; System Panel; --- from Ubuntu, I ADB to access stuff at the prompt which when having a # is really really powerful. Maybe I was wrong but before I put the new ROM on I didn't think the "more" command was available.]
Cool, try superuser and the wifi app from the market. Flash almost any of the newer roms, and they're already both usable, wifi and usb.
Sent from my PC36100 using XDA App
[DISCLAIMER] Images are provideded "as is", use at your own risk!
[NOTE] This project is no longer maintained!
Quite a few people seem to end up in non-bootable-states (myself included) when trying to root/app/tweak etc..
So I made a couple of images that will help you trigger Factory Restore on your Nook Simple Touch.
Compability:
Nook Simple Touch - [1.0.0], [1.0.1], [1.1.0]
Requirements:
- A microSD card of atleast 128MB of size (existing data will be lost)
- Make sure your NST is charged! A failed root will drain your NST quickly without you noticing it!
Tools:
- Windows: win32 Disk Imager
- Linux: d'uh .. dd
- Mac: diskutil and dd
Still unsure about tools?, look here
Versions: (You only need one of these depending on how messed up your NST is. Try 0.1 first!)
- Version 0.1 [Without boot partition restoration] n2T-Recovery_0.1.rar (2MB)
- Version 0.2 [With boot partition restoration] n2T-Recovery_0.2.rar (16MB)
Usage:
- Uncompress the image
- Write the image to your mSD card with one of the tools listed above.
- Power up your Nook Touch with the mSD card inserted.
- Follow the instructions displayed on the screen.
If all went well you should see the factory restore screen popping up in 10-20 seconds after reboot, and you'll be back to the version your NST was originally shipped with* when it's finished.
If it doesn't, please share your "detailed" story in this thread and feel free to PM me, I've restored quite a few "hopeless" cases
[*] Factory Restore doesn't wipe your /data
Update:
26.11.2012 - Added new download links
28.01.2012 - Moved files to new server
Changelog:
[0.1]
- Initial release
[0.2]
- Rewrites boot partition before triggering Factory Restore
Credits:
- Based on Nook Simple Touch 1.0.0 boot partition
- Made possible by Noogie image by nookDevs
Scary!
But good solution when everything else fails. Thanks!
apeine said:
Scary!
But good solution when everything else fails. Thanks!
Click to expand...
Click to collapse
Nothing scary about it, it only writes to a single file on your N2 to trick it into believing there has been 8 missed boot attempts.
That is good to know, because timed things on smartphone and the like is a usual way to messy results. Try putting an iphone in DFU mode in order to jailbreak it...
apeine said:
That is good to know, because timed things on smartphone and the like is a usual way to messy results. Try putting an iphone in DFU mode in order to jailbreak it...
Click to expand...
Click to collapse
Ah I see your point, but there's really no timing involved with this process.
Cleaned up the instructions a little, thank you.
Did Not Completely Restore, But...
I was able to restore by the following:
1. Tried your method on a rooted (1.00 FW) Touch but it seemed to hang on the last bit of rebooting.
2. I wrote the factory 1.01 update to an SD card using Winimage, turned the Touch off, put the SD Card in, turned the Nook on, let it go to sleep (per BN Instructions for applying update) - it woke up, applied 1.01 and unrooted simultaneously.
3. Reregistered and rerooted using ManualNooter.
docfreed said:
I was able to restore by the following:
1. Tried your method on a rooted (1.00 FW) Touch but it seemed to hang on the last bit of rebooting.
2. I wrote the factory 1.01 update to an SD card using Winimage, turned the Touch off, put the SD Card in, turned the Nook on, let it go to sleep (per BN Instructions for applying update) - it woke up, applied 1.01 and unrooted simultaneously.
3. Reregistered and rerooted using ManualNooter.
Click to expand...
Click to collapse
do you have a link for the .img for the update? I only found a zip file, not sure how to use Disk Imager to put that on there.
But yeah, I'm experiencing the same issue, hangs on the reboot part.
docfreed said:
I was able to restore by the following:
1. Tried your method on a rooted (1.00 FW) Touch but it seemed to hang on the last bit of rebooting.
Click to expand...
Click to collapse
wajanus said:
But yeah, I'm experiencing the same issue, hangs on the reboot part.
Click to expand...
Click to collapse
Not sure what you guys mean by "rebooting part" can you be a little more detailed?
docfreed said:
2. I wrote the factory 1.01 update to an SD card using Winimage, turned the Touch off, put the SD Card in, turned the Nook on, let it go to sleep (per BN Instructions for applying update) - it woke up, applied 1.01 and unrooted simultaneously.
Click to expand...
Click to collapse
I have never seen or even heard of a 1.0.1 update image.
The 1.0.1 update is distributed as a zip file that has to be saved on the Nooks internal storage trough usb. This makes no sense to me.
docfreed said:
3. Reregistered and rerooted using ManualNooter.
Click to expand...
Click to collapse
Again this makes no sense, ManualNooter is for Nook Color ..
ros87 said:
Not sure what you guys mean by "rebooting part" can you be a little more detailed?
I have never seen or even heard of a 1.0.1 update image.
The 1.0.1 update is distributed as a zip file that has to be saved on the Nooks internal storage trough usb. This makes no sense to me.
Again this makes no sense, ManualNooter is for Nook Color ..
Click to expand...
Click to collapse
Answers -
1. By "hanging" I meant it's stuck on the last little bit of writing the restore img - never quite finishes.
2. Just go to BN site and you can download "update.zip 1.01" for the Touch - it gets applied by placing on the root of the internal memory and booting up
3. My Bad - I meant TouchNooter
docfreed said:
Answers -
1. By "hanging" I meant it's stuck on the last little bit of writing the restore img - never quite finishes.
Click to expand...
Click to collapse
Ok, so the factory restore got triggered but didn't complete, wonder why.
Did you try to trigger restore again?
I'm gonna look into adding more advanced recovery options to the tool.
docfreed said:
2. Just go to BN site and you can download "update.zip 1.01" for the Touch - it gets applied by placing on the root of the internal memory and booting up
Click to expand...
Click to collapse
Yes I know, but you said you wrote it to sdcard with winimage, which didn't make any sense
The only way I can get my nook to boot into a usable environment is by way of a touchnooter bootable mSD. I managed to move the 1.0.1 update onto the NOOK patition, but I had to boot off of a noogie SD (for some reason, USB mode doesn't work when I boot off of touchnooter)to do so. Even after letting it go to sleep, it doesn't seem to recognize that there's an update. I have no clue what to do.
EDIT: Tool is a lifesaver.
mrmystery96 said:
The only way I can get my nook to boot into a usable environment is by way of a touchnooter bootable mSD. I managed to move the 1.0.1 update onto the NOOK patition, but I had to boot off of a noogie SD (for some reason, USB mode doesn't work when I boot off of touchnooter)to do so. Even after letting it go to sleep, it doesn't seem to recognize that there's an update. I have no clue what to do.
Click to expand...
Click to collapse
I've replied to your PM.
Thanks for this img. Accidentally powered off the Nook with a core android file missing and when I turned it back on, I was stuck on a looping 5-dot start up screen. This gave me a very easy way to fix it and didn't really erase anything, either. The TN stuff was gone, but every app I'd installed myself after rooting with TouchNooter remained, as did my launcher and setup, etc.
Glad to hear it worked for you
I also have new version under testing that will help people with more severe problems.
mrmystery96 a few posts up had a completely broken boot partition after some app/mod tried to write its recovery there.
He got a development copy from me last night and he was able to successfully restore his Nook Touch, so I should be able to release it in a day or two.
How long is it generally expected to take? I'm just looking at a blank (but backlit) screen with your sd image.
I dd'd the file to the root of the sd card (/dev/sdc), not any partition. Is it supposed to be on a partition?
kkinder said:
How long is it generally expected to take? I'm just looking at a blank (but backlit) screen with your sd image.
I dd'd the file to the root of the sd card (/dev/sdc), not any partition. Is it supposed to be on a partition?
Click to expand...
Click to collapse
Backlit? There's no backlight on the Nook Simple Touch
Ciao, I have a problem...
I rooted my nook, it was working, but it seems to me slower when it opens a book, and sometimes it crashes opening a book.
So I would like to restore.. I saw your post: fantastic!
I downloaded the image, i copy ect i followed all the instructions..
I extract the sd, it start to restoring to original factoring... but after that my nook was like before
with android and also my old books...
I would like to "unistall" android... that's all, could you help me?
gioranaa said:
Ciao, I have a problem...
I rooted my nook, it was working, but it seems to me slower when it opens a book, and sometimes it crashes opening a book.
So I would like to restore.. I saw your post: fantastic!
I downloaded the image, i copy ect i followed all the instructions..
I extract the sd, it start to restoring to original factoring... but after that my nook was like before
with android and also my old books...
I would like to "unistall" android... that's all, could you help me?
Click to expand...
Click to collapse
The built in "Factory Restore" doesn't wipe everything, it just restores important parts of your system.
If you want to clean your NST you can boot it while pressing both left and right bottom buttons (it will trigger Factory Reset (not restore))
If you want your NST absolutely 100% clean, I'm sorry to say that you should have made a backup before rooting it
ros87 said:
The built in "Factory Restore" doesn't wipe everything, it just restores important parts of your system.
If you want to clean your NST you can boot it while pressing both left and right bottom buttons (it will trigger Factory Reset (not restore))
If you want your NST absolutely 100% clean, I'm sorry to say that you should have made a backup before rooting it
Click to expand...
Click to collapse
no back up...
do you know where I can find a clean one?
do you think it is possible to clean everyhitng unpdating to the 1.01 clean version?
I understood: I have to push the power button, THEN both left and right bottoms button, in order to reset.
gioranaa said:
no back up...
do you know where I can find a clean one?
Click to expand...
Click to collapse
You can't.
Every NST contains unique data so it's not possible to make a generic restore image. It is possible to make one customised to your NST tho, I've made a few of those.
gioranaa said:
do you think it is possible to clean everyhitng unpdating to the 1.01 clean version?
Click to expand...
Click to collapse
No
gioranaa said:
I tried to boot (from power off state) while pressing both left and right bottoms button, but it didn't wake up: i pushed for more than 5 sec power button while i was pushing left and right but nothing happened.. could you help me?
Click to expand...
Click to collapse
Just press the power button until you see the screen flicker, then immediately press and hold those buttons until you see the "Factory Reset" screen, then follow the instructions on the screen.
What is it and why am I getting this prompt? I'm rooted with 2.3.4
Obviously I shouldn't accept this update but does anyone know what this is?
Sent from my Xoom using xda premium
Hi. I am new.
I just installed the ROM 2.3.4 last night that was posted in the xda forum(upgraded manually from 2.2 on a Unrevoked rooted Dinc).
I installed the 4.06 ROM and I am reading the official was 4.08...
Do I need another upgrade? Or is this 'the' upgrade that is for root users?
Not trying to steal your post ugxvibe. both of our questions might have similar answers.
if you update will you lose root control? What about all the apps? I'm most concerned about not being able to tether...
Just flash wildstangs 4.08.605.2 ota rom. It is the newest ota update, but already rooted.
how do I do that? Through rom manager?
Is there a way to stop the update reminder from popping up without actually installing it? I'm afraid I might mess up my phone and don't want to risk losing everything g on it.
Guys, to stop the prompt from appearing just press install and it will try to reboot but will just error and u will never see it again trust me .
Sent from my HTC Droid Incredible using xda premium
d-pabs said:
how do I do that? Through rom manager?
Is there a way to stop the update reminder from popping up without actually installing it? I'm afraid I might mess up my phone and don't want to risk losing everything g on it.
Click to expand...
Click to collapse
Yes thru rom manager.
You can dissable the notifications by editing your /system/build.prop file. Look for:
ro.config.htc.nocheckin = 0
and change the 0 to a 1. If you dont see that line add it somewhere in the file.
I went to make the nocheckin = 1 modification, but I already had it, and I'm still getting the update notifications. Not even sure how it got there. All I've done is root with Unrevoked, maybe that does the edit?
NetGoo said:
I went to make the nocheckin = 1 modification, but I already had it, and I'm still getting the update notifications. Not even sure how it got there. All I've done is root with Unrevoked, maybe that does the edit?
Click to expand...
Click to collapse
It should have worked, you may need to clear the cache partition. Or there is another method go to /etc/security and rename otacerts.zip to otacerts.zip.bak
Like what was said above...
If you have Clockwork or some other custom recovery, if you just allow it to update when prompted, it will not install and will cause no other problems. You must have the stock recovery in order for the update to install.
It CANNOT install if you don't have the stock recovery.
But, I would also go into the /cache directory and find the update file and zap it (It will be obvious). I just use ADB and "rm" it from my PC. You could use root explorer or something. Otherwise you will have a big update file just sitting there and hogging space.
cmlusco said:
It should have worked, you may need to clear the cache partition. Or there is another method go to /etc/security and rename otacerts.zip to otacerts.zip.bak
Click to expand...
Click to collapse
I found the file thru root explorer but cannot change it due to message that says it's read only. other options?
Thanks.
bgtruitt said:
I found the file thru root explorer but cannot change it due to message that says it's read only. other options?
Thanks.
Click to expand...
Click to collapse
At the top of the screen in Root Explorer, change r/o to r/w. Then make your change.
Sent from my ADR6300 using xda premium
im rooted n using the clockworld mod for roms, I attempted to run the 4.08 update from User wildstang following the instructions but after installing the update n rebooting it just sits at "Dorid incredible" white screen and never boots. I may be doing something wrong here, can someone break it down for me? suggestions?
NOTE: I use CWMR 5X. Some wipe options below are not included in earlier recovery versions. Still wipe what is available the best you can.
1. Put the Rom on the root of your SD Card
2. Compare MD5 Sum
Windows: MD5 Calculator
LINUX: Open Terminal and type: md5sum [path to the rom on your sd card]
Mac: Open a terminal and type: md5 [path to the rom on your sd card]
3. Reboot to Recovery
4. Wipe these:
Main Screen:
wipe data/factory reset - x2
wipe cache partition - x2
Advanced:
Wipe Dalvik Cache - x3
Wipe Battery Stats - optional
Mounts and Storage:
Format-
/boot - x2
/system - x2
/datadata - x2
/data - x2
/cache - x2
5. Install Rom from SD Card by going back and selecting install from SD card.
6. Reboot and enjoy!
followed each step to the letter but still wont boot : /
Ok i changed nothing in the method of installing the rom and for whatever reason it worked!! 4.08 now phone is 10X faster and im loving it. Only issue i see now is i cannot get back into clockworld mod! why is that? i hold down power and vol down for a long time and when release it just starts the boot sequence any suggestions?
clutchdroid said:
Ok i changed nothing in the method of installing the rom and for whatever reason it worked!! 4.08 now phone is 10X faster and im loving it. Only issue i see now is i cannot get back into clockworld mod! why is that? i hold down power and vol down for a long time and when release it just starts the boot sequence any suggestions?
Click to expand...
Click to collapse
Uncheck fastboot in menu > applications.
Thank you sir.
clutchdroid said:
Ok i changed nothing in the method of installing the rom and for whatever reason it worked!! 4.08 now phone is 10X faster and im loving it. Only issue i see now is i cannot get back into clockworld mod! why is that? i hold down power and vol down for a long time and when release it just starts the boot sequence any suggestions?
Click to expand...
Click to collapse
I had the same problem, but after two times running the install its still getting the hang. Hopefully I'll get better luck on try #3.
Did you figure out what caused the temporary issue?
spitzaf said:
I had the same problem, but after two times running the install its still getting the hang. Hopefully I'll get better luck on try #3.
Did you figure out what caused the temporary issue?
Click to expand...
Click to collapse
I may have missed a format inside mounts and storage make sure you hit them all.
cmlusco said:
Yes thru rom manager.
You can dissable the notifications by editing your /system/build.prop file. Look for:
ro.config.htc.nocheckin = 0
and change the 0 to a 1. If you dont see that line add it somewhere in the file.
Click to expand...
Click to collapse
OK I've found the file you're talking about and it doesn't have that line in it so I need to add it. I can't easily get access to a computer right now to run the command line on my phone so i have been trying to use the terminal emulator instead. It says I doesn't have a text editor...is there a way to edit via the emulator? Do you wkno which commands to use?
Thanks again
Yep, still having a minor issue with this. I have added the line suggested and I have cleared my cache yet I still get periodic prompts to install the update. I'm not really keen on doing so. Can anyone else suggest a way to stop the (weekly) prompts?
Thanks
Since the information for this device is so fragmented, I decided to attempt to keep it all in one (or a series of) posts. I aim to link to the original posts as well as outline what do to with your device from the time it leaves to box to running the latest and greatest modified rom or CM9 or whatever else is out there. I will not link directly to anything, rather I will link to the thread, and I very seriously recommend reading at least the post, if not the thread, before you begin ANYTHING.
This guide is a work in progress, it is not complete, and I will work on it bit by bit until it's completed!
Section 1: So its shiny and new...how can I MOD IT?
This will be assuming the new shiny toy in question is indeed an Acer Iconia Tab A100, this is not meant to cover any other devices. And, this is assuming it's coming with Honeycomb installed, in stock form. If its used, or comes with ICS, the next section will amuse you.
First thing most users that want to mod their devices do is root their device. Now, rooting is not unlocking, as carrier unlocking is not boot loader unlocking. Rooting a device allows you to access the system in a much more in depth manner, including read/write (R/W) access to the /system partition, among other things. It allows use of programs such as Titanium Backup (TB or TiBu) ROM Toolbox, overclocking or other clock setting utilities such as SetCPU or CPU Master for overclocking (if the kernel supports it) underclocking and undervolting.
So...how do I do that rooting thing? Well assuming you are running Honeycomb and are wanting to update to ICS plus root and unlock the bootloader, we will use the info from this thread Simple Root Method by ZeroNull to update you to ICS and then gain Root access on that new ICS install!
What about rooting Honeycomb? Well most users are already running ICS and prefer it, and those on Honeycomb are likely wanting to update to ICS, so I will leave this out for now. If I have the time I will come back and include the link for that as well.
Now, ICS is installed, and you're rooted, what else can I do? Well you can unlock your bootloader, and load up a custom recovery such as CWM or TWRP and using those, install Custom ROMS! For this, we visit this thread here Install unlocked bootloader by ZeroNull. Follow ALL directions in this thread for a fully unlocked bootloader!
Custom recoveries, what are they and how do I get that shiz? Custom recoveries, CWM and TWRP, allow the user to flash anything they want, provided its for their device and properly packaged. This included custom roms, some tools, and allows you to "wipe" various parts of the device's storage and backup/restore to a previous installation. Powerful, and dangerous, do not go pushing buttons to things you do NOT understand! Also, you MUST delete or rename /system/etc/install-recovery.sh prior to flashing recovery! This will restore stock recovery every time android boots, wiping out your custom recovery. The only time you want that file there is if you are using the crossix mount swap mod, which replaces that file with a modified version that leaves recovery alone.
Safe to do wipe:
Wipe cache, data, dalvik cache, system. Theonew also reports Flex and boot can be wiped as well as SD-EXT. This is not to be confused with External SD, this is a separate partition on your External SD card, wiping it will NOT wipe external SD, only what's installed on that partition, the rest is safe and requires a separate wipe.
If you wipe system you MUST install a new rom or restore from backup!
If you wipe boot please restore or install a new ROM before rebooting! Safety first.
Not safe to wipe:
Don't wipe anything else, and always install a new rom or backup after wiping system!
Never reboot system after wiping without first restoring or installing a new ROM!
Post 2 will cover custom recovery functions in more detail, for both recoveries.
Now that you have an unlocked bootloader, what can I do? Install that custom recovery! There is two flavors, CWM and TWRP, CWM available here CWM Recovery by ptesmoke. Follow the instructions in this post to the letter! Only attempt this after you have ICS, rooted, and unlocked the boot loader correctly! Next we have TWRP Recovery here TWRP Recovery by ZeroNull. Again, follow the instructions to the letter, and attempt only after ICS, root and unlocked boot loader are finished.
Ok, gots me some custom recoveries, what about custom roms? This is why we just did all that work, to prepare for this! Custom ROMs! I'll be listing some (all?) ROMs that you can use, besides stock HC and ICS.
The list in order of version, oldest to newest, updated to retired:
4.0.3
KEBBERSROM by Hardslog Stock based 4.0.3
Flex Reaper by civato ICS 4.0.3 Modified Stock
Green ICS by lgcmn & ZeroNull ICS 4.0.3 Modified Stock
4.0.4
KEBBERSROM SHELLSHOCK by Hardslog 4.0.4, based on A500 and A700 ROMs
Nightly Builds of CM9 by pio_masaki ICS 4.0.4
Aoikaze Modified CM9 by pio_masaki ICS 4.0.4
4.1.1
CM10 Preview builds by waydownsouth 4.1.1
4.1.2
Unofficial CM10 builds by pio_masaki (stock and modded, Phone UI and Tablet UI)
Jellytime Sosei by pio_masaki Jellybean 4.1.2
Cyanosaki_Flex by Hardslog
4.2.2
CarbonROM JB 4.2.2 Unofficial by pio_masaki
These are most of the ROMs. There are others that seem to no longer be in active development and are based on the old leaks that vache was kind enough to grab for us. Development is currently only active in the KEBBERSROM builds by Hardslog, and occasional updated in the CM10 builds by pio_masaki.
That ends Section 1, preparing for awesomeness, and Post 2 will continue with installing your new custom ROM!
Section 2: Recoveries and what they can do for you.
This section will cover recoveries and what they can do, and how to do it. I will be starting with TWRP, as I use that on all of my devices, and after that I will include a CWM section, as a lot, if not most, use that. They are similar in what they do, but different in where things are.
TWRP Recovery
Official TWRP for A100 by linuxsociety
This assumes you have already done everything in section 1, including installed ICS, rooted it, unlocked your bootloader, and installed TWRP custom recovery. Links for this information is provided in Section 1, in the post above.
First thing you should ALWAYS do when you enter recovery, before doing ANYTHING ELSE, is make a nandroid backup!
Getting into recovery: Depending on what ROM you use, this is done a couple ways. First is an AOSP ROM, like CM9/AOKP, which you can hold the power button, then select Reboot, then Recovery. In modified stock or rooted stock ROMs, this menu doesn't exist, you can either use an app like Quick Boot, and select recovery, or power off, then hold the Volume - key (closest to the rotation lock switch) and while holding it, hold power, once the acer screen comes up and starts saying Recovery kernel, release both and recovery will boot provided an update.zip is NOT on the root of your external SD card. This method works for any ROM.
Now I'm in recovery, what do I do? As I mentioned, make a nandroid backup before you do ANYTHING else! From the first screen (home screen) in TWRP select Mount. In mount you can leave everything alone and at the bottom will be two options with Circles. Select Using external SD Card for Backup. This will store your backup on your external SD card, never use internal SD if possible. After you select use external SD, press the Home button in the upper right corner. Now, back on the Home screen, select Backup. Double check the boxes checked are System, Data, Boot and Recovery. At the bottom is a nice little slide bar, slide that over and sit back. Takes about 4-5 minutes depending on how full your device storage is. This does NOT backup internal SD! After this is done, you have created a nandroid backup that when restored will put the system exactly how it was last time you used it. You can make multiple backups of multiple ROMs without issue, just however big your SD card is to hold them.
The restore menu, or the OOPS SAVE MEH menu is your best friend. This will restore you back to the last state your device was in for the backup that is restored. By default TWRP saves by date and time, however you can rename this with any file manager, never caused me any issues. Theonew reminded me of an MD5 issue that can happen on renaming backups, if this does happen, rename it back to the stock naming system to fix it. Generally I'll just append the ROM name to the front, so instead of 2012-6-14--18-25-01 it'll be CM9-2012-6-14--18-25-01. Make sense? That way to restore it in case of error, just drop the name. Easy. Theonew also did some testing, and confirmed that spaces in the folder name WILL cause MD5 errors and fail the restore, please use ONLY dashes and underscores (- and _ lol) in the folder name! To restore make sure you are on the Home screen, then select Restore. In the window you will see a list of your current backups, select one. Next screen has check boxes, make sure System, Data, Boot and Recovery are checked, then slide the bar to begin. This takes a bit, make sure you let it finish! Once done, your system will be at the last point it was used for that backup.
Advanced restore...I'm to lazy to reload and reset up my stuff after a ROM flash, so this is the fast and dirty way of doing it. If you flash a ROM and you don't feel like manually restoring your apps, you can uncheck System, Recovery and Boot, and leave only Data checked. This will restore your user installed apps and settings over the current ROM install. I don't recommend this for different ROMs, only for updates of the same ROM! Up to you but if you get alot of issues, you'll know why. After advanced restoring, go to the Home Screen and select Advanced, then Fix Permissions. Press Home again and select Wipe. Wipe Cache and Dalvik Cache, then reboot system.
Alright, enough already lets get our flash on! From the Home screen, select Wipe, then press on Cache, Dalvik Cache, Factory Reset, and System. Optional you can wipe Battery Stats if your battery seems off. Leave the rest alone. Once these are all wiped, go back to the Home screen, and press Install. The window on the left is your device folders, window on the right is contents of the current folder. I hope you remembered where your rom.zip is, because you select it here. Press on the zip for the ROM of your choice, then slide the bar to flash it. After that is done, select the left button Wipe Cache and Dalvik, then select Reboot system.
OK LETS ROCK THAT ROM! Woah, slow down scooter, there's a few things to do, or not do, first. After it boots, meaning it's past the boot animation and is sitting on the Welcome screen, set it down and leave it alone for 10 minutes or longer. Don't sign in, don't do anything, just leave it be for 10 minutes. If you can't think of what to do to manage the time you have to wait for awesomness of custom ROMs, read the thread of the ROM you chose. Set the thread for 50 posts and just read. After 10 minutes, hold the power key, and either choose Power off or Reboot, Reboot depending on ROM used. After it finishes rebooting (that was alot faster wasn't it?) you can go ahead and do the Welcome stuff, log in to Google, setup your device, download your apps, restore your apps etc. After restoring your apps (try not to restore app + data if possible, though I know games and stuff you'll want to) reboot one more time. After that second reboot, use the tablet as normal. From my experience this offers the BEST possible ROM usage, a vast reduction in lag, bugs, and oddness.
What else can I do with the TWRP Recovery? Well, the most useful tools are Backup, Restore (and advanced restore) and the wipe menu, plus fix permissions. Those generally can fix anything thats wrong. If you notice alot of lagging, FCs or general unruliness, wipe Cache, Dalvik Cache, and Fix Permissions. Another useful ability is ADB, which is beyond the scope of this section, but may be included generally in a later section. ADB can be used to repair otherwise bricked devices, and offers a very large amount of tools that you don't normally get to use in Recovery. Keep in mind ADB is powerful, and can quickly destroy your device, so please, be careful using it.
Placeholder for CWM Recovery section - coming soon!
CWM Recovery for A100 by ptesmoke
Section 3
Additional Recovery tools:
Blackhole Wipe/Nullifier by pio_masaki
These are tools I created to make wiping a little easier, but please read the post completely before deciding to use it! There are multiple versions, and they can and will wipe internal SD, as well as take up to 40 minutes to run (1, not all). Please ask questions if you have them there and I will help as best I can!
AROMA Recovery Touch Recovery
A touch file manger to be used in recovery, even on non touch CWM! Good for renaming backups as soon as you make them (I tend to forget afterwards and get confused by 6 backups with just dates). Also moving a downloaded zip from internal to external or whatever before running a system wipe, any number of things. Please read the post completely before using this tool! It can cause damage if not used properly and with care!
Kernels:
linuxsociety / godmachine's A100 OC Kernel
Plenty of extra balls thrown in for good measure, a good place to look if you like high benchmarks and plenty of extra goodies baked in. Available in a few flavors, with some GPU OC thrown in for good measure.
ezterry's A100 OC/UV Kernel
The only other option for a kernel that we have besides stock and CM9's included kernel. Excellent kernel, really wakes up the A100, allows up to 1.5 GHz for some extra umph and undervolting to help conserve power on our very weak batteries.
PRO TIPS:
The 10 minute rule:
The reason I mention waiting 10 minutes on first boot of a ROM install is this: Alot of things happen the first time the ROM runs, alot of scripts run, the kernel has to settle and search and move things, files are flying all over the nand. Think of a tornado in a cubicle. That's first boot for your device. Allowing it 10 minutes uninterrupted allows all of that to happen and settle down. The following reboot lets all that new info fire up from it's new home and continue settling in. After restoring and downloading apps, that reboot allows that new info to settle into it's new home and the system to catch up. This isn't device specific, rather a general rule of thumb for all devices. Does not really apply to restores unless something is changed.
Undervolting:
Undervolting on this device is only available on ezterry's excellent kernel. The following is a rough guideline of how to do it, and do it right:
Start small, don't just dump it -200 and expect it to work. For the time you're testing, make sure it is NOT set for boot. If something goes wrong you don't want it doing it everytime it boots, right? Go in small increments, -25 is usually OK. For now, don't overclock. Starting at 1 Ghz, lower every speed range down -25, and run the device for at least 10-20 minutes, normal use, hard use, benchmark, browse the web, watch a HD movie. If all is fine and its not lagging, freezing, force closing or heating up more then usual, move everything to -50, and repeat. My device freezes at -150 but runs stable at -145. Every device and chip is different, mine may do -145 yours may do -175 or only -50.
Overclocking
Overclocking is available on ezterry's bodacious (already used excellent) kernel, up to 1.5 GHz, and the CM9 kernel up to 1.4GHz. As with undervolting, this should be done in small steps and tested between to find your max. Generally 1.5 GHz is fine for every device, however all devices and chips are slightly different, and some may not be stable at it. Mixing undervolting and overclocking can be tricky, but following the steps above for undervolting you can find that sweet spot for your device.
Batteries and why they fail
This section is entirely my opinion, other's swear one way, other's another, but this is what I've concluded from multiple posts for this device.
Consider 10% to be 0%. There have been more then a couple posts that say they let their battery fall below 10% and they can NOT get the device to work properly again afterwards. I think there's a few reasons for this, and I'll explain them now. First, a lot of batteries tend to have some kind of breaker protection if the voltage drops below a certain level. This is to prevent damage to the cells, which it does, however we can't close that breaker to restore activity from the battery, IE, it's dead anyways. This threshold varies from one device to another, one battery pack to another, some can go to 0% and be ok, others can't. I say voltage level, because while draining the voltage can spike up, and it can also spike down, which can fall below this threshold even though it says you have 5% battery life remaining, and trigger the protection.
The acer does not seem to power on without a working battery. If the battery is "dead" it doesn't seem to boot. Its basically a brick until either the battery is replaced (by acer I would assume) or the motherboard is replaced due to some sort of damage causing this. Replacing the motherboard costs almost as much as a new unit, so at this point, just save up some more and buy a new one.
For this, I never go below 10% if ever possible. Even on my phones.
Another thing I try not to do is charge in bursts, or at random times. Basically, I plug in at 10%, then allow full charge to 100%, I don't charge in between those ranges, and I don't charge for periods less then 100%. So I don't plug in at 48% then unplug at 60%. I've learned this one from my Evo 4g, the battery was fantastic for months, then I started using the car charger to top off, and the battery life over the course of 2 weeks took a very noticable hit on overall life. I lost easily 4 hours a day usage on it. This on a phone and ROM combo that got me 16 hours a day.
Again this entire section is just what I've noticed and is purely my opinion, please do whatever you please with your device, it is yours after all!
ADB and Fastboot...is it really a faster boot?
No, fastboot isn't a toggle to boot at warp 9. Fastboot is a mode you can put your bootloader into for flashing the system for upgrades, repairs, mods, or general havok if you're not careful. The bootloader is what you see when you first turn on your device, that lovely Acer logo with the text up in the left corner (usually saying bootloader version and Unlocked Mode if unlocked, or nothing if it's locked). If you go into fasboot, it will say download usb protocol, so if you see that, you're in fastboot mode for whatever reason.
How do I get into fastboot mode?
Well you can do this in a couple ways, either Quickboot app (reboot bootloader), if you're on CM9, the power menu will give the option, or you can use ADB for it.
adb reboot bootloader
I'll explain some more about adb after fastboot, I know its odd, but one does have something to do with the other at times.
Once you've rebooted to the bootloader (device will turn off, vibrate, then boot to acer screen) you can then issue your fastboot commands assuming 2 things:
Acer USB drivers are installed and working correctly (if you use adb to reboot, then it is)
Your tablet is connected to your PC over USB.
Now, at this point, its up to you to do whatever you want, but BE CAREFUL USING FASTBOOT FLASH! It doesn't care or check what you're flashing, it'll just flash it. For example, I flashed CWM Touch recovery to boot once because I was distracted and mixed up the images for whatever reason. End result: Can't boot android. Why? Because boot was recovery, it only booted to CWM Touch recovery. Booting to actual recovery booted to TWRP, which was my previously installed recovery. I got it back easy enough once I figured out what I did wrong, but not all mistakes are reversible, or fixable!
General Fastboot uses and commands...
general layout goes like this:
fastboot (this is calling the command) flash (this is what fastboot will do) recovery (where it will send it to) recovery.img (the file it will send)
So, it looks like this:
fastboot flash recovery recovery.img
it will then flash whatever img to whatever partition you said, and let you know when it's done. You can flash any img to any partition, provided it fits, which means you do have to be careful about what you flash to where!
when you are finished with fastboot:
fastboot reboot
There are plenty of other commands, but the general basic use of fastboot is to flash a recovery or bootloader, so that is what I laid out above.
This section is hugely in need of improving, I know, but the guide in general is still rough, my apologies.
What about ADB?
ADB, or Android Debugging Bridge, can be used in System or in custom recoveries to interact with the device behind the curtain, meaning what you do isn't readily apparent on the device itself, unless you do something obvious like reboot it. ADB has a ton of commands, in particular in ADB Shell mode (you drop into the device shell itself, issuing commands from within itself, not from the PC).
Some random ADB commands:
adb reboot (where to reboot to) so:
adb reboot recovery
adb pull (what file to copy) /(where to copy file to) so for example, a recovery log to the adb working folder:
adb pull /cache/recovery/last_log recovery.txt
adb push /(file to copy to) /(file to send to device) so for example, placing that recovery file back into the device:
adb push recovery.txt /cache/recovery/last_log
Thats all the time I have for now, sorry in advance, I'm still working on all of this, I swear lol
Placeholder for additional tips and usage, some ADB stuff, and anything else I can think of.
Placeholder for Toubleshooting.
Placeholder for FAQS.
System Modding
justjackyl's Iconia A100 CM10 Setup & Use Tips/Tricks
A good guide to check out to try to get the most out of your A100 on CM10 (or any JB ROM like Sosei/black bean). A must read for those new to CM10/JB on these devices or in general. Not an outright mod, but a good source of information about some modding you should browse.
Hulu Flash Hack by NoSudo
What the Hulu Flash Hack by NoSudo does is allow you to use our android browser (setup according to the thread) to watch sites like Hulu to play on your android flash player. Its basic function is to scan for, then backup, then place a modified libflashplayer.so file. Setup with script manager and run at boot for best results. As always, read the thread for more information.
Mount Swap by crossix
What the Mount Swap by crossix does is pretty awesome, it mounts your external SD as internal, meaning your 32GB external SD card shows as internal, and is used for your apps, data, downloads, whatever, as if it was your internal SD. Internal SD is then mounted as external SD. It's operation is based on install-recovery being replaced with crossix's version. Instead of replacing recovery, it runs the mount swap. Requires Root, as the file is placed into /system/etc. Designed for stock/modified stock ROMs, it can be used with AOSP/AOKP ROMs by using script manager and setting it to run as Root at Boot. Please read the thread for the files and information on how to use it.
Adapted to ICS Build Prop Mods by patrick_spd4u adapted from crossix
What the Build Prop mods do is pretty basic, however can greatly increase the abilities of the A100, including faster boot times, more apps/games available for download in the Play Store, and tons of other stuff. Adapted from crossix's mods for HC.
Guide to 2 ways of running the crossix mount swap script, Acer based and AOSP/AOKP based
Direct paste from a post I made about this earlier...details using ES File Manager, however you can adapt it for any root file manager.
Using your tab, download the crossix mod zip file.
Unzip the file to get your epic mount swap mod by crossix, it can be unzipped anywhere.
At this point, I'm using ES File Manager but you can use Root Explorer or whatever. I'll be giving directions for ES.
Go into settings, scroll down and check the box for Up to Root.
Scroll a little futher down, same menu, and check the box for Root Explorer. Tap Yes, then allow when SU asks.
Now check the box next to Mount File System.
A little notice should pop up saying system is writable. If it fails at this point, you'll need to reroot, though it should work fine.
Press back, and go to where your crossix install-recovery.sh file is, hold your finger on it, and select Copy from the menu.
Press back and keep pressing it until you get to /. You'll see folders like acct, cache, config, d, etc.
Scroll down to system, and tap on it to go into system
Tap on etc to enter the etc directory.
You should now be in /system/etc, check up top there will be the address bar showing where you are.
You shouldn't have an install-recovery.sh file there, but if you do, long press it and select rename, then rename it install-recovery.bak.
On the upper buttons, select paste.
Now hold on the install-recovery.sh and select Properties, all the way at the bottom of that menu.
Next to where it says permissions, click Change
You will get a new window showing 3 rows of 3 colums of boxes with Xs.
Check the boxes so it looks like this:
XXX
XXX
XXO
Click on OK, then OK again, you should be back to the main ES window. Go ahead and hit home, or hit back over and over to exit.
Stock or Modified stock ONLY
Reboot the device by whatever method you prefer.
Once it finishes booting, wait a minute, then check your Settings>storage and your external SD card should show as internal. You only need to do this 1 time, it will continue to do this after.
AOSP/CM9/AOKP ONLY
Go to the Play store and download Script Manager(smanager).
After it installs, open the app then select Browse as root, Allow when SU asks, then click OK.
It will likely be listing /mnt/sdcard as your default directory, press the folder with .. to go back up until it says /
Click on system, then etc
It should now show /system/etc
Find your install-recovery.sh file, and it will open a new window.
Pay close attention here!
Right under the buttons that say Run Exit Edit Save are some icons,
Fav Su Boot Net Wick Ntfy
Press on Su and Boot, then click on Save.
Now exit smanager and reboot.
Wait a minute, then check settings>storage and your external SD should show up as Internal.
Don't disable smanager from running at boot! If you disable it, your script won't run. smanager must remain installed, or the script won't run.
Thanks to:
ZeroNull: For being one of the pioneers for getting our devices cracked open for our amusement!
ptesmoke: Also for being a pioneer in getting custom recoveries on our devices!
vache: For releasing the ICS leaks way ahead of schedule and hosting them for us to use and abuse!
civato: For releasing his Flex Reaper ROMs on our devices, his modified stock ROMs are still (IMO) the slickest available!
da-pharoah: For helping me understand how recoveries work a little better, allowing me to create Blackhole Wipe/Nullifier, and general encouragement for creating things for this device! (G2x and KF forums)
ezterry: For creating an OC/UV kernel that so far is the best EVER for any ROM on our device!
Theonew: reading ALL of that, and providing some nice info I missed and left out, and catching typos (Almost made it...)
crossix: that mount swap mod is just awesome, I never run a ROM without it!
NoSudo: creating a method to easily modify the system to watch HULU and other sites that normally won't allow it!
There's more I'm forgetting, I'll be adding more as I remember, I promise.
Even though I knew everything you posted, it was very interesting and I recommend everyone (even if you don't need it or already know) to read this guide. Its a marvellous read with some humor to keep you going. One thing though:
- You stated that its only safe to wipe "cache, dalvik cache, data, and system". Technically, this is not true. Flexrom and boot partitions are also safe to wipe (and for some roms for certain devices, the boot partition must be wiped for stable kernel performance, etc.). It's also a good idea to wipe sd-ext if you have it set up (in most cases). Once again, excellent guide (you even did a part of my job ).
Theonew said:
Even though I knew everything you posted, this is a brilliant guide and I recommend everyone (even if you don't need it or already know) to read this guide. Its a marvellous read with some humor to keep you going. One thing though:
- You stated that its only safe to wipe "cache, dalvik cache, data, and system". Technically, this is not true. Flexrom and boot partitions are also safe to wipe (and for some roms for certain devices, the boot partition must be wiped for stable kernel performance, etc.). It's also a good idea to wipe sd-ext if you have it set up (in most cases). Once again, excellent guide (you even did a part of my job ).
Click to expand...
Click to collapse
While sd-ext is safe to wipe, using factory reset wipes that for you, and I think, could be wrong, but cwm does it on data wipes. Part of why I missed it was I confused it with my phone, where wiping sd-ext bricks the phone, and also people mix it up with external SD. I'll add it in as its a very valid point, and I shouldn't let personal things interfere with the guide.
As for boot, our devices don't need that wiped and honestly asks for problems if someone doesn't restore or install a rom to cover it. I've never wiped it on any device, however I will also add that in as it is good info. I left it out of "safe" to prevent possible issues from wiping it.
I forgot about flex and I honestly don't know what it is for lol. Again thanks for reminding me and I'll add it in.
Of course I'm open to posts like these please give some input on what I missed or need to correct, I want this to be the go to guide for the a100 for anything needed!
Tapatalked from my Galaxy S II.
pio_masaki said:
I forgot about flex and I honestly don't know what it is for lol....Of course I'm open to posts like these please give some input on what I missed or need to correct, I want this to be the go to guide for the a100 for anything needed!
Click to expand...
Click to collapse
In your 4th to last sentence of the "Advanced Restore" section, you have a typo . Anyways, according to here: forum.tegraowners.com/viewtopic.php?f=10&t=149, Flexrom is "a partition on the nand that acer made to hold some proprietary apks and build information".
Oh damn almost made it without a typo...not bad for just running through all of that without really checking on it..other then it was english.
Corrections and additions added to the posts, thanks!
pio_masaki said:
Oh damn almost made it without a typo...not bad for just running through all of that without really checking on it..other then it was english.
Corrections and additions added to the posts, thanks!
Click to expand...
Click to collapse
One more thing - This occurred for one of my other devices, but the problem may still exist here. I haven't tried it with TWRP, but renaming CWM backups can cause a md5 mismatch error to occur. If this happens, simply rename it back to a date (in the default format).
I've never ran into that issue on any of my devices in CWM or TWRP, however I have heard of it occuring, definatly something I should add in there. Full of good catches tonight aren't you?
Awesome write up, thanks you guys!!
What about Zeronull's .014 v1.2 rom? http://forum.xda-developers.com/showthread.php?t=1574897
I'm still digging through all the threads for the ROMs, however I included the currently developed or recently released ROMs first, ZN has since released Green ICS, which is included already. I do plan to list every ROM, but it'll take some time to finish this guide up with as much info as possible, then go back and add things in.
pio_masaki said:
I've never ran into that issue on any of my devices in CWM or TWRP, however I have heard of it occuring, definatly something I should add in there. Full of good catches tonight aren't you?
Click to expand...
Click to collapse
I tested it to see if it occurs, and it turns out that it does. I made a backup with CWM, renamed it then tried to restore, and it immediately gave me the "md5 mismatch" error.
Theonew said:
I tested it to see if it occurs, and it turns out that it does. I made a backup with CWM, renamed it then tried to restore, and it immediately gave me the "md5 mismatch" error.
Click to expand...
Click to collapse
That is so weird I never have that issue cwm or twrp. I use es file manager..maybe why?
Tapatalked from my Galaxy S II.
pio_masaki said:
That is so weird I never have that issue cwm or twrp. I use es file manager..maybe why?
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
I renamed it using Root Explorer. Have you tried renaming them to something including spaces?
Theonew said:
I renamed it using Root Explorer. Have you tried renaming them to something including spaces?
Click to expand...
Click to collapse
No, as its a Linux based environment I use dashes and underscores never spaces in directory names. That shouldn't cause md5 fails because the md5 is based per zip not the folder name. If you could try an experiment and rename with es I'd appreciate it, and maybe with and without spaces. I'll try root explorer when I get home and see if it causes issues.
Tapatalked from my Galaxy S II.
pio_masaki said:
No, as its a Linux based environment I use dashes and underscores never spaces in directory names. That shouldn't cause md5 fails because the md5 is based per zip not the folder name. If you could try an experiment and rename with es I'd appreciate it, and maybe with and without spaces. I'll try root explorer when I get home and see if it causes issues.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Done. The error seems to only occur when spaces are used in the name.
Theonew said:
Done. The error seems to only occur when spaces are used in the name.
Click to expand...
Click to collapse
Thanks for taking the time to figure that one out, I've been testing a new rom on my phone plus a new test T20 kernel for ezterry and getting cm9 build 5 up, just kinda managed to forget that experiment lol
I'll have some time...maybe...to append that new bit into that section tonight. The "free" time has been spent trying to get aokp for the a100 but my lack of experience, random problems with the repos and devs ignoring my PMs its been going slow. And by slow I mean nowhere.
Tapatalked from my Galaxy S II.
Great read. Sorta like flashing for dummies. Thaanks for your work.
Sent from my HTC Glacier using Tapatalk
It's great to have all this information compiled in one location. Looking forward to your next installment. THX
I politely ask any person able to help to explain to me, like I am a three year old, exactly how to update a Samsung Glide from 4.0.4 to whatever newer version is able to work on the phone, that is rooted? AGAIN... I ask this politely.
Allmystical1 said:
I politely ask any person able to help to explain to me, like I am a three year old, exactly how to update a Samsung Glide from 4.0.4 to whatever newer version is able to work on the phone, that is rooted? AGAIN... I ask this politely.
Click to expand...
Click to collapse
No problem, we are all new at this once, right?
First Step: Downloads!
TWRP:
http://dualhoki.vim.hu/bubor/dev/twrp-i927/twrp-2.8.4-for_odin.tar.md5
ROM:
Here is a matter of preference. If you want the latest *working* version, you can upgrade to 5.0, but you lose the camera. I presume you want the camera to work, so I suggest Bubor's CM11 for KitKat. There are other good roms too, like PAC and SediRom, but we will start with Bubor's CM11.
http://dualhoki.vim.hu/bubor/dev/11.0/cm-11-20160126-UNOFFICIAL-i927.zip
http://dualhoki.vim.hu/bubor/dev/11.0/cm-11-20160126-UNOFFICIAL-i927.zip.md5sum
ODIN:
http://www.mediafire.com/download/7us5q44aab1xl9d/Odin304.zip
Second Step: Prepare.
I am presuming that you are using a Windows computer. If you are using a Linux computer, I can tell you what to do also, but these instructions are for Windows. I am also presuming that you have an external SD card in your phone, if you do not, go buy one and put it in your phone.
Unzip the Odin304.zip by right clicking on it and say unzip/extract, etc. If your Windows does not have this option, you need to download a program like winzip or 7zip so you can unzip this file. If you need those programs, they can be googled and downloaded.
Third step: Further preparation.
Turn on your phone and plug it into a usb cord and plug the usb cord into your computer. If you are using Windows, it will try to find drivers for the phone. It should be automatic and just work. If it does not, then you need the drivers, which are here:
http://www.mediafire.com/download/0up21ccc9gajwjv/Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
*If you downloaded this file, just double click it like a program, it should open and install drivers for your phone. Do not do this unless your computer cannot find drivers for your phone!
Fourth step: Charge your phone.
Plug in your phone and FULLY charge it. ALL the way to 100% CHARGED. No exceptions. No shortcuts. Do it. Then UNPLUG YOUR PHONE AND TURN IT OFF.
Fifth step: Put TWRP on your phone.
a. Your phone should now be unplugged and off. Open the ODIN folder that you unzipped earlier and double click on ODIN to open the program.
b. Click on the PDA button ( you and I both know that your phone is not a PDA, this is not a typo ) and it will open a browser. Find the twrp-2.8.4-for_odin.tar.md5 file and select it. It should now fill in the blank line next to PDA with this info.
c. WHILE HOLDING THE UP VOLUME BUTTON ON YOUR PHONE, press and hold the power button. When you see "SAMSUNG" you can release the power button, but KEEP HOLDING THE UP BUTTON, untill you see a yellow triangle and warning notice. If you hold too long, that is okay as it will take you straight to the download mode with the green android that says "ODIN" at the top and "Downloading" in the middle. If you got stopped at the yellow warning/triangle, press up again to go to download mode.
d. Plug your phone into the usb, and the usb into your computer.
e. In the Odin program, press start.
You should now see a serries of verbage going by on the left, at the top a green bar may fill in, and hopefully, in the end it says "success" or "pass". Your phone should reboot all by itself. If ODIN says fail, ask for further instructions. If passed, close Odin.
Sixth step: Put your CM11 files on your phone.
Your phone should have rebooted and looks just like it did before, now powered on, and in your stock Ice Cream Sandwich firmware. As with any file transfer, plug your USB into the phone and computer. Drag the CM11 files to the phone. Anywhere will do, but if you have an external SD card in your phone, I recommend you put it there.
Seventh Step: Boot into TWRP.
a. Turn off your phone.
b. Unplug the USB.
c. HOLD THE DOWN VOLUME BUTTON and press the POWER BUTTON. When you see "Samsung" release the POWER BUTTON, but keep holding the VOLUME DOWN BUTTON. At the top of the screen, white letters should say something like "entering recovery".
d. When you see "Team Win Recovery Project" release the down volume button.
Eighth step: Make a backup!
a. Press "Backup" button on screen.
b. Check all checkboxes (system, cache, data, boot, Android Secure)
c. Press "Storage: sdcard (xxxx mb)" bar.
d. Select "External_sd" to choose to backup to your external sd card.
e. Slide the swipe bar to the right to backup. This will take a few minutes, with progress bar.
NOTE: if the screen dims, when you touch it, you will see a TWRP lock icon, swipe right to unlock it.
f. When backup is completed, it will say "reboot system", do not click that. Click the "home" icon in the lower left corner.
g. Click the "Wipe" button.
h. Swipe right to factory reset.
i. Click the "home" icon in the lower left corner.
j. Click the "install" button.
k. At the top, click on the "Storage: sdcard (xxxx mb)" bar.
l. Select "External_sd"
m. choose the cm-11-20160126-UNOFFICIAL-i927.zip
n. When that is done, click on the "reboot system" button.
The system will reboot. You should now see CM11's boot screen. The first boot takes a bit of time.
Ninth step: Thank Bubor.
a. Log into XDA.
b. Go to http://forum.xda-developers.com/captivate-glide/development/dev-cm-11-0-t2802184
c. Slap every thanks button that is for a post by Bubor untill it tells you that you cannot slap any more thanks buttons (that is only 8 thanks per day).
Tenth step: Enjoy your phone!
....I think you know how to do that.....
If you have ANY questions, please just post them here and we will see if we can answer them.
I am thanking you so very much! Also... I do apologize for such a time lapse in my reply. Life happened.
I followed the above procedure and have CM11 installed. But my problem is I can't use my SIM card anymore because it's like my phone doesn't see it at all. I checked my settings and saw that I no longer had an IMEI number. I used the restore feature and the stock ROM had an IMEI number. What should I do? I saw a few threads about using a program to rewrite the IMEI or others to copy the file containing the IMEI but I wasn't really sure what I should do or how to copy files to and from that partition from my computer. I should add that the phone is unlocked.
tr3sie7e said:
I followed the above procedure and have CM11 installed. But my problem is I can't use my SIM card anymore because it's like my phone doesn't see it at all. I checked my settings and saw that I no longer had an IMEI number. I used the restore feature and the stock ROM had an IMEI number. What should I do? I saw a few threads about using a program to rewrite the IMEI or others to copy the file containing the IMEI but I wasn't really sure what I should do or how to copy files to and from that partition from my computer. I should add that the phone is unlocked.
Click to expand...
Click to collapse
Great question, and an interesting problem!
First, I am really glad that you followed the instructions and made a backup! It is good to know that you can always go back to the way it was.
I recommend that you download another rom from the developer section here, such as Sedi-rom, omni-rom, etc., and try flashing that. If you flash one of those roms, does your IMEI stay for those roms?
Try this one: http://forum.xda-developers.com/showthread.php?t=2789727
You can do steps 7 through 10 with any of the roms in the developer thread. If this other rom works, you can use it, or download others and try them. If the SediRom does not work also, then we will need to sit down and figure this out.
I really appreciate the fact that you're here to help.
I downloaded and installed SediRom 2.1.2 and my IMEI still shows as "Unknown." However this time I should add there is a serial number, which I don't believe was present in CM11 or in the stock ROM, although I'm not sure if that's at all significant. I made an external backup of the efs file from the stock ROM, is there some way I could just reinstall CM11 and replace/overwrite the efs to give it an IMEI number? I'd really like to use CM11 if possible, I was enamored by how good it looked and how functional it was, especially since the last time I tried CM a long time ago I didn't have such a good opinion of it. Plus the bootloader is friggin sweet !
I recently got the phone unlocked off eBay, so I don't know its past history but I was able to access the network when I had the SIM card in prior to initially installing CM11 but not afterwards. I'm trying to use a T-Mobile SIM but like I said I was able to successfully access the network prior to installing CM11. But the IMEI doesn't show at all regardless if the SIM is in at all.
Is there some kind of different hardware/firmware like in a newer slightly different version of the phone that came out resulting in compatibility issues? I'm not the most experienced but I've dipped by toes in this before, so I would be willing to go the extra mile if it meant I could get CM11 to work, because honestly it looked like everything I could ever want from this phone with a good looking theme too...
Do you have a full backup of the efs partition?
If so it should be enough to restore it.
Sent from my LG-H815 using XDA Labs
xdajog said:
Do you have a full backup of the efs partition?
If so it should be enough to restore it.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Yes I believe so. I used the procedure from this thread to back it up. I tried copying the efs directly over using the built in file manager with root access, but when I try to copy the entire efs folder over I get a non-descriptive error "this operation has failed." I tried copying the nv_data.bin folder by itself to overwrite the one currently there (which copied successfully), then rebooted the phone but the IMEI still shows as "unknown." Do I need to copy the efs while the phone is in recovery mode or via PC or something because of file in-use errors or something else I don't know about?
tr3sie7e said:
Yes I believe so. I used the procedure from this thread to back it up. I tried copying the efs directly over using the built in file manager with root access, but when I try to copy the entire efs folder over I get a non-descriptive error "this operation has failed." I tried copying the nv_data.bin folder by itself to overwrite the one currently there (which copied successfully), then rebooted the phone but the IMEI still shows as "unknown." Do I need to copy the efs while the phone is in recovery mode or via PC or something because of file in-use errors or something else I don't know about?
Click to expand...
Click to collapse
Well restoring efs have to be done in recovery only! Do not try to do this while android is running!!
To be honest the absolute best way is having a dd partition dump of the whole partition. When you have followed the mentioned guide do you have used also dd like this?
dd if=/dev/block/mmcblk0p1 of=/storage/external_SD/efs.img
I don't know if copying the efs folder alone would work.. better is restoring the whole partition if possible. Do you have such kind of backup?
Sent from my LG-H815 using XDA Labs
Hi there,
Many thanks for this great post! I am going through the steps and when I press Start in Odin3 v3.04, I get this message
<OSM> twrp-2.8.4-for_odin.tar.md5 is invalid.
Please help.
Many thanks in advance!
Andrew
azwindsor said:
Hi there,
Many thanks for this great post! I am going through the steps and when I press Start in Odin3 v3.04, I get this message
<OSM> twrp-2.8.4-for_odin.tar.md5 is invalid.
Please help.
Many thanks in advance!
Andrew
Click to expand...
Click to collapse
try to rename to recovery.tar.md5
try older version, and flash the latest from recovery.
azwindsor said:
Hi there,
Many thanks for this great post! I am going through the steps and when I press Start in Odin3 v3.04, I get this message
<OSM> twrp-2.8.4-for_odin.tar.md5 is invalid.
Please help.
Many thanks in advance!
Andrew
Click to expand...
Click to collapse
Redownload. Maybe the file you had downloaded gets corrupted or is incomplete ..
.
Sent from my LG-H815 using XDA Labs
bubor said:
try to rename to recovery.tar.md5
try older version, and flash the latest from recovery.
Click to expand...
Click to collapse
Many thanks bubor! Renaming worked like a charm.
FYI, I tried re-downloading it, but that didn't seem to work yesterday.
I really appreciate all of your work, everything is working great.
Thanks for the quick responses.
All the best!
So I'm really late here but the phone got thrown to the backburner and I forgot about it. Lol but anyways, I created the EFS backups using dd like it said, but I'm not sure how to restore them? Do I unpack them and then use ADB to move them there? I'm kind of confused. Also, for some reason going through the TWRP to the stock ROM doesn't let me root it, it crashes every time I get to that screen, don't know if that's important to the operation. Hope I can finally get this stupid thing working right with the custom ROM...
tr3sie7e said:
So I'm really late here but the phone got thrown to the backburner and I forgot about it. Lol but anyways, I created the EFS backups using dd like it said, but I'm not sure how to restore them? Do I unpack them and then use ADB to move them there? I'm kind of confused. Also, for some reason going through the TWRP to the stock ROM doesn't let me root it, it crashes every time I get to that screen, don't know if that's important to the operation. Hope I can finally get this stupid thing working right with the custom ROM...
Click to expand...
Click to collapse
Check my faq here:
http://forum.xda-developers.com/showthread.php?t=2789727&p=54075993
Scroll down to restore efs.
.
Okay so I used TWRP to do a factory restore, flashed SuperUser, then flashed CM11, went into TWRP and did the terminal commands you listed in the guide for backing up the EFS... to no avail. Would it be better to copy the EFS while I'm still on the rooted stock ROM using a terminal app? I don't understand what the problem is...
tr3sie7e said:
Okay so I used TWRP to do a factory restore, flashed SuperUser, then flashed CM11, went into TWRP and did the terminal commands you listed in the guide for backing up the EFS... to no avail. Would it be better to copy the EFS while I'm still on the rooted stock ROM using a terminal app? I don't understand what the problem is...
Click to expand...
Click to collapse
Please paste the output of the results. Doing this in twrp is the correct way.