Related
My brother is traveling in India till the middle of may and his Vibrant 16gb that I unlocked, rooted, and installed CM7 has stopped booting and loops on the CM7 boot screen. had him go into recovery and clear the cache partition, but same thing happens..
so 2 things,
1. do photos by default save on his micro sd (2GB) or on the internal memory (16GB) he has over 1000 photos saved on the phone that he is worried about
losing...
2. if he completely wipes in recovery will he lose his pictures.
thanks! been months since i have had my hands on a vibrant, otherwise i could remember these things lol
Wiping data/factory reset from Recovery will NOT remove anything thats in your sdcard or internal sd.
What i suggest you do
Get into DOWNLOAD MODE, ODIN, stay on eclair and transfer the pictures before something else happens and you actually lose it, go on a flashing spree and flash other ROMS
If you need help getting into downloadmode/ odin etc. Just ask.
Thanks for the info.. he does not have access to a computer, thats why he hasnt been able to backup anything. he has only had cell/internet 2 weeks since january ..
If he still has the cm7 zip on his sdcard he should try reflashing
Yep, if he has any kind of ROM still on his SD, you can erase data/factory reset and then flash the ROM over it and it should be fine. Tell us what the ROM, if any, name is before you do it in case its like a eclair/froyo/gb/ics rom and it may not work directly.
Hi guys, I am trying to flash this ROM, I have to tell you that it is the first time I am doing it, but having problem. I have razr M rooted with supperSU, safestrep 3.11. I rebooted into SS3.11 and tried to create a ROM Slot, but it does nothing. I go to either rom slot out of 4 and see options, but nothing happens when I press create ROM button. I do message Space :0MB at the botom, although I have at least 10GB free on SD card and at least 2.5GB on the internal memory. Can you pelase help-Gene
gene.volchenko said:
Hi guys, I am trying to flash this ROM, I have to tell you that it is the first time I am doing it, but having problem. I have razr M rooted with supperSU, safestrep 3.11. I rebooted into SS3.11 and tried to create a ROM Slot, but it does nothing. I go to either rom slot out of 4 and see options, but nothing happens when I press create ROM button. I do message Space :0MB at the botom, although I have at least 10GB free on SD card and at least 2.5GB on the internal memory. Can you pelase help-Gene
Click to expand...
Click to collapse
I also replied to your question on DroidRzr.com.
When you create a new ROM slot in SS, all it does is setup the partitions for you to safely flash a new ROM. After the ROM slot is created, you need to choose the "Install" option for that ROM slot. Then, you will choose the "Energy ROM" zip from your SD. Make sure you only install aftermarket ROMs in one of the additional ROM slots, not in stock. Once you are comfortable with the new ROM, there are ways to install the ROM in the stock slot, but that will come in play later on
RikRong said:
I also replied to your question on DroidRzr.com.
When you create a new ROM slot in SS, all it does is setup the partitions for you to safely flash a new ROM. After the ROM slot is created, you need to choose the "Install" option for that ROM slot. Then, you will choose the "Energy ROM" zip from your SD. Make sure you only install aftermarket ROMs in one of the additional ROM slots, not in stock. Once you are comfortable with the new ROM, there are ways to install the ROM in the stock slot, but that will come in play later on
Click to expand...
Click to collapse
He nailed it. I will note that you say you have as 3.11. The latest for the RAZR M is 3.12. It can be found on droidrzr.com. Good luck!
timpohladthomas said:
He nailed it. I will note that you say you have as 3.11. The latest for the RAZR M is 3.12. It can be found on droidrzr.com. Good luck!
Click to expand...
Click to collapse
I installed V3.12, although in the applications view it says V3.12 and when I go to the safestrap recovery it says v3.11 (TWRP v2.2.2.1) strange ??
I go in Boot Options/ROM-Slot-1 chose wither 1GB, or 2GB or 3GB while System partition size of 1024MB and Cache partition size of 300 MB are already selected, at the bottom I see "Free Space:0MB (while I still have 10GB of SD and 3GB of internal free memory). Create ROM slot button does notv respond or does nothing when I press it.
Can you please help? Gene
gene.volchenko said:
I installed V3.12, although in the applications view it says V3.12 and when I go to the safestrap recovery it says v3.11 (TWRP v2.2.2.1) strange ??
I go in Boot Options/ROM-Slot-1 chose wither 1GB, or 2GB or 3GB while System partition size of 1024MB and Cache partition size of 300 MB are already selected, at the bottom I see "Free Space:0MB (while I still have 10GB of SD and 3GB of internal free memory). Create ROM slot button does notv respond or does nothing when I press it.
Can you please help? Gene
Click to expand...
Click to collapse
Safestrap must not be recognizing the free space on your internal sd card. I would recommend uninstalling safestrap, just to be safe confirm your root with root checker, and then install safestrap again. Just use a 1 gb rom slot to avoid any problems that may be occuring due to memory. Post back if the problem persists.
bgregs514 said:
Safestrap must not be recognizing the free space on your internal sd card. I would recommend uninstalling safestrap, just to be safe confirm your root with root checker, and then install safestrap again. Just use a 1 gb rom slot to avoid any problems that may be occuring due to memory. Post back if the problem persists.
Click to expand...
Click to collapse
Hi, I finally was able to install the ROM and power the phone up, but cannot really enjoy it, because cannot use company emails... My company requires storage formatting and wile this option exist on this ROM, it looks like it does not work, neither through the option provided via exchange remote service nor locally by going to settings\ security\format. Is there an option to do that? Also I am constantly running on the low memory. I wiped all apps from stock rom slot, did factory reset and wiped cashe etc, allocated 2gb to Rom slot1 and after installing rom there, before any apps installed, I only have 1.1gb free. Is there any way to increase storage? Last but not least camera with phosphere works even kind of in sphere mode, but the alignment movement is as slow as it could possibly be, it takes a min to move from first picture to the second. Did any guys experienced that?
Thanks a lot in advance for help---Gene
gene.volchenko said:
Hi, I finally was able to install the ROM and power the phone up, but cannot really enjoy it, because cannot use company emails... My company requires storage formatting and wile this option exist on this ROM, it looks like it does not work, neither through the option provided via exchange remote service nor locally by going to settings\ security\format. Is there an option to do that? Also I am constantly running on the low memory. I wiped all apps from stock rom slot, did factory reset and wiped cashe etc, allocated 2gb to Rom slot1 and after installing rom there, before any apps installed, I only have 1.1gb free. Is there any way to increase storage? Last but not least camera with phosphere works even kind of in sphere mode, but the alignment movement is as slow as it could possibly be, it takes a min to move from first picture to the second. Did any guys experienced that?
Thanks a lot in advance for help---Gene
Click to expand...
Click to collapse
As far as the email goes, I'm not sure. I'm not sure which ROM you're using now, but I believe that the 4.2 camera that is available on the ROMs for our phone isn't fully functional yet. Last I checked photoshpere doesn't work, but I could be wrong. The way I increased storage on my phone was to install my new ROM on to the stock partition. This is possible with safestrap, but you will want to make sure you have a backup of your stock ROM just in case something goes wrong. Once you make the backup of your stock ROM, download the custom ROM on to a different partition and set it up as you like. Then, make a backup of the custom ROM in recovery. Delete the partition that you created for the custom ROM and RESTORE the custom ROM backup on the stock partition. Restoring is important because installing does not work (I bricked my phone doing that). Then install safestrap on your new custom ROM and enjoy all the free space you had with your stock ROM!
bgregs514 said:
As far as the email goes, I'm not sure. I'm not sure which ROM you're using now, but I believe that the 4.2 camera that is available on the ROMs for our phone isn't fully functional yet. Last I checked photoshpere doesn't work, but I could be wrong. The way I increased storage on my phone was to install my new ROM on to the stock partition. This is possible with safestrap, but you will want to make sure you have a backup of your stock ROM just in case something goes wrong. Once you make the backup of your stock ROM, download the custom ROM on to a different partition and set it up as you like. Then, make a backup of the custom ROM in recovery. Delete the partition that you created for the custom ROM and RESTORE the custom ROM backup on the stock partition. Restoring is important because installing does not work (I bricked my phone doing that). Then install safestrap on your new custom ROM and enjoy all the free space you had with your stock ROM!
Click to expand...
Click to collapse
Okay, so here is the issue that I'm having. I have everything set up (SafeStrap, downloaded Eclipse v1.2 ROM, have it saved to my SD card), but when I go to actually flash the ROM, the screen says that it failed/unable to flash. I've tried removing the ROM slot, creating it again, and still getting the same issue. Also tried going into the stock recovery and clearing the cache partition from there, wiping the data, etc. Still got nothing. So now I'm really confused as far as what the problem is?
jase5273 said:
Okay, so here is the issue that I'm having. I have everything set up (SafeStrap, downloaded Eclipse v1.2 ROM, have it saved to my SD card), but when I go to actually flash the ROM, the screen says that it failed/unable to flash. I've tried removing the ROM slot, creating it again, and still getting the same issue. Also tried going into the stock recovery and clearing the cache partition from there, wiping the data, etc. Still got nothing. So now I'm really confused as far as what the problem is?
Click to expand...
Click to collapse
It's been a while since I've used SafeStrap so I'm not completely sure what the issue could be. Are you opposed to unlocking your bootloader? If not, there's a great selection of ROMs out there that are very amazing. Our phone has been receiving a lot of dev support lately and they have put much time in to some of these newer ROMs. I would recommend unlocking and installing a custom recovery to flash these with. There are many stock based ROMs out there that you can choose from if you prefer those, or there is a great deal of CM support as well. If you have any questions, don't hesitate to send me a message and I can walk you through the steps of unlocking and installing a custom recovery!
bgregs514 said:
It's been a while since I've used SafeStrap so I'm not completely sure what the issue could be. Are you opposed to unlocking your bootloader? If not, there's a great selection of ROMs out there that are very amazing. Our phone has been receiving a lot of dev support lately and they have put much time in to some of these newer ROMs. I would recommend unlocking and installing a custom recovery to flash these with. There are many stock based ROMs out there that you can choose from if you prefer those, or there is a great deal of CM support as well. If you have any questions, don't hesitate to send me a message and I can walk you through the steps of unlocking and installing a custom recovery!
Click to expand...
Click to collapse
Well here's the thing. I don't think that I can unlock my bootloader now. I've tried using the steps that were provided, but I guess that since I just got the phone a few days ago, it's downright impossible for me to do so. That's why I installed SafeStrap - because of that issue. If it was possible for me to unlock my bootloader now, I sure as heck would rather do that than go through the process I've gone through for the past couple of days. I will send you a message, and maybe you can help me out with unlocking the bootloader if it's possible?
http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
This is the only way that Ive been able to unlock my bootloader, run this utility and if it says Status code: 3 you are in luck! Even if it doesnt have the Unlocked Bootloader Warning upon startup you still are unlocked.
Good luck!
Got a question here on installing CROMi 4.2.1, love the ROM when I get it working, my problem is, whenever a new version is out and I try to install I run into all kinds of issues. I'll try to outline the exact problems I'm having here. It goes something like this, I will download new ROM, throw it onto SD card, then boot into recovery and attempt to install. Now if I try to install without clearing any caches/data etc. it will say it installs, but then it won't boot into the ROM at all, just sticks at ASUS screen. So I go through and clear everything, internal, system, dalvik cache etc. Then I try to install again, usually it will fail at least 5-6 times, sometimes it just won't do it at all, so I'll reboot, go into recovery again and try it, still no go. Then I'll use a different SD card, still won't work right, then I'll clear everything again and go for another try and after 3 or 4 or more failed times it will finally install and boot. So I'm curious if there's just something obvious and dumb that I'm missing here, or if it's just a normal issue with this and something that will always be there? It just doesn't make sense to me that it would fail so many times and just work for no apparent reason? Any pointers would be much appreciated!
I assume your using twrp 2.4.4.0-4.2 as your installing CROMi for 4.2.1 and on the 4.2.1 bootloader (10.6.1.8)?
If so not sure this is the issue but I have had & read of other's having issues with some micro sd cards using twrp 2.4.4.0-4.2
You could try in twrp doing a full wipe (cache, dalvik cache, factory reset, system, internal storage) then in twrp file manager copy the CROMi rom zip from your micro sd to your internal storage and install the rom from there and see if that works without issue.
pjc21 said:
I assume your using twrp 2.4.4.0-4.2 as your installing CROMi for 4.2.1 and on the 4.2.1 bootloader (10.6.1.8)?
If so not sure this is the issue but I have had & read of other's having issues with some micro sd cards using twrp 2.4.4.0-4.2
You could try in twrp doing a full wipe (cache, dalvik cache, factory reset, system, internal storage) then in twrp file manager copy the CROMi rom zip from your micro sd to your internal storage and install the rom from there and see if that works without issue.
Click to expand...
Click to collapse
Yep those are the versions I'm working with! Didn't realize there were sd card issues, thanks for the info. One last question, where should I copy the ROM to on the internal storage? Don't want to accidentally copy to a place that's gonna get wiped during install.
Sounds like you have something corrupted.
I'd do a full wipe of internal storage (making sure you have all your backups on external storage), flash the rom and see if that helps.
Also if your ext card is causing issues try booting without it in after the first flash.....
sbdags said:
Sounds like you have something corrupted.
I'd do a full wipe of internal storage (making sure you have all your backups on external storage), flash the rom and see if that helps.
Also if your ext card is causing issues try booting without it in after the first flash.....
Click to expand...
Click to collapse
The famous sbdags himself responds! Just wanted to take the opportunity to tell you that your ROM is incredible, puts the Transformer on par with, or better than the iPad. Installed RC2 this morning and it is running great! Thanks for all the great work. When I was having those install issues I would do a full wipe of internal, system, and all caches, but installs would still fail extremely often. The strange thing is, that after a few wipes, and numerous times trying to install, it would finally work and boot and everything would work fine. I'm thinking it has something to do with how the SD card interacts with the recovery system but maybe I don't know what I'm talking about. All that I know is that I downloaded on my tab this morning, and ran the install from the internal storage, and bam, flawless install the first time around. So I'm going to give some kudos to pjc21 because I think it was just an issue with the SD card interfacing with recovery.
asinglenoob said:
The famous sbdags himself responds! Just wanted to take the opportunity to tell you that your ROM is incredible, puts the Transformer on par with, or better than the iPad. Installed RC2 this morning and it is running great! Thanks for all the great work. When I was having those install issues I would do a full wipe of internal, system, and all caches, but installs would still fail extremely often. The strange thing is, that after a few wipes, and numerous times trying to install, it would finally work and boot and everything would work fine. I'm thinking it has something to do with how the SD card interacts with the recovery system but maybe I don't know what I'm talking about. All that I know is that I downloaded on my tab this morning, and ran the install from the internal storage, and bam, flawless install the first time around. So I'm going to give some kudos to pjc21 because I think it was just an issue with the SD card interfacing with recovery.
Click to expand...
Click to collapse
Glad to hear it worked as it should. :good::good::good:
Hi everyone, sorry to post but I'm at wits end.
I've searched and googled all over for the past week and have found problems similar to mine but none of the fixes have worked.
If this has already been asked I apologise and will remove but here goes:
I rooted my phone and using the latest cwm flashed the rc1 of cm10, this didnt flash properly so I tried again, no joy.
I read around and decided to try with a different recovery, twrp.
So I tried flashing with that, again no joy. so i used twrp to do factory reset and cache wipes. As I was unfamiliar with the layout of twrp I'm under the impression I've deleted or wiped the cache/system and data partitions.
I've since flashed a PIT file to restore the original partitions, gone back to stock tried reflashing new roms. Its been a nightmare.
The issue itself is no recovery can mount the ext-sd which is actually the internal memory and cannot access the cache/log etc.
The phone itself shuts down randomly and then will not boot up.
Adb can't write or push anything to the device either, the strange thing is when the phones working for brief periods of time I can read and write to device memory?so at this point I'm flat out of ideas.
Any help/ideas or advice would be gratefully received, once again thanks guys
kingbob134 said:
Hi everyone, sorry to post but I'm at wits end.
I've searched and googled all over for the past week and have found problems similar to mine but none of the fixes have worked.
If this has already been asked I apologise and will remove but here goes:
I rooted my phone and using the latest cwm flashed the rc1 of cm10, this didnt flash properly so I tried again, no joy.
I read around and decided to try with a different recovery, twrp.
So I tried flashing with that, again no joy. so i used twrp to do factory reset and cache wipes. As I was unfamiliar with the layout of twrp I'm under the impression I've deleted or wiped the cache/system and data partitions.
I've since flashed a PIT file to restore the original partitions, gone back to stock tried reflashing new roms. Its been a nightmare.
The issue itself is no recovery can mount the ext-sd which is actually the internal memory and cannot access the cache/log etc.
The phone itself shuts down randomly and then will not boot up.
Adb can't write or push anything to the device either, the strange thing is when the phones working for brief periods of time I can read and write to device memory?so at this point I'm flat out of ideas.
Any help/ideas or advice would be gratefully received, once again thanks guys
Click to expand...
Click to collapse
Try and root your phone again with this http://forum.xda-developers.com/showthread.php?t=2219803
Thanks for the suggestion, this is the root file I've been flashing already
kingbob134 said:
The issue itself is no recovery can mount the ext-sd which is actually the internal memory and cannot access the cache/log etc.
Click to expand...
Click to collapse
Ext sd is your sdcard.Internal memory is the system and data.
The pit file was not needed after you formatted the system.Its only for repartition.
My suggestion is to format system flash stock rom do a factory reset then reboot.
Sent from my GT-I9500 using Tapatalk 4
Sorry thats my mistake, I can't mount ext-sd in recovery to format it and nothing can be acessed in cache or cache/logs, hence I thought it was an issue with the partitions. I've tried your suggestion but will try again.
Thankyou
kingbob134 said:
Sorry thats my mistake, I can't mount ext-sd in recovery to format it and nothing can be acessed in cache or cache/logs, hence I thought it was an issue with the partitions. I've tried your suggestion but will try again.
Thankyou
Click to expand...
Click to collapse
Is your phone booting fine ? I didn't understand your actual problem.I just checked the recovery.Sd-ext is the second partion for the sdcard./external sd is the sdcard.
If cache can't be mounted just format it.
Sent from my GT-I9500 using Tapatalk 4
Hi again. Cache can be mounted and formatted but recovery can't access cache/logs. My biggest issue is that the phone will randomly close when under stress and hit a bootloop that can only be cured by attaching the charger. The phone does boot I'm currently running pacman ROM. Tbh I'm fairly certain I wiped something important but flashing stock and even a pit file hasn't corrected it
kingbob134 said:
Hi again. Cache can be mounted and formatted but recovery can't access cache/logs. My biggest issue is that the phone will randomly close when under stress and hit a bootloop that can only be cured by attaching the charger. The phone does boot I'm currently running pacman ROM. Tbh I'm fairly certain I wiped something important but flashing stock and even a pit file hasn't corrected it
Click to expand...
Click to collapse
Weired.Did you try other recoveries ? Unfortunately I don't have any idea of what else you can do.
I've tried cwm, twrp and am currently running philztouch recovery as this seems to be the most stable on my phone, I can mount every directory but sd-ext and it also cant format that directory.
I installed AParted app to it this afternoon during a shortlived moment of clarity, phone not me, and tried fixing partitions/blocks. the only viewable were /dev/block/mmcblk0 and /dev/block/mmcblk1
the former, blk1 had 4 pieces of varying sizes but no registered file system whilst the latter was fat32. Could it be that the unacessable sd-ext is in the wrong file format? I've read for cwm and philz it needs to be ext4 but I may be mistaken.
also the crashing seems to occur when an app or process attempts to write to our unaccesable area and leaves me in a bootloop stating the battery is dead. So weird...
beginning to lose hope of solving this and fixing my buggy phone
Anyone with any ideas/experience please help, I'm willing to try almost anything at this point
thanks again guys
ext-sd?
Have no idea about this, but who cares
Many TWRP and CWM first releases break /data and /cache when you format them in recovery
Only known fix for is to flash a full STOCK rom (sammobile tar.md5) using odin + PIT (the right one, memory wise)
All my last recovery releases fully support all format options on S4
By the way, internal storage = sdcard = /data
Thanks for your quick reply Phil. I've flashed back to stock multiple times using a pit file and the sammobile firmware for my device. No joy unfortunately. And your recovery brings back an error when trying to mount or format sd-ext. I don't know what the issue could be but its crashing my phone near constantly
kingbob134 said:
Thanks for your quick reply Phil. I've flashed back to stock multiple times using a pit file and the sammobile firmware for my device. No joy unfortunately. And your recovery brings back an error when trying to mount or format sd-ext. I don't know what the issue could be but its crashing my phone near constantly
Click to expand...
Click to collapse
Hi,
try to fix it tru kies recovery.
Have you tried formating your Ext SD card in a PC? maybe its corrupt?
Also the boot loop you mentioned, only being fixed by attaching a charger sounds like a faulty battery. Is it swollen in the middle?
I would try new SD card and/or battery and see if that helps.
I've tried lies and no joy. The sd-ext is a partition in the internal memory not the external SD card, confusing I know. Battery appears fine. During my reading someone mentioned it may be inaccessible due to it being in the wrong format also that it could've corrupted blocks of memory and the crash occurs when the phone tries to access said block. Any thoughts?
kingbob134 said:
I've tried lies and no joy. The sd-ext is a partition in the internal memory not the external SD card, confusing I know. Battery appears fine. During my reading someone mentioned it may be inaccessible due to it being in the wrong format also that it could've corrupted blocks of memory and the crash occurs when the phone tries to access said block. Any thoughts?
Click to expand...
Click to collapse
Hhhhmmm have you tried running a e2fsck on the sd-ext block?
Sd-ext is the second partition of the SD card while /external-sd is the primary.If you don't have a second partition that's normal if it can't get mounted.
Sent from my GT-I9500 using Tapatalk 4
sd-ext is in external_sd
If that's only error you get, it is not an error, it is normal
Google for sd-ext
ijnegea jessie
Well that clears that issue but still leaves me with the crashes and bootloop.
When I try to flash a ROM via recovery it isn't 100percent successful and it then says it can't access cache and cache/recovery/log even though when the phone is running they are visible so I know they're there. This is driving me to despair now. Thanks for the input guys
kingbob134 said:
Well that clears that issue but still leaves me with the crashes and bootloop.
When I try to flash a ROM via recovery it isn't 100percent successful and it then says it can't access cache and cache/recovery/log even though when the phone is running they are visible so I know they're there. This is driving me to despair now. Thanks for the input guys
Click to expand...
Click to collapse
Did you try a factory reset with philz recovery ? Technically that should format cache and data with a compatible filesystem
Sent from my GT-I9500 using Tapatalk 4
Styrke said:
Did you try a factory reset with philz recovery ? Technically that should format cache and data with a compatible filesystem
Sent from my GT-I9500 using Tapatalk 4
Click to expand...
Click to collapse
Yeah I tried that. Still nothing
Hello, I have a question that I would like to ask here. Until a few days ago, every time i would flash a new ROM and I would wipe my data, before flashing the ROM I would have 9,12GB free out of 9,12GB (I have the S4 16GB version). After I flashed another ROM (I don't remember which one), every time I would wipe everything for a new install, I would have 8,98GB free out of 9,12GB. This has never happened to me before. I tried flashing a stock firmware via odin, flashing a .pit file, I still have 8,98GB.
So my question is: is it possible to increase this storage to where it was before? Is it possible that a part of my internal memory has become unusable? I saw ways of increasing internal storage via microSD cards, but I am not looking for that. Thanks in advance!
luptatorul said:
Hello, I have a question that I would like to ask here. Until a few days ago, every time i would flash a new ROM and I would wipe my data, before flashing the ROM I would have 9,12GB free out of 9,12GB (I have the S4 16GB version). After I flashed another ROM (I don't remember which one), every time I would wipe everything for a new install, I would have 8,98GB free out of 9,12GB. This has never happened to me before. I tried flashing a stock firmware via odin, flashing a .pit file, I still have 8,98GB.
So my question is: is it possible to increase this storage to where it was before? Is it possible that a part of my internal memory has become unusable? I saw ways of increasing internal storage via microSD cards, but I am not looking for that. Thanks in advance!
Click to expand...
Click to collapse
Did you wipe internal storage too?
Sometimes there are files that remain even after rom flash. Happened to me once when game data of 2GB took space on my internal storage even though I couldn't find it. Had to switch back to the rom on which the game was installed in order to delete the game files.
I'm sure an internal storage wipe would've also done the trick, but I didn't want to wipe then.
GDReaper said:
Did you wipe internal storage too?
Sometimes there are files that remain even after rom flash. Happened to me once when game data of 2GB took space on my internal storage even though I couldn't find it. Had to switch back to the rom on which the game was installed in order to delete the game files.
I'm sure an internal storage wipe would've also done the trick, but I didn't want to wipe then.
Click to expand...
Click to collapse
I wiped absolutely everything. I also tried different recoveries, like TWRP and CWM.
luptatorul said:
I wiped absolutely everything. I also tried different recoveries, like TWRP and CWM.
Click to expand...
Click to collapse
Maybe flashing stock rom with a pit file will help. The pit file will repartition the phone.
GDReaper said:
Maybe flashing stock rom with a pit file will help. The pit file will repartition the phone.
Click to expand...
Click to collapse
I did that as well. I flashed OL4 firmware. It didn't really help...