Related
Help needed please!
I'm trying to install Dexters Mod update and I keep getting the same results, it reads:
Finding update package...
Opening update package...
E: Can't open/sdcard/update.zip
(bad)
Installation aborted
Formatting misc...
I've formatted my SD card. I've tried renaming the file with a capital U, lowercase u, etc. I've wiped the unit....nothing works.
My SD card worked fine when I installed the Elocity update from their website.
What am I doing wrong? I really want to get that Marketplace installed....
Thanks for your help!
Did you do it from Recovery menu? It's necessary.
elocity
Hi, I need help with this too, I really want the market on my elocity. Thanks
Kentavr66X said:
Did you do it from Recovery menu? It's necessary.
Click to expand...
Click to collapse
Yes, I did it from the System Update option which puts the unit into the recovery menu. That's the correct way, yes?
It looks like all the Mod files from this site are damaged or corrupted...? I run a test on the download on my computer and there appears to be issues with the download. Has anyone else had this problem???
Any help is greatly appricated. Thanks!
I had trouble with the install also: i was able to enter the recovery mode but it would recognize the update then i would see the android logo and box with arrow then nothing from there this happened several times. I left the card in the unit turned it off then back on , then went to the system update and chose to update , which it did and rebooted then was locked in an Elocity loop. I reset the unit and the market and everything was there. I might of been close to bricking it ,but it works now. Be careful
esemelis said:
Yes, I did it from the System Update option which puts the unit into the recovery menu. That's the correct way, yes?
It looks like all the Mod files from this site are damaged or corrupted...? I run a test on the download on my computer and there appears to be issues with the download. Has anyone else had this problem???
Any help is greatly appricated. Thanks!
Click to expand...
Click to collapse
Sounds like your downloaded zip file was corrupted - this happens often. Try downloading it again and then try to install after that.
Recarr said:
I had trouble with the install also: i was able to enter the recovery mode but it would recognize the update then i would see the android logo and box with arrow then nothing from there this happened several times. I left the card in the unit turned it off then back on , then went to the system update and chose to update , which it did and rebooted then was locked in an Elocity loop. I reset the unit and the market and everything was there. I might of been close to bricking it ,but it works now. Be careful
Click to expand...
Click to collapse
This is quite normal. boot loop happens to 90% of users. Its well documented in the development thread. The Android logo you saw is also expected. From there, you're supposed to hit the Menu soft key and use the other soft keys to navigate the recovery console. Also well documented in the development thread.
sagggas said:
Sounds like your downloaded zip file was corrupted - this happens often. Try downloading it again and then try to install after that.
Thanks sagggas. I've tried to download it about 20 times and I get the same problem. When I run a test on the downloaded zip file my computer says it may be corrupted or incomplete. I don't get it. It's as if the something is wrong with the file, but others seem to have made it work. Any suggestions please??? I'm almost ready to get rid of this device....but since this is the only problem I've had I'm torn!
Click to expand...
Click to collapse
GetRight Download Manager
Hi
This reminds of a problem I had downloading a large software program a while back. Many people were having the same problem with corrupt files. The company recommended using a download manager called GetRight.
It worked great! It is free to use and you can get it at:
http://getright.com/get.html
Let us know if it works for you.
esemelis said:
sagggas said:
Sounds like your downloaded zip file was corrupted - this happens often. Try downloading it again and then try to install after that.
Thanks sagggas. I've tried to download it about 20 times and I get the same problem. When I run a test on the downloaded zip file my computer says it may be corrupted or incomplete. I don't get it. It's as if the something is wrong with the file, but others seem to have made it work. Any suggestions please??? I'm almost ready to get rid of this device....but since this is the only problem I've had I'm torn!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Jazzbone, that download manager worked perfectly! Once I was able to download the Dexter Mod without it getting corrupted the install went very smoothly.
Thank you sooo much for that suggestion! I can't wait to see what this tablet can do now.
Having the same problem. I did check out the website, but I saw nothing for Android,
Dealcloser73 said:
Having the same problem. I did check out the website, but I saw nothing for Android,
Click to expand...
Click to collapse
The getright manager is software for your PC to help you download large files from the internet. In our case, the functionality would then allow us to copy the newly downloaded file (apparently with a lower frequency of corruption) from our PC to our SD cards for use in our Android devices.
Hello People,
Firstly I would like to apologize if this is a duplicate post, Googling reveals tons of different documents which actually has confused me and as I have tried many, I don't even know now what have I screwed up.
Phone - U8800H
OS - Linux
I tried to update my phone and it got messed up. It simply won't boot but go in an infinite loop or restarting every 3 seconds (once the HUAWEI logo is displayed).
By pressing both Vol buttons and starting the phone I can go into bootloader mode (pink screen) and the phone drives get mounted. However trying to go to recover mode by pressing the Vol UP key during start up simply again keeps restarting the phone.
I have tried various solutions which include re-downloading the images folder files again, replacing the recover.img from clockwork, formatting that partition and retrying, almost everything.
The phone simply keeps restarting. Replacing or removing any of the file in the images folder gives me a blue screen during going to bootloader mode.
As I cant get to recover mode I don't know what to do.
The warranty of the phone is finished as it was only of three months. I was told by the company I purchased it from to be a "power problem" but I think its a software problem as I messed it up myself.
If anyone has faced such situation before please help.
Thanks.
find original rom and reinstall it.
Otherwise what rom where you on?
arkudos said:
find original rom and reinstall it.
Otherwise what rom where you on?
Click to expand...
Click to collapse
U cant install rom without clockworkmod?
sent from ideos x5
eddydc1 said:
U cant install rom without clockworkmod?
sent from ideos x5
Click to expand...
Click to collapse
_original_ means what the phone came with
Rom is the.......
He needs to go back to original phone, or to find probably the old boot.img he had, that is why I asked which rom he was on....
arkudos said:
_original_ means what the phone came with
Rom is the.......
He needs to go back to original phone, or to find probably the old boot.img he had, that is why I asked which rom he was on....
Click to expand...
Click to collapse
Okk
sent from ideos x5
The original ROM was U8800HV100R001AREC00B135SP01 CUSTC213D001 (Kuwait VIVA). I have downloaded it as well.
However as suggested it asks me to create a dload folder in a formatted SD card with the zipped files within it, and then start the phone in 'recovery mode'. However the phone doesn't start in that mode with the same restarting issue.
One person suggested to create a 'dload' folder in the SD card with no contents in it and then start the phone in 'bootloader' mode and the phone will auto revert to its default firmware. I did as suggested but it didn't work either.
I have the original boot.img that came with the phone. I also downloaded a fresh boot.img (along with the other three files that come in the images folder) but still the same result of restarting during trying to start in 'recover mode'.
It was working fine till I messed it up trying to upgrade it to 2.3 to change the patched wpa_supplicant file to connect to Ad-Hoc networks.
I think I need to change the files required for 'recover mode' to default ones, but I don't know where they reside. Any tutorial in this direction would be great.
Thanks.
My guess is that some of the partitions got messed up somehow, some different filesystems (ext4 over ext3) in 2.3 stock fw.
Have you tried copying update.app to dload-folder of sdcard then booted phone with both vol-down and vol-up pressed (bootloader mode). That should in theory start the update...
Sent from my u8800 using XDA App
huzefa_from_kuwait said:
The original ROM was U8800HV100R001AREC00B135SP01 CUSTC213D001 (Kuwait VIVA). I have downloaded it as well.
However as suggested it asks me to create a dload folder in a formatted SD card with the zipped files within it, and then start the phone in 'recovery mode'. However the phone doesn't start in that mode with the same restarting issue.
One person suggested to create a 'dload' folder in the SD card with no contents in it and then start the phone in 'bootloader' mode and the phone will auto revert to its default firmware. I did as suggested but it didn't work either.
I have the original boot.img that came with the phone. I also downloaded a fresh boot.img (along with the other three files that come in the images folder) but still the same result of restarting during trying to start in 'recover mode'.
It was working fine till I messed it up trying to upgrade it to 2.3 to change the patched wpa_supplicant file to connect to Ad-Hoc networks.
I think I need to change the files required for 'recover mode' to default ones, but I don't know where they reside. Any tutorial in this direction would be great.
Thanks.
Click to expand...
Click to collapse
Ok then.... because I'm lost... which rom was on!
2.2.1?
or 2.3.?
these are the files needed FIRST....
---------- Post added at 05:31 PM ---------- Previous post was at 05:16 PM ----------
Ok IF you were on 2.2.... on sdcard make \dload folder with update 2.2 original rom!!!!
Vol+ Vol- Power on...pink screen and it should do the rest!!!
Recovery after you reinstall 2.2!
Now IF you managed to put 2.3... then put 2.3 update in sdcard \dload and again it should do the rest.
If you are trying to come back to 2.2 or miui oxygen cm7 from the beta.... first put the 2.3 beta back on via the sdcard.
I have put the original ROM in 'dload' folder and as suggested I shall have started the phone in 'bootloader' mode now. There is no movement on the screen so I don't know even if its doing something.
How much should I wait or shall I be notified if the update is done ?
Thanks.
huzefa_from_kuwait said:
I have put the original ROM in 'dload' folder and as suggested I shall have started the phone in 'bootloader' mode now. There is no movement on the screen so I don't know even if its doing something.
How much should I wait or shall I be notified if the update is done ?
Thanks.
Click to expand...
Click to collapse
Is your folder structure like this
/sd
/sd/dload
/sd/dload/update.app
If it is, then boot to bootloader. you should see it is doing stuff.
julle131 said:
Is your folder structure like this
/sd
/sd/dload
/sd/dload/update.app
If it is, then boot to bootloader. you should see it is doing stuff.
Click to expand...
Click to collapse
I have double checked it again, the structure is 'dload' folder in the root of the memory card and the update.app file in it, still however I don't see any movement in the 'bootloader' mode, just the "pink" screen continuously lit.
What am I doing wrong ?
Thanks.
huzefa_from_kuwait said:
I have double checked it again, the structure is 'dload' folder in the root of the memory card and the update.app file in it, still however I don't see any movement in the 'bootloader' mode, just the "pink" screen continuously lit.
What am I doing wrong ?
Thanks.
Click to expand...
Click to collapse
Pink screens means it didn't work. Your phone isn't mounting the sd-card right in bootloader mode. You could try to put the dload-folder on internal sd-card, should be possible since you're on linux. Think you just need to mount the right partition when connecting your phone via usb when in pinkscreen. I don't recall exactly which partition as I'm using Windows and haven't tried this, but you should be able to find some more info around here by searching a bit...
U8800
Hello XDA-Forum!
Same problem here with my u8800
I have original recovery.img but i fd' other files by overwriting them.. (yes i know...)
Now my phone doesen't start flashing and i cant do anything. I was using almost latest version of oxygen mod.
Do i need original files to flash my phone back to stock in image/... floder? And if i need, can i dig version form recovery.img? or might this is problem with partitions? I think oxygen is known by partition problems.
HFZenon said:
Pink screens means it didn't work. Your phone isn't mounting the sd-card right in bootloader mode. You could try to put the dload-folder on internal sd-card, should be possible since you're on linux. Think you just need to mount the right partition when connecting your phone via usb when in pinkscreen. I don't recall exactly which partition as I'm using Windows and haven't tried this, but you should be able to find some more info around here by searching a bit...
Click to expand...
Click to collapse
I have tried as you suggested, There were 5 partitions on the phone 2 of which were smaller than 200MB and therefore could not save the update file which is larger in size. I have tried over the remaining three partitions but in vain, they all end up with the same pink screen.
However you might be correct that my phone is not mounting the SD card as I can't see the SD card in the list of mounted drives in the computer.
To put/move files on SD card I have to use my another phone
I will get another SD card and try. In the meanwhile if there is anything else I could try, do advice me.
Thanks.
Nahkamies said:
Hello XDA-Forum!
Same problem here with my u8800
I have original recovery.img but i fd' other files by overwriting them.. (yes i know...)
Now my phone doesen't start flashing and i cant do anything. I was using almost latest version of oxygen mod.
Do i need original files to flash my phone back to stock in image/... floder? And if i need, can i dig version form recovery.img? or might this is problem with partitions? I think oxygen is known by partition problems.
Click to expand...
Click to collapse
Hi, and welcome to XDA!
I guess you got the same problem with sd-card not mounting properly if you can't initiate stock flashing via dload-folder-method.
If you search the forums you'll find links to download all files that's needed in the image-folder of pinkscreen-partition. Then you'll hopefully be able to boot to recovery (vol-up + power), wipe data/cache/dalvik cache and flash whatever ROM you'd like. Remember this erases all your data, hopefully you've backed up whatever precious stuff you've got on your phone.
HFZenon said:
Hi, and welcome to XDA!
If you search the forums you'll find links to download all files that's needed in the image-folder of pinkscreen-partition.
Click to expand...
Click to collapse
Thank u!
I loaded Official 2.3 overseas original boot.img & recovery.img but nothing new happened. volume up+power = bootloop, if i try flash volumeup+down + power = pinkscreen. If i delete image folder comes blue. Another ideas?
Nahkamies said:
Thank u!
I loaded Official 2.3 overseas original boot.img & recovery.img but nothing new happened. volume up+power = bootloop, if i try flash volumeup+down + power = pinkscreen. If i delete image folder comes blue. Another ideas?
Click to expand...
Click to collapse
Remember that you need all files from the same version. Try this, those are from stock 2.2 if I'm not mistaken. When (if?) you get into recovery, remember to clear cache / data / dalvik cache.
HFZenon said:
Remember that you need all files from the same version. Try....
Click to expand...
Click to collapse
Bingo! I'm very grateful of your help!
Nahkamies said:
Bingo! I'm very grateful of your help!
Click to expand...
Click to collapse
Glad to hear you get it working as we both had the basically same problem.
For me however still it is the same issue, except that while going into the recover mode now it shuts down instead or restarting endlessly. Where as the bootloader mode simply does nothing.
Can you post the exact steps you did to get your work so I can also repeat them?
Thanks.
@huzefa_from_kuwait:
You've got the U8800H right? Then you need to find the correct image-folder for your phone, as it differs from what I uploaded which is for U8800.
Hello.
I have a problem with my S4 i9500. I've successfully rooted it and flashed custom recovery. But I'd also like to install custom rom on it, and there is where problem begins. Every time I flash rom and reboot it stucks at boot logo. I've tried it with Philz and TWRP recoveries and three different kitkat AOSP based roms. But the situation looks the same every time, despite waiting over 15-30 minutes the system doesn't boot properly, it stucks at boot logo. Creating backups and restoring stock rooted rom works flawlessly however with both recoveries.
I've also tired twice to install rom without doing factory reset before and then it goes trough boot logo, however stucks at "android is being actualised" window or something like that.
I hoped to get rid of ugly and slow touchwiz from my phone as fast as possible, but with no succes so far. What am I doing wrong?
Sorry for possible mistakes, english is not my first language.
mintor said:
Hello.
I have a problem with my S4 i9500. I've successfully rooted it and flashed custom recovery. But I'd also like to install custom rom on it, and there is where problem begins. Every time I flash rom and reboot it stucks at boot logo. I've tried it with Philz and TWRP recoveries and three different kitkat AOSP based roms. But the situation looks the same every time, despite waiting over 15-30 minutes the system doesn't boot properly, it stucks at boot logo. Creating backups and restoring stock rooted rom works flawlessly however with both recoveries.
I've also tired twice to install rom without doing factory reset before and then it goes trough boot logo, however stucks at "android is being actualised" window or something like that.
I hoped to get rid of ugly and slow touchwiz from my phone as fast as possible, but with no succes so far. What am I doing wrong?
Sorry for possible mistakes, english is not my first language.
Click to expand...
Click to collapse
It should just work.
- Is your bootloader up to date?
- Running latest modem?
- Try not to flash it from your external sd but from your internal.
- Use something like Airdroid to transer the files from your laptop to your phone. I find it more reliable then cabled.
- Redownload the rom again.
- Use TWRP recovery. The rest is outdated.
- Make sure to properly wipe in the recovery. Maybe even wipe your internal storage (/data).
That's what comes to mind.
Lennyz1988 said:
It should just work.
- Is your bootloader up to date?
- Running latest modem?
- Try not to flash it from your external sd but from your internal.
- Use something like Airdroid to transer the files from your laptop to your phone. I find it more reliable then cabled.
- Redownload the rom again.
- Use TWRP recovery. The rest is outdated.
- Make sure to properly wipe in the recovery. Maybe even wipe your internal storage (/data).
That's what comes to mind.
Click to expand...
Click to collapse
How do I check bootloader version and update it if necesarry?
I tried flashing both from internal and external memory, with te same result (no success).
Also, I didn't transfer roms form PC, I downloaded them directly to my phone. I did it the same way with my older phones and never had an issue like this.
mintor said:
How do I check bootloader version and update it if necesarry?
I tried flashing both from internal and external memory, with te same result (no success).
Also, I didn't transfer roms form PC, I downloaded them directly to my phone. I did it the same way with my older phones and never had an issue like this.
Click to expand...
Click to collapse
As silly as it sounds, try to download them on your pc and then transfer them.
Lennyz1988 said:
As silly as it sounds, try to download them on your pc and then transfer them.
Click to expand...
Click to collapse
I was unable to get airdroid working correctly. I'm not sure if it wasn't because of SD restrictions on Kitkat. Maybe this causes my problem as well? I also realized that many file related operations like renaming a folder, deleting files and even downloading it is unsuccessful unless I use stock samsung app. I've transferred the rom later via USB cable and flashed, but the problem still occurs.
mintor said:
I was unable to get airdroid working correctly. I'm not sure if it wasn't because of SD restrictions on Kitkat. Maybe this causes my problem as well? I also realized that many file related operations like renaming a folder, deleting files and even downloading it is unsuccessful unless I use stock samsung app. I've transferred the rom later via USB cable and flashed, but the problem still occurs.
Click to expand...
Click to collapse
What roms are you trying to flash?
Lennyz1988 said:
What roms are you trying to flash?
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-s4/i9500-develop/rom-t2913193
http://forum.xda-developers.com/showthread.php?t=2688387
and CM11 found outside XDA, I cannot find link.
I also tried to flash CM10.2 and 10.1, but both recoveries refused to even flash it.
I found out that the problem is I cannot flash kernel. I tried to flash few of them, but nothing changed in About device/Kernel Version. I also have SE for Android status "Enforcing".
mintor said:
I found out that the problem is I cannot flash kernel. I tried to flash few of them, but nothing changed in About device/Kernel Version. I also have SE for Android status "Enforcing".
Click to expand...
Click to collapse
What does it say your model is when you are in download mode?
Lennyz1988 said:
What does it say your model is when you are in download mode?
Click to expand...
Click to collapse
Do you mean "Product name"? It's SHV-E300K
It's Korean model. I'm not sure if GT-I9500 ROMs will work correctly on SHV-E300K (if it's booting), due to too many differences between International and Korean version.
Sent from my ASUS_Z00AD
mintor said:
Do you mean "Product name"? It's SHV-E300K
Click to expand...
Click to collapse
Then why did you say you have an i9500? You have a SHV-E300K which is a completely different model.
Lennyz1988 said:
Then why did you say you have an i9500? You have a SHV-E300K which is a completely different model.
Click to expand...
Click to collapse
Because in About device/Model number it shows I9500. Sorry, I didn't know the info from download mode is more important. Why would it show different things anyway?
mintor said:
Because in About device/Model number it shows I9500. Sorry, I didn't know the info from download mode is more important. Why would it show different things anyway?
Click to expand...
Click to collapse
Because you can change it manually, but you cannot change the model in in download mode.
forum.xda-developers.com/showthread.php?t=2284543&page=101
Use that thread for reference.
Ok guys bare with me. This is my first Thread. So it may look a little different then the others :laugh:
At least Your honor 7x will no longer be a paper weight
I posted last week that I do Indeed have a good TWRP Honor 7x BND-L24 USA Variant. Since then I have been getting hammered with requests for it. So being the great guy that I am, I have come to the rescue. NO MORE PAPER WEIGHT :laugh: I have also included TWRP 3.1.1. You will Find Direct download links below.
I have heard that Huawei will be releasing the firmware by end of next week. Go to play store and download Huawei Firmware
Finder(FF) To keep checking for it. Once there you can download it through Huawei FF.
When I did the backup TWRP gave me error 255 with the data.img but it did still back it up. I have the boot.img, system.img and data.img. data.img (data.img untested but should work)
If it does not I have a post here https://forum.xda-developers.com/showthread.php?p=75735265#post75735265 that explains how to use just the boot.img and system.img to recover your phone. IGNORE that it is for the 6x. It does indeed work with the 7x
If your phone is bricked and do not have twrp
1.Turn off phone
2. hold volume down while plugging in usb cable from your pc or laptop. That will put you in fastboot.
Tutorial here https://www.xda-developers.com/how-to-root-honor-7x/ on how to download and install ADB tools.
3.. Download TWRP 3.1.1 for honor 7x here https://drive.google.com/open?id=1dzP5ie7vQEn_dGfZHI383bt2sFxwtcTb
For people with TWRP installed
1. Download My TWRP backup here https://drive.google.com/open?id=1Udc4thELESZ4n_nXYmx6loQtTkjHOqSy
2. Extract the zip file to your ext, sdcard.
3. Boot phone into twrp.(Bricked phones hold volume up and press power to launch twrp assuming it is installed.
4. Select restore in twrp menu then choose sd card then the backup folder.
5. Flash the boot system and data img files
6 Reboot.
NO more paper weight :good:
Oh if anyone has twrp 3.2x that works with this with 7x BND-L24 do share please
Well hope this was not to bad :laugh:
Hit that thanks button. Yea that one under my post on the right :laugh:
Hope this has helped
Thank you
lowspeed said:
Thank you
Click to expand...
Click to collapse
No problem. Least I can do. This site has helped me out a lot
Paper weights suck :laugh:
Didn't work. I got to the "booting now" screen and was stuck there forever. I had to restore my old System and Boot partitions to get back to normal.
Didn't Work for me. goes tot the erecovery page.
Is this the only know method to get back to stock. i tried to uninstalled exposed and somehow eneded up stuck in the erecovery boot loop? very lost any help would be greatly appreciated.
Didn't work, on BND-L34 which is the same model as BND-L24 and it says your device is booting now and never boots.
tomjfmu said:
Didn't work, on BND-L34 which is the same model as BND-L24 and it says your device is booting now and never boots.
Click to expand...
Click to collapse
sad days. do you happen to know of any other alternatives? should i made a backup in TWRP before i rooted and did anything?
This does not work. Restoring data leads to error 255 and restoring just boot and system leads to an unbootable system. Also, the link provided does not help one bit. Can you please try to explain here? Thanks.
dukethedj said:
This does not work. Restoring data leads to error 255 and restoring just boot and system leads to an unbootable system. Also, the link provided does not help one bit. Can you please try to explain here? Thanks.
Click to expand...
Click to collapse
Yes please would love some insight on this. thanks in advance.
forgotenxlegacyx said:
Is this the only know method to get back to stock. i tried to uninstalled exposed and somehow eneded up stuck in the erecovery boot loop? very lost any help would be greatly appreciated.
Click to expand...
Click to collapse
As long as you flash the boot.img first it will wok I tested it myself on my wifes and daughters phone and it worked Perfectly. i did not go into detail to do it correctly because there are tutorial's on here that explain how to flash those files
BiggDipper said:
As long as you flash the boot.img first it will wok I tested it myself on my wifes and daughters phone and it worked Perfectly. i did not go into detail to do it correctly because there are tutorial's on here that explain how to flash those files
Click to expand...
Click to collapse
Would you mind linking a thread on how that is done? sorry for my ignorance
forgotenxlegacyx said:
sad days. do you happen to know of any other alternatives? should i made a backup in TWRP before i rooted and did anything?
Click to expand...
Click to collapse
i have an idea, maybe you can make a backup not just including the system, data, and boot but other stuff. Because I accidentally wiped everything, and I changed the vender to a10/tl10, and that bricked the phone even more. And the data img doesn't work. You can fix it with this https://forum.xda-developers.com/oneplus-5/help/error-255-twrp-t3739468. If someone has a working bnd-l24 or bnd-l34 can you give me everything in the backup?
BiggDipper said:
As long as you flash the boot.img first it will wok I tested it myself on my wifes and daughters phone and it worked Perfectly. i did not go into detail to do it correctly because there are tutorial's on here that explain how to flash those files
Click to expand...
Click to collapse
So you first do that then you do the rest?
Tried again. Getting the 255 error when flashing the Data
Yeah, error 255 is boot looping me too.
does it works well?
Thanks!
RoxRedEye said:
Thanks!
Click to expand...
Click to collapse
You were able to get it to work?
I want to get behind and support this, so much, .But the OP is not registered user, so cant even verify their reputation.
I am late to this device and thread, but my phone will arrive tmw.
I would like to know if this is the only current available restore method for BND-L24?
Hi everyone, I owns a Black, Made in China variant Mi A1, bought it almost 10 months ago so it's in brand new condition.
A night I was using it as regular, watching YouTube, It suddenly restarted automatically, and stuck on 'Android One' boot animation.
I wasn't doing any heavy or intensive task, was not having any issue except storage full. The device is on official stock rom and on June security patch with Android 8.1.
I've tried >?1. Apply update from ADB in recovery mode with June update, which gave me -> E: footer is wrong. E: signature verification failed. Installation aborted
>?2. Apply update from SD card with the same update as above, which gave me -> Couldn't mount SD card
Bootloader is locked, USB debugging is off, no custom recovery installed.
Is there any way to make it work again without erasing user data? I'm familiar with all kinds of Command Line Interface and with almost every tech term. Any help would be appreciated.?
I think only Miflash, with first nougat rom works for you. Save user data. Works for me, after I tried Lineage OS.
ROGGGER3G said:
I think only Miflash, with first nougat rom works for you. Save user data. Works for me, after I tried Lineage OS.
Click to expand...
Click to collapse
Hi,
i have also experienced the same issue recently and struggling hard to make it working again.
I have tried with MI flash but u need to have a bootloader unlocked as well. If not, flashing will not start.
Shashankjindal said:
Hi everyone, I owns a Black, Made in China variant Mi A1, bought it almost 10 months ago so it's in brand new condition.
A night I was using it as regular, watching YouTube, It suddenly restarted automatically, and stuck on 'Android One' boot animation.
I wasn't doing any heavy or intensive task, was not having any issue except storage full. The device is on official stock rom and on June security patch with Android 8.1.
I've tried >1. Apply update from ADB in recovery mode with June update, which gave me -> E: footer is wrong. E: signature verification failed. Installation aborted
>2. Apply update from SD card with the same update as above, which gave me -> Couldn't mount SD card
Bootloader is locked, USB debugging is off, no custom recovery installed.
Is there any way to make it work again without erasing user data? I'm familiar with all kinds of Command Line Interface and with almost every tech term. Any help would be appreciated.
Click to expand...
Click to collapse
Without reason? Probably THIS is the reason. I think your problem is related to data partition and a flash with Miflash can't help you. Only a factory reset can solve this.
ROGGGER3G said:
I think only Miflash, with first nougat rom works for you. Save user data. Works for me, after I tried Lineage OS.
Click to expand...
Click to collapse
Does it work in locked bootloader? Btw thanks for the reply.
sipollo said:
Without reason? Probably THIS is the reason. I think your problem is related to data partition and a flash with Miflash can't help you. Only a factory reset can solve this.
Click to expand...
Click to collapse
Can you describe what in the data partition caused this? Because I've been using this device with 90% storage filled for months??*.
And I've factory reset the device as there was no other ways to make it work again but still I want to know what was the cause of the problem.
Shashankjindal said:
Can you describe what in the data partition caused this? Because I've been using this device with 90% storage filled for months??*.
And I've factory reset the device as there was no other ways to make it work again but still I want to know what was the cause of the problem.
Click to expand...
Click to collapse
When memory is almost full R/W errors can occur.
Maybe 90% you see is not including temporary-swap files, so that you are dangerously close to 100% storage filled.
sipollo said:
Without reason? Probably THIS is the reason. I think your problem is related to data partition and a flash with Miflash can't help you. Only a factory reset can solve this.
Click to expand...
Click to collapse
sipollo said:
When memory is almost full R/W errors can occur.
Maybe 90% you see is not including temporary-swap files, so that you are dangerously close to 100% storage filled.
Click to expand...
Click to collapse
Thank you for your answer & time, I'll be carefull in the future.
ROGGGER3G said:
I think only Miflash, with first nougat rom works for you. Save user data. Works for me, after I tried Lineage OS.
Click to expand...
Click to collapse
I have just softbricked my Mi A1 and need to flash the official rom with MiFlash, problem is that I can't find the right file to flash. Any tips to where I can download the official firmware? I'm looking for the zipped version, not an image. MiFlash can't read the images I've downloaded so far.
FantLarve said:
I have just softbricked my Mi A1 and need to flash the official rom with MiFlash, problem is that I can't find the right file to flash. Any tips to where I can download the official firmware? I'm looking for the zipped version, not an image. MiFlash can't read the images I've downloaded so far.
Click to expand...
Click to collapse
Here are some of the links where you can find the official rom in .zip format. Check if they are compatible with MiFlash tool-
https://firmwarefile.com/xiaomi-mi-a1
https://dhananjaytech.com/flash-stock-rom-mi-a1-through-twrp/
Here is the XDA thread- https://forum.xda-developers.com/mi-a1/development/rom-tissot-stock-oreo-8-0-rooted-t3735760.
I'll be happy if this was helpful.
Shashankjindal said:
Here are some of the links where you can find the official rom in .zip format. Check if they are compatible with MiFlash tool-
https://firmwarefile.com/xiaomi-mi-a1
https://dhananjaytech.com/flash-stock-rom-mi-a1-through-twrp/
Here is the XDA thread- https://forum.xda-developers.com/mi-a1/development/rom-tissot-stock-oreo-8-0-rooted-t3735760.
I'll be happy if this was helpful.
Click to expand...
Click to collapse
Great stuff thanks.
sipollo said:
Without reason? Probably THIS is the reason. I think your problem is related to data partition and a flash with Miflash can't help you. Only a factory reset can solve this.
Click to expand...
Click to collapse
There was another thread where someone proceeded to soft brick his device after downloading a file despite having low available storage.
barrack1 said:
There was another thread where someone proceeded to soft brick his device after downloading a file despite having low available storage.
Click to expand...
Click to collapse
Thank you for the help, there seems just no way to save user data, factory reset is the only option.
Shashankjindal said:
Does it work in locked bootloader? Btw thanks for the reply.
Click to expand...
Click to collapse
works