I'm using cm9 that has the team win recovery. When I try to flash the cm 11 kitkat rom it says fail. Do i need to use a cwm recovery or is the download link bad ?
mr. ya-di-da said:
I'm using cm9 that has the team win recovery. When I try to flash the cm 11 kitkat rom it says fail. Do i need to use a cwm recovery or is the download link bad ?
Click to expand...
Click to collapse
Flash it from cwm... but after the flash completes, reboot recovery and do you're wipes ( again ) and flash kitkat from it's recovery. Then reboot.
Let it chill for a few minutes, then boot back to recovery and flash you're 4.4 gapps.
This process always worked for me on 4.3 and I'm assuming it will work on 4.4. But I've not flashed 4.4 yet. So proceed with caution.
Good luck...
I will try it when I get home from work so I can use Odin to flash a cwm recovery. Everytime I use mobile Odin to flash a recovery it bricks my phone ....why does that happen ?
mr. ya-di-da said:
I will try it when I get home from work so I can use Odin to flash a cwm recovery. Everytime I use mobile Odin to flash a recovery it bricks my phone ....why does that happen ?
Click to expand...
Click to collapse
I'm not sure about the mobile Odin issue... are you making sure the tar file for the kernel is a good download and that it is compatible with the Android version and rom you're trying to run...?
Try downloading the Directboot EL29 kernel from rwilco12's repo.. ( make sure you get the Directboot EL29 kernel and not the stock el29 kernel )
After you have it and the rom you want on you're sdcard... use mobile Odin to flash the el29 db kernel.. it should boot to recovery on it's own..
Push volume up, volume down, volume up... this enables the power button as the select button...
Do you're wipes... and flash 4.4...reboot recovery... do wipes.. ( data, cache, dalvik, and format system )...flash 4.4 again.. reboot.. settle in for a few minutes and then boot recovery and flash gapps 4.4...reboot.
Let me know how it goes... I'll stick around tonight until we get ya up and running...
It failed.. (status 7)
mr. ya-di-da said:
It failed.. (status 7)
Click to expand...
Click to collapse
Ok... I'll try to get to it tomorrow... but Thursday at the latest.
OK thx. I saw that other people where getting the same fail (status 7) let me know what u find.
Status 7 is a syntax error in the updater script... Probably missing a semicolon or something silly like that.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Not related to this issue, unsure if it would be better etiquette to make my own thread for this, but an issue I'm having with dastins CM11 ROM (12-04-13 version) is that I have two "Internal Storages" instead of one (I do not own/use a SD card)
On CM10/10.1/10.2 I had one internal storage, but on CM11 I have a 2GB internal storage and then a second internal storage (that things seem to not be installed to at all) with the remainder of my devices space.
One of the applications I used a lot on stock TouchWiz and earlier versions of CM is larger than two gigs, so on CM11 I can't even install it because it says I have insufficient storage. Is there a way I can combine the two internal storages into one, so it functions like it did on CM10.2 so I can use all of my devices space instead of only 2GB?
---------
Another question, and this one I'm probably just being blind and not seeing it, or maybe this setting is in a different location in KitKat, is my phone is set to USB mass storage instead of MTP. Normally I head over to Settings > Storage > hit the menu key and change USB connection type to MTP, but the menu key doesn't seem to do anything anymore on the Storage page. Where would I change to MTP instead of Mass Storage, or how can I just disable Mass Storage, I honestly don't care about being able to get any files on/off the device, but 90% of the time I'm charging on USB and I just don't want a full screen prompt showing up every time I touch my phone saying "Hey! It's Plugged In! Do you want to turn USB Storage on?"
You need to flash cm11 with the newest cwm... The old regular way of the"safe" recovery doesnt work... The easy way Is to download the blasphemy kernel and install it then boot back into recovery... It will be cwm 6.0.4.5... Flash the rom with this and no status 7...
Hope this helps...
Sent from my SPH-D710 using Tapatalk 2
I have an EL29 direct boot zip file that works with agats and even the newer cwms to flash back to.
I've tested it on the following recoveries and not had an issue at all:
agats (both 1.3 and 1.4), stock twiz, and the latest CWM they are useing.
I have gone to el29 direct boot with all of the above and had no issues, it goes into el29 recovery just fine.
DO keep in mind though I made this zip mainly for flashing into roms, not as a stand alone kernel, so you may have issues wif you use this as your standard go to kernel with the rom. Mst roms already have thier own kernel anyways, so that's normally not an issue, jsut so you are aware this is basically used for flashing roms not as the normal kernel.
I can host it on dev-host if anyone is interested, otherwise I won't bother.....and I ask because sometimes people just don't wanna be bothered, so I always ask......anyways let me know I will host it.
Just as a side note the steps I have done are as follows:
-reboot to recovery
-flash el29 zip file within said recovery (as I said I've tested this on all the above and it works fine)
-reboot recovery (it will be el29 now)
It should be back to the el29 recovery and you can flash from there.
Done this on hood pope (4.3), Viluminati (4.4 and 4.4.1 KitKat), cm10.1 (4.2.2) and stock Twiz rooted (not stock Twiz recovery) but agats recovery 1.3 and 1.4.
Those that don't know how to activate the power button to select what you do is toggle up > down >up > down until it says something about it being activated, you can then just use power to select your option.
kitkat 4.4.1
I rooted my device using rwilcos fl24 method although I was on a fd24 model. After root I flashed a custom recovery using Odin I believe it was agats...I then proceeded to flash a ROM cm10.1 then upgraded to cm 10.2. Now running KitKat 4.4.1 12/7 edition I believe and works like a charm...thought I had a battery problem because it wouldn't charge right it would take forever. I didn't I jus had to stop oc/uv ...BTW using the kernel that came with the rom flashed using cwm recovery from cm10 which was on jb not ICS and works fine little bugs here and there such as attempting to open incognito window fc browser the battery read when phone was off was inconsistent versus when the device is off but other then that KitKat is great if I can help anyone I'll be more then glad to I don't mind helping people that don't know I don't give attitude and noon user friendly,after all I was there once....besides all the guys who really know what thier doing are busy creating Roma and tweakimg programs to keep us happy let's make it a little easier on them like I said I don't know everything but I have some knowledge and if I'm able to point you in the right direction without wasting your time I will
easyrider77 said:
I have an EL29 direct boot zip file that works with agats and even the newer cwms to flash back to.
I've tested it on the following recoveries and not had an issue at all:
agats (both 1.3 and 1.4), stock twiz, and the latest CWM they are useing.
I have gone to el29 direct boot with all of the above and had no issues, it goes into el29 recovery just fine.
DO keep in mind though I made this zip mainly for flashing into roms, not as a stand alone kernel, so you may have issues wif you use this as your standard go to kernel with the rom. Mst roms already have thier own kernel anyways, so that's normally not an issue, jsut so you are aware this is basically used for flashing roms not as the normal kernel.
I can host it on dev-host if anyone is interested, otherwise I won't bother.....and I ask because sometimes people just don't wanna be bothered, so I always ask......anyways let me know I will host it.
Just as a side note the steps I have done are as follows:
-reboot to recovery
-flash el29 zip file within said recovery (as I said I've tested this on all the above and it works fine)
-reboot recovery (it will be el29 now)
It should be back to the el29 recovery and you can flash from there.
Done this on hood pope (4.3), Viluminati (4.4 and 4.4.1 KitKat), cm10.1 (4.2.2) and stock Twiz rooted (not stock Twiz recovery) but agats recovery 1.3 and 1.4.
Those that don't know how to activate the power button to select what you do is toggle up > down >up > down until it says something about it being activated, you can then just use power to select your option.
Click to expand...
Click to collapse
There's a tread that might use your assistance
Sent from my d710 using XDA Premium 4 mobile app
CM 4.4.1 build 2013-12-07
Hey guys...Been rocking this build for a month now with no real problems. Only a couple of things i have noticed and thought I would drop in and mention since I haven't heard about it talked about in the main thread or here yet.
1. Every once in a while I will be showing full 3g bars and wont connect to the internet (says "no connection") I have fixed this with just toggling off and then back on the Sprint Radio Toggle in the drop down window. The phone will then immediately connect after.
2. During the first 2 weeks the camcorder was working...now its just borked. Every time i try to use it, it will just freeze up (the camcorder) and then force close. Then the camera is also unresponsive after trying to use the camcorder. I have tried to clear catch and force stop but the only way to fix this is with a reboot.
SPH-D710 EL26.....flashed to Boost Mobile with working Hangouts MMS and SMS from day one (no fix)
Build; 4.4.1 2013/12/07
Everything else is just ROCK SOLID, and love this ROM.
adjday said:
2. During the first 2 weeks the camcorder was working...now its just borked. Every time i try to use it, it will just freeze up (the camcorder) and then force close. Then the camera is also unresponsive after trying to use the camcorder. I have tried to clear catch and force stop but the only way to fix this is with a reboot.
Click to expand...
Click to collapse
This Camera Fix worked to get my camcorder working perfectly. Have you tried it? http://forum.xda-developers.com/showthread.php?p=48620791&highlight=3a04f599232ee62c6b63a6e4f1d3f7d3#post48620791
You can uninstall the gallery app (using titanium backup)
Then download and install a different Kit Kat gallery app...(just search google, it's everywhere Lol)
Related
I soft-bricked my galaxy and there's no way to fix it, help! Okay, this is a what happened, I installed a custom ROM which worked out perfectly well until one day all applications started force closing for apparently no reason so I reboot and got stuck in a boot loop. I can only access download mode, recovery is out of the question. I tried to flash back to stock with Odin and it "passed" but the screen was just blank. So, I removed the USB cable hoping it will work and it got stuck in another boot loop. I tried everything that I could have think of but nothing works. It seems that I'm not the only one and is common for Galaxy W devices. Please help!
Also, in the worst case how do I send it back to Samsung? I mean, I know how to but will they fix it?
Location ?
Sent from my GT-I8150 using xda premium
dont worry , you can just flash it again. A new stock ROM would do. Its no problem.
We have a guide here on this forum. Check it out ^_^
andynroid said:
Location ?
Sent from my GT-I8150 using xda premium
Click to expand...
Click to collapse
Umm....Malaysia?
jrandroid said:
dont worry , you can just flash it again. A new stock ROM would do. Its no problem.
We have a guide here on this forum. Check it out ^_^
Click to expand...
Click to collapse
I have tried that and it does not work.
Me too I got the same problem. But flashed a stock rom and everything 's working well except data network. Sending it to Samsung centre to fix. To brick it join the Galaxy W Malaysian users group on FB I'm sure you'll find the solution to brick
Sent from my GT-I8150 using XDA
darthbii said:
Me too I got the same problem. But flashed a stock rom and everything 's working well except data network. Sending it to Samsung centre to fix. To brick it join the Galaxy W Malaysian users group on FB I'm sure you'll find the solution to brick
Sent from my GT-I8150 using XDA
Click to expand...
Click to collapse
Can you please explain what did you do exactly?
Hi
Sorry, but if you cannot go to recovery problem..
The problem is in your hardware
I already put this problem to this thread
Read carefully
To many member have re-post this problem
So your are not alone
For the others please aware this situation,
This is not problem that you can solve by flashing
Read the thread with "star" first before you posting and get confuse
Regards
Stock Gaming Rom Stable i8150XXLM8
i may have the same problem i use cynanogen mod 9 build 3 then flash to this stock gaming rom..problem start
1. 3g/wcdma not detected/no 3g icon appear/cannot download anuthing
2. reboot using clockwokr mod....but cannot reboot..its say root acces posibly lost..but SU does exist in apps
andydidacus said:
i may have the same problem i use cynanogen mod 9 build 3 then flash to this stock gaming rom..problem start
1. 3g/wcdma not detected/no 3g icon appear/cannot download anuthing
2. reboot using clockwokr mod....but cannot reboot..its say root acces posibly lost..but SU does exist in apps
Click to expand...
Click to collapse
did you full wipe before flashing stock rom?
what stock gaming rom, it is full recovery?
you may can try:
- flashing again cwm using odin,
- if succesfull, boot to cwm, format data and cache, except system
- try reboot normally.
- if failed, format everything, except your sdcard,
- flashing stock rom using odin, (better use stock rom provided for your country), use original stock rom, not modified rom ! with size more than 350mb, its contain recovery, baseand and everything you need. of course your cwm will be replaced after. you can flash again cwm after your phone boot normally.
good luck.
andydidacus said:
i may have the same problem i use cynanogen mod 9 build 3 then flash to this stock gaming rom..problem start
1. 3g/wcdma not detected/no 3g icon appear/cannot download anuthing
2. reboot using clockwokr mod....but cannot reboot..its say root acces posibly lost..but SU does exist in apps
Click to expand...
Click to collapse
In reverting back to GB 2.3.6 from CM9, you should do format /system to be able to flash successfully. Try it.
Yes i jave succesfully revert to gb rom..n finally traded it woth sgn
Sent from my GT-N7000 using xda premium
Thanks
coliv_aja said:
did you full wipe before flashing stock rom?
what stock gaming rom, it is full recovery?
you may can try:
- flashing again cwm using odin,
- if succesfull, boot to cwm, format data and cache, except system
- try reboot normally.
- if failed, format everything, except your sdcard,
- flashing stock rom using odin, (better use stock rom provided for your country), use original stock rom, not modified rom ! with size more than 350mb, its contain recovery, baseand and everything you need. of course your cwm will be replaced after. you can flash again cwm after your phone boot normally.
good luck.
Click to expand...
Click to collapse
Thanks really worked! ^
Hi! yesterday I tried to get cyanogenmod to my Samsung galaxy W. Firstly I used this tutorial to root my phone View attachment 1899558
Then I installed clockworkmod recovery with this tutorial
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I did the ''IV. Accessing ClockworkMod Recovery'' , I tried to backup my phone, but there wasn't enough space to do it, so I pressed ''reboot'' and this happens, it goes through the samsung and galaxy w logo, but after that the screen just turns black, this happens every time when I try to turn it on. I can access the clockworkmod recovery.
I have tried to ''wipe the cache partition'', ''wipe data/factory reset'' and wipe ''dalvik cache'' but it doesn't seem to work.
What should I do, I don't want cyangenmod after this haha I just want to know if there is a way to get the phone working.
Any answers would be appreciated
Eerooo said:
Hi! yesterday I tried to get cyanogenmod to my Samsung galaxy W. Firstly I used this tutorial to root my phone View attachment 1899558
Then I installed clockworkmod recovery with this tutorial View attachment 1899561
When I did the ''IV. Accessing ClockworkMod Recovery'' , I tried to backup my phone, but there wasn't enough space to do it, so I pressed ''reboot'' and this happens, it goes through the samsung and galaxy w logo, but after that the screen just turns black, this happens every time when I try to turn it on. I can access the clockworkmod recovery.
I have tried to ''wipe the cache partition'', ''wipe data/factory reset'' and wipe ''dalvik cache'' but it doesn't seem to work.
What should I do, I don't want cyangenmod after this haha I just want to know if there is a way to get the phone working.
Any answers would be appreciated
Click to expand...
Click to collapse
Some wrong sequence there :
Forgets the steps as per attachment.
In assumption the CM9 ROM.zip is in your SD Card...
Boot to CWM
Locate the CM9 ROM using and remember the location i.e. External SD etc
Now under Advance...Format all folders clean (not the folder containing the CM9 ROM)
Wipe / Format / Cache etc = the usual
Wipe Dalvik
Fix Permission
Flash the CM9 then GAPPS
Reboot...:good:
No need to back-up once you have used CM9...you will never go back to GB
If you insist on back-up just move all your treasures in your PC 1st, best to format the SD Card then move the ROM.zip to it
andynroid said:
Some wrong sequence there :
Forgets the steps as per attachment.
In assumption the CM9 ROM.zip is in your SD Card...
Boot to CWM
Locate the CM9 ROM using and remember the location i.e. External SD etc
Now under Advance...Format all folders clean (not the folder containing the CM9 ROM)
Wipe / Format / Cache etc = the usual
Wipe Dalvik
Fix Permission
Flash the CM9 then GAPPS
Reboot...:good:
No need to back-up once you have used CM9...you will never go back to GB
If you insist on back-up just move all your treasures in your PC 1st, best to format the SD Card then move the ROM.zip to it
Click to expand...
Click to collapse
Thank you so much!There is still a problem my phone recognizesmy sd card it and also tells me how much storage i have left. But when i want to use an application like the camera it says there is no sd card. What should I do?
E: Already got the problem fixed
Got another SD card to swap ?
Please Help me T.T
I just wanna go back to original Stock Rom and yesterday I Flash the firmware Malaysia with Odin.. the Odin haven't pass then my phone automatically restart and after few minutes the odin said PASS and the message there wrote ''distroy instant'' and ''Killed timer''... after that my galaxy w cannot boot.. it just stucked at the start screen wallpaper there.....
please help me... sorry for my broken english...
---------- Post added at 02:01 PM ---------- Previous post was at 01:21 PM ----------
odin wrote Close serial portal and wait until rebooting but it havent PASS and my wonder cannot start and it stucked at samsung logo....
j0rd4nkzf said:
Umm....Malaysia?
I have tried that and it does not work.
Click to expand...
Click to collapse
last time my phone cannot start too because i flash wrong file, then i send service centre at lowyat saying my phone suddenly can't be turned on (don't say ur already root or whatever can void the warranty)
Ore Sanjou!
j0rd4nkzf said:
I soft-bricked my galaxy and there's no way to fix it, help! Okay, this is a what happened, I installed a custom ROM which worked out perfectly well until one day all applications started force closing for apparently no reason so I reboot and got stuck in a boot loop. I can only access download mode, recovery is out of the question. I tried to flash back to stock with Odin and it "passed" but the screen was just blank. So, I removed the USB cable hoping it will work and it got stuck in another boot loop. I tried everything that I could have think of but nothing works. It seems that I'm not the only one and is common for Galaxy W devices. Please help!
Click to expand...
Click to collapse
u must service it in SamsungServiceCenter
I've read and read many threads in this subject. Now im just soo confused. Please help me understand the steps required to update my rooted GB to ICS.
This is what i'm on.. rogue ET recovery 1.1.2 (CWM v5.0.2.7)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I would like to update to go to [ROM][TeaM VeNuM]◣◢)BOA(now Blue Too)v0.2 -FF18-Updated 07-02-12 De-Odexed TW/LG/ICS
In order for me to update to this ICS rom, i need to update my CWM recovery correct..? AGAT recovery is what most recommend.
here..
http://forum.xda-developers.com/showthread.php?t=1687354
So i boot my phone into recovery and install the AGAT.zip to update my recovery then i should be free to install venum rom correct?
Or do i need to be already in a ICS stock rom to flash the AGAT recovery to update to the Venum rom...???
please help me understand..!!!! thanks in advance
Your model number shows SPH-D710 which is the Sprint Epic Touch 4G. This forum is for the SGH-i777 AT&T Galaxy S II. Completely different phone.
Ill bounce this to the ET4G forum for you...
Red5 said:
Your model number shows SPH-D710 which is the Sprint Epic Touch 4G. This forum is for the SGH-i777 AT&T Galaxy S II. Completely different phone.
Ill bounce this to the ET4G forum for you...
Click to expand...
Click to collapse
Wow... ok.. I feel really stupid now thanks... I'm starting out well.. lol
anyone..??
If you have mobile Odin install the stock el26 kernel from there if not use Odin boot into recovery and use calks wipe all then flash rom should work with no problems its the safest way to flash here's a link to el26 from my drive save ya some time looking. make sure you nandroid backup and titanium backup before hand and also make sure you have the rom on your sdcard.
El26
https://docs.google.com/file/d/0B7aReWYt54fKUGxBNXEwXzNPaHM/edit
Calks wipe all
https://docs.google.com/file/d/0B7aReWYt54fKMTlzN2p0YXFqUXM/edit
Sent from my SPH-D710 using Tapatalk 2
Sry forgot to set the share settings should be ok now
Sent from my SPH-D710 using Tapatalk 2
Its alright, ya got it now =)
I was attempting to flash to the newest AOKP rom(7-13), well preparing to flash to it anyhow. I flashed the latest AGATS recovery as per QBKing's video posted on the...14th I'm sure.
Anyhow, I flashed the recovery and now I am unable to get past the samsung splash. After having done this, I imagine I did it wrong, but I can still get to the recovery, which is AGATS now. You say that the way you just posted was the safest way to flash? I believe you, being that it looks the simplest.
orr
Would i be able to flash the AOKP rom now? QBK said this is the safest recovery, if something on my prior setup isn't savy with this recovery, if I flash this new ICS rom, then it should all work itself out?
So for anyone wondering, I went ahead and flashed the rom, and it worked. I went ahead and installed AOKP rom, and it booted up. I re-installed agats recovery FF18 (<-- this is right right? I need to learn, teach me! lol) then booted back into the rom to make sure that it worked, and it did. rebooted into recovery, mounted usb, copied gapps, unmounted.
I just flashed gapps, and am rebooting ......and am now stuck in a boot loop to the recovery? What happened??
Alright lol, I somehow was stuck in a loop, but I did a battery pull whilst in agat, then hit the power button, it rebooted into agat but straight into the reboot menu, and then I clicked reboot to system and I'm back to the rom now.
I'm not getting any Wifi or 4g, and low signal. but I do have play store. jumped feet first into it, now I gotta deal with it ....
Agats recovery is a TouchWiz based recovery. That's probably why you are having issues with wifi and possible many other issues. I suggest you start again and flash EL26 using mobile Odin , factory reset+ wipe cache+dalvik cache, install aokp rom and gapps right after and then reboot. The included recovery in the latest AOKP, TWRP, has been modified and be labeled as safe. There is no need to flash another recovery. But as you may know, there is always a risk when flashing ICS, so take things slow and double check things
Sent from my SPH-D710 using xda app-developers app
Well it would seem that another one of my problems is that I can't access my storage menu under settings, leading me to believe that I don't have any access to my SDcard. I'm just going to use regular odin to flash down to EL26. then follow btaylor545 instructions below. Unless I ca figure out installing this mobile_odin .apk to my phone somehow. I'd prefer that, don't wanna raise the y_triangle.
mosez.315 said:
Well it would seem that another one of my problems is that I can't access my storage menu under settings, leading me to believe that I don't have any access to my SDcard. I'm just going to use regular odin to flash down to EL26. then follow btaylor545 instructions below. Unless I ca figure out installing this mobile_odin .apk to my phone somehow. I'd prefer that, don't wanna raise the y_triangle.
Click to expand...
Click to collapse
You can't go into the market and download it? You could also just download a file explorer from the market and install it that way. And there now an app called Triangle away and will take away the triangle as long as you are on ICS. It's made by the same person who made Mobile Odin, Chainfire.
Yeah, I have the store, but I don't have access to it because I need to be connected to my data, can't via 3/4G, or my wifi, so I can't download anything via market. I'm reading to figure something out now...
---------- Post added at 11:23 PM ---------- Previous post was at 11:00 PM ----------
Alright!
So through all my fruitful searching (it actually turns up great results here!!) I got Mobile Odin Lite pushed to my device via APKPush. I need to instal an addon because its Odin Lite, but its only for flashing FW's, so I oughta be all right to flash the el26 kernel with Mobile Odin.
So now I have all of the tools available to me, I just need the route. I oughta be fine doing all of this, ICS to ICS, because it's the released ICS, not the leaked correct?
:highfive: i just wanted to give everyone a big thanks... I'm officially on ICS..! :victory:
I basically did as stated by btaylor545 and SkippyDogg...
- Used stock el26 kernel .TAR version
- flashed stock EL26 kernel using ODIN mobile purchased from the market.
- Phone will reboot after flash. Hold vol up and power button to go into recovery.
- use Calks wipe all .zip multiple times..
- then flashed my ICS rom...
Rom used:
http://forum.xda-developers.com/showthread.php?t=1694483
One last question... If i wanted to try another ICS rom, is it best practice to flash back to GB rom and EL26 kernel then go to another ICS rom or just using EL26 stock kernel be sufficient to jump to another ICS rom.. Thanks again..
mclain1 said:
:highfive: i just wanted to give everyone a big thanks... I'm officially on ICS..! :victory:
I basically did as stated by btaylor545 and SkippyDogg...
- Used stock el26 kernel .TAR version
- flashed stock EL26 kernel using ODIN mobile purchased from the market.
- Phone will reboot after flash. Hold vol up and power button to go into recovery.
- use Calks wipe all .zip multiple times..
- then flashed my ICS rom...
Rom used:
http://forum.xda-developers.com/showthread.php?t=1694483
One last question... If i wanted to try another ICS rom, is it best practice to flash back to GB rom and EL26 kernel then go to another ICS rom or just using EL26 stock kernel be sufficient to jump to another ICS rom.. Thanks again..
Click to expand...
Click to collapse
Welcome to ICS! :victory:
To Answer your question, just flashing the kernal though Mobile Odin and repeat the steps I mentioned and you're good to goo.
I've managed to get to ICS successfully too! AOKP Fri da 13th build. I'm having problems with service still, can't find where to connect to my wifi, and no 4g. Is that where a different modem kernel would come in?
SkippyDogg said:
Welcome to ICS! :victory:
To Answer your question, just flashing the kernal though Mobile Odin and repeat the steps I mentioned and you're good to goo.
Click to expand...
Click to collapse
That is awsome skippyDogg..! Thanks again.. . Awesome community..!
mosez.315 said:
I've managed to get to ICS successfully too! AOKP Fri da 13th build. I'm having problems with service still, can't find where to connect to my wifi, and no 4g. Is that where a different modem kernel would come in?
Click to expand...
Click to collapse
Mosez, i'm still a noob, but i usually resolve reception issues by flashing a different modem. I'm on FC14 now with this new rom and so far no connectivity issues, i'll give it a couple more days..
I think I'm still on a GB kernel for some reason...when I go to system settings>about phone> it tells me I still have an EL29 baseband version. Whats up with that? Is that the problem causer?
Your base band version is your modem. Flash a rom does not upgrade your modem. There is a section with all the different modems available. You can flash thru recovery or mobile Odin.
Sent from my SPH-D710 using xda app-developers app
Lol, I know now. The delay of any responses to my inquiries is making me search these things out on my own, but the directional assistance of just getting it out of my head and down on the forum helps immensely.
I found the Modem/kernel repository, and am going to flash the FF18 modem to see if it turns out some better results. My question now is that all of the guide are telling me to flash CWM recovery kernel, like a whole new rom, you know. I was curious if I could just flash this zip with the TWRP recovery, and just be the end of it, or do I wipe catch/factory restore/dalvik too?
mosez.315 said:
Lol, I know now. The delay of any responses to my inquiries is making me search these things out on my own, but the directional assistance of just getting it out of my head and down on the forum helps immensely.
I found the Modem/kernel repository, and am going to flash the FF18 modem to see if it turns out some better results. My question now is that all of the guide are telling me to flash CWM recovery kernel, like a whole new rom, you know. I was curious if I could just flash this zip with the TWRP recovery, and just be the end of it, or do I wipe catch/factory restore/dalvik too?
Click to expand...
Click to collapse
I believe the newest TWRP allows you to flash modems now, so it should be as easy and downloading the FF18 Modem.zip and placing it on your internal storage, rebooting into TWRP recovery and flashing it. Just as a note, different modems work best on different phones.
So for example your phone might get fast 3G speeds on FF18 but get really slow 3G at FF02. 4G is also affected when flashing a new modem. So you have test out each modem if you want the best possible speed for your phone.
And sadly, AOKP at the moment does not allow you to update the phones Profile and PRL. Both of those actions together can fix signal and and speed issues from time to time.
Sent from my SPH-D710 using xda app-developers app
Hi guys, i just updated my Ace 2 from 2.3.6 GB to 4.1.2 JB through Samsung Kies. After the update process, i used the "root.zip" (err, just saw it while searching from the forum) in order for it to be rooted. I also downloaded gooManager, Root Browser, ROM manager, Greenify, Titanium. Also removed unnecessary apps using Root Browser ( saw list of bloated apps on Ace 2 also in this forum). It is my first time rooting my droid and I want to obtain knowledge in order to maximize my droid's capabilities.
So here's my questions (so far):
1. Why is it my Recovery Mode is looking like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
instead of looking like this:
since because i wanted to flash it but when I see some tutorials, their recovery mode has a ROM Manager logo which made me hesitated on flashing.
2. What can you recommend on me , a newbie , about flashing tips in order to flash my Ace 2 into 4.4 kitkat?
Source : http://forum.xda-developers.com/showthread.php?t=2524905
3. Can someone tell me how to flash proper because im confused on flashing through recov mode and using Odin
4. Lastly, if i factory reset my 4.1.2 JB through recov. mode, will it revert my droid into 2.3.6 GB ? will it remove the root?
since i also saw some tutorials flashing by factory reset in recov. mode then installing from SD Card also in recov. mode
Please help me clear my mind on flashing Thank you !
So here's my questions (so far):
1. Why is it my Recovery Mode is looking like this:
instead of looking like this:
since because i wanted to flash it but when I see some tutorials, their recovery mode has a ROM Manager logo which made me hesitated on flashing.
1- because thats CWM, never use rom manager. Search forum for cwm 6 by shaaan
EDIT: temp cwm 6 http://forum.xda-developers.com/showthread.php?t=2141395
2. What can you recommend on me , a newbie , about flashing tips in order to flash my Ace 2 into 4.4 kitkat?
Source : http://forum.xda-developers.com/showthread.php?t=2524905
2- thats a theme, no kitkat yet
3. Can someone tell me how to flash proper because im confused on flashing through recov mode and using Odin
3- follow instructions in first post of EVERY rom thread, you should be safe
4. Lastly, if i factory reset my 4.1.2 JB through recov. mode, will it revert my droid into 2.3.6 GB ? will it remove the root?
since i also saw some tutorials flashing by factory reset in recov. mode then installing from SD Card also in recov. mode
4-
-no
-no
-dont follow those tuts, follow our ace 2 ones, to revert to 2.3 search forum for the thread, its late here ill try to link the thread for you
Sent from my GT-I8160 using Tapatalk
Try to download it again and as it says, it is for Android 4.3.
nairb310 said:
1. Why is it my Recovery Mode is looking like this instead of looking like this:
4. Lastly, if i factory reset my 4.1.2 JB through recov. mode, will it revert my droid into 2.3.6 GB ? will it remove the root?
since i also saw some tutorials flashing by factory reset in recov. mode then installing from SD Card also in recov. mode
Please help me clear my mind on flashing Thank you !
Click to expand...
Click to collapse
1: In the Ace 2, recovery comes from the kernel. You can temporarily load "cwm6.zip" to upgrade until the next reboot "Android system recovery 3E" into CWM 6.0.2, and once you install another kernel with a modified recovery (CM10.2 contains CWM 6.0.3 for example) it will always load in place of the stock one.
4: Factory reset means deleting everything under /data (the system memory in which apps are installed by default), /cache and .android_secure (apps moved to SD or USB storage), the OS and all system applications will persist. You will technically stay rooted, but SuperSU will only remain if it was installed as a system app.
To switch between 2.x and 4.x you must flash and repartition with a complete 3-part firmware (with PIT, CODE/PDA and CSC files), like LK4 or MB4. After that you can install an OS of the same generation using Odin/Heimdall (for tar files) or CWM (for zips).
Most stock-derivate firmwares recommend a base version but it's usually optional; AOSP roms (Cyanogen, AOKP and the like) don't care at all.
Ryccardo said:
1: In the Ace 2, recovery comes from the kernel. You can temporarily load "cwm6.zip" to upgrade until the next reboot "Android system recovery 3E" into CWM 6.0.2, and once you install another kernel with a modified recovery (CM10.2 contains CWM 6.0.3 for example) it will always load in place of the stock one.
4: Factory reset means deleting everything under /data (the system memory in which apps are installed by default), /cache and .android_secure (apps moved to SD or USB storage), the OS and all system applications will persist. You will technically stay rooted, but SuperSU will only remain if it was installed as a system app.
To switch between 2.x and 4.x you must flash and repartition with a complete 3-part firmware (with PIT, CODE/PDA and CSC files), like LK4 or MB4. After that you can install an OS of the same generation using Odin/Heimdall (for tar files) or CWM (for zips).
Most stock-derivate firmwares recommend a base version but it's usually optional; AOSP roms (Cyanogen, AOKP and the like) don't care at all.
Click to expand...
Click to collapse
Thank you for your reply but i cant understand some of the term you are saying XD So basically on 1. recovery kernel can be upgraded ? and my kernel i think is old ? so that is why my recov mode is not looking like ROM manager logo?
so also i can flash using ROM manager or Recovery mode with my current system ?
Flash temp cwm 6 zip in stock recovery(will be called update.zip, i added link). Dont use rom manager
Sent from my iPhone
nairb310 said:
Thank you for your reply but i cant understand some of the term you are saying XD So basically on 1. recovery kernel can be upgraded ? and my kernel i think is old ? so that is why my recov mode is not looking like ROM manager logo?
so also i can flash using ROM manager or Recovery mode with my current system ?
Click to expand...
Click to collapse
The same kernel that runs "the full Android experience" also contains the recovery that boots with up+home+power. Some kernels have the "Android system recovery 3E" (which can be temporarily upgraded to CWM with cwm6.zip), others have CWM directly.
Basically, if you have a Cyanogen ROM installed, it will have CWM preinstalled. For everything else keep the temporary CWM in you external storage.
(All this ignores Gingerbread kernels, but let's keep matters simple as you're probably using JB)
Work in Progress
List of Custom Recoveries for the Samsung Galaxy Ace II X
For all things rooting and installing, a custom recovery is often needed. New things are being developed day and night. Thus, I find it necessary for there to be a list of all the recoveries that are compatible with the Samsung Galaxy Ace II X. Some are better than others, though it is a matter of preference. Anyways, commencing the list...
1. ClockworkMod 5.5.0.4 - not my work
ClockworkMod recovery, usually abbreviated as CWM or CWMR, is a custom recovery based off of AOSP source, created by Koushik Dutta (known by the nickname "Koush").
Bugs - Mount USB doesn't work.
Download
2. ClockworkMod 6 - not my work
Bugs - Mount USB doesn't work, "dancing screen," SOME USERS REPORT THAT INSTALLING CWM6 CAUSES THE DEVICE TO BOOT INTO RECOVERY INSTEAD OF THE ROM
Download
3. TeamWin Recovery Project 2.6.3.0 - my work
TeamWin Recovery Project, often abbreviated as TWRP, is a custom recovery that has a fully touch-driven interface. Aside from the uniquity of being 100% touch controlled, it also contains an ubiquity of features. It has a built-in file manager, support for sideloading via ADB, support for backups and restoring backups, a completely theme-able interface, and more sorts of customization.
Bugs - Mount USB doesn't work.
Download
Changelog:
Release 2 - backported some features from TWRP 2.7, fixed color tint issue, implemented internal storage
Release 1 - initial release
4. TeamWin Recovery Project 2.7.1.0 - my work
Download
Bugs - None reported.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Changelog:
Release 4 - Upgraded to 2.7.1.0 (customized to build on a JB-based tree: removed mouse support via USB OTG, removed text wrap for now), fixed internal storage
Release 3 - Fixed color tint issue
Release 2 - Fixed USB Mass Storage
Release 1 - Initial release *TWRP 2.7.1.0 has some mount issues. Don't use it.
5. TeamWin Recovery Project 2.8.1.1 - by @draekko
Check his post here for details and download links.
This list will be updated regularly as recoveries are updated, new recoveries are built, or for miscellaneous reasons. If there are any bugs I haven't mentioned for any of the recoveries, let me know and I'll add it to the OP.
Nice thread.
keep up the good work.
Any more recoveries and kernels for ace2x 7560m
Sent from my GT-S7560M using XDA Premium 4 mobile app
CodeName, you resolve the bug for TWRP 2.6 can you try for CWMR 6 ? :angel:
It's just a question :good:
Woops, wasn't seeing any notifications because I forgot to suscribe. Anyways...
AndroidAssassin said:
Any more recoveries and kernels for ace2x 7560m
Sent from my GT-S7560M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What do you mean? I can tell you that I am not done with custom recoveries or custom kernels. CM10.2 is just my focus at the moment. Also, this thread is under construction. I don't have time to work on it for awhile.
Seb269 said:
CodeName, you resolve the bug for TWRP 2.6 can you try for CWMR 6 ? :angel:
It's just a question :good:
Click to expand...
Click to collapse
I've already tried, but I either got build errors or a black screen when I booted into CWM6. I'll try again sometime another day, because I would love to get a nonbuggy CWM6 working. Just a question - is CWM6 different from Philz Touch or are the two a single custom recovery?
Codename13 said:
Woops, wasn't seeing any notifications because I forgot to suscribe. Anyways...
What do you mean? I can tell you that I am not done with custom recoveries or custom kernels. CM10.2 is just my focus at the moment. Also, this thread is under construction. I don't have time to work on it for awhile.
I've already tried, but I either got build errors or a black screen when I booted into CWM6. I'll try again sometime another day, because I would love to get a nonbuggy CWM6 working. Just a question - is CWM6 different from Philz Touch or are the two a single custom recovery?
Click to expand...
Click to collapse
They are the same.
Bug report (TWRP 2.7.0.0)
I have bug report (TWRP 2.7.0.0) - settings are not saving, every time I enter recovery, I have to set everything again. Console says that it can't find something to store the settings if I remember correctly.
gregory678 said:
I have bug report (TWRP 2.7.0.0) - settings are not saving, every time I enter recovery, I have to set everything again. Console says that it can't find something to store the settings if I remember correctly.
Click to expand...
Click to collapse
The latest release? I have no such problem. TWRP is configured so that the settings are stored on the external sdcard. So if you don't have one, your settings won't be saved. I considered setting the cache partition as the TWRP settings storage, but cache is often wiped when installing ROMs and packages. The same with system, data, et cetera. I've considered setting the recovery partition as a settings storage partition; however, whenever a new build of TWRP is installed, the recovery partition will be overwritten. I could try splitting the cache partition up so there is the cache partition and a new 12mb partition, but then there would either be errors when installing firmwares via Odin, or the new settings storage partition would be wiped. Unless you have any better ideas than the sdcard being the settings storage, don't complain. I'm not sure what's causing your issue - perhaps it's because you only insert your sdcard when you boot into TWRP? Enlighten me, and tell me a bit about your device setup (ROM, kernel, size of sdcard, etc).
OMG, I'm such dumb, I just noticed that settings file is hidden. I was wondering why it's always left empty folder after rebooting from recovery mode, now I discovered a hidden settings file in it, I'm Scherlock of the year . Sorry for bothering you, can someone delete these ashaming posts?
Hi Everyone, so I have tried installing a few of these recoveries with Odin. Every time it runs through fine, no errors, but when I restart the device in recovery mode I just get the default stock recovery screen. Has anyone encountered this?
I'm going to stop working on TWRP 2.7.x because it is designed to be built in KitKat-based ROMs' source trees since I don't work on KitKat. I had several issues trying to restore a backup of stock ROM, because it does not have SELinux support at all. There's a reason why TWRP dropped support for older versions of Android - SELinux. It causes the restore to fail for some reason. Anyways, I'll message one of our device's KitKat-based ROM devs, and I'll find someone who can continue work on TWRP 2.7 for us. I was also having issues compiling it after some major commits that were committed to it, so I really am unable to compile it properly unless I migrate to KitKat, which I won't be doing for awhile. Good news though, I've managed to get internal storage working on TWRP 2.6.3.0!
Jeremicus said:
Hi Everyone, so I have tried installing a few of these recoveries with Odin. Every time it runs through fine, no errors, but when I restart the device in recovery mode I just get the default stock recovery screen. Has anyone encountered this?
Click to expand...
Click to collapse
Delete /system/etc/install-recovery.sh then try installing a recovery again and booting into it.
Can someone make a .zip file that has the recoveries .img to be flashed in recovery instead of .tar which needs odin for the ace2x preferably one of TWRP RECOVERIES PLEASE
Sent from my GT-S7560M using Tapatalk
I was thinking about the advantages of TWRP 2.7 over 2.6. I knew that if I looked in the commit history for 2.7 on Github, I would be bound to find the commits that brought in some of my favorite features of TWRP 2.7.0.0. That, along with I having just discovered that Github commits can be download as patches, will bring the best version of TWRP for us yet. So far, I've successfully backported haptic feedback (along with the settings for it) and a bit more. I've also fixed internal storage in TWRP. I plan to backport the smoother scrolling, USB Mass Storage (it only works in 2.7 at the moment because 2.7 added in a different way to handle and mount UMS. I'll backport the different way of handling and mounting UMS), and add in some other bits of fun. It's going to be really cool, and it really isn't time consuming, so I should be able to bring it to you all very soon.
AndroidAssassin said:
Can someone make a .zip file that has the recoveries .img to be flashed in recovery instead of .tar which needs odin for the ace2x preferably one of TWRP RECOVERIES PLEASE
Sent from my GT-S7560M using Tapatalk
Click to expand...
Click to collapse
Just download Recovery Tools from the Play Store.
It dont have nething for ace2x
Sent from my GT-S7560M using XDA Premium 4 mobile app
Codename13 said:
I'm going to stop working on TWRP 2.7.x because it is designed to be built in KitKat-based ROMs' source trees since I don't work on KitKat. I had several issues trying to restore a backup of stock ROM, because it does not have SELinux support at all. There's a reason why TWRP dropped support for older versions of Android - SELinux. It causes the restore to fail for some reason. Anyways, I'll message one of our device's KitKat-based ROM devs, and I'll find someone who can continue work on TWRP 2.7 for us. I was also having issues compiling it after some major commits that were committed to it, so I really am unable to compile it properly unless I migrate to KitKat, which I won't be doing for awhile. Good news though, I've managed to get internal storage working on TWRP 2.6.3.0!
Click to expand...
Click to collapse
So you suggest 2.6.3.0 instead 2.7.0.0 for stock rom users. Regarding restore issues?
______________________________________________
Thank you for great work.
So far so good. The only Bug-free recovery! :victory:
husokal said:
So you suggest 2.6.3.0 instead 2.7.0.0 for stock rom users. Regarding restore issues?
______________________________________________
Thank you for great work.
So far so good. The only Bug-free recovery! :victory:
Click to expand...
Click to collapse
Yes, I say to use 2.6.3.0 as a universal recovery for our device. TWRP 2.6.3.0 works for both stock and custom ROMs, it doesn't enforce SELinux, so I say to use it. Plus, I've back ported some little changes from 2.7 to make it even better. Thank you for the praise, but it actually does have some bugs (mount USB storage) which I'll probs try to fix after the summer.
Codename13 said:
Yes, I say to use 2.6.3.0 as a universal recovery for our device. TWRP 2.6.3.0 works for both stock and custom ROMs, it doesn't enforce SELinux, so I say to use it. Plus, I've back ported some little changes from 2.7 to make it even better. Thank you for the praise, but it actually does have some bugs (mount USB storage) which I'll probs try to fix after the summer.
Click to expand...
Click to collapse
Im sorry i dont know much things about SELinux
As i see 2.7.0.0 Forces SELinux which i dont know what can be problem about it.
and 2.6.3.0 Mount Storage not working.
So im using 2.7.0.0 for my stock. Cause i need this function sometimes.
Sorry for noob question but what can be problem about Enforcing SELinux for 4.0.4
Edit:
Got it! : http://forum.xda-developers.com/showpost.php?p=52013947&postcount=5392
There's another bug with cwm 6. It shows a warning called warning:no file_contexts, as well as bootlooping into cwm again. This happens when you flash any rom, or restore to a nandroid backup. Please add this bug for future reference, as this can cause low experienced users to brick their devices.
s7560m said:
There's another bug with cwm 6. It shows a warning called warning:no file_contexts, as well as bootlooping into cwm again. This happens when you flash any rom, or restore to a nandroid backup. Please add this bug for future reference, as this can cause low experienced users to brick their devices.
Click to expand...
Click to collapse
So is it pretty much unusable? I never actually tested it and I didn't even create it, but a user had told me that it worked fine. I'll post a little warning for CWM6. Anyways, I think that TWRP 2.6.3.0 is the best custom recovery ATM. Of course, there are only 4 custom recoveries that have been built. I actually was going to return to porting some other custom recoveries to our device the other day. I want to port CWM6, Philz Touch, try out a few little hacks, and I want to implement internal storage into TWRP 2.7 just as it is in TWRP 2.6. Also, I think I'm going to try fixing the USB Mounting issue in TWRP 2.6. I know that 2.7 introduced a new, more universal way of handling UMS, so I'm going to see if I can backport it.
EDIT - It seems that there's also a new version of TWRP out. It seems to be quite minor, but I'll see if I can port it. It's been bumped up to version 2.7.1.0 now.
Codename13 said:
So is it pretty much unusable? I never actually tested it and I didn't even create it, but a user had told me that it worked fine. I'll post a little warning for CWM6. Anyways, I think that TWRP 2.6.3.0 is the best custom recovery ATM. Of course, there are only 4 custom recoveries that have been built. I actually was going to return to porting some other custom recoveries to our device the other day. I want to port CWM6, Philz Touch, try out a few little hacks, and I want to implement internal storage into TWRP 2.7 just as it is in TWRP 2.6. Also, I think I'm going to try fixing the USB Mounting issue in TWRP 2.6. I know that 2.7 introduced a new, more universal way of handling UMS, so I'm going to see if I can backport it.
Click to expand...
Click to collapse
Definitely twrp is the best! Never had any issues with it whatsoever, and has a great ui. If you could though, it would be awesome to try and port philz touch and cwm touch as well, just in case those who like cwm want that touch feature, or like the theme and features of philz touch . And I really hope the usb mounting issue can be fixed, as it can save so much time, rather than downloading to my computer, transferring to phone external storage, and then booting into recovery. Those who are lazy don't want to do all of that lol. Anyways, keep up all of the good work, and hopefully these bug fixes and new recoveries are implemented in future notice!
I was running rooted stock version of kit kat. Yesterday afternoon I had Google Music running while doing housework when suddenly the music stopped. I checked the phone and the screen was black and would not turn on. Pulled the battery and then it stuck at the AT&T logo for 30+ minutes. I booted into CWM to perform a factory reset and potentially reinstall the ROM from the external sd card. The factory reset produced the following error.
Code:
--Wiping Data ...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache
Formatting /sdcard/.android_secure...
Error mounting /sdcard/.android_secure!
Skipping format...
Data wipe complete
Fiddled around more with CWM to reset and try to fix. Now, upon reboot, it hands at the Samsung Galaxy Note II screen.
Any help on fixing this so it can at least limp along until my Nexus 6 gets here would be greatly appreciated.
Use Phil touch recovery, and use wipe\clean to install new ROM. Should fix your problem. Also if you are going to a Nexus 6 you should try CM11 when u flash a new ROM.
If you want to use CWM then just format the system and flash a new ROM.
Sent from my GT-N7105 using XDA Free mobile app
I'm unfamilair with Phil Touch recovery.
Can I flash it using JOding on OSX?
ShrekOpher said:
Use Phil touch recovery, and use wipe\clean to install new ROM. Should fix your problem. Also if you are going to a Nexus 6 you should try CM11 when u flash a new ROM.
If you want to use CWM then just format the system and flash a new ROM.
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
John.T.Erskine said:
I'm unfamilair with Phil Touch recovery.
Can I flash it using JOding on OSX?
Click to expand...
Click to collapse
You can check here
http://forum.xda-developers.com/showthread.php?t=2201860
Sent from my SHIELD Tablet using XDA Free mobile app
Odin doesn't recognize the device. It could be the browser version running on an old macbook pro, but I believe it is the fact that the phone's internal sd card is corrupted somehow.
John.T.Erskine said:
Odin doesn't recognize the device. It could be the browser version running on an old macbook pro, but I believe it is the fact that the phone's internal sd card is corrupted somehow.
Click to expand...
Click to collapse
Have you tried formating the data and system from cwm?
Go into recovery and go to "advanced" and select format system and/or format data.
Sent from my GT-N7105 using XDA Free mobile app
Tried that and received the same error as the OP. Can not mount SD card.
ShrekOpher said:
Have you tried formating the data and system from cwm?
Go into recovery and go to "advanced" and select format system and/or format data.
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
Same issue
I'm having the same issue as OP. The phone won't get back to recovery. Won't even go into download mode.......Please help!
Edit: I was so used to working on my wife's phone (Note 1) that I was using the wrong button combination for download mode. I still can't get back to recovery, but I'll be ok once I get home.
Try to flash stock rom in Odin. That should fix any errors but if you're still getting errors there's other stuff to try
absinthesummer said:
Try to flash stock rom in Odin. That should fix any errors but if you're still getting errors there's other stuff to try
Click to expand...
Click to collapse
Not the OP but I just tried this with KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user_low_ship.tar and it did not help.
Here's what I have done thus far:
1. Reflash the stock ROM from sammobile via ODIN
2. Ends in a FAIL on sboot.img
3. Phone says unsupported version (I believe this is due to the Knox locking. I can't downgrade)
4. Reflash recovery-clockwork-touch-6.0.4.3-t0lteatt.img using Heimdall
5. Wipe data, cache, and Dalvik cache (noting the errors regarding the /data partition still occur)
5. Sideload cm-11-20141008-SNAPSHOT-M11-t0lte.zip
6. Sideload gapps-kk-20140606-signed.zip
7. Reboot the phone
8. Stuck in a boot loop on the cyanogenmod logo
Thoughts on where to go from here? Tearing my hair out.
ProjektTHOR said:
Not the OP but I just tried this with KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user_low_ship.tar and it did not help.
Here's what I have done thus far:
1. Reflash the stock ROM from sammobile via ODIN
2. Ends in a FAIL on sboot.img
3. Phone says unsupported version (I believe this is due to the Knox locking. I can't downgrade)
4. Reflash recovery-clockwork-touch-6.0.4.3-t0lteatt.img using Heimdall
5. Wipe data, cache, and Dalvik cache (noting the errors regarding the /data partition still occur)
5. Sideload cm-11-20141008-SNAPSHOT-M11-t0lte.zip
6. Sideload gapps-kk-20140606-signed.zip
7. Reboot the phone
8. Stuck in a boot loop on the cyanogenmod logo
Thoughts on where to go from here? Tearing my hair out.
Click to expand...
Click to collapse
Yes that's definitely KNOX bootloader kicking back your flash attempts in odin. MA4 is pretty old firmware. You need MK6 or NE5. Here's where you can get the latest 4.3-4.4.2 firmwares: http://forum.xda-developers.com/galaxy-note-2-att/development/rom-att-i317-ucucne5-mj4-stock-odex-t2802189
This should correct the data issue, if not, you may need to grab a pit file, but usually flashing the latest stock fixes it without requiring all that.
Flash that, re-root, flash new recovery (note: use a newer recovery, cwm sometimes has issues with our device, but twrp has been updated to work with 4.3+ same with philz, if you prefer that UI. Once 4.4.4 comes out, it doesn't play well with cwm, philz, OR older versions of twrp- I had a fight with a note 3 and recoveries yesterday, finally got it going with the latest twrp).
Boot up the device, flash/update your supersu. If you want to install a different rom now, go ahead. Once you have a new recovery installed, format (manually) /system /data /internal storage /cache /dalvik. The internal storage is important b/c it's usually what causes the /data corruption. Always wipe internal storage when switching between roms (or even between an update, I do). I don't usually wipe everything 3 times like some people do, but it is important to wipe the essentials. In twrp, internal storage is an option when wiping. In cwm & philz, you have to go under mounts & storage & it's second up from the bottom (format /data including /data/media> sdcard). Then back out to the main recovery menu and flash your rom, if you have any issues reboot recovery (not system) and re-flash it.
One more thing, make sure you have enough system storage for the gapps. I've run into issues where the rom flashed fine but gapps was too big for the system and didn't flash correctly. Try a slim gapps
Hope this helps, if you have any other questions I'm happy to try to help. We'll get it fixed for ya
Not able to flash other ROMS besides Stock now.......
In my previous post, I was able to get to download mode and flashed back to stock. I thought I was flashing At&t Stock 4.3, but was really flashing At&t 4.1.2 Stock.
I guess it would help to state what happened and the order of things. I'm at work so I don't have the exact versions for each file used, but I'll try my best. I was running DN3 v3.1.1. Something was happening where there was very little space left on my internal storage and I felt like it was time to try a different Rom since I had been on this for a few months as a daily.
1. I flashed BlissStalk with no issues, just didn't care much for the Rom (no hate, just not my cup of tea!)
2. Next I flashed CyanideMod and didn't care for that either. No issues, just wasn't my cup of tea.
3. I then attempted to flash the DS NE5 Rom, using CWM, and it would come on and show the Samsung Galaxy Note II screen and then go black. I had to do a battery pull to get anywhere and then it would come back on and get back to the Galaxy Note II screen and freeze there, or cut off completely again. This is what brought me here to this thread.
I was able to go back to stock 4.1.2, then stock 4.3, and even now on stock 4.4.2. But now I can't flash any Rom at all without getting stuck. I tried to flash DN3's latest and keep getting stuck at the second Samung Screen. I have tried to reboot and tried to reflash as the help says. I am reading through various topics and FAQ pages, but I figured this may be more than any particular Rom issue (I've tried flashing other Roms and I'm getting stuck on those too-either stuck at logos or turning off completely). I have to keep flashing back to stock.
I am researching this, even while at work, but does anyone have any idea what could be wrong?
PS Even though I don't state it above, I followed all flashing directions to a T!
dirtyalphaman said:
In my previous post, I was able to get to download mode and flashed back to stock. I thought I was flashing At&t Stock 4.3, but was really flashing At&t 4.1.2 Stock.
I guess it would help to state what happened and the order of things. I'm at work so I don't have the exact versions for each file used, but I'll try my best. I was running DN3 v3.1.1. Something was happening where there was very little space left on my internal storage and I felt like it was time to try a different Rom since I had been on this for a few months as a daily.
1. I flashed BlissStalk with no issues, just didn't care much for the Rom (no hate, just not my cup of tea!)
2. Next I flashed CyanideMod and didn't care for that either. No issues, just wasn't my cup of tea.
3. I then attempted to flash the DS NE5 Rom, using CWM, and it would come on and show the Samsung Galaxy Note II screen and then go black. I had to do a battery pull to get anywhere and then it would come back on and get back to the Galaxy Note II screen and freeze there, or cut off completely again. This is what brought me here to this thread.
I was able to go back to stock 4.1.2, then stock 4.3, and even now on stock 4.4.2. But now I can't flash any Rom at all without getting stuck. I tried to flash DN3's latest and keep getting stuck at the second Samung Screen. I have tried to reboot and tried to reflash as the help says. I am reading through various topics and FAQ pages, but I figured this may be more than any particular Rom issue (I've tried flashing other Roms and I'm getting stuck on those too-either stuck at logos or turning off completely). I have to keep flashing back to stock.
I am researching this, even while at work, but does anyone have any idea what could be wrong?
PS Even though I don't state it above, I followed all flashing directions to a T!
Click to expand...
Click to collapse
Ok so you've got the ne5 bootloader, so any time you flash stock you'll have to flash that version or above. Stock rom works, but custom ones don't, correct?
What's weird is that the latest dn3 is a modified stock rom so that shouldn't be an issue.
When you flashed stock, you re-rooted and did you update super su? I'm sure you already know but you should update super su's binaries & let it disable Knox, which will set your seLinux from enforcing to permissive. That could potentially be a reason why you can't flash new roms, Knox & selinux interfering with the kernel flash part of the rom(s) you're trying. If you haven't done this you may want to try and then try flashing a custom rom again. If you still encounter issues I'll try to help.
---------- Post added at 12:32 PM ---------- Previous post was at 12:21 PM ----------
John.T.Erskine said:
I'm unfamilair with Phil Touch recovery.
Can I flash it using JOding on OSX?
Click to expand...
Click to collapse
Also, cwm is pretty old and prone to bugs on our devices. However philz is based on cwm and very similar in terms of user interface. It's not as different as twrp is. It has the same style and setup just a few additional tools that cwm doesn't have. It's also more compatible with our devices. If I had to choose one I wouldn't choose cwm, I'd go with philz or twrp for the sake of compatibility.
Thanks. I'll try this when I get home. Yea, once I flashed stock I kept getting Security Notices. I saw this was due to Knox and disabled it but that was a few flash attempts ago. I will follow you steps and let you know how it goes. Once again, thanks.
absinthesummer said:
Yes that's definitely KNOX bootloader kicking back your flash attempts in odin. MA4 is pretty old firmware. You need MK6 or NE5. Here's where you can get the latest 4.3-4.4.2 firmwares: http://forum.xda-developers.com/galaxy-note-2-att/development/rom-att-i317-ucucne5-mj4-stock-odex-t2802189
This should correct the data issue, if not, you may need to grab a pit file, but usually flashing the latest stock fixes it without requiring all that.
Click to expand...
Click to collapse
You are a saint. I'm not sure why I was struggling to find stock 4.4-series firmwares that could be flashed. I was so focused on getting them from sammobile or samware-firmware that I didn't even think to look here. I am going to try this process today and let you know if it works out!
absinthesummer said:
When you flashed stock, you re-rooted and did you update super su? I'm sure you already know but you should update super su's binaries & let it disable Knox, which will set your seLinux from enforcing to permissive. That could potentially be a reason why you can't flash new roms, Knox & selinux interfering with the kernel flash part of the rom(s) you're trying. If you haven't done this you may want to try and then try flashing a custom rom again. If you still encounter issues I'll try to help.
Click to expand...
Click to collapse
I really think this is my issue. I tried updating Super SU by flashing 1.75, but I think that's old. It doesn't show up and when I download it from the PLAY store, it says there is no SU Binary. It's too late to fiddle with this now, but I will mess around with it tomorrow. I think I lost my root and it's not trying to let me get it back. But I don't give up that easy. I was looking through the sticky thread to get the most up to date SU flash, but because it's late and I had a lot going on, this project will have to wait until tomorrow. Thanks for your help and I will let you know what happens tomorrow.
dirtyalphaman said:
I really think this is my issue. I tried updating Super SU by flashing 1.75, but I think that's old. It doesn't show up and when I download it from the PLAY store, it says there is no SU Binary. It's too late to fiddle with this now, but I will mess around with it tomorrow. I think I lost my root and it's not trying to let me get it back. But I don't give up that easy. I was looking through the sticky thread to get the most up to date SU flash, but because it's late and I had a lot going on, this project will have to wait until tomorrow. Thanks for your help and I will let you know what happens tomorrow.
Click to expand...
Click to collapse
Sounds like you've figured it out. 1.75 is very old. Latest (stable) is 2.16. There are also beta versions out. I can link you to the latest flashable in the morning.
You may want to re-root via cf auto root if you can't get it to flash, but if you've got access to recovery a flash to the latest supersu should take... it's just not with 1.75 because those binaries are so outdated, it likely can't overpower enforcing selinux. That has been resolved in newer versions. I'm almost positive you'll be fine with a newer supersu/root.
Edit:
here's the link to 2.16 zip download: http://download.chainfire.eu/589/SuperSU/UPDATE-SuperSU-v2.16.zip
And here's a link to chainfire's thread so you can bookmark it & always have access to the latest:
http://forum.xda-developers.com/showthread.php?t=1538053
absinthesummer said:
Sounds like you've figured it out. 1.75 is very old. Latest (stable) is 2.16. There are also beta versions out. I can link you to the latest flashable in the morning.
You may want to re-root via cf auto root if you can't get it to flash, but if you've got access to recovery a flash to the latest supersu should take... it's just not with 1.75 because those binaries are so outdated, it likely can't overpower enforcing selinux. That has been resolved in newer versions. I'm almost positive you'll be fine with a newer supersu/root.
Edit:
here's the link to 2.16 zip download: http://download.chainfire.eu/589/SuperSU/UPDATE-SuperSU-v2.16.zip
And here's a link to chainfire's thread so you can bookmark it & always have access to the latest:
http://forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
Hey, this worked for my root. I installed and updated the SU Binary. It got stuck trying to disable Knox, but I rebooted and went right back to it--Knox was disabled in a few seconds! Thanks again. I will wait until I get home to try to flash again because I would hate to end up stuck at work without my phone working and also because..........my name.......my name is Ken. And I.......I'm a flashaholic...........
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dirtyalphaman said:
Hey, this worked for my root. I installed and updated the SU Binary. It got stuck trying to disable Knox, but I rebooted and went right back to it--Knox was disabled in a few seconds! Thanks again. I will wait until I get home to try to flash again because I would hate to end up stuck at work without my phone working and also because..........my name.......my name is Ken. And I.......I'm a flashaholic...........
Click to expand...
Click to collapse
Awesome! Good luck (and I think we're all flash-aholics)
Thank you for all of your help!!! Flashed the latest DN5 rom and it's working great. I found an issue that might have been preventing me from flashing earlier besides the botched root. My external sd card is having a few issues. A week or so ago it changed to read only and wouldn't let me move any files to or from it. Tonight it wouldn't let me flash the rom, but it worked when moved the rom to the internal storage. So I'm good to go! Can't thank you enough!
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app