So i have unlocked my bootloader, rooted my Honor 8, and attempted to flash a Custom rom to my device. when following the directions to wipe and format data, i some how completely wiped my internal storage of my phone, and can only boot into recovery, no matter how many times i flash the ROM i always get a failure to install due to there being nothing in my internal storage.
it will not mount the data.
hopefully this isnt a perm brick. please let me know what direction to take to fix this!!!!
thanks in advance.
i some how fixed my error and got my rom to boot up successfully please close thread, sorry for a panicked post
Related
I rooted the phone following the steps here on the xda thread and I tried afterwards upgrading the firmware to ics. I followed these instructions http://www.android.gs/update-htc-one...-firmware-rom/ and afterwards my phone just keeps restarting and restarting. I didn't make a recover image because I was too confident that it was going to work. Afterwards I panicked and pressed factory reset, thinking everything will turn back to normal. I lost all the files I saved onto the sd card and I don't know what to do now. I can't even use the all in one kit. Please help, I greatly appreciate it
If you can't get into bootloader/fastboot anymore, you're bricked. I would not know how to revive it. Otherwise, you're not bricked.
You need a functioning recovery. You can flash it in fastboot if you're unlocked.
If you have successfully flashed a recovery but you can't boot into recovery, try erasing your cache from fastboot:
fastboot erase cache
If you can boot into fastboot, make sure you can mount your sdcard partition. I don't mean mount it onto your computer over USB, but just mount it onto the root filesystem.
If you can not mout your sdcard partition, go to the sticky in Q&A on fixing unmountable sdcard. It involves flashing a stock recovery and clearing storage in bootloader. If you had to do this, flash your custom recovery back and confirm you can now mount your sdcard partition.
Now that you have a functioning recovery and a mountable sdcard, you're good to adb push a rom to your sdcard and flash it in recovery. I suggest you format system, data, and cache first. You probably need to flash the boot image that comes with the rom from fastboot.
-Jobo
Hi All,
I have the Telstra HTC One XL, and have just recently attempted to install CM10 ROM - however have run into some problems that I would appreciate some advice to rectify. I had recently updated to Jelly Bean OTA.
I followed the guide on these forums - http://forum.xda-developers.com/showthread.php?t=1859478
I Successfully unlocked bootloader by following the steps at HTCdev.com
I Successfully installed TWRP Custom Recovery
I Downloaded CM10 as per - http://forum.xda-developers.com/showthread.php?t=1790032. I transferred this as well as Google Apps onto my phones storage.
When attempting to install CM10, I created the Nandroid backup as recommended, and proceeded to wipe the mentioned items using TWRP (a guide I saw said to wipe everything). This is when my Nandroid back-up got wiped. TWRP gives you the option to wipe cache, delvik cache, factory reset, system, external storage, internal storage and format data. I did alll of these, and this was my mistake I believe? I proceeded to try and install CM10 and gapps from internal storage (I had to re load these back on after I wiped everything), and the install of CM10 displayed as successful.
Upon rebooting to system, the HTC screen comes up first and then goes to the CM10 animation. The phone then stays on this animation (rotating circle) for up to 10-15 minutes.
I have read thread after thread with people experiencing similar issues, and have tried rectifying my problem with various versions of roms and different guides out there. I can still boot into recovery (TWRP) mode via bootloader, and this means I can still mount my phone's storage onto my PC and have access to the storage directory. As I have deleted the Nandroid backup though, and because the ROM's won't install, I am stuck in no man's land.
There must surely be a way to have a ROM installed (even if its back to stock Telstra) from the position I am in, it would be greatly appreciated if someone may be able to point me in the right direction.
Thanks,
Robbie
maybe yall need to "fastboot flash boot boot.img" now
robbie.d said:
TWRP gives you the option to wipe cache, delvik cache, factory reset, system, external storage, internal storage and format data. I did alll of these, and this was my mistake I believe?
Click to expand...
Click to collapse
Why do people keep doing this??? Just because TWRP gives you all those options, doesn't mean you should use them.
Sometimes, people will say to do a "full wipe" when flashing a ROM. But that term is a bit misleading. Factory reset (from TWRP, never from hboot), wipe Dalvik and wipe cache is all that is technically required when flashing a new ROM. Some people like to wipe more "just in case". But if you aren't completely confidant in what you are doing, keep in simple and don't make it more complicated than it needs to be.
I don't know if wiping everything is the cause of your woes, but it certainly didn't help, and caused you to do some extra steps.
Flash boot.img via fastboot as previously suggested. Otherwise, just try to re-download and flash the files agin. Its seems that some people are having troubles booting after flashing CM10 (even after doing the correct wipes and flashing boot.img). Doesn't seem to be much rhyme or reason, but just flashing again has fixed the problem for at least one person.
Thanks so much, such a simple fix! That has me booted up into CM10.
I have installed cm-10-20130107-NIGHTLY-evita and cm-10.0.0-evita , however with both of these versions, my touch screen is not working once it boots up. I can function with the volume up/down, and with the power buttons, but cannot get past my SIM card lock screen.
I noticed this thread http://forum.xda-developers.com/showthread.php?t=2083314 (no solution yet)...
Does anyone have a solution to this issue that seems a common one?
Alternatively, more than happy to get an alternative ROM on my phone in the interim...Can someone recommend me a ROM?
Again, I really appreciate the quick response to my problem, very happy my phone is in operation!
hello, last week i bricked my tf300, this is what happened...
i installed the energy rom along with the 4.2.1 bootloader, i was already using twrp 2.4.3.0 and it seemed to work fine for a while but then i had problems with a double screen after trying a different rom (cant remember which) anyway i tried the usual resets and wipes to to fix it but no joy. I then used the wipe data in bootloader thinking a full clean wipe would sort it but it just booted straight into twrp.
in twrp nothing will mount apart from system, ive used fastboot to flash various stock blobs, proper twrp img etc but even tho fastboot said everything flashed ok, i still boot into the old twrp which wont mount anything apart from system.
i then got an old 8 gig sd card and put stock roms and energy rom on root of the sd card , in twrp i mounted system but cant mount cache, data or sd card but strangely, i was able to copy the above roms from the sd card and move them to the mounted system partition which i was then able to install the energy rom with aroma installer , happy days i thought until after installation it rebooted straight to twrp again asking for password?
when i try to install stock roms by the above method it fails because cache isnt mounted. i think the twrp is corrupted, how do i fix this?
could someone with the know how tell me what im doing wrong,? should i full wipe again? should i wipe the twrp and how do i do this?
i am sort of a newb to this and any advice would be great
First things first, I'm a newbie when it comes to all these.
I installed CM11 after much effort, but some things didn't work out well so afterwards, I installed CM12.1* (FXP-cm-11-20150301-UNOFFICIAL-taoshan).* But then I decided that I wanted to change my Gapps Package, so I went to recovery mode once again to wipe my phone and install CM12 all over again.
The thing is that for some reason I just couldn't wipe it (no error message) but I was able to log in back to the system (CM12).
I messed around with a few settings and finally I decided to install twrp 2.8.7.0 through the flashify app. I rebooted to recovery, tried to wipe again my phone and then, all hell broke loose.
I realized that I cannot wipe internal memory of all things, and cannot install any new ROM. Can't flash another recovery either through windows flashtool like CWM 6.0 Philz touch, for example. Well, it does flash but my phone keeps on logging into the twrp recovery. I also can't flash my original fft (obviously). I can't do really anything besides messing around with twrp options (and I've messed a lot with them). I'm all out of ideas, so please someone help. When trying to wipe internal storage, the following message appears:
E:mkdosfs /dev/block/mmcblk0p32 process ended with ERROR=1
E:Unable to wipe '/sdcard'.
E:Unknown MTP message type: 1
E:Unable to wipe '/sdcard'
I have the whole log, for anyone interested.
Please help and remember, I'm a newbie.
Thank you.
immortalwind said:
First things first, I'm a newbie when it comes to all these.
I installed CM11 after much effort, but some things didn't work out well so afterwards, I installed CM12.1*(FXP-cm-11-20150301-UNOFFICIAL-taoshan).* But then I decided that I wanted to change my Gapps Package, so I went to recovery mode once again to wipe my phone and install CM12 all over again.
The thing is that for some reason I just couldn't wipe it (no error message) but I was able to log in back to the system (CM12).
I messed around with a few settings and finally I decided to install twrp 2.8.7.0 through the flashify app. I rebooted to recovery, tried to wipe again my phone and then, all hell broke loose.
I realized that I cannot wipe internal memory of all things, and cannot install any new ROM. Can't flash another recovery either through windows flashtool like CWM 6.0 Philz touch, for example. Well, it does flash but my phone keeps on logging into the twrp recovery. I also can't flash my original fft (obviously). I can't do really anything besides messing around with twrp options (and I've messed a lot with them). I'm all out of ideas, so please someone help. When trying to wipe internal storage, the following message appears:
E:mkdosfs /dev/block/mmcblk0p32 process ended with ERROR=1
E:Unable to wipe '/sdcard'.
E:Unknown MTP message type: 1
E:Unable to wipe '/sdcard'
I have the whole log, for anyone interested.
Please help and remember, I'm a newbie.
Thank you.
Click to expand...
Click to collapse
try wipe->advanced wipe -> change fs -> ext4
SdtBarbarossa said:
try wipe->advanced wipe -> change fs -> ext4
Click to expand...
Click to collapse
Thank you for your answer my friend, but I actually managed to fix my problem just moments before you posted your answer! What I did was to flash the cm12.1 recovery nightly which logged me into this recovery (although it seemed all messed up and.. broken). Nevertheless, I managed to flash the CM12.1 ROM from there and everything worked fine!
Bro #immortalwind.. I'm having the same problem exactly what you had. Seriously fu***d up with all with boot loop @ recovery. Could not able to hard reset / factory reset at neither CWM nor TWRP. Tried all knows possible ways. Please could you help me here. Any1 who can halp me here pls...
P.S: literally not moving from the boot load, so flashing a ROM could not be possible i think. any other suggestions please.....
RaamXperiaL said:
Bro #immortalwind.. I'm having the same problem exactly what you had. Seriously fu***d up with all with boot loop @ recovery. Could not able to hard reset / factory reset at neither CWM nor TWRP. Tried all knows possible ways. Please could you help me here. Any1 who can halp me here pls...
P.S: literally not moving from the boot load, so flashing a ROM could not be possible i think. any other suggestions please.....
Click to expand...
Click to collapse
Try this out
RaamXperiaL said:
Bro #immortalwind.. I'm having the same problem exactly what you had. Seriously fu***d up with all with boot loop @ recovery. Could not able to hard reset / factory reset at neither CWM nor TWRP. Tried all knows possible ways. Please could you help me here. Any1 who can halp me here pls...
P.S: literally not moving from the boot load, so flashing a ROM could not be possible i think. any other suggestions please.....
Click to expand...
Click to collapse
Just reflash stock ftf. You'll be good to go. If that fails, check drivers and downgrade flashtool. After that, normally, install a boot image with a recovery, install your rom gapps, reboot.
Managed to flash.ftf... Thanks for the help friends.
Sent from my C2104 using XDA Free mobile app
Hello, thanks for your help.
It seems I bricked my galaxy s7 while trying to format the /data partition.
I installed TWRP 3.2 and a custom rom, and everything went smoothly until then.
I tried installing an audio mod which throwed a " can't mount /data" error, searching for solutions I read that formatting the data partition to fat and back to ext4 should solve the problem, I tried formatting it to fat with TWRP, however on the first try I got a message that it suceeded, followed by a message that /data could not be mounted, TWRP seemed to be still working (there was no reboot button or any other buttons, just a "working" bar). After giving the phone 3 hours I decided to restart it, now I can't access TWRP; it stays on it's "splashcreen", and of course the phone won't boot.
I'm having a rough time with this so I will appreciate it a lot if you can help me.
Thank you.
Boot to download mode, flash stock firmware using Odin, then retry the TWRP installation.
For wiping data, you have to make sure you use the wipe option that makes you type out 'yes' to wipe, the other factory wipe methods don't actually properly wipe the partition.
iirc you also then need to flash the dm no verity zip from the TWRP thread.
Bro you didn't have to do anything but just formating the phone in the first place. Aassuming you're on oreo , it happens to a lot of people and myself, after flashing a kernel twrp was unable to munt data, all i had to do is a data format in twrp that fixed the problem .