Database Users

[Q] External SD-Card error, please help

Hi
I have HTC hero with CWM recovery. I was in recovery and mounted the sd card, copied few files from sd-card to comp and then on the phone I just clicked back button then realised I should have Unmounted that, having done that on the next reboot it gave me an error to remove the card and insert it, I realised something is wrong so went back into the recovery and tried mounting it but it gave me the error - "unable to write to ums Lunfile".
I dont know what to do now, the card is 8GB and dont have any other card, everything was working fine prior to this.

Plug the card into your PC and format it

sorry mate, that did not work, I also used another 2GB card, formated but that does not work as well.
Using 2GB and going into CWM recovery, while mounting it still gives the same msg?

I also checked that 8GB card putting into the card reader and using it on Win-7, the card shows fine, it is showing that Fat32 partition, obviously it is not going to show me Linux partitions.
So the point is how am I going to use that 8GB card back into my HTC hero?
should I flash CWM again on the phone? will that work?
But the phone does not recognise any sdcard so I cannot flash as well..??
what to do?

Try to reflash jordfaz's CWM

Try that : http://forum.xda-developers.com/showthread.php?t=1780438

kemoba said:
Try to reflash jordfaz's CWM
Click to expand...
Click to collapse
That does not seem to be for hero gsm i guess
SANSYF said:
Try that : http://forum.xda-developers.com/showthread.php?t=1780438
Click to expand...
Click to collapse
this thread to be honest has got only 1 person replying and was quite annoyed as he couldnt do it and was gonna throw his phone then so I am worried.
Is there anyway I could either flash RA-Hero-1.7 recovery image through command windows, if that could solve this problem?
and how to if possible.

http://forum.xda-developers.com/showthread.php?t=1723409 here, copy the .zip to a SDcard via your PC and flash it with your existing recovery

kemoba said:
http://forum.xda-developers.com/showthread.php?t=1723409 here, copy the .zip to a SDcard via your PC and flash it with your existing recovery
Click to expand...
Click to collapse
My friend you didnt get it.
My sdcard itself is not recognised by the recovery, so obviously even if I put it on the sdcard, the card itself is not recognised so I cannot use it.
Thats why I asked if it would be possible to put xxxxxx.IMG file through FASTBOOT and if anyone can advise if that would work?
Else as I already have CWM 5.xx can I replace it with recovery-RA-hero-1.7xx.IMG file? will that solve the problem?

Try it, i taught you cant mount your SD card, are you S-OFF, if you are get Amon RA .img, reboot to fastboot, do fastboot flash recovery AmonRa.img

kemoba said:
Try it, i taught you cant mount your SD card, are you S-OFF, if you are get Amon RA .img, reboot to fastboot, do fastboot flash recovery AmonRa.img
Click to expand...
Click to collapse
No I am S-ON
will that be a problem?
suddenly now adb has stopped working.
what a day begins man
could you please give me the step by step commands to flash amonra.img please..

Can you boot into your ROM ? Does your ROM "see" your SD card. If both of these questions answer yes then do this. Mount your SDCard in your ROM and copy amonra.img to it. Then do
Code:
adb remount
adb shell
flash_image recovery /sdcard/amonra.img or flash_image recovery /mnt/sdcard/amonra.img
exit
adb reboot recovery
Hopefully it should go ok, if you get some errors copy output here and i'll help

I can boot into ROM but it cannot see the sdcard?
Now no matter what I do the "adb" doesnt see the devices as well -
I treid
adb kill-server
adb start-server
adb devices
and it says no devices found
I tried going in fastboot mode and then also adb does not see my device.
it has gone to a stage - helpless

Is USB debugging on ??? Are you on linux or windows ?

kemoba said:
Is USB debugging on ??? Are you on linux or windows ?
Click to expand...
Click to collapse
windows 7 and debugging is on

:S This is weird... It sure would help if you were S-OFF but now since no SDCard or ADB this is gonna be a tough fix. Only think i see posible is to get ROM Manager from market and flash CWM recovery from there, i think that ROM Manager will flash version 2.x.x.x

i checked that, there is no market on the phone now as everything was app2sd, market is gone as well

I have Ubuntu on one machine, it was there just for some trial and learning purpose
would anything help with that

Are you sure your USB cable is OK ? No device found is almost 100% bad cable connection, do you have a spare USB

My cable is ok, i have a spare one as well, tried that , same thing, adb doesnt find anything.
I also installed android sdk20 on another pc (64bit) and that doesnt recognise phone in recovery as well..
even while connected, it doesnt even show new drivers installing or nothing..

[Q] Nexus 4 Accidentally Formated (Not able to boot)

Hey,
For starters, xda has been VERY VERY helpful to me over the past few months and I thank everyone who has ever contributed to a question or a discussion I have read.
I have a google nexus 4, and i managed to format the whole phone while i was installing a new rom. Now i can boot into bootloader and CWM but there is no files on the /sdcard/ there so that i can flash the phone
I tried to use the feature "adb push", but it´s not permited as i cannot enable the USB debugging...
I tried these guidelines: http://forum.xda-developers.com/showthread.php?t=1754018 but they didn´t help.
My phone info is:
Fastboot Mode
Product_Name: mako
HW Version: rev_11
Bootloader_version: makoz101
Signing - Production
Secure boot - enabled
Look state: Unlocked
Any ideas or suggestions are welcome.
Thank You

Boot it to fastboot and flash factory image and you're good to go. You can find instructions in the General section.

andr0idfreak said:
Boot it to fastboot and flash factory image and you're good to go. You can find instructions in the General section.
Click to expand...
Click to collapse
Fastboot = Bootloader?
Flash Recovery image, this is what i´m unable to do.
I have tried many methods from the general section, any particular thread do you think is most helpful?
I really appreciate your answer.

You could connect the phone to a PC and use CWM to mount the SD card. Copy a CWM flashable rom (99% of custom roms) to the SD card, disconnect from the PC and use CWM to flash. Job done

madgibbon said:
You could connect the phone to a PC and use CWM to mount the SD card. Copy a CWM flashable rom (99% of custom roms) to the SD card, disconnect from the PC and use CWM to flash. Job done
Click to expand...
Click to collapse
In CWM i go to "Mounts and Storage" i see the list:
mount /system
unmount /data
mount /sdcard
format.....
If i press mount /sdcard the screen flashes and nothing happens still says the same "mount /sdcard/"
Any thoughts?

arifagic said:
In CWM i go to "Mounts and Storage" i see the list:
mount /system
unmount /data
mount /sdcard
format.....
If i press mount /sdcard the screen flashes and nothing happens still says the same "mount /sdcard/"
Any thoughts?
Click to expand...
Click to collapse
You cannot currently mount SD from recovery. Use adb to push the files you want to flash to your SD, then flash them in recovery.
adb push romname.zip /sdcard/

arifagic said:
Fastboot = Bootloader?
Flash Recovery image, this is what i´m unable to do.
I have tried many methods from the general section, any particular thread do you think is most helpful?
I really appreciate your answer.
Click to expand...
Click to collapse
Fatboot = Bootloader, yup! I would read this thread for detailed information.
http://forum.xda-developers.com/showthread.php?t=2010312
If you are not so comfortable with about, you can try out Wug's Nexus Root Toolkit (a bit riskier though) that I have used a couple of times to restore factory images, works fine.
madgibbon said:
You could connect the phone to a PC and use CWM to mount the SD card. Copy a CWM flashable rom (99% of custom roms) to the SD card, disconnect from the PC and use CWM to flash. Job done
Click to expand...
Click to collapse
This is the most simple way if you have CWM recovery.

Fixed!
Had the same problem just now and it scared the heck out of me.
Solved it by doing the following (Did this using ClockWorkMod Recovery 6.0.2.3 so some steps may be different from yours)
Boot to recovery
Connect your device to PC
Download and extract this - http://forum.xda-developers.com/showthread.php?t=1996051
Go to device manager and see that your device has the ! sign
Install the drivers you just downloaded to your device
Rename your rom to update.zip and copy it to where your adb is located
Your device should now be detected by adb so type this - adb push update.zip /sdcard/
In your device, go to install from SD card > apply /sdcard/update.zip
DONE!

Thanks man
I just tried this in boot loader, then i got this error:
http://awesomescreenshot.com/0a3ydrw8d
(Device not found)
---
Then i booted into CWM v6.0.1.9 and then the device was found, and it seems like it successfully transfered the file.
http://awesomescreenshot.com/03cydsr1c < which is great, but when i go to "install zip from sdcard" -> "choose zip from sdcard" the screen blinks and at the bottom it says:
- No files found
----
I then formated the sdcard from the advanced menu and retried transfering the files and it worked
Fantastic!!! Jusdavis i can´t thank you enough.

[Q] Won't boot after ROM install

Hello! My first post here on the forum
So I've got this problem that my Samsung Galaxy S4 won't boot properly after the rom install.
The recovery I've been using is CWM and after the install when I press reboot the phone vibrates and the "Samsung Galaxy S4 GT-I9505" screen shows up and then the phone immediately shuts down again. Now I can't get the phone to start... :/
Thanks, Joakim.

juckeyy said:
Hello! My first post here on the forum
So I've got this problem that my Samsung Galaxy S4 won't boot properly after the rom install.
The recovery I've been using is CWM and after the install when I press reboot the phone vibrates and the "Samsung Galaxy S4 GT-I9505" screen shows up and then the phone immediately shuts down again. Now I can't get the phone to start... :/
Thanks, Joakim.
Click to expand...
Click to collapse
Do a data factory reset reflash the rom again and clear the caches and reboot. Which rom did you flash?

gee2012 said:
Do a data factory reset reflash the rom again and clear the caches and reboot. Which rom did you flash?
Click to expand...
Click to collapse
Hmm alright, I tried to flash 4.2.2 google edition. But the problem is now when I go into recovery my phone can't find any ROM to install.
It feels like it's broken. And I've got no adapter for the micro-SD card so I manually can put in a rom to the SD :/
I can get in to the CWM recovery but in "install zip update package -> choose ZIP from sdcard" there is nothing. So all I can do is try to get a rom into the external SD and flash from there?

juckeyy said:
Hmm alright, I tried to flash 4.2.2 google edition. But the problem is now when I go into recovery my phone can't find any ROM to install.
It feels like it's broken. And I've got no adapter for the micro-SD card so I manually can put in a rom to the SD :/
I can get in to the CWM recovery but in "install zip update package -> choose ZIP from sdcard" there is nothing. So all I can do is try to get a rom into the external SD and flash from there?
Click to expand...
Click to collapse
Yes, do that. Power down the phone, take the sdcard out and place a rom on it, boot into recovery and flash it in CWM. If that gives problems flash a stock rom in downloadmode with Odin.

juckeyy said:
Hmm alright, I tried to flash 4.2.2 google edition. But the problem is now when I go into recovery my phone can't find any ROM to install.
It feels like it's broken. And I've got no adapter for the micro-SD card so I manually can put in a rom to the SD :/
I can get in to the CWM recovery but in "install zip update package -> choose ZIP from sdcard" there is nothing. So all I can do is try to get a rom into the external SD and flash from there?
Click to expand...
Click to collapse
push rom with adb. (you must have adb file on your pc)
boot into custom recovery, connect your phone, put the rom in with adb folder, open cmd prompt in the adb folder and type:
Code:
adb devices
you must see serial number
Code:
adb push name_of_rom.zip /data/media/
or
Code:
adb push name_of_rom.zip /sdcard/
Code:
adb reboot recovery
then install the rom

samersh72 said:
push rom with adb. (you must have adb file on your pc)
boot into custom recovery, connect your phone, put the rom in with adb folder, open cmd prompt and type:
Code:
adb devices
you must see serial number
Code:
adb push name_of_rom.zip /data/media/
or
Code:
adb push name_of_rom.zip /sdcard/
Code:
adb reboot recovery
then install the rom
Click to expand...
Click to collapse
I`am out of thanks and will thank you tomorrow, wasn`t sure adb sideload worked on Samsung devices (i now it works on HTC, Sony and Nexus devices)

gee2012 said:
I`am out of thanks and will thank you tomorrow, wasn`t sure adb sideload worked on Samsung devices (i now it works on HTC, Sony and Nexus devices)
Click to expand...
Click to collapse
NVM my friend
adb commands work in custom recovery mode even if "usb debugging" is disabled.
it is just a simple push to sd :good:
EDIT: @gee2012 can you do me a favor, since i dont have my s4 with me right now, can you try if adb recognized your phone in custom recovery mode?? i just want to be sure
Code:
adb devices
thx

gee2012 said:
Yes, do that. Power down the phone, take the sdcard out and place a rom on it, boot into recovery and flash it in CWM. If that gives problems flash a stock rom in downloadmode with Odin.
Click to expand...
Click to collapse
Hmm, couldnt find my adapter. Is there no way to flash in the stock rom with odin?
samersh72 said:
push rom with adb. (you must have adb file on your pc)
boot into custom recovery, connect your phone, put the rom in with adb folder, open cmd prompt in the adb folder and type:
Code:
adb devices
you must see serial number
Code:
adb push name_of_rom.zip /data/media/
or
Code:
adb push name_of_rom.zip /sdcard/
Code:
adb reboot recovery
then install the rom
Click to expand...
Click to collapse
Hmm wow seems like a long process but i'll try it.
Thanks!

samersh72 said:
NVM my friend
adb commands work in custom recovery mode even if "usb debugging" is disabled.
it is just a simple push to sd :good:
EDIT: @gee2012 can you do me a favor, since i dont have my s4 with me right now, can you try if adb recognized your phone in custom recovery mode?? i just want to be sure
Code:
adb devices
thx
Click to expand...
Click to collapse
No bro, the device is OFFLINE. You would have checked the box first when the device was on in usb mode. Like you have to with a nexus (fingerprint).

gee2012 said:
No bro, the device is OFFLINE. You would have checked the box first when the device was on in usb mode. Like you have to with a nexus (fingerprint).
Click to expand...
Click to collapse
are you sure you are in custom recovery??
no, you need usb debugging enabled only when the OS is booted.
in custom recovery, you will see the serial number with "recovery" at the right in cmd
adb in custom recovery works fine with my SII plus
Code:
C:\Users\Samer\Desktop>adb devices
List of devices attached
014E1E761000700C recovery
C:\Users\Samer\Desktop>
thank you my friend

samersh72 said:
are you sure you are in custom recovery??
no, you need usb debugging enabled only when the OS is booted.
in custom recovery, you will see the serial number with "recovery" at the right in cmd
adb in custom recovery works fine with my SII plus
thank you my friend
Click to expand...
Click to collapse
Wait one minute bro.

samersh72 said:
are you sure you are in custom recovery??
no, you need usb debugging enabled only when the OS is booted.
in custom recovery, you will see the serial number with "recovery" at the right in cmd
adb in custom recovery works fine with my SII plus
Code:
C:\Users\Samer\Desktop>adb devices
List of devices attached
014E1E761000700C recovery
C:\Users\Samer\Desktop>
thank you my friend
Click to expand...
Click to collapse
Hey when I type in adb devies it says mine is unauthorized :/

samersh72 said:
push rom with adb. (you must have adb file on your pc)
boot into custom recovery, connect your phone, put the rom in with adb folder, open cmd prompt in the adb folder and type:
Code:
adb devices
you must see serial number
Code:
adb push name_of_rom.zip /data/media/
or
Code:
adb push name_of_rom.zip /sdcard/
Code:
adb reboot recovery
then install the rom
Click to expand...
Click to collapse
Yes, you`re right. The serialnumber is shown in recovery mode after typing adb devices in cmd. Was on stock ( + stock recovery) and not rooted.
Sorry it took so long. I have usb debugging enabled btw.
-Edit- also with usb debugging disabled the serialnumber is shown.in recovery.

juckeyy said:
Hey when I type in adb devies it says mine is unauthorized :/
Click to expand...
Click to collapse
make sure you have the right driver for samsung
you must have custom recovery and not stock recovery to be recognized by adb command
use the latest adb file version (attached)
make sure that your phone in custom recovery mode
put the rom into adb folder and open cmd in that folder
push the rom
gee2012 said:
Yes, you`re right. The serialnumber is shown in recovery mode after typing adb devices in cmd. Was on stock ( + stock recovery) and not rooted.
Sorry it took so long. I have usb debugging enabled btw.
Click to expand...
Click to collapse
+1
it will not recognize your phone in stock recovery :good:
EDIT: yes, enabling usb debugging is used only when your phone is booted in os

samersh72 said:
make sure you have the right driver for samsung
you must have custom recovery and not stock recovery to be recognized by adb command
use the latest adb file version (attached)
make sure that your phone in custom recovery mode
put the rom into adb folder and open cmd in that folder
push the rom
+1
it will not recognize your phone in stock recovery :good:
EDIT: yes, enabling usb debugging is used only when your phone is booted in os
Click to expand...
Click to collapse
I've got the right driver, my phone is in CWM recovery and rom is in the adb folder.
What do you mean with "open cmd in that folder"?

juckeyy said:
I've got the right driver, my phone is in CWM recovery and rom is in the adb folder.
What do you mean with "open cmd in that folder"?
Click to expand...
Click to collapse
open adb folder where the rom included.
"shift" + mouse right click, choose "open command window here"
download adb.zip 1.0.31 attached in my previous post, if you dont have it

samersh72 said:
open adb folder where the rom included.
"shift" + mouse right click, choose "open command window here"
download adb.zip 1.0.31 attached in my previous post, if you dont have it
Click to expand...
Click to collapse
I did still didnt work. Now I managed to get a ROM into my SD-card so now i'll boot custom recovery and try to install.
lets hope for the best!

Hey again!
Just wanna thank everybody for the help. I solved everything with flashing in stock ROM with odin.
I'll try again tomorrow with other ROM:s
Thanks, Joakim.

had same problem
hi there my s4 done the same after trying to install cy 10.1
I made a back up first with cwm
then went to install cy 10.1 rom after it said it was done I reboot and got the same problem
I took out my battery waited couple of mins and booted up in cwm mode then went to restore and installed my back up
alls working again but still have not found a fix to install custom roms.

fezz64 said:
hi there my s4 done the same after trying to install cy 10.1
I made a back up first with cwm
then went to install cy 10.1 rom after it said it was done I reboot and got the same problem
I took out my battery waited couple of mins and booted up in cwm mode then went to restore and installed my back up
alls working again but still have not found a fix to install custom roms.
Click to expand...
Click to collapse
Is it the same with other roms?
Make sure the download is not corrupted.
Wipe data, cache and dalvic after flashing the rom, reboot
sent from my Galaxy

*SOLVED* Embarrassed to ask for help - but please help!

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

I installed update.zip with TWRP - system does not boot

Hello. I wiped my phone from TWRP 3.2.1.0. Then installed update.zip from B09 Nougat for A2017G version. My system does not boot. Is update.zip the complete system or maybe I am in bad sytuation not having full system install.

Filozof71 said:
Hello. I wiped my phone from TWRP 3.2.1.0. Then installed update.zip from B09 Nougat for A2017G version. My system does not boot. Is update.zip the complete system or maybe I am in bad sytuation not having full system install.
Click to expand...
Click to collapse
You didn't realize that it failed to flash, right? You have no system. Download raystef66's TWRP flashable B09 bootstack and stocksystem and flash them. Also flash Magisk 15.2 and format data (not wipe).
Or you can use slim⁴ or just a custom ROM, but read this time

Filozof71 said:
Hello. I wiped my phone from TWRP 3.2.1.0. Then installed update.zip from B09 Nougat for A2017G version. My system does not boot. Is update.zip the complete system or maybe I am in bad sytuation not having full system install.
Click to expand...
Click to collapse
Next news. This couses that I hvae not TWRP anymore, I have stock recovery. I cannot install anything by sideload. I cannot also enter bootloader mode to flash TWRP. Is there anyone to help to resolve this puzzle?

Filozof71 said:
Next news. This couses that I hvae not TWRP anymore, I have stock recovery. I cannot install anything by sideload. I cannot also enter bootloader mode to flash TWRP. Is there anyone to help to resolve this puzzle?
Click to expand...
Click to collapse
If you have an SD card flash an update.zip. i even made a guide some time ago on how to do this if you don't know how to (update/roll back officially). Or go into EDL mode and use axon7tool to install TWRP, then use the B09 flashable zips

Choose an username... said:
If you have an SD card flash an update.zip. i even made a guide some time ago on how to do this if you don't know how to (update/roll back officially). Or go into EDL mode and use axon7tool to install TWRP, then use the B09 flashable zips
Click to expand...
Click to collapse
Hello.
1. I alredy tried to put update.zip file from B09 update and when I choose "Apply update from SD card" I obtain:
Supported API: 3
--- Couldn't mount /sdcard
Installation aborted
2. I cannot put the phone in a state I could be seen by command "adb devices". Are You sure axon7tool is over it?
When I check "Rebot to bootloader" I obtain placeholder and when I click volume button I obtain menu:
Power Off
Restart
Recovery
Fastboot
When I check "Fastboot it just reloads to the same menu". The device is not visible by "adb devices" command
BTW I owned ZTE Nubia Z7 mini, and now I also have LeEco Le Max 2. None of this was not so easy to put in unstable state. I performed about 50 ROM installations on my LeEco, wiping, backups and restores, adb sidloads and havo no such problems like with Axon 7.

Hello I tried to used EDL mode and Axon 7 Tool. I issued command:
D:\zteaxon>axon7tool-1.5-win64.exe -w recovery
Device not detected
Failed to connect
When was in recovery
D:\zteaxon>axon7tool-1.5-win64.exe -w recovery
Failed to connect
When was in EDL

Filozof71 said:
Hello I tried to used EDL mode and Axon 7 Tool. I issued command:
D:\zteaxon>axon7tool-1.5-win64.exe -w recovery
Device not detected
Failed to connect
When was in recovery
D:\zteaxon>axon7tool-1.5-win64.exe -w recovery
Failed to connect
When was in EDL
Click to expand...
Click to collapse
3 things:
-Format your SD card, it might not be mounted because of that
-I don't know if you did, but read about how to use axon7tool. You have to install zadig drivers for it to work. Read Controllerboy's guide
-Don't try to get adb anywhere because you can do nothing with it
-Don't try to use fastboot because you have to install it when you are in TWRP.
Plus, don't compare "how hard it is to do stuff in this phone" since you are the one who made all the mistakes...

Choose an username... said:
You didn't realize that it failed to flash, right? You have no system. Download raystef66's TWRP flashable B09 bootstack and stocksystem and flash them. Also flash Magisk 15.2 and format data (not wipe).
Or you can use slim⁴ or just a custom ROM, but read this time
Click to expand...
Click to collapse
Ok i came from LeEco Le 2 Max and this is very easy phone comparing to Axon 7. Now I am stuck with no Bootloader, edl also seems not to work. The only I can boot to stock Nugat 7 Recovery but cannot naither sodeload, nor update from SD. Please help

Filozof71 said:
Ok i came from LeEco Le 2 Max and this is very easy phone comparing to Axon 7. Now I am stuck with no Bootloader, edl also seems not to work. The only I can boot to stock Nugat 7 Recovery but cannot naither sodeload, nor update from SD. Please help
Click to expand...
Click to collapse
did you read the comment above,

Choose an username... said:
3 things:
-Format your SD card, it might not be mounted because of that
-I don't know if you did, but read about how to use axon7tool. You have to install zadig drivers for it to work. Read Controllerboy's guide
-Don't try to get adb anywhere because you can do nothing with it
-Don't try to use fastboot because you have to install it when you are in TWRP.
Plus, don't compare "how hard it is to do stuff in this phone" since you are the one who made all the mistakes...
Click to expand...
Click to collapse
Dear collegue off course I am not about to blame anybody than me for these mistakes. Thanks for your guides. Any further help will be appreciated

Dear collegue so far I formatted some old 8GB micro SD card, placed update.zip and was able to install it on the phone. Now I perform Google restore of my phone. Seems to bo OK. Thank You All for your help.
Finally I performed "unlock bootloader" command from Axon 7 Toolkit, flashed with Miflash and I have again fastboot running.
BIG THANKS.

OK. I was able to manage it. Here some remarks, maybe or maybe not obvious for everybody.
1. Performing again unlock bootloader with MiFlash (ZTE Axon Toolkt) repairs fastboot mode
2. When I installed original ROM from SD Card then flashed TWRP my system decoded the data partotion - it asked password at system startup and data partition was unable to remove/wipe from TWRP. Then I flashed original recovery with fastboot and was able wipe data partition

Filozof71 said:
Dear collegue so far I formatted some old 8GB micro SD card, placed update.zip and was able to install it on the phone. Now I perform Google restore of my phone. Seems to bo OK. Thank You All for your help.
Finally I performed "unlock bootloader" command from Axon 7 Toolkit, flashed with Miflash and I have again fastboot running.
BIG THANKS.
Click to expand...
Click to collapse
Hey, I'm in the exact same situation as yours. maybe worse.
How'd you get the sd card update to work?
also what update.zip did you use? Cold you give me the link, please?
I get the error "Sorry, you can't sdcard upgrade"

Evil0verlord said:
Hey, I'm in the exact same situation as yours. maybe worse.
How'd you get the sd card update to work?
also what update.zip did you use? Cold you give me the link, please?
I get the error "Sorry, you can't sdcard upgrade"
Click to expand...
Click to collapse
Try to disable OEM unlock (or enable it) from Developer options. Then try again.
If it doesn't work, then you can update via EDL. It's a bit riskier but it will work