Hi guys, I had on my Jiake P6 (MTK 6582) default rom – 4.2.2 Jelly Bean and I flashed my phone couple times and I was wondering if I could flash my phone to Marshmallow (6.0). So I downloaded this Marshmallow
Code:
mtkroms.com/2016/02/marshmallow-cyanogenmod-13-for-mt6582.html
and tried to flash my phone in TWRP recovery. It failed, so I tried to flash back to 4.2.2 stock rom and it failed too.
So my situation now is that I can’t flash any rom, cause: “Can’t mount /system”. And my internal memory is very weird. Everything I do with it is being reseted. I connect my phone to PC and do format my phone internal sd card. After restarting my phone the internal memory resets and there are the same files I had there before the formating. After each restart of mobil the whole settings I’ve set puts back into factory format state. What should I do to have fully functional phone again, please??
I also tried to flash my phone with Flash tools in windows and nothing happens, then after googling the Can’t mount /system problem I’ve noticed that maybe I should use CWM recovery, so I tried to flash it with Flash tools and It gives me an error after download to phone is complete and there is stil TWRP recovery on my phone.
Related
(For the ones who will ask, yes i have read a lot of threads with this problem and tryed almos all of them, and i even read about other phones with this problem so the point is fix this.)
Hi,
I write cuz i got this problem in mi sisters galaxy i9003 SL.
Shi is a basic user, just use the phone for calls and whatsapp. It had Pou and go Locker installed and nothing else.
The phone got slow so we decided to do "factory reset", but it doesnt formated and keep the user information even programs, so decided to flash the phone so it would be forced to wipe the data, i'vr got the same phone and flashed it a lot of times.
Flashed with odin 1.85 the PIT (latona) and no problem
Then XXKPE 4 Files, and it seems no problem, but it didnt restart so got into bootloop.
So re flashed XXKPE.
Here is when the problem starts, the phone got into a strange mode, at last i never saw it before, i ve got the android robot saying something about kernel with a loading bar, i let the phone work til it got discarged, but when i turned it on again i ve got the problem(E:format_volume: rfs format failed). Then the phone stopped charging. i manage to enter recovery mode but for my surprise it was the normal recovery from samsung and i flashed clockworkmod and even tested it. So i re flashed clockworkmod and it works, but if i flash anything it comes back to samsung recovery mode. i still can get to download mode.
I have tryed the following:
Re flash room stock entel chile ------> problem
Re flash XXKPE 4 archivos---------> problem
Re Flash clockworkmod-------> works but if i flash anithing it comes to samsung recovery again.
Re flash Kernel-------> problem
I have read about the dead memory of the phone an take it back with a SD card, i dont want to sorry. Here the SD card costs more than the phone.
So i want to try tosolve this. not a very advanced user, but i can learn quickly.
I'm open to ideas.
Thanks.
yvel21 said:
(For the ones who will ask, yes i have read a lot of threads with this problem and tryed almos all of them, and i even read about other phones with this problem so the point is fix this.)
Hi,
I write cuz i got this problem in mi sisters galaxy i9003 SL.
Shi is a basic user, just use the phone for calls and whatsapp. It had Pou and go Locker installed and nothing else.
The phone got slow so we decided to do "factory reset", but it doesnt formated and keep the user information even programs, so decided to flash the phone so it would be forced to wipe the data, i'vr got the same phone and flashed it a lot of times.
Flashed with odin 1.85 the PIT (latona) and no problem
Then XXKPE 4 Files, and it seems no problem, but it didnt restart so got into bootloop.
So re flashed XXKPE.
Here is when the problem starts, the phone got into a strange mode, at last i never saw it before, i ve got the android robot saying something about kernel with a loading bar, i let the phone work til it got discarged, but when i turned it on again i ve got the problem(E:format_volume: rfs format failed). Then the phone stopped charging. i manage to enter recovery mode but for my surprise it was the normal recovery from samsung and i flashed clockworkmod and even tested it. So i re flashed clockworkmod and it works, but if i flash anything it comes back to samsung recovery mode. i still can get to download mode.
I have tryed the following:
Re flash room stock entel chile ------> problem
Re flash XXKPE 4 archivos---------> problem
Re Flash clockworkmod-------> works but if i flash anithing it comes to samsung recovery again.
Re flash Kernel-------> problem
I have read about the dead memory of the phone an take it back with a SD card, i dont want to sorry. Here the SD card costs more than the phone.
So i want to try tosolve this. not a very advanced user, but i can learn quickly.
I'm open to ideas.
Thanks.
Click to expand...
Click to collapse
so what you are saying is every time you try to flash something... even your stock firmware via odin the phone just resets to its orignal state (i.e E:format_volume: rfs format failed).what I see from here is your device system data has been completely formatted but failed to flash any firmware.... try with memory card and sim card removed and flash KPE(all files)... there isn't any need to flash any kernel on stock so just avoid it...
follow these steps
*Get samsung USB drivers and install on the pc/laptop.
*Download ODIN and the KPE files.(for I9003 only)
*Connect your phone in Download mode.
*ODIN will detect the device and flash the stock.
*If your flash was successfull you will get your phone back in running condition.
GOODLUCK
mustafahussain said:
so what you are saying is every time you try to flash something... even your stock firmware via odin the phone just resets to its orignal state (i.e E:format_volume: rfs format failed).what I see from here is your device system data has been completely formatted but failed to flash any firmware.... try with memory card and sim card removed and flash KPE(all files)... there isn't any need to flash any kernel on stock so just avoid it...
follow these steps
*Get samsung USB drivers and install on the pc/laptop.
*Download ODIN and the KPE files.(for I9003 only)
*Connect your phone in Download mode.
*ODIN will detect the device and flash the stock.
*If your flash was successfull you will get your phone back in running condition.
GOODLUCK
Click to expand...
Click to collapse
Same thing happend to my SL and now its dead so good luck
Thanks,
Still trying to make it work, after a few tryes to flash xxKPE it stopped charging but some how re flashing xxkpe got it to work back again, but doesnt start the OS, still in bootloop.
yvel21 said:
Thanks,
Still trying to make it work, after a few tryes to flash xxKPE it stopped charging but some how re flashing xxkpe got it to work back again, but doesnt start the OS, still in bootloop.
Click to expand...
Click to collapse
The internal SD might be broken like mine.
Try boot into recovery, then adb shell, execute and paste output in this thread again:
Code:
ls -l /dev/block/mmcblk*
fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk1
There are several ways it can get broken, and i know a few ways to customize firmwares to workaround them.
i faced this problem in I9000 & I9003 and solution is .....
get memory card and format it on yr pc
make file system is fat32
when done put sd card into phone
flash the phone with pit file
make sure to mark repartion
and when done
yr phone work just fine
P>>S
never get out this sd card from phone
or it will go to loop mode again
try and post result here
B.R
Hi. I have a shield tablet with Blisspop a friend gave me. Since for some reason the os was quite broken I'm trying to reinstall it via recovery mode and microSD. I already swiped and tried with two different rom (blisspop and cyanogen), formatting the SD exFAT/NTSC, but I can't read the zip file when in recovery mode (storage/sdcard1). It says there are no files and I got an error if I try to mount it. What am I doing wrong?
hi folks,
My device was on cm11 and I wanted to try the slim6 rom and the new TWRP update for the recovery. I tried the TRWP unified version of Andi but after the flash succeded , everything from the tablet (Rom, data, system, etc..) was completly erased. Now the new recovery dosent read anything, even if I put a SD card with the files to flash. I tried to flash a another recovery with odin but the odin program freeze when I select the recovery . I can't find any working links for stock firmware and the one from sammobile crash most of the time before the end.
Any ideas of what happened on my device ?
So i tried to install a new kernel,but things got messy,the kernel installed,but when it booted it gave me a black screen,could only hold the power button to open the turn off,restart features.I tried to flash a new firmware with odin,but it just fails to flash,if i boot into recovery twrp and try to copy somehting on my internal storage it gives me an error saying my phone is disconnected or not responding,then i formated everything and now i only have recovery to boot into with no options to install a firmware with odin since it fails.Tried with smart switch as well,nothing.I guess it has something to do with the fact that i coudn't copy anything on my internal storage.Any ideas?
Issue solved,used adb sideload to install a custom rom and that worked
I've got an old Samsung Galaxy Note 10.1 (N8010) which was flashed to a custom ROM (Cyanogenmod) in 2016. I'm not sure what version because I'm unable to boot it. A few weeks ago, the tablet rebooted without reason and got stuck on the Cyanogenmod bootscreen forever. I've let it run for 24 hours without result.
So this is what I tried:
Reboot into recovery mode (TWRP 2.8.6.0) and wipe everything. Then I tried to flash a different ROM, but when the device reboots, everything seems to be reset and it tries to boot the old corrupted ROM again. I also tried a newer version of LineageOS. But for that, I need a newer TWRP version. So I download and put the newest TWRP version on it using ODIN mode. Flash Passes says ODIN, but after reboot, TWRP 2.8.6.0 is still being loaded. I tried it again without 'reboot' checked so I can reboot directly back into recovery manually, but this also, didn't worked. (by the way, ADB works when loading TWRP, FASTBOOT doesn't work when loading ODIN mode, fastboot doesn't recognize the device)
I tried to flash stockrom back onto the device, also using ODIN mode. Flash passes, no errors. Device reboots and.. nope! It still tries to load the old Cyanogenmod forever.
I'm basically stuck here. I can't update to a newer Recovery and I cant flash the rom because everytime I reboot the device, everything change i made is gone.
I noticed that when I list files in /data the folder seems to be empty.
I also tried to reformat /data to fat and back to ext4 but formatting to fat fails and formatting to ext4 succeeds, however, after a reboot, everything i did seems to be undone by the device. Even the time and date is reset.
Is there a way I can bring back my tablet back to life? Thank you!
I have pulled the recovery.log file and uploaded it to pastebin.
I can't post a link to it because I do not have made 10 posts yet.. (very anoying). So i put the adress here:
https://pastebin.com/3muqPMzz
FSCK check on /data returned this:
Code:
~ # e2fsck /dev/block/platform/dw_mmc/by-name/USERDATA
e2fsck 1.41.14 (22-Dec-2010)
/dev/block/platform/dw_mmc/by-name/USERDATA: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? y
yes
e2fsck: unable to set superblock flags on /dev/block/platform/dw_mmc/by-name/USERDATA
And Odin mode: NAND ERASE ALL returns
Code:
<ID:0/006> Complete(Write) operation failed.
It seems like my Note 10.1 tablet is suffering from the emmc brick bug.
niquedegraaff said:
I've got an old Samsung Galaxy Note 10.1 (N8010) which was flashed to a custom ROM (Cyanogenmod) in 2016. I'm not sure what version because I'm unable to boot it. A few weeks ago, the tablet rebooted without reason and got stuck on the Cyanogenmod bootscreen forever. I've let it run for 24 hours without result.
So this is what I tried:
Reboot into recovery mode (TWRP 2.8.6.0) and wipe everything. Then I tried to flash a different ROM, but when the device reboots, everything seems to be reset and it tries to boot the old corrupted ROM again. I also tried a newer version of LineageOS. But for that, I need a newer TWRP version. So I download and put the newest TWRP version on it using ODIN mode. Flash Passes says ODIN, but after reboot, TWRP 2.8.6.0 is still being loaded. I tried it again without 'reboot' checked so I can reboot directly back into recovery manually, but this also, didn't worked. (by the way, ADB works when loading TWRP, FASTBOOT doesn't work when loading ODIN mode, fastboot doesn't recognize the device)
I tried to flash stockrom back onto the device, also using ODIN mode. Flash passes, no errors. Device reboots and.. nope! It still tries to load the old Cyanogenmod forever.
I'm basically stuck here. I can't update to a newer Recovery and I cant flash the rom because everytime I reboot the device, everything change i made is gone.
I noticed that when I list files in /data the folder seems to be empty.
I also tried to reformat /data to fat and back to ext4 but formatting to fat fails and formatting to ext4 succeeds, however, after a reboot, everything i did seems to be undone by the device. Even the time and date is reset.
Is there a way I can bring back my tablet back to life? Thank you!
I have pulled the recovery.log file and uploaded it to pastebin.
I can't post a link to it because I do not have made 10 posts yet.. (very anoying). So i put the adress here:
https://pastebin.com/3muqPMzz
Click to expand...
Click to collapse
Some of what you describe seems to suggest that your internal sdcard is corrupted, but, you still have TWRP booting. I would think that TWRP wouldn't boot if the internal was damaged.
Sent from my LGL84VL using Tapatalk
I can boot twrp but anything I do in there is temporary. I can't write to the internal SD. Only read. Seems like the emmc brick bug to me. I wish there was a way to check if this is absolutely true.