Database Users

Can't flash partitions

Hello all,
I left a similar post in a couple other threads, and thought maybe someone here might have some insight into my problem.
Been running AICP rom (no custom kernel except the one that comes with AICP) with f2fs on /data and /cache for several months on 16GB grouper. About a month or so ago, the wife installed a game that wouldn't run on this hardware (King's Paradise Bay), and I uninstalled it. It left a file in /data/data/....etc that couldn't stat in TWRP, so no nandroid backups since then. I figured I'd just backup user data with TiBkp and wipe with fresh install of latest AICP when time permitted.
The other night I noticed the N7 was boot looping, getting to the stage where the boot animation dims. The boot anim would hang and after several seconds the Google unlock splash screen would come up and the N7 would try to boot again.
I can get into TWRP and bootloader with no problem. However, when TWRP comes up, the log shows the red entries for 2 files that can't stat, which has been this way since that game was uninstalled. I cannot seem to wipe *any* partition, and when I attempt to format or wipe userdata in TWRP, the N7 spontaneously reboots. Manually attempting to wipe/format/etc. via FastBoot doesn't work, with error message showing after trying to flash bootloader. Also, I can't change /data or /cache back to ext4. I am able to successfully read, write, and delete files on the N7 via computer USB MTP connection.
If the N7's flash memory has somehow become corrupted, is there a way to completely erase/format/whatever so that this wonderful device can become usable again? Any help would be greatly appreciated.
Thanks in advance.

Hello,
don't flash Bootloader via Fastboot. You should do this commands:
Code:
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot erase boot

Trafalgar Square said:
Hello,
don't flash Bootloader via Fastboot. You should do this commands:
Code:
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot erase boot
Click to expand...
Click to collapse
Yes, I have attempted all these commands, followed by flashing with either fastboot or TWRP with no success. Fastboot reports success, but partitions are not erased.

I have the same problem. The Nexus Root Toolkit can not flashign. It succeeds only boot TWRP. In TWRP computer sees the files from the tablet.I could not rename and delete. Wipe the TWRP and stock recovery displays the status OK, and the files are deleted. Fastboot shows that uploads, but all files remain unchanged.

Nexus only runs with Jelly bean 4.2.2 (downgrade from 5.1.1)

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

Please help! Stuck with bootloop after updating SuperSU

Today I got a message saying that SuperSU needs to be updated on my rooted Nexus 10 with stock Android 5.1. Then it booted into TWRP and flashed the zip file, but now it's stuck with the bootloop forever. How can I get out this mess without losing anything? Step-by-step instruction with fastboot would be highly appreciated.
Would reflashing 5.1 with the following commands be good enough to restore the system without losing userdata once I boot into fastboot mode?
fastboot flash bootloader bootloader-manta-mantamf01.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash system system.img
Do I need those erase steps such as
fastboot erase boot
fastboot erase cache
fastboot erase system
Thanks in advance!

mj56gt said:
Today I got a message saying that SuperSU needs to be updated on my rooted Nexus 10 with stock Android 5.1. Then it booted into TWRP and flashed the zip file, but now it's stuck with the bootloop forever. How can I get out this mess without losing anything? Step-by-step instruction with fastboot would be highly appreciated.
Would reflashing 5.1 with the following commands be good enough to restore the system without losing userdata once I boot into fastboot mode?
fastboot flash bootloader bootloader-manta-mantamf01.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash system system.img
Do I need those erase steps such as
fastboot erase boot
fastboot erase cache
fastboot erase system
Thanks in advance!
Click to expand...
Click to collapse
Don't you have the nandroid backup?
Your steps look right. I check them on here: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
See the last part of step 11. It says:
Code:
If going for a complete back to stock using the manual flashing of the zip file, execute the following commands after the above 4:
fastboot erase userdata
fastboot flash userdata userdata.img
So if you DON"T do this step, user data should be there. But I do not own this tablet and not 100% sure about that. Do that on your own risk :fingers-crossed:

Many thanks for checking the steps for me!
nitin.chobhe said:
Don't you have the nandroid backup?
Click to expand...
Click to collapse
No, I don't have a recent nandroid backup. I can still run adb, and have managed to pull out those photos on the tablet. Do you think that I could boot into the recovery mode and perform the nandroid backup?
nitin.chobhe said:
Code:
If going for a complete back to stock using the manual flashing of the zip file, execute the following commands after the above 4:
fastboot erase userdata
fastboot flash userdata userdata.img
So if you DON"T do this step, user data should be there. But I do not own this tablet and not 100% sure about that. Do that on your own risk :fingers-crossed:
Click to expand...
Click to collapse
What's the worst scenario if I don't erase the userdata?

mj56gt said:
Many thanks for checking the steps for me!
No, I don't have a recent nandroid backup. I can still run adb, and have managed to pull out those photos on the tablet. Do you think that I could boot into the recovery mode and perform the nandroid backup?
What's the worst scenario if I don't erase the userdata?
Click to expand...
Click to collapse
1. Even if you do nandroid, it would be exact replica of your current state i.e. boot loop
2. Worst scenario is bootloop

nitin.chobhe said:
1. Even if you do nandroid, it would be exact replica of your current state i.e. boot loop
2. Worst scenario is bootloop
Click to expand...
Click to collapse
I've fully restored the system without losing any data! Really appreciate your help!

mj56gt said:
I've fully restored the system without losing any data! Really appreciate your help!
Click to expand...
Click to collapse
What steps did you follow... Happy that it worked out for you! :good:

mj56gt said:
I've fully restored the system without losing any data! Really appreciate your help!
Click to expand...
Click to collapse
Just the steps in my original post, and also the same steps mentioned in the link you mentioned. Thanks again for your kind help!

mj56gt said:
Just the steps in my original post, and also the same steps mentioned in the link you mentioned. Thanks again for your kind help!
Click to expand...
Click to collapse
You can just press that thanks button ?
Sent from my Nexus 4 using XDA Free mobile app

PIT files
My nexus 10 has the boot loop problem and I think I have been left with the only option of Re-Partition but I need the PIT file. Can anybody help or provide this file?
I have tried everything else (fastboot, adb, temporary custom recoveries, Nexus Root Toolkit) with no success.

[HELP] Recovery Bricked and can't reflash

Hello,
I've decided to install the Beta version of Oxygenos 3.0. Since my phone came from the OnePlus support, I've unlocked the oem, installed TWRP and flashed the Oxygen zip.
However, a day later I've spotted important touchscreen issues (I can't use the touchscreen sometimes).
To see if it is a software problem, I've decided to go to the recovery to reflash a backup. When I try to go to recovery mode, nothing Happen! (Just the oneplus logo ).
So, i've decided to reinstall TWRP by flashing it with fastboot.
"fastboot flash recovery recovery.img" -> OK
"fastboot boot recovery.img"
downloading 'boot.img' ...
OKAY [0.702s]
booting...
FAILED (remote: dtb not found)
Click to expand...
Click to collapse
I've tried to install the stock recovery but I've the same error.
PLEEEASE HELP. I've waited a week to receive my phone because it had a problem but it's broke again :crying:
Note: I can go in Android normally (but with the touchscreen problem)

http://forum.xda-developers.com/oneplus-2/general/firstaid-zip-revert-h2os-mm-beta-to-lp-t3306967 try this.

This happened to me too except I would not boot into the OS or recovery. I ended up going into fast boot and formatting the System, recovery and data partitions. Here is what I typed.
fastboot format system
fastboot format recovery
fastboot format data
I am not sure if you have to format the data but I did.
After that I flashed TWRP
fastboot flash recovery recovery.img
Then I booted into recovery and was able to restore.

AndroidBeginNinja said:
http://forum.xda-developers.com/oneplus-2/general/firstaid-zip-revert-h2os-mm-beta-to-lp-t3306967 try this.
Click to expand...
Click to collapse
Thank you,
I've done this and I had a working recovery, (bootloop if I try to boot up normaly but it's not a problem I just have to flash a rom)
Trey22200 said:
This happened to me too except I would not boot into the OS or recovery. I ended up going into fast boot and formatting the System, recovery and data partitions. Here is what I typed.
fastboot format system
fastboot format recovery
fastboot format data
I am not sure if you have to format the data but I did.
After that I flashed TWRP
fastboot flash recovery recovery.img
Then I booted into recovery and was able to restore.
Click to expand...
Click to collapse
I've tested your manipulation and it worked well too.
For those having the same problem OR want to install Oxygen OS the CLEAN WAY, read this post before: https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108/
It is very important to read the faq before flashing and doing **** like me.

http://forum.xda-developers.com/one...overy-teamwin-recovery-project-3-0-0-t3310713 flash this first before you flash oos3

Developers please help for resolve problem of sim 2 imei 0

because of modem update in hydrogen os 2.5 this whole mess starts pls help

Rohanlovely said:
because of modem update in hydrogen os 2.5 this whole mess starts pls help
Click to expand...
Click to collapse
This new modem firmware is quite unstable, I advise you against using it. My solution to get working second SIM was to restore OOS 3.1 modem and format modemst1, modemst2 and persist partitions. Not until after formatting the partitions did it work again (CM14 keept rebooting/crashing).

pitrus- said:
This new modem firmware is quite unstable, I advise you against using it. My solution to get working second SIM was to restore OOS 3.1 modem and format modemst1, modemst2 and persist partitions. Not until after formatting the partitions did it work again (CM14 keept rebooting/crashing).
Click to expand...
Click to collapse
How u got back the sim 2 working ?

pitrus- said:
This new modem firmware is quite unstable, I advise you against using it. My solution to get working second SIM was to restore OOS 3.1 modem and format modemst1, modemst2 and persist partitions. Not until after formatting the partitions did it work again (CM14 keept rebooting/crashing).
Click to expand...
Click to collapse
how do you format the partitions? through TWRP? so steps are, flash oos 3.1 then format the modemst1 and 2?

Rohandd said:
how do you format the partitions? through TWRP? so steps are, flash oos 3.1 then format the modemst1 and 2?
Click to expand...
Click to collapse
Sim 2 start working after that ?? U tried that ?

Like I said, both SIM cards work again after flashing OOS 3.1 ROM (or firmware files manually) and then using the ordinary fastboot format command to format modemst1 and modemst2, then used fastboot flash persist persist.img with the persist partition dump found in this forum.

pitrus- said:
Like I said, both SIM cards work again after flashing OOS 3.1 ROM (or firmware files manually) and then using the ordinary fastboot format command to format modemst1 and modemst2, then used fastboot flash persist persist.img with the persist partition dump found in this forum.
Click to expand...
Click to collapse
could you please list out the exact steps you have done to fix your issue?
there are many users who are getting this issue including me.
please list the steps with the links of files you flashed. it would be a great help.

​
pitrus- said:
Like I said, both SIM cards work again after flashing OOS 3.1 ROM (or firmware files manually) and then using the ordinary fastboot format command to format modemst1 and modemst2, then used fastboot flash persist persist.img with the persist partition dump found in this forum.
Click to expand...
Click to collapse

https://drive.google.com/file/d/0B9IqSEI0OM37RTM5M09Ib180U0E/view
I got it
Persist.img for oneplus 2?

Rohanlovely said:
https://drive.google.com/file/d/0B9IqSEI0OM37RTM5M09Ib180U0E/view
I got it
Persist.img for oneplus 2
Click to expand...
Click to collapse
Did you tried with this??
any fix??

ashu01 said:
Did you tried with this??
any fix??
Click to expand...
Click to collapse
My laptop windows crashed after repairing that i will try

Rohanlovely said:
My laptop windows crashed after repairing that i will try
Click to expand...
Click to collapse
can you join this telegram group link
https://telegram.me/joinchat/CbL5zUA-vInKg1B5M8baqQ

Had the same problem
Hi,
Just to give you all a quick background. I was in the same situation as you. Flashed H2OS didn't like the jumpy signal therefore wanted to go back to OOS.
First boot of OOS resulted in no connectivity (no wifi, no data, no Bluetooth). I followed the method above and deleted modemst1 and modemst2 and formatted modemst (all done thru fastboot)
Once I did that I was able to boot into OOS to get the signals. As petris said above, wiping and then booting into the software results in a fresh re-write of those modem partitions.
At this point I factory resetted the OOS software (just to be safe) and also installed the stock recovery (somehow my device wasn't booting into TWRP everytime I installed it).
After the factory reset I checked my IMEI's and saw my IMEI2 as 0. Luckily I don't use slot 2 so getting it to show IMEI wasn't a priority. However my camera wasn't working. Everytime I opened up the camera it would show a black screen for 30 seconds and then close with a message showing "Unknown error"
At this point I tried searching the persist.img file that someone suggested in this thread. I downloaded that from google drive and clean flashed it thru fastboot.
After a reboot I was able to get the camera working again.
So all in all for now everything works as expected. I am on the latest OOS 3.1.0 software and have no intentions of doing anything else until there is fix for IMEI2. I am regularly checking oneplus forums where people like me have esclated the issues. I think on the recognized developers Naman is working for a fix and seeing into this issue.
TLDR : IMEI2 shows 0

ashu01 said:
can you join this telegram group link
https://telegram.me/joinchat/CbL5zUA-vInKg1B5M8baqQ
Click to expand...
Click to collapse
now new is problem started in my mobile telegram guys i able start d 2nd sim in my mobile but now sim 1 imei is 0

Rohanlovely said:
https://drive.google.com/file/d/0B9IqSEI0OM37RTM5M09Ib180U0E/view
I got it
Persist.img for oneplus 2
Click to expand...
Click to collapse
u tried it? works?

lockmunk said:
u tried it? works?
Click to expand...
Click to collapse
I tried and was fine.
First i did full wipe, then flash this zip + any rom and rom started fine.

pitrus- said:
Like I said, both SIM cards work again after flashing OOS 3.1 ROM (or firmware files manually) and then using the ordinary fastboot format command to format modemst1 and modemst2, then used fastboot flash persist persist.img with the persist partition dump found in this forum.
Click to expand...
Click to collapse
I get this error while trying to format modem
formatting 'modemst1' partition... Formatting is not supported for filesystem with type ''. FAILED ()
---------- Post added at 07:45 PM ---------- Previous post was at 07:43 PM ----------
rajatdixit said:
Hi,
Just to give you all a quick background. I was in the same situation as you. Flashed H2OS didn't like the jumpy signal therefore wanted to go back to OOS.
First boot of OOS resulted in no connectivity (no wifi, no data, no Bluetooth). I followed the method above and deleted modemst1 and modemst2 and formatted modemst (all done thru fastboot)
Once I did that I was able to boot into OOS to get the signals. As petris said above, wiping and then booting into the software results in a fresh re-write of those modem partitions.
At this point I factory resetted the OOS software (just to be safe) and also installed the stock recovery (somehow my device wasn't booting into TWRP everytime I installed it).
After the factory reset I checked my IMEI's and saw my IMEI2 as 0. Luckily I don't use slot 2 so getting it to show IMEI wasn't a priority. However my camera wasn't working. Everytime I opened up the camera it would show a black screen for 30 seconds and then close with a message showing "Unknown error"
At this point I tried searching the persist.img file that someone suggested in this thread. I downloaded that from google drive and clean flashed it thru fastboot.
After a reboot I was able to get the camera working again.
So all in all for now everything works as expected. I am on the latest OOS 3.1.0 software and have no intentions of doing anything else until there is fix for IMEI2. I am regularly checking oneplus forums where people like me have esclated the issues. I think on the recognized developers Naman is working for a fix and seeing into this issue.
TLDR : IMEI2 shows 0
Click to expand...
Click to collapse
Did u get such type of an error:
formatting 'modemst1' partition... Formatting is not supported for filesystem with type ''. FAILED ()
If not just tel me the steps u followed

ashokmor007 said:
I get this error while trying to format modem
formatting 'modemst1' partition... Formatting is not supported for filesystem with type ''. FAILED ()
---------- Post added at 07:45 PM ---------- Previous post was at 07:43 PM ----------
Did u get such type of an error:
formatting 'modemst1' partition... Formatting is not supported for filesystem with type ''. FAILED ()
If not just tel me the steps u followed
Click to expand...
Click to collapse
Make sure your bootloader is unlocked

rajatdixit said:
Make sure your bootloader is unlocked
Click to expand...
Click to collapse
yes it is unlocked