My tablet has somehow become “write protected”. I can install and remove apps but when I restart it revert to how the tablet looked 1 month ago.
Even if I do a “Factory data reset”. It just reboot into the old “image”. I am going slightly mad over this.
I no longer can enter Recovery. I get “ Secure Boot: image SOS checksum fail!”
I have tried to write a new recovery(dd if=/sdcard/recovery-thor2002ro-rev1.*.img of=/dev/block/mmcblk0p1) but still same issue.
Anyway, all I would like is to have a working recovery installed again. But how ??
Update: I have also tried to nvflash it but I get "Formatting partition 2 BCT please wait.. FAILED!"
Update2: /dev/block/mmcblk0p8 /data ext4 ro,nosuid,nodev,noatime,nodiratime,user_xattr,acl,barrier=1,data=ordered,noauto_da_alloc 0 0
Should that not be RW ??
I have an Acer 500 running 4.0.3/2.6.39.4+
Image: Acer_AV041_A500_RV03RC01_WW_GEN1 Build: Lightspeed_4.8
magiske said:
My tablet has somehow become “write protected”. I can install and remove apps but when I restart it revert to how the tablet looked 1 month ago.
Even if I do a “Factory data reset”. It just reboot into the old “image”. I am going slightly mad over this.
I no longer can enter Recovery. I get “ Secure Boot: image SOS checksum fail!”
I have tried to write a new recovery(dd if=/sdcard/recovery-thor2002ro-rev1.*.img of=/dev/block/mmcblk0p1) but still same issue.
Anyway, all I would like is to have a working recovery installed again. But how ??
Update: I have also tried to nvflash it but I get "Formatting partition 2 BCT please wait.. FAILED!"
Update2: /dev/block/mmcblk0p8 /data ext4 ro,nosuid,nodev,noatime,nodiratime,user_xattr,acl,barrier=1,data=ordered,noauto_da_alloc 0 0
Should that not be RW ??
I have an Acer 500 running 4.0.3/2.6.39.4+
Image: Acer_AV041_A500_RV03RC01_WW_GEN1 Build: Lightspeed_4.8
Click to expand...
Click to collapse
hello i have exactly the same issue
have you found a solution?
thks
U guys will need to rollback to hc and nvFlash from there....using timmydean v4! It will give u root and cwm.
Actually, I've just rolled back myself with it......it completely wipes yr tab and u will need yr cpuid
After u get the big white PASS, put yr tab in apex mode and nvflash the BL and recovery again
Sent from my A500 using Tapatalk 2
dibb_nz said:
U guys will need to rollback to hc and nvFlash from there....using timmydean v4! It will give u root and cwm.
Actually, I've just rolled back myself with it......it completely wipes yr tab and u will need yr cpuid
After u get the big white PASS, put yr tab in apex mode and nvflash the BL and recovery again
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
ok thanks to take a look on my problem!
So i have try your suggest! I have read the pdf include . Run DotNEtDetector, retrieve my serial. The tools detect my acer and display my actuel version (Flexreaper) but for new image version I have N/A in red and the next button is dimmed!
What can I do?
Thanks
Run it again
Sent from my GT-I9300 using Tapatalk 2
---------- Post added at 09:13 AM ---------- Previous post was at 09:07 AM ----------
Oops....run again but this time do not connect yr sub cable till the euu gives u the ok to do so....and the steps for manual apex mode....sorry I short on time at mo...see any of my las t posts for more info
Sent from my GT-I9300 using Tapatalk 2
SO I have try to run it.................so many time
With 3 differents PC.(XP ans 7)
I had wait until euu said me that it don't detect my ACER.
Start in APX mode manually
plug USB
ICONIA detected
enter my CPUID
click next
Iconia vibrate and display entering ACER download mode
and EEU display me "sorry update failed Please follow instruction......." (french translation)
SO what can i do?
gerardpuducul said:
SO I have try to run it.................so many time
With 3 differents PC.(XP ans 7)
I had wait until euu said me that it don't detect my ACER.
Start in APX mode manually
plug USB
ICONIA detected
enter my CPUID
click next
Iconia vibrate and display entering ACER download mode
and EEU display me "sorry update failed Please follow instruction......." (french translation)
SO what can i do?
Click to expand...
Click to collapse
Oh dear, this is not good, is your tab under warranty???
Sent from my GT-I9300 using Tapatalk 2
Have look at this thread
Posts 5, 8, and 9 if none of these solutions work, then
your tabs motherboard may be faulty, and will need
replacement....
http://forum.xda-developers.com/showthread.php?t=1846616
dibb_nz said:
Oh dear, this is not good, is your tab under warranty???
Sent from my GT-I9300 using Tapatalk 2
Have look at this thread
Posts 5, 8, and 9 if none of these solutions work, then
your tabs motherboard may be faulty, and will need
replacement....
http://forum.xda-developers.com/showthread.php?t=1846616
Click to expand...
Click to collapse
Oh no please don't said that!
I just want to remind that my ACER is FULLY working!
I can enter in bootloader , revovery without problem! I can launch my ROM and use it. I can install application without problem and use it. But when i reboot all modification are gone. Installed application are gone ,Can install new recovery or ROM.
This problem has arrived one day without doing nothing special ( no recovery/bootloader/ROM flash). Maybe an apk install or a battery low. But nothing that can be consider as "Dangerous"
Maybe a detail but have on ACER A501.
Thanks
Its my experience that when things "just happen one day" after doing nothing dangerous .... then it points to a hardware failure and this is especially so, if the EUU update says "update failed".....
which 501 rom are u currently using?
are you rooted?
have you tried reflashing the rom?
what happens when you use pwr and vol up buttons? -
if you have the v8 bootloader -can u access fastboot???
dibb_nz said:
Its my experience that when things "just happen one day" after doing nothing dangerous .... then it points to a hardware failure and this is especially so, if the EUU update says "update failed".....
Click to expand...
Click to collapse
OH NO !!!! PLEASE!!!:crying::crying::crying:
which 501 rom are u currently using? ICS FLEXREAPER
are you rooted? YES (include in ICS FLEXREAPER)
have you tried reflashing the rom? Yes. I push Power + vol up -> enter into TWRP recovery -> Wipe System/Data/cache/etc- > Try to flash Thor JB 15. Installation seems OK. Reboot and still in FLEXREAPER
what happens when you use pwr and vol up buttons? - I go into TWRP recovery
if you have the v8 bootloader -can u access fastboot??? Yes i can select fastboot but the tabs seems doing nothing. What is exactly fastboot?
Thanks again
fastboot is the easiest way of doing things.....u must connect yr tab to yr PC then open a command prompt from the fastboot folder....just like using adb.....if u aren't sure how to use it, then it may be best to use another method......
you can reflash the v8 bootloader again but please flash cwm 1.7.3 recovery....until we get u fixed....
But first backup yr stuff, to yr PC.
2nd be sure you have yr cpuid/sbk....Don't attempt to reflash anything till you've done this.....its very important....
trying to flash thors rom has screwed yr system.....it doesn't work well with the v8 bootloader.....so we need to Wipe and fully format yr tab....
from yr tab go.into settings>backup & restore and select "Factory Reset".
Then do it again....
next reflash the v8 bootloader and cwm 1.7.3....
Go into recovery, and format /data, /cache and /flexrom partitions.
then flash a V8 COMPATIBLE rom
go back into the wipe menu and do another full wipe.
reboot.....cross yr fingers and pray to the Acer gods!!!
Just a note....when flashing a rom....be sure to read the installation instructions very carefully....which bootloader u need and full wipes and formats are required for first time installs....the tiniest piece of leftover data can really corrupt things.....
Sent from my GT-I9300 using Tapatalk 2
fastboot is the easiest way of doing things.....u must connect yr tab to yr PC then open a command prompt from the fastboot folder....just like using adb.....if u aren't sure how to use it, then it may be best to use another method......
Click to expand...
Click to collapse
I had try a little bit with fastboot. When i launch fastboot from bootloader, my tabs is recognize by the PC to an ACER Fast boot device. But when I try to list device with command "fastboot devices", the PC detect nothing. I had a only "?" on the prompt
you can reflash the v8 bootloader again but please flash cwm 1.7.3 recovery....until we get u fixed....
Click to expand...
Click to collapse
I try that with a lot of different tools but no success
But first backup yr stuff, to yr PC.
2nd be sure you have yr cpuid/sbk....Don't attempt to reflash anything till you've done this.....its very important....
Click to expand...
Click to collapse
Don't worry i had save all my cpuid/sbk long ago
trying to flash thors rom has screwed yr system.....it doesn't work well with the v8 bootloader.....so we need to Wipe and fully format yr tab....
from yr tab go.into settings>backup & restore and select "Factory Reset".
Then do it again....
Click to expand...
Click to collapse
Trying to Factory Reset few time. Everytime the process seems finishing successfully , the tabs reboot, but i am still with all my settings
next reflash the v8 bootloader and cwm 1.7.3....
Click to expand...
Click to collapse
I try !! i promisse! AfterOTA, BlacktThund3r, Bad sector...........
take a look of this file which is a resume of my attempt :
https://docs.google.com/document/d/1d9ASpp1AFtdKTRA5zxfD2bQuHAwMA4CKGb18XhcXnWM/edit
Go into recovery, and format /data, /cache and /flexrom partitions.
Click to expand...
Click to collapse
Everything I do withmy TWRP recovery seems having no effect. the recovery said ok after each wipe but when i reboot i am still with my flexreaper.
then flash a V8 COMPATIBLE rom
go back into the wipe menu and do another full wipe.
reboot.....cross yr fingers and pray to the Acer gods!!!
Just a note....when flashing a rom....be sure to read the installation instructions very carefully....which bootloader u need and full wipes and formats are required for first time installs....the tiniest piece of leftover data can really corrupt things.....
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I dream to do that
gerardpuducul said:
I had try a little bit with fastboot. When i launch fastboot from bootloader, my tabs is recognize by the PC to an ACER Fast boot device. But when I try to list device with command "fastboot devices", the PC detect nothing. I had a only "?" on the prompt
Click to expand...
Click to collapse
Try this first.....
Yes that's correct, seeing "?" is Good!
Now type in this
fastboot erase usersdata
fastboot erase cache
fastboot reboot
Trying to Factory Reset few time. Everytime the process seems finishing successfully , the tabs reboot, but i am still with all my settings
Click to expand...
Click to collapse
Everything I do withmy TWRP recovery seems having no effect. the recovery said ok after each wipe but when i reboot i am still with my flexreaper
Click to expand...
Click to collapse
Yes you will be....it won't affect your rom....it takes you back to how yr tab was when u first installed flexreaper..
It does not take u back to factory stock like itwas when u first bought yr tab....unfortunately....
The screenshots show the ebt error and partition errors which timmydeans v4 usually fixes
I'm sorry....I cannot suggest anything else....your issue is beyond my skill level!!!
But I will try and get someone else to help u.....
dibb_nz said:
Try this first.....
Yes that's correct, seeing "?" is Good!
Now type in this
fastboot erase usersdata
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
fastboot erase userdata (and not fastboot erase usersdata I have seen your trap :cyclops
Code:
C:\ACER\adt-bundle-windows-x86_64\adt-bundle-windows\sdk\platform-tools>fastboot erase userdata
erasing 'userdata'...
OKAY [ 1.769s]
finished. total time: 1.770s
fastboot erase cache
Code:
C:\ACER\adt-bundle-windows-x86_64\adt-bundle-windows\sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.996s]
finished. total time: 0.997s
fastboot reboot
reboot and still under flexreaper with all my settings !!!:crying:
I had also try
fastboot -w
Code:
C:\Users\nxp10261\Documents\ACER\adt-bundle-windows-x86_64\adt-bundle-windows\sdk\platform-tools>fastboot -w
erasing 'userdata'...
OKAY [ 1.781s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type α ☺ not supported.
OKAY [ 0.797s]
erasing 'cache'...
OKAY [ 0.991s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type α ☺ not supported.
OKAY [ 0.796s]
finished. total time: 4.368s
why i have File system type α ☺ not supported???
I'm sorry....I cannot suggest anything else....your issue is beyond my skill level!!!
But I will try and get someone else to help u.....
Click to expand...
Click to collapse
Will I meet ACER A501 Master?:highfive:
Hey there,
Dibbs asked me to chime in here. So not sure what exactly I can do to help.
First thing, when dealing with Fastboot and Adb, it helps to have a good USB cable. Not one of those cheap things that came with a camera or printer.
I'm not saying go out and buy some expensive cable, what I say, is if you have somebody with an HTC cable, borrow it.
Also, if it applies, connect it to the mainboard, not one of the USB ports on the front of a desktop pc.
These are things I have noticed in the past year.
Next, here is a link to an app that sets your partitions back on the a501. No, I haven't used it yet. No need to. However, it has 2 batch files.
http://d-h.st/iQX
501a and 501b
Now, granted I have not used this, however, the partition tables and BCT seem sound. My guess, is that if rearranges your partitions to correct order, and perhaps installs V8 bootloader.
So you are welcome to try it. Can't hurt.
MD
And also, just to bring me up to date, are you on the V8 bootloader?
Before you do anything else.
MD
gerardpuducul said:
fastboot erase userdata (and not fastboot erase usersdata I have seen your trap :cyclops
Code:
C:\ACER\adt-bundle-windows-x86_64\adt-bundle-windows\sdk\platform-tools>fastboot erase userdata
erasing 'userdata'...
OKAY [ 1.769s]
finished. total time: 1.770s
fastboot erase cache
Code:
C:\ACER\adt-bundle-windows-x86_64\adt-bundle-windows\sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.996s]
finished. total time: 0.997s
fastboot reboot
reboot and still under flexreaper with all my settings !!!:crying:
I had also try
fastboot -w
Code:
C:\Users\nxp10261\Documents\ACER\adt-bundle-windows-x86_64\adt-bundle-windows\sdk\platform-tools>fastboot -w
erasing 'userdata'...
OKAY [ 1.781s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type α ☺ not supported.
OKAY [ 0.797s]
erasing 'cache'...
OKAY [ 0.991s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type α ☺ not supported.
OKAY [ 0.796s]
finished. total time: 4.368s
why i have File system type α ☺ not supported???
Will I meet ACER A501 Master?:highfive:
Click to expand...
Click to collapse
sorry for my spelling error...'trap'
YES YOU WILL ALWAYS be returned to flexreaper UNTIL you flash a new rom, its just the way it works!!!! BUT having all your settings still is not what should happen
I've asked the acer a501 master to take a look for you....please be patient...he will be along as soon as he possibly can, ok?
Moscow Desire said:
Hey there,
Dibbs asked me to chime in here. So not sure what exactly I can do to help.
First thing, when dealing with Fastboot and Adb, it helps to have a good USB cable. Not one of those cheap things that came with a camera or printer.
I'm not saying go out and buy some expensive cable, what I say, is if you have somebody with an HTC cable, borrow it.
Also, if it applies, connect it to the mainboard, not one of the USB ports on the front of a desktop pc.
These are things I have noticed in the past year.
Next, here is a link to an app that sets your partitions back on the a501. No, I haven't used it yet. No need to. However, it has 2 batch files.
http://d-h.st/iQX
501a and 501b
Now, granted I have not used this, however, the partition tables and BCT seem sound. My guess, is that if rearranges your partitions to correct order, and perhaps installs V8 bootloader.
So you are welcome to try it. Can't hurt.
MD
Click to expand...
Click to collapse
Hi Moscow desire and thanks to take a look on my problem.
First thing concerning the cable : I had try with ACER micro usb cable and with another micro usb using in my work(I flash Android device with it)
So a quick resume of my context:
I have a FULLY WORKING A501 with
bootloader Skrilax V8
twrp 2.1.3
FLEXREAPER-ReliX
fastboot is working
I can enter into bootloader
I can enter into recovery
I can launch my ROM FLEXREAPER-ReliX
but every modification that i try to apply to my tab has no effect after reboot
- reset factory : process seems ok but when i reboot i have still all my settings
- install new application : application working but after reboot application has disappear
- try to flash new ROM : enter into recovery/ select zip THOR ROM/Aruma installer process and said successful but when i reboot I am still under FLEXREAPER-ReliX
- try to reflash bootloader V8 : Failed with AfterOTA, thunderB3rd
- try to fix Partition table with Badsector : Failed
(all screenshot here https://docs.google.com/document/d/1d9ASpp1AFtdKTRA5zxfD2bQuHAwMA4CKGb18XhcXnWM/edit)
So now i try your Babsector :
the tabs said :
Code:
Entering Acer Download Mode
but process failed :
Code:
H:\ACER\BadSector\Image>"a501 A.bat"
****************************************************************
* Before executing, be sure to delete recovery-from-boot.p *
* from /system to ensure recovery will stick *
****************************************************************
****************************************
* Reboot your tablet into APX mode *
****************************************
Generate your SBK with your CPUID from here :
http://vache-android.com/v1/index.php?site=sbk
Enter your SBK:0xA78B1E00 0xBB9D0301 0xFBD7E703 0x00022103
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x038061874100a497
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714409/714409 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: APP
creating partition: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. FAILED!
command failure: create failed (bad data)
bootloader status: partition table is required for this command (code: 8) messag
e: nverror:0x4 (0x4) flags: 0
Press any key to continue . . .
Yeah, sounds like corrupted data sectors on the BCT partition. Not sure if it's recoverable. Could be a physically bad sector in the emmc chip.
I don't mind pitching in, but, I have a busy schedule the next couple days, so won't be able to help you much till the weekend.
There's another app called "badsector". It's in one of the posts in either General, or Q&A. Never used it,m but operates on the same principal as babsector. If I'm not mistaken, might fix your issue.
Here is some info on your issue. This is pretty much the problem you have.
http://forum.xda-developers.com/showthread.php?t=1691729&page=3
You may want to send a PM to Yaworsky in that thread, He may be able to help you out a little more than I can.
MD
Moscow Desire said:
Yeah, sounds like corrupted data sectors on the BCT partition. Not sure if it's recoverable. Could be a physically bad sector in the emmc chip.
I don't mind pitching in, but, I have a busy schedule the next couple days, so won't be able to help you much till the weekend.
Click to expand...
Click to collapse
No problem!! I am with this issue since 1 month now so i can live with it few days more! :good:
There's another app called "badsector". It's in one of the posts in either General, or Q&A. Never used it,m but operates on the same principal as babsector. If I'm not mistaken, might fix your issue.
Click to expand...
Click to collapse
I had already try badsector and the result is the same!! ( see the summary of my try https://docs.google.com/document/d/1d9ASpp1AFtdKTRA5zxfD2bQuHAwMA4CKGb18XhcXnWM/)
Here is some info on your issue. This is pretty much the problem you have.
http://forum.xda-developers.com/showthread.php?t=1691729&page=3
Click to expand...
Click to collapse
I had try to find faulty sector but when i launch
Code:
nvflash --rawdevicewrite 0 1664 mmcblk0_start.img --bl bootloader.bin --sbk 0xA78B1E00 0xBB9D0301 0xFBD7E703 0x00022103 --go
I had
Code:
C:\ACER\root-3.2.1-V4\root-3.2.1\Image>nvflash --rawdev
icewrite 0 1664 mmcblk0_start.img --bl bootloader.bin --sbk 0xA78B1E00 0xBB9D030
1 0xFBD7E703 0x00022103 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x038061874100a497
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
download command failed NvError 0x120002
command failure: bootloader download failed (bad data)
bootloader status: Bct file not found (code: 21) message: flags: 1073840124
You may want to send a PM to Yaworsky in that thread, He may be able to help you out a little more than I can.
MD
Click to expand...
Click to collapse
I had sent him a message
PS ; Just one more thing ;
I had try to use fastboot
so I had launch
Code:
>fastboot boot recovery_thor1.7.3.img
and successfully reboot into CMW recovery but the problem is still there!!:crying::crying::crying:
Every modification that I with CMW (format/reset/install recovery/ROM) said ok at the end of process but dissappear when i reboot!!!:crying::crying::crying:
Hello,
I have a Mi A1 since one week and I have already a large problem.
The problem began with a basic crash on an app (Facebook). The phone didn't respond and I turned off the phone.
When I turned on, the phone was stuck on the boot image (White screen with Mi Logo and Google colors). I tried to turn off and on several times but it didn't work.
I opened the phone and disconnected the battery but always the same problem.
Then, I booted the phone in fastboot and unlocked it via the command fastboot oem unlock. Then I tried to flash the stock ROM via fastboot. I choosed this version : Android 7.1.2 Nougat (N2G47H.7.12.7) because I had the last update (from : https://xiaomifirmware.com/roms/download-official-roms-xiaomi-mi-a1/).
Immediately i have this error :
Code:
fastboot flash modem_a C:\Users\Lau\Desktop\tissot_images_7.12.7_7.1\images\modem.img ||
target reported max download size of 536870912 bytes
sending 'modem_a' (86016 KB)...
OKAY [ 2.466s]
writing 'modem_a'...
FAILED (remote: flash write failure)
finished. total time: 2.499s
"Flash modem_a error"
I tried to flash with Miflash tool 2017.7.20 but I have the same message, Flash modem_a error.
I also tried to boot the phone in EDL Mode with fastboot_edl, the phone reboot, I have a message your device software cannot be checked for corruption and then the boot screen (with the messsage "Unlocked") and after 30 seconds, I have the black screen with the droid and "No command" (https://scache.vzw.com/kb/images/google/pixel/android_system_recovery_no_command.jpg )
Someone should have an idea to restore the phone ?!
Thanks a lot !
That screen with "No command" is usually related to the recovery. If I remember well, once in that screen, you have to press and hold power button for few seconds then press and release volume up button to enter in recovery. By reading your post I can see you didn't even try the most easy thing: A factory Reset! Try to wipe data from recovery if you can enter in it.
The modem error could be related at the fact that you're flashing a firmware that is not global or for your country. Try to change firmware version and make sure it is the right firmware region.
Inviato dal mio G8141 utilizzando Tapatalk
Thank for the quick answer.
I thinked to the recovery but I didn't know how to acces. With your help, I found and I made a wipe data. It made 5 minutes I have the message Formatting /data.... It seems too long... :/
EDIT : I stopped the wiping, it's seems it was block.
When you spoke of an other firmware, do have you a link ? Here is the information of my phone
Code:
xiaomi/tissot/tissot_sprout
71.2/N2G47H/7.12.19
This is a link to the October release of the Rom
https://androidfilehost.com/?fid=745849072291684522
This is a guide of how to flash it with Mi Flash Tool
https://forum.xda-developers.com/mi-a1/how-to/rom-factory-images-t3688548
If you are not able to flash with Mi Flash tool, try this guide to Flash manually via fastboot.
Once in fastboot (i suggest you to use the official one included in Android SDK becouse are the most updated ones and don't use some other installer like minimal. Add installer for Windows) follow this guide to Flash firmware images manually. It's for nexuses but the fastboot commands are universal
https://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
Inviato dal mio G8141 utilizzando Tapatalk
Thank you for the link, that was I made.
I tried to flash manually the ROM with fastboot and I found a clue, the filesystem seems not normal...
I have this message :
C:\adb>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
FAILED (remote: Partition table doesn't exist)
finished. total time: 0.009s
EDIT : And I have the last version of fastboot/adb from there : https://developer.android.com/studio/releases/platform-tools.html
lolo1410 said:
Thank you for the link, that was I made.
I tried to flash manually the ROM with fastboot and I found a clue, the filesystem seems not normal...
I have this message :
C:\adb>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
FAILED (remote: Partition table doesn't exist)
finished. total time: 0.009s
EDIT : And I have the last version of fastboot/adb from there : https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
You must flash to system_a or system_b, "system" partition really doesn't exist.
Indeed, it's work now, it's flashing !
I noticed that for TWRP, there is also a "slot A" and "slot B". Is it new in Android ? Is there 2 kind of system ?
EDIT :
Unfortunately, it didn't work...
I had this message :
C:\adb_new>fastboot flash system_a system.img
target reported max download size of 536870912 bytes
sending sparse 'system_a' 1/6 (522959 KB)...
OKAY [ 15.867s]
writing 'system_a' 1/6...
FAILED (remote: flash write failure)
finished. total time: 15.898s
And here is the log for Miflash :
Code:
[16:52:10 28ba25530704]:MiFlash 2017.7.20.0
[16:52:10 28ba25530704]:image path:C:\Users\Lau\Downloads\tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf\tissot_images_7.12.19_7.1
[16:52:10 28ba25530704]:env android path:"C:\Users\Lau\Desktop\miflash\Source\ThirdParty\Google\Android"
[16:52:10 28ba25530704]:script :C:\Users\Lau\Downloads\tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf\tissot_images_7.12.19_7.1\flash_all_except_storage.bat
[16:52:10 28ba25530704]:Physical Memory Usage:1355776 Byte
[16:52:10 28ba25530704]:$fastboot -s 28ba25530704 getvar product 2>&1 | findstr /r /c:"^product: *tissot" ||
[16:52:10 28ba25530704]:product: tissot
[16:52:10 28ba25530704]:$fastboot -s 28ba25530704 oem unlock ||
[16:52:11 28ba25530704]:...
[16:52:11 28ba25530704]:$fastboot -s 28ba25530704 flash modem_a C:\Users\Lau\Downloads\tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf\tissot_images_7.12.19_7.1\images\modem.img ||
[16:52:11 28ba25530704]:(bootloader) Device already : unlocked!
[16:52:11 28ba25530704]:eek:KAY [ 0.030s]
[16:52:11 28ba25530704]:finished. total time: 0.030s
[16:52:13 28ba25530704]:target reported max download size of 536870912 bytes
[16:52:13 28ba25530704]:sending 'modem_a' (86016 KB)...
[16:52:13 28ba25530704]:error:"Flash modem_a error"
[16:52:13 28ba25530704]:"Flash modem_a error"
[16:52:13 28ba25530704]:error:"Flash modem_a error"
[16:52:13 28ba25530704]:process exit.
[16:52:13 28ba25530704]:flashSuccess False
[16:52:13 28ba25530704]:isFactory False CheckCPUID False
[16:52:13 28ba25530704]:before:flashSuccess is False set IsUpdate:True set IsDone True
[16:52:13 28ba25530704]:after:flashSuccess is False set IsUpdate:false set IsDone true
Can you boot into TWRP (use version 3.1.1-0 or 3.1.1-1 "fastboot boot twrp.img")? Do you see /data partition?
Yes I can boot into but I can't install it. Before I tried to flash manually, I was able to unlock the data partition but not anymore (Error : E: Decrypt took too long, killing process - Failed to decrypt data)
I have an access with adb shell.
Some people had luck with flashing persist.img from August update, you might try that as well. There is also a chance that your flash memory is damaged and you will need to visit a service center.
Okay try this.
Download the latest build (android n) from mi firmwares official page.
Unzip the file (http://en.miui.com/forum.php?mod=viewthread&tid=1415168&extra=page=1&mobile=2)
Download miflashtool (http://en.miui.com/thread-807252-1-1.html)- guide & tool.
Past the path in the tool.
Click refresh
Click flash
Boom your good.
Make sure to select clean flash and lock.
ADB and fastboot should be installed.
_mysiak_ said:
Some people had luck with flashing persist.img from August update, you might try that as well. There is also a chance that your flash memory is damaged and you will need to visit a service center.
Click to expand...
Click to collapse
I flashed "persist.img" succesfully but always the same problem, stucked on Boot...
zeyaan said:
Okay try this.
Download the latest build (android n) from mi firmwares official page.
Unzip the file (http://en.miui.com/forum.php?mod=viewthread&tid=1415168&extra=page=1&mobile=2)
Download miflashtool (http://en.miui.com/thread-807252-1-1.html)- guide & tool.
Past the path in the tool.
Click refresh
Click flash
Boom your good.
Make sure to select clean flash and lock.
ADB and fastboot should be installed.
Click to expand...
Click to collapse
I already tried several times but I have always errors (See log of previously post). With Miflash, I succeeded to flash the 2 boot et 2 system but phone is always blocked.
I tried to wipe via TWRP but it blocks on "Formatting Data using make_ext4fs...".
I think I'm good to send it at a service center...
There's a TWRP backup of first beta build oreo.Try restoring it.
Same Problem.
inally he managed to flash the ROM action, thank you very much to everyone for your patience and help, especially PALMATRON and fosco_
He used the tutorial of this link: https://xiaomifirmware.com/roms/down...-xiaomi-mi-a1/
1. Tools Download r26 for Windows.
2. Unzipped the instruments on disk C of my computer.
3. Unzipped the files of the last ROM available for the Xiaomi Mi A1 in the folder C: \ Tools so that the Images folder and the flashing scripts that come with the ROM are included in it.
4. Then double click on flash_all.bat to delete everything and just leave the boot loader open.
5. Automatically start flashing and take about 10-15 minutes and voila!
https://uploads.tapatalk-cdn.com/20171123/37d3867bf5d0fb7967a03a05869914ae.jpg
Try do with clean and lock or just clean i was have the same problem and i fix this only with miflash and after when my mi a1 restarts on boot i copy with terminal persist.img
thanks a lot
Saved my life, thanks. The rom on this link works PERFECTLY - my Mi A1 was stuck on botlooping after a fail tentative to root it.
XDVRMX said:
This is a link to the October release of the Rom
https://androidfilehost.com/?fid=745849072291684522
This is a guide of how to flash it with Mi Flash Tool
https://forum.xda-developers.com/mi-a1/how-to/rom-factory-images-t3688548
If you are not able to flash with Mi Flash tool, try this guide to Flash manually via fastboot.
Once in fastboot (i suggest you to use the official one included in Android SDK becouse are the most updated ones and don't use some other installer like minimal. Add installer for Windows) follow this guide to Flash firmware images manually. It's for nexuses but the fastboot commands are universal
https://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
Inviato dal mio G8141 utilizzando Tapatalk
Click to expand...
Click to collapse
Dear mates,
2 days I am trying to find answer to my problem and finally decided to start new post on exact issue I faced.
device is MI A1 with android one and current version on it was according to picture attached from recovery was tissot_10.0.19. when I took this phone from my mate to fix it was not booting with first MIUI page stacked on the screen.
fastboot output were saying:
--------------------------------------------------
C:\WINDOWS\system32>fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.058s]
Finished. Total time: 0.059s
------------------------------------------------
getvar is attached
i tried to flash using miflash ver 2020.3.14 in fastboot mode but it was not successful because of locked bootloader and "locked everything".
i tried to load OTA updates using embedded recovery, but not successful, screenshot attached.
i got the error " E:Error in sideload/package.zip (Status 1)
and all time repeating error : fail to clear BCB message fail to fsync /dev/block/bootdevice/by-name/misc: operation not permitted
any option from recovery meny does not provide any result. wipe data/factory reset were stucking with erasing data notification for hours without result.
at the end i cam to EDL mode by shorting hardware test point. quallcomm driver was ok at computer Device Manager, miflash and QFIL are identifying device on com port 20 but flashing does not finish successfully , it stop at 12 sec in Miflash, and at 1,46% in QFIL. verbose log for QFIL is also attached .
main concern in QFIL log file is "IGNORING UNRECOGNIZED Attribute" stats for attributes from TARGET. my impression is phone is asking to send data in rawmode <?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="true" /></data> and Qfil is ignoring this attribute. as the result file copy finish with error
23:37:45: INFO: TARGET SAID: 'Finished sector address 131072'
23:37:45: DEBUG: XML FILE (92 bytes): CharsInBuffer=92-92=0
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?><data><response value="NAK" rawmode="false" /></data>
and we have repeating replies from Target as this : <?xml version="1.0" encoding="UTF-8" ?><data><log value="0 bytes received, 1048576 sectors more to go" /></data>
sorry for long explanation, the goal is to share as clear picture of the situation as possible.
i tried the same procedure with QFIL on other computer and had the same result.
now phone is in all time EDL mode. i suppose it is because i checked "erase all before configuration" option in QFIL firehose configurations.
Thanks to everyone in advance for your time and help if you could provide your suggestions how to solve the issue.
I can't solve this problem for more than 4 days and I have android 8.1 and it gives the same problem, you can do the easiest thing, as they say, edl test point, you can try but I don't recommend how you can mess up something if you were able to solve the problem, please tell me how to solve it
Try to flash stock rom via MiFlash Tool. Make sure to see COM port on MiFlash tool (press refresh to detect com port). Then after you see COM port. Flash it with "clean all" option(on the bottom). If you connect to EDL mode properly, process will be finished succesfully. But if you get some "Invalid argument, unknown error" errors, you are not connected to edl mode.
try to enter edl mode with this code in fastboot
Code:
fastboot oem edl
If it give OKAY, then you are ready to flash with Miflash tool.
There is another way to flash img files with fastboot mode. If you dont success, write here.
atc mode is not worked and I don't want to enter the testpoint, how can I tell you and the loader is not open, so this is also not a small problem as you look at it, so if there are other ideas, please send them to me
PLEASEEEEE
Testpoint is a final way. even if you cant enter testpoint, you cant do more
ivomin said:
It's ALIVE!.
Just to update that after debugging the whole windows com stack I struck on a wall and it seems that windows 7 and 10 block something there (I manage to get out of the driver to win kernel on debug but then it fails and didn't had any more nerves to deal with and I'm not a windows guy myself).
So the only solution for low lvl writing is to use linux with point boot to EDL. It seems that for mi A1 even if Qualcomm's boot chain is broken (https://blog.quarkslab.com/analysis-of-qualcomm-secure-boot-chains.html) it should fall to EDL in most cases but in our phone (global version at least) it goes to diagnostic mode (not to be confused with Download mode) regardless of drivers in windows - this is hardwired in the chip. So under linux you should fall in to download mode with hardware short of motherboard points to fall in to the correct mode. You should forget about windows as it depends too much on the selected driver (yes you can manually change driver and fu** the whole chain of communication). You need to hardwarely go to Download mode. Don't believe what windows reports.
From there you can use QDL (check documentation on how to install (you'll also need to install gcc (ubuntu - apt get install gcc) https://github.com/96boards/documentation/blob/master/consumer/guides/qdl.md).
Then download a full firmware flash from xiaomi (that's for MiFlash) and use the files in the images folder for the command ( for instance to be more easy copy images folder to qdl folder and:
./qdl --debug --storage emmc --include 'images' 'images/prog_emmc_firehose_8953_ddr.mbn' 'images/rawprogram0.xml' 'images/patch0.xml')
This will fix the first part of the qualcomm bootchain from there you will have access to fastboot and then use all other tutorials concerning fixes from fastboot.
If enough ppl want it I'll write extended tutorial in the other section.
Click to expand...
Click to collapse
Try this. It should bring you to mostly original state and from there you can fastboot unlock and proceed with installing shrp or twrp.
I have a Redmi 7a brick, it has an unlocked bootloader, TWRP was flashed and Android 12 custom rom
At one point, unexpectedly during normal operation, the phone froze, an attempt to restart led to freezing on the Redmi splash screen, which later switched to Fastboot. When you try to start the recovery, it loads for about 20 minutes and responds very slowly to actions, in the mount column, the internal memory partition is 0MB, attempts to format / change the file system lead to a freeze, the phone is detected through the computer using fastboot, but any attempts to flash the recovery / system are not what they don’t lead to (writes that it’s successful, but in fact nothing), as they said on other forums and examples, this is the death of internal memory, but maybe there is an opportunity to fix it
Stimayk said:
I have a Redmi 7a brick, it has an unlocked bootloader, TWRP was flashed and Android 12 custom rom
At one point, unexpectedly during normal operation, the phone froze, an attempt to restart led to freezing on the Redmi splash screen, which later switched to Fastboot. When you try to start the recovery, it loads for about 20 minutes and responds very slowly to actions, in the mount column, the internal memory partition is 0MB, attempts to format / change the file system lead to a freeze, the phone is detected through the computer using fastboot, but any attempts to flash the recovery / system are not what they don’t lead to (writes that it’s successful, but in fact nothing), as they said on other forums and examples, this is the death of internal memory, but maybe there is an opportunity to fix it
Click to expand...
Click to collapse
Try to flash with original miui ROM.
itmasen1 said:
Try to flash with original miui ROM.
Click to expand...
Click to collapse
I tried but no changes are applied
UPD: I'm again try to flash original ROM and fastboot give a
Sending 'sec' (0 KB) OKAY [ 0.004s]
Writing 'sec' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
Flash sec error
How to fix it?
Stimayk said:
UPD: I'm again try to flash original ROM and fastboot give a
Sending 'sec' (0 KB) OKAY [ 0.004s]
Writing 'sec' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
Flash sec error
How to fix it?
Click to expand...
Click to collapse
in principle, there is a solution by going through EDL MODE . you have a chance to restore your phone,
do your research on the net about this method.