DON'T INSTALL THIS (MANUALLY OR FLASHING)!! Stickman got a bootloop after manual write of the recovery
I just builded a test version with the CWM builder, here is the download link: http://jenkins.cyanogenmod.com/job/recovery/35056/
Personally, i would try the inputrecovery.img cause it has the same size as the original recovery
Good luck
Stickman89 said:
I've built CWM from CM sources. Haven't tried it as of yet though.
Flash at your OWN risk. I will not take responsibility for any actions taken by the user in combination with the provided file... By downloading this image your accepting full liability for any issues that should arise as a result of undergoing ANY flashing/modding on YOUR device.
Click to expand...
Click to collapse
All the credits go to Stickman89 | Thank you for the port
Thank him here: http://forum.xda-developers.com/showthread.php?p=44545580
HOW TO FLASH
-Connect your device in MTP mode
-Enable USB Debuggin
-Open a terminal and navigate to recovery.img's location
-adb reboot-bootloader
-fastboot flash recovery recovery.img
-fastboot reboot
-Done!
To boot into recovery: adb reboot-recovery
This recovery haven't been tested, we don't know acurately if it work (or if the bootloader is fully unlocked), flashing this can BRICK your phone
FYI...
Code:
adb reboot recovery
This will allow you to boot into the stock recovery before you've even flashed a thing. The bootloader is the screen with the static Huawei Logo, therefore I'm pretty certain that this is going to have a very little outcome of disaster since we could still get back into bootloader and/or boot into the ROM.
In any case we perform the below to create a backup recovery.img before doing anything like so:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p11 of=/sdcard/BackupRecovery.img
Before beginning first we need to obtain the dumped "BackupRecovery.img" located on your sdcard as can be seen from the above command.
Copy it onto your machine where your fastboot binaries coincide. Then should you need to restore, you'd need to perform the below:
Code:
adb reboot bootloader
Code:
fastboot flash recovery BackupRecovery.img
Code:
fastboot reboot
If I try just to boot it:
Code:
$ sudo fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.310s]
booting...
FAILED (remote: invalid command)
finished. total time: 0.311s
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recove
y recovery.img
target reported max download size of 838860800 bytes
sending 'recovery' (6816 KB)...
OKAY [ 0.194s]
writing 'recovery'...
[B]FAILED (remote: flash failure, ErrNo:2)[/B]
finished. total time: 0.200s
Yeah our bootloader sucks, I tried... No harm caused whatsoever.
Best Regards,
s89
I'm going to try flashing it through stock recovery as an update.zip.
Try a flash all, flash origial B107 boot, efi, modem and after that, recovery. When i get my laptop, i'll explain it better
Sent from my HUAWEI P6-U06 using xda app-developers app
Stickman89 said:
I'm going to try flashing it through stock recovery as an update.zip.
Click to expand...
Click to collapse
How's work? . We are nervous and excited. Thank champion.
Stickman and me are searching an alternative method to get the recovery in a secondary partition, keep reading this forum for more info
Sent from my HUAWEI P6-U06 using xda app-developers app
For now I urge all people to not flash the provided recovery.img for the time being whilst we are investigating a safer alternative for implementing CWM for our device. Please be patient in the meantime, thankyou.
Added a version builded with CWM, inputrecovery.img have the same size of the original recovery so it should work, as usual, flash etc etc at our own risk
Haven't seen any updates on this, does it work?
It won't work until huawei release a tool to sign the UPDATE.APP.
I'm sorry
Sent from my HUAWEI P6-U06 using xda app-developers app
S34Qu4K3 said:
It won't work until huawei release a tool to sign the UPDATE.APP.
I'm sorry
Sent from my HUAWEI P6-U06 using xda app-developers app
Click to expand...
Click to collapse
Understandable, thanks for the reply. Makes me want to see this and just get device that's fully unlocked with 3rd party ROM support. =(
S34Qu4K3 said:
flashing this can BRICK your phone
Click to expand...
Click to collapse
so why u putting it here u mento ..
Yeah, if it's not working don't upload it here. When you make something that's working, upload, everyone who is developing here must upload only working 100 % stuff, not unstable stuff that can brick people's phones.
HUAWEIAscendP6 said:
Yeah, if it's not working don't upload it here. When you make something that's working, upload, everyone who is developing here must upload only working 100 % stuff, not unstable stuff that can brick people's phones.
Click to expand...
Click to collapse
You're wrong, we need those devs, who contribute.
With our Phone we have the Problem, that we only can flash unsigned things on B118CN.
So we can only start real developing with this Firmware.
Or at least a other firmware without signing-check.
Users must read before they flash something. Everything with isn't functioning correctly (at this point) shows visible that it can brick our device.
Without testing-builds there will be no working builds!
raolleel said:
You're wrong, we need those devs, who contribute.
With our Phone we have the Problem, that we only can flash unsigned things on B118CN.
So we can only start real developing with this Firmware.
Or at least a other firmware without signing-check.
Users must read before they flash something. Everything with isn't functioning correctly (at this point) shows visible that it can brick our device.
Without testing-builds there will be no working builds!
Click to expand...
Click to collapse
Maybe devs should do tests on their own phones.
HUAWEIAscendP6 said:
Maybe devs should do test on their own phones.
Click to expand...
Click to collapse
I don't know why you are so mean, and you don't understand testing builds.
Even if a build doesn't work, even if there are bugs we should contribute our builds.
The community can help to erase the bugs, everyone can contribute to those projects.
Keep in mind building Roms, Kernels, Mods isn't easy, it needs very much time and concentration.
We don't get any money, we all do this to contribute to the community.
Devs help each other, to erase bugs.
Not everyone can test the builds, maybe they don't have the phone, maybe their phone is in rapair or something.
People like you are those, who should think before they post.
You get our stuff for fee. So say thank you, and don't comment on them, cause there are not bugfree.
HUAWEIAscendP6 said:
Maybe devs should do test on their own phones.
Click to expand...
Click to collapse
We do Test things prior to uploading and sharing, BUT we can't control what the user (the rest of the community) will do with what we share. If you utilize wrong commands to flash a kernel, recovery or whatever then it will not be Developer's fault. That's the reason for the big bold warning at the beginning of each development thread.
And last for not least, The developer is not FORCING you to test something that can brick your phone, it is up to you and it'll be your responsability if the phone bricks.
I've seen your posts, and most of the time you keep complaining about the phone, about a ROM, a recovery etc... If you don't like it sell it and if this or that doesn't work for you don't use it.
Just my 2 cents...
jimbo77 said:
We do Test things prior to uploading and sharing, BUT we can't control what the user (the rest of the community) will do with what we share. If you utilize wrong commands to flash a kernel, recovery or whatever then it will not be Developer's fault. That's the reason for the big bold warning at the beginning of each development thread.
And last for not least, The developer is not FORCING you to test something that can brick your phone, it is up to you and it'll be your responsability if the phone bricks.
I've seen your posts, and most of the time you keep complaining about the phone, about a ROM, a recovery etc... If you don't like it sell it and if this or that doesn't work for you don't use it.
Just my 2 cents...
Click to expand...
Click to collapse
I don't know what posts you saw, but show me one post in which I complain about the phone.
Related
I always flash a new radio with recovery and I have now been told this is not the correct way on doing this, But all radio flash tutorials I have read say to do it this way.
What all your votes on this?
Depends on if you have modified nand partitions. If you have one with a cache partition to small to hold radio you HAVE to flash from fastboot.
Apart from that I believe there is little difference in the risks associated.
superste2201 said:
Depends on if you have modified nand partitions. If you have one with a cache partition to small to hold radio you HAVE to flash from fastboot.
Apart from that I believe there is little difference in the risks associated.
Click to expand...
Click to collapse
I have stock nand, what's the limit cache on that? new radio is out its a 11mb zip
Am worried using recovery now lol this will be my 4th radio flash with recovery and not one single problem?
it is generally safer to flash radio from fastboot.
if it can go wrong, then it is defienietly more probable while doing that trough recovery.
shankly1985 said:
I have stock nand, what's the limit cache on that? new radio is out its a 11mb zip
Am worried using recovery now lol this will be my 4th radio flash with recovery and not one single problem?
Click to expand...
Click to collapse
Stock should have 40 mb cache, if i remember well...sure you can flash it via recovery then, but fastboot is still safer imo.
vnvman said:
Stock should have 40 mb cache, if i remember well...sure you can flash it via recovery then, but fastboot is still safer imo.
Click to expand...
Click to collapse
Think am just going to stick with recovery like I said I not had one problem.
shankly1985 said:
Think am just going to stick with recovery like I said I not had one problem.
Click to expand...
Click to collapse
It's your choice, tho bricking is more frequent with that way: if the archive gets damaged recovery will flash it anyway and eventually brick your device, fastboot instead doesn't allow you to flash a malformed image, afaik...
vnvman said:
It's your choice, tho bricking is more frequent with that way: if the archive gets damaged recovery will flash it anyway and eventually brick your device, fastboot instead doesn't allow you to flash a malformed image, afaik...
Click to expand...
Click to collapse
True I never thought of that
Can I use this fastboot on windows7? Is there a upto data tutorial you can link me to please that would be great thanks.
shankly1985 said:
True I never thought of that
Can I use this fastboot on windows7? Is there a upto data tutorial you can link me to please that would be great thanks.
Click to expand...
Click to collapse
Yep, you can use it (i got the same os), but in order to do that you have to download the android sdk and set up adb properly. There's a lot of tutorials on how to do this, here's the first i stumbled across:
http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
Imho it's a rule of thumb to have a working adb/fastboot if you wanna be into the rom flashing thing: sooner or later they'll save your arse
vnvman said:
Yep, you can use it (i got the same os), but in order to do that you have to download the android sdk and set up adb properly. There's a lot of tutorials on how to do this, here's the first i stumbled across:
http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
Imho it's a rule of thumb to have a working adb/fastboot if you wanna be into the rom flashing thing: sooner or later they'll save your arse
Click to expand...
Click to collapse
Thanks yes I already have all that done and installed USB driver's. I did this when first rooting my phone
so it just learning how to use fastboot
So what ive been reading is this true.
As long has the zip file is not damaged you should be ok flashing in recovery. So if I just check zip file befor flashing for error's I will be fine?
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?
Developer Koush has a tool to build from the latest sources for ClockworkMod Recovery. It gives you the most recent changes in code so you don't need to wait for an official build.
DISCLAIMER:
Neither myself nor Koush is responsible for any damages caused to your device. These are EXPERIMENTAL / BETA builds and include code that may or may not have been approved by the developer for your specific device. Proceed at your own risk.
11/28/2012
Here is the latest build that is supposed to be optimized for JB 4.2
CWM-6.0.1.9-touch-recovery.img
Just did minor testing and it works fine.
As always...use at your own risk. I am not responsible for the bad things that happen to you. That's just called karma.
Click to expand...
Click to collapse
Tool: http://builder.clockworkmod.com/
Go to the "Existing Devices" tab and select "crespo4g" and use the check-box to toggle the option for touch recovery.
Credit goes to Koush for his build tool and custom recovery.
OLD
CWM 6.0.1.3 w/ Touch for fastboot: CWM-6.0.1.3-touch-recovery.img
CWM 6.0.1.3 w/o Touch for fastboot: CWM-6.0.1.3-recovery.img
The new version includes the option to create a flashable .zip from your current ROM while preserving your privacy by leaving out the /data partition.
Click to expand...
Click to collapse
cant get this to install
andrewddickey said:
Developer Koush has a tool to build from the latest sources for ClockworkMod Recovery. It gives you the most recent changes in code so you don't need to wait for an official build.
DISCLAIMER:
Neither myself nor Koush is responsible for any damages caused to your device. These are EXPERIMENTAL / BETA builds and include code that may or may not have been approved by the developer for your specific device. Proceed at your own risk.
CWM 6.0.1.3 w/ Touch for fastboot: CWM-6.0.1.3-touch-recovery.img
CWM 6.0.1.3 w/o Touch for fastboot: CWM-6.0.1.3-recovery.img
The new version includes the option to create a flashable .zip from your current ROM while preserving your privacy by leaving out the /data partition.
Tool: http://builder.clockworkmod.com/
Go to the "Existing Devices" tab and select "crespo4g" and use the check-box to toggle the option for touch recovery.
Credit goes to Koush for his build tool and custom recovery.
Click to expand...
Click to collapse
This will not install for me for some reason. I keep trying with fastboot and it keeps failing some failed: write error or something likes that. i even put the img in a zip and it still wont flash it. I dont know what i am doing wrong
nwo122383 said:
This will not install for me for some reason. I keep trying with fastboot and it keeps failing some failed: write error or something likes that. i even put the img in a zip and it still wont flash it. I dont know what i am doing wrong
Click to expand...
Click to collapse
Which one? Touch or regular? I used the touch .img and flashed on my phone just fine.
Put it in the same folder as fastboot and rename it to "recovery.img"
Use the command:
fastboot flash recovery recovery. img
Both give me the same problem I can flash other recoveries this just will not work I'll try again tomorrow
Sent from my Nexus S 4G using Tapatalk 2
Hypothetically speaking, would this tool work on any recovery....for example, twrp....or a ps freedom port so I could use my ns4g as a ps3 factory service mode dongle?
Both give me the same problem I can flash other recoveries this just will not work I'll try again tomorrow<br />
<br />
<br />
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
I'll check when I get to the office in the morning. Might be an issue with the upload. Might have to re-up again.
hp420 said:
Hypothetically speaking, would this tool work on any recovery....for example, twrp....or a ps freedom port so I could use my ns4g as a ps3 factory service mode dongle?
Click to expand...
Click to collapse
To the best of my knowledge...no.
Only for CWM since it syncs with Koush's code.
nwo122383 said:
This will not install for me for some reason. I keep trying with fastboot and it keeps failing some failed: write error or something likes that. i even put the img in a zip and it still wont flash it. I dont know what i am doing wrong
Click to expand...
Click to collapse
My stupid fat fingers hit thanks on the wrong post
I had no issues flashing this recovery thru flash image gui...
Sent from my Nexus S 4G using Tapatalk 2
Just a little side note. When flashing a recovery or boot image via fastboot, and you have problems, try the erase command first:
fastboot erase recovery
Then
fastboot flash recovery recovery.img
Just a good safety measure.
Later,
~WickiD~
-----
Sent from my phone
using my finger...
-----
wickid_d said:
Just a little side note. When flashing a recovery or boot image via fastboot, and you have problems, try the erase command first:
fastboot erase recovery
Then
fastboot flash recovery recovery.img
Just a good safety measure.
Later,
~WickiD~
-----
Sent from my phone
using my finger...
-----
Click to expand...
Click to collapse
I just tried this and still same error
FAILED (remote: Write Fail)
i just cant seem to get this recovery to load. i can flash any other recovery via fastboot except this one. i flashed earlier cwm and twrp. i also tried putting this in a flashable zip that didnt work and then i tried using flash image gui to get this to work and that did not work. i dont know what i am doing wrong.
i am going to try to redownlad the files and try to flash again maybe i got 2 bad downloads.
update: even after redownloading still getting that same error. but i can flash other recoveries this is perturbing me.
nwo122383 said:
i just cant seem to get this recovery to load. i can flash any other recovery via fastboot except this one.
Click to expand...
Click to collapse
Ditto. No info to provide as to why I am having trouble. No worries
This recovery Success damaged my d720 after format sdcard system and data.. cwm cant mount it after reboot... even twrp can help or stock recovery will not recognized.. but folder is there if check via adb command.
Sent from my Galaxy Nexus using xda premium
6.0.1.9
Here is the latest build that is supposed to be optimized for JB 4.2
CWM-6.0.1.9-touch-recovery.img
Just did minor testing and it works fine.
As always...use at your own risk. I am not responsible for the bad things that happen to you. That's just called karma.
andrewddickey said:
Here is the latest build that is supposed to be optimized for JB 4.2
CWM-6.0.1.9-touch-recovery.img
Just did minor testing and it works fine.
As always...use at your own risk. I am not responsible for the bad things that happen to you. That's just called karma.
Click to expand...
Click to collapse
Hmm..I found that USB mount doesn't work in 6.0.1.9 (crespo)
So I guess there'll be same issue can be occured in crespo4g.
Sent from my Nexus S using Tapatalk 2
andrewddickey said:
Here is the latest build that is supposed to be optimized for JB 4.2
CWM-6.0.1.9-touch-recovery.img
Just did minor testing and it works fine.
As always...use at your own risk. I am not responsible for the bad things that happen to you. That's just called karma.
Click to expand...
Click to collapse
Karma would be the things that happen to you when ya have it coming...not things that happen due to glitched software and such. Have you tested the primary uses for the update you posted? Any negative results found? Just a matter of curiosity...
Sent from my Nexus S 4G using XDA Premium HD app
---------- Post added at 10:57 PM ---------- Previous post was at 10:55 PM ----------
Just asking as I would hate to have to send the whole night troubleshooting my device to sort out the bad karma lol
Sent from my Nexus S 4G using XDA Premium HD app
Thanks for clearing that up for me.
Working:
Flash
Backup
Restore
Wipes
Fix Permissions
Not Working:
Mount USB
Odd:
When you select "Reboot System", it asks if you want to disable ROMs from flashing a recovery. Just hit "Back" to reboot.
That's the extent of my testing. Will do more tomorrow.
He did remove all the extra "No"s when confirming selection. That's nice.
Is there a way to flash this from my phone?
Sent from my Nexus S 4G using Tapatalk 2
---------- Post added at 03:38 AM ---------- Previous post was at 03:18 AM ----------
Nm
Sent from my Nexus S 4G using Tapatalk 2
no matter how many recoveries i try to flash through fastboot, nothing stays, it always sends me to stock recovery. any tips?
lemonoid said:
no matter how many recoveries i try to flash through fastboot, nothing stays, it always sends me to stock recovery. any tips?
Click to expand...
Click to collapse
I think you have to change a file name to install.recovery.sh.old or something like that
where is the guide or tutorial?
where is the guide or tutorial?
Hi I just bought a 2nd hand M8 s-on tampered whenever I go to bootloader then select recovery it just stock on htc logo for a very long time so hard to off even pressing power button.
question is, is it possible to delete the recovery installed? I suspect he deleted the custom recovery installed on that phone.? or can I use flashify to add new TWRP? thanks hope someone will help me
Yes, you can use fastboot to boot or install a new recovery.
First, get a recovery image - either TWRP or CWM. Make sure you download the .img file for your phone. Then, boot into fastboot mode and flash it. This thread covers pretty much everything you need - just skip the bootloader unlock section, as you are already unlocked:
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
jshamlet said:
Yes, you can use fastboot to boot or install a new recovery.
First, get a recovery image - either TWRP or CWM. Make sure you download the .img file for your phone. Then, boot into fastboot mode and flash it. This thread covers pretty much everything you need - just skip the bootloader unlock section, as you are already unlocked:
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
Click to expand...
Click to collapse
thanks BTW Im not good on those command Ive tried on my m7 last month i think to use flashify to install a new recovery can I use the same method?
imfuzzyyy said:
thanks BTW Im not good on those command Ive tried on my m7 last month i think to use flashify to install a new recovery can I use the same method?
Click to expand...
Click to collapse
My recommendation would be to learn how to do it with adb/fastboot. Apps like Flashify are a crutch, and won't do you any good if you find yourself in a jam, such as not being able to boot into the OS.
Don't forget to: fastboot erase cache
thanks for your help evryone but i really dont know all of those command but can I use flashify for this method?
imfuzzyyy said:
thanks for your help evryone but i really dont know all of those command but can I use flashify for this method?
Click to expand...
Click to collapse
You won't know the commands either if you don't learn to use them but instead rely on apps like flashify. Why have a custom recovery like TWRP? Are you planning on flashing a custom ROM? What if that custom ROM doesn't boot up and you can't get into the OS, how will you then fix the problem seeing as flashify won't be available to you?
I'm in agreement with Redpoint on this, you should really consider learning the basic commands at least. It will make fixing any problems you might encounter much more simpler. Relying on all-in-one toolkits and apps like flashify won't make matters easier for you if things go "South".
The issue however is not that you don't know it, instead it's your reluctance to want to learn it. Yet when something goes wrong you'd still come on here expecting everyone else to fix the problem for you.
[Guide] How To Setup And Use Fastboot
There you can find some reading materials for fastboot commands.
{Tutorial} (Basics of ADB) For Beginners Part-1
There's some stuff about adb as well.
XDA-University Some great informative threads right here on XDA. Everyone here is more than willing to help someone with problems, no doubt. The least, however, that you can do is also educate yourself on the basics, else it's just insulting to expect others to go through such effort if you yourself can't even make the effort to learn anything. Especially if you are the one(inexperienced) that wants to flash and make changes to his device. :good:
If you're willing to learn some and need help along the way, then ask and anyone here can help and would be more than happy to! :highfive:
All that said, download the recovery you need. Get yourself adb or the mini-sdk from mike1986's site get it set up and start doing things the right way.
After you have it all set up. Connect phone to PC, reboot to bootloader.
Code:
adb reboot bootloader
Flash recovery
Code:
fastboot flash recovery name_of_recovery.img
Clear cache
Code:
fastboot erase cache
Reboot and enjoy.
Code:
fastboot reboot
BerndM14 said:
You won't know the commands either if you don't learn to use them but instead rely on apps like flashify. Why have a custom recovery like TWRP? Are you planning on flashing a custom ROM? What if that custom ROM doesn't boot up and you can't get into the OS, how will you then fix the problem seeing as flashify won't be available to you?
I'm in agreement with Redpoint on this, you should really consider learning the basic commands at least. It will make fixing any problems you might encounter much more simpler. Relying on all-in-one toolkits and apps like flashify won't make matters easier for you if things go "South".
The issue however is not that you don't know it, instead it's your reluctance to want to learn it. Yet when something goes wrong you'd still come on here expecting everyone else to fix the problem for you.
[Guide] How To Setup And Use Fastboot
There you can find some reading materials for fastboot commands.
{Tutorial} (Basics of ADB) For Beginners Part-1
There's some stuff about adb as well.
XDA-University Some great informative threads right here on XDA. Everyone here is more than willing to help someone with problems, no doubt. The least, however, that you can do is also educate yourself on the basics, else it's just insulting to expect others to go through such effort if you yourself can't even make the effort to learn anything. Especially if you are the one(inexperienced) that wants to flash and make changes to his device. :good:
If you're willing to learn some and need help along the way, then ask and anyone here can help and would be more than happy to! :highfive:
All that said, download the recovery you need. Get yourself adb or the mini-sdk from mike1986's site get it set up and start doing things the right way.
After you have it all set up. Connect phone to PC, reboot to bootloader.
Code:
adb reboot bootloader
Flash recovery
Code:
fastboot flash recovery name_of_recovery.img
Clear cache
Code:
fastboot erase cache
Reboot and enjoy.
Code:
fastboot reboot
Click to expand...
Click to collapse
thanks for the help bro., btw where can I install official TWRP for our m8? can you provide some link? really appreciate it thanks
imfuzzyyy said:
thanks for the help bro., btw where can I install official TWRP for our m8? can you provide some link? really appreciate it thanks
Click to expand...
Click to collapse
TWRP 2.8 - HTC One m8 2014 GSM page
*IT IS FOR UNLOCKED BOOTLOADERS ONLY*
Voila ..
Alas TWRP is working on Nokia 8 NB1 based on v4.88B kernel. Wifi and Magisk root both are working on my mobile. Please and report if it is working for you as well.
Download:
https://mega.nz/#!nRgVWKqB!fWx4zO1f19Shs_I8Thkw4ycsZMMMmSYP24cK0MHIBlM
Flash:
adb reboot bootloader
fastboot flash boot_a TWRP_NB1_boot_v2.img
fastboot reboot
Click to expand...
Click to collapse
If working well, also flash boot_a partition as well.
Then following below thread to root it using MagiskManager
https://forum.xda-developers.com/nokia-8/development/pre-rooted-boot-image-nokia-nb1-v4-88b-t3798063
Check Following Post for Update:
https://forum.xda-developers.com/showpost.php?p=77307135&postcount=74
WARNING: Don't change boot slot using TWRP . I am not responsible if you brick your phone.
Many thanks!
Does this mean if you have this IMG, you can flash after any other (even older) IMGs without verify check?
With fastboot and OST LA from here?
That would be a fantastic news!!! :good:
Overall, the fastboot doesn't seem to work on my device. Once I get my phone into bootloader state it says naturally DOWNLOAD MODE but any fastboot devices command ends up with <Waiting for devices>. I've switched drivers from Nokia's one to diffrent non device specific but nothing helps. Any idea on how to fix it ?
- edit -
Came out that the adb and fastboot drivers can't be outdated so be sure to use newest from SDK Platform Tools - otherwise u won't see the device.
head66 said:
Many thanks!
Does this mean if you have this IMG, you can flash after any other (even older) IMGs without verify check?
With fastboot and OST LA from here?
That would be a fantastic news!!! :good:
Click to expand...
Click to collapse
Didn't checked by flashing it. But, logically yes. Though system partition is still encrypted. That may cause an issue. But for custom ROM developers - it can be a start. Provided - your bootloader is unlocked.
KonikoO said:
Overall, the fastboot doesn't seem to work on my device. Once I get my phone into bootloader state it says naturally DOWNLOAD MODE but any fastboot devices command ends up with <Waiting for devices>. I've switched drivers from Nokia's one to diffrent non device specific but nothing helps. Any idea on how to fix it ?
- edit -
Came out that the adb and fastboot drivers can't be outdated so be sure to use newest from SDK Platform Tools - otherwise u won't see the device.
Click to expand...
Click to collapse
Hey,
maybe that can help u.
Fastboot need Admin permissions on windows open a CMD as Admininstator.
On Linux just login into user root.
WORKING
Image is working! Thanks a lot!
Magisk is also working after patch. (With WiFi)
KonikoO said:
Overall, the fastboot doesn't seem to work on my device. Once I get my phone into bootloader state it says naturally DOWNLOAD MODE but any fastboot devices command ends up with <Waiting for devices>. I've switched drivers from Nokia's one to diffrent non device specific but nothing helps. Any idea on how to fix it ?
- edit -
Came out that the adb and fastboot drivers can't be outdated so be sure to use newest from SDK Platform Tools - otherwise u won't see the device.
Click to expand...
Click to collapse
Did you checked if USB debugging is on in the developer settings?
Powered by View 10
KonikoO said:
Overall, the fastboot doesn't seem to work on my device. Once I get my phone into bootloader state it says naturally DOWNLOAD MODE but any fastboot devices command ends up with <Waiting for devices>. I've switched drivers from Nokia's one to diffrent non device specific but nothing helps. Any idea on how to fix it ?
- edit -
Came out that the adb and fastboot drivers can't be outdated so be sure to use newest from SDK Platform Tools - otherwise u won't see the device.
Click to expand...
Click to collapse
I have it problem on Windows 10 too. If you want very strong, download any Linux-based LiveCD, flash it on USB and load. After this install adb and fastboot from LineageOS site (delete space after "https://" https:// wiki.lineageos.org/devices/bacon/build) and run commands.
P.S.: I am sorry for my bad English, but I hope help you
Wow, you are a genius! So glad to see twrp on our Nokia 8 xD but with encrypted /system. Does it mean nandroid backup is not possible at the moment? Also, with your magisk patched kernel, can i flash over or do i need to first flash twrp then reroot with your method?
corpsegrinder62 said:
Wow, you are a genius! So glad to see twrp on our Nokia 8 xD but with encrypted /system. Does it mean nandroid backup is not possible at the moment? Also, with your magisk patched kernel, can i flash over or do i need to first flash twrp then reroot with your method?
Click to expand...
Click to collapse
Flash TWRP img, then re-root using Magisk method provided in the URL.
Created another version of TWRP. Now /data is browsable, but showing garbled file names So, nanodroid is still unachievable. Don't have a backup phone, so could not take the risk of loosing my data, else could have un-encrypt ICE filesystem encryption and could have build a stock based ROM without encrypted partition.
bidhata said:
Flash TWRP img, then re-root using Magisk method provided in the URL.
Created another version of TWRP. Now /data is browsable, but showing garbled file names So, nanodroid is still unachievable. Don't have a backup phone, so could not take the risk of loosing my data, else could have un-encrypt ICE filesystem encryption and could have build a stock based ROM without encrypted partition.
Click to expand...
Click to collapse
Thanks bro. You are making tremindous progress on this phone though. Hopefully you inspire other devs to jump the train on our N8
Does this work with a locked bootloader? And if so do I just follow the steps here? Or do I need OST LA?
thank you so much for your time and effort. Much appreciated. Can the stock recovery be backed up and restored Later? Is it advised to flash it on TA 1012 Nokia 8 unlocked? How can we revert to the original state? Does OEM Unlock help in this case? Is it an image of the whole OS like previous mod attempts?
iKillua said:
Does this work with a locked bootloader? And if so do I just follow the steps here? Or do I need OST LA?
Click to expand...
Click to collapse
You need an unlocked bootloader. Else fastboot not let you overwrite /boot partition. No OST LA required.
trandafirmd said:
thank you so much for your time and effort. Much appreciated. Can the stock recovery be backed up and restored Later? Is it advised to flash it on TA 1012 Nokia 8 unlocked? How can we revert to the original state? Does OEM Unlock help in this case? Is it an image of the whole OS like previous mod attempts?
Click to expand...
Click to collapse
There is no different partition for recovery. So, just flashing the original boot partition ( boot.img ) will be enough to restore. OEM unlocked is required to decrypt the /data partition. This one is just the boot.img modification.
bidhata said:
There is no different partition for recovery. So, just flashing the original boot partition ( boot.img ) will be enough to restore. OEM unlocked is required to decrypt the /data partition. This one is just the boot.img modification.
Click to expand...
Click to collapse
Is this img suitable for restore https://mega.nz/#!yYwUWKwC!5wb2EkDhFKE2QIhI5tW0SE_uqkn2UL2uEPkTM01G5Mg?0 I can't see any 1012 img's How can I backup the boot.img from my phone?
Thank you.
trandafirmd said:
Is this img suitable for restore https://mega.nz/#!yYwUWKwC!5wb2EkDhFKE2QIhI5tW0SE_uqkn2UL2uEPkTM01G5Mg?0 I can't see any 1012 img's How can I backup the boot.img from my phone?
Thank you.
Click to expand...
Click to collapse
It is the same image for TA 1004 / TA-1012 . Taken from v4.88B update.
I realized that after the download finished. I apologize for jumping the gun. Since I'll have to unlock my bootloader, is there a way to do a full system backup through adb or otherwise? Most likely, I have a locked bootloader and before I can figure out a way to unlock it, I will have to backup as much data as possible since unlocking it will most likely wipe all my data and do a factory reset.
You can not make a backup unfortunately.
could you and other people making useless threads put it in the thread title and OP so that 99.9% of nokia 8 owners that dont have a way of unlocking the bootloader dont waste our time by having the salt rubbed in, thanks