Related
hello,
today i downloaded the Android 5.0 Image from Google and wanted to flash it.
i extraced the tgz file and flashed the boot.img and system.img via fastboot.
so far so good. i reboot the tabelt and it has a bootloop.
so i used the flash-all.bat included in the tgz file but it wont flash it (didnt copied the error message)
so i tried flashing 4.4.4. but when i flash anything it wont work (fastboot flash recovery recovery.img for example)
i tried differend usb ports and with fastboot devices it shows my device.i tried rebooting the laptop and the tablet. no changes
example
Code:
C:\Users\xxx\Desktop\nakasi-lrx21p>fastboot flash recovery recovery.img
sending 'recovery' (5682 KB)...
after 20 min of waiting nothing changes.
my setup:
a laptop with windows 8.1
all drivers installt
original nexus 7 usb cable
drivers are working fine. i often flashed something on the n7 and my m7 bevor on this laptop
Code:
C:\Users\xxx\Desktop\nakasi-lrx21p>fastboot flash boot boot.img
sending 'boot' (5146 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
thats a error message i get when something more happens then "sending 'xxx' (xxx kb)
Code:
FAILED (data transfer failure (Too many links))
finished. total time: 85.114s
now i managed to flash recovery (TWRP)
but i cant do anything there. in the pc its not listet (adb devices) and in the log of TWRP it says
Code:
E:Unable to mount '/data'
E:Unable to mount '/system'
E:Unable to mount '/cache'
E:Unable to mount '/data'
now i got in TWRP (changing to Clockworkmod Recovery doesnt change anything) and got to Wipe-> Advanced
there i tried to repair the partions . doesnt works. but if i format it that works and could be mounted again. (in system i have to format it in an different file format and back to ext4)
so now i flashed the rom (stock 5.0 from google) and it boots... waiting whats coming next....
etsch said:
now i got in TWRP (changing to Clockworkmod Recovery doesnt change anything) and got to Wipe-> Advanced
there i tried to repair the partions . doesnt works. but if i format it that works and could be mounted again. (in system i have to format it in an different file format and back to ext4)
so now i flashed the rom (stock 5.0 from google) and it boots... waiting whats coming next....
Click to expand...
Click to collapse
i have the same problem how did you format it and did it fix the problem
do you have TWRP ?
you go to wipe-> advanced
there you can choose which repair and format.
ive formated one by one and then it shows the size after formating.
now my tablet booted into android (i think its ugly) but iam afraid going in the recovery
Hi,
I have a Nexus 4 which was flashed with Lollipop 5.1.1.
My problem started when, after letting the battery completely drain and then trying to turn the phone on again, I got stuck on the message "Android is starting... optimizing apps" for days. I tried rebooting and factory format with no success.
I also tried formatting it through TWRP, but I got the message "Unable to mount /cache". After that, I tried flashing older factory images but only got my phone to work with the oldest version of jelly bean available by google developers page (4.2.2). After I got it to work, I tried to OTA update it to 4.3, but the same message "Android is starting ... optimizing apps" came back.
I had no other choice but to fastboot format it and flash it again with 4.2.2.
Any ideas on what could possibly be causing this? I thought it might be some problem in the cache partition but haven't found a way to fix it or if it's even possible to. Apparently everything's working with 4.2.2 but I'd love to go back to 5.1.1!
Thanks in advance!
dont dirty flash the factory image. make a clean factory image flash
After flashing stock KK or LP, are you also flashing userdata.img and then booting into stock recovery to format/wipe data before booting the ROM for the first time?
audit13 said:
After flashing stock KK or LP, are you also flashing userdata.img and then booting into stock recovery to format/wipe data before booting the ROM for the first time?
Click to expand...
Click to collapse
Haven't tried that, I'll give it a go and post the results here!
I've also noticed the phone isn't receiving any signal and it doesn't display the IMEI anymore..
The lack of an imei is a definite problem. Try flashing the stock LP or KK ROM and check for the imei.
audit13 said:
The lack of an imei is a definite problem. Try flashing the stock LP or KK ROM and check for the imei.
Click to expand...
Click to collapse
Did a clean factory image flash of Lollipop 5.1.1, booted into twrp recovery (I'm not sure how to go back to stock recovery) to wipe the data and got the following message:
E: UnMount: Unable to find partition for path '/sdcard'
E: Mount: Unable to find partition for path '/sdcard'
Updating partition details...
E: Unable to mount '/cache'
...done
E: Unable to mount '/cache'
Full SELinux support is present
E: Unable to mount '/cache'
E: Unable to mount '/cache'
MTP Enabled
Formatting Data using make_ext4fs function.
Ypu may need to reboot recovery to be able to use /data again.
Updating partition details...
E: Unable to mount '/cache'
...done
After that I rebooted the phone and it's been stuck on bootloop again since then.
When you flash a stock ROM, did you flash the recovery.img? Sometimes, I find that only stock recovery can properly format the cache. When flashing my Nexus 5 to stock from a custom ROM, I get an error message when I boot into stock recovery that the cache has an invalid format. Once I perform a factory wipe, the cache is properly formatted and wiped.
audit13 said:
When you flash a stock ROM, did you flash the recovery.img? Sometimes, I find that only stock recovery can properly format the cache. When flashing my Nexus 5 to stock from a custom ROM, I get an error message when I boot into stock recovery that the cache has an invalid format. Once I perform a factory wipe, the cache is properly formatted and wiped.
Click to expand...
Click to collapse
Yeah, I flashed the images for boot, recovery, system, userdata and cache separately. I'll look up how to get back into stock recovery now and I'll try what you've said!
If recovery.img was flashed, the phone should not have TWRP, it should be a stock recovery. If stock recovery cannot be flashed, this leads to me believe that something is wrong with the memory chip.
audit13 said:
If recovery.img was flashed, the phone should not have TWRP, it should be a stock recovery. If stock recovery cannot be flashed, this leads to me believe that something is wrong with the memory chip.
Click to expand...
Click to collapse
I tried it again, flashed everything including recovery, went into stock recovery mode and wiped the data. Apparently its back to being stuck on bootloop
Use fastbot commands to erase cache and userdata. Then use fastboot to flash the userdata.img file, boot directly to recovery, and wipe again.
audit13 said:
Use fastbot commands to erase cache and userdata. Then use fastboot to flash the userdata.img file, boot directly to recovery, and wipe again.
Click to expand...
Click to collapse
Did it, still stuck on bootloop... Not sure if it can be somehow related but I got this message when I booted into recovery
The recovery screen looks correct because, after flashing userdata.img, you must format in stock recovery.
I am at a loss as to why 4.2.2 works while kk and LP do not.
audit13 said:
The recovery screen looks correct because, after flashing userdata.img, you must format in stock recovery.
I am at a loss as to why 4.2.2 works while kk and LP do not.
Click to expand...
Click to collapse
Ah, thanks for the help, anyway!
If someone else knows what to do.. The phone is now back to the initial message "android is starting... optimizing apps". Kinda of losing hope now
I've done this to my Nexus 5 once, too.
You basically screwed your cache partition.
Boot into the bootloader. Hook the phone up to your pc and open the command prompt.
Enter these commands:
fastboot erase cache
fastboot format cache
fastboot reboot-bootloader
When successful boot into recovery and the errors should be gone.
You should be able to flash a new rom now.
playitlouder said:
I've done this to my Nexus 5 once, too.
You basically screwed your cache partition.
Boot into the bootloader. Hook the phone up to your pc and open the command prompt.
Enter these commands:
fastboot erase cache
fastboot format cache
fastboot reboot-bootloader
When successful boot into recovery and the errors should be gone.
You should be able to flash a new rom now.
Click to expand...
Click to collapse
This got rid of the unable to mount cache error, flashed the rom again but it's still stuck on bootloop :/
thafuchs said:
This got rid of the unable to mount cache error, flashed the rom again but it's still stuck on bootloop :/
Click to expand...
Click to collapse
Okay. Progress
You have probably already nuked all your data. So I would suggest erasing and formatting everything again and then flash the newest factory image.
Enter bootloader again, on your pc do the following:
fastboot erase system
fastboot format system
fastboot erase data
fastboot format data
fastboot reboot-bootloader
Then grab the factory image, open the flash_all.bat file in an text editor (either use windows notepad, or grab notepad++).
You have to "cd" to the directory of your factory image. I would suggest to type "c:" *press enter* then cd *pull the folder that contains the factory image into the command prompt* *press enter*.
If you type "dir" now you should get your factory image directory.
Now just type in every command from the flash_all.bat one by one. Report, if there are any errors.
playitlouder said:
Okay. Progress
You have probably already nuked all your data. So I would suggest erasing and formatting everything again and then flash the newest factory image.
Enter bootloader again, on your pc do the following:
fastboot erase system
fastboot format system
fastboot erase data
fastboot format data
fastboot reboot-bootloader
Then grab the factory image, open the flash_all.bat file in an text editor (either use windows notepad, or grab notepad++).
You have to "cd" to the directory of your factory image. I would suggest to type "c:" *press enter* then cd *pull the folder that contains the factory image into the command prompt* *press enter*.
If you type "dir" now you should get your factory image directory.
Now just type in every command from the flash_all.bat one by one. Report, if there are any errors.
Click to expand...
Click to collapse
Okay, got some errors on the way... trying to erase data failed (Remote: partition table doesnt exist), format data failed too (formatting is not supported for filesystem with type ' '.)
Also, on the last command:
.\fastboot -w update .\image-occam-lmy48t.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
[...]
checking version-bootloader
FAILED
Device version-bootloader is 'MAKOZ10o'
Update requires 'MAKOZ30f'
Rebooted and its now stuck on google logo
Sorry, you should have typed: (it obviously cannot format something that is not there )
fastboot erase userdata
fastboot format userdata
Have you flashed the bootloader?
Have you rebooted after flashing the bootloader?
fastboot flash bootloader bootloader-mako-makoz30f.img
fastboot reboot-bootloader
Don't forget to also flash the radio.
These "does not contain" errors are normal.
playitlouder said:
Sorry, you should have typed: (it obviously cannot format something that is not there )
fastboot erase userdata
fastboot format userdata
Have you flashed the bootloader?
Have you rebooted after flashing the bootloader?
fastboot flash bootloader bootloader-mako-makoz30f.img
fastboot reboot-bootloader
Don't forget to also flash the radio.
These "does not contain" errors are normal.
Click to expand...
Click to collapse
Okay, I've flashed bootloader, rebooted, flashed radio, rebooted, typed the update command but the checking of bootloader version failed again.. rebooted and its back to being stuck on google logo
Hello everyone!
I tried installing the latest fastboot ROM on a RN QCOM, and MiFlash fails with an error that it is unable to format a partition.
After booting into TWRP, I see that /data partition says size is 0MB, usage and free space also 0MB and it is unable to mount it. The other partitions are fine(though I can't find the EFS partition for the IMEI files). Previously running Hexagon ROM and TWRP 3020.
I can only boot into fastboot and recovery. The command "fastboot erase data" fails and says partition table is missing. How can I rewrite the partition table? All the methods I found need adb but my device is dead... Please help!
Thank you!
hello all,
my yureka(a05510) CAN boot into bootloader and recovery,
Ive tried flashing roms, different recoveries(twrp v3.00 and 2.8), formatting data, mount, resizing partitions, annabathinas method, flashing fastboot images(cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip) through fastboot commands and batch files like flash-all.bat (lots of times) and even YGDP method for flashing stock firmware(gives unknown error:5 last error:997 msg: CP8675_I02_P1 , download failed please try again.) i even tried writing emmc img to micro sd(i believe used when phone does not boot into fastboot mode, though NOT my case) and hoped it would change something but that failed too.
please help. thanks in advance.
is your problem solved ? because i am facing the same issue right now and i am not able to find any way out
Pranay_619 said:
is your problem solved ? because i am facing the same issue right now and i am not able to find any way out
Click to expand...
Click to collapse
Fastboot erase system
Fastboot erase cache
Fastboot erase userdata
Sent from my AO5510 using Tapatalk
Hey, I accidentally corrupted my persist partition, the phone is unusable; the WiFi doesn't work, and it restarts every 2 Minutes. I tried flashing persist
fastboot flash persist persist.img
FAILED (remote: Error: This image isn't allow download)
I already tried erasing persist, but it won't let me.
Can someone please tell me a method to unlock the persist partition for download so I can flash persist.img? Please note that I can't flash TWRP either, says partition table doesn't exist. Is there a way to maybe flash it through Mi Flash Tool?
boot to twrp
enable mtp from twrp if not enabled
copy persist.img to root of your phone storage
open terminal in twrp
and give the following command
dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27
and done
now persist partition will be restored
reboot your phone
No twrp
raaz1431994 said:
boot to twrp
enable mtp from twrp if not enabled
copy persist.img to root of your phone storage
open terminal in twrp
and give the following command
dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27
and done
now persist partition will be restored
reboot your phone
Click to expand...
Click to collapse
As I said earlier, I can't flash a custom recovery, tells me that partition table does not exist.
Hi man!.
do you flash with factory_reset.bat?, if the answer is yes, you have to flash tissot 7.23 with the attachment (change the txt extension to bat and start the phone in fastboot, when it finish, start the phone in fastboot and unlock the bootloader and try to flash the persist partition again in fastboot, if didnt work, boot the TWRP recovery (yes, boot it with fastboot boot recovery.img ) and flash the persist image with adb shell, dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist , the persist image must be in the internal memory (you can copy it with MTP) when the phone starts, you can change the WLAN and Bluetooth mac addres in /persist/wlan_mac.bin, /persist/bluetooth/.nv_bluetooth, to change the serial numer /persist/.sn
Hope it works to you
PD. If you flash the factory_reset.bat, probably you lost the IMEI to and that would be a problem.
do not flash twrp
just boot to twrp using fastboot command
fastboot boot twrp.img
---------- Post added at 12:49 AM ---------- Previous post was at 12:48 AM ----------
CoolPlushBear said:
As I said earlier, I can't flash a custom recovery, tells me that partition table does not exist.
Click to expand...
Click to collapse
do not flash twrp
just boot to twrp using fastboot command
fastboot boot twrp.img
CoolPlushBear said:
As I said earlier, I can't flash a custom recovery, tells me that partition table does not exist.
Click to expand...
Click to collapse
Did you ever solve this issue or find a work around? I have same issue.....
If you don't flash the backup of your persist partition and use instead someone else's backup, you'll mess up your phone.
- # dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27
dd: writing '/dev/block/mmcblk0p27': No space left on device
2049+0 records in
2048+0 records out
1048576 bytes (1 .0MB) copied, 0.114366 seconds, 8.7MB/s
FAIL~~
CoolPlushBear said:
Hey, I accidentally corrupted my persist partition, the phone is unusable; the WiFi doesn't work, and it restarts every 2 Minutes. I tried flashing persist
fastboot flash persist persist.img
FAILED (remote: Error: This image isn't allow download)
I already tried erasing persist, but it won't let me.
Can someone please tell me a method to unlock the persist partition for download so I can flash persist.img? Please note that I can't flash TWRP either, says partition table doesn't exist. Is there a way to maybe flash it through Mi Flash Tool?
Click to expand...
Click to collapse
Don't try to flash persist.img You can encounter more trouble
You can Lost IMEI and sensor, try this metodo:
https://forum.xda-developers.com/mi-a1/how-to/tool-persist-resurrector-v1-0-0-0-t3781095
carlosorta said:
Hi man!.
do you flash with factory_reset.bat?, if the answer is yes, you have to flash tissot 7.23 with the attachment (change the txt extension to bat and start the phone in fastboot, when it finish, start the phone in fastboot and unlock the bootloader and try to flash the persist partition again in fastboot, if didnt work, boot the TWRP recovery (yes, boot it with fastboot boot recovery.img ) and flash the persist image with adb shell, dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist , the persist image must be in the internal memory (you can copy it with MTP) when the phone starts, you can change the WLAN and Bluetooth mac addres in /persist/wlan_mac.bin, /persist/bluetooth/.nv_bluetooth, to change the serial numer /persist/.sn
Hope it works to you
PD. If you flash the factory_reset.bat, probably you lost the IMEI to and that would be a problem.
Click to expand...
Click to collapse
what is tissot 7.23?
raaz1431994 said:
boot to twrp
enable mtp from twrp if not enabled
copy persist.img to root of your phone storage
open terminal in twrp
and give the following command
dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27
and done
now persist partition will be restored
reboot your phone
Click to expand...
Click to collapse
still working in 2020. Thanks for your post. Small thread but powerful. :dynamite: