Related
Last night, I decided to try out the Trinity kernel. I downloaded and flashed, and everything went without error. After that, I pushed a custom boot animation over ADB. The first one didn't work, and after the splash screen disappeared it was simply a black screen, but then I pushed one I downloaded from XDA and it was fine.
Now, though, I want to make a nandroid, but CWM is running into some issues. I started the ROM manager app, entered a name for the nandroid as usual, and hit OK, but when it rebooted into nandroid, it gave me an error saying "Error mounting /system" and rebooted back into CM7. That's odd, I thought, I never had any problems like that before. So I rebooted into CWM myself by holding down power+vol down and tried making a nandroid there. No luck. Then I went to mounts and storage and tried to manually mount /system. CWM gave me the error again.
I'm not really sure what's causing this. I thought it might be because now I'm using an ext4 filesystem because of Trinity (right? haha I'm new to kernels and such) and CWM might not support reading it, but if that's the case, I think I would not be the first to have this issue. Yet I searched, on that thread, on Google, on XDA general search, and didn't see anything. I also doubt it's the boot animation.
My last nandroid was yesterday. The only changes to the system I remember right now is that I flashed CM7 nightly 101, then flashed Trinity, rebooted, and flashed the boot animation mentioned. I installed apps since then but none of them had root so I doubt that's it. I would reflash CM7 to overwrite Trinity, but I read on the Trinity thread that if I did that without restoring an old CM7 kernel nandroid first, I'd be stuck in a bootloop because of ext4...?
So, what should I do? I don't want to make anything worse than it already is by tinkering with this myself, I no longer have a current nandroid, that's why I'm asking XDA. Does anyone have an idea why this might be happening? I'm sorry if a thread like this already exists or if this is in the wrong forum (if so mods please move it), this is my first time posting and my search skills could suck (although I looked in all the places I could think of)
Thanks for your help! My G2x is running CM7 nightly 101. Both the nvflashed CWM in recovery and the CWM started by the rom manager app are version 3.0.2.7.
I got the same problem as you bro right after flashing trinity
Sent from my LG-P999 using XDA App
ritthyhang said:
I got the same problem as you bro right after flashing trinity
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Good, so I'm not the only one! I thought that was too odd to be true.
Here's what I've done. I reflashed cm7 nightly 101 to get my CM kernel back and rebooted. Sure enough, bootloop. Or it never got past the splash screen to the CM7 android skateboard boot animation. I went back in recovery, though, and was able to mount /system. Odd. So I flashed trinity again and tried mounting /system again and no go. So this definitely has something to do with Trinity... I restored my nandroid, reflashed 101,and that's where I am now. Tomorrow, I will make an up-to-date nandroid and do some tinkering to try to figure out what's going on. Maybe it has something to do with the boot animation, maybe not, exactly what's going on is what I am going to try to figure out if no dev shows up here.
Could you give me a few details about your case? Were you coming from cm7 too? Did you do any boot animation tinkering like me?
Sent from my LG-P999 using XDA App
Okay so I was eaglesblood 1.6 and flashed trinity the other day. Before trinity I was on miui and made plenty of nandroid backup. So today and 1.7 got released so before update I try to backup then behold Our Problem. So after I confirm that I can flash 1.7 over 1.6 I decided to take that risk and flashed anyways. On 1.7 the Superuser was updated I notice, so I decided to make a backup and it Work. So I think the problem was had to do with the outdated Superuser. I think I might be wrong that's just my experience.
Sent from my LG-P999 using XDA App
ritthyhang said:
Okay so I was eaglesblood 1.6 and flashed trinity the other day. Before trinity I was on miui and made plenty of nandroid backup. So today and 1.7 got released so before update I try to backup then behold Our Problem. So after I confirm that I can flash 1.7 over 1.6 I decided to take that risk and flashed anyways. On 1.7 the Superuser was updated I notice, so I decided to make a backup and it Work. So I think the problem was had to do with the outdated Superuser. I think I might be wrong that's just my experience.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Hmm. So to clarify: You were running MIUI, then you flashed eb followed by trinity. Then, eb 1.7 was released and you went to nandroid, but you couldn't mount /system, so you took the risk and upgraded anyways. The new be came with a new version of superuser, and you were able to make nandroids once again. Is this correct?
One very important question if it is. Did you flash trinity again after flashing the eb 1.7 update?
Also, could I ask what version of superuser came in this update? I am using version 2.3.6.3, which is the latest according to Superuser check for updates, but ROM Manager lists a 3.0 beta version and I'm wondering if you're using that. To check, open Superuser, go to the settings tab, and scroll all the way down. It's the second to last option for me. It's unlikely that superuser is making the difference, since it works as a part of Android and our problem is in recovery, before Android loads, but I can see how it might be possible. If you're using the 3.0 beta, I will flash to that and see if it fixes.
I will look into this some more tomorrow, specifically right now I want to know what filesystem eb's kernel recommends.
Sent from my LG-P999 using XDA App
G2X here same problem.
I think they key here is MIUI. I tried to load MIUI image and it didnt go well. I formatted and CWR to restore and its been giving me issues same cant mount system errors.
Right now I downloaded CM7 and installed it from scratch and I can use the phone but it wont backup my ROMs anymore.
Have you guys found anything new ?
lithivm said:
I think they key here is MIUI. I tried to load MIUI image and it didnt go well. I formatted and CWR to restore and its been giving me issues same cant mount system errors.
Right now I downloaded CM7 and installed it from scratch and I can use the phone but it wont backup my ROMs anymore.
Have you guys found anything new ?
Click to expand...
Click to collapse
Update cwm to latest recovery 5.0.2.0 i believe.
fcisco13 said:
Update cwm to latest recovery 5.0.2.0 i believe.
Click to expand...
Click to collapse
+1 cwmr 5.0.2 is the first to officially support ext4 partitions
Sent from my LG-P999 using xda premium
lithivm said:
I think they key here is MIUI. I tried to load MIUI image and it didnt go well. I formatted and CWR to restore and its been giving me issues same cant mount system errors.
Right now I downloaded CM7 and installed it from scratch and I can use the phone but it wont backup my ROMs anymore.
Have you guys found anything new ?
Click to expand...
Click to collapse
I just stopped using Trinity and went back to the stock CM kernel. I don't think it's just miui, I never used that. But...
fcisco13 said:
Update cwm to latest recovery 5.0.2.0 i believe.
Click to expand...
Click to collapse
squish099 said:
+1 cwmr 5.0.2 is the first to officially support ext4 partitions
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
YESS! Looks good. I did hear about that. Looks like it's time to give Trinity another try
Error mount/system!
I can't restore my stock rom,i've tried to fully wipe but got:
-- Wiping data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete.
and cant restore
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error mounting /system!
Skipping format
Can't mount /system!
and cm7 doesnt boot,now im just stuck in ClockworkMod Recovery v4.0.0.5
is there any ways to flash stock rom in clockworkmod??
asn_86 said:
I can't restore my stock rom,i've tried to fully wipe but got:
-- Wiping data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete.
and cant restore
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error mounting /system!
Skipping format
Can't mount /system!
and cm7 doesnt boot,now im just stuck in ClockworkMod Recovery v4.0.0.5
is there any ways to flash stock rom in clockworkmod??
Click to expand...
Click to collapse
Update your recovery, both, fake and nvflash.
i was also having the can't load system issue. upgrading to latest clockwork mod via rom manager to v5.0.2.0 resolved the issue and i was able to take a backup of my current system.
jblah said:
i was also having the can't load system issue. upgrading to latest clockwork mod via rom manager to v5.0.2.0 resolved the issue and i was able to take a backup of my current system.
Click to expand...
Click to collapse
Where do I find the latest clockwork mod and how do I install it? I currently have a soft bricked phone, and I can't seem to get it unbricked. I tried using the pit files with the stock rom, the dbdata stuff and everything else. What happened was the the system was in ICS, but something happened and I couldn't load into CWM 4 and the system wouldn't boot. So to fix, I used odin to install the stock rom (v2.3.3), but the stock rom came with CWM 3.0, so now I'm at 3.0 and can't mount the file system and it's not booting. I'm assuming that if I upgraded the CWM back to a newer version, I'll be able to restore the system and gain access to the file system again.
reboot problem
i jus flashed ext4 converter for kernel update every think went fine but i couldnt mount system coz it was showing error i neglected dat nd flashed every thing was done nd when i rebooted it gt stuck in d samsung galaxy y logo...plzzz help meee wat to do..plzzz help
Abizer98 said:
i jus flashed ext4 converter for kernel update every think went fine but i couldnt mount system coz it was showing error i neglected dat nd flashed every thing was done nd when i rebooted it gt stuck in d samsung galaxy y logo...plzzz help meee wat to do..plzzz help
Click to expand...
Click to collapse
I'd ask in the samung galaxy forums bud.
"my mind draws lots of blanks actually"
Solution
asn_86 said:
I can't restore my stock rom,i've tried to fully wipe but got:
-- Wiping data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete.
and cant restore
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error mounting /system!
Skipping format
Can't mount /system!
and cm7 doesnt boot,now im just stuck in ClockworkMod Recovery v4.0.0.5
is there any ways to flash stock rom in clockworkmod??
Click to expand...
Click to collapse
actually yes. the /system folder is corrupt and it need to be formatted. so all you need to do is format / system then it will work as it should
hope that helps
PHone: Lg G2x
I have looked at all the forums for a related article. I rooted my phone and have cwm 3.0.2.7. I was able to make a backup before. The first rom i installed was cm7 nightly. After the first install from zip, there was a bootloop. So i tried fiddling around with the recovery menu and finally, somehow, it booted. Now, i realize i want to get the lg g2x update OTA. this requires stock roms. (also, my first backup is erased. I was being stupid)
Now i want to go back to my stock rom and have no backup. So i downloaded a g2x backup and put it in the clockworkmod folder/backup. Before restoring, i wanted to make a backup, however, it says it "cant mount system." I tried reflashing cwm and installing the root again. However, the problem persists.
What can i do to get back to froyo 2.2.2? How can i fix, "cant mount / system problem"? I dont want to do anything just yet as i fear bricking my phone. I tried restoring to the downloaded backup but it says md5 mismatch
Please help me!
My t101 was fine the day before yesterday, and i used it at that night. but on yesterday morning, when i got up, i found it was shut down automatically.
i tried to restart it, and it stayed in the startup boot screen. I thought it was system breakdown, so i tried several ROMs according to the procedures in the threads.
i downloaded 8.6.5.21, Revolver_TF_3.11_gnufabio and KRAKD-1.5.2, but none of those work. i still stuck in the boot screen.
I don't know what to do now. Please give me an advise. Thank you!
What's your serial number?
Have you formated /system, /data and /cache when you flashed another ROM? If not, there may be traces of the older ROM that could make the newer ROM fail or not boot at all...
I would try the following:
If you have a working nandroid backup, restore it!
If you don't have, go to recovery, delete /system, /data and /cache and flash a new ROM.
If none of the above work, you could try a NVFlash method.
you could also try to load the factory default from out of CWM.
Or restore a backup, if you have one?
when i tried to wipe data, it said error in removing something. anyway, i've solved this problem. i used nvflash with prime1.4rom, it worked. my t101 is alright now. Thanks for your advise.
no, i don't have a backup. but i will do that, in case it happens again. thank you.
In future always backup!!
Also when youre installing a new rom make sure to be carefull and make a clean install
Download team rogue recovery that will make sure data/media is not touched thats your internal sd
Before each rom wipe cache/dalvik cache/system/battery states/staging minimum i usually back up everything so i wipe all partitions and go ground up through nvflash.
Sent from my tf running krakd warped an twisted 1544mhz Blades kernel
I posted this in Q&A, but no replies led me to post here as well.
Hi. I've been using this Xoom for a couple weeks now, and just started having this problem yesterday.
Before I noticed the promblem I was on EOS 3 Wingman. I had TWRP 2.2.2.0 as recovery.
I wanted to give CM10 nightlies a shot. Downloaded the ROM and GAPPS through Goo. I tried to flash the CM10 ROM and GApps zip through the Goo interface. Xoom rebooted and instead of installing, I just got a contantly repeating error saying the install failed.
Eventually I rebooted the xoom and went into recovery. I tried to wipe data and it said it couldn't be mounted. Same error for wiping system, cache, etc...
Rebooted xoom and the EOS 3 rom was still working fine, I downloaded [Recovery] ClockworkMod 3.2.0.0 (R4c) Modded for Internal media [UPDATED 10/6]" and flash via adb. rebooted to recovery and tried wipe. same issue. nothing could be wiped. everything said "failure mounting <applicable partition>".
I tried flahing rogue recovery and got the same thing. I said screw it and rebooted back into EOS and it's been working fine. EOS was updated last night to 143, so i downloaded and tried to install through goo. I got the repeating errors again. Rebooted into recovery and still got the errors where it seems like none of the partitions are writeable.
I WAS able to install the EOS update directly through recovery.
Has anyone ever seen this behavior before and know how to fix it? I can't even export logs in the 2 CWM recoveries because they fail when trying to write the log file.
If I try to install an update through goo, it reboots to recover and just keeps scrolling "An Update Error has occured".
I can reboot to recovery and install the zip from there directly with no issue.
Here is the log for the failed data wipe...
I:mke2fs command: mke2fs -t ext4 -m 0 /dev/block/mmcblk0p10
mke2fs 1.41.12 (17-May-2010)
/dev/block/mmcblk0p10 is apparently in use by the system; will not make a filesystem here!
E:Unable to format data.
* Verifying filesystems...
I:=> Let's update filesystem types via verifyFst aka blkid, command: 'blkid'.
* Verifying partition sizes...
Ievice has /data/media
I:Total used space on /data is: 5122715648
I:Total in /data/media is: 3962468352
I:Actual data used: 1160247296
du: /data/media/.android_secure: No such file or directory|
once in recovery, if I try to format data, it says "Unable to format data". Log
Well I can't help, I'm in the same boat...hoping to get some insight from any responses you might get.
grey.ghost said:
Well I can't help, I'm in the same boat...hoping to get some insight from any responses you might get.
Click to expand...
Click to collapse
It's extremely unusual to get no responses to an issue like these here at XDA. leads me to believe it might be a very uncommon problem. The folks here are usually on the ball about any issue that has even arisen before.
That being said, I am going to try to flash the stock RUU back on from this link...
http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard
After I finish, I re-root/unlock.
I'll let you know how it goes.
I'll let you know if I come up with something as well. So far I've managed to erase the sd card and maintain a constant boot loop.
Flashing all of the stock img, relocking, and unlocking again didn't do ****.
Found an original MZ600 SBF, which is what I need for verizon 3g xoom, I'm installing this via RSD Lite to see if it blows away whatever is causing the issue.
I was able to wipe the entire system and use adb to repeat the unlock and root steps. So far so good. I'm using the CWM 3.2.0.0 recovery image right now though. I have at least been able to get into a clean copy of a ROM and no bootloops yet. Can't restore data off old Nandroids, so I'm about to update to the newer CWM based recovery image and see if that will help.
I think I'm OK now.
I installed the SBF. Let all of the OTA updates come in including the ICS update where my 3g stops.
flashed the ROGUE recovery from fastboot.
I was able to format all partitions and install and boot CM9 nightly.
Me too, i was sweating hard for a bit, but was able to go through the entire process from stock, unlock, root, rogue recovery and then flashed CNA. Got that working without boot loops or fc and then advance restored data from a previous nandroid through rogue to get it back. A couple of apps had to be redownloaded from the market, but it looks as if I'm back in business. I want to try TWRP, but every time I do something screws up, so I think I'll stop trying.
Thanks for the help.
grey.ghost said:
Me too, i was sweating hard for a bit, but was able to go through the entire process from stock, unlock, root, rogue recovery and then flashed CNA. Got that working without boot loops or fc and then advance restored data from a previous nandroid through rogue to get it back. A couple of apps had to be redownloaded from the market, but it looks as if I'm back in business. I want to try TWRP, but every time I do something screws up, so I think I'll stop trying.
Thanks for the help.
Click to expand...
Click to collapse
Are you installing Twrp from goo manager. Cause I have not had any issues with the goo manager download. But did have issues with the zip file here on xda. I dont kknow if it is worth a try but that is how I did it.
Sent from my Xoom using xda app-developers app
Well sense this is a twrp related issue I would think u would have asked in my thread where I released the port for twrp to Xoom,
Having said that, at one point n time there was a note n the open about open script recovery. But its is also buried in the thread too. So I will answer your question and also presume a few things... and please correct me if I am wrong anywhere.
Once u set the download path in goo app to /data/media/goomanager/ and downloaded a ROM, clicked flash ROM, and entered recovery once u saw all the E/ update error u manually rebooted the Xoom and did not let the script finish installing the ROM? If I am correct that so far. That's what cause your additional problems. You basically rebooted recover while mid install of a ROM.
Now as stated it the twrp thread for Xoom, these errors are false errors and should be ignored. To add it the reassurance that they are intact false errors, from goo app select to flash a ROM again and simple allow the script to finish and then the tablet will reboot on its own when it is finished with the script. And you will be greeted with your new ROM you just successfully flashed.
Again let me know if I am wrong on assuming you forced a reboot mid install ( aka while u saw all the errors)
Sent from my Nexus 7 using Tapatalk 2
runandhide05 said:
Well sense this is a twrp related issue I would think u would have asked in my thread where I released the port for twrp to Xoom,
Having said that, at one point n time there was a note n the open about open script recovery. But its is also buried in the thread too. So I will answer your question and also presume a few things... and please correct me if I am wrong anywhere.
Once u set the download path in goo app to /data/media/goomanager/ and downloaded a ROM, clicked flash ROM, and entered recovery once u saw all the E/ update error u manually rebooted the Xoom and did not let the script finish installing the ROM? If I am correct that so far. That's what cause your additional problems. You basically rebooted recover while mid install of a ROM.
Now as stated it the twrp thread for Xoom, these errors are false errors and should be ignored. To add it the reassurance that they are intact false errors, from goo app select to flash a ROM again and simple allow the script to finish and then the tablet will reboot on its own when it is finished with the script. And you will be greeted with your new ROM you just successfully flashed.
Again let me know if I am wrong on assuming you forced a reboot mid install ( aka while u saw all the errors)
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
No, after pushing the TWRP recovery to the Xoom using adp, I would clean install a ROM and get one of two results....1) the ROM would run for a few seconds and then reboot, or 2) the ROM would run, but everything would fc. Fixing permissions, wiping everything, etc., wouldn't help the issue. No matter what I tried under TWRP, those were the results. I ended up having to start from scratch to negate whatever it was that was making the xoom go funky. Once I pushed rogue and followed the same process, I was back in business.
Sent from my Xoom using Tapatalk 2
Hello people, I know there are already threads about this but I just can't figure out what I'm doing wrong..
I was running cyanogenmod on my device when suddenly everything started to force close so I decided to try out another rom, Miui.
(http://agaragar-agaragar.appspot.com/forum.xda-developers.com/showthread.php?t=2221606)
I have done this flashing of roms before already which went all well, so I decided it would be a good idea to forget to make a backup :silly:
and this is what I did:
wipe data/factory reset
wipe cache partition
wipe dalvik cache
and then I tried to flash Miui, but it says:
Finding update package...
Opening update package...
E:Can't open /sdcard/miui.zip
(bad)
Installation aborted.
what I tried to solve:
Redownloading the zip in different browsers.
Trying different recovery (first try was in CWM, then I tried TWRP)
Tried flashing from a different SD card
Tried reformating SD card
I also tried to flash different roms, but everything that I try to flash gives the same error, so I think there is a problem with my phone and not with the zip which I try to flash.
Also something went wrong while trying to solve the problem and now I dont have any OS installed on my phone so I can only use recovery and a PC to solve this problem.
Can you guys please help me?
I have been searching for a solution on the internet for a whole day now and I have still not found a solution!
kpro1996 said:
Hello people, I know there are already threads about this but I just can't figure out what I'm doing wrong..
I was running cyanogenmod on my device when suddenly everything started to force close so I decided to try out another rom, Miui.
(http://agaragar-agaragar.appspot.com/forum.xda-developers.com/showthread.php?t=2221606)
I have done this flashing of roms before already which went all well, so I decided it would be a good idea to forget to make a backup :silly:
and this is what I did:
wipe data/factory reset
wipe cache partition
wipe dalvik cache
and then I tried to flash Miui, but it says:
Finding update package...
Opening update package...
E:Can't open /sdcard/miui.zip
(bad)
Installation aborted.
what I tried to solve:
Redownloading the zip in different browsers.
Trying different recovery (first try was in CWM, then I tried TWRP)
Tried flashing from a different SD card
Tried reformating SD card
I also tried to flash different roms, but everything that I try to flash gives the same error, so I think there is a problem with my phone and not with the zip which I try to flash.
Also something went wrong while trying to solve the problem and now I dont have any OS installed on my phone so I can only use recovery and a PC to solve this problem.
Can you guys please help me?
I have been searching for a solution on the internet for a whole day now and I have still not found a solution!
Click to expand...
Click to collapse
try changing your sdcard
and check if you haven't have shortcut virus in your pc
try downloading new zip pack
and use twrp recovery ,go to advance options and open file manager, check there if there is any un-named folder in your sdcard delete it and then try flashing the rom.:fingers-crossed:
i hope this will work
hit thanks if helped
nit_in said:
try changing your sdcard
and check if you haven't have shortcut virus in your pc
try downloading new zip pack
and use twrp recovery ,go to advance options and open file manager, check there if there is any un-named folder in your sdcard delete it and then try flashing the rom.:fingers-crossed:
i hope this will work
hit thanks if helped
Click to expand...
Click to collapse
I already tried using another sdcard
what do you mean with downloading a new zip pack?
I did try to redownload the rom though.
when I get back from school I will try the twrp recovery thingy, I hope it works!!
Try flashing garuda kernel first in my signature there is a link for it, after that try with some rom, I doubt that this will work but.... that's the best I can think of now. Changing recovery is maybe your best bet. Also try with some other rom, who knows.
kpro1996 said:
I already tried using another sdcard
what do you mean with downloading a new zip pack?
I did try to redownload the rom though.
when I get back from school I will try the twrp recovery thingy, I hope it works!!
Click to expand...
Click to collapse
i hope so
and check if your pc haven't have shortcut virus
I now use twrp recovery,
when I pressed the button 'power off' in twrp it said:
Install Superuser
your device does not appear to be rooted
blah blah
so somehow my phone is de-rooted
I'm going to install superuser and then try to instal a rom, I will post what happened.
wish me luck
okay now ive insalled superuser again, I tried different zips the first 2 it was complaining something about md5 but the third one installed fine(my first succes since a long time )
this means my phone is rooted again right? becauses twrp does not say it is not.
but I still cant install a rom though, but i haven't tried installing the kernel you mentioned, is this the right link for the download?
github.com/digitalcode
EDIT:
I couldn't find a good download for garuda kernel so I downloaded cranium kernel which installed fine!
but I can still not install a rom, I try to instal miui v4 revised, if that doesn't work i try to instal the stock west european rom, and if that doesn't work I try to install cm10, but nothing works all the same (bad) error!
help me, do I really need garuda kernel? if so can you please give me a download link to the zip?
EDIT 2:
Maybe if I use another PC to copy the zips to the SD, will that work?
I'm gonna try, I'm now open to try everything that comes to my mind, I really want my phone to be working again!!
kpro1996 said:
I already tried using another sdcard
what do you mean with downloading a new zip pack?
I did try to redownload the rom though.
when I get back from school I will try the twrp recovery thingy, I hope it works!!
Click to expand...
Click to collapse
kpro1996 said:
okay now ive insalled superuser again, I tried different zips the first 2 it was complaining something about md5 but the third one installed fine(my first succes since a long time )
this means my phone is rooted again right? becauses twrp does not say it is not.
but I still cant install a rom though, but i haven't tried installing the kernel you mentioned, is this the right link for the download?
github.com/digitalcode
EDIT:
I couldn't find a good download for garuda kernel so I downloaded cranium kernel which installed fine!
but I can still not install a rom, I try to instal miui v4 revised, if that doesn't work i try to instal the stock west european rom, and if that doesn't work I try to install cm10, but nothing works all the same (bad) error!
help me, do I really need garuda kernel? if so can you please give me a download link to the zip?
EDIT 2:
Maybe if I use another PC to copy the zips to the SD, will that work?
I'm gonna try, I'm now open to try everything that comes to my mind, I really want my phone to be working again!!
Click to expand...
Click to collapse
to skip thre md5 check on flashing rom
in twrp recovery go to settings and uncheck force md5 verification of zip file
and try to flash rom
if any error you get post it
if works hit thanks
ps:do not flash superuser before flashing rom
and do a clean installation,wipe everything and then flashing
if flashing sense or jaggy rom create ext partition
good luck mate
i wish this will work for u
SUCCES!!
I FINALLY GOT MY PHONE BACK!!!
I think the problem actually was with the copying of the file from my pc to the phone,what I normally did was : take out the sd card, put it in a reader and then copy the files to the sd.
Now I connected my phone while in twrp to my pc with a wire and then copied the zip file to the phone !!!
its such a simple solution but so hard to find!!
my phone is booting right now I hope it works!
it takes a long time, probably building the dalvik cache..
fingers crossed
All right! My phone is working again now! I'm going to install a mount 2 SD script and then i'mdone for a while with all this stuff! Thank you all who helped me!