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...
Related
Hi there,
I have a rooted N7000 running original Android v 2.3.6
I want to flash (test) it with a custom ROM.
I made a full backup of my current system (via CWM backup)
Now, when I flash a (new Android 4) custom ROM, will it then be possible to restore the old v2.3.6 image that I made, using CWM?
Other question: Do I need to take care of what type Kernal version I have
I have 2.6.35.7-N7000XXKKA-CL726566
Baseband-version is N7000XXkk5
Thanks for your reply.
Rene
jbin said:
Hi there,
I have a rooted N7000 running original Android v 2.3.6
I want to flash (test) it with a custom ROM.
I made a full backup of my current system (via CWM backup)
Now, when I flash a (new Android 4) custom ROM, will it then be possible to restore the old v2.3.6 image that I made, using CWM?
Other question: Do I need to take care of what type Kernal version I have
I have 2.6.35.7-N7000XXKKA-CL726566
Baseband-version is N7000XXkk5
Thanks for your reply.
Rene
Click to expand...
Click to collapse
nothing to worry about, that is what backup is intended to do.
the only thing you have to watch that you're on safe kernel like philZ when wiping data in stock ics or jb (read sticky threads)
example: if you are on philz kernel and runing ics or jb, when you restore your backup of gb, you restore your gb kernel, system, data etc, just like backing home
djoni_gitara said:
nothing to worry about, that is what backup is intended to do.
the only thing you have to watch that you're on safe kernel like philZ when wiping data in stock ics or jb (read sticky threads)
example: if you are on philz kernel and runing ics or jb, when you restore your backup of gb, you restore your gb kernel, system, data etc, just like backing home
Click to expand...
Click to collapse
OK, Thanks for the reply. So if I understand correctly:
1. I make a backup of my current ROM (Image via CWM) and put it in a safe place.
2. I can flash any custom ROM, and test/play with them.
3. Afterwards I can put back my old ROM again via CWM restore.
4. Reboot, and I'm back in the old state.
Is this right?
Can I flash ROMs by using CWM also (using zip files) or do I need to flash, using Odin?
I actually do not understand your remark about philZ, can you explain a bit more about what that means.
Thanks for your help so far
Rene
jbin said:
OK, Thanks for the reply. So if I understand correctly:
1. I make a backup of my current ROM (Image via CWM) and put it in a safe place.
2. I can flash any custom ROM, and test/play with them.
3. Afterwards I can put back my old ROM again via CWM restore.
4. Reboot, and I'm back in the old state.
Is this right?
Can I flash ROMs by using CWM also (using zip files) or do I need to flash, using Odin?
I actually do not understand your remark about philZ, can you explain a bit more about what that means.
Thanks for your help so far
Rene
Click to expand...
Click to collapse
Since you are going to try custom rom, you need not to worry about emmc brickbug, since they will be using a safe kernel..but double check before flashing...so, if you are on Stock ICS kernel, you should NOT wipe/factory reset..if you do, you will brick your phone..you can just go through couple of sticky threads to know abt emmc brickbug, if you are not aware of that..whatever the steps you have mentioned above are correct..but when you flash a custom rom, follow the instructions mentioned in the Custom rom OP...
Shyam said:
Since you are going to try custom rom, you need not to worry about emmc brickbug, since they will be using a safe kernel..but double check before flashing...so, if you are on Stock ICS kernel, you should NOT wipe/factory reset..if you do, you will brick your phone..you can just go through couple of sticky threads to know abt emmc brickbug, if you are not aware of that..whatever the steps you have mentioned above are correct..but when you flash a custom rom, follow the instructions mentioned in the Custom rom OP...
Click to expand...
Click to collapse
+1
jbin said:
OK, Thanks for the reply. So if I understand correctly:
1. I make a backup of my current ROM (Image via CWM) and put it in a safe place.
2. I can flash any custom ROM, and test/play with them.
3. Afterwards I can put back my old ROM again via CWM restore.
4. Reboot, and I'm back in the old state.
Is this right?
Can I flash ROMs by using CWM also (using zip files) or do I need to flash, using Odin?
I actually do not understand your remark about philZ, can you explain a bit more about what that means.
Thanks for your help so far
Rene
Click to expand...
Click to collapse
1. Yes, copy your /clockworkmod to your pc (just for double safety) dont cut it or move it, you need it on your internal sd card always, if you wanted to restore it again... and dont rename it (you will end up with message md5 missmatch!)
2. of course
3. Every new custom kernel like Philz kernel ( for ICS TW and JB TW) http://forum.xda-developers.com/showthread.php?t=1901191
or hydracore (not working on TW JB, but works on all other) http://forum.xda-developers.com/showthread.php?t=1749863
have built in CWM 6.x.x.x , You can recognize them by the gray background in CWM recovery. (there is no need to install independet CWM or something else, like you do on your stock GB kernel)
They are built in almost every custom rom, and these kernel are safe for wipe.
3.1 . So if you flashed new custom TW ics or jb, and after playing with them, you want back to your nandroid backup, just go boot in recovery (now you see a grey background CWM6) do all the wipes (in my experience the best way is: (advanced > wipe dalvik cache, go back > wipe cache, then wipe/data factory reset, then go into mounts and storage > format cache,system,data and preload , dont format emmc and sd card. go back into backup/restore > restore from (internal sd card or some other place depends on where you place your backup)
4. of course, when youo see a message backup complete, reboot it
Spent quite some time searching through the forum but I'd still like a few pointers on where to start particularly (in which order).
Like;
1) Root
2) CWM
3) ROM Manager
4) SuperUser
5) Odin
6) Data wipe
7) Binary count reset
8) Recovery Manager
9) Custom ROMS
(EVEN THOUGH I'VE NUMBERED THEM, IT'S NOT LIKE I KNOW THE ORDER, JUST IN CASE YOU'RE WONDERING)
So here are my main questions:
1) In which order do I install them ?
2) Is there any relationship between them? (i.e. I thought ROM Manager let you install CWM and with CWM you can get to Recovery manager or something...)
3) Do I need the Recovery manager for recovery or for installation of custom ROMS?
4) What is the point of getting custom ROMS when I get root ?
Phone: GT-I8190
Android: 4.1.1
Baseband/Build: I8190XXALJL
Thanks in advance, and apologies for asking same question if there is a thread around here about it.
I'd prefer ppl to explain rather than referring to other threads as that got me a little confused before. (you may still refer if that thread is clear enough)
Ok. The order is
1- Root (superuser comes with it)
2- CWM
3-see the right rom for u
4- wipe data, cache, and dalvic in advanced, to flash rom
5-reset counter when u flash anthing in odin u will have a yello triangle to remove u have to reset counter ( does not effect the phone
Press like if i helped u
Sent from my HTC One X
mhoss48 said:
Ok. The order is
1- Root (superuser comes with it)
2- CWM
3-see the right rom for u
4- wipe data, cache, and dalvic in advanced, to flash rom
5-reset counter when u flash anthing in odin u will have a yello triangle to remove u have to reset counter ( does not effect the phone
Press like if i helped u
Sent from my HTC One X
Click to expand...
Click to collapse
Could u explain 3 a bit more ?
Also is there any relationship between CWM, ROM manager, custom ROMS and Recovery Manager ?
Go to development forum, pick one of the pre rooted firmwares and flash via odin. Then install rommanager app from tbe play store and flash cwm recovery. Don't worry about binary count coz triangle away app works on our phone. If you want to wipe the phone reboot to recovery and wipe data. To boot into recovery use the quick boot app from play store.
Sent from my GT-I8190 using Tapatalk 2
...and most important.. Don't forget to make a full nandroid backup in recovery before you start to apply mods and other things
Might come in handy if the phone fails to boot!
Should note that after custom rom you can't get access software update through kies air. At least I can't :-\
Sent from my GT-I8190 using Tapatalk 2
Sv: Where to start ?
Who needs Kies when there is XDA?
Sent through time and space from my s3mini.
vonuzu said:
Go to development forum, pick one of the pre rooted firmwares and flash via odin. Then install rommanager app from tbe play store and flash cwm recovery. Don't worry about binary count coz triangle away app works on our phone. If you want to wipe the phone reboot to recovery and wipe data. To boot into recovery use the quick boot app from play store.
Sent from my GT-I8190 using Tapatalk 2
Click to expand...
Click to collapse
So if I understand this the right way; CWM recovery has custom ROMS or am I getting the wrong idea ? - Why do I need it ?
(It's just that I've been a little confused because of the mass information available on XDA, so bear with me if I'm a bit annoying
tys0n said:
...and most important.. Don't forget to make a full nandroid backup in recovery before you start to apply mods and other things
Might come in handy if the phone fails to boot!
Click to expand...
Click to collapse
Which would you prefer; Nandroid or Titanium ?
Do I need "busybox" for anything ?
Do I need Kies to connect my phone to PC btw ?
Another question: There are two recovery images on the official site of CWM, do we need to choose the normal one or the touch and what about the ROMS, do I need to install those seperately ?
Mystique03 said:
So if I understand this the right way; CWM recovery has custom ROMS or am I getting the wrong idea ? - Why do I need it ?
(It's just that I've been a little confused because of the mass information available on XDA, so bear with me if I'm a bit annoying
Which would you prefer; Nandroid or Titanium ?
Do I need "busybox" for anything ?
Click to expand...
Click to collapse
With cwm or any other custom recovery you will be able to install zip files with mods, tweaks, roms, and so on. Simply put, non-samsung-signed-things + other functions as well.
You wont find many custom roms for s3mini yet wich it to be flashed through cwm. For now i think theres only BenzRom but I guess more will come
Nandroid or Titanium ? BOTH!
Nandroid for restore if something goes really bad, and remember to make sure you have a backup before you apply changes or mods. If you dont like it you can easily go back to previous state without flashing new firmware and have to install all your apps from scratch.
You will be just where you were at the time the nandroid was made.
Titanium backup to backup your apps and appdata. When installing new rom you can simply restore all your apps and appdata without downloading everything again. Do not restore systemdata. It often leads to alot of trouble.
Just make sure you save all your backups on your external sd, so it won't get wiped by mistake.
Busybox is needed if you want more than just root so go ahead and install.
tys0n said:
With cwm or any other custom recovery you will be able to install zip files with mods, tweaks, roms, and so on. Simply put, non-samsung-signed-things + other functions as well.
You wont find many custom roms for s3mini yet wich it to be flashed through cwm. For now i think theres only BenzRom but I guess more will come
Nandroid or Titanium ? BOTH!
Nandroid for restore if something goes really bad, and remember to make sure you have a backup before you apply changes or mods. If you dont like it you can easily go back to previous state without flashing new firmware and have to install all your apps from scratch.
You will be just where you were at the time the nandroid was made.
Titanium backup to backup your apps and appdata. When installing new rom you can simply restore all your apps and appdata without downloading everything again. Do not restore systemdata. It often leads to alot of trouble.
Just make sure you save all your backups on your external sd, so it won't get wiped by mistake.
Busybox is needed if you want more than just root so go ahead and install.
Click to expand...
Click to collapse
Last couple of questions for now (apologies ) ;
1)Do I need Kies to connect my phone to PC btw, cuz I read something about USB debugging mode to be turned on and ADB...
2)There are two recovery images on the official site of CWM, do we need to choose the normal one or the touch and what about the ROMS, do I need to install those seperately ?
3)So every time we flash another ROM it has a chance to brick or are we safe if we made a backup beforehand ?
4)What format should I format my card to ? - FAT32, NTFS, ext4 or ...?
5)Does data wipe erase all data on phone or phone and sd card ?
6)Given both CWM and Odin flash what would be more recommended ?
Mystique03 said:
Last couple of questions for now (apologies ) ;
1)Do I need Kies to connect my phone to PC btw, cuz I read something about USB debugging mode to be turned on and ADB...
2)There are two recovery images on the official site of CWM, do we need to choose the normal one or the touch and what about the ROMS, do I need to install those seperately ?
3)So every time we flash another ROM it has a chance to brick or are we safe if we made a backup beforehand ?
4)What format should I format my card to ? - FAT32, NTFS, ext4 or ...?
5)Does data wipe erase all data on phone or phone and sd card ?
6)Given both CWM and Odin flash what would be more recommended ?
Click to expand...
Click to collapse
No worries. Better be safe than sorry
1. No, you dont need keis unless you want to look for official updates.
For filetransfer I use Airdroid or box/dropdox/4shared. Official updates will be available to download anyway
Adb (Android Debug Bridge) is just a terminal. I won't go in to details here but you will find lots of threads on how to install and use it if you search xda.
2. They both do the same thing, but in touch-version you make your choices on touch screen while the other one is managed with phones physical buttons. I prefer the latest.
Roms for cwm are packed as .zip & are downloaded separately. As I said before there isn't much to chose from for our device yet.
3. Everything done after root is a risk. Even root can be dangerous if it's not done right.
Usually if something goes wrong it will just lead to a softbrick wich can be fixed in download mode or recovery.
Once rooted, make sure you do that cwm-backup to keep on your external sd. It's also a good idea to keep an odin flashable firmware on your computer, just to be sure.
4. Go for fat32. It can be changed later if you want to explore link2sd, sd-swap etc..
5. Factory reset will wipe all internal, but not your external sd.
6. cwm makes it possible to flash custom roms while odin can't. You need odin to flash official samsung firmware, but cwm to flash custom roms, mods, and so on. Can't really compare those two with each other, as they are used for different things.
:good:
Dated, but still very relevant.
tys0n said:
No worries. Better be safe than sorry
1. No, you dont need keis unless you want to look for official updates.
For filetransfer I use Airdroid or box/dropdox/4shared. Official updates will be available to download anyway
Adb (Android Debug Bridge) is just a terminal. I won't go in to details here but you will find lots of threads on how to install and use it if you search xda.
Click to expand...
Click to collapse
What should I do for wired transfers only, I mean.
Do I need to search for the phone specific driver for pc at Official Samsung site or is there no driver ?
Any other things I need to turn on except USB debugging mode when wired ?
Edit: Nvm, just got on the right track again
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.
Hello everyone.
Forgive me for asking how to change my recovery from CWM to TWRP once again, but all threads I have read so far don't answer my question, which is:
I would like to keep my PAC-Android with all data and just change CWM 6.0.3.1 to TWRP so that I can try other ROMs such as ViperOne or Revolution HD.
Most threads I've read point to Goo Manager which should be able to install OpenRecoveryScript. That gives me the notification that "no recoveries were found for my device". The next option is to use fastboot. For that, I need to unlock the bootloader of my device, which means that I will [theandroidsoul / htc-one-m7-bootloader-unlock-guide OUTSIDE LINK DELETED]lose all ROM data, apps, private data, just everything[/URL]. Since it's possible to flash TWRP over CWM via Goo Manager, I think it should be possible to do this without deleting all data.
I would appreciate any help.
For those of you who are wondering why I want to lose my PAC-Android:
Speakerphone does not work (works fine in Skype though) and I would like to try it on a custom ROM which is closer to stock.
I hope I understand your query correctly..
1. First of all, since you are initially using CWM. Backup your current PACAndroid using CWM.
2. Flash TWRP using your existing CWM recovery.
a. Here's the flashable zip: https://www.dropbox.com/s/716uhr84madvvjl/TWRP_2.6.3.4_m7.zip
3. Flash any ROM (Viper or ARHD)
If you would like to revert to PACAndroid.
1. Flash CWM recovery using your previously installed TWRP.
2. Restore backup.
double_ofour said:
I hope I understand your query correctly..
1. First of all, since you are initially using CWM. Backup your current PACAndroid using CWM.
2. Flash TWRP using your existing CWM recovery.
a. Here's the flashable zip: (outside-url deleted)
Click to expand...
Click to collapse
hum, didn't know it was that easy. thanks a lot for that. (I already had openrecovery-twrp-2.6.3.4-m7ul.img, I haven't flashed anything but zips yet. What about those .img files?)
double_ofour said:
3. Flash any ROM (Viper or ARHD)
If you would like to revert to PACAndroid.
1. Flash CWM recovery using your previously installed TWRP.
2. Restore backup.
Click to expand...
Click to collapse
So, just to be clear, that means that by flashing TWRP I only change my recovery and I will still be able to boot PAC-Android and I will not lose any data. Then, I can create a TWRP-based backup of my PAC-Android and dispose of all CWM-related stuff?
Everything OK. I flashed TWRP and will stick to it. Backup done.
Thank you a lot!
No problemo amigo!.. Hey hit thanks!..
FYI, you could have flashed the .img file without even rebooting (if you are rooted). The TWRP web site even has instructions--it just requires a single shell command. What happens in the background is very simple--the data in the .img is written to the phone's recovery partition.
This is how I last upgraded TWRP--it just works. (The command is called "dd", but I won't bore you by giving the full instructions.)
Well guys this is my first time on the forums. My phone is rendered near useless right now. A few days ago, i rooted my phone via towelroot. as a friend reccomended, i installed ROM manager and flashed clockworkmod recovery. I backed up my stock, perfect ROM with CWM and decided to try installing cyanogenmod 10.3.1......... it wouldn't install. I even tried other apps like ROM installer. Then i came across the handy dandy Cyanogenmod Installer. This seemed great, i didn't have to do anything except click a few buttons on my PC. as i was ready to enjoy a new custom ROM, the following message popped up, "Root access possibly lost. Fix?". I was given the options of "No" and "Yes - Fix root (/system/xbin/su)". i chose the second one, and waited for my device to boot. when it did, it was stock Touchwiz Android version 4.4.2, just like i had initially. what's more is my imei and bandwidth version were both "unknown" and i my sim card was undetected. I decided that technology had gotten the better of my and i tried to flash my old stock ROM back on. i found the file in recovery mode but it kept saying "no files found" whenever i clicked on it. I tried the cyanogenmod installer again, this time choosing "No", resulting in exactly the same scenario. At this point, I would be fine having the stock ROM since i have had such bad luck with the "developer's world" of Android.......... PLEASE HELP!!!!!
Another note:
ROM manager now is telling me that CWM is not installed, yet it is present in recovery mode......
EddyTeddy01 said:
Another note:
ROM manager now is telling me that CWM is not installed, yet it is present in recovery mode......
Click to expand...
Click to collapse
Have you tried installing some other recovery, like TWRP? You won't be able to install CM from it, but you should be able to install other roms.
touchbattle.mika said:
Have you tried installing some other recovery, like TWRP? You won't be able to install CM from it, but you should be able to install other roms.
Click to expand...
Click to collapse
How do I replace CWM with twrp? If I flash twrp, wouldnt CWM stay on my phone as default recovery?
EddyTeddy01 said:
How do I replace CWM with twrp? If I flash twrp, wouldnt CWM stay on my phone as default recovery?
Click to expand...
Click to collapse
follow the guide and replace your recovery easily. after flashing, what recovery you have flashed will be default recovery, i recommend philz, they are all downloadable in the guide
MaHo_66 said:
follow the guide and replace your recovery easily. after flashing, what recovery you have flashed will be default recovery, i recommend philz, they are all downloadable in the guide
Click to expand...
Click to collapse
Would I have to uninstall CWM? I'm just wondering if the file for CWM will still be on my phone. I'll check out the link.
EddyTeddy01 said:
Would I have to uninstall CWM? I'm just wondering if the file for CWM will still be on my phone. I'll check out the link.
Click to expand...
Click to collapse
it´s the best if you also do a format of internal sd in recovery before changing the recovery, because sometimes there are some folders left of it in interrnal memory and you cant delete it, do that if this will be the case. but i think Philz and CWM use same folder, so if you flash philz it will be okay if im correct otherwise you can always format internal sd afterwards
Edit: dont use rom manager for recovery actions, use recovery itself, much more reliable
MaHo_66 said:
follow the guide and replace your recovery easily. after flashing, what recovery you have flashed will be default recovery, i recommend philz, they are all downloadable in the guide
Click to expand...
Click to collapse
That guide made it possible for me to install all custom roms. Witz the recovery installed first it did not work. Thx