Hey,
A friend gave me his Galaxy S after another friend of him got it into this following state (I'm not sure what exactly he did or tried to do):
The phone is stuck in a boot loop, sometimes it shows the first frame of the boot animation for a second before booting again. When I start it in recovery mode (Android System Recovery (3e)) I get this error messages:
Code:
-- Copying media files...
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:can't mount /sdcard
your storage not prepared yet. please use UI menu
for format and reboot actions
The phone does not have an SD card in it.
After reflashing with the same firmware as original, I get these errors:
Code:
-- Copying media files...
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:can't mount /sdcard
your storage not prepared yet. please use UI menu
for format and reboot actions
meida files copy failed.
-- Wiping data...
Formatting /data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
Formatting /cache...
Deleting Meta Data
Data wipe failed.
I've tried flashing different firmwares too, including rooted ones, and the results were the same except for a case where the first error was about not being about to mount mmcblk0p1 instead of sdcard, and another case where another firmware cause the phone to appear to boot, but after a minute or too it got stuck on a black screen and stopped responding.
I followed many different guides on how to fix similar problems, but none of them actually worked.
Please help, thanks a loooot in advance.
http://forum.xda-developers.com/showthread.php?t=1134975
Maybe it will help?
Thanks for the reply. Solutions 1-3 are irrelevant, as I can get into download mode, but even after flashing, any version, the problem is still there. I tried solution 4 (dbdata flash), but it doesn't solve anything. Are there any other partitions I can flash and might be able to solve this?
Ok, next thread
http://forum.xda-developers.com/showthread.php?t=1069867
Maybe here is solution?
Tried flashing the files there and no luck, still the same error. =/
I sent Faria, who said he has tools for solving this problem in that topic a PM, hopefully he'll share his tools with the community.
Meanwhile, I don't mind trying different solutions.
I also noticed something – if I keep the phone in the boot loop for a long time, it will eventually get to either a loop of the carrier boot animation (Which normally doesn't loop), or actually boot for one time. (When it booted I tried to power it off and see if it would boot again normally, and it didn't =/)
i have this kind of error few months ago, what i do was, flash pit file only with repartition, then flash pda, phone & csc.... agn flash this dbdata.rfs file, should fix the issue.
Just tried it, no luck, exactly the same error as before. =/
ops... sorry to heard that, at least it work for me but too bad not for u.....
I have the exact same error message and problem . Really hope someone can find a fix for this because I've spent hours and hours
Yep, EXACTLY same problem as OP and NO fixes for me yet. Tried everything from this thread and other threads. Let's see who's the real king of knowledge who can fix this.
any luck with this issue?
In my case it was solved by Click, but as in thread: for some people it works with repartition, while for some - without.
Or, try it Here I'd pay attention to page 2, Darky's resurrection... maybe looking for newer version at Darkyrom.
spamtrash said:
In my case it was solved by Click, but as in thread: for some people it works with repartition, while for some - without.
Or, try it Here I'd pay attention to page 2, Darky's resurrection... maybe looking for newer version at Darkyrom.
Click to expand...
Click to collapse
thank you spamtrash.
i tried all this various methods. i was able to boot into android but after reboot, it never got into android anymore. stuck in boot loops. ill try Darky's resurrection now, its the last option i havent tried yet. i cant believe there are no scripts or smth to fix and rebuild file system in such cases.
ambrozic said:
thank you spamtrash.
i tried all this various methods. i was able to boot into android but after reboot, it never got into android anymore. stuck in boot loops. ill try Darky's resurrection now, its the last option i havent tried yet. i cant believe there are no scripts or smth to fix and rebuild file system in such cases.
Click to expand...
Click to collapse
Any Luck????????
I'd be interested with results as well. As last hope, you can try http://forum.xda-developers.com/showthread.php?t=1330491 this one, but it requires hardware mod...
Sent from tam-tam drum
any update or fix?
Someone found any fix for this?
Yep!
Hi guys!
Yep - probably I found the solution. One month ago I have bought i9000 with this problem (as broken). Finally I managed to start that SGS and even install ICS on it. The problem is (as I suppose) that internal flash memory is broken and You have to move /data partition to external SD card. So some flashes, some changes in files and repartitioning of SD card does the thing.
Currenty I am in the middle of preparing a tutorial to be pushed on YT to show how I managed to solve the problem. Stay tuned
Best regards
this is a hope.. =)=)=) please send me a tutorial. thanks
Ready
So.
Finally I had some time to add voice recording to my movie and volia - is ready.
I hope it will help at least somehow.
I am not sure if this manual will help in Your case(s), but it might be at least a hint
Best regards
Fteller.
^ So, umm, where's the link for your YT video? Thanks.
Related
Hi, i am a newbie of Android. i flashed my Captivate to I9000ZSJPD, but found that the rotation has some problem. So, i tried to flashed other different rom many many times and try to fix up. I believe i make sometime wrong in between and bricked my phone... anyway, i tried to fix it by ADB in download mode
And now, it will going to recovery mode in opening...
and show:
_______________________________________________
update media, please wait
E:Can't mount /dev/block/st110
(Invalid argument)
E:copy_dbdata_media:Cant's mount
your storage not prepared yet, please use UI me
nu for format and reboot actions
copy default media content failed
_______________________________________________
(I tried to flash I9000TGYJH1, I9000XXJP3, I9000XWJP6, I9000XXJPM, but still show it when starting)
i guess i need to format internal sd-card??? however, in this kernel,
The screen show "Enter: OK Key", but my Captivate seem no "OK Key", and all keys are not working except UP and DOWN....
if i reinstall "kernel-captivate-stock.tar.md5", it can be use "power key" to choice, but no format, or wipe data/factory rest option....
What should i do? Pls help me...
Try and Odin 1-click back to stock. Sounds like you might've had a lag-fix installed and you can't format the internal SDCard.
Odin should overwrite and format it starting you off fresh.
Either way.. your not totally screwed yet. Keep plugging away.
Thanks so much Avgjoegeek!, it's work again!
I am having the exact same problem on Rogers 896. I have tried the ODIN 1-click but it just seems to hang on either the Master Clear or the Rom flash. How long should it take? It seems fairly straightforward, am I missing something?
I had experiencing a problem with my SGS I9000 wherein I could not completely delete anything that had been installed on my phones internal memory... be it applications \ videos \ images \ etc ... I say completely because it did used to tell me that the contents have been deleted when done in KIES and when I had done a factory reset \ formatted my storage... But the contents kept reappearing everytime my phone started up again... Tired of this I decided to flash my phone using Odin3.
My Phone's specs at that time were (had updated to Gingerbread fro Froyo through Kies):
PDA: I9000DDJV6
Phone: I9000DDJV4
CSC: I9000ODDJV6
Now, I've tried flashing using multiple firmware versions... started with the stock DDJV6 version I found here... http://forum.xda-developers.com/showthread.php?t=846913 ... and followed all instructions on how to use Odin while flashing using PIT 512...
This sent my phone first into a continual boot cycle... I was able to get into the Download Mode again after a few attempts and then, I tried flashing again with the Gingerbread firmware 2.3.3 given here
http://androidadvices.com/update-samsung-galaxy-s-gt-i9000-stable-gingerbread-xxjvk/ ...
and when that failed too... I also tried Gingerbread version 2.3.5 .. which was given here...
http://androidadvices.com/update-samsung-galaxy-gt-i9000-xxjvs-gingerbread-235-firmware/3/
Now, I problem I face is... though am able to flash the rom, I keep getting a whole bunch of Force Close error messages when the phones boots up...
(I've attached some images of the error message I am getting...)
I read somewhere that should be getting the standard setup options such as the Google registration page and language options once the flashing is completed... but I don't get that page at all... I just keep getting error messages as the phone reboots!
I've also restarted the phone in Recovery mode (Vol Up + Home + Power) to delete cache files and stuff... but that doesn't help either... I can't seem to understand what step am I missing... I must have tried flashing my phone like a dozen times since yesterday but the problem persists...
I would appreciate if you all could help me out of this problem.
Regards,
Vishal
and if it helps, all data including the Apps and other stuff continute to stay on my phone and haven't been deleted... I had checked 'Re-Partition' in Odin3 hoping it would reformat the storage.
I have the same issue! Stuffed if i can find the solution anywhere... Ill keep an eye and ear out though and if i find a fix elsewhere ill let u know here.
Maybe a silly idea but have you tried another a version above odin 1.3? there is 1.7 and 1.8...
Also another silly thing.. You say you can flash the rom's, does that mean you have custom recovery and tried wipe from there as well...
Go into recovery and do a factory reset.. if u haven't already
Sent from my GT-I9000 using XDA Premium App
Factory reset from recovery menu didn't work for me. Appears to say/do all the right things in the yellow text, but end result is exactly the same as it was. Will try higher Odin versions tonight.
Re:
Thanks for your response everyone.
The Reset option doesn't work for me either... Tried this through the 'Privacy' menu ... as well as getting into the Recovery Mode using the Vol Up + Menu + Start button combination... Please let me know if I've missed any other way to factory reset\wipe the data...
Odin versions... I've used the older version (1.3?) as well as 1.7 ... have also tried using pit 803... but to no avail...
The fact that I can't delete any content on the internal storage drive may mean that it might have got corrupted and may need a replacement?
I am new to this and hence might sound like a noob but I appreciate your patience...
Everyone starts as a noob or beginner, so there are no silly questions.
To totally reset your phone and clear everything off of it you can use the dialer code *2767*3855# : this will delete everything that has been added from your side, including all of your files!
BUT : you should be aware that the formatting starts immediately after you type in the last '#' without getting asked if you really want to wipe everything, so be careful.
Same here; Odin 1.7 didn't alter result. Nor does entering reset code in dialler...
Re:
The other day, I tried to flash the stock rom using the PDA file only... The procedure I followed was... Opened Odin, added PIT 512 and checked Re-Partition, added the DDJV6 PDA file... Hit Start... The process completed and as my phone rebooted again, it went into Recovery and threw up the following error messages:
E: copy_dbdata_media: Can't mount /cache your storage not prepared yet.
E: failed to mount /cache (Invalid Argument)
E: Can't mount /cache/recovery/recovery_kernel_log
E: copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
Upon clicking 'wipe data/factory reset'
E: format_volume: rfs format failed on /dev/block/stl11
Does this indicate something?
And, I do keep getting the force close error messages as well... and some of them are for applications like Titanium Backup and Read It Later... which have already been uninstalled .. but they still seem to exist in the phone's memory...
No idea if this will work but I was recently guided to this thread and it maybe of help to you because it says that it brings you back to a proper base... read the last 5 pages as this is usually recommended in long threads and obviously the whole of the first page. The thread I mean is the one where it says efs recovery below
Re:
Thanks Talon, I will surely try this out!
There's a guy who had a similar problem as mine and he seemed to have solved it by flashing EZBase-4.0.7z ... so perhaps it might help me as well... currently on download... will let you know how it went!
Re:
Flashing with EZBase hasn't got rid of the Force Close error messages... I get tonnes of them... for almost everything from android.phone to even applications which I had uninstalled several times but they just mysteriously come back .... everytime I flash...
Do I need to get root access before I can perform a clean flash... as in, with no force close messages?
vish123 said:
The other day, I tried to flash the stock rom using the PDA file only... The procedure I followed was... Opened Odin, added PIT 512 and checked Re-Partition, added the DDJV6 PDA file... Hit Start... The process completed and as my phone rebooted again, it went into Recovery and threw up the following error messages:
E: copy_dbdata_media: Can't mount /cache your storage not prepared yet.
E: failed to mount /cache (Invalid Argument)
E: Can't mount /cache/recovery/recovery_kernel_log
E: copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
Upon clicking 'wipe data/factory reset'
E: format_volume: rfs format failed on /dev/block/stl11
Does this indicate something?
And, I do keep getting the force close error messages as well... and some of them are for applications like Titanium Backup and Read It Later... which have already been uninstalled .. but they still seem to exist in the phone's memory...
Click to expand...
Click to collapse
THAT (above) could be sorted out with: Click
vish123 said:
Flashing with EZBase hasn't got rid of the Force Close error messages... I get tonnes of them... for almost everything from android.phone to even applications which I had uninstalled several times but they just mysteriously come back .... everytime I flash...
Do I need to get root access before I can perform a clean flash... as in, with no force close messages?
Click to expand...
Click to collapse
Try flashing a froyo rom... might help... then after that if you get no force closes flash gingerbread
Sent from my GT-I9000 using XDA Premium App
Re:
Okay, will download the EzBase froyo version and try flashing that...
As an aside, would you please list the reasons why these force close messages usually pop up? May be I will be able to link my problem to any one of them and then perhaps spot what the root problem could be?
To quote my original problem... To I am unable to fully uninstall the applications which I had installed on my USB storage card... They come back... but most are not functional... I get force close error messages when I try to open them...
And now, am getting force close every time I flash ...
Thanks spamtrash! I will try doing that first... and then perhaps try flashing with EZBase Froyo...
Re:
Okay, so I tried flashing this time using EZBase 2.0 (Froyo version)... and though there were no errors in the Recovery Mode... the force close error messages did come up when the setup wizard is supposed to open... (
Is that some drivers on my phone have not been installed properly which causes these messages to pop up?
I once got an error message saying "Samsung Android" had failed to install ... but when I checked my Device Manager (Win 7)... the ADB Interface was green and installed properly... ??
vish123 said:
The other day, I tried to flash the stock rom using the PDA file only... The procedure I followed was... Opened Odin, added PIT 512 and checked Re-Partition, added the DDJV6 PDA file... Hit Start... The process completed and as my phone rebooted again, it went into Recovery and threw up the following error messages:
E: copy_dbdata_media: Can't mount /cache your storage not prepared yet.
E: failed to mount /cache (Invalid Argument)
E: Can't mount /cache/recovery/recovery_kernel_log
E: copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
Upon clicking 'wipe data/factory reset'
E: format_volume: rfs format failed on /dev/block/stl11
Does this indicate something?
And, I do keep getting the force close error messages as well... and some of them are for applications like Titanium Backup and Read It Later... which have already been uninstalled .. but they still seem to exist in the phone's memory...
Click to expand...
Click to collapse
If u r flashing only the pda file then do one thing first... Open the tar file and see whether it has boot.bin and sbl.bin... If it has then do a full reset by *2767*3855#... And then flash without pit and repartition... Only pda... Do nt tick mart repartition... This wud do ur job...
Sent from my GT-I9000 using xda premium
And if u ve any lagfixes or partition changes then remove that first...
Sent from my GT-I9000 using xda premium
Hi all
I'm avoiding posting on the Slim thread as this ends up being a bit of a mess.
I've been using Slimbean 3.0 since last Thursday without major issues (nothing big, I was just waiting for the right moment to do a full backup and clean everything).
What happens is that my phone dies while coming back home from work and when I try to reboot it start bootlooping. There's no way I can get it back to life.
At this point I can get to download mode, but nothing else.
Yesterday I've been suggested to start looking into flashing something like CM10 and so I did.
By following these instruction http://wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd I manage to flash via heimdall CWM speedmod kernel without problems.
I finally have CWM working.
From there I can't get adb detect the device. The only way I can upload the rom is via CWM itself and so I did: I upload both Slimbean 4.2.1 RC1 and Slim_Gapps and cm10.0, just in case.
What I'm trying next is a full wipe to start from clean: full wipe/factory reset works OK, but when I try to format /system I get:
Code:
E:Can't mount /dev/block/st19 to /system with parameters auto llw,check=no
(File exists)
Error mounting /system/!
Skipping format...
Done.
This is the point where I'm at.
If I try to flash Slim I get (error 0), being unable to format system for the same above reason.
If I try to flash cm10.0 it doesn't even pass the device assertion check.
Now I'm particularly clueless. Do I need a different CWM that better supports Slim? Or is the system error something that is inherently wrong with my current status?
Any help is greatly appreciated.
PS: I was trying to find help on #freenode with no luck, I'm available there if anyone wants to help, my nick is ThePeach.
UPDATE: ok it seems that by trying to flash Slimbean it actually replaced the CWM with the one I was used to that comes with Slim and finally managed to format /system and flash Slim correctly without problems.
Yay!
I really hope nobody will ever find himself in this kind of mess...
Hi,
I have a problem with my Moto G 2014 XT1068 which is described in topic: forums.androidcentral.com/moto-g-2013/391289-something-seriously-wrong-my-moto-g.html#post3668518
I can't do these steps, because dialog window shows up all the time, and i cant go further.
I have disabled usb debugging option and can't disable ART runtime.
First of all "Factory" in bootloader doesn't work. Wipe and factory reset via stock recovery has no effect; old android remains, the same using TWRP:
"E:Unable to open 'cache/recovery/.version' but ends successfully
and PHilz.
I've tried to flash many roms using many recoveries( TWRP - few versions up to 2.8.5 because 2.8.6 has display flickering bug, few Philz, and few others that also flicker) and fastboot and msfastboot(both on linux).
When i flash via fastboot or mfastboot using xml.zip roms everything looks ok, there are no errors, but flashing has no effect - I have still old ROM with old issue.
When i flash via different recoveries always some errors appears. For example flashing latest CM 12.1 nightly
via TWRP i get:
"E:Error executing updater binary in zip '/sideload/package.zip'
or via stock recovery (ADB sideload) get:
"(...)
Verifying update package...
E:Failed to verify whole-file signature
E:signature verification failed
Installation aborted."
Partition erase in fastboot despite "OKAY" message in CLI has no effect. As i understand this should remove all files from partitions.
This problem showed up when i discharged battery to 0% and turned on the phone.
Have you any ideas what should i try more?
Thanks in advance.
Hi,
I've tried other things to back my phone to life, like turn on usb debugging or even delete files, all via adb shell in recovery, but it is impossible. In TWRP or PhilzTouch I remount partitions with rw privileges, it look like I'm able modifying files via vi and cat to check results but when remount one more time old files still exist, so it is like there is some buffer? (maybe some security lock?), when try rm -rf files it shows up that i can't delete because it read only... (but mount says rw). After remount partitions with rw privileges wipe /data in twrp ended successfully but has no effect.
Do you know why everything looks ok, but it is not? Of course android boots up but is useless and after few minutes phone turns off.
i have the exact same problem with xt1064 that shuts off after bootanimation, all flashing and wiping look ok, but stuck in same result.
i read in some threads it's due to corrupt partitions and there's no solution yet to this problem, i hope this is not true, please share if you make any progress, i will do the same. best of luck.
Sounds like you both have a failed eMMC. If that is the case, and I'm certain it is, there is nothing that can be done to "save" or "restore" your devices.
Sent from my XT1031
hi, maybe any1 has already found a solution?
dihcar said:
i have the exact same problem with xt1064 that shuts off after bootanimation, all flashing and wiping look ok, but stuck in same result.
i read in some threads it's due to corrupt partitions and there's no solution yet to this problem, i hope this is not true, please share if you make any progress, i will do the same. best of luck.
Click to expand...
Click to collapse
I have exactly the same issue with my XT1063. Reading a lot for a solution, traying all without success.
Hopping someone can help us!
After unlocking the bootloader, installing TWRP recovery and rooting my phone with SuperSU (v2.82), I was preparing to install a custom ROM (more specifically the Resurrection Remix 7.1.2.) all in all, things ended up going out of hand and I accidentally deleted my internal storage, losing every single bit of my existing ROM, not to mention the RR ROM file as well. Now when I try to wipe, I can't, it usually says "Failed to mount '/data' (Device or resource busy) and "Unable to mount storage".
I tried using ADB sideload but to no success, only the same message. What I can understand is that the previous data is gone, I tried changing the format of data, system and cache to FAT & exFAT but it still did not resolve my issue.
I'm out of options here, I don't want to have to give up this phone because of my stupidity.
I also tried flashing the LineageOS 14.1 ROM to see if anything was different, here is what it said:
Installing zip file '/sideload.package.zip'
Target: HUAWEI/EVA-L09/HWEVA:7.0/HUAWEIEVA-L09/C432B361:user/release-keys
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
detected filesystem exfat for /dev/block/bootdevice/by-name/userdata
mount: failed to mount /dev/block/bootdevice/by-name/userdata at /data: Device or resource busy
unmount of /data failed; no such volume
Patching system image unconditionally...
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
Script succeeded: result was [1.000000]
Although it said succeeded it clearly did not work and I am sitting without a ROM. I'm not smart when it comes to these things please help a guy out.
(Is there a way to going back to completely stock EMUI 5.0?)
Cheers.
EMUI 5.01 requires encryption, which you obviously removed.
Search for DC Unlocker, it can probably fix it for 25 Euros
zgfg said:
EMUI 5.01 requires encryption, which you obviously removed.
Search for DC Unlocker, it can probably fix it for 25 Euros
Click to expand...
Click to collapse
I know this is awkward to ask and all, but how exactly do I go about this, I'm pretty lost and I have minimal experience with this stuff..
I never had to use it but here is their portal (with download info, prices, instructions, etc)
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
If you search on XDA or search on Google for eg XDA Huawei DC Unlocker you will find threads with first hands experience (I've seen them several tines but didn't save to Favorites)
zgfg said:
I never had to use it but here is their portal (with download info, prices, instructions, etc)
If you search on XDA or search on Google for eg XDA Huawei DC Unlocker you will find threads with first hands experience (I've seen them several tines but didn't save to Favorites)
Click to expand...
Click to collapse
I'm terribly sorry for being THIS stupid. As I'm looking into this even more, I'm conflicted about the credit amount I need, been scrolling through the list and I can't really find my problem involving firmware I suppose.
People usually buy for 15 Euros. It may help you, Chrome will automatically translate from German
https://www.android-hilfe.de/forum/...-wiederherstellung-mit-dc-phoenix.818669.html
I'm not educated about DC Unlocker but that is NOT neccesary here. You can easily repair the /data partition by flashing the stock recovery via fastboot, formatting data with that stock recovery and then flashing TWRP again. After that TWRP should be able to read the data partition again.
You can easily go back to stock completely and even restore your bootloader by doing a "rollback" to Android 6. (dload method). After that you can normally upgrade from there though EMUI to the latest version of stock.
christopherpfister said:
I'm not educated about DC Unlocker but that is NOT neccesary here. You can easily repair the /data partition by flashing the stock recovery via fastboot, formatting data with that stock recovery and then flashing TWRP again. After that TWRP should be able to read the data partition again.
You can easily go back to stock completely and even restore your bootloader by doing a "rollback" to Android 6. (dload method). After that you can normally upgrade from there though EMUI to the latest version of stock.
Click to expand...
Click to collapse
I've tried using eRecovery to format the data but to no success, I can't even use the touch screen for some reason, (I know about the volume keys, but when it comes to selecting the Wi-Fi, there is no success whatsoever). If you do know a fix for this, could you possibly walk me through this?
Hexagonal said:
I've tried using eRecovery to format the data but to no success, I can't even use the touch screen for some reason, (I know about the volume keys, but when it comes to selecting the Wi-Fi, there is no success whatsoever). If you do know a fix for this, could you possibly walk me through this?
Click to expand...
Click to collapse
UPDATE: I flashed the stock recovery image and it showed me the wipe cache partition and factory data and system reset, I tried both, only the cache one succeeded, the other one failed. I saw a post that directed you to flash boot.img, recovery.img, recovery2.img and then system.img, I did that, but I couldn't boot into my phone - the good thing is however! That I can use my touchscreen in the recovery now.
Obviously the second time booting into EMUI recovery it prompts me to 'Download latest version and recovery', I try to connect to my Wi-Fi, seems okay but then it suddenly fails. More specifically it says 'Getting package info failed'. Save me please :crying:
So this "erecovery" never worked in any way for me (the one which offers you to download the latest version).
Instead you need the normal recovery you already used. Formatting failed for me the first time too, try it again and then it will try to format "low-level" which worked for me.
Go directly into fastboot from that, flash TWRP and go directly into TWRP.
After that should be able to use /data in TWRP. As soon as you are able to start TWRP without any error messages (like "Device busy" or something) go to Wipe and then format data.
Important: check which partition type you have! For EMUI you need "f2fs" and for lineage you need "ext4". You can see and change that in TWRP under Wipe -> "change or repair filesystem".
If you have any more questions, just ask.
christopherpfister said:
So this "erecovery" never worked in any way for me (the one which offers you to download the latest version).
Instead you need the normal recovery you already used. Formatting failed for me the first time too, try it again and then it will try to format "low-level" which worked for me.
Go directly into fastboot from that, flash TWRP and go directly into TWRP.
After that should be able to use /data in TWRP. As soon as you are able to start TWRP without any error messages (like "Device busy" or something) go to Wipe and then format data.
Important: check which partition type you have! For EMUI you need "f2fs" and for lineage you need "ext4". You can see and change that in TWRP under Wipe -> "change or repair filesystem".
If you have any more questions, just ask.
Click to expand...
Click to collapse
So what you're saying is, as soon as I get my data sorted and my partition set to the right one I should be able to install the custom ROM. I could use data and even formatted it, tried installing Lineage but I must've had the storage on the wrong type, now I'm back with the same issue, I'll try to fix it and post my results here. Thank you!
Hexagonal said:
So what you're saying is, as soon as I get my data sorted and my partition set to the right one I should be able to install the custom ROM. I could use data and even formatted it, tried installing Lineage but I must've had the storage on the wrong type, now I'm back with the same issue, I'll try to fix it and post my results here. Thank you!
Click to expand...
Click to collapse
Update: It did NOT work, tried flashing LineageOS through ADB sideload, it was going fine before the bar completely filled up around 50% of the way done, it said 'detected filesystem ext4 for /dev/block/bootdevice/by-name/system' and in the next line it said 'script succeeded: result was [1.000000]'
Help me, I'm begging you, at the moment I don't have an access to a microSD that has the capacity to hold the stock files to do the dload method, therefore this is my only hope.
Hexagonal said:
Update: It did NOT work, tried flashing LineageOS through ADB sideload, it was going fine before the bar completely filled up around 50% of the way done, it said 'detected filesystem ext4 for /dev/block/bootdevice/by-name/system' and in the next line it said 'script succeeded: result was [1.000000]'
Help me, I'm begging you, at the moment I don't have an access to a microSD that has the capacity to hold the stock files to do the dload method, therefore this is my only hope.
Click to expand...
Click to collapse
Whats the error? Why doesn't it work? What happens when you try to boot?
christopherpfister said:
Whats the error? Why doesn't it work? What happens when you try to boot?
Click to expand...
Click to collapse
That's what I'm trying to figure out, when I try to boot in it's just stuck on a boot loop. Unfortunate..
Remember that you have to what *a while* for the first boot. Only if you see no change after 5-8 minutes or so something is definitely wrong.
Have you checked in TWRP if your /data partition is ext4?
christopherpfister said:
Whats the error? Why doesn't it work? What happens when you try to boot?
Click to expand...
Click to collapse
christopherpfister said:
Remember that you have to what *a while* for the first boot. Only if you see no change after 5-8 minutes or so something is definitely wrong.
Have you checked in TWRP if your /data partition is ext4?
Click to expand...
Click to collapse
I know, but it was flashing the Huawei logo and the unlocked bootloader warning continuously. It was set on EXT4 but as I was saying, it said script succeeded at 50%.
Hexagonal said:
'detected filesystem ext4 for /dev/block/bootdevice/by-name/system' and in the next line it said 'script succeeded: result was [1.000000]'
Click to expand...
Click to collapse
That just said that /system partition is ext4. That is default even for stock I believe. You need to check for /data.
christopherpfister said:
That just said that /system partition is ext4. That is default even for stock I believe. You need to check for /data.
Click to expand...
Click to collapse
I deliberately set the data partition to EXT4 before installing
Hexagonal said:
I deliberately set the data partition to EXT4 before installing
Click to expand...
Click to collapse
Can you check in TWRP if it actually says /data is ext4?
Which lineage are you trying to install? Don't you need a vendor.zip for some of them?
/data is indeed on EXT4, and I was installing the one that was on the room section.