Related
Hello all,
So I've been digging through the site for a week or so before i made the plunge to Root my stock Magic. I bought at v1.5, updated to 1.6 (before I new I wanted to Root). I have since gone back to 1.5, created back up with Cyanogen, Flashed, Wiped and am now at the point where Im trying to load my new Rom (Cyanogen's latest) via update.zip.
Problem is, Im using a mac so there is no zip extension by default. I add the extention, plug the SD into my phone, boot to recovery and attempt to install but I fails displaying: "E:Can't access open/sdcard/update.zip (bad) Installation aborted"
Any idea's? I've seen a couple recommenations to rename minus "zip" or reformat the SD card. None of which have helped. Im currently sitting at v1.5 rejecting the Tmobile 1.6 system update messages a couple times an hour!!! *sigh*
if your using a recent recovery rom you should have choose zip option
so just download cy rom leave name as is then put in root of sd boot to recovery and choose zip
sitimber said:
if your using a recent recovery rom you should have choose zip option
so just download cy rom leave name as is then put in root of sd boot to recovery and choose zip
Click to expand...
Click to collapse
Thanks for you response.
I am using CyanogenMod v1.4 Recovery. I have the option to "apply any zip from SD" but nothing is displayed in the list unless its named "update.zip" I had other files on the card that don't show up. In fact, Cyanogen's last update links to a Wiki that doesn't even instruct you to rename the new Rom's to 'update' but again, my SD doesnt display them.
Is the zip on the root of your card? You should probably redownload the CM rom and put that one you redownloaded on your sdcard without renaming it or anything. That might work.
how do you copy the file across
phone in recovery mode or phone fully booted
if the first you will need to reboot back to recovery after you copied it accross to show
you could fully format your card fat32 if your using cy rom mount sd card and copy just the cy rom across to the card remember to backup card first
sitimber said:
how do you copy the file across
phone in recovery mode or phone fully booted
if the first you will need to reboot back to recovery after you copied it accross to show
you could fully format your card fat32 if your using cy rom mount sd card and copy just the cy rom across to the card remember to backup card first
Click to expand...
Click to collapse
I tried 2 options. 1)Fully booted via usb into the card and 2)removing card and mounting via a Card Reader to my Mac. In both cases I booted to Recovery Mode on the phone and had the same result.
As far as formating the card, its not stock, its an 8 gig that I formated via the phone's erase/format function. Is that not sufficient?
In regards to cy's ROM Im not able to access it after I backup with the apk i have (never get the "Load Custom Rom" button, which is why im using cynoagens.
Anartic said:
Is the zip on the root of your card? You should probably redownload the CM rom and put that one you redownloaded on your sdcard without renaming it or anything. That might work.
Click to expand...
Click to collapse
Yup...had already tried that too. *sigh* SD card wont see anything unless its named 'update.zip'.
try the amon_ra recovery
http://rapidshare.com/files/291689412/recovery-RA-magic-v1.2.3H.img 32a phone
http://rapidshare.com/files/291689411/recovery-RA-magic-v1.2.3G.img 32b phone
Copy recovery-RA-magic-v1.2.3H.img to a location where fastboot can find it.
Boot your Magic into fastboot mode (boot while holding BACK)
Connect your Magic via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-magic-v1.2.3H.img (remember to change the H to a G if you have 32b)
when booted to recovery
partition card via this
than go to bottom of menu and select mount sd card
copy file across and reboot back to recovery
select choose.zip and ???????
Ohene10 said:
Im currently sitting at v1.5 rejecting the Tmobile 1.6 system update messages a couple times an hour!!! *sigh*
Click to expand...
Click to collapse
I'm assuming the quoted statement above is still true. I flash via a Mac all the time, so here's what I would do if I were you.
Have the phone booted into your standard ROM.
Plug in the USB cable.
Pull the top menu down on your phone and choose Mount USB.
You should see a new volume in Finder on your Mac (Mine is called no name)
Put the TWO files required for Cyanogenmod on the root of that volume (one of the files is called HTCRootedBase something or other.zip and the other is Cyanogen's actual changes)
Power off the phone after the file copy is complete.
Unplug the USB.
Reboot into recovery by holding the Home&Power button.
Choose apply any zip
Select the HTCRootedBase file first.
Let it do its thing.
When it says "Install from SD complete", run apply any zip again.
Choose the Cyanogen zip file.
When it says "Install from SD complete", reboot the phone.
Be PATIENT. It may take 5 minutes for the phone to reboot, but as soon as you see the blue Android logo with the guy on the skateboard you can start doing the happy dance.
sitimber said:
try the amon_ra recovery
http://rapidshare.com/files/291689412/recovery-RA-magic-v1.2.3H.img 32a phone
http://rapidshare.com/files/291689411/recovery-RA-magic-v1.2.3G.img 32b phone
Copy recovery-RA-magic-v1.2.3H.img to a location where fastboot can find it.
Boot your Magic into fastboot mode (boot while holding BACK)
Connect your Magic via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-magic-v1.2.3H.img (remember to change the H to a G if you have 32b)
when booted to recovery
partition card via this
than go to bottom of menu and select mount sd card
copy file across and reboot back to recovery
select choose.zip and ???????
Click to expand...
Click to collapse
Forgive my ignorance but Im completely new to this. After fastbooting and connecting to my Mac Im stumped....
jsnyng said:
I'm assuming the quoted statement above is still true. I flash via a Mac all the time, so here's what I would do if I were you.
Have the phone booted into your standard ROM.
Plug in the USB cable.
Pull the top menu down on your phone and choose Mount USB.
You should see a new volume in Finder on your Mac (Mine is called no name)
Put the TWO files required for Cyanogenmod on the root of that volume (one of the files is called HTCRootedBase something or other.zip and the other is Cyanogen's actual changes)
Power off the phone after the file copy is complete.
Unplug the USB.
Reboot into recovery by holding the Home&Power button.
Choose apply any zip
Select the HTCRootedBase file first.
Let it do its thing.
When it says "Install from SD complete", run apply any zip again.
Choose the Cyanogen zip file.
When it says "Install from SD complete", reboot the phone.
Be PATIENT. It may take 5 minutes for the phone to reboot, but as soon as you see the blue Android logo with the guy on the skateboard you can start doing the happy dance.
Click to expand...
Click to collapse
Unable to install the ROM...same error message: "E:Can't access open/sdcard/HTC_ADP_1......zip (bad) Installation aborted"
can you try another sd card
Ok, problem solved! It seems my Mac was not correctly downloading the files in the zip format even though i was manually changing the extention. Luckily i have Parallels so I downloaded via XP and added the correct zip files to my sd from there and success! Thanks for all your help!!!
glad you got there bet you learned alot about adb recovery because of your little problem
Hi Folks,
M relatively very new to android usage. I recently brought Samsung Nexus S which I loaded with MIUI to experiment and experience a richer UI feel. However, it didn't work too well for me due to stability issues like message keeps crashing even after applying mms.apk patch.
Well after been thru with the experiment, I want to get back to stock ROM which came with Nexus S. I referred to the forum link but I keep getting an error as installation failed in recovery mode. Is there something wrong that I am doing. Some One please help!!!!!
It would be great if I can have my nexus S on dual boot with both MIUI and Stock ROM installed and I having option to chose one while booting the phone.. However, that is not a must have....
Must have is only a way to get back to Stock ROM for Nexus... All help very much appreciated.
<Many Thanks to all...
You know that the Nexus S rewrites the stock recovery over every boot (unless you rename it) Can you boot into fastboot? And reflash CWM?
Sent from my NS (no it's NOT SNS or GNS)
Moved to Nexus S forums for better exposure.
To get back to stock:
a) boot into fastboot mode (vol up + power on)
b) flash cwm recovery via adb console (fastboot flash recovery recoveryname.img) (recovery file has to be inside the /tools folder in adb)
c) go into cwm recovery
d) mount usb storage
e) after pop up on pc: copy the the correct zip for your NxS type on your sdcard/usb storage. Download it from here: http://forum.xda-developers.com/showthread.php?t=1056062
f) unmount usb storage
g) stay inside the recovery menu, but go to install from zip menu
h) navigate to the zip file you downloaded and placed on your usb storage at e)
i) confirm the installation and wait for it to finish
j) move to top recovery menu, choose reboot and you're done, stock Android 2.3.4
If you get any unknown device errors you're missing usb drivers for your phone mostlikely, get them from the guides on this forum.
If everything else fails you. Go to www.samfirmware.com > Toolbox > firmware > etc > choose correct firmware for your NxS model. After downloading Odin itself from samfirmware.com (Toolbox > programs) as well.
Start Odin, there should be a yellow field with a port number (if not you're missing drivers). Make sure only "Auto reboot" and "F. Reset time" are checked. Add the correct files from the zip you got off samfirmware.com. Bootloader belongs to Bootloader, PDA to PDA and Phone to Modem. CSC can be left empty, it'll just change the carrier info inside the bootloader. Press "Start", wait for Odin to finish, it'll say when it's done (takes ~2-3mins, yellow field is now blue and says "Pass").
rentaric said:
To get back to stock:
a) boot into fastboot mode (vol up + power on)
b) flash cwm recovery via adb console (fastboot flash recovery recoveryname.img) (recovery file has to be inside the /tools folder in adb)
c) go into cwm recovery
d) mount usb storage
e) after pop up on pc: copy the the correct zip for your NxS type on your sdcard/usb storage. Download it from here: http://forum.xda-developers.com/showthread.php?t=1056062
f) unmount usb storage
g) stay inside the recovery menu, but go to install from zip menu
h) navigate to the zip file you downloaded and placed on your usb storage at e)
i) confirm the installation and wait for it to finish
j) move to top recovery menu, choose reboot and you're done, stock Android 2.3.4
If you get any unknown device errors you're missing usb drivers for your phone mostlikely, get them from the guides on this forum.
If everything else fails you. Go to www.samfirmware.com > Toolbox > firmware > etc > choose correct firmware for your NxS model. After downloading Odin itself from samfirmware.com (Toolbox > programs) as well.
Start Odin, there should be a yellow field with a port number (if not you're missing drivers). Make sure only "Auto reboot" and "F. Reset time" are checked. Add the correct files from the zip you got off samfirmware.com. Bootloader belongs to Bootloader, PDA to PDA and Phone to Modem. CSC can be left empty, it'll just change the carrier info inside the bootloader. Press "Start", wait for Odin to finish, it'll say when it's done (takes ~2-3mins, yellow field is now blue and says "Pass").
Click to expand...
Click to collapse
I am able to get in cwm and perform a fastboot. unfortunately, I keep getting error when i select the zip file to install the stock rom.
a) you downloaded a corrupted file (compare mp5 tags if possible)
b) you downloaded the wrong rom for your device
c) the rom has to be in the top folder of the sdcard/usb storage
d) did you unmount the usb storage after copying the file onto your phone?
I am able to get in cwm and perform a fastboot.
Click to expand...
Click to collapse
This makes me wonder though, you mixed up the order? Booting into fastboot is performed before flashing/entering cwm recovery.
Any help?
Tried downloading every single ROM I found but none of them allow me to update from my current firmware.
I think I mgiht need to first stablish a european stock android 5 so I can go ahead and use the ROMS that are actually around the web, but cdont know how to do that!
THANKS!!
I have the same problem, althought mine ends in B140. Does anyone know how to update it?
same problem but i have b210.
thanosnic said:
same problem but i have b210.
Click to expand...
Click to collapse
heroe7121 said:
I have the same problem, althought mine ends in B140. Does anyone know how to update it?
Click to expand...
Click to collapse
groggycl said:
Any help?
Tried downloading every single ROM I found but none of them allow me to update from my current firmware.
I think I mgiht need to first stablish a european stock android 5 so I can go ahead and use the ROMS that are actually around the web, but cdont know how to do that!
THANKS!!
Click to expand...
Click to collapse
yes it is possbile... but a long way..
Things you need:
Root
Unlocked bootloader
TWRP recovery
Stock Recovery
First thing first, unlock your bootloader (see chapter 2 of this MEGA thread). Then you need TWRP recovery. Download this : (it contains root file and twrp).
TWRP and ROOT
Now, tap your build number 7-10 times, this will get you Developers Option on Settings. Go to Developers Option and enable it, also you must enable "Enable USB Debugging.. then connect it to your computer. Now extract the downloaded folder, you'll see a folder named data. go inside that and hold Shift and Right Click and Click on Open Commands Windows Here.. run following commands inside quotations:
"adb devices" -> lists your device, if it doesn't then you have some problems while enabling USB debugging... do it again..
"adb reboot bootloader" -> it will reboot the device to white screen with android logo and it must display "Unlocked" on green colours. if it doesn't, it means you havent unlocked your bootloader and you must not proceed any further..
"fastboot flash recovery recovery.img" -> doing this will flash TWRP recovery
"fastboot reboot"->reboots the device..
For rooting, copy 1.zip and 2.zip to your phone/sd card. Then you must go to recovery mode. Connect your mobile to computer via USB cable, and open commands window on data folder (same as you did for TWRP).
"adb reboot recovery" -> will go to TWRP recovery. Click on Install and select 1.zip first to flash... after flashing it will reboot your device. Open the SuperSu app once and close and uninstall it. Go to recovery mode again and then flash 2.zip.. it will reboot again.. now, download Es File explorer or other root browsers. go to /data/app and cut eu.chainfire.supersu and paste it in /system/app with the following permissions rwx r-x r-x and reboot. Congrats, you are rooted now.. Off to next steps.
Now, as you're rooted. Download this file ... After downloading this file you need to copy and paste to this path: /dev/block/platform/hi_mci.0/by-name (for this, you need to be rooted).. It will change your region from c185 to c432.. Restart and you must have c432.
Now, unroot your device and flash stock recovery(for the time being). It is necessary to have stock recovery and be unrooted while upgrading android.
Upgrading process
Download this http://huaweidevices.ru/huaweiservic...urope_Dual.rar B132 version, there must be 2 folders "dload"(it should contain UPDATE.APP with file size approx. 1.3 GB) and "custom" (custom folder must also have UPDATE.APP file inside it, but very small in size) , copy the dload folder to internal memory of your phone (the folder must have updata.app inside it) and do local update... after that copy the custom folder to your device and rename it to dload and do local update again.
Note: it is necessary to flash larger UPDATE file and then smaller UPDATE file to remove Balong issues.
Then download this: http://huaweidevices.ru/huaweiservic...170_Europe.zip B170 version and repeat the above process of upgrading.
after this you should be able to see OTA update of B550/B560 marshmallow update... if it doesn't show yet, then download it from here: http://download-c.huawei.com/downloa...20&siteCode=es B550 version.
Hi guys,
Unable to boot after c*cking up a manual upgrade from B10 to B11 on my A2017G and would love your input. I feel like if I can just install TWRP again it should be an easy fix. Here's some specifics:
1. my phone is unlocked, rooted and running stock firmware.
2. I was trying to install stock recovery to install the B11 update. I did so but also tried to install another zip (B10 bootloader?) which I seem to have flashed wrong. Now just get the screen as shown on attachment and cannot boot.
3. Stock recovery seems to have been flashed and I can boot to this. From here I can boot to bootloader but can't seem to do anything from there.
4. I try update via ADB with the sideload command, but get the message "E:footer is wrong. E: Signature verification failed. Installation aborted".
5. I try to Update from SD as have the firmware zip file and TWRP on the root of my external SD card, but get the message "Couldn't Mound /sdcard, aborted."
6. The only time my phone shows as a connected device in ADB is when I try to sideload files. No other ADB code seems to work, only get the message "error: closed" on the terminal.
Assuming I've got all the firmware files (and full backups on my external SD) I feel like if I can just install TWRP again it should be an easy fix. So, any ideas on how I install TWRP given situation above?
Best,
Neil
nstirton said:
Hi guys,
Unable to boot after c*cking up a manual upgrade from B10 to B11 on my A2017G and would love your input. I feel like if I can just install TWRP again it should be an easy fix. Here's some specifics:
1. my phone is unlocked, rooted and running stock firmware.
2. I was trying to install stock recovery to install the B11 update. I did so but also tried to install another zip (B10 bootloader?) which I seem to have flashed wrong. Now just get the screen as shown on attachment and cannot boot.
3. Stock recovery seems to have been flashed and I can boot to this. From here I can boot to bootloader but can't seem to do anything from there.
4. I try update via ADB with the sideload command, but get the message "E:footer is wrong. E: Signature verification failed. Installation aborted".
5. I try to Update from SD as have the firmware zip file and TWRP on the root of my external SD card, but get the message "Couldn't Mound /sdcard, aborted."
6. The only time my phone shows as a connected device in ADB is when I try to sideload files. No other ADB code seems to work, only get the message "error: closed" on the terminal.
Assuming I've got all the firmware files (and full backups on my external SD) I feel like if I can just install TWRP again it should be an easy fix. So, any ideas on how I install TWRP given situation above?
Best,
Neil
Click to expand...
Click to collapse
Are you able to boot into EDL mode by typing ADB reboot edl ?
If so you can flash desired recovery with axon7tool
marcus.linkenbach said:
Are you able to boot into EDL mode by typing ADB reboot edl ?
If so you can flash desired recovery with axon7tool
Click to expand...
Click to collapse
Hi, thanks for your reply. Unfortunately not, just get the message "error: closed" in the terminal. Is there a button combination I could press in order to get into EDL?
nstirton said:
Hi, thanks for your reply. Unfortunately not, just get the message "error: closed" in the terminal. Is there a button combination I could press in order to get into EDL?
Click to expand...
Click to collapse
Try vol+ + vol- + power
it seems that the only time my device will show as connected in ADB is when I navigate through Recovery and select the "Apply Update from ADB" option. But even then, whilst it shows as connected, it only seems to allow the "sideload" command. Please see screenshot of Terminal. So at no other time will it show as a connected device.
Similarly, to have it show up in Device Manager, it'll only show when I switch the phone off, hold down Vol+ & Vol- and attached the power cable.
You are still on MM. So you are able to boot into bootloader.
adb reboot bootloader
fastboot devices
Now it should show your device as fastboot
If so you can now flash recovery with “fastboot flash recovery recovery.img“
marcus.linkenbach said:
You are still on MM. So you are able to boot into bootloader.
adb reboot bootloader
fastboot devices
Now it should show your device as fastboot
If so you can now flash recovery with “fastboot flash recovery recovery.img“
Click to expand...
Click to collapse
Thanks for your reply. Unfortunately as mentioned the only time my device shows as connected in Terminal is when I select "Update via ADB" whilst in recovery. Otherwise the device never shows as connected in adb.
So unfortunately fastboot doesn't seem to be an option for me.
Perhaps my drivers are out of whack but assuming what I've done to my phone hasn't changed that, it must be something PC - side.
nstirton said:
Thanks for your reply. Unfortunately as mentioned the only time my device shows as connected in Terminal is when I select "Update via ADB" whilst in recovery. Otherwise the device never shows as connected in adb.
So unfortunately fastboot doesn't seem to be an option for me.
Perhaps my drivers are out of whack but assuming what I've done to my phone hasn't changed that, it must be something PC - side.
Click to expand...
Click to collapse
But what if it shows your device as sideload? Can't you there reboot into fastboot?
No, it doesn't accept the command. Only one accepts is sideload. You can see from my screenshot a few posts back that the device is connected but shows different to how it normally would.
Breakthrough!
I seemed to follow the steps I've tried 100 times today and I now have TWRP installed again!
Thanks again to those who helped
Current scenario: I can only boot into Android Recovery.
Options on screen:
.Reboot system rom
.Reboot to bootloader
.Apply update from ADB
.Apply update from SD card
.Wipe data/factory reset
.Wipe cache partition
.View recovery logs
.Power Off
Select "apply udate from ADB" only allows me ADB sideload. Not sure how to sideload TWRP. Selecting any rom gives me signature issue.
When I select "apply update from ADB", Windows 10 devmgmt.msc shows "Universal Serial Bus devices: ZTE A2017U".
I cannot boot to get any serial port connection.
Your assistance is appreciated!
itsmeinarizona said:
Current scenario: I can only boot into Android Recovery.
Options on screen:
.Reboot system rom
.Reboot to bootloader
.Apply update from ADB
.Apply update from SD card
.Wipe data/factory reset
.Wipe cache partition
.View recovery logs
.Power Off
Select "apply udate from ADB" only allows me ADB sideload. Not sure how to sideload TWRP. Selecting any rom gives me signature issue.
When I select "apply update from ADB", Windows 10 devmgmt.msc shows "Universal Serial Bus devices: ZTE A2017U".
I cannot boot to get any serial port connection.
Your assistance is appreciated!
Click to expand...
Click to collapse
Of course you can't sideload TWRP... Things would be much easier
You left out a rather important piece of info. Is your phone unlocked? Do you have OEM unlocking or usb debugging enabled?
Also, the current scenario is nice to know, but how did you get there?? ?
From the MiFavor recovery you can only install MiFavor ROMs that have been signed by ZTE, so no luck there. You have 3 things to try:
-Factory reset and see if it works. Honestly not knowing what the heck you did doesn't help, but if it suddenly entered the recovery without you touching anything, then you will probably recover the phone by formatting your data.
-Turn it off, then hold Vol+ and Vol- together and connect the USB cable (should be connected to your PC on the other end). The phone will either flash a red light and stay black or keep the red light on. If the red light stays on, get the MultiDL tool from raystef and use it to enter EDL, if the red light went off it already was in EDL. Then use EDL Tool by djkuz with a package corresponding to your phone model to rewrite the system
-Tinker with the official update.zip files and an SD card (or adb sideload). The sd card method is much more reliable than adb sideload, so get one if you will try the official update method
Choose an username... said:
You left out a rather important piece of info. Is your phone unlocked? Do you have OEM unlocking or usb debugging enabled?
Also, the current scenario is nice to know, but how did you get there??
Click to expand...
Click to collapse
Thanks! I'll try your suggestions and report back.
As for how I got here, I previously only had issues and ran MiFlash to get TWRP and access to the SD-Card. I then installed A2017Uv1.1.0B35_Bootstack_by_DrakenFX.zip and then A2017Uv1.1.0B35_StockRecovery_by_DrakenFX.zip.
Not sure what I did incorrect.
I'll spend a few days trying your suggestions. Again .. Thanks for your suggestions.
itsmeinarizona said:
Thanks! I'll try your suggestions and report back.
As for how I got here, I previously only had issues and ran MiFlash to get TWRP and access to the SD-Card. I then installed A2017Uv1.1.0B35_Bootstack_by_DrakenFX.zip and then A2017Uv1.1.0B35_StockRecovery_by_DrakenFX.zip.
Not sure what I did incorrect.
I'll spend a few days trying your suggestions. Again .. Thanks for your suggestions.
Click to expand...
Click to collapse
What were you trying to accomplish by flashing those two files? The bootstack is part of the official update files, you shouldn't have to use them at all unless you are using custom ROMs.
You can use EDL Tool to get TWRP back, instead of reflashing stock which is usually a huge file. But download a full EDL file anyways, it might save your arse someday