EDIT: SOLVED. Sorry, please ignore
I am using TWRP, I factory reset fine.
I then lined up 3 zip files to flash. CM10.1, Gapps and Cerberus
The screen turned off while flashing and I panicked. It wouldnt turn on again. I'm thinking it was because of the screen off delay.
I panicked and pushed all of the buttons several times but couldn't get the screen to turn on again.
Now I've turned off the screen off delay and now I'm trying to re install CM but it keeps getting the following
E: Unable to mount ' /system '
I can still access TWRP recovery and Download.
Is there any way to restore the partitions?
--------------------------------------------------------
Edit from here on:
I was able to recover the partitions by downloading this following PIT file:
http://d-h.st/v7C
I used it with ODIN, I put my phone in download mode and put pushed the PIT file onto my phone, which fixed the partitions. From there I was able to just install CM10.1 like normal
Related
This morning my phone crashed while I was trying to run gReader. Upon reboot, the phone would just hang at a black screen after the initial SGS Logo.
I decided to recover and put the device into download mode, launched ODIN and tried to flash JP3, JM5 and JG8, all to no avail. At the reboot after ODIN is complete I get the Samsung recovery utilities and then an error message as follows:
Update media please wait ...
E:Can't Mount /dev/blk/mmcblk0p1 (invalid argument)
E:copy_dbdata_media: Can't mount SDCARD:
copy default media content failed
Trying to format the internal SDCARD from Recovery Utils gives the same error
I am stuck! Any ideas?
that's beyond me.
you got into download mode, that's good
but when flashing you get that error, that's not good
did you use the 1 click lag fix?
never mind i see your siggy you were on Modaco rom... hmm...
try Odin-ing a stock ROM, and see if that fixes your phone?
then Odin back whatever is your custom ROM
You are further through the flash process than I was when I ran into problems, plus have a Vibrant over a European Galaxy S - but I'd still try a 'blank' flash with Odin. Enter download mode, connect up and let Odin run without any files linked in. This got me back into the phone and then allowed for a proper new fw flash thereafter.
No matter what I did I could not get the internal SDCARD recognized. A trip to the Bell store and a DOA swap and now I have a new device.
Any update on how to fix this?
Edit: All happy now, a change of pc solved the problem of not detecting the device!
Hi all! I have another challenge for you!
Right, I've got myself in a tizz with my Defy +. While updating between CM10.1 versions I found myself in a situation where I couldn't get past the boot animation. So I loaded the TWRP restore I had made prior to updating...
Except it wouldn't, instead it came up with 'Failed' each time I tried any of the TWRP backups I had created. So the next step was to wipe partitions and start flashing various ROMs until I found one what worked. Except they didn't work either. Eventually I thought the best idea would be to just turn the phone off and see where I was with booting.
So power on, boot logo, blue light, red light then... nothing. Just the boot logo static. Went into the custom bootloader to go into recovery again, nothing. Pressing Custom recovery simply loops back to the top bootloader screen.
Ok next step, flash .sbf and start from scratch. So into the Moto bootloader it is to plug in and flash except... it's no longer detected by my computer.
"Ok" I think, "We'll just flash files from the SD card after I use an external SD card reader.
Except now when I enter Moto recovery to flash the TWRP recovery I get:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verifiaion failed
Installation aborted
So to recap:
1) Tried to flash and update, failed
2) Tried to recover, recoveries wouldn't write (I think this is becaue I'd changed to EXT4 on /data and /cache and had forgotten to go back to EXT3 before trying to recover)
3) Tried to boot, epicly failed
4) Tried to flash .sbf, Defy+ won't appear in RSDLite 5.7 with latest driver
5) Tried to flash from SD card, sig verification failed
6) Googletastic for the last four days
Notes:
a) I CAN charge the Defy+ using the wall charger but I get '?' for the battery level indicator but...
b) In Cmod bootloader 2.1 (Which I can use a little) it shows the correct battery level
c) I /was/ getting some errors with not being able to mount /cache from the moto recovery but I've since used the cmod bootmenu 2.1 to set it back to ext3 and it's all happy now, those errors aren't appearing
d) Plugging in my Defy red lens I get W8 x64 detecting the correct portal drivers and such but when I go to moto bootloader this device also doesn't appear in RSDLite
e) Both devices prompt windows to install a Motorola Flash Interface driver in Device Manager when plugged in in moto bootloader mode and neither device appears in RSDLite despite the fact the program is running in Admin mode
f) Looking at the logs in bootloader, it appears that I might not have formatted anything from ext4 to 3, everything I select in the cmod bootmenu returns .E:Error in /system/... , (Result: Invalid arguement) , Done..
So at the moment I think I need to acheive one of the following:
1) Find a file that allows me to write any useful data to /system like a recovery or some of those bootmenu files that passes the signature verification
2) Find a way to troubleshoot RSDLite so I can actually flash .sbf and get out of this hellhole
Many regards!
Alexis
If your custom recovery is not working, then you cannot do anything other than flash an sbf(nothing except data and cache wipe can be done via stock recovery): this is due to the locked boot loader(recoveries cannot be simply flashed from the stock recovery as you're trying to do)
Sent from my MB526 using Tapatalk 2
Success (ish)!
Yes I swapped to a different machine and then upgraded the version of RSD Lite installed on it from 4.7 to 6.1.5
[URL="http://forum.gsmhosting.com/vbb/f166/rsdlite-6-0-mtk-patch20-rsd-lite-6-0-a-1545012/index2.html#post8988239"]http://forum.gsmhosting.com/vbb/f166/rsdlite-6-0-mtk-patch20-rsd-lite-6-0-a-1545012/index2.html#post8988239
And flashed the 'lower' of the two .sbf's from the links on this forum for the British variant. After a DEA1 error (Phone is dead, code corrupt and all the bad things) I managed to flash the file.
As of yet I've not managed to get out of the bootloop but I've not carried out the requisite steps as mentioned in the "So you think you've bricked your Defy/Defy+" thread.
Lessons learned:
1) Motorola drivers and RSD Lite are pennickety, you will probably need to mix them up in order to get them to behave properly
2) If all else fails, use a different computer
3) You will probably need to flash over and over, while making every effort to not muck them up. Be aware the efuse system only has limited uses before it's useless though...
My saga continues, from no USB support hopefully to a fully working device again
In the end switching PC then doing the factory reset from moto recovery let the phone boot, all standard but the dodgy USB stuff at the first post is what sent me away from the right track.
Hello
I think the phone is bricked but I'm trying anyway...
Only adb is working but i can't copy zip file on the phone
"failed to copy 'LG-G2_D802-StockMOD_v1-01.zip' to '/sdcard/rom.zip': I/O error"
It works for small files... great
Everytime I reboot in recovery mode it's like he lost everything on sdcard, even on / if I put a zip, nothing stay after a reboot
If I put CM in / for exemple and I try to flash it I've got :
Updating partition details....
E:Mount: Unable to find partition for path '/cm.zip'
Error flashing zip
Updating partition details....
If you can go to download mode, just go back to stock. In general section.
Can't back to Download mode :/
Hello,
I have been trying to flash android 5.1.1 factory image onto my Nexus 7 (nakasi-grouper). It is unlocked and I have the factory image zip file pushed onto the /sdcard/ folder using adb. But when it tried to install it, it gives me an error message saying:
Error: Unable to mount /data /cache /system ( i am unable to mount System/Cache/Data from TWRP either)
I have tried multiple methods going through different threads form your website (which is awesome btw! ), but everything fails.
Flashing through fastboot and Nexus Tool kit (Wugs) from PC , gets interrupted at Failed to write boot-loader -- writing system...... and the device switches off automatically. And when i turn it on again, the process fails.
Finally I have tried to factory reset it, it took a whole night but it is still stuck at: Formatting Cache using make_ext4fs function. I am considerably new to android and I have no clue how to proceed from here. Any help is much appreciated!
here's the backstory
i was trying to install HavocOS but failed multiple times.. always stuck in twrp after i installed GApps.. then i remember i tried to flash the HavocOS rom before the stock firmware.. then it shut off for a second and now i'm stuck in twrp with unable to mount /data and unable to mount storage error
and now here's the situation
1. i can't flash any rom/zip files (turn off for a second then back to twrp)
2. i can't transfer any file to internal (not detected on pc)
3. i can't mount data
4. i can't wipe internal
5. i can't wipe data
6. error unable to mount /data and unable to mount storage on everything
7. i can't get into fastboot
8. i'm stuck in twrp
anybody know how to fix it? :crying:
SagenKrieg said:
here's the backstory
i was trying to install HavocOS but failed multiple times.. always stuck in twrp after i installed GApps.. then i remember i tried to flash the HavocOS rom before the stock firmware.. then it shut off for a second and now i'm stuck in twrp with unable to mount /data and unable to mount storage error
and now here's the situation
1. i can't flash any rom/zip files (turn off for a second then back to twrp)
2. i can't transfer any file to internal (not detected on pc)
3. i can't mount data
4. i can't wipe internal
5. i can't wipe data
6. error unable to mount /data and unable to mount storage on everything
7. i can't get into fastboot
8. i'm stuck in twrp
anybody know how to fix it? :crying:
Click to expand...
Click to collapse
have you tried reboot to bootloader option under reboot in twrp
SagenKrieg said:
here's the backstory
i was trying to install HavocOS but failed multiple times.. always stuck in twrp after i installed GApps.. then i remember i tried to flash the HavocOS rom before the stock firmware.. then it shut off for a second and now i'm stuck in twrp with unable to mount /data and unable to mount storage error
and now here's the situation
1. i can't flash any rom/zip files (turn off for a second then back to twrp)
2. i can't transfer any file to internal (not detected on pc)
3. i can't mount data
4. i can't wipe internal
5. i can't wipe data
6. error unable to mount /data and unable to mount storage on everything
7. i can't get into fastboot
8. i'm stuck in twrp
anybody know how to fix it? :crying:
Click to expand...
Click to collapse
Flash stock rom via fastboot.
And try to reboot to bootloader from twrp it'll put you in fastboot mode.
SagenKrieg said:
here's the backstory
i was trying to install HavocOS but failed multiple times.. always stuck in twrp after i installed GApps.. then i remember i tried to flash the HavocOS rom before the stock firmware.. then it shut off for a second and now i'm stuck in twrp with unable to mount /data and unable to mount storage error
and now here's the situation
1. i can't flash any rom/zip files (turn off for a second then back to twrp)
2. i can't transfer any file to internal (not detected on pc)
3. i can't mount data
4. i can't wipe internal
5. i can't wipe data
6. error unable to mount /data and unable to mount storage on everything
7. i can't get into fastboot
8. i'm stuck in twrp
anybody know how to fix it? :crying:
Click to expand...
Click to collapse
1. install the drivers again https://androidfilehost.com/?fid=890278863836289045 hope now it may connect to pc
2. check that, to reboot to fastboot mode (i kno u said abv, but just do a try.) try to reboot fastboot mode from twrp
3. download https://androidfilehost.com/?fid=11410963190603882446
4. Open firmware folder and click on flashall_AFT.cmd & wait
5. i cant say itil work just giv a try
ajayravi1122 said:
1. install the drivers again https://androidfilehost.com/?fid=890278863836289045 hope now it may connect to pc
2. check that, to reboot to fastboot mode (i kno u said abv, but just do a try.) try to reboot fastboot mode from twrp
3. download https://androidfilehost.com/?fid=11410963190603882446
4. Open firmware folder and click on flashall_AFT.cmd & wait
5. i cant say itil work just giv a try
Click to expand...
Click to collapse
That's what I told the person to do in short he/she didn't respond.
He/she should update the thread whether he/she got it working by doing something or fixed it via service center. Others just try to help without knowing if it is needed or not.
First of all, i want to say i'm sorry to all of you.. especially for those who tried to help me by replying my thread. I'm sorry for being silent and not updating on you guys. I managed to figure it out the next day after i posted this thread before any of you replied and just kinda forget this thread- which is a bad thing to do. I'm sorry guys. I won't do that ever again.
With that out of the way, i'm going to answer all of your replies
ajmalhussainhy said:
have you tried reboot to bootloader option under reboot in twrp
Click to expand...
Click to collapse
I tried that, it didn't work. Either reboot to system or bootloader, it just went back to TWRP.. with the "Keep System Read Only?" thing.. acting like i just installed TWRP for the first time. Even when i chose to turn off the device, it came back to TWRP.
z1_nile said:
Flash stock rom via fastboot.
And try to reboot to bootloader from twrp it'll put you in fastboot mode.
Click to expand...
Click to collapse
As i specified in my first post, i can't get into fastboot. Totally stuck in TWRP.
ajayravi1122 said:
1. install the drivers again https://androidfilehost.com/?fid=890278863836289045 hope now it may connect to pc
2. check that, to reboot to fastboot mode (i kno u said abv, but just do a try.) try to reboot fastboot mode from twrp
3. download https://androidfilehost.com/?fid=11410963190603882446
4. Open firmware folder and click on flashall_AFT.cmd & wait
5. i cant say itil work just giv a try
Click to expand...
Click to collapse
Didn't try that one, because as i said i've figured it out the next morning.
z1_nile said:
That's what I told the person to do in short he/she didn't respond.
He/she should update the thread whether he/she got it working by doing something or fixed it via service center. Others just try to help without knowing if it is needed or not.
Click to expand...
Click to collapse
Again, sorry for that
Here's what i did to fix the issue :
1. After some more searching in the next morning (literally the next morning, few minutes before i gone to school), i stumbled to this thread post : https://forum.xda-developers.com/showthread.php?t=2522426
it says that if you "Put the phone under a strong light and longpress power and volume down, your phone will reboot in bootloader.".
So i tried that. I hold my phone right in front of my monitor, then hold the power and volume up to get into fastboot mode. And Voila, it worked. I get into fastboot without any problem whatsoever.
Somebody else also replied "Just hold the power and volume down for a long time and hold it in front of a bright light, something about the proximity sensor."
So.. yeah. Didn't really know how it worked out, but it worked. :silly:
2. After that, i just installed a different version of TWRP (This one specifically https://dl.wafuu.id/twrp/X00T/twrp-3.2.3-0-X00T-20181214.img which i got from someone in the telegram group) and just redo the HavocOS installing process. It went smooth, and i manage to boot the system without any problem.
Problem solved. Just like that. However, i think i know what was causing the issue.
When i was trying to install the GApps (before stuck in bootloop), i only managed to get to the part when i had to choose to either save my choices or not. After that it just went back to TWRP. I didn't know that it wasn't actually installed yet, because i thought it was installed already. Yep, that was my first time installing GApps and i actually never seen the entire installing process. The way i know that is when i installed it after the fix (after i installed a different TWRP) and then saw the "installing things" part. Silly me.
So i think that was the issue. It was because i used an older version of TWRP which i got from this thread https://forum.xda-developers.com/asus-zenfone-max-pro-m1/development/recovery-twrp-3-2-1-x-t3787134 . Maybe GApps didn't support that version. I knew it was an old version of TWRP. Why i was using that version and not the latest one? Because when i tried to install the latest one from this thread https://forum.xda-developers.com/as...ent/recovery-unofficial-twrp-3-2-3-0-t3888110 , it didn't work on my phone. It fails to detect my internal memory (0mb).
I think that's all i can say. Again, i'm sorry to all you guys for the late respond. Thank you for replying my thread and trying to help me. I hope this thread will eventually help someone who faced a similar problem to mine.
*Last but not least, Shout out to Dyruz from the telegram group who provided me the working TWRP and tried to help me as best as he can. I would've not fix the issue this because of him. Cheers!