Hi,
So, i thought of trying different ROMS,earlier i was using stock rom. Now, i download many new roms like cyanogen 11, creed v4, chobits...., etc.
But Cyanogen OS 11 was the only ROM which i could get to work, rest of them just installed and when i rebooted my device through CWM. Nothing happened and cwm just opened again instead of the actual thing. Like i said Cyanogen was the only exception in which when i rebooted my device it actually started
Please help me(what am i doing wrong)
Also what's up with Link2SD and cyanogen
Harry947 said:
Hi,
So, i thought of trying different ROMS,earlier i was using stock rom. Now, i download many new roms like cyanogen 11, creed v4, chobits...., etc.
But Cyanogen OS 11 was the only ROM which i could get to work, rest of them just installed and when i rebooted my device through CWM. Nothing happened and cwm just opened again instead of the actual thing. Like i said Cyanogen was the only exception in which when i rebooted my device it actually started
Please help me(what am i doing wrong)
Also what's up with Link2SD and cyanogen
Click to expand...
Click to collapse
CM11 uses cwm6 and requires your system to be in ext format
Stock Roms use cwm5 and requires your phone system to be in rfs format
To clarify
If flashing cm11 use cwm6
If flashing stock roms use cwm5
In both cases make sure you format system data cache then mount system data cache before flashing the rom zip
You will need to use the cm11 kernel with cm11 (in rom zip)
You will need to use a stock kernel for stock roms
You will need to reformat your system back to rfs for stock based roms unless the kernel supports ext - you do this by flashing stock rom via odin (link at top of dev thread or in my signature)
marcussmith2626 said:
CM11 uses cwm6 and requires your system to be in ext format
Stock Roms use cwm5 and requires your phone system to be in rfs format
To clarify
If flashing cm11 use cwm6
If flashing stock roms use cwm5
In both cases make sure you format system data cache then mount system data cache before flashing the rom zip
You will need to use the cm11 kernel with cm11 (in rom zip)
You will need to use a stock kernel for stock roms
You will need to reformat your system back to rfs for stock based roms unless the kernel supports ext - you do this by flashing stock rom via odin (link at top of dev thread or in my signature)
Click to expand...
Click to collapse
Thanks for the information but i don't think you got my question...
I can only install cyanogenmod 11 no other rom(i haven't tried any stock one)
Is this the problem, if you want to install a new custom rom, first you have to again install a stock rom...?
Also can you suggest a gapp package as i cannot install both nano and pico ones(they're too large for my s5360) and i did find a mini package but in that i cannot connect to my google account
Thanks
Harry947 said:
Also can you suggest a gapp package as i cannot install both nano and pico ones(they're too large for my s5360) and i did find a mini package but in that i cannot connect to my google account
Thanks
Click to expand...
Click to collapse
Read my post again
The reason why you can't install another rom if you have flashed cm11 is because only cm11 uses cwm6 & stock based roms use cwm5 - also the file systems between cm11 and stock based are different
For stock based roms
Flash stock rom via odin If not already on stock
Flash a temp cwm5 zip in stock recovery
Format system data cache
Mount system data cache
Flash rom zip
Restart
The gapps for cm11 is clearly available on the first post of the rom thread
Gapps for Gingerbread is easily available via Google if you search gapps
marcussmith2626 said:
Read my post again
The reason why you can't install another rom if you have flashed cm11 is because only cm11 uses cwm6 & stock based roms use cwm5 - also the file systems between cm11 and stock based are different
For stock based roms
Flash stock rom via odin If not already on stock
Flash a temp cwm5 zip in stock recovery
Format system data cache
Mount system data cache
Flash rom zip
Restart
The gapps for cm11 is clearly available on the first post of the rom thread
Gapps for Gingerbread is easily available via Google if you search gapps
Click to expand...
Click to collapse
Thank you for replying again
You see, i am not trying to install stock rom..
I tried installing chobitsdigitalis, even other custom roms but even after successful flashing they never booted.
And yes gapps are available but i cannot install any of them due to the storage problem
Harry947 said:
Thank you for replying again
You see, i am not trying to install stock rom..
I tried installing chobitsdigitalis, even other custom roms but even after successful flashing they never booted.
And yes gapps are available but i cannot install any of them due to the storage problem
Click to expand...
Click to collapse
When I say stock rom this also includes any custom roms based on stock rom - such as the ones you mentioned
You are obviously on the wrong file system & not using a stock based kernel
Flash stock rom via odin first to convert back to rfs & stock kernel & use cwm5 to flash stock based custom roms
Gapps for Gingerbread (for use on stock based custom roms only & cm7) https://goo.im/gapps/gapps-gb-20110828-signed.zip
Gapps for cm11 only on rom thread
Thanks a lot !!
I'll try that and let you know
Thanks again for all your help .....
CyanogenMod 11 uses the open-source MTD driver for the internal flash chip, as opposed to all other ROMs which use Samsung's BML driver. No other custom ROM uses the MTD driver (apart from the custom kernels that people are releasing for CM11, which are all based on my kernel source that use the MTD driver).
In order to go back to any ROM that uses the BML driver (which includes ROMs such as CyanogenMod 9), the partitions first need to be converted back to the old BML format. You need to flash all components of a full stock ROM at the same time - the PDA, CSC and MODEM - via Odin. There's no other way to go back.
psyke83 said:
CyanogenMod 11 uses the open-source MTD driver for the internal flash chip, as opposed to all other ROMs which use Samsung's BML driver. No other custom ROM uses the MTD driver (apart from the custom kernels that people are releasing for CM11, which are all based on my kernel source that use the MTD driver).
In order to go back to any ROM that uses the BML driver (which includes ROMs such as CyanogenMod 9), the partitions first need to be converted back to the old BML format. You need to flash all components of a full stock ROM at the same time - the PDA, CSC and MODEM - via Odin. There's no other way to go back.
Click to expand...
Click to collapse
Psyke, as you're a part of the androidarmv6 team, do you have any info on ART on armv6?
Related
Apologies if this question is fundamentally stupid, I am a noob and have never tried modifying a ROM.
My question is if I can copy a CWM kernel zip file contents into a CWM ROM zip file and flash my phone without breaking / bricking my phone.
Background Info
I typically try and run the latest leaked stock ROM.
At the moment it is EH17.
I swap out the kernel for the plus kernel so that I can run ext4
I'm looking to start trying out some themes
I recently watched qbking77's video on how to uninstall a theme
Its essentially just just re-flash your CWM ROM
I would like to be able to flash without having to swap file systems every time.
Will extracting the ROM zip, overwriting files with kernel zip contents, rezipping, and flashing my phone cause problems?
Thanks for any help you can offer
Hmm, if you are just running a stock rom, you dont need to uninstall anything. You can just download a EH17 theme (or whatever type of ROM you are on), boot into CWM, wipe cashe and dalvik cashe 3 times each and then choose install from sdcard and choose the theme you want to flash.
Now if you want to try another one after that, do the same process. Wiping the cashes and flashing the theme is all you need to do.
Hello
I have Motorola Bravo, everything stock 2.2.1 ROM
but I want to install custom ROMs and I have one question: Does Motorola Bravo's bootloader need unlock? I ask that, because I also have Motorola Atrix 4G and I had to unlock it's bootloader to install Cm7
Enigmavision said:
Hello
I have Motorola Bravo, everything stock 2.2.1 ROM
but I want to install custom ROMs and I have one question: Does Motorola Bravo's bootloader need unlock? I ask that, because I also have Motorola Atrix 4G and I had to unlock it's bootloader to install Cm7
Click to expand...
Click to collapse
No, just install 2nd-init recovery (search the Defy Forums\CM7 threads here) then flash away . Our bootloader is locked up like a con in a SuperMax with a triple life sentence. I'm getting ready for work so I don't have time to hotlink.
skeevy420 said:
No, just install 2nd-init recovery (search the Defy Forums\CM7 threads here) then flash away . Our bootloader is locked up like a con in a SuperMax with a triple life sentence. I'm getting ready for work so I don't have time to hotlink.
Click to expand...
Click to collapse
Here you go: https://www.box.com/shared/p07z8hangnqxydducrhr.
Edit: on a side note, I've had issues restoring my JB nand from the cm7 recovery. I get "error restoring system" in the middle of a nand restore. It also completely screws up mounts and the only thing I can do is install a ROM from scratch. The md5 checks out as well. Any ideas?
Dr. Orange said:
Here you go: https://www.box.com/shared/p07z8hangnqxydducrhr.
Edit: on a side note, I've had issues restoring my JB nand from the cm7 recovery. I get "error restoring system" in the middle of a nand restore. It also completely screws up mounts and the only thing I can do is install a ROM from scratch. The md5 checks out as well. Any ideas?
Click to expand...
Click to collapse
JB has a newer recovery. Install a JB rom then restore the nand of the JB backup.
Flash JB rom (cache\data wipes don't matter since you won't be booting into the system)
Reboot directly into recovery (don't let the system boot up, even once)
Restore JB Backup as usual
This is actually a common problem with Defy users running older MS2 roms trying to flash JB -- the different recovery versions can be a pita to deal with sometimes; but its usually fixed by flashing a rom with a compatible recovery version then restoring the nand afterwards.
While I won't go into the full details, you can also take the recovery from a JB rom and a GB rom and make them into a flashable zips -- basically open the rom's zip and delete all the /system folders except /system/bootmenu and edit the rom's updater-script to only set permissions to /system/bootmenu. It would also be a good idea to add in ramdisk backup commands as well (the init.rc files under 2nd-init and 2nd-boot) since they can change from rom to rom. Once all that's done you'll be able to flash the required recovery version for the nand you intend to restore or flash the JB recovery after flashing any rom and have an up-to-date recovery with an older rom. If you use multiboot it would be a good idea to merge it into your new recovery zip as well.
/About to test a CM7 port with many tweaks -- if it boots I'll start adding in some market apps and finish it up later today . Then its off to start updating PA with a Custom Kernel . I may have to drop MS2 PA support if the MS2's Custom Kernel differences makes it incompatible with the Defy base
skeevy420 said:
JB has a newer recovery. Install a JB rom then restore the nand of the JB backup.
Flash JB rom (cache\data wipes don't matter since you won't be booting into the system)
Reboot directly into recovery (don't let the system boot up, even once)
Restore JB Backup as usual
This is actually a common problem with Defy users running older MS2 roms trying to flash JB -- the different recovery versions can be a pita to deal with sometimes; but its usually fixed by flashing a rom with a compatible recovery version then restoring the nand afterwards.
While I won't go into the full details, you can also take the recovery from a JB rom and a GB rom and make them into a flashable zips -- basically open the rom's zip and delete all the /system folders except /system/bootmenu and edit the rom's updater-script to only set permissions to /system/bootmenu. It would also be a good idea to add in ramdisk backup commands as well (the init.rc files under 2nd-init and 2nd-boot) since they can change from rom to rom. Once all that's done you'll be able to flash the required recovery version for the nand you intend to restore or flash the JB recovery after flashing any rom and have an up-to-date recovery with an older rom. If you use multiboot it would be a good idea to merge it into your new recovery zip as well.
/About to test a CM7 port with many tweaks -- if it boots I'll start adding in some market apps and finish it up later today . Then its off to start updating PA with a Custom Kernel . I may have to drop MS2 PA support if the MS2's Custom Kernel differences makes it incompatible with the Defy base
Click to expand...
Click to collapse
Yep that makes sense. Thanks for the help as always skeevy.
*edit* Same issue.
Restoring system...
Error while restoring /system!
Problem while restoring system!
Maybe I didn't reboot correctly...bad backup maybe? I've restored this backup before with no problems. : \
*edit again* I goofed. Your instructions worked fine.
in teamwin official website i couldn't find twrp recovery support for motorola bravo, however motorola defy was in the list to get twrp recovery.
does TWRP for defy work on bravo? or we need a different for bravo? i love that recovery ...can some body help me install that on my bravo???
hiandro said:
in teamwin official website i couldn't find twrp recovery support for motorola bravo, however motorola defy was in the list to get twrp recovery.
does TWRP for defy work on bravo? or we need a different for bravo? i love that recovery ...can some body help me install that on my bravo???
Click to expand...
Click to collapse
The Defy TWRP works on the Bravo, but its only up to version 2.1 and can't install large Aroma roms (WR, Pikachu, etc). Your better off reading the thread over at Defy Development. Its neat and works, but our custom CWM 5 is the best for us in terms of reliability and stability.
skeevy420 said:
The Defy TWRP works on the Bravo, but its only up to version 2.1 and can't install large Aroma roms (WR, Pikachu, etc). Your better off reading the thread over at Defy Development. Its neat and works, but our custom CWM 5 is the best for us in terms of reliability and stability.
Click to expand...
Click to collapse
can u give me link to download latest CWM please.
hiandro said:
can u give me link to download latest CWM please.
Click to expand...
Click to collapse
Its installed be default with CM10 or PA. The newer the rom, the newer the recovery.
You can copy the zip/system/bootmenu/.... to other roms to get the touch ui in the bootmenu, just don't overwrite your current roms init scripts....and use a PRE 2nd Kernel zip when porting the bootmenu to non custom kernel roms. This isn't something I'd advise doing cause if you don't know what your fully doing you can easily put yourself in a position to flash the sbf. I sbf'd 3 times adding the JB Touch bootmenu to CM7.
skeevy420 said:
Its installed be default with CM10 or PA. The newer the rom, the newer the recovery.
You can copy the zip/system/bootmenu/.... to other roms to get the touch ui in the bootmenu, just don't overwrite your current roms init scripts....and use a PRE 2nd Kernel zip when porting the bootmenu to non custom kernel roms. This isn't something I'd advise doing cause if you don't know what your fully doing you can easily put yourself in a position to flash the sbf. I sbf'd 3 times adding the JB Touch bootmenu to CM7.
Click to expand...
Click to collapse
I installed cm10 then after I went to stable recovery and I wipe data/factory reset and then wipe cache and again wipe dalvik cache,and then I went to install zip from SD card and then choose mokee and flashed the zip.and when I reboot the phone it got stuck at Motorola red logo. again i boot into recovery (it was different, which mokee installed maybe)and when i wipe data and cache it said something like this:can't mount E/cache/recovery/log .and then i went to backup and restore and restored my cm10 backup and it only restored system(no data) why did this happen did I did something wrong?? or is there problem in recovery?? please tell me about this.
hiandro said:
I installed cm10 then after I went to stable recovery and I wipe data/factory reset and then wipe cache and again wipe dalvik cache,and then I went to install zip from SD card and then choose mokee and flashed the zip.and when I reboot the phone it got stuck at Motorola red logo. again i boot into recovery (it was different, which mokee installed maybe)and when i wipe data and cache it said something like this:can't mount E/cache/recovery/log .and then i went to backup and restore and restored my cm10 backup and it only restored system(no data) why did this happen did I did something wrong?? or is there problem in recovery?? please tell me about this.
Click to expand...
Click to collapse
I have a couple of ideas, but I'd be guessing with all of them. Probably just an error from CM10 using a newer recovery than Mokee. Since CM10's /system was restored, so was its bootmenu\recovery -- try doing a full restore now that you're using the same recovery that backed it up .
Crap like this is why we need an unlocked bootloader, or even just a place to hide a custom recovery -- with every rom you flash, your recovery changes and bad things can\have happened. While its nowhere as bad as it once was, problems like yours still occur from time to time. Its the same reason that there's so many posts with people having problems from using BandroidX Recovery -- its a very old CWM based recovery that uses different formats than whats used now (can't even install newer roms with it). Old and new don't usually play nicely with us .
skeevy420 said:
I have a couple of ideas, but I'd be guessing with all of them. Probably just an error from CM10 using a newer recovery than Mokee. Since CM10's /system was restored, so was its bootmenu\recovery -- try doing a full restore now that you're using the same recovery that backed it up .
Crap like this is why we need an unlocked bootloader, or even just a place to hide a custom recovery -- with every rom you flash, your recovery changes and bad things can\have happened. While its nowhere as bad as it once was, problems like yours still occur from time to time. Its the same reason that there's so many posts with people having problems from using BandroidX Recovery -- its a very old CWM based recovery that uses different formats than whats used now (can't even install newer roms with it). Old and new don't usually play nicely with us .
Click to expand...
Click to collapse
Yeah, i tried to restore backup using cm10 recovery and although it said cant restore .android.secure something like that(iam not quite sure) it restored system as well as data.
The thing is i like mokee os .its speed, clean and clear... ecetra but it is not jelly bean.can't we have a cm10 tweaked and modified for bravo.of course I love your PA jelly bean there are lots of tablet tweaks can you also add some other functions like in pimp my rom.
And thanks man for answering my queries
Hi bro my friend had a problem with his galaxy y.
His sgy bootlooped after he installed a custom rom on it. Then he asked me to fix it. I tried many solution but no one works for his sgy.
1. Wipe data, wipe cache, fix permission etc. via untemporary cwm (v.5xx) and then reflash it. No effect, still bootlooping.
2. Flash custom rom via android stock recovery (someone said untemporary cwm is not for flashing rom so he recommen to flash it via stock rom) no effect, still bootlooping.
3. Flash via odin. No detected even usb driver installed. Tried on windows 7 ultimate & windows 8 pro. Still bootlooping (He don't think his usb debugging is on)
4. Flash flashable zip stock rom via cwm/android stock recovery. I haven't tried this one.
Any suggestion? Thanks!
Sent from my HTC One X using XDA Premium 4 mobile app
1 - what rom are you trying - cm roms require percys kernel and stock based roms require a stock based kernel
2 - did you mount system data cache after you wipe system data and cache before flashing a rom? (main cause of people not flashing a rom properly)
3 - did you install samsung drivers only and not have kies installed/running to use odin
you can flash a rom via any cwm tempory or perminant as long as the cwm is suitable for galaxy y - you format system data and cache and you mount system data and cache before you flash anything
marcussmith2626 said:
1 - what rom are you trying - cm roms require percys kernel and stock based roms require a stock based kernel
2 - did you mount system data cache after you wipe system data and cache before flashing a rom? (main cause of people not flashing a rom properly)
3 - did you install samsung drivers only and not have kies installed/running to use odin
you can flash a rom via any cwm tempory or perminant as long as the cwm is suitable for galaxy y - you format system data and cache and you mount system data and cache before you flash anything
Click to expand...
Click to collapse
thanks dude. i already done with it. it was about the driver lol
Hey guys need a help
Just don't slap me with - noob search this that blah blah (i know I'm one still read patiently)
Well i flashed a stock de odexed rom today via (hells kernel) cwm
When wifi was toggled it scanned for a while and then rebooted...
I flashed wifi drivers, re flashed kernel etc. Yet rom rebooted. Back to Evo X and wifi is fine (so i assumed it's a problem in software not my mobile)
I actually tried flashing drivers, setting permissions and re flashed kernel..
I searched on XDA and majority of posts were ICS and JB roms.. Hence I posted this. Thanks in advance
If you're using hells fusion #50 kernel Flash dhd1.1 in cwm with system mounted
if you are using most other stock based kernels flash dhd-stock in cwm with system mounted
marcussmith2626 said:
If you're using hells fusion #50 kernel Flash dhd1.1 in cwm with system mounted
if you are using most other stock based kernels flash dhd-stock in cwm with system mounted
Click to expand...
Click to collapse
Thanks a lot sir i didn't know about the two different files. I had oly dhd
And thanks for uploading it too ^_^
marcussmith2626 said:
If you're using hells fusion #50 kernel Flash dhd1.1 in cwm with system mounted
if you are using most other stock based kernels flash dhd-stock in cwm with system mounted
Click to expand...
Click to collapse
Sir it didn't work... After i flashed drivers(with system mounted) and toggled wifi, it detected network but then rebooted (actually it was more like hot boot)... Just as it was before. I guess i didn't download a proper de odexed rom.
tony_stark_noob said:
Sir it didn't work... After i flashed drivers(with system mounted) and toggled wifi, it detected network but then rebooted (actually it was more like hot boot)... Just as it was before. I guess i didn't download a proper de odexed rom.
Click to expand...
Click to collapse
if you have rom problems
download any stock based custom rom from dev section and put on root of sd card
go into recovery
flash temp cwm zip if using a kernel that doesn't already have cwm
goto mounts and storage
format system data and cache
mount system data and cache
flash rom zip
restart
at the moment you cannot download stock roms to flash via odin as hotfile has been closed down although I have uploaded a stock rom firmware to dev host which you can find on or near the last page of dokys firmware thread on dev section - it will boot your phone but its European firmware so may not work on your network but at least it will boot your phone if flashing a custom rom with the method above doesn't work
marcussmith2626 said:
if you have rom problems
download any stock based custom rom from dev section and put on root of sd card
go into recovery
flash temp cwm zip if using a kernel that doesn't already have cwm
goto mounts and storage
format system data and cache
mount system data and cache
flash rom zip
restart
at the moment you cannot download stock roms to flash via odin as hotfile has been closed down although I have uploaded a stock rom firmware to dev host which you can find on or near the last page of dokys firmware thread on dev section - it will boot your phone but its European firmware so may not work on your network but at least it will boot your phone if flashing a custom rom with the method above doesn't work
Click to expand...
Click to collapse
No worries sir, i have Evolution X rom and 2 other in my sd card. Also i have 2 backups.. I just wanted to experiment and probably try to solve the issue on stock. I'm in evo x and everything is working fine.
Thanks a lot for assisting me immediately (pressed the button too )
The thing is i don't have a comp. So i was trying out different stock (cwm flashable) . I will just download one from doky's thread after the website issue has been sorted out
tony_stark_noob said:
No worries sir, i have Evolution X rom and 2 other in my sd card. Also i have 2 backups.. I just wanted to experiment and probably try to solve the issue on stock. I'm in evo x and everything is working fine.
Thanks a lot for assisting me immediately (pressed the button too )
The thing is i don't have a comp. So i was trying out different stock (cwm flashable) . I will just download one from doky's thread after the website issue has been sorted out
Click to expand...
Click to collapse
flashing a stock cwm zip doesnt actually give you stock rom as such - think of it more like a custom rom with no changes made to any files
To make it work properly you really in the case of flashing a deodex stock rom via cwm you need to be on the same baseband as the stock rom
To actually flash stock rom and to change basebands you needs to flash the stock rom firmware via odin
marcussmith2626 said:
flashing a stock cwm zip doesnt actually give you stock rom as such - think of it more like a custom rom with no changes made to any files
To make it work properly you really in the case of flashing a deodex stock rom via cwm you need to be on the same baseband as the stock rom
To actually flash stock rom and to change basebands you needs to flash the stock rom firmware via odin
Click to expand...
Click to collapse
Sir i have indian version. I didn't change basebands but ya i didn't know about the odin thing which u mentioned. Thank u