So after I flashing Lineage os , it was working fine and until recently , so I was out without my phone and then when I got home I try to open my phone(power on) but didn't open . So I go and charge the phone and it was going well like the battery logo is there and everything is like normal . And then I go play some games , when I checked my phone again , it is at Lineage os boot logo and it is very very hot too . So I force shutdown it . And then take the batteries out to cooldown my phone , after that I try to start it again , but no use . So I went to recovery mode and wiped cache and dalvik cache using TWRP , but no use also , my phone still stuck at the boot logo .
I am very sorry for my bad english
Please help
You need to flash back to stock firmware and start over again. Something is corrupt.
Beamed in by telepathy.
shivadow said:
You need to flash back to stock firmware and start over again. Something is corrupt.
Beamed in by telepathy.
Click to expand...
Click to collapse
Can I transfer Lineage os and gapps to the phone without the phone being on ? Is there a way to transfer files to phone other that ADB SIDELOAD . And If I managed to transfer the files , can I flash the rom without losing the data ? Like the picture etc . Not the application .
Pixelzack said:
So after I flashing Lineage os , it was working fine and until recently , so I was out without my phone and then when I got home I try to open my phone(power on) but didn't open . So I go and charge the phone and it was going well like the battery logo is there and everything is like normal . And then I go play some games , when I checked my phone again , it is at Lineage os boot logo and it is very very hot too . So I force shutdown it . And then take the batteries out to cooldown my phone , after that I try to start it again , but no use . So I went to recovery mode and wiped cache and dalvik cache using TWRP , but no use also , my phone still stuck at the boot logo .
I am very sorry for my bad english
Please help
Click to expand...
Click to collapse
Try going to recovery and dirty flash the rom then wipe cache and dalvik then reboot.
By dirty flashing, i mean no wipes, just flash it over the existing one then wipe cache and dalvik then reboot.
MigoMujahid said:
Try going to recovery and dirty flash the rom then wipe cache and dalvik then reboot.
By dirty flashing, i mean no wipes, just flash it over the existing one then wipe cache and dalvik then reboot.
Click to expand...
Click to collapse
So , I tried to transfer rom and gapps to my phone through recovery , so when I mount storage , the device shown in my pc so I started transfer the files , when it reached around 39% , the device is missing . So I unmount the storage at TWRP and re-mount it . But no use , the device is not detected . What should I do?
Pixelzack said:
So , I tried to transfer rom and gapps to my phone through recovery , so when I mount storage , the device shown in my pc so I started transfer the files , when it reached around 39% , the device is missing . So I unmount the storage at TWRP and re-mount it . But no use , the device is not detected . What should I do?
Click to expand...
Click to collapse
Try using a different cable and a different USB port.
And check if MTP is enabled in "mount" through the button in the down right corner, it should say "disable MTP".
MigoMujahid said:
Try using a different cable and a different USB port.
And check if MTP is enabled in "mount" through the button in the down right corner, it should say "disable MTP".
Click to expand...
Click to collapse
Its a success ! although dirty flashing didn't work but I managed to transfer the files and flashed it . Thank you so much sir! :fingers-crossed: :fingers-crossed: :good: :good: :good:
MigoMujahid said:
Try using a different cable and a different USB port.
And check if MTP is enabled in "mount" through the button in the down right corner, it should say "disable MTP".
Click to expand...
Click to collapse
Hi sir , the problem came back , but this time , I noticed "Failed to mount /efs . Invalid Argument" when factory reset through TWRP . I was going to factory reset and then flash rom and Gapps but what should I do with the /efs ?
Pixelzack said:
Hi sir , the problem came back , but this time , I noticed "Failed to mount /efs . Invalid Argument" when factory reset through TWRP . I was going to factory reset and then flash rom and Gapps but what should I do with the /efs ?
Click to expand...
Click to collapse
OK, try flashing your Stock ROM with Odin first.
and see if everything goes right.
then you will have to re-flash the TWRP and try again.
Pixelzack said:
Hi sir , the problem came back , but this time , I noticed "Failed to mount /efs . Invalid Argument" when factory reset through TWRP . I was going to factory reset and then flash rom and Gapps but what should I do with the /efs ?
Click to expand...
Click to collapse
Make sure your imei still exists. If not then you need to fix the efs partition before you can proceed. Factory reset should always be done via the device software, NEVER TWRP!. TWRP has a habit of killing phones.
Beamed in by telepathy.
shivadow said:
Make sure your imei still exists. If not then you need to fix the efs partition before you can proceed. Factory reset should always be done via the device software, NEVER TWRP!. TWRP has a habit of killing phones.
Beamed in by telepathy.
Click to expand...
Click to collapse
if TWRP kills phones, then it wouldn't have been the most famous and the most used custom recovery in the android world.
he can do factory reset from there as long as he isn't using stock ROM, and even if he uses stock ROM, it does no harm, but it's more preferable that he uses stock recovery for that.
MigoMujahid said:
if TWRP kills phones, then it wouldn't have been the most famous and the most used custom recovery in the android world.
he can do factory reset from there as long as he isn't using stock ROM, and even if he uses stock ROM, it does no harm, but it's more preferable that he uses stock recovery for that.
Click to expand...
Click to collapse
Twrp has caused more mount issues than you've had hot dinners. The reason twrp is the 'most famous' recovery is because it's the only current recovery, Cwm is defunct. Cwm didn't cause mount issues, it only came about with twrp, on ALL devices.
I have also fixed the mount issue with twrp by changing recovery to an old official cwm and no problems since. Do not trust TWRP, you have been warned!.
Beamed in by telepathy.
MigoMujahid said:
OK, try flashing your Stock ROM with Odin first.
and see if everything goes right.
then you will have to re-flash the TWRP and try again.
Click to expand...
Click to collapse
I wiped and reflash the rom and Gapps , when I look at backup in TWRP , the EFS is 0mb , so I restored the EFS and rebooted the phone . It worked well . Thank you again ~!
shivadow said:
Make sure your imei still exists. If not then you need to fix the efs partition before you can proceed. Factory reset should always be done via the device software, NEVER TWRP!. TWRP has a habit of killing phones.
Beamed in by telepathy.
Click to expand...
Click to collapse
I was lucky that I made a backup of the EFS . After I restored the efs , the phone rebooted well . And my IMEI still exist . Thank you so much sir!
Pixelzack said:
I was lucky that I made a backup of the EFS . After I restored the efs , the phone rebooted well . And my IMEI still exist . Thank you so much sir!
Click to expand...
Click to collapse
Very lucky but that is why we stress that it MUST BE done, for times like these.
Beamed in by telepathy.
shivadow said:
Twrp has caused more mount issues than you've had hot dinners. The reason twrp is the 'most famous' recovery is because it's the only current recovery, Cwm is defunct. Cwm didn't cause mount issues, it only came about with twrp, on ALL devices.
I have also fixed the mount issue with twrp by changing recovery to an old official cwm and no problems since. Do not trust TWRP, you have been warned!.
Beamed in by telepathy.
Click to expand...
Click to collapse
I'll keep that in mind..
thanks :good:
Related
Hi everyone, i've got a huge problem with my i9300, i've got the foxhound/[email protected] rom since a week, and everything worked fine, i updated once without problems, however today i did the update with usual procedure, but now i've rebooted and i'm stuck on a bootloop after the apps optimizing part, where Android tries to optimize two apps, then open them, but then boot animation starts again over and over.
I tried going into recovery but it did not do anything, so i i tried flashing CWM via Odin, however now if i try starting in recovery only the samsung boot screen shows up and stays there forever.
Please help me
Pureemousseline said:
Hi everyone, i've got a huge problem with my i9300, i've got the foxhound/[email protected] rom since a week, and everything worked fine, i updated once without problems, however today i did the update with usual procedure, but now i've rebooted and i'm stuck on a bootloop after the apps optimizing part, where Android tries to optimize two apps, then open them, but then boot animation starts again over and over.
I tried going into recovery but it did not do anything, so i i tried flashing CWM via Odin, however now if i try starting in recovery only the samsung boot screen shows up and stays there forever.
Please help me
Click to expand...
Click to collapse
Go to CWM recovery and do a data/factory reset, wipe cache and dalvik cache, reboot and restore your apps.
gee2012 said:
Go to CWM recovery and do a data/factory reset, wipe cache and dalvik cache, reboot and restore your apps.
Click to expand...
Click to collapse
Well, problem is i cannot access recovery, but thanks for helping
Go in downloadmode and flash a stock rom with Odin. See item 2 and 3 in my signature
Sent from my GT-I9300 using xda premium
Is it possible to do so without wipe data ? I've got loads of things in there and my precedent Ti backup does not include them
Pureemousseline said:
Is it possible to do so without wipe data ? I've got loads of things in there and my precedent Ti backup does not include them
Click to expand...
Click to collapse
Well just installedit, still the same bootloop problem, just boot screen changes
Up, please help me, i'm so desperate right now
Flash Root via ODIN .
ROOT
http://forum.xda-developers.com/showthread.php?t=1684535
then recovery and Nandroid restore .
Fails then .
Wipe phone flash stock rom via Odin .
jje
JJEgan said:
Flash Root via ODIN .
ROOT
http://forum.xda-developers.com/showthread.php?t=1684535
then recovery and Nandroid restore .
Fails then .
Wipe phone flash stock rom via Odin .
jje
Click to expand...
Click to collapse
THANKS SO MUCH FOR THIS I MANAGED TO GO TO RECOVERY AND DO THE UPDATE AGAIN, NOW MY PHONE WORKS PERFECTLY WITHOUT LOSING DATA !!!!
Thank you really really much for this
Hey guys this is my first time messing with custom roms and my biggest fear has come true i think i bricked my phone, at least soft brick.
here is what happened:
I decided to flash supernexus 5 rom and everything went well, however my wifi wasnt working i tried to do a nandroid recover from a nandroid backup that i had from a while back made with the same version of cmw but it i got the message "no files found" even when i had put the folder with the recovery in my internal storage in the cmw folder. I decided to do a factory reset, wipe cache and dalvik cache but this didn't solve my problem with cmw not detecting the files then i went on and did this i went to mounts and storage as i read on a thread that mounting and unmounting everything solved the problem for a guy but this did not help either, then i went to mounts and storage and formated cache, data and system as shown in this youtube video http://www.youtube.com/watch?v=ZCoI62PG7jE&feature=g-hist after that i tried to rebot the phone but it wont get pass the inicial galaxy s3 i9300 screen, i tried whipe data cache and factory reset again but i still can't make it boot ,I can get to recovery however it still doesn't see the folder that i have there. If i connect the phone to the pc it says installing drivers for the device but it fails and i can't see the phone anymore as connected.
Please help me you have no idea how much i saved for buying this and i don't want to loose it.
this is the version of cmw that im using CF-SGS3-CWM-v5.5-v1.5
Krep3 said:
Hey guys this is my first time messing with custom roms and my biggest fear has come true i think i bricked my phone, at least soft brick.
here is what happened:
I decided to flash supernexus 5 rom and everything went well, however my wifi wasnt working i tried to do a nandroid recover from a nandroid backup that i had from a while back made with the same version of cmw but it i got the message "no files found" even when i had put the folder with the recovery in my internal storage in the cmw folder. I decided to do a factory reset, wipe cache and dalvik cache but this didn't solve my problem with cmw not detecting the files then i went on and did this i went to mounts and storage as i read on a thread that mounting and unmounting everything solved the problem for a guy but this did not help either, then i went to mounts and storage and formated cache, data and system as shown in this youtube video http://www.youtube.com/watch?v=ZCoI62PG7jE&feature=g-hist after that i tried to rebot the phone but it wont get pass the inicial galaxy s3 i9300 screen I can get to recovery however it still doesn't see the folder that i have there. If i connect the phone to the pc it says installing drivers for the device but it fails and i can't see the phone anymore as connected.
Please help me you have no idea how much i saved for buying this and i don't want to loose it.
Click to expand...
Click to collapse
You formatted system so you have no os to boot! Flash stock Rom with Odin.
Nb.......if you are using cm10/aosp you need to flash an ics Rom, let it boot, and enable wifi before then going on to flash the Rom as wifi won't work coming direct from jb Rom
slaphead20 said:
You formatted system so you have no os to boot! Flash stock Rom with Odin.
Nb.......if you are using cm10/aosp you need to flash an ics Rom, let it boot, and enable wifi before then going on to flash the Rom as wifi won't work coming direct from jb Rom
Click to expand...
Click to collapse
:laugh: THANKS SO MUCH you are the best, i was freaking out is almost 4am here and i couldn't sleep, you're a life saver.
Any idea why cmw doesn't see the restore files on the internal sd card
Krep3 said:
:laugh: THANKS SO MUCH you are the best, i was freaking out is almost 4am here and i couldn't sleep, you're a life saver.
Any idea why cmw doesn't see the restore files on the internal sd card
Click to expand...
Click to collapse
did you move the entire folder to your internal sd?
slaphead20 said:
did you move the entire folder to your internal sd?
Click to expand...
Click to collapse
yes everithing, and put it in the cmw folder
Krep3 said:
yes everithing, and put it in the cmw folder
Click to expand...
Click to collapse
can you remember if the backup was created with a different version of cwm to that which you are trying to restore it from?
slaphead20 said:
can you remember if the backup was created with a different version of cwm to that which you are trying to restore it from?
Click to expand...
Click to collapse
yes it was the same version only thing is that when i made it i have rooted with cf-root 6.4, but after flashing the stock elk4 leak i used cf auto root and then installed the recovery on its own but is the same version.
Krep3 said:
yes it was the same version only thing is that when i made it i have rooted with cf-root 6.4, but after flashing the stock elk4 leak i used cf auto root and then installed the recovery on its own but is the same version.
Click to expand...
Click to collapse
hmmmm......not sure what the problem is then, only thing I can suggest is flash the cf root again(not the auto one) and see if that sorts it, but I would move that backup back to its original location first
thanks again!! i will try flashing it again.
Krep3 said:
thanks again!! i will try flashing it again.
Click to expand...
Click to collapse
It's just a shot in the dark, but it's the direction I would head in if it happened to me......or I would just abandon the backup and start afresh !
Hi guys.
My phone is a international i9300
I've been searching for a problem like mine in the forum for three weeks now and I couldn't find a proper solution.
I just can't flash any rom via CWM anymore...
I can flash roms via ODIN, but when it comes to CWM, it gets stucked at Samsung logo after the install.
I tried:
Wipe cache / Dalvik / factory reset.
before the installation, after the installation, every combination possible.
Tried megawipe and no help.
Changed the kernel, Siyah, Googy, stock...
Changed versions of CWM, touch.
I have now the Phil'z 5.0.15.
I like very much the XXELK4 version from roalex with its MOD, for the call recording and full multiwindow support, but can't flash it anymore, nor any other custom or stock via CWM.
By now I can only have a full stock flashed via odin, or my Omega 46.1, wich I have a full backup.
Another solution could be find a .tar rooted and with the MODS flashable via Odin, but I really wanted to understand what's happening with my recovery.
Thank you all and congrats for the great work with the forum.
In cwm format..
Data
System
Cache
Then go to advanced and wipe dalvik cache
Then flash the rom.
Your cwm is upto date?
andrewwright said:
In cwm format..
Data
System
Cache
Then go to advanced and wipe dalvik cache
Then flash the rom.
Your cwm is upto date?
Click to expand...
Click to collapse
Sorry.
Forgot to include in the original post... I tried that too. Formatted everything
Got the 6.0.6.3
I also tried with the last Philz recovery.
And with previous versions of both too.
Have you tried to go bk to stock,root that firmware then install cwm then flash custom rom? Clean slate start.
Your problem may be a bad file download .
andrewwright said:
Have you tried to go bk to stock,root that firmware then install cwm then flash custom rom? Clean slate start.
Click to expand...
Click to collapse
Yes... didn't work...
JJEgan said:
Your problem may be a bad file download .
Click to expand...
Click to collapse
I'll try to download again, although it's not likely that several files are bad. I tried with so many different roms...
I bought another micro sd of 64gb. Maybe the one I'm using is ruining the files...
There can't be a so huge bug in philz recovery
Try install from internal sdcard, a simple 'Factory Reset before New Rom' no need to mega wipe anything.
Striatum_bdr said:
There can't be a so huge bug in philz recovery
Try install from internal sdcard, a simple 'Factory Reset before New Rom' no need to mega wipe anything.
Click to expand...
Click to collapse
Of course. And I tried with different versions of Philz' and also CWM. It can't be a bug in recovery.
Re-downloaded the revolution 29.0 and the Roalex XXELK4 rooted, copyed directly to internal and flashed... Same problem. Stuck at Samsung logo in boot. I'm begining to think my phone is screwed up. But this is so strange. I can restore my backup with no problems, and also can flash with Odin.
Is there a way to flash a .ZIP ROM in Odin?
Does not make any sense .
What model phone do you have ???
What model firmware are you flashing .
What about basic stock custom roms flashed via CWM ??
Have you booted to Philz recovery mounts and storage format sd card cache system and data then flash rom ??
Agree it is strange Deviating a little from your problem but have you tried flashing anything with TWRP recovery see if the problem persists with that.
JJEgan said:
Does not make any sense .
What model phone do you have ???
What model firmware are you flashing .
What about basic stock custom roms flashed via CWM ??
Have you booted to Philz recovery mounts and storage format sd card cache system and data then flash rom ??
Click to expand...
Click to collapse
I know it doesn't. That's why I'm going crazy.
I uploaded the screenshots with my system specs.
The model is correct, international i9300. Tried to download from the site and also directly from rommanager.
The firmwares I'm trying to flash are stock, but rooted by Roalex. I couldn't find a pure stock .zip for testing with CWM. The firmware I'm using is UBEMH5 from sammobile, wich I flashed via Odin.
Yes... Tried and formatted everything, several times, mounted, unmounted, every possible order...
Almost giving up. :crying:
tallman43 said:
Agree it is strange Deviating a little from your problem but have you tried flashing anything with TWRP recovery see if the problem persists with that.
Click to expand...
Click to collapse
I never used TWRP. Can I flash the same ROM file .zip with it or it requires it's own rom file type?
I'm gonna be out of the country for two days. When I come back I'll give it a try.
Thank you all so far.
ivansaab said:
I never used TWRP. Can I flash the same ROM file .zip with it or it requires it's own rom file type?
I'm gonna be out of the country for two days. When I come back I'll give it a try.
Thank you all so far.
Click to expand...
Click to collapse
It's been a while since i used it last time was when I had a S2 and I used it all the time:good: You can flash any rom with it that cwm can flash (as far as I know) but it had a little trouble restoring backups made with cwm but I think that got fixed.But you can make backups and loads of other things with it I recommend people to try it at least once This won't fix your cwm problem but would be interesting to see if it works
If twrp doesn't work on stock Flash googy Max dualboot kernel and keep stock as primary rom and custom as second rom. Then you have best of both world's :thumbup: also take the pic down with your emei showing :banghead: never ever show this!
What i would do in this situation is .
In recovery format cache system sd card preload .
Flash stock rom via Odin.
Check phone works ok .
Then root / flash philz recovery .
Put custom rom on sd card boot to recovery factory reset .
Then install custom rom watching setup to spot a failure point .
Wait for rom to load 10 mins fails then remove batter replace and factory reset .
Problem solved
Hi folks.
Think I figured out what's going on.
Via TWRP it says the files were corrupted, although the file sizes were identical.
I MD5 checked the files in my computer and they're ok, but when checked already inside my phone or SD they're not.
Instead of copying the files via USB cable I removed the SD card and inserted directly in my laptop slot and copyed the files. MD5 checked and they're ok...
After I tryed again copy via USB and the files were corrupted again.
I think my desktop USB or maybe the Samsung drivers are doing that.
Well, problem solved. I hope this helps other people in future problems.
Thank you all for your help and support. Keep on with the great work.
Mark solved then for other users .
Hi all,
I'm having a very strange issue with my i9300 today. I left it charging switched off overnight, and when I tried to switch it back on, it hangs on the Samsung bootscreen. I thought it was odd, but solvable. I went into recovery to try and reflash with the backup I have stored on my sdcard, however when it tried to wipe /Data, it rebooted and hung on the bootscreen again.
I initally had CWM 6.0.4.4 recovery installed, however I have tried PhilZ and TWRP to no avail. All three reboot on flashing /Data.
Anyone have any ideas?
For information, I was running 4.4 KitKat Unofficial. If you need any more information (preferably what can be pulled in Recovery/Download), I'll be happy to post it.
I need my phone running back normally ASAP!
Hi just a little confused..When you say all three reboot on flashing data do you mean data from your backup? If so your backup might be corrupt have you tried doing a clean flash with another rom or tried returning to stock?..Also if you don't want to lose data stored on your backup you can try flashing the original rom that you where on when you made the backup then using philz recovery in advanced settings/ restore you can then just restore data from your backup not the whole rom...And try formatting data system and cache but don't forget this will leave you without a rom so have one ready to install on your sd card....Hope all that makes sense
tallman43 said:
Hi just a little confused..When you say all three reboot on flashing data do you mean data from your backup? If so your backup might be corrupt have you tried doing a clean flash with another rom or tried returning to stock?..Also if you don't want to lose data stored on your backup you can try flashing the original rom that you where on when you made the backup then using philz recovery in advanced settings/ restore you can then just restore data from your backup not the whole rom...And try formatting data system and cache but don't forget this will leave you without a rom so have one ready to install on your sd card....Hope all that makes sense
Click to expand...
Click to collapse
Sorry, I should have been clearer. I was trying to Format the /Data partition in recovery in preparation to restore the backup, and every time a Recovery attempts to Format the partition the phone reboots.
I understand now thanks..Mmm..If you can't format data I would probably just flash stock again with Odin get your phone stable, then try to restore your backup...
tallman43 said:
I understand now thanks..Mmm..If you can't format data I would probably just flash stock again with Odin get your phone stable, then try to restore your backup...
Click to expand...
Click to collapse
Bleh. Returning to stock didn't work. It went past the bootscreen to the green android loading bar screen, went part way then rebooted, and stuck on boot again. >.>
Stickied faqs and guides .
But first what does Product Code say in download mode .
Originally Posted by tallman43<br />
I understand now thanks..Mmm..If you can't format data I would probably just flash stock again with Odin get your phone stable, then try to restore your backup...
Click to expand...
Click to collapse
<br />
<br />
Bleh. Returning to stock didn't work. It went past the bootscreen to the green android loading bar screen, went part way then rebooted, and stuck on boot again. >.>
Click to expand...
Click to collapse
You now have to go to recovery and wipe data/factory reset, wipe cache and reboot. It'll most probably work.
Sent from my silky smooth Samsung GALAXY S3
Rayan28 said:
You now have to go to recovery and wipe data/factory reset, wipe cache and reboot. It'll most probably work.
Sent from my silky smooth Samsung GALAXY S3
Click to expand...
Click to collapse
Ah, that would make sense. I'll give that a try now.
Nope. It's still hanging on the Samsung Bootscreen. Sigh.
I think I'm resigned to the fact I'm going to have to replace this. Most likely with a Nexus 5. Oh well. That sets back some of my luxury spending for the month again.
TermyJW said:
I think I'm resigned to the fact I'm going to have to replace this. Most likely with a Nexus 5. Oh well. That sets back some of my luxury spending for the month again.
Click to expand...
Click to collapse
Are you even flashing the correct ROM for your device with the correct model number? If yes, redownload the ROM. It could be a bad download. This time try the latest 4.3 Jelly Bean.
Ok , Im running CM 13 i9300 and it worked so well except the camera. I always got the error "Can't connect to camera" . So I was trying to fix that problem and I found couple of solution . The solution need an app that requires SuperSU permission . And It was kinda weird because there's no "permission asking" popup from SuperSU. So I open SuperSU and it told me to update SuperSU binary file. So I tried to update it and it failed. So I tried to update it manually but I found other thing which is to flash the latest version of SuperSU direct from chainfire website. I deleted the old SuperSU (The one that needs to be updated) and I flashed the new SuperSU zip and wipe dalvik cache through my TWRP Recovery and then I reboot my phone . And got stuck at the Cyanogenmod Logo . So what should I do to get my phone back to normal ? I mean back to CM13 and everything I have before. PLS HELP
Note : actually , after I flashed CM 13 . I dont have the SuperSU in my apps . So I manually downloaded it from the playstore . It's weird because it should automatically be there .
Isn't root access found under developer settings?
audit13 said:
Isn't root access found under developer settings?
Click to expand...
Click to collapse
I seriously dunno about the root access at the developer settings . Now my phone is soft bricked and I'm gonna lose all of my data. Any clue on how to reflash the CM13 without deleting my stuff?(factory reset)
p/s : Yes , It's in the Developer settings
Boot into TWRP and reflash the same version of CM that was on the phone before it soft-bricked.
audit13 said:
Boot into TWRP and reflash the same version of CM that was on the phone before it soft-bricked.
Click to expand...
Click to collapse
Should I clear data , wipe cache and dalvik , factory reset all that or just go to TWRP and just flash
You could just flash over the existing ROM without wiping. If it doesn't boot, wipe cache. If it still doesn't boot, wipe data and cache.
audit13 said:
You could just flash over the existing ROM without wiping. If it doesn't boot, wipe cache. If it still doesn't boot, wipe data and cache.
Click to expand...
Click to collapse
Ok sir , new problem .. So I uses CM13 Nightlies , And I dont remember which version. Can I use latest version of CM13 Nightlies?
Yes, try the latest nightly.
audit13 said:
Yes, try the latest nightly.
Click to expand...
Click to collapse
Man It worked , seriously thank you man :good: :good: :good:
Glad to hear you solved the problem. We're all here to help and learn from each other.