Hello guys,
i want to install LOS16, but running into problems at the beginning:
I updated my adb and OP Usb drivers.
I booted and flashed twrp-3.2.3-x_blu_spark_v9.91_op6
Now I tried to sideload OOS 9.0.17 -> Error: Cannot read file
I accessed the internal storage and tried to copy the file -> The Dialog to copy the files starts, but closes after some time, without any error.
Can anyone help?
Im sorry, I had already read about flash-all-partions.bat and forgot.
Now, after booting to bootloader and starting the bat i get many errors, that every .img file is nocht found
*sigh*
Yeah, everything is so obvious. unpacked all zips now its working....
delete pls
Related
Hello!
Yes, I am fairly new to this, but not a noob by any means. I've been upgrading ROM's for a long time, albeit Windows mobile.
I have rooted my Hero - confirmed by installing several ROOT only apps from the market, and accessing commands from su, # prompts.
I can't seem to upgrade my [otherwise stock] Sprint hero despite trying different approaches.
Hugely frustrating, a history of my attempts:
I copied the latest backup recovery file 1.5.2 to the root of my SD card.
I have installed ADB tools
So I open a command prompt and go into Android SDK/tools:
adb shell
su
# flash_image recovery /sdcard/ [recovery file name]
I then type 'reboot recovery' the phone reboots and I have the screen with phone image and large triangle with yellow '!' in it.
I hold 'HOME' and 'END' togerther to access menu of system recovery utility and I can only select 3 options:
reboot system now [Home+back]
apply sdcard:update.zip [Alt+S] * see below)
wipe data/factory rest [Alt+w]
At the bottom of the screen I have the error (which I have investigated and found that no-one seems to be able to explain, yet it doesn't seem to hinder most folks in flashing roms):
E:Can't open /cache/recovery/command
I initially expected to have MORE options as the first thing I wanted to do was create a Nandroid backup, but gave up on trying to do this!
*So I rename the fresh 1.1 rom zip to 'update.zip' and copy to the root of my SD card.
I 'reboot recovery' again, my phone restarts, I choose the 'Apply SDCard:update.zip' option and then it begins to install:
Install from sdcard....
Finding update package....
Opening update package....
Verifying update package....
E:No signature (599 files)
E:Verification failed
Installation aborted
I've tried updating different ROM's with similar negative results - and yes, I have checked the MD5 to ensure ROM's are 'good'
Ideas?
BTW - I still also have the error:
E:Can't open /cache/recovery/command
Get the fresh kitchen and run the auto root feature.
I would agree get the kitchen try the auto root because to me it sounds like there was a problem in your root process. screen that you are getting into is just the fastboot also what I have found to make life easier is rename the RA-Recovery-heroc-1.5.2.img to just recovery.img makes my life a whole lot easier as I mess with my phone so much I have had to RUU several times and that just makes rooting manualy a little faster.
As far as installing the Fresh ROM, I know I had an issue because I was using a MAC and when I downloaded the Zip file, the MAC would unzip it. I finally had to download the Zip file right to my phone and it worked fine.
raylusk said:
As far as installing the Fresh ROM, I know I had an issue because I was using a MAC and when I downloaded the Zip file, the MAC would unzip it. I finally had to download the Zip file right to my phone and it worked fine.
Click to expand...
Click to collapse
That's because you aren't supposed to unzip a rom.
Greetings.
I am trying to install Cyanogenmod 7.0.2 on my HTC Tattoo (still has 1.6). This is the first time I've done this.
I am following the Cyanogenmod wiki page that shows you the whole process of rooting+flashing a new rom (since this is my first post I am unable to post outside links in this thread).
In the "Installing Clockworkmod Recovery" section, I get the following error when trying to flash the image:
flash_image: not found
I listed the files in /sdcard and saw that it was completely empty.
Can anyone tell me what I missed?
I copied the Clockworkmod image file to the root directory by connecting my phone to my PC through USB (USB Debugging was on) and copying the file there.
Please let me know how to solve this.
Thank you.
I was able to solve my problem and proceed with the attempt to flash Clockworkmod. Now I'm getting another error though:
error writing recovery: No space left on device
I have plenty of space in the SD Card (~2GB), but I'm assuming the problem is with the phone's internal memory. I don't know what I can delete.
Any thoughts?
Thank you.
Hi
Ok so i see you have that kind of problems...
I done it this way.
Downloaded Rom Manager->Downloaded Superuser
Then in ROM MANAGER i clicked an option "Flash Clockwork Mod Recovery"..
After that my phone had Clockwork and i completed the procedure to Flash CM7...
Hope this will help you..
CROpipe said:
Hi
Ok so i see you have that kind of problems...
I done it this way.
Downloaded Rom Manager->Downloaded Superuser
Then in ROM MANAGER i clicked an option "Flash Clockwork Mod Recovery"..
After that my phone had Clockwork and i completed the procedure to Flash CM7...
Hope this will help you..
Click to expand...
Click to collapse
Hi,
Thanks for your reply.
I tried to do as you said and installed both Rom Manager and Superuser. But now I have other issues...
1. On Superuser, it says there is a newer version of su and to update. I accept and get the following error:
An error occurred and su was not updated. A zip file (su-2.3.1-bin-signed.zip) has been placed on your sdcard, please reboot into recovery mode and flash it to update your binary.
2. So, I decided to ignore the update of su and just move on to Rom Manager. Here, I get an error like "su was not found in /system/bin". Well, su is in "/data/local/bin", as per the cyanogen wiki to root the phone. After this, any attempt to flash Clockworkmod fails.
3. To try to make it so Rom Manager has everything it needs, I followed the wiki again, but this time I tried to move the su file to /system/bin. I got the following error:
failed on './su' - Cross-device link
Any ideas?
Thanks in advance!
Hmm, i had the same problem when i was trying to Flash CM7...
Your phone is not rooted...
I know its very frustrating but no worries!
1.Download program from this thread ->http://forum.xda-developers.com/showthread.php?t=761507... you'll see the program in attachemnts and dl the first one.
2.Paste it in your's SD card , install it (use ASTRO MANAGER, to find the program)
3.Open the program and root the phone with 1 click
4. Then Superuser will ask you to allow it and click yes, and go to ROM MANAGER.
5.You will have to allow the Superuser here too.. Do it.
6.Flash Clockwork Mod recovery, and reboot into recoverymod.
7.Flash your Rom , flash Gapps(Google applications)
8.Enjoy
Thank you CROpipe!
Your instructions worked! I now have CM7 installed on my HTC Tattoo!
Here are the issues I found though:
1. When I was trying to download the ROM using ROM Manager, the list of ROMs was empty. Maybe it's because I was not using the Premium version...? I ended up downloading the ROM from the forum, copying it to the SD card and installing it that way.
2. I tried also to install GApps through Rom Manager. I was afterwards able to set up my google account, but I still had to manually download GMail, Google Maps, ... I'm not sure if this is actually how it's supposed to go... :-/
Anyway, thanks again for the help.
Yap that is quite allright Congrats on your new ROM ))
Hi All,
I wanted to update my ideos s7-104 (best buy US) to the Joenilan froyo fusion rom and made one mistake along the way. I copied the .zip file to the external sd card not the internal sd card. So zip file is not available to CWM (2.5.1.8). I tried manually pushing the file to the tablet with ADB (from computer) but the tablet is not visible to the system (windows 7 64bit with drivers installed, I could not get HiSuite to install with upgrade.cmd). This is strange becasue the Upgrade utility which uses adb flashes the rom just fine. Of course I wiped the system and reformatted the device per the instructions. Now when the unit boots it goes the fastboot and then stops with option to reboot with back/home which works. I don't think the unit is bricked just yet since I can still get into the CWM recovery.
Does anyone have any bright ideas to move the Ideos S7 Froyo v1.3-EXT4 Stable.zip to the internal sdcard?
Thanks for all the useful information previously posted!
Bruce
St. Louis MO
Hi, let see if i can help you, if you have a backup restore, if you dont that implies some work, i dont use windows i prefer linux, you can try to create a virtual machine, with windows xp or linux ubuntu and then with fastboot commands push the file to sd card.
Another way, get the oficial rom for your tablet copy the file to ext-sdcard and follow the install instrutions of the rom, you must create the dload directory in ext-sdcard.
it look like you lost the system files and the kernel of the device, so it boot in to fastboot, fastboot does not acept adb, but fastboot has some commands to copy kernel and system file to the device, it cant copy a zip file, must be a img file.
Version 6.0.1 of cwm reads update files from ext-sdcard so you can also try to install that recovery version with fastboot.
Remember: it always a good idea to have a backup before doing anything.
Hope that helps.
Fixed
hal_2000 said:
Hi, let see if i can help you, if you have a backup restore, if you dont that implies some work, i dont use windows i prefer linux, you can try to create a virtual machine, with windows xp or linux ubuntu and then with fastboot commands push the file to sd card.
Another way, get the oficial rom for your tablet copy the file to ext-sdcard and follow the install instrutions of the rom, you must create the dload directory in ext-sdcard.
it look like you lost the system files and the kernel of the device, so it boot in to fastboot, fastboot does not acept adb, but fastboot has some commands to copy kernel and system file to the device, it cant copy a zip file, must be a img file.
Version 6.0.1 of cwm reads update files from ext-sdcard so you can also try to install that recovery version with fastboot.
Remember: it always a good idea to have a backup before doing anything.
Hope that helps.
Click to expand...
Click to collapse
Thanks so much for the tips. I was able to flash the trzmod-v3 image and now I have a working tablet again. Pretty slick I must say.
Hi, well done, i'm working with cm9 for s7 maybe in some few days you can try cm9
hal_2000
does anyone know the combination to get into recovery and cwm.
thank's
sorry my bad english
BANOUNDROID said:
does anyone know the combination to get into recovery and cwm.
thank's
sorry my bad english
Click to expand...
Click to collapse
Hi, with s7 power off press, menu + call(green key) + power, wait a few seconds and you get cwm screen if it is install
Hal_2000
When I try to copy my TWRP backup file to PC only the two boot files will copy. Is there a way around this. How would I pull the files using ADB? I have 4.3 and TWRP 2.6.
gale2000 said:
When I try to copy my TWRP backup file to PC only the two boot files will copy. Is there a way around this. How would I pull the files using ADB? I have 4.3 and TWRP 2.6.
Click to expand...
Click to collapse
Same issue....only two files copy over. It has to do with permission changes of the backup files with TWRP version 2.6. I tried doing an ADB pull in Windows, but could not get it to work (Various errors). I would also like to know the proper method to do this.
EDIT: Finally got the adb pull to work and all the files were copied over.
my nexus 4 was rooted with 4.3 but then i decide to upgrade to 4.4
this is the video i am trying to follow, basically just wipe & install which i did most the time.
youtube title "NEXUS 4: HOW TO MANUALLY UPDATE TO ANDROID 4.4 KITKAT"
it has two files one is mako and one is gapp.
after i did all the wiping in cwm and try to install the mako file, it shows "no file context" or sth similar, and installation is abort (i think there is problem when i transfer the file), but then i continue to install the gapp file (what the hell was i thinking?)
so now i am stuck in the google start up loop, i can only access cwm recovery mode and don't have a valid rom to install in my sdcard.
i tried to adb push another rom to the sdcard with no success (my storage was already very low, any way to remove files in the storage at this point?)
the "mount & storage" also doesn't seem to let me mount the sdcard (but system shows up "unmount").
so now i don't know what to do.
if anything has any idea or suggestion please let us know.
i am quite desperate now with a dead phone and will try anything.
thanks for reading such a long thread.
Dude that vid is old and it installs pa or some other port just flash factory images from google
Sent from my F1 using xda app-developers app
try to sideload a zip with ADB in recovery. no need to copy to your internal storage.
also try to connect with adb shell, then you can delete some files manual with rm.
Frickelpit said:
try to sideload a zip with ADB in recovery. no need to copy to your internal storage.
also try to connect with adb shell, then you can delete some files manual with rm.
Click to expand...
Click to collapse
any step by step guide to do this?
i am still new to this thing even i install a few roms before.
i will google it now, but any additional info is much appreciate.
thanks
Frickelpit said:
try to sideload a zip with ADB in recovery. no need to copy to your internal storage.
also try to connect with adb shell, then you can delete some files manual with rm.
Click to expand...
Click to collapse
frustrated..
i can't seem to get my windows to recogize the device (when i type adb devices, it shows an empty list)
already try trouble shooting this for a long time with no result.
any idea?
telly0050 said:
frustrated..
i can't seem to get my windows to recogize the device (when i type adb devices, it shows an empty list)
already try trouble shooting this for a long time with no result.
any idea?
Click to expand...
Click to collapse
after tons of troubleshooting finally got it back to work.
it ends up the reason is i didn't update to the latest cwm at the very beginning.
and sideloading 4.4 didn't work because of that too, i have to install an old 4.2 to have it working.