Related
Teamwin Recovery Project for A100 version 2.2.2.1 -godmachine81 release-
SOURCES: Available via Github
Download and Install via the official supported method by TWRP
Install Goo Manager app from Play Store, Open Goo Manager, In the Menu in top right corner go to "Install OpenRecovery Script" Follow Instructions On screen
Download Automated Installer (Windows / Linux):
Linux Installer - 2.2.2.1
Windows Installer - 2.2.2.1
Download IMG:
TWRP v2.2.2.1 main mirror
Download Flashable Zip: (Upgrade Only)
TWRP 2.2.2.1 Flashable Upgrade
Updated TWRP release features:
Uses a custom recovery kernel based off of my v1.5 standard kernel with most unneeded features taken out, i.e. governors, schedulers, networking, misc devices, and most things not needed for recovery operations
Kernel and TWRP includes patches aimed at brick prevention
Resolution is set at native 1024x600
Very fast actions and touch response
Backward compatibility with previous releases of TWRP
Compatibility with all Ice Cream Sandwhich and Jelly Bean ROMs for the A100(HoneyComb should be compatible too, however currently untested)
All previous features from TWRP that you may be familiar with are included
Mount Point Information:
External Storage - mountpoint= /external_sdcard
Internal Storage - mountpoint = /sdcard
Instructions:
Automated Installation (Windows/Linux):
Most importantly you need to have all drivers required for adb and fastboot working on your OS, this shouldn't be a concern for linux users, however it may be for Windows users as it is picky about adb drivers.
Download the above Automated Install .zip file for your operating system
Extract the contents of the Zip to a location on your PC's hard drive
Change to the extracted directory's contents.
Run the installer; On windows you may just double click the install-windows.bat file, on linux you need to run the install-linux.sh script
example linux installation commands:
Code:
cd a100_twrp_installer_linux
Code:
bash ./install-linux.sh
Read the on screen information of the progress. If you get any errors you will need to resolve the issue or try one of the following alternative install methods.
If you need more detailed installation instructions please read the INSTALL file included inside the .zip
Manual installation:
Download the .img file for the recovery
Connect your A100 device to USB on your PC
While your A100 is booted in either Android or Recovery just enter the following into your PCs command prompt/shell:
Code:
adb reboot bootloader
Now flash the image - at the command prompt/shell enter:
Code:
fastboot flash recovery openrecovery-twrp-2.2.2.1-a100.img
Reboot the device - again from the command prompt/shell:
Code:
fastboot reboot
Enter Recovery mode - While tablet shuts off, hold the Vol - (down) button until you see the screen saying "loading recovery kernel"
Checkout the new TWRP build and enjoy!
Flashable Upgrade Instructions: (flash just like you would any other .zip, but here are instructions anyway)
Download the Flashable ZIP above
Save to a location on your tablets internal or external memory
Boot to recovery
Choose the file a100_twrp_upgrade_2.2.2.1.zip in the install menu
Swipe to install
Wait and DO NOT Disconnect your A100!
When finished, go back to Main menu - choose Reboot - and Reboot Recovery
Enjoy the Official 2.2.2.1 TWRP Release!
If you would like to help out with the continuance of my kernel development and other goodies for your Acer Iconia Tab please consider a small donation to help out with bills, baby formula, wipes, diapers, etc. All donations are very appreciated by my family and I! Thanks
.....I was gonna mention some things about your brick stuff, but I think I'll save it for off forum.
On topic: its about time we twrp users got some loving, thanks for taking the time to put this together for us!
Tapatalked from my A100 - Jellytime X B6
pio_masaki said:
.....I was gonna mention some things about your brick stuff, but I think I'll save it for off forum.
On topic: its about time we twrp users got some loving, thanks for taking the time to put this together for us!
Tapatalked from my A100 - Jellytime X B6
Click to expand...
Click to collapse
And don't forget that i forgot the download link!! lol **fixed haha
Broken links, so you can correct it.
Fransis88 said:
Broken links, so you can correct it.
Click to expand...
Click to collapse
Thanks francis88, i just tested them on my end again (btw the hosting server is remote from me) it worked for me, so maybe you should check if you have an adblocker or some kind of ipfilter going on? possibly the host was having issues too, but the links works for me at the moment. tested both github sources and the download link to the img. Thanks again
*Edit: Please keep in mind I am using androidfilehost's beta site and they are doing quiet a bit of changes to the site lately trying migrate users from the original site over to the new, and once they get everything settled in and the 'beta' goes away everything should straighten back up. I really like the services at 'androidfilehost' and the owner is really great at working with devs, so please be patient as they continue to upgrade their servers to bring us superb file hosting services. If a link appears to be broken, please wait a few minutes and try again, if the link is down for a long period of time please contact me in PM so that the thread stays for discussion about the TWRP Recovery. Sorry and thanks everyone
linuxsociety said:
Thanks francis88, i just tested them on my end again (btw the hosting server is remote from me) it worked for me, so maybe you should check if you have an adblocker or some kind of ipfilter going on? possibly the host was having issues too, but the links works for me at the moment. tested both github sources and the download link to the img. Thanks again
*Edit: Please keep in mind I am using androidfilehost's beta site and they are doing quiet a bit of changes to the site lately trying migrate users from the original site over to the new, and once they get everything settled in and the 'beta' goes away everything should straighten back up. I really like the services at 'androidfilehost' and the owner is really great at working with devs, so please be patient as they continue to upgrade their servers to bring us superb file hosting services. If a link appears to be broken, please wait a few minutes and try again, if the link is down for a long period of time please contact me in PM so that the thread stays for discussion about the TWRP Recovery. Sorry and thanks everyone
Click to expand...
Click to collapse
Perfect, i have been able to download it. i had a very bad experience with CWRP, now I only use TWRP apart from the fact that their options seem to me much more practical.
Fransis88 said:
Perfect, i have been able to download it. i had a very bad experience with CWRP, now I only use TWRP apart from the fact that their options seem to me much more practical.
Click to expand...
Click to collapse
So let me know how you like it. Also if you happen to be a linux user, I have wrote an automated installer script for linux, Xbow59 is currently writing a windows batch script for installation, I currently have the Linux installation working though if you'd like to test/try it out just let me know. Windows users can look forward to an automated solution within a day or so
help :/........ i am on stock rooted ics. i just unlocked the bootloader sucsessfully and went to flash this. flashed the recovery. and when i try to boot into recovery i get the dead android guy with an ! in a triangle above him......... should i flash recovery again or try to boot into recovery again? i just dont want to mess anything up.
edit: im just scared its trying to update a stock package. i had an update a couple days ago and tryed to update but it failed since i deleted a bunch of bloat, no problem. but i dont know where it downloaded and if its still there trying to install.
nim.whit said:
help :/........ i am on stock rooted ics. i just unlocked the bootloader sucsessfully and went to flash this. flashed the recovery. and when i try to boot into recovery i get the dead android guy with an ! in a triangle above him......... should i flash recovery again or try to boot into recovery again? i just dont want to mess anything up.
Click to expand...
Click to collapse
By unlocking the bootloader successfully, what exactly did you do? If you flashed the btl100 file to the device that's not successfully unlocking, in fact don't touch that 100 file again. Hopefully you followed the guide and used the A200 bootloader unlock method. If you followed that guide though you wouldn't be getting the dead android looking guy. Be careful with this stuff, can easily brick!
linuxsociety said:
By unlocking the bootloader successfully, what exactly did you do? If you flashed the btl100 file to the device that's not successfully unlocking, in fact don't touch that 100 file again. Hopefully you followed the guide and used the A200 bootloader unlock method. If you followed that guide though you wouldn't be getting the dead android looking guy. Be careful with this stuff, can easily brick!
Click to expand...
Click to collapse
i used that method (only one i know) and i got the distotrted green acer logos and it says its unlocked. after i followed the steps to install twrp and it went smoothly. until i tryed booting into recovery. should i try to boot into recovery again? ive rebooted a few times so im still safe if i have to power off. OR should i try to reinstall twrp and follow the guide again. because i am CERTAIN i am unlocked. before i had to send in for repairs i had it unlocked but of course they relocked it.
(btw im not getting angry or smart assy with you haha,if it seems that way i dont mean it to come out that way)
nim.whit said:
help :/........ i am on stock rooted ics. i just unlocked the bootloader sucsessfully and went to flash this. flashed the recovery. and when i try to boot into recovery i get the dead android guy with an ! in a triangle above him......... should i flash recovery again or try to boot into recovery again? i just dont want to mess anything up.
edit: im just scared its trying to update a stock package. i had an update a couple days ago and tryed to update but it failed since i deleted a bunch of bloat, no problem. but i dont know where it downloaded and if its still there trying to install.
Click to expand...
Click to collapse
Delete or rename /system/etc/install-recovery.sh then install twrp again.
its overwriting your custom recovery every boot.
Tapatalked from my A100 - Jellytime X B6
nim.whit said:
i used that method (only one i know) and i got the distotrted green acer logos and it says its unlocked. after i followed the steps to install twrp and it went smoothly. until i tryed booting into recovery. should i try to boot into recovery again? ive rebooted a few times so im still safe if i have to power off. OR should i try to reinstall twrp and follow the guide again. because i am CERTAIN i am unlocked. before i had to send in for repairs i had it unlocked but of course they relocked it.
(btw im not getting angry or smart assy with you haha,if it seems that way i dont mean it to come out that way)
Click to expand...
Click to collapse
yep what pio said:
pio_masaki said:
Delete or rename /system/etc/install-recovery.sh then install twrp again.
its overwriting your custom recovery every boot.
Tapatalked from my A100 - Jellytime X B6
Click to expand...
Click to collapse
I had forgot all about this, even though it is in my unreleased linux auto installer. If by chance you are using linux, I have an installer that will do this all for you the right way, I just haven't posted it yet because I don't have the windows installer fixed
you can either download the linux installer git repo and just extract it to a directory named twrp_install or similar; just run sudo bash ./install-linux.sh after you are in the install directory. https://github.com/godmachine81/Acer-A100-TWRP-Installer/zipball/linux <<current linux installer for a100 twrp
Or you can clone the repo
Code:
git clone https://github.com/godmachine81/Acer-A100-TWRP-Installer.git
then checkout the linux branch:
Code:
git checkout linux
then install:
Code:
sudo bash ./install-linux.sh
The git method requires you have git installed, you will probably just want to install from the zipball method if you don't already have git
pio_masaki said:
Delete or rename /system/etc/install-recovery.sh then install twrp again.
its overwriting your custom recovery every boot.
Tapatalked from my A100 - Jellytime X B6
Click to expand...
Click to collapse
aahhhhhh. thought it was something of that nature. now will i have to delete/rename and reflash twrp every time i need to flash something? or will it stick once i sucsesfully flash it?
will report if it works in a few seconds
edit: noobness showed there. haha thats a script to reinstall recovery at boot so once i delete it it wont reflash stock recovery right?
edit edit: nope, im not on linux (yet) my computer is a mess of three harddrives and messed up registrys and unofficial windows 7 haha. once i buy a copy of windows 7 its a full wipe and partitioning for a windows/linux dualboot
EDIT EDIT EDIT: SUCCESS now i flash linux's kernel
Thanks for the help you guys. once i get some money from the boss man i will gladly donate a little something something for the cause
nim.whit said:
aahhhhhh. thought it was something of that nature. now will i have to delete/rename and reflash twrp every time i need to flash something? or will it stick once i sucsesfully flash it?
will report if it works in a few seconds
edit: noobness showed there. haha thats a script to reinstall recovery at boot so once i delete it it wont reflash stock recovery right?
edit edit: nope, im not on linux (yet) my computer is a mess of three harddrives and messed up registrys and unofficial windows 7 haha. once i buy a copy of windows 7 its a full wipe and partitioning for a windows/linux dualboot
EDIT EDIT EDIT: SUCCESS now i flash linux's kernel
Thanks for the help you guys. once i get some money from the boss man i will gladly donate a little something something for the cause
Click to expand...
Click to collapse
Once that's removed or renamed it will stop, one time deal.
Tapatalked from my A100 - Jellytime X B6
Also I noticed you mentioning that you are using a stock rom, you might want to talk to pio_masaki about this; but to my understanding the stock roms from Acer are not suppose to be flashed from custom recovery. I have read different things on this, however I haven't ever attempted to do such, from what I can tell doing this can or will brick your tablet by overwriting your bootloader and failing to install android, giving you no way to get to recovery nor android.. Might be something you want to discuss with him sometime.
linuxsociety said:
Also I noticed you mentioning that you are using a stock rom, you might want to talk to pio_masaki about this; but to my understanding the stock roms from Acer are not suppose to be flashed from custom recovery. I have read different things on this, however I haven't ever attempted to do such, from what I can tell doing this can or will brick your tablet by overwriting your bootloader and failing to install android, giving you no way to get to recovery nor android.. Might be something you want to discuss with him sometime.
Click to expand...
Click to collapse
In your kernel thread he mentioned staying on stock for stability, so I don't think he'll be flashing off stock anyways. Not yet anyways....
Restoring stock works as it leaves the boot loader alone.
Tapatalked from my A100 - Kuroikaze B3
pio_masaki said:
In your kernel thread he mentioned staying on stock for stability, so I don't think he'll be flashing off stock anyways. Not yet anyways....
Restoring stock works as it leaves the boot loader alone.
Tapatalked from my A100 - Kuroikaze B3
Click to expand...
Click to collapse
Thanks, just trying to look out for these newcomers - however I'm still a bit confused at which causes the brick. The way I first interpreted it, it was flashing any Acer packaged update.zip from a custom recovery that would cause it. Then someone said that only the HC zips would. So to play it safe, I believe I'd double double check as many times as possible before I flashed any .zip from Acer from either twrp or cwm if it was me. Wish there was some clarity though on which Acer zips are SAFE and which ones are BRICKs -n- a Zip lol
linuxsociety said:
Thanks, just trying to look out for these newcomers - however I'm still a bit confused at which causes the brick. The way I first interpreted it, it was flashing any Acer packaged update.zip from a custom recovery that would cause it. Then someone said that only the HC zips would. So to play it safe, I believe I'd double double check as many times as possible before I flashed any .zip from Acer from either twrp or cwm if it was me. Wish there was some clarity though on which Acer zips are SAFE and which ones are BRICKs -n- a Zip lol
Click to expand...
Click to collapse
The ics Acer zips are known brickers but it happens for a reason I'm not very clear on. HC will also brick it.
Basically there's a chance it will run the zip, attempt to flash everything, however for some reason it will fail to flash system or boot correctly, but does replace the bootloader. What I'm not clear on is why it fails on system or boot but succeeds on bootloader, or why recovery doesn't error flashing it.
Once this situation occurs you get locked out of both recovery and system by the bootloader, no adb or fastboot access to correct it.
Using the information I've gathered on this I've been working on a method to restore to stock if needed, but its going slow as I have to triple check everything before I even test it. Its a long and annoying process but should result in a 100% factory stock system.
Tapatalked from my Galaxy S II.
Installed and working perfectly!
Fransis88 said:
Installed and working perfectly!
Click to expand...
Click to collapse
Great Francis88, mind I ask which method of installation you chose?
I have an HTC Explorer and have installed CM 9 easily. Unlock bootloader through HTC , install custom CWM recovery using fastboot, then install CM 9 zip from sd card using CWM recovery. I have tried to do the same with my daughter's Wildfire. I get as far as installing a CWM recovery but it hangs at a "hat" icon when I try to use it. I have tried several CWM img files, including the one in the "cm49?" zip. None work. Is there a way for me to get a CWM recovery working? I don't want to go through all the s-off process, I don't think it is needed. My Explorer works great with s-on. I hope someone can help. I promised my daughter I would get ICS on her phone as her Christmas present.
bobharding said:
I have an HTC Explorer and have installed CM 9 easily. Unlock bootloader through HTC , install custom CWM recovery using fastboot, then install CM 9 zip from sd card using CWM recovery. I have tried to do the same with my daughter's Wildfire. I get as far as installing a CWM recovery but it hangs at a "hat" icon when I try to use it. I have tried several CWM img files, including the one in the "cm49?" zip. None work. Is there a way for me to get a CWM recovery working? I don't want to go through all the s-off process, I don't think it is needed. My Explorer works great with s-on. I hope someone can help. I promised my daughter I would get ICS on her phone as her Christmas present.
Click to expand...
Click to collapse
If I'm not mistaken you have to flash the boot.img manually with S-ON so I think a S-Off'd device is much better and it isn't that hard to S-Off it. I don't know if the S-Off methods still work if you unlocked it before but they should.
Besides you haven't taken the CWM from Pico/Explorer and tried to install it on the Wildfire, have you?
miniAndroidian said:
If I'm not mistaken you have to flash the boot.img manually with S-ON so I think a S-Off'd device is much better and it isn't that hard to S-Off it. I don't know if the S-Off methods still work if you unlocked it before but they should.
Besides you haven't taken the CWM from Pico/Explorer and tried to install it on the Wildfire, have you?
Click to expand...
Click to collapse
Thanks for your reply. All the cwm img files I have used have come from this forum. I had high hopes for the one I extracted from "pc49img.zip" as it seemed to say it might work on another post. It installed like the other but doesn't work.
bobharding said:
Thanks for your reply. All the cwm img files I have used have come from this forum. I had high hopes for the one I extracted from "pc49img.zip" as it seemed to say it might work on another post. It installed like the other but doesn't work.
Click to expand...
Click to collapse
I got a question are you just unlocked or already rooted on the WF? I think you can't install CWM if you're not rooted. That would be nice to know. Otherwise you can may follow this guide
miniAndroidian said:
I got a question are you just unlocked or already rooted on the WF? I think you can't install CWM if you're not rooted. That would be nice to know. Otherwise you can may follow this guide
Click to expand...
Click to collapse
Just unlocked after following the procedure on "htcdev.com". With my Explorer you can root the phone with the aid of the CWM recovery you install after unlocking it. Maybe the CWM recoveries for Wildfire assume your phone is already rooted, but I don't know how to root it without having a working CWM recovery first.
bobharding said:
Just unlocked after following the procedure on "htcdev.com". With my Explorer you can root the phone with the aid of the CWM recovery you install after unlocking it. Maybe the CWM recoveries for Wildfire assume your phone is already rooted, but I don't know how to root it without having a working CWM recovery first.
Click to expand...
Click to collapse
Yeah you're right. I think the progress on S-ON should be like this:
-flash CWM
-flash superuser rights (thats how it worked on the HTC One X)
I found this:
http://forum.xda-developers.com/showthread.php?t=1484124&highlight=recovery
Let me know if it worked.
miniAndroidian said:
Yeah you're right. I think the progress on S-ON should be like this:
-flash CWM
-flash superuser rights (thats how it worked on the HTC One X)
I found this:
http://forum.xda-developers.com/showthread.php?t=1484124&highlight=recovery
Let me know if it worked.
Click to expand...
Click to collapse
Thanks for all your help miniAndroidian (the Nexus 4 should be awesome, (I am saving up, but they are not available in Australia at the moment. I told my daughter she should get one too, but she hasn't got the money either, so that's why I am working on the Wildfire)
Unfortunately the post you directed me to says you have to flash the CWM recovery from the stock recovery but I don't have that anymore as I have replaced it with the CWM recovery which just hangs. There must be a way round it, but I am no expert at all.
bobharding said:
Thanks for all your help miniAndroidian (the Nexus 4 should be awesome, (I am saving up, but they are not available in Australia at the moment. I told my daughter she should get one too, but she hasn't got the money either, so that's why I am working on the Wildfire)
Unfortunately the post you directed me to says you have to flash the CWM recovery from the stock recovery but I don't have that anymore as I have replaced it with the CWM recovery which just hangs. There must be a way round it, but I am no expert at all.
Click to expand...
Click to collapse
Same in Germany with the Nexus 4 but it should be avalible in the middle of january
Back to the topic:
You have to put the "update.zip" to the root of your SD-Card and boot into the bootloader menu (the white screen with 3 android's on the bottom) and then it should recognize the new CWM.
Terrific. I didn't understand it. My daughter lives 100km from me so I will have to visit her this weekend. She left after Christmas saying "Dad, admit it you are a failure" after I had spent hours on it, so this might show her I am not as useless as she thinks. I am intending to flash the "mini" CM 9 rom. I hope this is the best one.
bobharding said:
Terrific. I didn't understand it. My daughter lives 100km from me so I will have to visit her this weekend. She left after Christmas saying "Dad, admit it you are a failure" after I had spent hours on it, so this might show her I am not as useless as she thinks. I am intending to flash the "mini" CM 9 rom. I hope this is the best one.
Click to expand...
Click to collapse
I really hope it works (i'm out of solutions ) otherwise you should really think about S-Off'ing it.
miniCM 9 is the fastest one but the sensor buttons don't give a vibration feedback it's a kinda annoying.
Good luck
I have had a very very frustrating day. I tried "update.zip", didn't do anything. I even renamed it "pc49img.zip" nothing. I finally found a windows program called "unlock root". I used the free version. You just connect up the phone via usb and press root. It gets you to confirm it is a wildfire and then after a bit says successfully rooted. I then installed Superuser, Rom Manager and ES File Explorer to check it.
I backed up the present rom successfully with Rom Manager. It even has an option for flashing Clockworkmod recovery and one for rebooting into recovery for manual management. It downloads CWM recovery 5.0.2.0 but it doesn't work either (looking at the files on the SD card I think it is just the same as the "update.zip"). There is also an option for installing a rom from sd card but when I went to this it asked if there was any addon, and of course I need tiny gapps. It then said I need the paid version for this. Seeing the recovery didn't work I didn't want to risk it.
My conclusion is all the present CWM recoveries require S-Off. I have read some people like the Aroma installer. I know nothing about it, but I wonder if it might be possible to install the CM 9 rom with it.
I have worked out what my problem has been. I have fallen for the old Trackball trick. I must be the only person not to know you use the Trackball in CWM recovery not the power button. I sent my daughter an email and she has confirmed the recovery in Rom Manager actually works when you use the Trackball. I will have to visit her again now to install CM 9.
MiniCM9 installed. Working great. I will put a how to in "General"
Okay, so I tried to install Cyanogenmod to my Xperia S and well, I failed. I had flashed clockworkmod v1 since a long time ago and thought how it would go easily to just flash the Cyanogenmod, although, at first I got a message that looked like it was trying to tell me it was the wrong phone (the nozami version of cyanogenmod 9, which I'm quite sure was for Sony LT26) so I tried installing CWM 2, which was remarkably easy with RecoverX. Still got the same message though. So I later tried OpenSEMC-OTA-RC2. Got the same message this time, just that CWM this time said the ROM was for another phone. Both times though, it didn't say any real phone model or anything like that.
So after searching around on the page I found in the installation file that I should fastboot flash the boot.img into the phone and then do a regular flash. For this i used
Code:
fastboot flash boot boot.img
and restarted the phone as I needed to run to school. (Still came 5mins late though )
Continuing in school, my last step was to flash the zip file. This time I got no errors, but neither could I start my phone.
I've bricked the phone and well, I can get into fastboot, but nothing else, really. Not even the charging screen.
So my conclusion would be to run
Code:
fastboot flash recovery recovery-nozami.img
And redo the processes, but it says it needs root to do that, even tho, as I said, its already rooted. What can I do?
Also, the phone is unlocked since quite some time ago
How do I delete this reply?
Petomatick said:
I forgot to tell, the European phone in question is Xperia S, with unlocked bootloader and has been rooted since the day I got it, approximately a year ago.
Click to expand...
Click to collapse
Umm...next time on be a bit polite and someone will come to help you nicely. The developers who work on your phones do so for free and they have no obligation to provide the guides or their development works to you. Its upto you to read the guides or not to. If you would have searched properly then you would find only one guide for installing cwm on your device because xperia s doesnt have a separate recovery partition. you will find only one guide cwm 6.0.3.2 for xperia s by doomlord. Follow the instructions there and then flash the cm package using cwm recovery as per the instructions provided along with cm
Dark Wraith said:
Umm...next time on be a bit polite and someone will come to help you nicely. The developers who work on your phones do so for free and they have no obligation to provide the guides or their development works to you. Its upto you to read the guides or not to. If you would have searched properly then you would find only one guide for installing cwm on your device because xperia s doesnt have a separate recovery partition. you will find only one guide cwm 6.0.3.2 for xperia s by doomlord. Follow the instructions there and then flash the cm package using cwm recovery as per the instructions provided along with cm
Click to expand...
Click to collapse
You're right. I should've calmed down before I wrote the topic. Sorry community.
Also, the phone is from the European region.
Petomatick said:
Okay, so I tried to install Cyanogenmod to my Xperia S and well, I failed. I had flashed clockworkmod v1 since a long time ago and thought how it would go easily to just flash the Cyanogenmod, although, at first I got a message that looked like it was trying to tell me it was the wrong phone (the nozami version of cyanogenmod 9, which I'm quite sure was for Sony LT26) so I tried installing CWM 2, which was remarkably easy with RecoverX. Still got the same message though. So I later tried OpenSEMC-OTA-RC2. Got the same message this time, just that CWM this time said the ROM was for another phone. Both times though, it didn't say any real phone model or anything like that.
So after searching around on the page I found in the installation file that I should fastboot flash the boot.img into the phone and then do a regular flash. For this i used
Code:
fastboot flash boot boot.img
and restarted the phone as I needed to run to school. (Still came 5mins late though )
Continuing in school, my last step was to flash the zip file. This time I got no errors, but neither could I start my phone.
I've bricked the phone and well, I can get into fastboot, but nothing else, really. Not even the charging screen.
So my conclusion would be to run
Code:
fastboot flash recovery recovery-nozami.img
And redo the processes, but it says it needs root to do that, even tho, as I said, its already rooted. What can I do?
Also, the phone is unlocked since quite some time ago
Click to expand...
Click to collapse
Hi,
We do not use fastboot to install cwm or any recovery on the Xperia S as it doesn't have a recovery partition. Instead, the recovery is present in the ramdisk of the kernel. So flashing the boot.img installs cwm too. To get your phone working, please follow these steps -
1. Flash the rom's boot.img throught fastboot.
2. Enter Cwm.
3. Wipe data/factory reset,cache partition, advanced---> wipe dalvik cache
4. Flash the rom zip and reboot.
If your phone still refuses to boot then flash a stock firmware using Flashtool by Androxyde and start the procedure from step one again.
Good luck
abcdjdj
Sent from my LT26i using xda app-developers app
Thank you for your reply, but I cant flash anything. Its telling me the phone isn't rooted, but I know it is.
Good evening everyone!
I've recently wanted to update my Hercules from 4.1 (I know it's reeealy outdated) to version 6.0 Marshmallow.
So I did a few steps and now I cant' seem to go any further, and I need your help.
So far, I've done the following:
-Installed TWRP 2.8.7.0
-Used Odin to flash the TWRP mentioned above
Now, I know there are a few problems regarding this version of the TWRP on the Hercules, so I tried fixing it by using Odin again and flashing the updated 2.8.7.1 and even the 3.0 version that I found on some threads, but with no sucess.
I haven't even had the chance to install Marshmallow on my phone in the first chance, because I couldn't find any .ZIP folders on the TWRP instalation menu.
I really appreciate your help guys, I'm a noob at this and I'm just starting to figure what is what, I just need my phone updated. It's running so far atleast, so it's not hard bricked I guess.
Did you follow the instructions to flash TWRP using Odin?
olafo73 said:
Did you follow the instructions to flash TWRP using Odin?
Click to expand...
Click to collapse
I'm pretty sure I did everything I was intended to do. I installed Samsung Kies so I could install the drivers on my mobile, and then TWRP through Odin properly with the blue light showing up. After flashing it, it turned green and said PASS or PASSED. So I think I did everything right on that end, I can even access TWRP with no real problems.
I even tried to do a ROOT on my system, but again, I couldn't use ZIP or any other files on the TWRP installation option because they simply do not appear
bump
Watching this thread as I have the same problem.
I can boot to TWRP 2.8.7, but if I try to install, there's no file to install from.
I can go back to TWRP 2.6.0, and then mount the card and see the ROM, but every ROM I try fails. Something about non-virtual partitions if I try 4.4 or better, and error executing updater binary if i try 4.1
aguycalled80 said:
Watching this thread as I have the same problem.
I can boot to TWRP 2.8.7, but if I try to install, there's no file to install from.
I can go back to TWRP 2.6.0, and then mount the card and see the ROM, but every ROM I try fails. Something about non-virtual partitions if I try 4.4 or better, and error executing updater binary if i try 4.1
Click to expand...
Click to collapse
How did you go back to TWRP 2.6.0?
N1ZUW said:
How did you go back to TWRP 2.6.0?
Click to expand...
Click to collapse
With Odin.
I can boot in download mode no problem.
N1ZUW said:
Good evening everyone!
I've recently wanted to update my Hercules from 4.1 (I know it's reeealy outdated) to version 6.0 Marshmallow.
So I did a few steps and now I cant' seem to go any further, and I need your help.
So far, I've done the following:
-Installed TWRP 2.8.7.0
-Used Odin to flash the TWRP mentioned above
Now, I know there are a few problems regarding this version of the TWRP on the Hercules, so I tried fixing it by using Odin again and flashing the updated 2.8.7.1 and even the 3.0 version that I found on some threads, but with no sucess.
I haven't even had the chance to install Marshmallow on my phone in the first chance, because I couldn't find any .ZIP folders on the TWRP instalation menu.
I really appreciate your help guys, I'm a noob at this and I'm just starting to figure what is what, I just need my phone updated. It's running so far atleast, so it's not hard bricked I guess.
Click to expand...
Click to collapse
I don't know of any problems with any of the recoveries. However there are different recoveries for different roms which need to be used in a specific order and in a specific way, the first time that you virtually repartition your phone.
Have you gone through the process of applying the "virtual partition" and installing the modified "virtual partition" recovery? This is required for most of the MM roms on this phone (Hercules). The process is very well documented here http://forum.xda-developers.com/galaxy-s2-tmobile/help/guidance-sgh-t989-updating-issue-t3414641 in the #2nd post.
markusrow said:
I don't know of any problems with any of the recoveries. However there are different recoveries for different roms which need to be used in a specific order and in a specific way, the first time that you virtually repartition your phone.
Have you gone through the process of applying the "virtual partition" and installing the modified "virtual partition" recovery? This is required for most of the MM roms on this phone (Hercules). The process is very well documented here http://forum.xda-developers.com/galaxy-s2-tmobile/help/guidance-sgh-t989-updating-issue-t3414641 in the #2nd post.
Click to expand...
Click to collapse
Hi, thanks for replying
No, I dont' take I have taken that step actually. I'm pretty new to this and I tried following every step correctly, but I know that I failed or skipped something at some extent and I've been trying to figure out what exactly, so I can fix it. I guess I need to Virtual Partition my phone then, could you post me the link do to so? Because I think you posted one that would take back to this post
aguycalled80 said:
With Odin.
I can boot in download mode no problem.
Click to expand...
Click to collapse
How do you go in download mode if you have TWRP installed? Does TWRP work as download mode aswell? Thanks for your help man, hope you can fix your phone too!
N1ZUW said:
How do you go in download mode if you have TWRP installed? Does TWRP work as download mode aswell? Thanks for your help man, hope you can fix your phone too!
Click to expand...
Click to collapse
I shut it down in TWRP then hold volume down and power to go into download mode.
My phone has gone backwards now though - it doesn't matter what I load in Odin now, it won't boot up. The SAMSUNG screen is on, with a progress bar, but it never gets to the end. It stops right near the end and it sits there until I reboot it again.
So as the title says, after flashing cm14. 1 can't go into recovery anymore, it just a black screen. I tried to use flashify but nothing, a couple of apps show that I have twrp 3.0.2.1 but can't get into it... Help?
Cheers
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Which thread is this from please?
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Yeah man im in the same boat, if i get time ill try this twrp recovery. Where did that recovery come from?, it seems like the CM recovery for 14.1 nightly high jacks the recovery partition (i call it that,i dont know the term for it)
Sent from my ONEPLUS A3000 using Tapatalk
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Hw4ng3r said:
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Click to expand...
Click to collapse
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Thanks a lot guys, that did the trick, and done with flashify
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
@JKMB888 it does work 100% is as simple as flashing the TWRP. Actually, i installed it with CM 14.1 running just fine
Sent from my ONEPLUS A3000 using Tapatalk
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Edit: I found the solution, i had a pattern lock screen and i removed it!
HC4Life said:
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Click to expand...
Click to collapse
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
GrandMasterB said:
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
Click to expand...
Click to collapse
Look at my edited reply...
m4manusraj said:
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Click to expand...
Click to collapse
actually flashify did the trick for me as I had no access to a pc for the time
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
i am facing just the same situation with cm14.1 nightly and can't boot into recovery
i tried flashing the recovery image provided by you i.e. twrp-3.0.2-22-oneplus3.img but i face the same problem again
when i go into the recovery all i see is a black screen with a white notification light on and it remains there untill i switch off my phone manually using the power button
i tried facing the problem when i installed the cm14.1 nightly
i was unable to login snapchat as i device was rooted as said by the message on snapchat
so i decided to unroot my device via supersu FULL UNROOT option
after a reboot i successfully logged into snapchat
then i tried to root it again
i went into recovery to flash the supersu zip
and since then i have been unable to see the twrp recovey
please help me
This thread is a life save. Tried everything and it drove me nuts not getting into recovery.
THANK YOU!
gangangan2 said:
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
Click to expand...
Click to collapse
Thank you so much it's work for me now..
After I got the recovery back, I flashed CM13 again and ARM64 6.0 Nano Gapps for my Oneplus 3, but I'm getting an error after the "preparing apps' screen is loaded saying that - unfortunately the process android.process.media has stopped one plus 3 boot and then the phone switches off.
Any solution to this? I've already tried flashing different versions of CM13.
Thank you!! I was looking for hours.
This link fixed the problem!
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Hey, guys. I'm pretty sure I bricked my phone and there's no way to get out.
So I was on CM13 official builds on my OP3. Then, on the OTA update system they have, I got moved onto the CM14.1. I downloaded from here and went into my twrp recovery to flash. I made a clean flash and then proceeded to go back to system. I thought everything was ok until I realised I hadn't flashed a gapps package which I pretty much need to survive as all my contacts backups etc. are on there. I powered off my phone and went to go back into the recovery after downloading gapps 7.1 micro. It went past the *You're device can not be trusted'* and then went to the oneplus screen. After that, it stayed like that for about 30 secs and powered off. At first, I thought I messed something up and tried again. I repeated that for about 3 times and it didn't work. I tried going into the normal system and coming back to recovery and it didn't work still. In fact, now I can't even get into system. Now, i can only boot up to fastboot, where my computer still doesn't realise my phone is plugged in.
Anyone got any ideas on how to fix this? I wouldn't say I'm a noob at this because I have flashed many times before but I'm relatively new to the scene. I didn't see this thread before i ripped my hair out and i think wrecked my phone @JKMB888
EDIT: I sorted it out with help from Naman Bhalla's unbrick thread and this. A certain combo works and now I'm on CM14.1 enjoying life