Related
Hello All!
So my gt540 has already been rooted and fastboot works. I have been running a 2.2 rom flashed through fastboot for a few months now, but I would like to get clockwork recovery working now for the added features of flashing zips and restoring and whatnot.
I have has a lot of trouble finding clear directions on how and what to do to get clockwork recovery on this device. Like I said, I already have root and fastboot is working as well. Can anyone please provide me with instructions on what I need to do from this point?
I have looked at this thread already, http://forum.xda-developers.com/showthread.php?t=817903, but I am still unsure of what exactly I am to do. Also, the mirrors are broken on this page.
Thank you for your help!
download the app root toolbox from the market
and then download a recovery .img and go to advance
flash recovery, find the file and press on it.
wait until finish and then all done!
Or here are better instructions!!
http://forum.xda-developers.com/showpost.php?p=16783348&postcount=1
Installing recovery:
You have multiple choices to choose from.
ClockworkMod Recovery 2.5.1.8 (Recommended)
ClockworkMod Recovery 4.x (Recommended but you may run into incompatible .zip files, download the recovery_clockwork_x.x.x.x_swift.zip file)
Amon RA 2.2.1 (Recommended)
Amon RA 1.7.0.1 (Not recommended due to incompatibility with zip files and recovery backups. Also .zips must be signed)
Download the recovery image of your choice (I strongly recommend Clockwork 2.5.1.8)
Next put your phone in Fastboot mode by rebooting then holding Camera+Power, make sure USB Cable is plugged in. Also let Windows search Windows Update for drivers.
Download fastboot.exe from here: http://adf.ly/2M8Hi and extract it to the desktop. Also put the recovery image you downloaded onto the desktop too.
Be sure to have your fastboot drivers installed, if you use Vista/Windows 7 then the driver should be auto-downloaded from Windows Update, if you use XP or the drivers won't install from Windows Update, then look at this.
Open a command prompt and type the following:
Code:
cd Desktop
fastboot devices (if you see ? fastboot then your device is recognized)
fastboot flash recovery name_of_recovery.img
fastboot reboot
When fastboot says rebooting, hold down HOME and wait. You should see clockwork pop up. Recovery is now on your phone. You can delete the fastboot, kdz and recovery file from your pc because we won't be needing them again. Unless you need to use fastboot.exe again, but just download the fastboot.zip again if you need it) The other files, we don't need.
(NOTE: If your phone reboots with no boot logos (LG logo and animation), or when you flash recovery and it doesn't come up, follow the steps found here. Thanks to fishears for the post!)
Now, installing custom ROMs. Pick any ROM you'd like from the ROM Development section, if you can, get the recovery version, it is much easier to install. Determine if it is a recovery backup, or update.zip
Recovery backups usually contain some .img files and a nandroid.md5 file. The folder containing these files will need to go in the sdcard\clockworkmod\backup folder. Flash them by going to Backup/Restore>Restore>Then pick the backup folder.
Recovery update.zips contain three (or four) files/folders:
boot.img (file)
install-busybox.sh (file, only appears in SOME ROMs)
system (folder)
META-INF (folder)
DO NOT EXTRACT THESE, just put the .zip file on your sdcard, then go into recovery and go to install .zip from sdcard>choose .zip>pick the .zip you downloaded. (NOTE FOR SWIFTDROID: You MUST put the update-cm-xxxxx.zip file found in the SwiftDroid_x.x.x.x_Recovery.zip on your sdcard for it to install!!!)
THANKS TO EFFORTLESS FOR INSTRUCTIONS!!
Thank you thank you very much sir!
kweng_ca said:
Thank you thank you very much sir!
Click to expand...
Click to collapse
Ur welcome!
Just thank me!
Sent from my GT540
After getting my GS3/i9300 I realized that I didn't have a Windows computer anymore to root it. So I was stuck finding an alternative to Odin. I had trouble finding one aggregated source of Mac info that was relatively recent (last post I see is from Feb 2012) and all in one place.
I'm on MacOS X 10.7.5 (Lion) which isn't the most current version. I'm also a noob so maybe I got lucky as I've seen many comments within the various threads where my steps didn't work for other people.
When you download Chainfire's Auto-Root zip file, you'll need to do things a bit differently than with Odin. After unzipping, you'll need to untar the .tar file as well. You'll want the recovery.img and cache.img files in a folder on your PC. You'll need to know the path to that directory.
Instead of using the Heimdall GUI (which I found confusing), I ended up finding Chainfire's comments about using the Linux/Terminal commands in one of his old posts. He said it was "hearsay" but I can confirm that it worked on my GS3. Credit goes to jzuijlek for posting it (his post).
You'll want to install Heimdall from here
Currently they're saying to install version 1.3.1 instead of 1.3.2.
After Heimdall installs, I suggest rebooting your Mac.
Now to the good stuff...
Boot your phone into download mode:
1) Unplug your phone from the computer.
2) Turn your phone off
3) Hold both the volume down + home button. Then press and hold power until download mode comes up. Then press the volume up key to continue.
3) Plug in your phone
4) Open up Terminal and then cd to your recovery/cache.img files directory
5) Then type in this command:
sudo heimdall flash --recovery recovery.img --cache cache.img
If all goes well then you'll see stuff being installed and your phone will reboot and you'll be DONE!
However, if you're like me, you got an error. The response from Heimdall said, "Claiming interface failed". It turns out that there may be conflicts with Kies kexts if you have it installed. If you don't have it installed and you're seeing this error, I'm not sure if I can help. I suggest uninstalling Kies as you won't need it after you root. I searched Google with my error and finally found this gem from March 2012!
http://blog.scott.wallace.sh/2012/03/getting-heimdall-to-work-on-your-mac.html
As such, if you've installed Kies on your Mac and you're having this error, I suggest using the following commands. It seems some kernel extensions that Kies installs conflict with Heimdall.
sudo kextunload -b com.devguru.driver.SamsungComposite
sudo kextunload -b com.devguru.driver.SamsungACMData
sudo kextunload -b com.devguru.driver.SamsungACMControl
After this, I tried to flash again and it worked like a charm!
Now you're rooted.
However, Chainfire doesn't support CWM in his CF-Autoroot anymore so you'll need to get CWM or some other recovery image (Philz, TWRP, etc.). You can search these forums but these links should be mostly correct
CWM (find the Samsung Galaxy S3 i9300 in the list: http://www.clockworkmod.com/rommanager
Philz (built on CWM): http://forum.xda-developers.com/showthread.php?t=2002953
TWRP: http://forum.xda-developers.com/showthread.php?t=1943592
You'll flash the same way as above with just the .img file
Boot into download mode using sequence above.
(Example with CWM)
Open up Terminal and cd to the directory with your .img file.
Then type:
sudo heimdall flash --recovery recovery-clockwork-6.0.2.7-i9300.img
For reference...to boot into recovery:
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
I hope this helps! Let me know if you think I got anything wrong!
Is this still theway to root on mac?
I have s3 uk 3 network. 4.1.2 xxella.
I blieve my phone was open to sds attack before the xxella update. can i keep this recovery?
I would strongly advise against using Heimdall. Nothing against the authors, but I tried it and would recommend avoiding it. Simpler approach is to setup Windows (In my case Windows 7) in a VM environment (I bought VMware Fusion) and just use the normal Odin. You'll get far more support from people here, and less headaches.
While i agree that Odin is easier and gives you more help from the community, i used Heimdall anyway due to not having any wish at installing windows on my mac.
This method does work (as of may 2013), however:
-Uncheck the "reboot after flashing" option in Heimdall. When Heimdall has done its job, manually boot into recovery. This way your custom recovery wont be overwritten by stock recovery.
Happy flashing!
Nvflash-ICS Restore!
This guide will not provide information to install Nvflash-ICS as that is covered well elsewhere.
Once you have read the information on that page click Guide.
All necessary partitions are backed up with Nvflash and you can restore only the ones necessary to recover your unit.
The second method to restore has been removed until further study can be done!
If your problem can't corrected using this information and normal use of recovery, adb, and fastboot go to this post to access the IRC channel for all Asus transformers using nvflash.
I have finished installing Nvflash but where are my files?
/sdcard/AndroidRoot/ - this is your internal sdcard
Click to expand...
Click to collapse
What files should I have?
blob.bin
blob.txt – the extension on this file varies
bootloader.ebt
create.bct
recovery.bct
bricksafe.img
factory-config.img
unlock-token.img
Click to expand...
Click to collapse
Nvflash recovery and going back to ICS for a fresh start.
Use blobunpack to unpack a stock ICS blob. The blob is found by unzipping the stock ICS firmware twice.
You can find the ICS firmware at this link (9.4.3.30) (post #3).
[INDEX][18 April 2013]TF300T & TG-INDEX of Roms/Dev Guides/Kernels/Recoveries/etc.
Please give philos64 a thanks while there, without him you would have a very hard time finding these downloads if at all.
these files have to be in the folder with Nvflash
wheelie -r --blob blob.bin -created with Nvflash install
nvflash --resume --download 4 blob.EBT -created with blobunpack
nvflash --resume --download 10 blob.APP – created with blobunpack
nvflash --resume --download 6 blob.LNX – created with blobunpack
nvflash --resume --download 5 recovery.img-ICS twrp recovery image name
nvflash --resume --go
then press volume down to enter twrp, flash root, flash rom or whatever you wish
Click to expand...
Click to collapse
If your problem can't corrected using this information and normal use of recovery, adb, and fastboot go to this post to access the IRC channel for all Asus transformers using nvflash.
What is blobunpack?
Here are some links to download and explain use.
https://github.com/AndroidRoot/BlobTools
windows compiled blobtools - http://forum.xda-developers.com/showpost.php?p=21620550&postcount=24
see post #7 for info - http://forum.xda-developers.com/show....php?t=1068548
There were no dates for the following information.
The current AndroidRoot.mobi bootloader versions are
Transformer Prime: 9.4.2.28r01
Transformer TF300: 9.4.3.30r01
Transformer TF700:9.4.5.30r01
ChangeLog:-
Patch: Enable ‘fastboot boot’ command (removes ‘fastboot continue’, use ‘fastboot reboot’ instead).
Patch: Force unlocked state (protect your unlock status no matter what happens to your token).
Patch: Remove blob requirement from ‘fastboot flash’ (Flash the raw images (example: ICS_recovery.img) and not blob files).
Click to expand...
Click to collapse
When failing to get into APX mode you can try the following suggestions.
Special thanks to wha2do and daws for their input!
Also wha2do has posted a guide to enter APX that provides detail not found here! Please see his guide and give proper thanks if you find it helpful!
http://forum.xda-developers.com/show...3#post36159253
1.To enter APX mode you either have to boot, choose reboot (if available) and hold volume up pressed until it reboots and then the screen should remain black. Or if that doesn't work, completely shutdown your tablet and wait a second or two and then hold volume up pressed while pressing power on and keep it pressed until screen is blank.
or
2.fastboot -i 0x0B05 reboot (hold volume up)
or
3. adb reboot (hold volume up)
or
4. with unit powered on hold volume up and press reset with paperclip - (don't press hard)
reset is located about 25mm or 1in below the sdcard
or
5. su
reboot -hold volume up.
This is done using a terminal; Android terminal is free from the play store. You must be rooted for this to work.
or
6. Another way:- Provided by daws
Power off the tablet and don't touch the power button again.
Connect USB cable to tablet but not to PC yet.
Press volume up and then connect USB cable to PC.
Wait a few seconds before releasing volume up button.You should now be in APX mode.
Thanks for the help daws.
or
Only if there is no other resort!
7. remove cover from unit, disconnect battery, press and hold volume up, reconnect battery!
Click to expand...
Click to collapse
Good Luck!
Click to expand...
Click to collapse
Due to my dock smoking my motherboard I have purchased a new motherboard and luckily it came as 4.0.3 ICS.
I now have installed and use Nvflash on my tablet.
In case anyone is interested this is the unit I purchased.
The box shows - Manufacturer's Reconditioned Parts - 90 Day Limited Warranty.
Usefull guide
Good work and helpfull guide for xda members :good:
Nice stuff
philos64 said:
Good work and helpfull guide for xda members :good:
Nice stuff
Click to expand...
Click to collapse
Thank you for your kind words.
can I use these file
blob.bin
blob.txt – the extension on this file varies
bootloader.ebt
create.bct
recovery.bct
bricksafe.img
factory-config.img
unlock-token.img
from other tf300t to unbrick my tf300T bricked ver 4.1.2.?.
chanhny said:
can I use these file
blob.bin
blob.txt – the extension on this file varies
bootloader.ebt
create.bct
recovery.bct
bricksafe.img
factory-config.img
unlock-token.img
from other tf300t to unbrick my tf300T bricked ver 4.1.2.?.
Click to expand...
Click to collapse
No.
The files contain device-specific keys and cannot be used for other devices.
See the original thread for details:
[DEV][TOOL][BRICKPROOF]TF300 NVFlash release!
There's something I've not been quite clear about with NVFlash.
So I do my backup and keep my files.
Afterwards I upgrade to Jelly Bean (because I need the JB bootloader for ROM's right?), put TWRP recovery on, and flash a new ROM that uses the bootloader version I have.
So now I have the JB bootloader, can I still enter APX mode and do a restore, or do I have to remain on ICS bootloader to do a restore?
Is NVFlash truly unbrickable? A glance at this forum shows loads of bricks, would this have sorted their problem if they backed-up first?
Thanks!
tobdaryl said:
This guide will not provide information to install Nvflash as that is covered well elsewhere.
Once you have read the information on that page click Guide.
All necessary partitions are backed up with Nvflash and you can restore only the ones necessary to recover your unit.
I have finished installing Nvflash but where are my files?
What files should I have?
Nvflash recovery and going back to ICS for a fresh start.
What is blobunpack?
Caution
Caution
There were no dates for the following information.
When failing to get into APX mode you can try the following suggestions.
Caution
Full brick recovery
Caution
Good Luck!
Click to expand...
Click to collapse
I played around with your instructions today. Ran into 2 snags:
1. Using blob UI, I typed "u" for unpack, then "blob." It returned with "cannot open 'b'";
2. Typed blobunpack.exe blob. Gave me all the files as shown in attached thumb, except LNX. Where did I go wrong?
graphdarnell said:
I played around with your instructions today. Ran into 2 snags:
1. Using blob UI, I typed "u" for unpack, then "blob." It returned with "cannot open 'b'";
2. Typed blobunpack.exe blob. Gave me all the files as shown in attached thumb, except LNX. Where did I go wrong?
Click to expand...
Click to collapse
I'm having problems with the UI myself. It worked properly when posted. We probably have had an update that broke the UI. I'll remove the link. The tools are easy to use without the UI.
You don't have an LNX extension but you do have boot.img which is the same partition. Did you possibly rename the file and forget? Packing and repacking are still working properly for me including LNX.
I also updated the download link. The link now shown is for the version that can sign when blobpacking.
tobdaryl said:
I'm having problems with the UI myself. It worked properly when posted. We probably have had an update that broke the UI. I'll remove the link. The tools are easy to use without the UI.
You don't have an LNX extension but you do have boot.img which is the same partition. Did you possibly rename the file and forget? Packing and repacking are still working properly for me including LNX.
I also updated the download link. The link now shown is for the version that can sign when blobpacking.
Click to expand...
Click to collapse
Not really. I didn't touch it. I'll do it again today to see. Thanks for the reply.
No recovery
Hello Everybody,
I followed the instructions to restore my device however when my tf300t reboots I can't get the device into recovery mode. It will start up into android or if I hold the volume down during restart it says "platform pre os boot configuration cold booting linux". I download a ICS twrp img recovery file from here for the tf300t. "http://techerrata.com/browse/twrp2/tf300t"
My only options at this point are to enter APX mode or boot into android.
If somebody could help me install a recovery so I can use custom roms I would appreciate it!!!!!
Thanks,
Mike
waynestatemac said:
Hello Everybody,
I followed the instructions to restore my device however when my tf300t reboots I can't get the device into recovery mode. It will start up into android or if I hold the volume down during restart it says "platform pre os boot configuration cold booting linux". I download a ICS twrp img recovery file from here for the tf300t. "http://techerrata.com/browse/twrp2/tf300t"
My only options at this point are to enter APX mode or boot into android.
If somebody could help me install a recovery so I can use custom roms I would appreciate it!!!!!
Thanks,
Mike
Click to expand...
Click to collapse
Use nvflash again to flash only twrp.
or
Other options
fastboot -i 0x0B05 flash recovery twrp.blob
fastboot -i 0x0B05 reboot
or if rooted
adb shell
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 Then reboot to complete installation.
adb reboot
I use 2.5.0.0 twrp as I have problems with 2.6.0.0.
tobdaryl said:
Use nvflash again to flash only twrp.
or
Other options
fastboot -i 0x0B05 flash recovery twrp.blob
fastboot -i 0x0B05 reboot
or if rooted
adb shell
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 Then reboot to complete installation.
adb reboot
I use 2.5.0.0 twrp as I have problems with 2.6.0.0.
Click to expand...
Click to collapse
Thanks tobdary for replying back. I tried other versions of the recovery but none seem to work. I can't do that fastboot method because I dont get the fastboot option when the I hold the volume down and power like I did when the tablet was bone stock. I can't get su access on the tablet because its not rooted anymore once I reinstalled the nvflash rom so I cant try and flash recovery that way either. I'm really stuck and not sure why this isn't working!
Thanks,
Mike
waynestatemac said:
Thanks tobdary for replying back. I tried other versions of the recovery but none seem to work. I can't do that fastboot method because I dont get the fastboot option when the I hold the volume down and power like I did when the tablet was bone stock. I can't get su access on the tablet because its not rooted anymore once I reinstalled the nvflash rom so I cant try and flash recovery that way either. I'm really stuck and not sure why this isn't working!
Thanks,
Mike
Click to expand...
Click to collapse
I'm not sure either.
Try flashing stock recovery and recheck your bootloader menu for fastboot.
tobdaryl said:
I'm not sure either.
Try flashing stock recovery and recheck your bootloader menu for fastboot.
Click to expand...
Click to collapse
Do you know where I can find the stock recovery? Is it something ziped in the original rom file?
I was able to root the tablet using a program that that uses a exploit while android is running. I then could adb through su access and flash different twrp recovery blob files to the tablet. Though the tablet rebooted and showed a blue line with recovery being installed when I restarted I have no options to load recovery, fastboot, or linux. I'm thinking the bootloader is corrupt. I own a tf201 and might have accidentally used one of the hairybean 2.3 (4.2) bootloader updates for that device on this one. Is there a way to get my bootloader back to the original and maybe that will fix it?
Thanks,
Mike
waynestatemac said:
Do you know where I can find the stock recovery? Is it something ziped in the original rom file?
I was able to root the tablet using a program that that uses a exploit while android is running. I then could adb through su access and flash different twrp recovery blob files to the tablet. Though the tablet rebooted and showed a blue line with recovery being installed when I restarted I have no options to load recovery, fastboot, or linux. I'm thinking the bootloader is corrupt. I own a tf201 and might have accidentally used one of the hairybean 2.3 (4.2) bootloader updates for that device on this one. Is there a way to get my bootloader back to the original and maybe that will fix it?
Thanks,
Mike
Click to expand...
Click to collapse
The first thing you flash in this guide is the bootloader. nvflash --resume --download 4 blob.EBT
With nvflash you can flash only what is needed for your situation. If you feel the problem is the bootloader you can flash just that and try again.
What you describe sounds like stock recovery is still working on your tablet. If flashing the bootloader does not help I would use stock 9.4.3.30, unzip once and place the remaining zip on your internal sdcard. You may get an update notification. Accept it and let your tablet do the work. If you don't get the notification reboot your tablet and you should see it then. Doing this will write stock bootloader, recovery, etc.
Stock recovery is the blob.SOS when you blobunpack. Just use the stock 9.4.3.30 blob and use the resulting SOS (recovery.img).
TF300T Bricked accessible using APX Mode.
Hello @tobdaryl
I have read your thread fully, but my case differs a little bit and need your advice:
I have unlocked ASUS TF300T.
I cant access FastBoot or ADB.
I can access the APX mode.
The ASUS shows only the ASUS logo when powered on.
I don't have BackUp of anything.
I have flashed everything from my ASUS, even the recovery. (I was novice):angel:
Any suggestions or advices please?
What should i do and from where shall i get the needed files, etc...
Thank you in advance.
Nader H.AL-Dirany
NaderALDirany said:
Hello @tobdaryl
I have read your thread fully, but my case differs a little bit and need your advice:
I have unlocked ASUS TF300T.
I cant access FastBoot or ADB.
I can access the APX mode.
The ASUS shows only the ASUS logo when powered on.
I don't have BackUp of anything.
I have flashed everything from my ASUS, even the recovery. (I was novice):angel:
Any suggestions or advices please?
What should i do and from where shall i get the needed files, etc...
Thank you in advance.
Nader H.AL-Dirany
Click to expand...
Click to collapse
I have read your previous posts in addition to this one.
There are four vehicles to restore your tablet. (some things can be done within android but you have no access)
1. recovery - stock or twrp
2. fastboot
3. adb
4. nvflash
I notice you also posted in my guide for accessing adb, fastboot, and apx. You were unable to access fastboot, adb, or recovery with those methods.
I don't know of any way to recover through apx without nvflash previously installed and you have no access to the other three methods.
Needs Stickied ... thanks man you helped save my butt :good:
Trigger911 said:
Needs Stickied ... thanks man you helped save my butt :good:
Click to expand...
Click to collapse
Thanks! *I'm glad you found the info useful.
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).
My OS is Linux Mint 17. I'm running 4.4.2 NAE and haven't found not one tutorial explaining how to Root, Flash Custom Recovery and ROMS with this particular software number. I installed Samsung drivers and installed with Wine but get and error when device connected sometimes:
"Unable to mount Samsung Android"
"Unable to open MTP device '[usb:001,008]'"
Even though I get the error message my device's files are accessible from my Linux based pc. Please tell me I can Root my device and how
My device specs are:
Phone: Samsung Galaxy S4 SPH-L720
Android version: 4.4.2
Software number: L720VPUFNAE
Kernel version: 3.4.0-481102
Baseband version: L720VPUFNAE
Build number: KOT49H.L720VPUFNAE
TowelRoot app with Sprint code " 1337 0 1 7380 4 0 " worked for me my first attempt at root. Thanks Mr. W0lf and anyone else involved. Video tutorial link below:
http://youtu.be/ZGwMs8JPBhE
I still would like to see tutorials on how to Root, Flash Recovery and Roms for Linux Mint users
Sent from my SPH-L720 using XDA Developers App
Josey Wales said:
My OS is Linux Mint 17. I'm running 4.4.2 NAE and haven't found not one tutorial explaining how to Root, Flash Custom Recovery and ROMS with this particular software number. I installed Samsung drivers and installed with Wine but get and error when device connected sometimes:
"Unable to mount Samsung Android"
"Unable to open MTP device '[usb:001,008]'"
Even though I get the error message my device's files are accessible from my Linux based pc. Please tell me I can Root my device and how
My device specs are:
Phone: Samsung Galaxy S4 SPH-L720
Android version: 4.4.2
Software number: L720VPUFNAE
Kernel version: 3.4.0-481102
Baseband version: L720VPUFNAE
Build number: KOT49H.L720VPUFNAE
Click to expand...
Click to collapse
You don't use wine or samsumg drivers when rooting from linux. Install heimdall and flash using the heimdall command line.
untar the odin package, then flash the extracted image files separately with heimdall
heimdall on linux is all I use for flashing odin packages. Note The partition names are case sensitive, and differ between phones, but this example is for gs4.
mv odinpack.tar.md5 odinpack.tar
tar -xvf odinpack.tar
extracting blah blah blah...
boot.img
recovery.img
system.img.ext4
...
eg. > heimdall flash --RECOVERY recovery.img --BOOT boot.img --SYSTEM system.img.ext4 ...etc.
here's the gs4 partition names and typical gs4 image file names for heimdall command reference:
heimdall flash --APNHLOS NON-HLOS.bin
heimdall flash --ABOOT aboot.mbn
heimdall flash --BOOT boot.img
heimdall flash --HIDDEN hidden.img.ext4
heimdall flash --MDM modem.bin
heimdall flash --RECOVERY recovery.img
heimdall flash --RPM rpm.mbn
heimdall flash --SBL2 sbl2.mbn
heimdall flash --SBL3 sbl3.mbn
heimdall flash --SYSTEM system.img.ext4
heimdall flash --TZ tz.mbn
heimdall flash --CACHE cache.img.ext4
I use fedora, which uses yum for installation:
> sudo yum install heimdall
I think mint uses synaptic, which I'm not familiar with, so you're on your own there. You could go crazy and use synaptic to install yum, then use the above yum command. Probably a bit much.
Thanks for your input. I read through the Hemidall topic posted here but I guess I didn't read enough. I'm kind of new to Linux, still learning my way around performing commands from terminal. I'll go ahead and uninstall Samsung drivers from my home pc when I get in later and give Hemidall a shot
Sent from my SPH-L720 using XDA Developers App
Yes it was a bit much lol I did however manage to install Heimdall using the tutorial from the Cyanogen wiki:
http://wiki.cyanogenmod.org/w/Install_and_compile_Heimdall#Installing_prerequisites
Now where do I get the .tar files and a step-by-step install/flash recovery tutorial without getting the KNOX bootloader. My device has Root
Sorry but I'm just trying to be cautious and through
Josey Wales said:
Yes it was a bit much lol I did however manage to install Heimdall using the tutorial from the Cyanogen wiki:
http://wiki.cyanogenmod.org/w/Install_and_compile_Heimdall#Installing_prerequisites
Now where do I get the .tar files and a step-by-step install/flash recovery tutorial without getting the KNOX bootloader. My device has Root
Sorry but I'm just trying to be cautious and through
Click to expand...
Click to collapse
You should find the tar files inside the odin rom zip files
If you're trying to be cautious, you might want to test out the heimdall functionality first by flashing say, just the cache only from one of the stock roms. If it fails halfway through, it's no biggie. Just clear cache until you get it working. Use the above flash command that contains the --CACHE partition as a reference. Just be careful not to flash boot.bin from NAE or you're done. The procedure is the same as using odin, except you unzip and untar the rom manually with linux, and flash the untar'd images with the heimdall command as above.
r0ckstar said:
You might want to test out the heimdall functionality first.
Click to expand...
Click to collapse
Only if I'm able to flash a Recovery. I tried flashing Philz Recovery and CWM but failed. I followed the CyanogenMod tutorial posted here:
http://wiki.cyanogenmod.org/w/Install_CM_for_jfltespr#Installing_a_custom_recovery_on_Galaxy_S4_.28Sprint.29
several times but kept getting this error heimdall flash --recovery recovery.img --no-reboot
ERROR: Failed to open file "recovery.img"
after typing "heimdall flash --RECOVERY recovery.img --no-reboot" in terminal. I extracted both recovery folders to my Desktop even changing folder names from:
recovery to RECOVERY
philz_touch_6.15.4-jfltespr to PHILZ or philz
Heimdall is install and working correctly v1.4.1. Heimdall-frontend is installed as will. I don't need frontend to flash a Recovery. I don't know what else to do here
Josey Wales said:
Only if I'm able to flash a Recovery. I tried flashing Philz Recovery and CWM but failed. I followed the CyanogenMod tutorial posted here:
http://wiki.cyanogenmod.org/w/Install_CM_for_jfltespr#Installing_a_custom_recovery_on_Galaxy_S4_.28Sprint.29
several times but kept getting this error heimdall flash --recovery recovery.img --no-reboot
ERROR: Failed to open file "recovery.img"
after typing "heimdall flash --RECOVERY recovery.img --no-reboot" in terminal. I extracted both recovery folders to my Desktop even changing folder names from:
recovery to RECOVERY
philz_touch_6.15.4-jfltespr to PHILZ or philz
Heimdall is install and working correctly v1.4.1. Heimdall-frontend is installed as will. I don't need frontend to flash a Recovery. I don't know what else to do here
Click to expand...
Click to collapse
You still have to go into the folders to access the files. you flash the files, not the folders. cd into the philz directory, look for the recovery.img or whatever name it is there, then from that directory: heimdall flash --RECOVERY <case sensitive name that's in there>, hopefully recovery.img as to be unambiguous. If you're flashing from the correct directory, you should see the file when you do ls -la command. Otherwise, you would have to add the path to the file name when flashing from a different location. You're almost there.
I tried flashing Philz Recovery in Heimdall a few times and got this error:
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
ERROR: Protocol initialisation failed!
Releasing device interface...
Re-attaching kernel driver...
Click to expand...
Click to collapse
I tried different USB cables and the one included with my device
Josey Wales said:
I tried flashing Philz Recovery in Heimdall a few times and got this error:
I tried different USB cables and the one included with my device
Click to expand...
Click to collapse
There may be some issue with your linux permissions. Try running the command as root, also the phone has to be in download mode when you run the command. And... make sure the usb port is at least a usb2.0, and not an external hub.
r0ckstar said:
There may be some issue with your linux permissions. Try running the command as root, also the phone has to be in download mode when you run the command. And... make sure the usb port is at least a usb2.0, and not an external hub.
Click to expand...
Click to collapse
Issue with permissions? I used "sudo" command, file path is a directory, all 6 onboard usb2.0 ports are functional. I don't know what else to do. I flash the latest CWM recovery using Flashify. . .
I really would like to get this sorted out as I want to get into flashing with Heimdall.
Sent from my SPH-L720 using XDA Developers App
Josey Wales said:
Issue with permissions? I used "sudo" command, file path is a directory, all 6 onboard usb2.0 ports are functional. I don't know what else to do. I flash the latest CWM recovery using Flashify. . .
I really would like to get this sorted out as I want to get into flashing with Heimdall.
Sent from my SPH-L720 using XDA Developers App
Click to expand...
Click to collapse
Usually, this type of error means that either something else in linux is already using the usb port, or there's a heimdall installation issue.
check permissions (755) on heimdall.kext if your version has it.
I don't know where mint puts it.
The simplest thing to do is try every port one by one, BUT restart the computer before each attempt. I've had to do this myself in the past. If that fails, try downgrading your heimdall installation to 1.4.0. I think that's the earliest version that still supports L720. Every flavor of linux is a bit different in this regard, and there's many variables involved here. These kinds of things are typical for linux users. It's not for everyone, only people with awesomeness. Remember, we're pioneers of sorts using heimdall/linux when everyone else is using windows. Failure is not an option (or at least the admission of failure is not an option)...