Hi guys.. what is the latest firmware for a510, n where can i get it?
Can suggest me the best build/firmware version? Im using 1.044 now.
Problems that im facing now :
-Shadowgun touchscreen unresponsiveness
-Browser sometimes goes all white when switching apps/tabs. Have to scroll back to the top for the page to show again
-sometimes the tab is laggy and slow
Edited:
I accidentally posted at the wrong section, can move it? Thanks!
Also good to know is where to get the updates....couldn't find any so far. I've noticed the following versions when looking at other threads:
Acer_AV041_A510_0.004.04_WW_GEN1
Acer_AV041_A510_0.039.00_WW_GEN1
Acer_AV041_A510_1.021.01_WW_GEN1
Acer_AV041_A510_1.029.00_WW_GEN1
Acer_AV041_A510_1.032.00_PA_CUS1
Acer_AV041_A510_1.033.00_PA_CA
Acer_AV041_A510_1.043.00_EMEA_DE
Acer_AV041_A510_1.044.00_WW_GEN1
Acer_AV041_A510_1.060.00_EMEA_CUS1
Acer_AV041_A510_1.072.00_EMEA_CUS1
Acer_AV041_A510_1.073.00_WW_GEN1
Acer_AV041_A510_1.076.00_WW_GEN1 (?)
Acer_AV041_A510_1.076.00_EMEA_DE
Acer_AV041_A510_1.076.00_PA_CUS1
Acer_AV041_A510_1.079.00_PA_CA
Acer_A510_AV041.RV34RC05_EMEA_DE (1.099.00)
But most downloads are from Russian or Chinese websites...
hel
how to install these files...i want to reset my recovery too...how to fully reformat all the partition..
guiburi said:
how to install these files...i want to reset my recovery too...how to fully reformat all the partition..
Click to expand...
Click to collapse
Explained in several of these forums, please use search.
1. how to install files (translated from one of the russian sites):
Code:
1. Download the firmware file and rename it to update.zip
2. Copy update.zip to the root of an external sdcard (on the tablet /mnt/external_sd/), make sure the sdcard is pre-formatted to FAT32.
3. Turn off the tablet, hold down both volume and minus (with two dots) and the power button and hold until you see the text in the upper left corner.
4. Will start flashing automatically, which will be accompanied by an animation on the screen.
5. After the firmware will automatically reboot and turn on the tablet in normal mode!
Whatever you do, you do at your own risk!
Do not forget to connect the charger! When flashing do not connect to your PC!
2. Reset recovery
You can do that by installing a new recovery. First find one that suites you, or find the stock recovery that came with your device. I don't have an A510, so I don't have any of these files
3. Format full partition
You can either do that from a recovery (like CWM) or by doing factory reset:
Hold Volume+ (one dot) and Poweron and immediately toggle your rotation switch. BEWARE: this will immediately start to reset your device to factory defaults!
I did a bunch of searching, but I just want to clarify having never done this before...
method 1 seems pretty simple and the way to go to wipe my tablet, but will it do the following?
-completely wipe my system partition. i will loose root (and any other messing around i did in there, including my failed attempts at cifs and openvpn, and any hosts file from ad block software)
-wipe my personal data partition (/mnt/sdcard)
-leave no trace of the million apps that i have uninstalled that still have a lingering file or two
any recommendation on firmware? im running 1.079_pa_ca right now. installing any of the above, will it still do OTA update back to that? or is it not recommended to mix language/region?
Rusty_Gunn said:
I did a bunch of searching, but I just want to clarify having never done this before...
method 1 seems pretty simple and the way to go to wipe my tablet, but will it do the following?
-completely wipe my system partition. i will loose root (and any other messing around i did in there, including my failed attempts at cifs and openvpn, and any hosts file from ad block software)
-wipe my personal data partition (/mnt/sdcard)
-leave no trace of the million apps that i have uninstalled that still have a lingering file or two
any recommendation on firmware? im running 1.079_pa_ca right now. installing any of the above, will it still do OTA update back to that? or is it not recommended to mix language/region?
Click to expand...
Click to collapse
Hi Rusty_Gun,
Rusty_Gunn said:
-completely wipe my system partition. i will loose root (and any other messing around i did in there, including my failed attempts at cifs and openvpn, and any hosts file from ad block software)
-wipe my personal data partition (/mnt/sdcard)
Click to expand...
Click to collapse
I am quite sure it will, although it depends on the update.zip. Some format /system and in a rare case I've seen it just copies stuff...If you extract the updater-script in the zipfile you can see and if you send it to us, we can tell you
Rusty_Gunn said:
-wipe my personal data partition (/mnt/sdcard)
Click to expand...
Click to collapse
No, I don't think I have seen official update.zip also wipe /data. Again can be checked from updater-script
Rusty_Gunn said:
-leave no trace of the million apps that i have uninstalled that still have a lingering file or two
Click to expand...
Click to collapse
Then make sure to factory reset after flashing the update.zip, only that way it will wipe everything
Rusty_Gunn said:
any recommendation on firmware? im running 1.079_pa_ca right now. installing any of the above, will it still do OTA update back to that? or is it not recommended to mix language/region?
Click to expand...
Click to collapse
No recommendation here... sorry, don't own the A510.
fastboot update
Hello,
I'm trying to install one of those stock firmware because my tab (a510) don't boot anymore, it stuck on "ICONIA TAB".
With stock reconevry it did not work, and with fastboot update i get this error:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot update
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I try all of them, same result.
any idea? please
LaMangouste said:
Hello,
I'm trying to install one of those stock firmware because my tab (a510) don't boot anymore, it stuck on "ICONIA TAB".
With stock reconevry it did not work, and with fastboot update i get this error:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot update
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I try all of them, same result.
any idea? please
Click to expand...
Click to collapse
Did you try a factory reset (Vol+ and Vol-, Poweron, and toggle rotate switch)?
And you really tried to enter recovery (Vol- + Poweron) and install update.zip (which is in the external sdcard)?
Fastboot update update.zip requires a different format of the update.zip so that won't work. The update.zip really needs to be installed by entering recovery.
Btw. I think it accesses the bit to install update.zip before it even loads the recovery, so it's probably part of the bootloader, not the recovery image.
Regards,
Nika.
nikagl said:
Did you try a factory reset (Vol+ and Vol-, Poweron, and toggle rotate switch)?
And you really tried to enter recovery (Vol- + Poweron) and install update.zip (which is in the external sdcard)?
Fastboot update update.zip requires a different format of the update.zip so that won't work. The update.zip really needs to be installed by entering recovery.
Btw. I think it accesses the bit to install update.zip before it even loads the recovery, so it's probably part of the bootloader, not the recovery image.
Regards,
Nika.
Click to expand...
Click to collapse
Thanks for reply,
I tried hard reste, i got an error... that's very strange.
And yes I really think i entered recovery, i put the update.zip on external sd and boot with vol- and power.
It write that it clear cache before sd update, and "Booting recovery kernel image".
But after that i see only a lying down android with a red triangle during 2 minutes, then reboot.
Is it a good idea to try flashing your cwm recovery and try with it?
ps: sorry for my bad english
LaMangouste said:
Thanks for reply,
I tried hard reste, i got an error... that's very strange.
And yes I really think i entered recovery, i put the update.zip on external sd and boot with vol- and power.
It write that it clear cache before sd update, and "Booting recovery kernel image".
But after that i see only a lying down android with a red triangle during 2 minutes, then reboot.
Is it a good idea to try flashing your cwm recovery and try with it?
ps: sorry for my bad english
Click to expand...
Click to collapse
Your English is fine, no worries
What error did you get after or during your hard reset?
For the update.zip, which firmware did you try and did you also try others? It looks like your update.zip is not recognized, it should try to install it already before it is booting the recovery kernel image (I think after cache). If you let me know which firmware you used I can check whether the update.zip is signed and correctly formed to be installed using stock recovery.
Although I do think the recovery should work I would use that as a last resort, and officially (if you can) I would advice to go to Acer or your supplier to get it fixed if we fail here. Installing the recovery may void warranty or they may complain and make it harder to fix your device. Also remember the recovery has not been tested much, and definitely not for installing new firmwares...
Regards,
Nika.
nikagl said:
Your English is fine, no worries
What error did you get after or during your hard reset?
For the update.zip, which firmware did you try and did you also try others? It looks like your update.zip is not recognized, it should try to install it already before it is booting the recovery kernel image (I think after cache). If you let me know which firmware you used I can check whether the update.zip is signed and correctly formed to be installed using stock recovery.
Although I do think the recovery should work I would use that as a last resort, and officially (if you can) I would advice to go to Acer or your supplier to get it fixed if we fail here. Installing the recovery may void warranty or they may complain and make it harder to fix your device. Also remember the recovery has not been tested much, and definitely not for installing new firmwares...
Regards,
Nika.
Click to expand...
Click to collapse
I tried hard reset again, and it worked! The error is gone, and my tab work again! Well, it's really weird.
But it does not explain why i can't install any the update.zip, i tried all the firmware from your post. (1.029.00 1.060.00 1.073.00 1.076.00)
By the way, i don't need to install it anymore...
Thanks for your help.
LaMangouste said:
I tried hard reset again, and it worked! The error is gone, and my tab work again! Well, it's really weird.
But it does not explain why i can't install any the update.zip, i tried all the firmware from your post. (1.029.00 1.060.00 1.073.00 1.076.00)
By the way, i don't need to install it anymore...
Thanks for your help.
Click to expand...
Click to collapse
Very good news. Just one more question: you have never tried to install any other recovery? And did you try rooting the device?
Regards,
Nika.
nikagl said:
Very good news. Just one more question: you have never tried to install any other recovery? And did you try rooting the device?
Regards,
Nika.
Click to expand...
Click to collapse
No, i did not install any recovery, i just unlock it. But yes, devive was root, it can be the cause?
LaMangouste said:
No, i did not install any recovery, i just unlock it. But yes, devive was root, it can be the cause?
Click to expand...
Click to collapse
I don't think root caused it, but I'm still trying to find a common denominator in the issues some people are having. What rooting method did you use? I have seen one root with a new boot image, but most roots are based on mempodroid exploit (which should be quite safe other than that it might be unavailable after an update)...
I used this method, i think it's safe. http://forum.xda-developers.com/showthread.php?t=1531646
LaMangouste said:
I used this method, i think it's safe. http://forum.xda-developers.com/showthread.php?t=1531646
Click to expand...
Click to collapse
That's the mempodroid exploit root method, so that should really be ok
nikagl said:
I don't think root caused it, but I'm still trying to find a common denominator in the issues some people are having. What rooting method did you use? I have seen one root with a new boot image, but most roots are based on mempodroid exploit (which should be quite safe other than that it might be unavailable after an update)...
Click to expand...
Click to collapse
I know why i update did not work, it's quite stupid but i forgot my external sd was ntfs formated, i think it must be fat32...
LaMangouste said:
I know why i update did not work, it's quite stupid but i forgot my external sd was ntfs formated, i think it must be fat32...
Click to expand...
Click to collapse
Yeah, it definitely needs to be FAT32 thanks for letting us know, next time i'll make sure to ask
ntfs support will be added when custom kernel begin to appear.
but for that, we will need a working recovery
nikagl said:
Explained in several of these forums, please use search.
1. how to install files (translated from one of the russian sites):
Code:
1. Download the firmware file and rename it to update.zip
2. Copy update.zip to the root of an external sdcard (on the tablet /mnt/external_sd/), make sure the sdcard is pre-formatted to FAT32.
3. Turn off the tablet, hold down both volume and minus (with two dots) and the power button and hold until you see the text in the upper left corner.
4. Will start flashing automatically, which will be accompanied by an animation on the screen.
5. After the firmware will automatically reboot and turn on the tablet in normal mode!
Whatever you do, you do at your own risk!
Do not forget to connect the charger! When flashing do not connect to your PC!
2. Reset recovery
You can do that by installing a new recovery. First find one that suites you, or find the stock recovery that came with your device. I don't have an A510, so I don't have any of these files
3. Format full partition
You can either do that from a recovery (like CWM) or by doing factory reset:
Hold Volume+ (one dot) and Poweron and immediately toggle your rotation switch. BEWARE: this will immediately start to reset your device to factory defaults!
Click to expand...
Click to collapse
I keep getting the dead droid with the red triangle. im trying to go back to 1060 because ever since the ota update my touch sensativity has been terrible. 1073 worked for me but the touch is just as bad. 1060 was the best but that zip image wont flash for me.
Related
Hi,
My SGT 7.7 seems brick after I took it out of my bag. It gets stuck and stays on the boot screen where says "Samsung Galaxy Tab 7.7" for a few seconds, and then just keep rebooting.
It is able to go into the Download Mode when I press "Power+Vol-", but no response when I press "Power+Vol+". I tried to flash all kinds of firmware with Odin, but nothing work.
I also tried to flash it with .pit, PDA, PHONE and CSC. I got this screen and then stopped and Odin says "Now Writing, Please wait about 2 minutes."
I appreciate your help!
same problem here, but caused from rom-manager! did nothing more than using the "reboot into recovery" option, i did NOT flash anything with rom-manager before!
download mode works, recovery works, but i can flash what i want, after turning the device on the "samsung 7.7" stays for about 30sec, then it reboots ad infinitum!
any ideas?
i'm within the one week were i can exchange the device without any problems, but i want to fix it myself if possible!
thx in advance!
TML1504 said:
same problem here, but caused from rom-manager! did nothing more than using the "reboot into recovery" option, i did NOT flash anything with rom-manager before!
download mode works, recovery works, but i can flash what i want, after turning the device on the "samsung 7.7" stays for about 30sec, then it reboots ad infinitum!
any ideas?
i'm within the one week were i can exchange the device without any problems, but i want to fix it myself if possible!
thx in advance!
Click to expand...
Click to collapse
I have seen similar symptoms on mine. it turned out to be corrupt /data filesystem. I had to use the sammy 3e recovery wipe data/factory reset option. And then reflash with odin.
(CWM could not fix this filesystem problem.)
(areyou sure rom manager is compatible with the different partitions on the 7.7)
Remember you will loose all user data !!!!!
davp said:
I have seen similar symptoms on mine. it turned out to be corrupt /data filesystem. I had to use the sammy 3e recovery wipe data/factory reset option. And then reflash with odin.
(CWM could not fix this filesystem problem.)
(areyou sure rom manager is compatible with the different partitions on the 7.7)
Remember you will loose all user data !!!!!
Click to expand...
Click to collapse
again thx,
but the problem is seems to be "deeper" than only a corrupt /data!
The tab doesnt boot further then "samsung 7.7", if data is corrupt then
at least android will load (bootanimation) and go into a bootloop in some stage!
Also, I didn't change or install or flash anything in rom-manager, I "only" used the reboot function!
After reflashing the device with repartition and HongKong.pit I think I messed up the partitions totally, so I would really need the PIT for 6810 (6800 has different partition layout) to repair this!
But as it seems no one has this PIT or is willing to provide it,
so I ordered an new tab which will arrive in the next hours, and return this one within the next days!
Where did you find the PIT file ? You may just destoried the partition. God bless you!
matth3w said:
Hi,
My SGT 7.7 seems brick after I took it out of my bag. It gets stuck and stays on the boot screen where says "Samsung Galaxy Tab 7.7" for a few seconds, and then just keep rebooting.
It is able to go into the Download Mode when I press "Power+Vol-", but no response when I press "Power+Vol+". I tried to flash all kinds of firmware with Odin, but nothing work.
Click to expand...
Click to collapse
I have a familiar problem....
I have not flashed or rooted my device - it is exactly how it came out of the box...
One morning while using it it froze - I did are reset by holding the power button down and then let it reboot but when it did it can not get past the "Samsung Galaxy Tab 7.7" screen.
Can get it into download mode, but if I go to recovery mode then all I get it a headline saying "Manual Mode" which grabs some manual .apk files and then just goes back into the boot mode with the "Samsung Galaxy Tab 7.7" screen.
Any ideas?
Had a Galaxy Tab Original and got the Galaxy SII and have mod them to death - just though for this one I would leave it original and enjoy the OTA updates as the were delievered - especially considering ICS in a matter of days
If you can boot into download mode you can call this a soft brick..
dont use ROM manager and install clockworkmod from that, incompatibility of cwm recovery will brick your phone..
Use odin only on PDA slots, you dont need repartition or pit files..it seems you got a corrupt recovery..
suwandiapr said:
Use odin only on PDA slots, you dont need repartition or pit files..it seems you got a corrupt recovery..
Click to expand...
Click to collapse
Suwandiapr - Thank you for this. When you say "Use odin only on PDA slots" you are suggesting that I will have to download and install a stock ROM aren't you?
Cheers (and again thank you)....
Aspi914 said:
Suwandiapr - Thank you for this. When you say "Use odin only on PDA slots" you are suggesting that I will have to download and install a stock ROM aren't you?
Cheers (and again thank you)....
Click to expand...
Click to collapse
yes, that is what he means.
Also, if you still have trouble after the first flash, you may need to go into samsung 3e recovery and do a data wipe/factory reset. Then flash again. Since these are non-wipe firmwares, simple flashing may not clear a corrupt filesystem.
Obviously you will lose all user data!
suwandiapr said:
If you can boot into download mode you can call this a soft brick..
dont use ROM manager and install clockworkmod from that, incompatibility of cwm recovery will brick your phone..
Use odin only on PDA slots, you dont need repartition or pit files..it seems you got a corrupt recovery..
Click to expand...
Click to collapse
thx, but as i said i DID NOT FLASH OR INSTALL ANYTHING with rom-manager, i only used the option "reboot into recovery"!
and i used odin to try to unbrick my device (i flashed a dozen roms as well as the sbl etc.), without any success. also, till now nobody has provided a 16GB PIT for 6810, therefore i returned the tab and grabbed a new one!
davp said:
Also, if you still have trouble after the first flash, you may need to go into samsung 3e recovery and do a data wipe/factory reset. Then flash again. Since these are non-wipe firmwares, simple flashing may not clear a corrupt filesystem!
Click to expand...
Click to collapse
Thank you Davp...
Ok...got the P6800ZSLA2 stock ROM and have managed to get it back...while I don't want to have to re-do all the data, I think I will take your advise and do a data wipe/reset.
Aspi914 said:
Suwandiapr - Thank you for this. When you say "Use odin only on PDA slots" you are suggesting that I will have to download and install a stock ROM aren't you?
Cheers (and again thank you)....
Click to expand...
Click to collapse
Yes you right, thats what i mean..
TML1504 said:
thx, but as i said i DID NOT FLASH OR INSTALL ANYTHING with rom-manager, i only used the option "reboot into recovery"!
and i used odin to try to unbrick my device (i flashed a dozen roms as well as the sbl etc.), without any success. also, till now nobody has provided a 16GB PIT for 6810, therefore i returned the tab and grabbed a new one!
Click to expand...
Click to collapse
Im sorry , my answer cannot solve your problem.. You say your device "stuck on Samsung logo" right? your recovery and download mode seem ok, from my experience its because /data corrupt or something crash on your filesystem..
If you can go to recovery menu, do factory reset,..
I cannot help you with pit.file coz i actually dont have the device right now..
Aspi914 said:
Thank you Davp...
Ok...got the P6800ZSLA2 stock ROM and have managed to get it back...while I don't want to have to re-do all the data, I think I will take your advise and do a data wipe/reset.
Click to expand...
Click to collapse
Good luck..
davp said:
I have seen similar symptoms on mine. it turned out to be corrupt /data filesystem. I had to use the sammy 3e recovery wipe data/factory reset option. And then reflash with odin.
Click to expand...
Click to collapse
I've experienced a similar problem with corrupt /data and couldn't overcome it.
How did you use Samsung recovery when you had CWM recovery flashed?
白い熊 said:
I've experienced a similar problem with corrupt /data and couldn't overcome it.
How did you use Samsung recovery when you had CWM recovery flashed?
Click to expand...
Click to collapse
You either get it from a full flash of stock firmware, or make your own tar with just recovery.img in it (extracted from stock). And flash with odin in the pda.
It is handy to be able to switch recoveries. CWM doesn't seem to match the 3e data wipe/factory reset.
The problem was:
I was playing a game, in the middle of it the Tab reset, I've never had it reset. Then it rebooted to the Samsung Tab 7.7 logo.
I thought, I'm lucky, made a CWM backup. So tried to restore the CWM backup. When the restore got to /data the tab rebooted again, i.e. something was messed with it.
So got stock firmware, flashed it from PC odin, flashed with success. But rebooted to the logo again.
Tried to get into the stock recovery, but it would only show "Updating..." something, I don't remember anymore, but the stock recovery wouldn't boot. Flashed it a couple of times, same result. Had to take the Tab back to the store...
Am kinda afraid to mess with it now, since I don't want it to happen.
So am wondering what to do if the same happens, or just forget CWM and flash stock recovery.img just to be safe?
I had similar issues after hard power-off [long hold power button]. Confirmed with adb into insecure cwm recovery that /data was corrupt. It explained why my restores stopped at /data.
Cwm data wipe, or format data did not help.
I flashed the stock 3e recovery.img in a tar with odin.
3e data wipe/factory reset. Reflash whole stock firmware with odin.
Check system boots ok.
Reflash cwm, then do restore ok.
I have seen stock 3e recovery fail to start properly. It seemed to be related to files/directories on the external sd card. It came up and said something like 'manual mode', 'updating'.
I tried clearing cache and hidden.
I know I deleted at least tmp_sec_fota directory off the external sd card, maybe someting to do with fota is upsetting our tabs from time to time.
Yep, exactly, that's it, it was "Manual mode" and "Updating", same symptoms, I couldn't get past it.
So what you're saying, I had a MicroSD in it, and that's why it was stuck at this? Not sure if I had an SD in it, but I flashed stock like three times, and then still couldn't enter 3e recovery, all the time had this "manual mode" come up...
Thanks for the guide of what you did.
Am downloading the latest Thai firmware now, to extract the stock recovery, so that I'm ready just in case.
Do you just tar the recovery.img and use that for flashing if necessary? No special permissions, nothing?
Sorry, not as clear cut as that... I did three things, cleared cache, cleared hidden, and
then started deleting files on sd. It is possible the problems are in multiple locations,
It is also possible that multiple attempts have an effect.
I personally feel I need both stock 3e and insecure cwm [and odin and adb] to be able to recover this tab. The broken 3e/reboot was my worst experience on this so far.
Use linux tar or the tab's busybox tar, to create an uncompressed tar with recovery.img as the only file. Do not use 7zip to create the tar, it didn't work for me (although it works fine to extract from the stock).
davp said:
Sorry, not as clear cut as that... I did three things, cleared cache, cleared hidden, and
then started deleting files on sd.
Click to expand...
Click to collapse
You mean you did this in CWM recovery? Because I hastily flashed the stock ROM when it wouldn't boot, and then I couldn't get into the recovery anymore and there was no way to flash CWM recovery from PC Odin, or is there?
SD you mean internal? Since with external you just pull it out...
This was my worst experience as well, and want to be ready if it ever happens again.
So to sum it up. If the /data is messed up, should we do the following?
1. In CWM recovery clear cache, clear hidden.
2. Flash stock e3 recovery.
3. In stock recovery wipe everything.
4. Flash stock ROM.
5. Boot.
6. Flash CWM recovery.
7. Restore backup.
please i have the same problem,where i find the stock e3 recovery?
thanks Davp!
---------- Post added at 03:29 PM ---------- Previous post was at 02:53 PM ----------
please,post a link for download the recovery.img tar for to flash with odin.this is my last hope!
I tried to go back to a stock rom and unroot my device by using the steps on the forum. What i have now is the unit comes on the asus logo shows but when it tries to boot up the screen is just black nothing happens. If i try to use an sd card with any thing on it doesn't read it. None of the files from the card show up in the menu. if have cleared the cache tried using the backup image that was on the device when i got it but still nothing. If you can help I would be grateful. I'm a noob to this rooting stuff. The only reason i brought it rooted was because of the price, I could not pass it up but after not getting some of the apps that i wanted to work if assume a rooted device is not for me.
jflynn0 said:
I tried to go back to a stock rom and unroot my device by using the steps on the forum. What i have now is the unit comes on the asus logo shows but when it tries to boot up the screen is just black nothing happens. If i try to use an sd card with any thing on it doesn't read it. None of the files from the card show up in the menu. if have cleared the cache tried using the backup image that was on the device when i got it but still nothing. If you can help I would be grateful. I'm a noob to this rooting stuff. The only reason i brought it rooted was because of the price, I could not pass it up but after not getting some of the apps that i wanted to work if assume a rooted device is not for me.
Click to expand...
Click to collapse
What instructions did you follow? Is the bootloader unlocked and can you boot into it? Does adb work? Need more info if we're going to help you.
It is rooted with
aokp-tf300t-build-38.
Android ver 4.0.4.
Kernel 2.6.39.4 g2bf1397-dirty.
Build IMM761.
bootloader unlocked
I was looking around in cwm menu before I tried to install the stock asus rom. Just going thru the menu's looking trying to familiarize myself with cwm. I went to backup and restore menu and there was Zip there. I hit to power button instead of the volume and it starting restoring the device. After that i have not been able to get it to do anything after the asus screen. But I can get into the menu of cwm. When i tried following the adb, i go into cmd on my computer and change directory it tells me the device is not ready. I tried putting a zip on a sd card but I cant get it to show on the device to install.
Try a factory reset in CWM, see if that helps.
tried the wipe data/factory reset several times with no luck. It goes through the process but still does not boot to any thing after asus logo.
jflynn0 said:
tried the wipe data/factory reset several times with no luck. It goes through the process but still does not boot to any thing after asus logo.
Click to expand...
Click to collapse
Can you flash a different ROM, maybe the stock one?
Had the same problem. Tried to flash stock from Twrp recovery.
Wipe do a factory reset, wipe system and than flash the aokp rom again.
Then reboot and when you are back in System you can put the rom you like on your internal SD.
Back to Recovery and flash the new rom.
I got adb working and it come up in devices list. How do i flash the aokp rom on the device. I'm learning this as i go along, after this i might get the hang of this . I cant seem to push files using adb either my directory is wrong. I unzip it into a folder (C:\romfolder\aokp_tf201_build-38.zip/sdcard) and all that comes up scrolling page of commands and help for adb when i push
this is the zip i dwl could not find built 38 for tf300 so i got tf201
http://aokp.co/index.php/releases/_/build-38-r24 also how do i make it an image to flash or can i download and image
jflynn0 said:
this is the zip i dwl could not find built 38 for tf300 so i got tf201
http://aokp.co/index.php/releases/_/build-38-r24 also how do i make it an image to flash or can i download and image
Click to expand...
Click to collapse
Do not flash a 201 rom or image. Thats for the prime. Never flash roms designed for another device no matter how similar they are.
ok I downloaded this on
http://goo.im/devs/termleech/tf300t/aokp_tf300t_unofficial_20120617_2100_build-39.zip
have to go to bed but when i get up this afternoon will try to get it o go to device.
How am I suppose to get it to the device if the sd card does not show up on file list in cwm?
Can you still use ADB? You can always push the files with that.
how do i use adb to push the file on to the device itself. because i can add it to the sdcard by just putting in on there and then placing sdcard in device but the menu as far as install zip from sdcard never shows any zips that are on the card itself. Only thing that shows up are list of directories that look like a standard list from cwm. Also if you choose any of directories from that list it returns no file found. If I choose apply update on sdcard no matter how many time i have called the file update.zip says "no such file or directory install aborted". Or how do i push and image to the restore section of the device and where do i find an image at?
well still no luck. I think I will give it a few more days and if I still cant get it guess will go to best buy and buy another on. Any thoughts on Toshiba excite?
Try this i posted a tutorial on how to fix this http://forum.xda-developers.com/showthread.php?t=1738825 hope it helps
Hello,
I have a problem.
Device bootloader unlocked, CWM Recovery v5.5.0.4 installed.
I tried to flash Acer_AV043_A700_1.025.00_EMEA_CUS1.
I thought that this firmware a zip file, then need to flash with CWM.
After nandroid backup start wipe data/factory reset and tablet hanged.
Then I reboot it and see nothing, just "Acer".
When with CWM restore my backup, system wrote something abought "MD5".
What can I do? Help me please!!! and sorry for my english.
Can you wipe cache and davlik cache?
Or try this:
While off hold volume+ button (one dot) and power button and then toggle the rotation switch on and off a few times.
For now I'm not at home. Will try and right away write.
nurbek05 said:
For now I'm not at home. Will try and right away write.
Click to expand...
Click to collapse
More than likely bricked. Best send it in for service.
As best as I can tell, you have to use the exact same rom version to go back to original.
Also, it seems CWM "may" have an issue restoring recovery backups. It's possible the data partition gets corrupted on restore, with possible system partition as with one other user. Hanging at the "wiping/formatting data seems to be a problem.
The MD5 is the checksum, which verifies the recovery backup is the same.
Remember, this is new territory, and a lot of this is untested.
MD
Itchiee said:
Can you wipe cache and davlik cache?
Or try this:
While off hold volume+ button (one dot) and power button and then toggle the rotation switch on and off a few times.
Click to expand...
Click to collapse
Hanged
nurbek05 said:
Hanged
Click to expand...
Click to collapse
Turn it in for service.
Your partitions are all destroyed. Data, System, and so it seems cache.
You can try getting a full rom, naming it to update.zip, and try installing using Vol + and PWR. this will of course wipe out you CWM and install a stock bootloader, but you already know it doesn't work anyhow.
If you can find the exact same rom it came shipped with, it might work.
Unfortunately, not a lot of roms to choose from right now, and asking for a certain version rom probably won't get many answers. Seems certain tabs require certain factory roms to run.
If your authorized Acer repair center is local, they may not charge you much for installing the correct service rom. Maybe.
70x Development is new. And these things happen, so expect it.
MD
Thank you, but I try.
Can you give me system.img?
nurbek05 said:
Thank you, but I try.
Can you give me system.img?
Click to expand...
Click to collapse
I don't have a system.img for your 700.
But, in the Dev forum, they have several full stock roms for download in the "ROMS" thread.
No, I do not know if they will work for you.
Sorry I can not be of much more help.
MD
seems we can only wait for NVflash
nurbek05 said:
Thank you, but I try.
Can you give me system.img?
Click to expand...
Click to collapse
your situation is just same as mine,seeming bricked after using fatory rest or wiping from cwm,I think it's the problem of the damn cwm.as i know from now there are several devices got bricked,all because of the goddamn cwm.as we know factory rest is the same as recovery wiping,i use the under the official recovery,everything wen fine,but after wiping via cwm from the forum,it appeared the problem.
i tried a lot of method,just as u mentioned,to flash *.img
but i found a curious thing,after dumping series of *.img from a well-mailfuntioning device i can use fastboot to flash "userdata" which the loaction is mmcblk010 or /dev/block/platform/sdhci-tegra.3/by-name/UDA,but after flashing,i can't erase userdata block in fastboot.then i reflashing the data.img to userdata block,then in cwm,i can mount /data,but it's still not able to wipe or format it.then i've found a data.img and flashing the userdata and reboot.then i enter the system,and it forced me to do a factory reset,of course as before,it's not mailfunctioning because of the cwm or the block itself damaged..
but i can enter adb,and i found that i can see the /data and the filesystem in it.then i use mount to modify it,for i can delete or modify the files in /data,and it appears normally.i delete everything in /data.then i want to try to reboot to see if it's working,but after rebooting,the device stuck at acer logo,then i reboot into the cwm,it can't be mounted again.it seems that i can flash the userdata but i can't format or wipe or modify...
and i tried to reflash the bootloader from a well-mailfunctioning deivece,not working,either.
then i go for searching the situation in google,i found there are a lot of similar problems of the tegra device,and the solution is nvflash...
i don't know if there are a block saving the information of partitions just like the PIT file of my galaxy s2,seems we should wait for nvflash?or the method to flashing PIT partitions file?
i installed the nvflash driver by modifying the usb id,but i can't do anything from nvflash,it's not matching.
If Acer A700 have Tegra3 then it have Secure Boot Key like Asus TF201?
http ://androidroot.mobi/2012/01/15/an-analysis-of-prime-security/
no way to nvflash
nurbek05 said:
If Acer A700 have Tegra3 then it have Secure Boot Key like Asus TF201?
http ://androidroot.mobi/2012/01/15/an-analysis-of-prime-security/
Click to expand...
Click to collapse
the asus has blocked the nvflash in tf201,and there isn't any method to flash a device of tegra3 via nvflash...
seems there is much time for us to wait
Any news abought nvflash?
In my town I more than sure that nobody can repair my A700.
Service is not good. But I can send it to capital where maybe repair.
Maybe need wait for nvflash or ROM which be compatibility with A700.
s
nurbek05 said:
Any news abought nvflash?
In my town I more than sure that nobody can repair my A700.
Service is not good. But I can send it to capital where maybe repair.
Maybe need wait for nvflash or ROM which be compatibility with A700.
Click to expand...
Click to collapse
same situation as mine....im in china and the device is not for sale publicly,i got it from a special way.seems there is noe one can repair the device all over the country,i should wait for the device on sale...
SD Card boot
I have exact the same problem.
Has anyone tried to boot from SD card?
Webitu
nurbek05 said:
Hello,
I have a problem.
Device bootloader unlocked, CWM Recovery v5.5.0.4 installed.
I tried to flash Acer_AV043_A700_1.025.00_EMEA_CUS1.
I thought that this firmware a zip file, then need to flash with CWM.
After nandroid backup start wipe data/factory reset and tablet hanged.
Then I reboot it and see nothing, just "Acer".
When with CWM restore my backup, system wrote something abought "MD5".
What can I do? Help me please!!! and sorry for my english.
Click to expand...
Click to collapse
Has yes to unbrick?you try to obtain a unbrick test of a500 to a700
http://forum.xda-developers.com/showpost.php?p=23584356&postcount=39
http://forum.xda-developers.com/showpost.php?p=23584356&postcount=39
DO NOT even think about running an A500 RUUs rom on your tablet.^^^^^^^^^^^^^^
Sure way to brick any device.
What you can do, is send lots of contacts to Acer, and demand the SBK (secure bootloader key). Then you can start thinking about NVFlash.
MD
I was just about to buy one of these tablets and now i read this quite upsetting info. There is no nvflash? Thats the suck for sure. Any word on it?
Anyone know if the tf700 has nvflash ability?
So I unlocked this without much trouble, and then when I was attemoting to use adb to flash images to recovery partition, one would just not work, and I stupidly tried to force it, and now it boots and just sits there.
I've seen a different website saying the Q can run Jellybean, and it also has info on getting the stock rom back .. but NO files. I know how to use the damn recovery tools once theyre booted up - those articles were completely useless. I don;t know what else to do. I tried to get the files that argghhhh jad posted to dropbox but they are not available anymore.
Stuck and been trying to fix this for the last 12 hours
EDIT:
Found stock recovery stuff, but I dont think it's going to help any...
Nevermind I suppose
I see that I can try the stock rar file posted for someone else in here to put into recovery, hope it works, I just dont know if the nernel is ok, but I would think so. It stops at the "unlocked"notificaton screen. anyay, yeah. If I get jellybean on instead ill share the info,
I believe you need to fastboot your recovery, not adb. Then you may be able to flash something back on there.
Sent from my XT897 using xda premium
tetrabyt said:
I believe you need to fastboot your recovery, not adb. Then you may be able to flash something back on there.
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
Thanks for the repl! S I actually have been using fastboot because adb for some reason just will not see the device (I checked the version and its correct supposedly). So what I did was take the WWRP rar, pull the contants out and make them into a .zip.and instaled with fastboot flash. The output looked ok:
sending 'userdata' (319120 KB)... OKAY [ 29.814s]
writing 'userdata'... OKAY [ 92.421s]
finished. total time: 122.235s
but what about all the other partitions? I jad done system earlier frok out of the stock zipfile. i think i may just try the entire Stock file insead, or maybe I am missing the fact that I beed to install the kernek into /boot, Any thoughts Thanks much!
EDIT: first im going to fastboot the recovery wit tue TWRP zip file, and try to install it from
I am a little confused, did you manage to get the recovery working? Looks like you were trying to flash the recovery img to your user data partition... Am I misreading your post.
-Saint
Whoaa just saw that. should have unzipped the recovery image and flashed it to the recovery partition with
Fastboot flash recovery recoveryfile.img
Then you can boot into recovery and flash one of the system dumps that these devs have generously posted for when we mess up like this...
Sent from my XT897 using xda premium
tetrabyt said:
Whoaa just saw that. should have unzipped the recovery image and flashed it to the recovery partition with
Fastboot flash recovery recoveryfile.img
Then you can boot into recovery and flash one of the system dumps that these devs have generously posted for when we mess up like this...
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
is this the basic method at present for a stock restore? i was looking at the thread with the files for RSD lite, but i was confused as to whether that was working. thx!
ok so I messed up what to flash from recovery. I had grabbed copies of the system, data, boot, etc for all the partitions thinking i needed to do them all from outside using fastboot,
Herby6262 said:
ok so I messed up what to flash from recovery. I had grabbed copies of the system, data, boot, etc for all the partitions thinking i needed to do them all from outside using fastboot,
Click to expand...
Click to collapse
Ok, the easiest way to get your phone up and running again is to push the newest TWRP from here, put it in your tools folder and push w fastboot:
fastboot flash recovery openrecovery-twrp-2.3.1.0-asanti_c.img
fastboot reboot recovery
Make a backup to your external sd card so that TWRP creates the directory needed to restore the stock system & boot. You should delete this first backup later since it will be broken.
Then download a system & boot image from here, unzip to the /TWRP/BACKUPS/"serial#"/ folder on your external sd. Do full wipes for system, dalvik, & factory reset; then restore Stock from within TWRP. Should be good to go.
:edit:
Just saw that tetrabyt already hit on this, consider this post a more detailed revision.
i must be retardedly doing this the wrong way, i quickly get twrp into recovery and can get in there, and I have the stock photon .zip in 1 big zip and in separate pieces, but how do you get them to the external card.. windows 7 fails to recognize the phone with some message MTP device unknown so I can't transfer it that way ... I dont know. Im about to chuck this thing out the window and be done with it. The whole purpose was to be able to install apps to the sdcard, originally. Only fastboot works from a command prompt, adb doesnt do a damn thing, trying multiple versions of it. I give up
Herby6262 said:
i must be retardedly doing this the wrong way, i quickly get twrp into recovery and can get in there, and I have the stock photon .zip in 1 big zip and in separate pieces, but how do you get them to the external card.. windows 7 fails to recognize the phone with some message MTP device unknown so I can't transfer it that way ... I dont know. Im about to chuck this thing out the window and be done with it. The whole purpose was to be able to install apps to the sdcard, originally. Only fastboot works from a command prompt, adb doesnt do a damn thing, trying multiple versions of it. I give up
Click to expand...
Click to collapse
Do you have an sd adapter or another device you can plug the sd into to transfer from your pc? Does adb fail when booted into TWRP also? Tried uninstalling/re-installing drivers?
Might be able to make a data img you could flash through fastboot, so long as the folder structure was correct... then use recovery from internal storage. Not certain on this: /data/media/sdcard/TWRP/BACKUP/"serial#"/
Maybe someone else can jump in here, this would be my last resort. Use any way possible to get it on external sd first.
-Saint
fallnSaint said:
Do you have an sd adapter or another device you can plug the sd into to transfer from your pc? Does adb fail when booted into TWRP also? Tried uninstalling/re-installing drivers?
Might be able to make a data img you could flash through fastboot, so long as the folder structure was correct... then use recovery from internal storage. Not certain on this: /data/media/sdcard/TWRP/BACKUP/"serial#"/
Maybe someone else can jump in here, this would be my last resort. Use any way possible to get it on external sd first.
-Saint
Click to expand...
Click to collapse
I believe there is a system.img floating around here somewhere.
Check out this thread
http://forum.xda-developers.com/showthread.php?t=1894575
Sent from my XT897 using xda premium
tetrabyt said:
I believe there is a system.img floating around here somewhere.
Check out this thread
http://forum.xda-developers.com/showthread.php?t=1894575
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
Thanks a ton for the help Saint, and others. I finally got it back in working order .. yay! Now to install that powermenu update someone made, and see about making android 4 opeate like the older versions, where you could install apps onto the external SD card. Am I correct in assuming they just F'ed it up by changing the /mnt names, while the software was not updated to accomodate those changes? Why the hell is internal memory now "sdcard" ... so odd. I have a friend whose internal storage is named "USB storage" on his phone. It's USB accessible .. but its a freakin flash card. So odd, and stupid. I really felt like 4.0 was a downgrade, personally. What improved? I see nothing, only things taken away (Im sure the underlying scheduler and thread management/memory mgmt is better, but you know what I mean .. anything visible?)
Herby6262 said:
Thanks a ton for the help Saint, and others. I finally got it back in working order .. yay! Now to install that powermenu update someone made, and see about making android 4 opeate like the older versions, where you could install apps onto the external SD card. Am I correct in assuming they just F'ed it up by changing the /mnt names, while the software was not updated to accomodate those changes? Why the hell is internal memory now "sdcard" ... so odd. I have a friend whose internal storage is named "USB storage" on his phone. It's USB accessible .. but its a freakin flash card. So odd, and stupid. I really felt like 4.0 was a downgrade, personally. What improved? I see nothing, only things taken away (Im sure the underlying scheduler and thread management/memory mgmt is better, but you know what I mean .. anything visible?)
Click to expand...
Click to collapse
Good to hear, glad you got her working again. As for how she runs, definitely snappier than older versions of android. Maybe just hardware, but I still see improvements w the wifes epic running ics, guessing that we will see better results once CM is dropped for this phone.
-Saint
Tried this, still stuck on Bootloader Unlocked Screen. TWRP restores don't seem to work right. I tried restoring an old backup I had of the boot/recovery/system with no luck. Everytime I wiped system/dalvik/cache/factory reset before restore. No errors show up.
So, I can go into fastboot, and I can flash files.
I tried RSD Lite 5.7 with this Zip
It flashes everything until RSD wants me to reboot. Then it reboots and gets stuck on the bootloader unlocked screen.
Any ideas?
[Edit] I flash CWM and found out that I can't mound /sdcard which doesn't seem right...
fallnSaint said:
Ok, the easiest way to get your phone up and running again is to push the newest TWRP from here, put it in your tools folder and push w fastboot:
fastboot flash recovery openrecovery-twrp-2.3.1.0-asanti_c.img
fastboot reboot recovery
Make a backup to your external sd card so that TWRP creates the directory needed to restore the stock system & boot. You should delete this first backup later since it will be broken.
Then download a system & boot image from here, unzip to the /TWRP/BACKUPS/"serial#"/ folder on your external sd. Do full wipes for system, dalvik, & factory reset; then restore Stock from within TWRP. Should be good to go.
:edit:
Just saw that tetrabyt already hit on this, consider this post a more detailed revision.
Click to expand...
Click to collapse
After RSD Lite, it might not have booted up because the system image was removed from the file to make it work. Probably if you flash TWRP after doing the RSD file, and restore Rangerbry's system backup, you might be good..
No Luck.
Just tried this.
Got the following Errors during only system restore:
E:Unable to mount '/cache'
E:unable to mount '/data'
Still stuck on Unlocked bootloader screen.
My emmc might be corrupted I think
I do have sprint insurance. Think they can reflash stock?
yogi2010 said:
After RSD Lite, it might not have booted up because the system image was removed from the file to make it work. Probably if you flash TWRP after doing the RSD file, and restore Rangerbry's system backup, you might be good..
Click to expand...
Click to collapse
coolroman123 said:
No Luck.
Just tried this.
Got the following Errors during only system restore:
E:Unable to mount '/cache'
E:unable to mount '/data'
Click to expand...
Click to collapse
Was that in CWM or TWRP recovery? Just trying to make sure the process was correct, haha. I have only started using TWRP on this device, but i think the 2 recoveries use different backup formats?
coolroman123 said:
Tried this, still stuck on Bootloader Unlocked Screen. TWRP restores don't seem to work right. I tried restoring an old backup I had of the boot/recovery/system with no luck. Everytime I wiped system/dalvik/cache/factory reset before restore. No errors show up.
So, I can go into fastboot, and I can flash files.
I tried RSD Lite 5.7 with this Zip
It flashes everything until RSD wants me to reboot. Then it reboots and gets stuck on the bootloader unlocked screen.
Any ideas?
[Edit] I flash CWM and found out that I can't mound /sdcard which doesn't seem right...
Click to expand...
Click to collapse
Can you boot to bootloader or just to fastboot? There are two control files in that RSD zip, one doesn't flash bootloader, try removing that one and forcing the reflashed bootloader. Then try restoring again. About all I can think of if it successfully flashes the other components... Maybe just restore system and not boot or data?
-Saint
Everything you need is here to return to stock WITH ota update.
http://forum.xda-developers.com/showthread.php?t=2001226
The only thing simple is the belief in simplicity.
Hello, I would like some help since I got this device just yesterday.
I got it with the EMUI 4 Android 6.0 stock installed on it. Since there was no update for it I unlocked the bootloader installed twrp rooted and manually flashed EMUI 5 7.0. Everything worked fine.
I created a backup through TWRP and restored it succefully multiple times.
Then I installed the Meticulus TWRP (since I was told it is a prerequisite for the AOSP). I Flashed the AOSP but it stuck during the boot animation (30 minutes afterwards I powered it off).
I reflashed my old TWRP and tried restoring my backup. IT fails with the explanation "Cannot wipe /vendor" while at the top it says "Cannot mount /vendor (invalid argument)" "Cannot mount /product (invalud argument)".
Anyone has a clue how to fix this? Fastboot adb all works so there should be a way to boot into an OS properly?
Since AOSP was not booting i guess you forgot formatting /data partition to ext4... And did u Used Stock vendor and not openkirin ones ?
Gesendet von meinem Honor 6X mit Tapatalk
As said I have replaced the custom TWRP with the default one so I think this should not apply anymore?
The "cannot mount vendor/product" messages came from the default TWRP after I reflashed it again.
At the top it says "cannot mount /vendor" either so I guess that is the actual problem?
It would be nice to get teh AOSP up but I really want to be able to boot into something first honestly.
And did u Used Stock vendor and not openkirin ones
Click to expand...
Click to collapse
Can you please explain? When I flashed your ROM i was on your TWRP. Does this even matter anymore?
At best I would be able to restore my backup.
To me it appears to be caused by the vendor partition.
Is there any way I can manually create that through TWRP?
algg said:
To me it appears to be caused by the vendor partition.
Is there any way I can manually create that through TWRP?
Click to expand...
Click to collapse
Yes you can but not creating it through twrp, but flashing it by fastboot mode: this is because
image (.img) files needs to be flashed by fastboot mode to avoid any kind of problem.
So, you should look for the last version of stock firmware on which you was before going custom, like BLN-L21CXXXB368 for example; tell me your build number and I'll find the package for you. Then, extract from the UPDATE.APP (a very big file that contains every partition in your phone like recovery, vendor, data, ecc. - you'll find this file inside the zip archive that contains the downloaded update) the vendor.img using Huawei Update Extractor, and then flash it through fastboot mode using the command "fastboot flash vendor vendor.img".
Otherwise, you could rely on dload method to reflash a full update package, and this should really fix everything since that it'll be like a new and clean installation of the OS. Then, unlocking the bootloader again and reflash TWRP to finally restore your previous backup made when it was working would be the final step.
Feel free to ask for further help
Thanks for the reply first really appreciate it.
I got the device on EMUI 4 Marshmallow rooted it and unlocked the bootloader then installed the BLN-L21C185B140 which worked smoothly.
I used that update.zip and extracted into dload root folder and started the huawei recovery installer but it said "package not found".
I tried flashing something to vendor before with fastboot but it said command not allowed.
Maybe I am doing something wrong?
algg said:
Thanks for the reply first really appreciate it.
I got the device on EMUI 4 Marshmallow rooted it and unlocked the bootloader then installed the BLN-L21C185B140 which worked smoothly.
I used that update.zip and extracted into dload root folder and started the huawei recovery installer but it said "package not found".
I tried flashing something to vendor before with fastboot but it said command not allowed.
Maybe I am doing something wrong?
Click to expand...
Click to collapse
Latest build on Nougat after the update was BLN-L22C185B140 so? If yes, the package that you need to download is that one. Unluckily i can't help about dload method, i never had fortune using dload because package verification always failed at 5%, i tried every combination but without success.
Command not allowed while flashing vendor image... but flashing others, like recovery or boot.img is allowed? If yes, i don't know what's causing this sorry... I'm sure that my friend @shashank1320 could surely help more than me about how using dload method correctly. Check his signature, it should contain a guide on how to use it
RedSkull23 said:
Latest build on Nougat after the update was BLN-L22C185B140 so? If yes, the package that you need to download is that one. Unluckily i can't help about dload method, i never had fortune using dload, i never be able to using it successfully because package verification always failed at 5%.
Command not allowed while flashing vendor image... but flashing others, like recovery or boot.img is allowed? If yes, i don't know what's causing this sorry... I'm sure that my friend @shashank1320 could surely help more than me about how using dload method correctly. Check his signature, it should contain a guide on how to use it
Click to expand...
Click to collapse
For fastboot yes flashing recovery or boot do work but vendor does not. Maybe the ISO is corrupted somehow I will try it again on a different machine now with the tool.
The link you posted the dload method from is the one where I initially found it as well so yea.
Also it shouldn't matter what I install since the only thing I need is the actual vendor (and product?) partition to work. I have a functional backup just TWRP cannot create/mount the partitions. So even a way to just create them without any data would actually fix my problem (at least I hope so?)
When trying to use Fastboot to flash the vendor/product img I get remote: Command not allowed (yes my bootloader is unlocked) although I can flash the recovery without any problem.
The dload method does not work as said. I placed the extracted content of the update.zip into the dload folder but the software "cannot find" the package.
algg said:
When trying to use Fastboot to flash the vendor/product img I get remote: Command not allowed (yes my bootloader is unlocked) although I can flash the recovery without any problem.
The dload method does not work as said. I placed the extracted content of the update.zip into the dload folder but the software "cannot find" the package.
Click to expand...
Click to collapse
@RedSkull23, thanks for the tag mate.
@algg, No need to flash the vendor image as you already had the stock vendor img.
Now what else you can try is to flash the stock recovery, boot to stock recovery, select factory reset and reboot. It should most probably fix the issue.
If not, reflash the TWRP, a regular TWRO available and not specific to elite or meticulous, but generic one given by OldDroid.
I hope you have downloaded the content for dload, if not, download these for B140.
Flash this via TWRP- http://update.hicloud.com:8180/TDS/...afnaf/update_data_full_BLN-L21_hw_meafnaf.zip
no further changes and Then use dload method for this file- http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1756/g1755/v105054/f1/full/update.zip
Try above and provide feedback. This is what I could think of best possible way to have everything with all system app working.
If not, let me know and I will try to help further.
Hi, I thought I need the vendor image since TWRP (all versions) tell me "Could not mount/wipe vendor" and "Could not mount/wipe product" "invalid argument" for both.
I tried the factory reset before but it does not work. It stops at 23% then shows a red exclamation mark and just goes to the original screen with the 3 buttons (restart, shutdown and wipe).
I am currently trying to get it to recognize my sd card. But somehow it does not work through TWRP it just does not recognize the 8GB SD Card. Also I am currently on the TWRP I was before all of this happened (3.1 openkirin). Without the SD Card recognized I can't put the dload files for it on it and in turn I can't use the dload.
I mean technically it should very well be possible to fix the device since it isn't a real brick and even TWRP and Fastboot load. It's just that all those little things are somehow ruining it.
Edit: I will get a new micro sd for some reason this one does nt work. I'll say then whether the flash then dload worked.
@shashank1320
Mind explaining why I should first use TWRP to flash something and then on top of it use dload?
And why those specific files?
algg said:
Edit: I will get a new micro sd for some reason this one does nt work. I'll say then whether the flash then dload worked.
@shashank1320
Mind explaining why I should first use TWRP to flash something and then on top of it use dload?
And why those specific files?
Click to expand...
Click to collapse
Sure, let me explain.
The first file is the data file which will install few systems apps like file manager, updater, themes, clock, fm radio etc. This will work via dload as well but the installation time is around 3-7 seconds so, over the course of time and flashing few times, i realised that these PV files cannbe flashed via TWRP and it works perfectly fine specific to PV files( twrp won't supoort other stock zips). We foash this first so that it updates your buld number and also does not replace the recovery with stock (as if you flash the main update zip first, it will replace with stock recovery so flashing the 2nd file will be quick but with unstable system apps, sometime).
Now we flash the main zip file with update.app via dload and it Install the main firmware for boot, vendor, recovery, system, usrdata etc.
Hope this explanation helps, if not let me know and I will rephrase myself.
It does help. I did all of this and now in the dload app I get "Software install failed Incompatibilty with current version please download the correct update package".
When I flashed the zip you linked me with TWRP it said "cannot mount /data /vendor /product". Appearently data cannot be mounted since it is encrypted.
Any clue as to what I am doing wrong? Or is this device now a real brick with functioning recovery but without OS?
Is there any way I can "debug" what is going on while the boot animation is playing?
What is confusing me is that the boot animation plays just normal but it simply does not continue to the actual OS.
algg said:
It does help. I did all of this and now in the dload app I get "Software install failed Incompatibilty with current version please download the correct update package".
When I flashed the zip you linked me with TWRP it said "cannot mount /data /vendor /product". Appearently data cannot be mounted since it is encrypted.
Any clue as to what I am doing wrong? Or is this device now a real brick with functioning recovery but without OS?
Click to expand...
Click to collapse
Not bricked..its just Data is not mounted or encryption. Should never encrypted it. NVM.
Do one thing, boot to twrp recovery. Try flashing and get error, then go to main TWRP page and click on reboot, select recovery out of 4 options( power off, system, bootloader and recovery). It will boot to recovery, now try flashing it again and see. Most if the time it helps.
Else, go to main page, select wipe, click on format rather than wipe here, it will prompt for typing Yes to confirm. Biit to recovery from main twrp page ( as mentioned above). And try this same thing of formatting data couple of times and then flash the zip and then dload.
I know these are tedious steps but inhave revived my device many a times with all these tricks after some efforts.
Good luck
YAY it works.
Just to recap what I did:
I flashed your thing first through TWRP tried to flash your other link with dload (which did NOT work)
Then I flashed the thing (emui5 Android 7 for Europe) through TWRP played in my old backup of exactly this through TWRP cleared dalvik & cache.
Then I waited 20 minutse and now it started.
Really thanks to all of you very nice people here. I would be very baffled if it wasnt able to repair the device since Fastboot and Recovery still work.
But Huaweis recovery is beyond terrible.
algg said:
YAY it works.
Just to recap what I did:
I flashed your thing first through TWRP tried to flash your other link with dload (which did NOT work)
Then I flashed the thing (emui5 Android 7 for Europe) through TWRP played in my old backup of exactly this through TWRP cleared dalvik & cache.
Then I waited 20 minutse and now it started.
Really thanks to all of you very nice people here. I would be very baffled if it wasnt able to repair the device since Fastboot and Recovery still work.
But Huaweis recovery is beyond terrible.
Click to expand...
Click to collapse
It is terrible indeed. Glad your phone working.
Thanks to @RedSkull23 for tagging, else I may have not responded as he was already involved and was helping as usual.:good:
algg said:
Really thanks to all of you very nice people here. I would be very baffled if it wasnt able to repair the device since Fastboot and Recovery still work.
But Huaweis recovery is beyond terrible.
Click to expand...
Click to collapse
I'm happy for you man, indeed it would be so bad, especially because you got this device 3 or 4 days ago if i didn't read bad, anyway what matters is that now it works. Are you able to restore the previous backup through TWRP now? (But before trying... Make a backup of your actual OS )
shashank1320 said:
It is terrible indeed. Glad your phone working.
Thanks to @RedSkull23 for tagging, else I may have not responded as he was already involved and was helping as usual.:good:
Click to expand...
Click to collapse
Are you joking man? I just tagged you for more help, but practically you helped him in everything, not me; I'm sure that you would noticed the thread and helped as always even without my tag, i just speeded up things for being helpful to algg.
algg, I'd like to apologize myself; i didn't vanished after tagging shashank, today i just was at work and obviously i was busy for help, but as i saw with pleasure he already helped you to restore your OS and that was the objective. Nice one, guys!