Well here is cwm 6.0.4.5 for our beloved a500. You will need this to flash KitKat ROMs like the new kitkat rom that was recently relased for our tablet. It is recommended that you flash this in secboot as I am not very sure what works and what does not. It pays to have a working recovery in your recovery partition.
To flash this rom in your secboot, you must have skrilax bootloader installed from http://forum.xda-developers.com/showthread.php?t=1619913
Download link of recovery: http://www.mediafire.com/view/?myy59371lsrs6u4
Instructions:
1. Use this awesome tool from http://forum.xda-developers.com/showthread.php?t=2588979 to install adb and fastboot on your windows pc easily. (Remember to run the downloaded exe as administrator)
2. Install Acer A500 usb drivers from http://us.acer.com/ac/en/US/content/drivers (Just search for A500 in the search by product model search box.)
3. Make sure you have Skrilax_CZ's bootloader installed on your A500.
4. Turn off your A500 and turn it on again, this time holding the volume up button.
5. When the bootloader screen appears, scroll with the volume buttons and select Fastboot with the power button.
6. Now, copy the recovery.img which you downloaded from the download link above to the root of your C:/ drive.
7. Press start and open cmd.
8. In cmd, type cd C:/
9. Now, connect your A500 to the PC via usb and wait for a while before typing
Code:
fastboot flash secboot recovery.img
in cmd.
10. After the process is done, type
Code:
fastboot reboot
into cmd.
11. When the tablet boots, hold volume up and when the bootloader screen shows, scroll to Boot Secondary Kernel Image with the volume keys and select it with the power button. CWM should load and have fun!!!
Thanks to @pjsports for his 4.3 device source and vendor blobs
nelsontky said:
Well here is cwm 6.0.4.5 for our beloved a500. You will need this to flash KitKat ROMs in the future. It is recommended that you flash this in seboot as I am not very sure what works and what does not. It pays to have a working recovery in your recovery partition.
Download link: http://www.mediafire.com/view/?myy59371lsrs6u4
Installation:
fastboot flash secboot recovery.img (recommended)
Or
fastboot flash recovery recovery.img
Thanks to @pjsports for his 4.3 device source and vendor blobs
Click to expand...
Click to collapse
ok this is what i get when i try to flash this or any recovery
C:\sdk-tools>fastboot flash recovery recovery.img
sending 'recovery' (5132 KB)... OKAY [ 1.278s]
writing 'recovery'... FAILED (remote: (00030003))
finished. total time: 1.675s
C:\sdk-tools>
any ideas?
ok I got a recovery on there but now it is not seeing any files within my folders- this is so strange
I tried flashing this recovery but i get this error
also i tried flashing the img recovery with this app but i don't work either
https://play.google.com/store/apps/details?id=com.cgollner.flashify
nsciucco said:
ok this is what i get when i try to flash this or any recovery
C:\sdk-tools>fastboot flash recovery recovery.img
sending 'recovery' (5132 KB)... OKAY [ 1.278s]
writing 'recovery'... FAILED (remote: (00030003))
finished. total time: 1.675s
C:\sdk-tools>
any ideas?
ok I got a recovery on there but now it is not seeing any files within my folders- this is so strange
Click to expand...
Click to collapse
Erm what ROM are u using. And yea do you have like zip files in your folders cos I think the recovery only see zip files
tire_007 said:
I tried flashing this recovery but i get this error
also i tried flashing the img recovery with this app but i don't work either
https://play.google.com/store/apps/details?id=com.cgollner.flashify
Click to expand...
Click to collapse
Dun use the app (idk those apps never worked for me, well except for the Acer recovery installer) and when using fastboot, make sure the recovery.IMG is in the same directory as fastboot
I was on cm10.2. My tablet froze so I held the power button down to hard reset. Then it never booted up. I tried to go into recovery to install a new rom and I'm not even able to get into downloads. If I click sd or sd-ext there is no folders anything. It's like my device is wiped. I'm stuck. Only thing I can do is get into bootloader or apx mode. I've downloaded roms that I can supposedly flash in apx mode with that blackthunder tool. But I can't figure it out. I'm not an idiot either. I've rooted well over 200 phones . I do it for extra cash...and never had a issue like this
Sent from my SM-N900P using xda app-developers app
nsciucco said:
I was on cm10.2. My tablet froze so I held the power button down to hard reset. Then it never booted up. I tried to go into recovery to install a new rom and I'm not even able to get into downloads. If I click sd or sd-ext there is no folders anything. It's like my device is wiped. I'm stuck. Only thing I can do is get into bootloader or apx mode. I've downloaded roms that I can supposedly flash in apx mode with that blackthunder tool. But I can't figure it out. I'm not an idiot either. I've rooted well over 200 phones . I do it for extra cash...and never had a issue like this
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
Hmmm download a working recovery and flash into your recovery partition. Then flash this into secboot
Flash what?
Sent from my SM-N900P using xda app-developers app
nsciucco said:
Flash what?
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
Well you can download twrp from http://teamw.in/project/twrp2/88 and flash it to your secboot partition with "fastboot flash secboot [name of recovery].img" Then go to your boot menu (hold volume up when booting) and choose the akb partition (second partition) This should get you booted into twrp where your files should be there. If there are still no files, you have to use an external sdcard good luck
any chance you can build this: http://forum.xda-developers.com/showthread.php?t=2201860
against our device + CWM version 6.0.4.8?
I'd do it, but I have no idea where to start. I love PhilZ touch recovery, it's very customizable and also very useful.
kronflux said:
any chance you can build this: http://forum.xda-developers.com/showthread.php?t=2201860
against our device + CWM version 6.0.4.8?
I'd do it, but I have no idea where to start. I love PhilZ touch recovery, it's very customizable and also very useful.
Click to expand...
Click to collapse
Well i can try but no promises
thanks! apparently it's easy.
Once you can build stock CWM, just replace your bootable/recovery folder with this one and lunch for your device
Click to expand...
Click to collapse
I just don't have the sources, or the knowhow to compile this myself.
nelsontky said:
Well i can try but no promises
Click to expand...
Click to collapse
had a chance to try yet? not to bug or nag, just curious for an update
Now updated with instructions
Now this is updated with instructions!
thanks man.
good work
nelsontky said:
Now this is updated with instructions!
Click to expand...
Click to collapse
can you provide building instructions? I tried using the sources you used, but I get errors using his repos. He's got some repos from "loosethisskin" which don't allow building. I can't remember the exact errors, but I'm wondering what you did to avoid this(if you encountered this at all)
By simply not replacing those repos(ie: removing them from the manifest before syncing) I get a resulting recovery.img that fails to fastboot flash.
I've even tried using acer recovery flasher, and a couple other tools, but it doesn't boot.
I'd like to try building 6.0.5.0 as well as PhilZ Recovery, but again, I can't get it to build.
@nelsontky
Thanks for your job.
I want to make a backup before to install the new Bootloader ( Skrilax_CZ's), but to that I cannot do it with stock recovery (the stock recovery didn't have the option to backup/restore).
Is there some problem/incompatibility that avoid to load your recovery (6.0.4.5) before to load Skrilax_CZ's bootloader?
Or in another way the function of your recovery are based on Skrilax_CZ's bootloader?
Could you update your recovery with new file from CWM Github (recovery version is now 6.0.5.0)?
Could you post the configuration file (Board parameters) that you use to compile the recovery.
I downloaded the source of CWM and I want to test it myself.
If you update your CWM repository via GitHub pull command just recompile the recovery.
Proposal to download the file: could be better to distribute the recovery as zip (like A500_CWM_recovery_vx.x.x.x.x.zip - it's self explantory) with inside the recovery.img file. It's always better to avoid to download native recovery image to avoid partial download or corrupted file.
Thanks.
bovirus said:
@nelsontky
Thanks for your job.
I want to make a backup before to install the new Bootloader ( Skrilax_CZ's), but to that I cannot do it with stock recovery (the stock recovery didn't have the option to backup/restore).
Is there some problem/incompatibility that avoid to load your recovery (6.0.4.5) before to load Skrilax_CZ's bootloader?
Or in another way the function of your recovery are based on Skrilax_CZ's bootloader?
Could you update your recovery with new file from CWM Github (recovery version is now 6.0.5.0)?
Could you post the configuration file (Board parameters) that you use to compile the recovery.
I downloaded the source of CWM and I want to test it myself.
If you update your CWM repository via GitHub pull command just recompile the recovery.
Proposal to download the file: could be better to distribute the recovery as zip (like A500_CWM_recovery_vx.x.x.x.x.zip - it's self explantory) with inside the recovery.img file. It's always better to avoid to download native recovery image to avoid partial download or corrupted file.
Thanks.
Click to expand...
Click to collapse
The Skrilax_CZ bootloader is absolutely necessary, because it allows flashing and booting from the secboot. The recovery is too large to fit in the recovery partition. That having been said, I may be able to shrink it to fit, if I could get it to compile and boot.
I've had to do the same thing to the recovery for the HTC ChaCha,
He's not using a straight up CWM repo, he would be using the repos for CM10.2, which automatically compiles CWM along with it(or if you give it the arguments, it can compile just recovery)
The bootloader can only be flashed using nvflash, and for a backup, you'll need an older copy of CWM and flash that via fastboot. I personally recommend the tegraowners recovery(I don't like the tegraowners team, but their recovery really is best out of the older ones) you can find it here
Apparently windows 8 hates my tablet. so I tried it on a windows 7 machine, the result was a working recovery. although oddly, it build 6.0.4.6, not 6.0.5.0. weird. maybe I'll poke at it later and try to update just the cwm repo. whatever the case, this gives me a working setup to try PhilZ Touch Recovery
I believe that the main scope should be to have a recovery that use no more space than the partition size.
It's due to avoid not use unofficial bootloader and to avoid overwiting importan partition like NVRAM (IMEI).
Related
Alright I have a semi-bricked mytouch 4G. (a friend's phone) I followed the gfree guide and did the hboot flash and now I'm in a boot loop. I have the original boot screen loaded and I can get to the recovery menu. S is off so the phone is rooted. How do I get CWM on the phone so I can install a new ROM and kernel so I can unbrick this thing. With my verizon fascinate I have options to go from where I am stuck (Odin and .md5 files). Where do I go from here? Can somone give me a step by step without pointing me to a different forum? I have searched for more than a couple of hours and this is where I have found myself.
Did you go into a bootloop because of the rooting process? What did you do once you rooted the phone? Did you download ROM Manager? Need a lot more info about what was done in order to help you. You can flash cwr through adb, but before we get there I think you should break down exactly what happened post-root.
darinmc said:
Did you go into a bootloop because of the rooting process? What did you do once you rooted the phone? Did you download ROM Manager? Need a lot more info about what was done in order to help you. You can flash cwr through adb, but before we get there I think you should break down exactly what happened post-root.
Click to expand...
Click to collapse
I beleive it was after rooting. I followed the directions for gfree rooting exactly (of at least so I think, however, we can see that is apparently wrong). Rebooted the phone to check that S-off and then was stuck at a boot loop with the my touch 4g boot screen.
fsuagentsmith said:
I beleive it was after rooting. I followed the directions for gfree rooting exactly (of at least so I think, however, we can see that is apparently wrong). Rebooted the phone to check that S-off and then was stuck at a boot loop with the my touch 4g boot screen.
Click to expand...
Click to collapse
Since you have the engineering Hboot. this isn't that big of a problem, but you do need the ADB drivers at the bare minimum... use the blue link in my signature to get those up and running if you don't already.
first things first you need a recovery image.
Download this recovery image Download from here
Once you download it store the image only in the tools folder of your SDK or your c:\adb folder if you used True_blues method
now boot into your Hboot screen and plug the phone into the computer
go to your CMD prompt and type
Code:
fastboot devices
it should show you the serial number of the phone
if it does
then change your drive to the tools folder... basically where ever you store that image....
then type
Code:
fastboot flash recovery recovery.img
it should show you something like
Code:
sending 'recovery' (3426 KB)... OKAY [ 1.172s]
writing 'recovery'... OKAY [ 0.797s]
finished. total time: 1.969s
if it does unplug the phone and use the volume keys to navigate to the reboot recovery option
once you are their you can flash any ROM you want.
Make sure to update the recovery image to 3.0.2.x once you are up and running.
neidlinger said:
Since you have the engineering Hboot. this isn't that big of a problem, but you do need the ADB drivers at the bare minimum... use the blue link in my signature to get those up and running if you don't already.
first things first you need a recovery image.
Download this recovery image Download from here
Once you download it store the image only in the tools folder of your SDK or your c:\adb folder if you used True_blues method
now boot into your Hboot screen and plug the phone into the computer
go to your CMD prompt and type
Code:
fastboot devices
it should show you the serial number of the phone
if it does
then change your drive to the tools folder... basically where ever you store that image....
then type
Code:
fastboot flash recovery recovery.img
it should show you something like
Code:
sending 'recovery' (3426 KB)... OKAY [ 1.172s]
writing 'recovery'... OKAY [ 0.797s]
finished. total time: 1.969s
if it does unplug the phone and use the volume keys to navigate to the reboot recovery option
once you are their you can flash any ROM you want.
Make sure to update the recovery image to 3.0.2.x once you are up and running.
Click to expand...
Click to collapse
I get sending recovery failed... any help from there?
fsuagentsmith said:
I get sending recovery failed... any help from there?
Click to expand...
Click to collapse
on your phone do you where it says "fastboot usb" on the HBoot screen? does that show up?
neidlinger said:
on your phone do you where it says "fastboot usb" on the HBoot screen? does that show up?
Click to expand...
Click to collapse
yes, I see that
fsuagentsmith said:
yes, I see that
Click to expand...
Click to collapse
ok I changed it to that screen on the phone while trying to push the recovery image. It worked!!!
Awesome from here just go to the development section and pick out which ROM you like and use their directions for installing it.
as of currently i am using CM7.0.0 and my wife is using RoyalLiquid. Both are really nice ROMs.
neidlinger said:
if it does unplug the phone and use the volume keys to navigate to the reboot recovery option
once you are their you can flash any ROM you want.
Make sure to update the recovery image to 3.0.2.x once you are up and running.
Click to expand...
Click to collapse
Where is the reboot recovery option? As I said in original post I'm familiar with Samsung Galaxy and CWM not so much this phone.
fsuagentsmith said:
Where is the reboot recovery option?
Click to expand...
Click to collapse
are you in Recovery or in Hboot? what color is the screen? black or white?
neidlinger said:
Awesome from here just go to the development section and pick out which ROM you like and use their directions for installing it.
as of currently i am using CM7.0.0 and my wife is using RoyalLiquid. Both are really nice ROMs.
Click to expand...
Click to collapse
I'm planning on using CM7. what do I select after? just recovery on the HBoot menu?
neidlinger said:
are you in Recovery or in Hboot? what color is the screen? black or white?
Click to expand...
Click to collapse
This is HBoot, Screen is white. My selections are Fastboot, Recovery, Factory Reset, etc. Do I select recovery?
fsuagentsmith said:
This is HBoot, Screen is white. My selections are Fastboot, Recovery, Factory Reset, etc. Do I select recovery?
Click to expand...
Click to collapse
Awesome!!! I see what you told me to do! When I select recovery this is CWM 3! Awesome. I will see where I can go from here. I still may have questions.
fsuagentsmith said:
I'm planning on using CM7. what do I select after? just recovery on the HBoot menu?
Click to expand...
Click to collapse
Select recovery from the HBoot menu. That should reboot the phone into recovery. Once you are their select mount, then USB and store the ROM and the Gapps on the SDcard
Wipe the phone
select flash .zip from SDcard
Select the option for you to pick the .zip
flash the ROM
Flash the Gapps
Fix permission via the advanced menu
reboot the phone.
neidlinger said:
Select recovery from the HBoot menu. That should reboot the phone into recovery. Once you are their select mount, then USB and store the ROM and the Gapps on the SDcard
Wipe the phone
select flash .zip from SDcard
Select the option for you to pick the .zip
flash the ROM
Flash the Gapps
Fix permission via the advanced menu
reboot the phone.
Click to expand...
Click to collapse
Many thanks. I am up and running now on CM7. Looking at kernels to add to the tweak. Thanks again.
fsuagentsmith said:
Many thanks. I am up and running now on CM7. Looking at kernels to add to the tweak. Thanks again.
Click to expand...
Click to collapse
glad to see you got it going.
just make sure to do nandroid backups prior to flashing any new Kernels and make sure they are compatible with AOSP 2.3 ROMs.
neidlinger said:
Since you have the engineering Hboot. this isn't that big of a problem, but you do need the ADB drivers at the bare minimum... use the blue link in my signature to get those up and running if you don't already.
first things first you need a recovery image.
Download this recovery image Download from here
Once you download it store the image only in the tools folder of your SDK or your c:\adb folder if you used True_blues method
now boot into your Hboot screen and plug the phone into the computer
go to your CMD prompt and type
Code:
fastboot devices
it should show you the serial number of the phone
if it does
then change your drive to the tools folder... basically where ever you store that image....
then type
Code:
fastboot flash recovery recovery.img
it should show you something like
Code:
sending 'recovery' (3426 KB)... OKAY [ 1.172s]
writing 'recovery'... OKAY [ 0.797s]
finished. total time: 1.969s
if it does unplug the phone and use the volume keys to navigate to the reboot recovery option
once you are their you can flash any ROM you want.
Make sure to update the recovery image to 3.0.2.x once you are up and running.
Click to expand...
Click to collapse
Heeeeelp??? I'm having the same issue with the boot loop. My phone locked up when tried flashing CM7 and failed to restore my nanbackup. I can't boot to CM recovery anymore and when I tried to run that command, I'm getting "writing recovery.... FAILED <remote: image update error>"
*Note, that link u posted to download the recovery img is down
steb0ne said:
Heeeeelp??? I'm having the same issue with the boot loop. My phone locked up when tried flashing CM7 and failed to restore my nanbackup. I can't boot to CM recovery anymore and when I tried to run that command, I'm getting "writing recovery.... FAILED <remote: image update error>"
*Note, that link u posted to download the recovery img is down
Click to expand...
Click to collapse
Can I get some background info?
Sent from my HTC Glacier using XDA Premium App
Nicgraner said:
Can I get some background info?
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Well, I was rooted and had been running the leaked 2.3 stock rom. Decided I wanted to try CM7...and flashed it and it appeared to flash okay b/c I was able to boot up, but I couldn't get gapps to install, so I ended up trying to restore from my backup, and that failed, and I couldn't get back to CM recovery. So, I'm stuck in a constant boot loop.
So it seems I have messed up my phone decently bad
decided to go back and reload everything from scratch but unfortunately flashed back a CWM version thats 3.0.1 and when I try to flash my old recovery (ICS CM9) it gives me error 7
I am guessing thats because I have to install 5.0 CWM can anyone explain to me how to do this?
Thank you so much all!
Yan
More Info:
Ok so heres the deal.
I was originally running CM9 from Nexus MV ICS rom with a Franco Kernel.
All was well and phone was rock solid for weeks since he released with everything working.
as the update came out I was told I should revert back to 2.3.6 and wait for the OTA update that way I could have the true OEM ICS. It is pretty much 90% of why I originally Rooted and unlocked my phone.
I used this link.
http://forum.xda-developers.com/showthread.php?t=1063664
and downloaded
Android 2.3.6/GRK39F/UCKF1 Radio/KA3 Bootloader
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
That I flashed using CWM
Phone rebooted fine but had no SuperUser file and seemed like it no longer was rooted so though if I go back and re-root it should be fine.
Went to.
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/
and went straight to instruction 5) Open up a command prompt by typing “cmd” under Start->Search Programs and files.
Then type “cd \nexussrootnew” to browse into the directory in Windows. For Linux and Mac, should be similar to “cd /nexussrootnew“.
Then type “fastboot oem unlock“.
Thats when I went back to CWM 3.1.0.1 and tried to install any rom or backup and it just seems to give me Status 7 error.
I hate that I cant figure this out alone but I am a little lost.
Here's a link: http://forum.xda-developers.com/showthread.php?t=1382624
Use the search next time, it took less than 10 seconds for me to find the page.
063_XOBX said:
Here's a link: http://forum.xda-developers.com/showthread.php?t=1382624
Use the search next time, it took less than 10 seconds for me to find the page.
Click to expand...
Click to collapse
Actually I tried this originally
http://forum.xda-developers.com/showthread.php?t=1248760
Still get Status 7!
Sorry I usually search before just forgot to write that in!
Download CWM 5.0.2.0 and rename the .img to recovery.img
(i'll assume you have phone drivers and everything working, and fastboot)
Put the recovery.img into the same directory as your fastboot.exe
Boot into your bootmanager (vol up+power)
Plug phone into PC
Open up CMD prompt and change to the directory where you have fastboot.exe
(cd c:\android\tools) for example
type in:
> fastboot flash recovery recovery.img
reboot to recovery
seriosbrad said:
Download CWM 5.0.2.0 and rename the .img to recovery.img
(i'll assume you have phone drivers and everything working, and fastboot)
Put the recovery.img into the same directory as your fastboot.exe
Boot into your bootmanager (vol up+power)
Plug phone into PC
Open up CMD prompt and change to the directory where you have fastboot.exe
(cd c:\android\tools) for example
type in:
> fastboot flash recovery recovery.img
reboot to recovery
Click to expand...
Click to collapse
I tried that and unfortunately it gives me an error when I try it
says
"Error: cannot load recovery.img"
Used the download from this link!
http://forum.xda-developers.com/showthread.php?t=988686&highlight=recovery
Looks like someone else is having the same issue as me.
http://forum.xda-developers.com/showthread.php?t=996914&page=4
Try to just boot the newer cwm recovery with fastboot
Fastboot boot recovery recovery name.img
albundy2010 said:
Try to just boot the newer cwm recovery with fastboot
Fastboot boot recovery recovery name.img
Click to expand...
Click to collapse
Same error as earlier....
Can Not load
Darn this is frustrating!
sspikey said:
Same error as earlier....
Can Not load
Darn this is frustrating!
Click to expand...
Click to collapse
SWEET just got this phone to boot up again! No network right now for some reason but wifi works!
Here is what I used.
http://forum.xda-developers.com/showthread.php?t=884093
Where should I go from here? Ideas? I am guessing I have to install super user Zip through the current 3.0XX CWM right?
MORE PROGRESS!!!!!
Got CWM 5.0.2.0 loaded on to it by flashing the IMG through CMD
Worked after what I did earlier!
Progressing forward!!!!
Final cherry on top of the cake!!!
works perfectly again accepted my nandroid backup and shes running at 100%
ah feels good!
please help me i am also having the same problem i tried everything nothing seemed to work out and please check my thread ( http://forum.xda-developers.com/showthread.php?t=1533346 ) thnx.
I got an Acer A501 tablet and installed lightspeed 4.8. Everything was working fine but for some reason I decided to update the bootloader to Skrillax_CZ's unlocked bootloader which was recommended. Since updateing the bootloader the tablet randomly reboots itself and shut down. I also can no longer get into recovery mode. I tried using Clockwork mod and also with the volume+- buttons manually but all that happens is it hangs at "booting recovery kernel". Does anyone know how to change the bootloader without entering recovery mode?
guitarguy6 said:
I got an Acer A501 tablet and installed lightspeed 4.8. Everything was working fine but for some reason I decided to update the bootloader to Skrillax_CZ's unlocked bootloader which was recommended. Since updateing the bootloader the tablet randomly reboots itself and shut down. I also can no longer get into recovery mode. I tried using Clockwork mod and also with the volume+- buttons manually but all that happens is it hangs at "booting recovery kernel". Does anyone know how to change the bootloader without entering recovery mode?
Click to expand...
Click to collapse
1. Make sure you have the Android SDK installed to your PC.
2. Boot the tab to fastboot using PWR and Vol+
you should get a menu
Select Fastboot Mode. Should say it at the top center when in fastboot
3. Download your CWM image file and copy it to your C:\Program Files\Android\Android-sdk\platform-tools folder. (might be in Program Files (x86).
in that folder you will see a file called "fastboot.exe"
Wait, plug your tab in.
4. Open a command window in that folder (shift + right mouse click)
in the window, type fastboot flash recovery nameofyourrecover.img (where nameofyourrecovery is what the recovery image file is named.
5. Hit Enter
Should flash your CWM recovery image back. I advise you use the latest CWM recovery. 1.7.2 or 1.7.3 you can get at tegraowners site
MD
If I don't have a recovery image am I SOL? Can I download one from somewhere?
guitarguy6 said:
If I don't have a recovery image am I SOL? Can I download one from somewhere?
Click to expand...
Click to collapse
tegraowners.com is one place.
The other recovery, is PublicRecovery which you can find in the Dev Forum.
Both are good recoveries. Albeit the CWM one is notorious for not revealing source code on his kernels. Non-GPL, which is why he is not allowed to post his kernels or roms at XDA. Might be sending your usernames and login's for all anyone knows,
The CWM "is" GPL compliant. So no needs to worry.
The "search" button, is such an easy thing to use.
MD
Thank you for the help. I found an app in the play store called "Acer Recovery" and used it to flash clockwork recovery. I was able to get into recovery mode after that and install the Tegra Owners ICS rom I wanted to try. I won't forget to do a nandroid backup ever again lol.
guitarguy6 said:
Thank you for the help. I found an app in the play store called "Acer Recovery" and used it to flash clockwork recovery. I was able to get into recovery mode after that and install the Tegra Owners ICS rom I wanted to try. I won't forget to do a nandroid backup ever again lol.
Click to expand...
Click to collapse
Yeah, keep forgetting about that one. But, just make sure the Recovery you installed is a recent one. Not sure how often that app gets updated.
Some of the older versions have issues with ICS sometimes, especially TWRP. So check versions.
MD
****DISCLAIMER****
I am not responsible if you device decides to soft brick/ hardbrick or flys out the window
Recovery Installation Instructions:
1. unlock bootloader. (Hold volume up and power button, using terminal type in 'fastboot oem unlock', follow on screen instructions, (***WARNING THIS WILL WIPE DATA PARTITION***)
2. While in bootloader type 'fastboot flash recovery recovery.img'
3. select boot into recovery!!
Recovery Access:
Access recovery in pc via terminal/cmd
Adb reboot recovery
Or within the device...
Terminal emulator
Su
Reboot recovery
Or download an app from playstore that will do the work and reboot into recovery...
TWRP Version 2.7.1.0 Released:
Fully Working
Current issues list:
0 Issues
How to report an issue:
Message me with the a detailed description of the issue.
Provide a log.
Issues reported without a log will be ignored.
Download Link: http://d-h.st/cqQ
Source: https://github.com/omnirom/android_bootable_recovery
Release Changelog:
V1:
- TWRP booting
- graphics fixed but touchscreen not working
V2:
- Touchscreen fixed
- USB Mounts fixed
- software keys fixed.
V3:
- Improve read and write speeds on both internal and external storage. (TWRP method of calculating backup, MB/s seems inaccurate, jumps around way too much) but backup is very very fast!
- Improve graphical user interface speed, very very smooth!
- When not using TWRP, lp-core (super battery saving core) will be active and used as its suppose to.
- Drastically reduce TWRP loading times.
V4:
- TWRP Updated to latest source, includes better method of calculating backup and restore (now shows files and percentage complete, also supports colour text etc etc)
- Updated recovery kernel so backup and restore shall be faster
- Fixed 180 degree upside down recovery, now shows correctly
- TWRP now supports Nvidia OTA (NOTE: Installing nvidias OTA on a modified system may provide FC, DO NOT INSTALL IF YOU HAVE XPOSED INSTALLED)
CWM has been discontinued as it is not fully functioning while TWRP is and has much more, advanced features.
Unlocking Bootloader & Rooting
the new rom 4.3 should not be difficult... Now that we have recovery...
Unlocking bootloader
1. Unlock the bootloader
Access bootloader by either from poweroff holding volume down and power keys... Or enable USB debugging via pc enter adb shell reboot bootloader
Once at bootloader type in terminal/cmd fastboot oem unlock and follow intructions till the end...
WARNING DEVICE WILL WIPE USERDATA(EVERYTHING)
Device is now unlocked
2. install recovery - steps above
3. Download supersu.zip from chainfires website
Install via recovery... (Android terminal, su, reboot recovery)
Navigate to Supersu.zip via volume up, down keys and powerbutton - http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
Root achieved yay
More indepth tutorial incoming
Shaky156 said:
would really help if everyone could but high level moderators for tegra note device thread
Click to expand...
Click to collapse
Thanks Shaky for the efforts.
I agree with Tegra having its own thread, especially since so many OEM outlets will be selling this tablet and other iterations, like the coming Phone version of the Tegra 114i SoC.
e8hffff said:
Thanks Shaky for the efforts.
I agree with Tegra having its own thread, especially since so many OEM outlets will be selling this tablet and other iterations, like the coming Phone version of the Tegra 114i SoC.
Click to expand...
Click to collapse
Pm'd a high mod, has put the device on internal request list so dudes pls do pm mods and request, if you dont ask you dont get
V2 is compiling right now will test and upload after breakfast inshallah and CWM shall be functioning normal as in Image wont be flipped upside down anymore
Link to OTA 4.3 Tegra Note 4
http://forum.xda-developers.com/showthread.php?p=48866058#post48866058
Dpuble post delete pls
OP Updated with link to v2, although image is flipped so its sitting correctly, the device resolution is somewhat not set correctly so the CWM recovery looks out of shape a little but this doesnt affect the functionality of CWM
Also OP updated with link to OTA in zip file format fully factory... ENjoy
Double post delete pls
Bricked my device so cannot continue any further yet...
do you have the source for your CWM recovery. would love to have it so that development can continue. Thanks
Tomsgt said:
do you have the source for your CWM recovery. would love to have it so that development can continue. Thanks
Click to expand...
Click to collapse
Switching from CWM to TWRP for alot of reasons so will release source for TWRP, CWM source can be found in Cyanogenmod github. Also replied to your PM
http://d-h.st/eU9 TWRP v1 Recovery test
Shaky156 said:
http://d-h.st/eU9 TWRP v1 Recovery test
Click to expand...
Click to collapse
this is still CWM recovery you must have linked the wrong file. LOL
Tomsgt said:
this is still CWM recovery you must have linked the wrong file. LOL
Click to expand...
Click to collapse
That is weird...
fresh compile test here is another TWRP test: http://d-h.st/Y9u
fastboot flash recovery recovery.img
allot it to boot into your Android OS
adb reboot recovery, (TWRP should boot)
Shaky156 said:
That is weird...
fresh compile test here is another TWRP test: http://d-h.st/Y9u
fastboot flash recovery recovery.img
allot it to boot into your Android OS
adb reboot recovery, (TWRP should boot)
Click to expand...
Click to collapse
C:\Development\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot fl
ash recovery TWRP-2-recovery.img
target reported max download size of 641728512 bytes
sending 'recovery' (8384 KB)...
OKAY [ 0.311s]
writing 'recovery'...
FAILED (remote: (InvalidSize))
finished. total time: 0.335s
FAILED (remote: (InvalidSize)) looks like the recovery partition is pretty small. didnt notice it the first time I flashed it. witch is probably why I am still on CWM. Note Stock recovery is 8192KB but this one fails every time.
Tomsgt said:
C:\Development\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot fl
ash recovery TWRP-2-recovery.img
target reported max download size of 641728512 bytes
sending 'recovery' (8384 KB)...
OKAY [ 0.311s]
writing 'recovery'...
FAILED (remote: (InvalidSize))
finished. total time: 0.335s
FAILED (remote: (InvalidSize)) looks like the recovery partition is pretty small. didnt notice it the first time I flashed it. witch is probably why I am still on CWM. Note Stock recovery is 8192KB but this one fails every time.
Click to expand...
Click to collapse
I knew something wasnt right on your end since i did compile TWRP and was 100% sure I did. Will upload something soon
Shaky156 said:
I knew something wasnt right on your end since i did compile TWRP and was 100% sure I did. Will upload something soon
Click to expand...
Click to collapse
Yeah ut took me a couple tries to finally notice that LOL
Tomsgt said:
Yeah ut took me a couple tries to finally notice that LOL
Click to expand...
Click to collapse
Something isnt right, I need more than 1 tester to test TWRP on their device as it could be a user error,
Shaky156 said:
Something isnt right, I need more than 1 tester to test TWRP on their device as it could be a user error,
Click to expand...
Click to collapse
Guess i can be your second tester. Ill try this when i get home today. My bootloader is already unlocked and im rooted.
Edit: I dont even have CWM loaded so this will be fresh attempt strait to TWRP
BKO Overdrive said:
Guess i can be your second tester. Ill try this when i get home today. My bootloader is already unlocked and im rooted.
Edit: I dont even have CWM loaded so this will be fresh attempt strait to TWRP
Click to expand...
Click to collapse
Dont attempt yet... wait for another release of TWRP
Hello,
I'm pretty new to rooting Sony devices and I can't seem to install custom roms on my Xperia Z2 using fastboot. My bootloader is unlocked (i've checked several times), USB debugging is checked and it believe my drivers are properly installed (fastboot devices cmd recognizes my device) but when i try to run "fastboot flash zip rom.zip" i get this annoying FAILED (remote: Command not allowed) message. I've looked through several threads but I can find any solution that applies to my case.
Any ideas would be welcome.
Thanks
I called Sony. Their official story is they do not support unlocking their own phones.
I asked her why, she said we just dont support unlocking the bootloader on some phones.
Im going to go break this phone and never recommend or buy sony products ever again
What exactly are you trying to flash?
Fastboot doesn't flash .zip files (I think). Whatever you are trying to flash must be extracted from the .zip file, then flashed via fastboot.
If you are trying to flash a custom kernel, you must have the boot.img file extracted from the .zip file in the same folder as the adb_fastboot folder, then hold in Shift then right-click and select, 'Open command window here' then type in cmd, 'fastboot flash boot boot.img'.
Once it says, 'Waiting for device', hold in the volume-up button on the phone and insert the USB cable into the phone.
Hope this helps.
I'm trying to flash android lollipop. I've tried extracting the boot.img flash it and then try to boot on recovery. A few times nothing happened and I couldn't force restore even using adb. Other times I just got stuck on the splash screen or in a loop reboot.
From what I've found online you can flash with flashboot using "flashboot flash zip Rom.zip" it starts transferring the room but it immediately does to the failed remote command not allowed error.
Sent from my D6503 using XDA Free mobile app
Where did you find that this command works for Xperia devices? I don't say that it can't work, but I see it for the first time (reading XDA for several years). All ROMs which I flashed were via flashtool or recovery, never through fastboot.
The best solution is to follow installation instruction of the given ROM.
RoamenCota
As far as I know most brands don't really support development but have you tried this the Sony Boot loader unlocking website?
_mysiak_
As for the cmd I found it online but I think it was an HTC forum. I guess it might not work in Xperia devices. I'm able to flash with flashtool but so far I've only managed to brick the phone.
Sent from my D6503 using XDA Free mobile app
Which ROM exactly are you trying to flash and what steps have you done?
_mysiak_ said:
Which ROM exactly are you trying to flash and what steps have you done?
Click to expand...
Click to collapse
I've tried flashing the [ROM][WIP]AOSP 5.0 Beta v2.0 from krabappel and the [ROM][SIRIUS][LP][5.0.1][SM-4.9] CyanogenMod 12 Unofficial [NIGHTLY BUILDS] from infected_ (sorry i'm not allowed to post links). As for the first one the process seems a bit more complex since there is a v2 plus an OTA to install. I've tried the second one first with flashboot but it didn't really work. With flash tool i've ended up bricking the phone.
CM is usually flashed via recovery (CWM, TWRP,..) - download ZIP, put it on SD card, boot into recovery, flash from there, reboot. Flashtool or fastboot should not be required. I would advise you to continue in ROM specific topics about any special installation steps/instructions.
_mysiak_ said:
CM is usually flashed via recovery (CWM, TWRP,..) - download ZIP, put it on SD card, boot into recovery, flash from there, reboot. Flashtool or fastboot should not be required. I would advise you to continue in ROM specific topics about any special installation steps/instructions.
Click to expand...
Click to collapse
For some reason that rom isn't able to be installed in TWRP recover. There's some install error may due to the fact that's a beta and not completely stable. If it doesn't work i'll just wait for a more stable version.
Just curious, even if it's a zip file, if I extract the complete package to the fastboot/adb folder and run "fastboot flash boot boot.img" there's no reason not to work right?
amrcardoso said:
For some reason that rom isn't able to be installed in TWRP recover. There's some install error may due to the fact that's a beta and not completely stable. If it doesn't work i'll just wait for a more stable version.
Just curious, even if it's a zip file, if I extract the complete package to the fastboot/adb folder and run "fastboot flash boot boot.img" there's no reason not to work right?
Click to expand...
Click to collapse
I don't think that it's worth the effort to flash those ROMs, unless you are really curious. Otherwise you should stick to verified and fully working ROMs.
It depends what you expect from that command. It will work, but it'll flash only kernel. System and other partitions remain untouched. Most probably you'll get bootloop with such combination.
_mysiak_ said:
I don't think that it's worth the effort to flash those ROMs, unless you are really curious. Otherwise you should stick to verified and fully working ROMs.
It depends what you expect from that command. It will work, but it'll flash only kernel. System and other partitions remain untouched. Most probably you'll get bootloop with such combination.
Click to expand...
Click to collapse
I'll probably stick with the zip flashing via recovery. But what step am I missing to flash a rom thorugh fastboot?
That most probably it's not possible to flash ROM via fastboot on Xperia devices. You have to use flashtool for FTF files and recovery for custom ROMs. Fastboot is used to flash kernel only.
_mysiak_ said:
That most probably it's not possible to flash ROM via fastboot on Xperia devices. You have to use flashtool for FTF files and recovery for custom ROMs. Fastboot is used to flash kernel only.
Click to expand...
Click to collapse
I have been able to flash the stock FTF but never a ROM using flashtool. Maybe that's why.
Thanks