Database Develop

Is Galaxy S advance supported with Rom Manager? If Not, other ways to change ROMs?

Hello,
I have recently purchased a Galaxy S Advance phone, and I am quite new to the android os.
I have read already many guides and forums about the whole process of rooting / flashing etc, so I have some knowledge of the terminology.
I already have a rooted phone with GB on it (yes, I know JB is about to come out officially ) and I wanted to change some of the UI elements.
I installed the rom manager app by koush, but yet to use it because I saw that in the past that the phone wasn't supported.
My question is: Does ROM Manager support this phone? Can I go ahead and flash CWM on it from the rom manager app, and then use it to flash other roms?
If not, which is the best solution to backup and replace roms? ODIN?
Thanks,

Одг: Is Galaxy S advance supported with Rom Manager? If Not, other ways to change ROM
YMatrix said:
Hello,
I have recently purchased a Galaxy S Advance phone, and I am quite new to the android os.
I have read already many guides and forums about the whole process of rooting / flashing etc, so I have some knowledge of the terminology.
I already have a rooted phone with GB on it (yes, I know JB is about to come out officially ) and I wanted to change some of the UI elements.
I installed the rom manager app by koush, but yet to use it because I saw that in the past that the phone wasn't supported.
My question is: Does ROM Manager support this phone? Can I go ahead and flash CWM on it from the rom manager app, and then use it to flash other roms?
If not, which is the best solution to backup and replace roms? ODIN?
Thanks,
Click to expand...
Click to collapse
Other way to change roms is custom recovery. On GB TWRP, on JB CWM.
Sent from Galaxy S Advance

Thanks fro your quick reply!
And what about ROM Manager? Does it work in this device?

YMatrix said:
Thanks fro your quick reply!
And what about ROM Manager? Does it work in this device?
Click to expand...
Click to collapse
I think it is not working. It is not supported. Way we install custom ROMs: download ROM zip, transfer to SD, then go to recovery and install it from there.

I checked TWRP supported devices list (tried to link it but forum wont allow new users to link ) and I don't see the galaxy advance S on their list either.
Is there a special mod version for this device?
And another question, if installed, will this wipe the current phone data or just the recovery loader? Since I want to backup my current ROM (+ contacts, settings etc.) before doing anything sketchy...

YMatrix said:
I checked TWRP supported devices list (tried to link it but forum wont allow new users to link ) and I don't see the galaxy advance S on their list either.
Is there a special mod version for this device?
And another question, if installed, will this wipe the current phone data or just the recovery loader? Since I want to backup my current ROM (+ contacts, settings etc.) before doing anything sketchy...
Click to expand...
Click to collapse
You have GB? Look here.
On I9070 recovery is on the same partition as kernel. So it can't be installed separatly. It is ported. You need to install this kernel, or CoCore. If you install with Odin - you will increase binary counter. For installation with ADB shell, or Terminal emulator (app from market) you need root - and it will not increase bc.

So I am guessing I will use the dd command line way since it doesn't increase the binary counter (why would we want to do that ).
Is it possible to backup the current ROM before flashing it with the TWRP modified ROM?
And another thing, since I will be using other ROMs, how can i add the TWRP recovery loader to them (you said that the recovery is on the same partition as the kernel, making me believe that each ROM I load will need to have TWRP on it)?

YMatrix said:
So I am guessing I will use the dd command line way since it doesn't increase the binary counter (why would we want to do that ).
Is it possible to backup the current ROM before flashing it with the TWRP modified ROM?
And another thing, since I will be using other ROMs, how can i add the TWRP recovery loader to them (you said that the recovery is on the same partition as the kernel, making me believe that each ROM I load will need to have TWRP on it)?
Click to expand...
Click to collapse
No, only JetMOD have embendend kernel too. And it have TWRP.
Hm, another thing. You better use non binary counter increaing root method. But it need you to flash whole firmware with Odin. And maybe you loose data. But if you do not do factory reset - it will be ok.

Sorry, I didn't understand your last post.

YMatrix said:
Sorry, I didn't understand your last post.
Click to expand...
Click to collapse
If you want to get TWRP with dd command you need to root your phone first.
There are 2 root methods. One that increase binary counter, and one that do not..
With one that do not increase - you need to flash whole firmware with Odin. And by doing that you might need to do factory reset. That will cause your data and app delete. You can try to boot, maybe it will be ok.

Oh, I already said I have a rooted device, so this wont be an issue.
What I asked was:
1) If I can backup my current ROM before installing the TWRP ROM you linked (in case something goes wrong).
2) When I install other modified ROMs, will they override the TWRP I installed, or just change the kernel system leaving TWRP in the recovery?

Одг: Is Galaxy S advance supported with Rom Manager? If Not, other ways to change ROM
YMatrix said:
Oh, I already said I have a rooted device, so this wont be an issue.
What I asked was:
1) If I can backup my current ROM before installing the TWRP ROM you linked (in case something goes wrong).
2) When I install other modified ROMs, will they override the TWRP I installed, or just change the kernel system leaving TWRP in the recovery?
Click to expand...
Click to collapse
Didn't pay attention.
You have backup option in TWRP, and you can restore it.
Custom roms do not have connection with kernel, just JetMod who do have kernel with TWRP too.
P.S. lol you confuse me. TWRP is kernel related, nothing to do with ROM.
When you want stock kernel back, just flash your firmware from sammobile.com.
So you need to change kernel to get TWRP. And with TWRP you do backup of system.
Sent from Galaxy S Advance

Bos manForu
Hmmmm, now I am a little confused.
Since I don't want to touch the kernel (yet), all I want to do is change the ROM (as in UI changes etc...).
I wanted to backup my current ROM and then load other ROMS.
I started off with ROM Manager because it seemed to answer what I wanted to do, but as you said ROM Manager doesn't support this phone and we went from there to TWRP.
Since I now get that TWRP is kernel related only and not ROM management, what would you advise right now for:
1) Backing up the current ROM
2) Loading other ROMs to the device?

YMatrix said:
Hmmmm, now I am a little confused.
Since I don't want to touch the kernel (yet), all I want to do is change the ROM (as in UI changes etc...).
I wanted to backup my current ROM and then load other ROMS.
I started off with ROM Manager because it seemed to answer what I wanted to do, but as you said ROM Manager doesn't support this phone and we went from there to TWRP.
Since I now get that TWRP is kernel related only and not ROM management, what would you advise right now for:
1) Backing up the current ROM
2) Loading other ROMs to the device?
Click to expand...
Click to collapse
You can do that only with TWRP.
And did you read ROM manager description?
* Flash your recovery to the latest and greatest ClockworkMod recovery.
Click to expand...
Click to collapse
For ROM manager you need custom recovery. And for I9070 that is embended in kernel. Full stop.
And it is connected to CWM, not to TWRP. We do not have CWM for Android 2.3.6. ported.
P.S. So to close this:
- You can't do any backup, installation of ROMs without custom recovery (in our case TWRP) on our phone.
- Custom recovery couldn't be installed separatly - it is embended inside kernel file - and has nothing to do with ROM.
It is clear now?

I think I got you now
1) CWM doesn't work on my phone because the recovery is attached to the kernel.
2) In order for me to backup my ROM I need to install the kernel with TWRP embedded (the one you linked me).
3) I also can't backup my current kernel without TWRP so in order for me to have TWRP I will be doing #2 without any backup? I am guessing this is the part where bricking has a chance of occurrence?

YMatrix said:
I think I got you now
1) CWM doesn't work on my phone because the recovery is attached to the kernel.
2) In order for me to backup my ROM I need to install the kernel with TWRP embedded (the one you linked me).
3) I also can't backup my current kernel without TWRP so in order for me to have TWRP I will be doing #2 without any backup? I am guessing this is the part where bricking has a chance of occurrence?
Click to expand...
Click to collapse
CWM = TWRP
Both are custom recoveryes. Not the same, but same purpose.
1) Our phone have same partition for kernel and recovery. So we can't install it separatly
2) You can backup kernel, but you will need Terminal emulator, and similiar command like instalation of other kernel
Code:
$ su
# dd if=/dev/block/mmcblk0p15 of=/sdcard/boot.bin
# reboot
This will backup your stock kernel on your sdcard. You can install it later this way (ofcourse if boot.bin file is on your sd)
Code:
$ su
# dd if=/sdcard/boot.bin of=/dev/block/mmcblk0p15
# reboot
You always can flash your stock kernel, Download mode do not have anything to do with kernel and recovery partition.
If this is little hard for you, just install custom kernel with TWRP. Or do not do anything. :laugh:
P.S. Trust me, you can't hard brick device with installing kernel. I am tester, and I flashed at least 10 non booting kernels, and 50+ booting ones.

I do trust you, just trying to get an understanding of how the things work on these devices.
So I now understand the backing up and flashing commands (I would like to know how you knew the mmcblk0p15 was the kernel partition for this phone), so where does the "Download mode" come in handy if u can flash directly from a terminal window?
If for some reason the flash wasn't successful, can you enter download mode and restore the backup you created?

YMatrix said:
I do trust you, just trying to get an understanding of how the things work on these devices.
So I now understand the backing up and flashing commands (I would like to know how you knew the mmcblk0p15 was the kernel partition for this phone), so where does the "Download mode" come in handy if u can flash directly from a terminal window?
If for some reason the flash wasn't successful, can you enter download mode and restore the backup you created?
Click to expand...
Click to collapse
Most likely you will have to flash whole firmware if something goes wrong. I told you what I know.
And if you can go in TWRP recovery, it can restore krenel with other things you backed up. And you can flash new kernel in TWRP too.
Somewhere is written what partition is for what. I do not know that. And developers told us what partition is for kernel and recovery.
I do not think that that thing with restoring downlaod mode will work. Newer tried or heard of it.
I tried to explain you, but maybe I was little confusing. :angel: My english is not great, and I didn't provide 1, 2, 3... steps explanation. Like I throw everything to you. :laugh::laugh::laugh:

:laugh: More or less I understand you :laugh:
So to sum up:
1) Create a backup of the current kernel
2) Flash Stock Kernel + TWRP
if all goes well....
3) Create full phone phone backup from TWRP
4) flash custom ROMs (or kernels) with TWRP
Hows that?

YMatrix said:
:laugh: More or less I understand you :laugh:
So to sum up:
1) Create a backup of the current kernel
2) Flash Stock Kernel + TWRP
if all goes well....
3) Create full phone phone backup from TWRP
4) flash custom ROMs (or kernels) with TWRP
Hows that?
Click to expand...
Click to collapse
That is ok.
And you backup old kernel that you can easy go back to stock one. Without flashing whole firmware, when you want stock. Like you want to go to service for warranty or something like that...

[Resolved] Need Help flashing stock rom to GT-N7000

Hi, I want to install AllianceRom on my Samsung Galaxy Note GT-N7000. I bought the phone used with Paranoid Android installed. I have read many threads, but have questions unanswered:
1) The first line in the AllianceRom install guide says don't ignore checking the checksum, just do it", but doesn't say how to check it.
2) The guide says to flash back to a stock rom first to avoid bricking, but the list on this site of all stock roms for the GT-N7000 has many different roms with many different dates and many different regions, and none for my region (Canada). I need to know which rom to flash before following the AllianceRom install guide.
The following information was acquired from settings/about phone. If any more info is needed, please let me know and I will post it.
Kernel Version:
3.0.15-CM-gda8f1e2-dirty
[email protected] #1
Sun Oct 7 19:52:13 ADT 2012
Cyanogenmod Version:
10.0.0-RC0-n7000
Paranoid Android Version:
2.52-Utacka
Build Date:
lör 3 nov+ 2012 02.23.+42 CET
Build Number:
pa_n7000-userdebug 4.1.2 JZO54K eng.utacka.20121103.022323 test-keys
Thanks in advance for any help, it is greatly appreciated.

1. It's checked using md5 checker. Download it from the Internet and run on pc. Then choose the downloaded zip in the tool. It will show a code. Match it with what's provided by the rom Dev.
2. As pa has a safe kernel, you do not need to go back to stock rom. Just format that system, data cache and preload partitions in Cwm and then flash the rom.
Sent from my GT-I9500 using xda premium

nokiamodeln91 said:
1. It's checked using md5 checker. Download it from the Internet and run on pc. Then choose the downloaded zip in the tool. It will show a code. Match it with what's provided by the rom Dev.
2. As pa has a safe kernel, you do not need to go back to stock rom. Just format that system, data cache and preload partitions in Cwm and then flash the rom.
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
Glad to hear I can skip the stock rom. I am a noob though, at least when it comes to phones, so I'm still not sure exactly what to do. If you could hold my hand just a little... I have downloaded the appropriate AllianceRom for my phone, do I need to verify it with md5 checker, and if so, where do I get the checksum to match? By format that system, data cache and preload partitions I assume you're referring to 3 different options in the Mounts and Storage menu in cwm recovery. If that is correct, then I just do those 3 things in that order, then I can flash the AllianceRom? Thanks again.

Dreams of Sanity said:
Glad to hear I can skip the stock rom. I am a noob though, at least when it comes to phones, so I'm still not sure exactly what to do. If you could hold my hand just a little... I have downloaded the appropriate AllianceRom for my phone, do I need to verify it with md5 checker, and if so, where do I get the checksum to match? By format that system, data cache and preload partitions I assume you're referring to 3 different options in the Mounts and Storage menu in cwm recovery. If that is correct, then I just do those 3 things in that order, then I can flash the AllianceRom? Thanks again.
Click to expand...
Click to collapse
again to check md5 :
http://lmgtfy.com/?q=md5+check
Put downloaded zip on external sd card
and yes under mounts and storage wipe /data /system /cache /dalvik
once wiped, go to install from zip and choose the file and flash

AllianceRom dev recommend to flash using rom customizer so that u can choose between stock or aosp theme and also choose the wipe options.
Flashing via cwm or twrp after the 3 wipes also works(but freezing sometimes) & u might get aosp theme by default. So if u want stock theme then reflash again from the new rom where it has rom customizer included. A lot of people were having installation freezing issue as well during installation thru rom customizer so u may need to reflash it several times. Good luck

[resolved] Need help flashing stock rom to GT-N7000
Done with no problems, thanks to all of you for your help.

[Q] Unable to start WiFi after flashing CWM 6.0.2.8 and 6.0.3.1 on custom JB ROM

Hello All,
I am on stock v4.1.2, flashed myself.
Now I want to move on to custom ROM.
My current stock ROM is rooted, and I have also unlocked my bootloader.
Now when I want to install custom ROM, I need to flash CWM, and when I do (tried v6.2.8 and v6.0.3.1), and install any ROM, my WiFi becomes unresponsive (failed to turn on). When I flash V20A back, everything turns normal.
I also gone through http://forum.xda-developers.com/showthread.php?t=2180138&page=43, and install the unsecure boot image after installing CWM 6028, but this make my custom rom hang on startup (on bootload screen).
Kindly help me out.
I have search a lot in the P880 forum, and didn't find any help regarding to this problem.

[email protected] said:
Hello All,
I am on stock v4.1.2, flashed myself.
Now I want to move on to custom ROM.
My current stock ROM is rooted, and I have also unlocked my bootloader.
Now when I want to install custom ROM, I need to flash CWM, and when I do (tried v6.2.8 and v6.0.3.1), and install any ROM, my WiFi becomes unresponsive (failed to turn on). When I flash V20A back, everything turns normal.
I also gone through http://forum.xda-developers.com/showthread.php?t=2180138&page=43, and install the unsecure boot image after installing CWM 6028, but this make my custom rom hang on startup (on bootload screen).
Kindly help me out.
I have search a lot in the P880 forum, and didn't find any help regarding to this problem.
Click to expand...
Click to collapse
i dont understand what the recovery has to do with the wifi. recovery is just an interface to easy install something, copy paste , edit , change permissions , etc , things we do using adb commands. it is just an environment. its something else u are doing wrong there.
<EDIT> yea i saw the thread on your link. others seem to have same problem but with the unsecure boot. why do u need unsecure boot if the bootloader is unlocked ? just install teamwin recovery or cwm recovery and the rom u want.

kessaras said:
i dont understand what the recovery has to do with the wifi. recovery is just an interface to easy install something, copy paste , edit , change permissions , etc , things we do using adb commands. it is just an environment. its something else u are doing wrong there.
<EDIT> yea i saw the thread on your link. others seem to have same problem but with the unsecure boot. why do u need unsecure boot if the bootloader is unlocked ? just install teamwin recovery or cwm recovery and the rom u want.
Click to expand...
Click to collapse
Well, I did. And it all went fine, and I am able to install various custom ROMs, and after I install custom ROM, my WiFi becomes unresponsive. I am completely at lost. I also tried MIUI v5 which is non-CM10.2 based, and it also showed the same issue.
Here are my steps to install a custom ROM.
- Currently I am on my V20A stock ROM.
- Root the stock ROM using the All-In-One-Toolkit v1.4.1
- Flush the CWM 6031 using ADB as
Code:
su
cat /mnt/sdcard/recovery.img > /dev/block/mmcblk0p1
sync
- After reboot, my device has the CWM.
- Copy custom ROM zip files to my device, and reboot to recovery
- Wipe out by data and cache
- Install ROM
thats it
And when I boot into the new custom ROM, my WiFi do not work.
Please help.

[email protected] said:
Well, I did. And it all went fine, and I am able to install various custom ROMs, and after I install custom ROM, my WiFi becomes unresponsive. I am completely at lost. I also tried MIUI v5 which is non-CM10.2 based, and it also showed the same issue.
Here are my steps to install a custom ROM.
- Currently I am on my V20A stock ROM.
- Root the stock ROM using the All-In-One-Toolkit v1.4.1
- Flush the CWM 6031 using ADB as
Code:
su
cat /mnt/sdcard/recovery.img > /dev/block/mmcblk0p1
sync
- After reboot, my device has the CWM.
- Copy custom ROM zip files to my device, and reboot to recovery
- Wipe out by data and cache
- Install ROM
thats it
And when I boot into the new custom ROM, my WiFi do not work.
Please help.
Click to expand...
Click to collapse
not exactly.
And here are my steps to install a custom ROM (if currently I am on my V20A stock ROM)
1. Root the stock ROM using the All-In-One-Toolkit v1.4.1
2. Unlock bootloader using All-In-One-Toolkit v1.4.1 or manually like this.
3. Flash the CWM 6.0.4.5 or 6.0.4.4 or TeamWin Recovery
4. Reboot the device in recovery.
5. Enter ADB sideload and install custom rom or using ADB bootloader or using ADB copy the rom in sd card and use install in recovery.
6. Wipe data and cache and reboot system.
<<STEPS DESCRIBED IN HELP SECTION - FREQUENTLY ASKED QUESTIONS>> ( by the way those must be updated too )

kessaras said:
not exactly.
And here are my steps to install a custom ROM (if currently I am on my V20A stock ROM)
1. Root the stock ROM using the All-In-One-Toolkit v1.4.1
2. Unlock bootloader using All-In-One-Toolkit v1.4.1 or manually like this.
3. Flash the CWM 6.0.4.5 or 6.0.4.4 or TeamWin Recovery
4. Reboot the device in recovery.
5. Enter ADB sideload and install custom rom or using ADB bootloader or using ADB copy the rom in sd card and use install in recovery.
6. Wipe data and cache and reboot system.
<<STEPS DESCRIBED IN HELP SECTION - FREQUENTLY ASKED QUESTIONS>> ( by the way those must be updated too )
Click to expand...
Click to collapse
I did wipe the data and cache after installing the custom ROM. But the result is the same; No WiFi response.
However, I always copy my custom ROMs by mounting my phone through USB to my Win8 laptop, and then copy the ROM file through windows explorer. And then install the ROM from the CWN recovery. Thus do not use ADB for copying files, or installing custom ROM as mentioned above. If this is the main issue reason, then advice.
Also I haven't tried TWRP till yet. Will do now. Till then, what else I can do.
Thanks for the quick replies.

i dont know what else you may doing wrong then. one was the insecure boot which is useless since u have unlocked the bootloader and the other that u had flash older version of cwm recovery. maybe compatibility issue with that version of cwm rec ? test and see.

format system also, when installing a new rom, not just data, cache & dalvik

kessaras said:
i dont know what else you may doing wrong then. one was the insecure boot which is useless since u have unlocked the bootloader and the other that u had flash older version of cwm recovery. maybe compatibility issue with that version of cwm rec ? test and see.
Click to expand...
Click to collapse
One piece of detail I missed to mentioned in my case previously was that, I unlocked my phone using the method mentioned in the thread http://forum.xda-developers.com/showthread.php?t=2263627 as I was unable to unlock using the official method.
After I unlock my bootloader, I have flashed V20A KDZ several times, and each time the SW Upd mode show me that my bootloader status is unlocked. Thus after first attempt of unlocking, I never came across need to unlocked my bootloader again as each time when I do the KDZ flash, I get the bootloader status as unlocked. And after each flash of KDZ, I was able to install CWM and custom ROMs, and boot into them successfully.
Is this something causing the issue?

[email protected] said:
One piece of detail I missed to mentioned in my case previously was that, I unlocked my phone using the method mentioned in the thread http://forum.xda-developers.com/showthread.php?t=2263627 as I was unable to unlock using the official method.
After I unlock my bootloader, I have flashed V20A KDZ several times, and each time the SW Upd mode show me that my bootloader status is unlocked. Thus after first attempt of unlocking, I never came across need to unlocked my bootloader again as each time when I do the KDZ flash, I get the bootloader status as unlocked. And after each flash of KDZ, I was able to install CWM and custom ROMs, and boot into them successfully.
Is this something causing the issue?
Click to expand...
Click to collapse
Now, I have repeated using CWM 6.0.4.5 and TWRP, and no breakthrough .... Starting to lose hope ... Help !!!

sorry , personally i dont know what else u may doing wrong there . and no it doesnt matter which way u unlock the phone, but since u unlock it , it stays that way until u lock it.
at least stock rom is working fine ? if that works fine there, then just install only custom kernel, do your tweaks, install another launcher and then delete the default, etc. u can do any modification u like to the stock one to make it look and work the way u want it.

kessaras said:
sorry , personally i dont know what else u may doing wrong there . and no it doesnt matter which way u unlock the phone, but since u unlock it , it stays that way until u lock it.
at least stock rom is working fine ? if that works fine there, then just install only custom kernel, do your tweaks, install another launcher and then delete the default, etc. u can do any modification u like to the stock one to make it look and work the way u want it.
Click to expand...
Click to collapse
Does it help if I installed a custom kernel on my custom ROM (with WiFi issue). My understanding is that the WiFi driver is compiled inside the kernel. So changing the kernel might reduce the issue. What do you think? If yes, then kindly advice me on which kernel should I install on my till now custom ROM MIUI v5 http://en.miui.com/download-79.html.

[email protected] said:
Does it help if I installed a custom kernel on my custom ROM (with WiFi issue). My understanding is that the WiFi driver is compiled inside the kernel. So changing the kernel might reduce the issue. What do you think? If yes, then kindly advice me on which kernel should I install on my till now custom ROM MIUI v5 http://en.miui.com/download-79.html.
Click to expand...
Click to collapse
a developer would never release a rom in public with wifi issues by default and since i have already tested all roms available before i end up to one, i can say that they all worked , but only had small bugs on homescreen. really i dont know what you are doing wrong and not even a teamviewer connection wouldnt help in this case. but on stock your phone works fine ? only in a custom rom u have this issue ?
<<EDIT>> did you also do a full format before going to another rom ? there is a choice in teamwin recovery ( dont know if its in cwm also ) to format data. careful i dont mean to wipe everything you see because you will remove the recovery too and u will have to flash it back. the format option deletes everything besides the recovery. if you dont format before you go to a totally different rom, then you maybe have issues. especially when going from stock to custom, differences are huge. you must format before flashing. and dont forget the gapps, if they are not inluded in rom. ( in your case miui there must have them inside, because i see its 256 mb+)

kessaras said:
a developer would never release a rom in public with wifi issues by default and since i have already tested all roms available before i end up to one, i can say that they all worked , but only had small bugs on homescreen. really i dont know what you are doing wrong and not even a teamviewer connection wouldnt help in this case. but on stock your phone works fine ? only in a custom rom u have this issue ?
<<EDIT>> did you also do a full format before going to another rom ? there is a choice in teamwin recovery ( dont know if its in cwm also ) to format data. careful i dont mean to wipe everything you see because you will remove the recovery too and u will have to flash it back. the format option deletes everything besides the recovery. if you dont format before you go to a totally different rom, then you maybe have issues. especially when going from stock to custom, differences are huge. you must format before flashing. and dont forget the gapps, if they are not inluded in rom. ( in your case miui there must have them inside, because i see its 256 mb+)
Click to expand...
Click to collapse
YES. When I flashed stock V20A, I never had issues with Wifi. Its when I install custom ROM, and any custom ROM.
So I suppose, either there is something wrong in my installing method, or in my stock ROM that won't allow WiFi to work on any custom ROM. But how much influential will be the stock ROM if it is being replaced by a custom ROM?
Well, I haven't formated before I install any custom ROM, as it was not instructed in the forums. But I will do that now, and let you know the results shortly.
Thanks again for the replies.

[email protected] said:
Well, I haven't formated before I install any custom ROM, as it was not instructed in the forums.
Click to expand...
Click to collapse
yea some informations are always missing from the instructions generally , but this is a developer forum , so it doesnt always include informations that are 100% well known to be done. So format and install again and tell me if its everything ok.

kessaras said:
yea some informations are always missing from the instructions generally , but this is a developer forum , so it doesnt always include informations that are 100% well known to be done. So format and install again and tell me if its everything ok.
Click to expand...
Click to collapse
Can you direct me how to install a custom ROM using ADB? Since when I format my /data, all of my custom roms that I copied will get deleted. So the only remaining option is to copy them using ADB.

[email protected] said:
Can you direct me how to install a custom ROM using ADB? Since when I format my /data, all of my custom roms that I copied will get deleted. So the only remaining option is to copy them using ADB.
Click to expand...
Click to collapse
What?????
Why would wiping your /data folder on internal storage delete your custom ROMs? Surely you keep them on your external SD-Card?

[email protected] said:
Can you direct me how to install a custom ROM using ADB? Since when I format my /data, all of my custom roms that I copied will get deleted. So the only remaining option is to copy them using ADB.
Click to expand...
Click to collapse
you dont need to copy it . u can open adb sideload from recovery and on pc use command : adb sideload [path/filename of rom.zip]

SimonTS said:
What?????
Why would wiping your /data folder on internal storage delete your custom ROMs? Surely you keep them on your external SD-Card?
Click to expand...
Click to collapse
So you are saying that, I copy them to external_sd, and then do the data format. Ok ... Will do and let you know.
BTW, I also found V20B. I will start with this stock rom instead of V20A. This might improves some thing.

[email protected] said:
So you are saying that, I copy them to external_sd, and then do the data format. Ok ... Will do and let you know.
BTW, I also found V20B. I will start with this stock rom instead of V20A. This might improves some thing.
Click to expand...
Click to collapse
AT LAST .... FIXED ...
I did two things, V20B, and format /system, /data before installing new ROM. So my steps were:
1) Flush V20B instead of V20A
2) After rooting, and installed CWM 6044 touch, copy custom ROM MIUI to external SDCARD
3) Reboot into recovery, and format /system, /data, and /cache partitions
4) Install custom ROM from external SDCARD
5) Wipe data and cache
6) Reboot into the new world

:good: formatting did the work sorry i didnt think of it earlier.

[Q&A] [RECOVERY][GUIDE][i9305]--CWM/PHILZ/TWRP latest versions+Odin v3.09 Guide--14-

[Q&A] [RECOVERY][GUIDE][i9305]--CWM/PHILZ/TWRP latest versions+Odin v3.09 Guide--14-
Q&A for [RECOVERY][GUIDE][i9305]--CWM/PHILZ/TWRP latest versions+Odin v3.09 Guide--14-07-2014
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][GUIDE][i9305]--CWM/PHILZ/TWRP latest versions+Odin v3.09 Guide--14-07-2014. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

someone could build a philz recovery from the latest source with F2FS support for i9305?

Just informing you TWRP is updated to a 2.8.5.0 version for i9305 since one week: http://techerrata.com/browse/twrp2/i9305

TWRP 2.8.5.0
Hello,
TWRP 2.8.5.0 is f2fs it or not ?
Best Regards

working thanks for this

Finally.
After searching for almost 3 days (almost straight, you know school was between it) I finally found this thread.
I´ve followed all the steps, and FINALLY that whole rooting stuff worked.
Previously I tried some YouTube Tutorials, and yes, the SuperSU showed up, but wasn´t openable nor usable nor updatable and worst of all NOT removable.
But This "Noob friendly" Guide really helped me out.
I can´t say thank you often enough.
So... THANK YOU, MATE.
P.S.: I´ve only made an account to thank you for your great work. Once again, Thank you.

Today build didn't work for me, stuck on Samsung logo
Sent from my GT-I9305 using Tapatalk

TWRP 2.8.7.0 for i9305?
The new version of TWRP 2.8.7.0 for i9305 has been up on the official TWRP site for weeks but it still seems to be corrupted (causing bootloops)? Where can I verify that a proper version has been uploaded? I know that there's a thread on i9305 development trying to make a stable version but who are behind these version released on official TWRP site and shouldn't they be doing the stable version?

Kaedin said:
The new version of TWRP 2.8.7.0 for i9305 has been up on the official TWRP site for weeks but it still seems to be corrupted (causing bootloops)? Where can I verify that a proper version has been uploaded? I know that there's a thread on i9305 development trying to make a stable version but who are behind these version released on official TWRP site and shouldn't they be doing the stable version?
Click to expand...
Click to collapse
the version in development thread is by me and works fine now
twrp builds the recoverys via jenkins and upload them... as for now they use a old tree for your device and thats why the broken build exists (no ome tests those builds)
the problem is you dont have any official maitainer .... so nobody takes care of your twrp builds....
i am not allowed to upload a stable build ... only a DEV that OWNS i9305 can do it (dont must be recognized dev but must proof some skill)
Sent from my Xperia T using XDA Free mobile app

SdtBarbarossa said:
the version in development thread is by me and works fine now
twrp builds the recoverys via jenkins and upload them... as for now they use a old tree for your device and thats why the broken build exists (no ome tests those builds)
the problem is you dont have any official maitainer .... so nobody takes care of your twrp builds....
i am not allowed to upload a stable build ... only a DEV that OWNS i9305 can do it (dont must be recognized dev but must proof some skill)
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for your fast reply and it is really nice to see you giving such an effort to bring this latest TWRP working on i9305! I wish I could have dug this info out before I had flashed the recovery version from the official site as I had to go stock to get my device working again (well, better than a bricked device though)!
So the Alpha 17 is fully working at the moment? Could we get a download link placed at the main post if possible? Awesome work, man!

Sir I lost my root and recovery how to fix?

shan482 said:
Sir I lost my root and recovery how to fix?
Click to expand...
Click to collapse
You can:
1. Follow the guide for the rooting process in ODIN with CF Auto root and also the custom recovery flashing.
OR
2. Flash just the custom recovery of your choice and then install a pre-rooted custom rom using the recovery you have flashed.
Both ways you will have custom recovery and root again

philz full wipe not working :crying:
plz help~~~ I flash the recovery from 4.3 stock, and then flash the rom
http://forum.xda-developers.com/galaxy-s3/development-i9305/rom-4-4-4-t3026347
I did a full wipe and then install the ROM, the rom can be flashed and run successfully.
But I found all data, including files from internal SD card such as whatsapp data and camera still exist (not wiped)
Then I search the threads and found there is a knox bootloader at stock 4.3 which is not a good thing
After using the rom for 2 days, I notices the touchwiz always FC, and the device always reboot
I wonder if the full wipe is not working well so that I am having some issues with the new ROM...
anyone could suggest me how to do a complete full wipe? Also if possible how to remove the knox bootloader? Thanks!

Jeorainc said:
plz help~~~ I flash the recovery from 4.3 stock, and then flash the rom
http://forum.xda-developers.com/galaxy-s3/development-i9305/rom-4-4-4-t3026347
I did a full wipe and then install the ROM, the rom can be flashed and run successfully.
But I found all data, including files from internal SD card such as whatsapp data and camera still exist (not wiped)
Then I search the threads and found there is a knox bootloader at stock 4.3 which is not a good thing
After using the rom for 2 days, I notices the touchwiz always FC, and the device always reboot
I wonder if the full wipe is not working well so that I am having some issues with the new ROM...
anyone could suggest me how to do a complete full wipe? Also if possible how to remove the knox bootloader? Thanks!
Click to expand...
Click to collapse
You should flash Android 5.1 for i9305.
The difference in speed, battery usage & user friendliness is massive.... It gives our device a new lease of life..
Get rid of 4.4. Install the latest Philz Recovery & KNOX is a problem you can solve. Search Google....
Flash cm12.1 for i9305 & install the gapps aroma package so you can choose exactly which Google apps you want in your system.
I use winxuser version of CyanogenMod 12.1. (Android 5.1.1)
Btw the devs are currently adapting Android 6.0 dor i9305 & it looks like it will work in a few weeks...
Sent with Tapatalk

Pe1ican0 said:
You should flash Android 5.1 for i9305.
The difference in speed, battery usage & user friendliness is massive.... It gives our device a new lease of life..
Get rid of 4.4. Install the latest Philz Recovery & KNOX is a problem you can solve. Search Google....
Flash cm12.1 for i9305 & install the gapps aroma package so you can choose exactly which Google apps you want in your system.
I use winxuser version of CyanogenMod 12.1. (Android 5.1.1)
Btw the devs are currently adapting Android 6.0 dor i9305 & it looks like it will work in a few weeks...
Sent with Tapatalk
Click to expand...
Click to collapse
Hi,
Lets talk about the behavior after full wipe using Philz,
as I know all data should be cleared right? But after I full wipe using philz and flash a rom, after that all data remains including all photos, whatsapp data etc.... is that a normal scenario?

Jeorainc said:
Hi,
Lets talk about the behavior after full wipe using Philz,
as I know all data should be cleared right? But after I full wipe using philz and flash a rom, after that all data remains including all photos, whatsapp data etc.... is that a normal scenario?
Click to expand...
Click to collapse
In Philz 6.48.4 (also the one im using), you have to go to ''mounts and storage'' and do a ''format /data and /data/media (/sdcard)'', this will wipe your internal SD (phone storage) where your photos, whatsapp data etc. are stored, so before wiping it make sure anything you need is saved elsewhere on your pc. If you need to wipe your external SD (micro sd), you need to do a ''format /storage/sdcard1''.
SOME INFO ABOUT WIPING BEFORE INSTALLING A ROM:
The following actions are what i consider a normal wipe.
*This is the wipe that you need most of the time.
- wipe data/factory reset
- wipe cache partition
- in advanced ---> wipe dalvik cache
Now flash the rom you want..
This is what i consider a full wipe.
*This is the wipe that you need if you want to have a clean installation.
- wipe data/factory reset
- wipe cache partition
- in mounts and storage ---> format /data and /data/media (/sdcard)
- in advanced ---> wipe dalvik cache
Now flash the rom you want..
And this is what i consider a mega wipe.
*This is the wipe that you need if you absolutely need to wipe everything. (more for advanced users who know exactly what they are doing)
- wipe data/factory reset
- wipe cache partition
- in mounts and storage ---> format /data
- in mounts and storage ---> format /boot
- in mounts and storage ---> format /modem (do it only if the rom your gonna install has modem/s included!)
- in mounts and storage ---> format /data and /data/media (/sdcard)
- in advanced ---> wipe dalvik cache
Now flash the rom you want..
For using Samsung 4.4.4 roms, such as N4 Elite Lite, Eclipse, TGP or Amcha rom, it is recommended at this point to update your bootloader to a 4.4.4 kitkat bootloader if you are still on a 4.3 bootloader, you can do that by flashing a Samsung official firmware with ODIN, preferably one for your region if it exists, if not any other latest firmware will do.
And FYI, the bootloader cannot be removed, its a part of your device !
If you dont know what bootloader you have at the moment, you can check it by going to the first page of my recovery/guide thread and then scroll down and at the end of the OP you'll see some info about bootloaders with a picture, where it says ''step 5''.
Maybe you already know some of this, but still i explained in details so that it will be also usefull for others
Happy flashing! :good:

MaHo_66 said:
In Philz 6.48.4 (also the one im using), you have to go to ''mounts and storage'' and do a ''format /data and /data/media (/sdcard)'', this will wipe your internal SD (phone storage) where your photos, whatsapp data etc. are stored, so before wiping it make sure anything you need is saved elsewhere on your pc. If you need to wipe your external SD (micro sd), you need to do a ''format /storage/sdcard1''.
SOME INFO ABOUT WIPING BEFORE INSTALLING A ROM:
The following actions are what i consider a normal wipe.
*This is the wipe that you need most of the time.
- wipe data/factory reset
- wipe cache partition
- in advanced ---> wipe dalvik cache
Now flash the rom you want..
This is what i consider a full wipe.
*This is the wipe that you need if you want to have a clean installation.
- wipe data/factory reset
- wipe cache partition
- in mounts and storage ---> format /data and /data/media (/sdcard)
- in advanced ---> wipe dalvik cache
Now flash the rom you want..
And this is what i consider a mega wipe.
*This is the wipe that you need if you absolutely need to wipe everything. (more for advanced users who know exactly what they are doing)
- wipe data/factory reset
- wipe cache partition
- in mounts and storage ---> format /data
- in mounts and storage ---> format /boot
- in mounts and storage ---> format /modem (do it only if the rom your gonna install has modem/s included!)
- in mounts and storage ---> format /data and /data/media (/sdcard)
- in advanced ---> wipe dalvik cache
Now flash the rom you want..
For using Samsung 4.4.4 roms, such as N4 Elite Lite, Eclipse, TGP or Amcha rom, it is recommended at this point to update your bootloader to a 4.4.4 kitkat bootloader if you are still on a 4.3 bootloader, you can do that by flashing a Samsung official firmware with ODIN, preferably one for your region if it exists, if not any other latest firmware will do.
And FYI, the bootloader cannot be removed, its a part of your device !
If you dont know what bootloader you have at the moment, you can check it by going to the first page of my recovery/guide thread and then scroll down and at the end of the OP you'll see some info about bootloaders with a picture, where it says ''step 5''.
Maybe you already know some of this, but still i explained in details so that it will be also usefull for others
Happy flashing! :good:
Click to expand...
Click to collapse
Really thanks for your answer and appreciate your great work for the N4 elite rom!
I didn't flash an android since android 2.1 and at that time a full wipe using CWM will wipe everything in the device, so I just wonder why the wipe recently will keep user data... once again thanks very much! :good::good::good:

can't flash kernel and rom

Hi there! I want to test the official CM12.1 rom so I decided to format the phone and flash a custom kernel and then the rom.
First I flashed TWRP (2.8.7.0) using fastboot and enter it. I made a complete wipe using the advanced wipe and marking all options (except usb-otg).
Once the partitions are clean I flashed the kernel using the install option and selecting the zip file, finally the same for the CM12.1 rom (nightly). Wiped cache and dalvik and restart, but somehow miui reinstalled.... (it is possible to completely delete miui?). The kernel seems to be the stock (3.4.0-g7f72d41-01413-g70bd50e).
I read in the official CM12.1 post that the rom automatically extends the system partition (merging the two system partitions to have a partition with 1.28GB), is this true or do I have to do it manually (flashing something?).
Thanks.

Flash this once and your partition will be 1.2 GB.

Thanks! Is it normal that it still shows just 629MB? (I can see it in the repair/resize/change-file-system section).
Now, every rom that I flash it stucks at the "mi boot logo"... Maybe I'm doing something wrong; I wipe/factory reset (including cache/dalvik) and then flash the zip, and (wipe again, the option at the left to reboot) and reboot to system.... It's stuck, I tried with other custom roms and it happens the same. What am I doing wrong??

Did you switched the partition (system 1 for non - miui and system 2 for miui)? It's located in advanced options in cwm.

pratyush997 said:
Did you switched the partition (system 1 for non - miui and system 2 for miui)? It's located in advanced options in cwm.
Click to expand...
Click to collapse
I'm using TWRP. So I have to flash CWM to extend the partition?

ChazyTheBest said:
I'm using TWRP. So I have to flash CWM to extend the partition?
Click to expand...
Click to collapse
I do not use TWRP, can't help you.

ChazyTheBest said:
I'm using TWRP. So I have to flash CWM to extend the partition?
Click to expand...
Click to collapse
Yes, the repartition zip only works on CWM. People said that they have problem while repartitioning with TWRP.

zzvilzz said:
Yes, the repartition zip only works on CWM. People said that they have problem while repartitioning with TWRP.
Click to expand...
Click to collapse
did you solve your problem?...im having that same problem of you :crying: