Related
I want to flash CM9 on my Sprint Nexus and reading through the threads I cant' get the info I need.
Do i need to update any radios to do anything else before flashing this? I just rooted yesterday using the dev tool and I'm itching to flash. I came over from HTC EVO and SGS2 and the nexus is all new to me, but so far loving it. Thanks so much for the help! below is my build information:
Baseband Version:
L700.05.V.FD02/L700.FD02
Build Number:
IMM76D.L700FD02
Make sure you're running a custom recovery such as TWRP or Clockwork and you should be fine.
ROM and radios are completely separate.
Smokeey said:
Make sure you're running a custom recovery such as TWRP or Clockwork and you should be fine.
ROM and radios are completely separate.
Click to expand...
Click to collapse
Ok so I can flash without updating the Radios? I'm currently using CWM
cyaiphone said:
Ok so I can flash without updating the Radios? I'm currently using CWM
Click to expand...
Click to collapse
Yes.
You already have the most updated radios.
Sent from a phone...
Thanks guys!
Dammit sorry one last question.
My My EVO had an SD Card. So if i place the ROM on my Nexus and I wipe data in recovery I'm I deleting my ROM? The norm was to Flash Cache, Davlik Cache, Data, and Factory restore on my EVO. Not sure how that works now that this phone does not have an SD card. Do we not wipe data when flashing ROMs on the nexus?
when you wipe the 'sdcard' partition remains untouched so dont worry
Thank you! Here I go!! This file im downloading from http://jenkinsmanifest.clockworkmod.com/device/toroplus shows it's only 137 mb. Are ROMS on the Nexus usually this small or is there something wrong with my Download?
That's AOSP ICS for ya. Gingerbread AOSP was even smaller.
Sent from my Galaxy Nexus using XDA
Hi guys I searched the forums but can't seem to figure this one out. I can flash and boot all ICS Roms completely fine. When I try ANY Jellybean ROM AOKP, CM whatever I get stuck on a boot screen loop. I use these steps:
Flash darkside super wipe
Flash ROM
Flash gapps
Flash darkside super wipe cache
Reboot
Now I've tried cwm 5.x.x and 6.x.x and twrp. Any suggestions?
MARINERMOOSE241 said:
Hi guys I searched the forums but can't seem to figure this one out. I can flash and boot all ICS Roms completely fine. When I try ANY Jellybean ROM AOKP, CM whatever I get stuck on a boot screen loop. I use these steps:
Flash darkside super wipe
Flash ROM
Flash gapps
Flash darkside super wipe cache
Reboot
Now I've tried cwm 5.x.x and 6.x.x and twrp. Any suggestions?
Click to expand...
Click to collapse
Download the file again. Sounds like a bad flash.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Thanks elesbb but this bootloop happens with ANY JB from I try to.flash on my hercules. So I don't think its bad downloads I wonder if I posted a log at during boot if someone could help.
MARINERMOOSE241 said:
Thanks elesbb but this bootloop happens with ANY JB from I try to.flash on my hercules. So I don't think its bad downloads I wonder if I posted a log at during boot if someone could help.
Click to expand...
Click to collapse
That's why I recommended downloading again. Sometimes packets are lost in cyberspace. I don't see how your device is the only one doing this. Gotta be something on your end. (Not trying to point fingers. Just saying it can be a million and 2 things )
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Ok, I now downloaded 4 different roms ALL Jellybean and ALL get frozen during the bootscreen and bootloop. ADB just sits at waiting for device when trying to logcat. I've reflashed to stock gingerbread just fine, reflashed to ICS AOKP just fine no loops. But going to JB after just keep causing a bootloop, its driving me crazy.
MARINERMOOSE241 said:
Ok, I now downloaded 4 different roms ALL Jellybean and ALL get frozen during the bootscreen and bootloop. ADB just sits at waiting for device when trying to logcat. I've reflashed to stock gingerbread just fine, reflashed to ICS AOKP just fine no loops. But going to JB after just keep causing a bootloop, its driving me crazy.
Click to expand...
Click to collapse
What cwm are u using? I couldn't flash any Jb roms with cwm 6
Sent from my SAMSUNG-SGH-T989 using xda premium
Rememdium said:
What cwm are u using? I couldn't flash any Jb roms with cwm 6
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Were you getting freeze bootloops?
I have tried cwm 5.x nd 6 which I'm on now. Also twrp gave me the same loop. I've even gone as far.as.formatting sdcard and eemc with no luck.
MARINERMOOSE241 said:
Were you getting freeze bootloops?
I have tried cwm 5.x nd 6 which I'm on now. Also twrp gave me the same loop. I've even gone as far.as.formatting sdcard and eemc with no luck.
Click to expand...
Click to collapse
Try switching to TWRP.
Then re-download the JB rom you want to use, put it on the root of your internal SD, make sure the MD5 matches and then try flashing again. I think most of these JB boot problems are coming from CWM recoveries.
Digital1325 said:
Try switching to TWRP.
Then re-download the JB rom you want to use, put it on the root of your internal SD, make sure the MD5 matches and then try flashing again. I think most of these JB boot problems are coming from CWM recoveries.
Click to expand...
Click to collapse
No they aren't. Teamchopsticks recommends cwm 6.0.1.1 as the optimal recovery to use.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
elesbb said:
Teamchopsticks recommends cwm 6.0.1.1 as the optimal recovery to use.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Where did you read that? And does 6.0.1.1 still have a broken cache wipe?
Someone had a similar problem in the dev thread and switching recoveries seemed to fix it. So worth trying.
Sent from a BAMF Jedi ROM from the Lightside
Digital1325 said:
Where did you read that? And does 6.0.1.1 still have a broken cache wipe?
Someone had a similar problem in the dev thread and switching recoveries seemed to fix it. So worth trying.
Sent from a BAMF Jedi ROM from the Lightside
Click to expand...
Click to collapse
I read it on their website but i came across it in binarybishops nightly thread. And no the cache wipe is fixed. I use the touch version, tried TWRP and CWM 5 hell i tried them all! They all produced the exact same results for me as far as performance goes. But ive never had any issues with 6.0.1.1 i love it to death
Ok guys this is very puzzling. I have been flashing roms for years and have never had a loop like this.
So I flashed TWRP again verified the md5 has was correct for both AOKP JB nightly and gapps. Flashed following the correct steps posted in the thread by Whitehawkx and I still get a bootloop freeze on the AOKP unicorn. So I tried CM 10 nightly... same freeze/loop. I downloaded AOKP ICS, no loop at all boots fine.
I've tried cwm 5, 6, and twrp all with the exact same results. I have formated SD external and internal EMMC... nothing has worked.... All I want is some Jelly bean goodness.... I flashed AOKP on my nexus 7 just fine. Like I said I am really stumped on this one as to why ICS roms would flash perfectly fine and using the same steps JB roms bootloop.
MARINERMOOSE241 said:
Ok guys this is very puzzling. I have been flashing roms for years and have never had a loop like this.
So I flashed TWRP again verified the md5 has was correct for both AOKP JB nightly and gapps. Flashed following the correct steps posted in the thread by Whitehawkx and I still get a bootloop freeze on the AOKP unicorn. So I tried CM 10 nightly... same freeze/loop. I downloaded AOKP ICS, no loop at all boots fine.
I've tried cwm 5, 6, and twrp all with the exact same results. I have formated SD external and internal EMMC... nothing has worked.... All I want is some Jelly bean goodness.... I flashed AOKP on my nexus 7 just fine. Like I said I am really stumped on this one as to why ICS roms would flash perfectly fine and using the same steps JB roms bootloop.
Click to expand...
Click to collapse
It's something wrong with your flash file. Use an actual adapter to transfer the file. And download it again. Then if you still get the loop plug your phone into your computer and boot it up then run adb logcat.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
elesbb said:
It's something wrong with your flash file. Use an actual adapter to transfer the file. And download it again. Then if you still get the loop plug your phone into your computer and boot it up then run adb logcat.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
When you say flash file do you mean the ROM? If so I've tried downloading it on my Mac and transferred it via USB mode still no dice. Also I.tried to.log at during the bootloop but adb never sees the device.
MARINERMOOSE241 said:
When you say flash file do you mean the ROM? If so I've tried downloading it on my Mac and transferred it via USB mode still no dice. Also I.tried to.log at during the bootloop but adb never sees the device.
Click to expand...
Click to collapse
Yes im saying the zip. Something isnt getting placed where it belongs or something is corrupt. And DONT use the USB mode, get an actual Mirco SD to SD adapter and a SD to USB adapter and do it that way.
elesbb said:
Yes im saying the zip. Something isnt getting placed where it belongs or something is corrupt. And DONT use the USB mode, get an actual Mirco SD to SD adapter and a SD to USB adapter and do it that way.
Click to expand...
Click to collapse
I have an adapter so I can try that right now. However, if the md5 hash is correct wouldn't that mean the zip downloaded correctly? And it still doesn't answer why every JB from bootloops while ICS does not.
MARINERMOOSE241 said:
I have an adapter so I can try that right now. However, if the md5 hash is correct wouldn't that mean the zip downloaded correctly? And it still doesn't answer why every JB from bootloops while ICS does not.
Click to expand...
Click to collapse
Yes that is usually the norm. But it is millions and millions and millions of bits of data we are talking about here... all it takes is for one of those bits to either not be there or be in the wrong place to screw it up. And yes that is extremely strange, but seeing as you are the only one experiencing this, i am sure its not the ROMs and its something you are doing or not doing. Im not trying to be rude or imply that you are dumb. its just extremely hard to pin point something weird like this when i dont have the device in my hands. See where im getting here?
elesbb said:
Yes that is usually the norm. But it is millions and millions and millions of bits of data we are talking about here... all it takes is for one of those bits to either not be there or be in the wrong place to screw it up. And yes that is extremely strange, but seeing as you are the only one experiencing this, i am sure its not the ROMs and its something you are doing or not doing. Im not trying to be rude or imply that you are dumb. its just extremely hard to pin point something weird like this when i dont have the device in my hands. See where im getting here?
Click to expand...
Click to collapse
I totally agree I don't believe its the roms themselves as they seem to work for most people. I've just never ran across this before.
MARINERMOOSE241 said:
I totally agree I don't believe its the roms themselves as they seem to work for most people. I've just never ran across this before.
Click to expand...
Click to collapse
I have on my HD2. But a complete format of the memory card using HP USB disk tools fixed it. Have you tried that yet?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
elesbb said:
I have on my HD2. But a complete format of the memory card using HP USB disk tools fixed it. Have you tried that yet?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Formated the SD card ... used the external adapter to copy the flash to the SD same bootloop I also copied the file directly to internal storage removed the sd card and flashed same result... looks like no Jelly bean for me... so freaking odd as I can flash ICS any rom all day long just fine.
Hey guys, I'm really new to rooting, flashing roms, and Android in general (I've used iOS since 2007 until a month ago... please have mercy on my soul). I have an AT&T GN2 that I would like to remove the bloatware from, hence why I began investigating rooting, but it's snowballed into my desire to try out some of the amazing ROMs that the developers here have produced. Since the Note 2 uses the Exynos 4, I rooted using the ExynosAbuse exploit and downloaded Titanium Backup to freeze the AT&T apps. So far, so good.
However, I am wanting to get into how to flash custom ROMs, like CyanogenMod, so I downloaded the CWM RomManager and flashed the CWM Recovery. I downloaded the CyanogenMod 10.1 release for the i317 model (here: http://forum.xda-developers.com/showthread.php?t=2024495) and the latest gApps package (for 4.2.1), and flashed both from CWM RomManager. When it rebooted, it showed the CyanogenMod boot screen, but it appears to be stuck there. I'm not sure what to do at this point, and am hoping I didn't brick my phone. Is there anything I can do at this point?
Use the three button combo to get into recovery, should be volume up, home, and power, and then wipe data or install a stock rooted ROM. That should help get you to a bootable stage.
Sent from my GT-N7105 using xda premium
Have you changed kernel???
Sent from my MT11i using xda app-developers app
id10terrordfw said:
Use the three button combo to get into recovery, should be volume up, home, and power, and then wipe data or install a stock rooted ROM. That should help get you to a bootable stage.
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
When I booted into recovery, I got the CWM recovery (which is a good thing, I suppose). I wiped the cache, and then installed the CM 10.1 zip and gApps zip. However, I think I still need to wipe data/factory reset, right?
So, at this point, I've:
1. Rooted the device using Chainfire's ExynosAbuse apk (super easy).
2. Installed RootChecker (success) and TI backup (froze bloatware apps).
3. Downloaded CWM RomManager.
4. Flashed CWM Recovery.
5. Downloaded CM 10.1 port for i317 (the AT&T GN2 model) and the 4.2.1 gApps zips.
6. Chose to install ROM from SD card in RomManager, added both CM 10.1 and gApps, and only selected install (did not wipe cache or user data at this point).
7. Received blue CyanogenMod boot screen... excited... but it remains on the boot screen. Sad face.
8. Removed battery to power the device off, placed battery back in, and then booted into recovery mode (CWM recovery).
9. Installed the CM 10.1 zip and gApps zip from SD, then wiped cache.
10. ???
Wipe data factory reset. Wipe cache/dalvik. Flash cm, flash gapps. Reboot
And dont use rom manager. Do it in recovery
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Peleus16 said:
Have you changed kernel???
Sent from my MT11i using xda app-developers app
Click to expand...
Click to collapse
This is a great point, at no point op has mentioned kernel.
Sent from my SAMSUNG-SGH-I317 using xda premium
cdshepherd said:
Wipe data factory reset. Wipe cache/dalvik. Flash cm, flash gapps. Reboot
And dont use rom manager. Do it in recovery
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
Okay, booted into CMW recovery and performed all in that order. It booted! Hurrah. Only problem: the AOSP keyboard crashes constantly, making text input not possible. Sigh...
NowhereOutThere said:
Okay, booted into CMW recovery and performed all in that order. It booted! Hurrah. Only problem: the AOSP keyboard crashes constantly, making text input not possible. Sigh...
Click to expand...
Click to collapse
Boot back into recovery and fix permissions. That may help
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
cdshepherd said:
Boot back into recovery and fix permissions. That may help
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
Okay, I booted into recovery mode and fixed permissions... the keyboard still crashes, which means I can't type anything. Do I have to do anything with the kernel? I didn't wipe the dalvik cache, should I have done that?
EDIT: wiped dalvik cache, didn't do anything... apparently, this was a fine release so I'm not sure what could be causing the keyboard issues.
NowhereOutThere said:
Okay, I booted into recovery mode and fixed permissions... the keyboard still crashes, which means I can't type anything. Do I have to do anything with the kernel? I didn't wipe the dalvik cache, should I have done that?
EDIT: wiped dalvik cache, didn't do anything... apparently, this was a fine release so I'm not sure what could be causing the keyboard issues.
Click to expand...
Click to collapse
Im not exactly sure either. I have yet to flash cm. Read the cm thread?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
cdshepherd said:
Im not exactly sure either. I have yet to flash cm. Read the cm thread?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
So what ROM are you using? I just picked cyanogenmod because I've heard of it before, but I would like something that works. Is there a way to add another ROM onto the phone's storage, as I don't have an SD card... And since I can't type anything, it's not like I can download it from the phone's browser?
NowhereOutThere said:
So what ROM are you using? I just picked cyanogenmod because I've heard of it before, but I would like something that works. Is there a way to add another ROM onto the phone's storage, as I don't have an SD card... And since I can't type anything, it's not like I can download it from the phone's browser?
Click to expand...
Click to collapse
Plug it into your computer and see if you can mount your internal sd. If you can download a new rom to your computer and transfer it to sd. Did you make a backup before flashing?
Im just running stock rooted for now.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Well, I'm downloading CleanROM right now. I also downloaded another cm 10.1 file just in case, perhaps it's because I downloaded it on the mobile Chrome browser that I'm having problems? I also downloaded a kernel from the thread to help with performance. However, if I can't get these on the phone, it doesn't matter. Since I'm on a Mac, I have to use Android File Transfer, and it isn't registering my phone, unfortunately. I may have to go out and buy a cheap SD card and throw the files on there. It may not hurt to have one around, anyways.
Text yourself the download link to CleanRom. :thumbup:
And chrome shouldnt have made a difference. I take it you didnt make a nandroid backup before you flashed cm?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
cdshepherd said:
Text yourself the download link to CleanRom. :thumbup:
And chrome shouldnt have made a difference. I take it you didnt make a nandroid backup before you flashed cm?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
No... I thought that a backup of the original ROM was made when flashing CWM recovery, but I am a noob and that did not happen. Unfortunately, the browser doesn't even work! So I cannot text myself the link for the download. I should be able to flash a zip file from a micro sdhc, right?
Flash the right GAPPS, the crashing keyboard is a symptom of incorrect GAPPS. The December one is for 4.2.1 only, which is what CM10.1 is based on. Make sure you flash the right GAPPS with the right CM version.
Sent from my GT-N7105 using xda premium
The CM you linked in the OP is CM10 not 10.1, so you flashed the wrong GAPPs
ManelScout4Life said:
The CM you linked in the OP is CM10 not 10.1, so you flashed the wrong GAPPs
Click to expand...
Click to collapse
Oh... crap. Is there any way I can get the correct gApps on my phone? Ugh... I'm going to have access to a Windows machine today, so I can download the correct GAPPS and put them on my flash drive. I can still put it in USB debugging mode, but will the PC recognize it? Android File Transfer software for Mac does not recognize the phone any more, so I'm a bit limited in what I can do. Unless, like I said before, I can just pop in an SD card with the correct file.
Just grab goo manager from the market and dl the correct gapps to your phone. Either that or use your phones browser. No need for a pc. Boot in recovery, wipe cache and dalvik and flash correct gapps. Should be gtg.
Edit: just saw your browser isn't working. Goo manager's your best bet. Could always try another browser from the market as well. Good luck.
NowhereOutThere said:
Oh... crap. Is there any way I can get the correct gApps on my phone? Ugh... I'm going to have access to a Windows machine today, so I can download the correct GAPPS and put them on my flash drive. I can still put it in USB debugging mode, but will the PC recognize it? Android File Transfer software for Mac does not recognize the phone any more, so I'm a bit limited in what I can do. Unless, like I said before, I can just pop in an SD card with the correct file.
Click to expand...
Click to collapse
While in recovery plug usb into computer (make sure drivers are installed) in recovery menu navigate to mount usb storage. See if that works
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Hello guys,
It's my first question to the forum. I hope you can give me a clue resolve this problem.
I bought a Note 2 SGH i317 some days ago.
It was my first root but with your trheads everything was ok (for some days).
I tried JediX, Custom Rom 4.2.5 and some other.
But after tried some custom roms, I noted that when I flash any rom the phone stucks on Samsung Galaxy Note II screen and I have to pull out the battery to turn off the phone.
I tried with many others roms and all did the same.
Later I realized that the flash process was very fast compared to the first ones, so I guess the flash proccess fails in some instance.
I returned to stock rom and root it again with same results.
I tried with CVM and TWRP.
I can restore some nandroid backups to get the phone working, but can't flash any rom now!
Do you have any suggestion?
Thanks in advance.
maztermdq said:
Hello guys,
It's my first question to the forum. I hope you can give me a clue resolve this problem.
I bought a Note 2 SGH i317 some days ago.
It was my first root but with your trheads everything was ok (for some days).
I tried JediX, Custom Rom 4.2.5 and some other.
But after tried some custom roms, I noted that when I flash any rom the phone stucks on Samsung Galaxy Note II screen and I have to pull out the battery to turn off the phone.
I tried with many others roms and all did the same.
Later I realized that the flash process was very fast compared to the first ones, so I guess the flash proccess fails in some instance.
I returned to stock rom and root it again with same results.
I tried with CVM and TWRP.
I can restore some nandroid backups to get the phone working, but can't flash any rom now!
Do you have any suggestion?
Thanks in advance.
Click to expand...
Click to collapse
Did you wipe the data/wipe the cache partition and clear the dalvik cache? I would start with those things.
CharliexCharger said:
Did you wipe the data/wipe the cache partition and clear the dalvik cache? I would start with those things.
Click to expand...
Click to collapse
Hi.
Yes. I did every step.
Sometimes I wipe both before and after flashing rom.
In some cases I format /system also.
I'm thinking in format some special partition/folder, but I don't know where to start or if it will works...
maztermdq said:
Hi.
Yes. I did every step.
Sometimes I wipe both before and after flashing rom.
In some cases I format /system also.
I'm thinking in format some special partition/folder, but I don't know where to start or if it will works...
Click to expand...
Click to collapse
That is weird. Did you root using Odin?
CharliexCharger said:
That is weird. Did you root using Odin?
Click to expand...
Click to collapse
I rooted it via Odin using Galaxy Note 2 Toolkit form here:
http://forum.xda-developers.com/showthread.php?t=1923956
with my specific tar file.
maztermdq said:
I rooted it via Odin using Galaxy Note 2 Toolkit form here:
http://forum.xda-developers.com/showthread.php?t=1923956
with my specific tar file.
Click to expand...
Click to collapse
Not sure what went wrong. I would search through the forums for anything similar to the issue that you're having. If all else fails I'd flash the stock firmware via Odin. Good luck!
CharliexCharger said:
Not sure what went wrong. I would search through the forums for anything similar to the issue that you're having. If all else fails I'd flash the stock firmware via Odin. Good luck!
Click to expand...
Click to collapse
Charlie,
To flash stock firmware is different form flash stock rom?
Must I search for a trhead to flash it?
Thank you!
maztermdq said:
Charlie,
To flash stock firmware is different form flash stock rom?
Must I search for a trhead to flash it?
Thank you!
Click to expand...
Click to collapse
Yes it is. You can find the stock here.
http://galaxynote2root.com/galaxy-note-2-stock-firmwares/
If flashing stock rom doesn't help, your internal memory might be corrupted, and might need to format it through recovery.
It's not a sure thing but it's another option to troubleshoot your problem. If you're gonna try that, make sure to backup all your stuff
Sent from my SGH-I317M using xda premium
AlonB. said:
If flashing stock rom doesn't help, your internal memory might be corrupted, and might need to format it through recovery.
It's not a sure thing but it's another option to troubleshoot your problem. If you're gonna try that, make sure to backup all your stuff
Sent from my SGH-I317M using xda premium
Click to expand...
Click to collapse
I think that something like that is the real problem.
Must I format /storage/sdcard0 or format everything except my external card?
By the way, how can the internal memory becames corrupt?
maztermdq said:
I think that something like that is the real problem.
Must I format /storage/sdcard0 or format everything except my external card?
By the way, how can the internal memory becames corrupt?
Click to expand...
Click to collapse
It's hard to say what made it corrupt (if at all, remember, this is only an assumption). Could've been an app that caused it, could've been flashing a custom rom, and something went wrong during the flashing process.
If you're using twrp (which i highly suggest you do), in the 'wipe' menu there's an option to wipe internal sd. DON'T FORGET! before you do this make a nandroid backup and keep that backup on your external sd, or on your computer. Also, backup all your stuff, like pictures, music, etc.
Sent from my SGH-I317M using xda premium
How long do you usually wait at the samsung logo?
AlonB. said:
It's hard to say what made it corrupt (if at all, remember, this is only an assumption). Could've been an app that caused it, could've been flashing a custom rom, and something went wrong during the flashing process.
If you're using twrp (which i highly suggest you do), in the 'wipe' menu there's an option to wipe internal sd. DON'T FORGET! before you do this make a nandroid backup and keep that backup on your external sd, or on your computer. Also, backup all your stuff, like pictures, music, etc.
Sent from my SGH-I317M using xda premium
Click to expand...
Click to collapse
Thank you AlonB.
I'll try.
I'm using CWM right now, because I thought that TWRP could be part of the problem.
I have two backups with CWM and two with TWRP, An one complete with Titanium also!
KDurantula said:
How long do you usually wait at the samsung logo?
Click to expand...
Click to collapse
Hi KDurantula,
At the begining abuout 20-30 minutes.
One time I waited for more than an hour.
Lately, no more than 15 min.
maztermdq said:
Thank you AlonB.
I'll try.
I'm using CWM right now, because I thought that TWRP could be part of the problem.
I have two backups with CWM and two with TWRP, An one complete with Titanium also!
Click to expand...
Click to collapse
AloneB,
I tried with fomat internal SD card, but without results.
After formated /sdcard, I formated /system, wiped data/factory settings, wiped cache and wiped dalvik.
I was ready to flash CleanROM 4.5, but stuck after teh second "Next".
So I went for the nandroid but... MD5 is worng!!
I'll try to back to stock again and see..
maztermdq said:
AloneB,
I tried with fomat internal SD card, but without results.
After formated /sdcard, I formated /system, wiped data/factory settings, wiped cache and wiped dalvik.
I was ready to flash CleanROM 4.5, but stuck after teh second "Next".
So I went for the nandroid but... MD5 is worng!!
I'll try to back to stock again and see..
Click to expand...
Click to collapse
Hi AloneB,
Before I return to stock rom, i tried with another rom; JediXPX... and it works!!
I must to try with some other, but at least this works when before the format it doesn't work.
Thank you!
PD: Excuse me my ingnorance, but how to thanks to you? And how can I close the thread?
maztermdq said:
Hi AloneB,
Before I return to stock rom, i tried with another rom; JediXPX... and it works!!
I must to try with some other, but at least this works when before the format it doesn't work.
Thank you!
PD: Excuse me my ingnorance, but how to thanks to you? And how can I close the thread?
Click to expand...
Click to collapse
The only thanks you could give is just hitting the thanks button on my answers to you. But you don't really have to, it's entirely up to you. If you think my responses are helpful to you, then by all means ... In order to close a thread you could ask a moderator to do so. I'm not sure you're obligated to do so.
Btw, if cwm gives you an md5 error, could be most likely because you changed the name cwm has originally assigned to that backup. To solve this, just change it to what it was. If you didn't change the backup name, you could try going into advanced menu in cwm and toggle signature check to disable
Sent from my SGH-I317M using xda premium
AlonB. said:
The only thanks you could give is just hitting the thanks button on my answers to you. But you don't really have to, it's entirely up to you. If you think my responses are helpful to you, then by all means ... In order to close a thread you could ask a moderator to do so. I'm not sure you're obligated to do so.
Btw, if cwm gives you an md5 error, could be most likely because you changed the name cwm has originally assigned to that backup. To solve this, just change it to what it was. If you didn't change the backup name, you could try going into advanced menu in cwm and toggle signature check to disable
Sent from my SGH-I317M using xda premium
Click to expand...
Click to collapse
I did it imediatly!
Thank you for your help.
Regards.
Any time I try to flash a rom or anything I keep getting this message: E:/error opening '/data/lost+found'
I've tried flashing different roms but it hasn't helped.
I'm having this weird problem where when I flash a new rom about 20 random apps are transferred over to the new rom. (like random games and apps)
Also every time I uninstall any app I get "cannot read data/xposed/modules.whitelist"
The app still uninstalls but this just concerns me.
Could anyone help me out? I just want to do a fresh install of liquid smooth.
Rayz321 said:
Any time I try to flash a rom or anything I keep getting this message: E:/error opening '/data/lost+found'
I've tried flashing different roms but it hasn't helped.
I'm having this weird problem where when I flash a new rom about 20 random apps are transferred over to the new rom. (like random games and apps)
Also every time I uninstall any app I get "cannot read data/xposed/modules.whitelist"
The app still uninstalls but this just concerns me.
Could anyone help me out? I just want to do a fresh install of liquid smooth.
Click to expand...
Click to collapse
I found this in the Nexus 4 forum-http://forum.xda-developers.com/showthread.php?t=2147501. Sounds like the same issue.
joeyhdownsouth said:
I found this in the Nexus 4 forum-http://forum.xda-developers.com/showthread.php?t=2147501. Sounds like the same issue.
Click to expand...
Click to collapse
When I searched around with this issue I did find that and tried to follow those steps but even after trying it a few times I'm still having the same problem.
Rayz321 said:
When I searched around with this issue I did find that and tried to follow those steps but even after trying it a few times I'm still having the same problem.
Click to expand...
Click to collapse
Are you wiping data?
joeyhdownsouth said:
Are you wiping data?
Click to expand...
Click to collapse
Yes and I'm on Team Win 2.5
Does anyone think they can help me out?
Rayz321 said:
Does anyone think they can help me out?
Click to expand...
Click to collapse
Wipe everything, data, system, cache and dalvik
Then try reflashing your rom
Ok have you installed any app to sd type of application? It sounds like your internal storage is being read as external and visa versa.
Also i know there's lots of support for twrp but I swear by cwm when it comes to the GS3. I use twrp on my Nexus and that's fine but on the S3 cwm has always worked better in my opinion.
What roms are you trying to flash? They are sprint s3 roms right from this section?
Sent from the future via Xparent Green Tapatalk 2
CNexus said:
Wipe everything, data, system, cache and dalvik
Then try reflashing your rom
Click to expand...
Click to collapse
I've done that. That's what the one post suggested.
I just don't understand why I'm still getting apps showing up when I install new roms.
What about wiping storage? I know you don't want to lose anything but it sounds like something in your storage causing this.
Rayz321 said:
I've done that. That's what the one post suggested.
I just don't understand why I'm still getting apps showing up when I install new roms.
Click to expand...
Click to collapse
Please see my post right above this one I quoted here. Let us know a few of those things and maybe we can get you going in the right direction.
Sent from the future via Xparent Green Tapatalk 2
edfunkycold said:
Ok have you installed any app to sd type of application? It sounds like your internal storage is being read as external and visa versa.
Also i know there's lots of support for twrp but I swear by cwm when it comes to the GS3. I use twrp on my Nexus and that's fine but on the S3 cwm has always worked better in my opinion.
What roms are you trying to flash? They are sprint s3 roms right from this section?
Sent from the future via Xparent Green Tapatalk 2
Click to expand...
Click to collapse
I haven't installed any app to sd type applications.
I do think part of the internal is being used as external but I thought that's just how it was.
I only have roms, nandroids, and titanium backups on my sd card.
I installed twrp because when I first started it seemed like that was what most people were recommending but it doesn't matter to me. I might switch.
Also I've been switching between cleanbean and liquid smooth, both from this section.
The main thing that bugs me is when uninstalling apps says "cannot read data/xposed/modules.whitelist"
The app still uninstalls but it just doesn't seem good.
Rayz321 said:
I haven't installed any app to sd type applications.
I do think part of the internal is being used as external but I thought that's just how it was.
I only have roms, nandroids, and titanium backups on my sd card.
I installed twrp because when I first started it seemed like that was what most people were recommending but it doesn't matter to me. I might switch.
Also I've been switching between cleanbean and liquid smooth, both from this section.
The main thing that bugs me is when uninstalling apps says "cannot read data/xposed/modules.whitelist"
The app still uninstalls but it just doesn't seem good.
Click to expand...
Click to collapse
A couple weeks ago, I was switching from a AOSP ROM to a TW ROM and I got the same error. Thinking it was TWRP, I hooked my phone up to my computer and flashed CWM. I then tried to flash the ROM in CWM and it was a no go. I still got the same error. I just decided to transfer all my data from my internal sd to my computer. I used Odin to flash the stock tar file. After that, I used QBKing77's method to root from recovery. Then I flashed my ROM and I got 0 errors. So all I had to do was start fresh haha. It took a bit of time because I was taking many precautions (as should you) Good luck!
Sent from my SPH-L710 using xda app-developers app
Yes just as posted above, but before going the route of Odin back to stock. Copy all your files (important) from internal and external to your computer. Then boot into recovery no need to change now and reformat your internal and external storage, wipe cache and dalvik and fix permissions and reboot. Then download a fresh zip of a rom to flash and test it. If it all works then go through your files and move back what you need. I'm pretty sure you have a bunch of O folders in your internal.
Sent from the future via Xparent Green Tapatalk 2