I am installing MIUI on my mytouch 4g and i keep getting an sd card read error, tried just doing a restore and it wont even do that. it says
assert failed: getprop("ro.product.device") == " passion" ll getprop("ro.build.product") == "passion"
E:Error in /sdcard/ muiu name
(status 7)
install aborted
I also just tried installing the recovery it goes thru but when i reboot it goes back to the clockworkmod recovery v2.5.1.2
please help
seanj2247 said:
I am installing MIUI on my mytouch 4g and i keep getting an sd card read error, tried just doing a restore and it wont even do that. it says restore complete but it doesnt take on the phone please help
Click to expand...
Click to collapse
Did you ever install any of the cm7 builds? Sounds like a bad/wrong recovery.
no whats that?
seanj2247 said:
no whats that?
Click to expand...
Click to collapse
NVM.
Are you trying to install a backup or a rom?
seanj2247 said:
I am installing MIUI on my mytouch 4g and i keep getting an sd card read error, tried just doing a restore and it wont even do that. it says
assert failed: getprop("ro.product.device") == " passion" ll getprop("ro.build.product") == "passion"
E:Error in /sdcard/ muiu name
(status 7)
install aborted
I also just tried installing the recovery it goes thru but when i reboot it goes back to the clockworkmod recovery v2.5.1.2
please help
Click to expand...
Click to collapse
Your installing a rom for the wrong device. Ours is the glacier, not passion.
i also tried with the glacier as well samething, and its a rom not a back up...i tried installing rodriguez muiu rom first, i saw it operating off of youtube for the mytouch 4g any ideas whats wrong and how to fix it?
use this one
http://forum.xda-developers.com/showthread.php?t=874257
for the N1 or desire and its in chinese does that matter?
seanj2247 said:
for the N1 or desire and its in chinese does that matter?
Click to expand...
Click to collapse
The one i linked too is for the mytouch4g. And its not in chinese. Read the whole OP of that thread.
i see it....this install should work?
ok, heres a direct link to the file you need to flash.
http://www.megaupload.com/?d=MJZA3P6K
its up and running i owe u bigtime ur a life saver!!!!
I dont know abouyt life saver, but you're welcome anyway. lol.
no 4g service?
seanj2247 said:
no 4g service?
Click to expand...
Click to collapse
Its 4g, just no icon for it.
how would i just go back to the restore since i tried previously but couldnt. or is it just gone forever?
some people should just leave their phone stock
just sayin
Please post questions in Q&A section.
Related
I've flashed it before, but decided to install evil's rom (reverted back to 2.5.1.2).. I didn't like it so I went back and restored CM7, now I can't flash 2.5.1.4.. I get an error saying "an error occurred while flashing your recovery". Please help! I'm new to these stuff, thanks guys.
Skunk2 DC said:
I've flashed it before, but decided to install evil's rom (reverted back to 2.5.1.2).. I didn't like it so I went back and restored CM7, now I can't flash 2.5.1.4.. I get an error saying "an error occurred while flashing your recovery". Please help! I'm new to these stuff, thanks guys.
Click to expand...
Click to collapse
Same thing happend to me this morning. it was weird cause before that i was flashing it fine in order to use CM7. I tried reboots but still nothing. I then just flashed ICE and used the rom manager from the ice Rom and it worked. I was able to flash 2.5.1.4. Try that.
I'll give that a shot, thanks!
Sent from my HTC Glacier using XDA App
k20matt said:
Same thing happend to me this morning. it was weird cause before that i was flashing it fine in order to use CM7. I tried reboots but still nothing. I then just flashed ICE and used the rom manager from the ice Rom and it worked. I was able to flash 2.5.1.4. Try that.
Click to expand...
Click to collapse
IT WORKED! Thanks again!
How did it work? Share what you did.
Same thing happened to me yesterday.
Check the clockwork/download/mirror1.kanged.net/recoveries folder on your SD card. Is there a .img file in there called recovery-clockwork-2.5.1.4-glacier.img? If it's not in there that's why you can't flash it, because it can't find the file.
Not sure why the file was missing from the folder.. but thats what it turned out to be.
You should be able to download the image from: http://phones.crackflashers.com/glacier/recoveries/glacier-cwm3src-2.img
Or you can get the file already named correctly out of this zip: http://goo.gl/nZJ7U
But you'll have to dig for it to find it.
then rename it to exactly "recovery-clockwork-2.5.1.4-glacier.img" and put it in the folder. It should work then.
shortskoolbus it makes no diff. Now if you were missing the file then it would give you this error message "No legacy recoveries found, Are you connected to the internet?" and if you do have the file then it gives you this error message "An error occurred while flashing your recovery."
I was trying to install new OC kernel and came across this as I originally thought it maybe linked to ClockworkMod as some folks in thread reported installing kernel without wipe cache/davlik. So I try to update it to 3.0.0.5 and it was successful but without result so I had to manually install 3.0.0.0 via console.
As I posted it originally on Q&A section when it happened none had issue and now everyone is having issue, POS I can't even access Dev thread as its says I need 10 posts when I have more I can't post it.
OptLynx said:
How did it work? Share what you did.
Click to expand...
Click to collapse
I just flashed ice glacier, went to rom manager, select all clockworkmod recoveries, select 2.5.1.4, and that's that
Sent from my HTC Glacier using XDA App
OptLynx said:
shortskoolbus it makes no diff. Now if you were missing the file then it would give you this error message "No legacy recoveries found, Are you connected to the internet?" and if you do have the file then it gives you this error message "An error occurred while flashing your recovery."
I was trying to install new OC kernel and came across this as I originally thought it maybe linked to ClockworkMod as some folks in thread reported installing kernel without wipe cache/davlik. So I try to update it to 3.0.0.5 and it was successful but without result so I had to manually install 3.0.0.0 via console.
As I posted it originally on Q&A section when it happened none had issue and now everyone is having issue, POS I can't even access Dev thread as its says I need 10 posts when I have more I can't post it.
Click to expand...
Click to collapse
Well I had the problem and went through the steps i described above to get it to work... So not sure.
Oh and it didn't say no legacy recoveries found, it said there was an error trying to flash. But it's working fine for me now after I out the img in that folder... so up to you guys if you want to try it.
Sent from my HTC Glacier using XDA App
Skunk2 DC said:
I've flashed it before, but decided to install evil's rom (reverted back to 2.5.1.2).. I didn't like it so I went back and restored CM7, now I can't flash 2.5.1.4.. I get an error saying "an error occurred while flashing your recovery". Please help! I'm new to these stuff, thanks guys.
Click to expand...
Click to collapse
its not just you, everyone is getting this error. Youll need to flash cwm 3 through fastboot or terminal emulator if you want to go to CM7 or MIUI until TrueBlue_Drew gets it fixed and releases an update.
Skunk2 DC said:
IT WORKED! Thanks again!
Click to expand...
Click to collapse
No Problem. Glad it worked. it was the only way i knew.
OptLynx said:
shortskoolbus it makes no diff. Now if you were missing the file then it would give you this error message "No legacy recoveries found, Are you connected to the internet?" and if you do have the file then it gives you this error message "An error occurred while flashing your recovery."
I was trying to install new OC kernel and came across this as I originally thought it maybe linked to ClockworkMod as some folks in thread reported installing kernel without wipe cache/davlik. So I try to update it to 3.0.0.5 and it was successful but without result so I had to manually install 3.0.0.0 via console.
As I posted it originally on Q&A section when it happened none had issue and now everyone is having issue, POS I can't even access Dev thread as its says I need 10 posts when I have more I can't post it.
Click to expand...
Click to collapse
Actually I am not sure what you are talking about OptLynx. What shortsloolbus said is 100% correct. If you are missing the image or it is in the wrong place it does not give you the "no legacy recoveries found" error. It will just say "error flashing recovery". And the reason it worked when people switched to a old Ice glacier rom is because IG isnt running the latest Rom Manager that has now changed the location of where it keeps the recovery images.
See my thread here for the new zip that places everything in the correct place. http://goo.gl/O5SlI
hi guys. I have a huge weird problem after the downgrade.
on MIUI (last release) i can mount the external sd and the internal, but cannot copy to them, because they are write protected :O , when i saw this was like WTF?!?!
can someone explain me what can I do to overcome this problem!? I've tried system restore aka wipe data/cache, already tried to flash again and the problem persists.
What can I do? Even on stock 2.2.2 after the downgrade, i can mount the external SD but after unmount i need to mount it on the memory tab in definitions.
Someone with know how, pls help me!
Thks in advance.
If necessary i can try a logcat of something if it helps (but i need some advice on this too)
enter project menu and test other USB modes... In my case works on google mode.
Sent from my U8800 using XDA App
nrdl said:
enter project menu and test other USB modes... In my case works on google mode.
Sent from my U8800 using XDA App
Click to expand...
Click to collapse
Sorry for my noobish, but where can i find that menu?
menu
Dial * # * # 2846579 # * # *
Go to projectmenu, background settings, log settings, log switch and set Log on
And
Set USB menu, you have that you want.
How did you downgrade I get a boot loop after trying to install miui after downgrading to 2.2
Sent from my U8800 using xda premium
Hayden18 said:
How did you downgrade I get a boot loop after trying to install miui after downgrading to 2.2
Sent from my U8800 using xda premium
Click to expand...
Click to collapse
Remember to do a factory reset / clear cache inbetween flashes. I always do and have never had any problem with bootlooping. Think it has something to do with filesystem changes from 2.2 to 2.3 (EXT3/EXT4 etc.). I also clear Dalvik-cache.
ivosantospt said:
Dial * # * # 2846579 # * # *
Go to projectmenu, background settings, log settings, log switch and set Log on
And
Set USB menu, you have that you want.
Click to expand...
Click to collapse
hi again. I'm on MIUI and I can't access that menu.
Conclusion... If I want to put my cell phone on it normal state, I need to flash it again with 2.3.5 right!?
ohh god! Never more Huawei... NEVER!
Could someone tell me if I have another way to put things right again!?
ohh god!
320 views and no one can help me!
Hmm. You're using an after-market ROM and blaming Huawei, interesting
Anyway, yeah it looks like dial foo doesn't work in cm7 either. It might work in 2.2 stock, but you'd have to flash 2.2 or 2.3 from Huawei in any case.
Sent from my u8800 using xda premium
ksatta said:
Hmm. You're using an after-market ROM and blaming Huawei, interesting
Anyway, yeah it looks like dial foo doesn't work in cm7 either. It might work in 2.2 stock, but you'd have to flash 2.2 or 2.3 from Huawei in any case.
Sent from my u8800 using xda premium
Click to expand...
Click to collapse
lol ksatta. you are a little bit right. but it's the same situation in official rom or miui or cm7 or anything else. Today i will try to flash the stock 2.3.5 rom again and see what is gonna to happen.
Yeah the official beta seems to mess up SDcards on many occasions, lots of people having problems. Ofcourse it's Beta, but still I guess it's ok to blame Huawei a bit
I wonder if the USB mode thing fixes it, we're trying to solve similar issues in the beta 1 V2 thread.
I Went back to miui after official beta2. Everything else is fine, but now i cant access to internal sd at all... External works fine. Tried change sd usage setting from x5 settings without success..
And another thing.. Does anyone have that huaweis backup program apk? I'd like to install that so i can restore my backup.
jukkus said:
I Went back to miui after official beta2. Everything else is fine, but now i cant access to internal sd at all... External works fine. Tried change sd usage setting from x5 settings without success..
Click to expand...
Click to collapse
Hmm, do the stock roms even support internal SD when external is inserted? not sure. Anyway I remember that in CM7 there was in the changelog at one point that internal SD is mounted as /foo.
ksatta said:
Hmm, do the stock roms even support internal SD when external is inserted? not sure.
Click to expand...
Click to collapse
I´m stuck with 2.3.5 beta 1 and it supports both. But dammit I want to flash MIUI again.
The new CWM doesn´t work for me. And I´m afraid to brick this crap trying the downgrade 2.2
NihilistWarGod said:
I´m stuck with 2.3.5 beta 1 and it supports both. But dammit I want to flash MIUI again.
The new CWM doesn´t work for me. And I´m afraid to brick this crap trying the downgrade 2.2
Click to expand...
Click to collapse
Did you tried genlokar's CWM 5.0.2.7 (originally made for pro version)?
This one also works with normal U8800.
boss_y said:
Did you tried genlokar's CWM 5.0.2.7 (originally made for pro version)?
This one also works with normal U8800.
Click to expand...
Click to collapse
I´ve tried that, since it is supposed to be the only CWM that works with official 2.3.5
But after the 3 wipes when I try to flash any custom rom I get:
assert failed: getprop("ro.product.device") == "u8800" || getprop("ro.build.product") == "u8800" || getprop("ro.product.board") == "u8800"
E:Error in /etc etc path.../
status 7 installation aborted
ksatta said:
Hmm, do the stock roms even support internal SD when external is inserted? not sure. Anyway I remember that in CM7 there was in the changelog at one point that internal SD is mounted as /foo.
Click to expand...
Click to collapse
You're right. They don't mount as sdcard at the same time. In my case I can't mount internal SD even without external. It seems to be mounted as /emmc all the time. Not as sdcard.
Continuing this in development/MIUI multilingual thread. Seems like I'm not alone. Some problems with su...
NihilistWarGod said:
I´ve tried that, since it is supposed to be the only CWM that works with official 2.3.5
But after the 3 wipes when I try to flash any custom rom I get:
assert failed: getprop("ro.product.device") == "u8800" || getprop("ro.build.product") == "u8800" || getprop("ro.product.board") == "u8800"
E:Error in /etc etc path.../
status 7 installation aborted
Click to expand...
Click to collapse
You can get it to flash if you comment out the assert(..) line from the .zip/META-INF/com/google/.../updater-script. I got CM7 to flash OK without downgrading to 2.2 first, BUT I didn't get CM7 to boot, tried lots of things. The assert line just aborts the script if the phone is not a U8800, the recovery might report it as u8800pro or something.
I think the 2.3 update also updates some of the non-standard partitions or something, but it might take a while before I look into it again, I spent way too much time on it yesterday
ksatta said:
You can get it to flash if you comment out the assert(..) line from the .zip/META-INF/com/google/.../updater-script. I got CM7 to flash OK without downgrading to 2.2 first, BUT I didn't get CM7 to boot, tried lots of things. The assert line just aborts the script if the phone is not a U8800, the recovery might report it as u8800pro or something.
I think the 2.3 update also updates some of the non-standard partitions or something, but it might take a while before I look into it again, I spent way too much time on it yesterday
Click to expand...
Click to collapse
Thanks a lot for the effort on that! I regret every day for trying huawei's gingerbread...
NihilistWarGod said:
Thanks a lot for the effort on that! I regret every day for trying huawei's gingerbread...
Click to expand...
Click to collapse
Well, when the sources are released and all the custom roms are updated with those, things will be better
So ill tell you all that happened.
I wanted to install the elite blade s4 rom which required creating an sd card partition so i went to recovery created 1024mb partition and 128mb swap as written in the rom page after that i flashed the s4 and it worked perfectly for a few days after that, one day my battery was on 89% and i turned the screen off and later when i tried to turn it on again it didnt happen therefore i connected it to the charger and tried so then it went into a bootloop and if i took out the charger it just vibrated and didnt switch on.i tried flashing the rom again from clockwork still the same problem i tried flashing cm7 still the same problem then when i thought of trying gsf r3 it showed
E:error in /sdcard/gsf-blade-r3.zip
(Status 7)
Installation aborted
What do i do?!
I forgot to mention that it doesnt boot unless i connect it to the comp
I similar issue with cm7 ics version from this forum the Dev section. I tried everything. Finally I bought an other ZTE blade. The old one is good as dead as it's not even powering.
advise.. Keep off the unstable roms with the blade.
Sent from my Blade using xda premium
xyz`1 said:
E:error in /sdcard/gsf-blade-r3.zip
(Status 7)
Installation aborted
What do i do?!
I forgot to mention that it doesnt boot unless i connect it to the comp
Click to expand...
Click to collapse
I think your SD card is corrupted or failing. You should format it in a computer without any EXT or SWAP partition. After that try to install CyanogenMod, Swedish Snow or any other ROM that doesn't require EXT or SWAP partition.
Which ClockWorkMod version do you use? I suggest 5.0.2.0.
I downloaded CM 7.1 stable for my Nook color, and when I go to install I get an assert error with a "status 7".
I've done a lot of flashing of ROMs on my DX, but I'm wondering if there's a step I'm missing. I've pretty much just done the usual routine for flashing a new ROM:
- nandroid backup
- wipe cache,system,data,dalvik cache
- flash ROM zip file
No luck for any ROM I've tried. Anyone know what I need to do to get this to work?
Go over the steps in my sig. If that's no help check out the links in it particularly eyeballer's and mrg666's.
Thanks, I'll try it out. Why don't the official CM7 and MIUI builds work?
Are there other Mirage Kangs I can try out? Any good ICS ones?
Thanks again,
Mike
Also, I'm assuming if I have CWMR already installed I don't need the boot SD, correct?
Same problem. I get
assert failed: getprop("ro.product.device") == "encore" || getprop("ro.build.product") == "encore" || getprop("ro.product.board") == "encore"
E: Error in /sdcard/download/encore_CM72_MiRaGe-06082012.zip
(Status 7)
Installation aborted.
Does this mean I have to do the SDcard boot?
In theory you could put any ROM in place of M-K you wanted but if you are wanting ICS I would install using one of those instruction threads. All I was suggesting was that you go over the basic steps I outline to make sure you weren't missing anything.
And yes, it sounds like something got corrupted and you need to start from scratch. I would at this point. I always look at it as time to flush the old and try out some new.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
So, I tried unrooting and doing a stock recovery, then using a boot-sdcard to flash any number of ROMs. I still get the same error.
At this point it seems something is fundamentally wrong. I tried several options on the flashing, nothing seems to get around this error.
Is there anything else I can do here?
Sent from my DROIDX using Tapatalk 2
mikecico said:
So, I tried unrooting and doing a stock recovery, then using a boot-sdcard to flash any number of ROMs. I still get the same error.
At this point it seems something is fundamentally wrong. I tried several options on the flashing, nothing seems to get around this error.
Is there anything else I can do here?
Sent from my DROIDX using Tapatalk 2
Click to expand...
Click to collapse
When you say you were able to do a stock recovery, what did you mean by that? Were you able to flash a stock ROM to emmc with recovery? Or did you do an 8 failed boot reset?
Also, what version of CWM are you using?
The problem you are having is the install zip cannot verify that it is flashing to the correct device. If it can't find that 'encore' in your properties it will abort. I'm not sure where that property is stored on your emmc, but the zip is not finding it.
Sent from my Nook Color running ICS and Tapatalk
leapinlar said:
When you say you were able to do a stock recovery, what did you mean by that? Were you able to flash a stock ROM to emmc with recovery? Or did you do an 8 failed boot reset?
Also, what version of CWM are you using?
Click to expand...
Click to collapse
I did a factory reset from the nook settings. Is that not sufficient?
I'm using CWM 5.x (don't have it handy to check, I can get the exact version if needed).
leapinlar said:
The problem you are having is the install zip cannot verify that it is flashing to the correct device. If it can't find that 'encore' in your properties it will abort. I'm not sure where that property is stored on your emmc, but the zip is not finding it.
Sent from my Nook Color running ICS and Tapatalk
Click to expand...
Click to collapse
What do you mean by emmc? I'm having to dig a little deeper on this one than I usually do, so I'm not familiar with all the terms.
It sounds like my root-revert wasn't as complete as I thought.
Sent from my DROIDX using Tapatalk 2
mikecico said:
I did a factory reset from the nook settings. Is that not sufficient?
Click to expand...
Click to collapse
No, you'll need to either flash the original version of your firmware or do an 8+1 reset.
mikecico said:
What do you mean by emmc?
Click to expand...
Click to collapse
Embedded Multimedia Card. The flash memory internal to the Nook Color.
Keep listening to leapinlar. Nothings broke beyond repair and he's teaching more than you in this thread.
mikecico said:
I did a factory reset from the nook settings. Is that not sufficient?
I'm using CWM 5.x (don't have it handy to check, I can get the exact version if needed).
What do you mean by emmc? I'm having to dig a little deeper on this one than I usually do, so I'm not familiar with all the terms.
It sounds like my root-revert wasn't as complete as I thought.
Sent from my DROIDX using Tapatalk 2
Click to expand...
Click to collapse
Emmc means embedded multimedia card. It is basically an SD card built into the Nook. It is where all of your internal information is stored. It is partitioned into 8 partitions to hold various kinds of information, like the system files for your ROM, and data that is specific to your installation (application settings, your login info, etc.).
When you did the factory reset it cleared the data info, but not the system info. That is good if you want your stuff off, but it does nothing to the system files (including the root files). So someone else could put their info in and yours will be gone.
Somewhere on one of those 8 partitions is info stored that tells the zip you are an encore. (It's 1, 2 or 3, I just don't know which). The zip is not finding it. That could be because one of those partitions is corrupt. Or the data could just be missing.
If you truly did a factory restore, like flashing a factory zip to emmc, then the info might come back.
OK, thanks! Looks like I've got some homework to do.
Sent from my DROIDX using Tapatalk 2
I also think I had modified some of the system info when I originally rooted this thing. It's not my device, and now the owner (much father in law) wants more than just a rooted device, he wants the full tablet experience. And I like hacking someone else's device.
Long story short, I'm learning quite a bit here, so thanks...
Sent from my DROIDX using Tapatalk 2
mikecico said:
I also think I had modified some of the system info when I originally rooted this thing. It's not my device, and now the owner (much father in law) wants more than just a rooted device, he wants the full tablet experience. And I like hacking someone else's device.
Long story short, I'm learning quite a bit here, so thanks...
Sent from my DROIDX using Tapatalk 2
Click to expand...
Click to collapse
Try looking here (post 148). It is a Stock Rom zip for 1.4.1. Try flashing that with your CWM. Use the first one. It still has an assert statement in it so it may also fail, but it is worth a try.
status 7 error
I'm on and a nook tablet and I'm trying to flash 7.2 stable, I already have CM7 Alpha on the nook which the install had gone smoothly. I tried to use rom manager which gets me to clockworkmod but I get the same error - status 7 when trying to install the cm-7.2.0-encore.zip that I downloaded from cyanogenmod.com.
I've tried downloading it a couple of times, I've tried a bootable sd card but I still get status 7 when trying to install. I've followed the install guide cyanogenmod's wiki to the letter but I cannot get past that error. Anyone have any idea what might be causing it? Right now I'm back to CM7 Alpha.
Heretic09 said:
I'm on and a nook tablet and I'm trying to flash 7.2 stable, I already have CM7 Alpha on the nook which the install had gone smoothly. I tried to use rom manager which gets me to clockworkmod but I get the same error - status 7 when trying to install the cm-7.2.0-encore.zip that I downloaded from cyanogenmod.com.
I've tried downloading it a couple of times, I've tried a bootable sd card but I still get status 7 when trying to install. I've followed the install guide cyanogenmod's wiki to the letter but I cannot get past that error. Anyone have any idea what might be causing it? Right now I'm back to CM7 Alpha.
Click to expand...
Click to collapse
It's because you are on a Nook TABLET. CM 7.2 is for a Nook COLOR. They are completely different devices. If you want to brick your Tablet, keep trying to install this!
Sent from my Nook Color running ICS and Tapatalk
mikecico said:
I also think I had modified some of the system info when I originally rooted this thing. It's not my device, and now the owner (much father in law) wants more than just a rooted device, he wants the full tablet experience. And I like hacking someone else's device.
Long story short, I'm learning quite a bit here, so thanks...
Sent from my DROIDX using Tapatalk 2
Click to expand...
Click to collapse
mikecico, are you sure you are on a nook color? They look almost identical, but the nook color has a black bezel and the nook tablet is silver. Like I said in my post above, they are different devices and that may be why the zip is rejecting the install. It's doing its job.
Sent from my Nook Color running ICS and Tapatalk
I just did a check on the model number, BNTV250. It's a tablet.
Sorry for the noise guys. I think he had told me it's a NC, and I used a NC root method successfully, so I had assumed that was correct.
Mike
Hello i try installing a couple roms from the mytouch 4g dev section but it wont install,all it says its completed but it boots up to the stock OS. I also try to full wipe but it says its completed but it boots up normal.
jeff7790 said:
Hello i try installing a couple roms from the mytouch 4g dev section but it wont install,all it says its completed but it boots up to the stock OS. I also try to full wipe but it says its completed but it boots up normal.
Click to expand...
Click to collapse
Are you rooted or HTC devunlock??
Just to be sure you have a Mytouch 4G not the slide?
Can you post more info on your Hboot so we can help thanks.
jeff7790 said:
Hello i try installing a couple roms from the mytouch 4g dev section but it wont install,all it says its completed but it boots up to the stock OS. I also try to full wipe but it says its completed but it boots up normal.
Click to expand...
Click to collapse
root u r device install cwm wipe u r data install rom
Rom
nilesh.wankhede said:
root u r device install cwm wipe u r data install rom
Click to expand...
Click to collapse
You need to make sure that your phone is unlock and S-off, if not installing another rom would not work and it could damage your phone.