[Q] Custom rom with locked bootloader... - Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A

I have LWW stock 4.0.4 rooted and CWM installed...
I just exploring in XDA and bump on these two thread...
http://forum.xda-developers.com/showthread.php?t=1705255
http://forum.xda-developers.com/showthread.php?t=1578109
This custom rom is compatible with lock bootloader now...so I wanna test it out...does anybody with lock bootloader successfully installed this rom and between ExMIUI and MiniCMSandwich Lite which one is better in your opinion...
Thanks.

I tried them both yesterday, just to get an idea. No problem at all with my locked bootloader. Anyway, since I only catched a glimpe of both ROMs, I can't post a real review. You should try them both and decide if you like them
MIUI is more... mmm... i-phone style. MiniCMSandwich looks like a Galaxy Nexus

Feanor88 said:
I tried them both yesterday, just to get an idea. No problem at all with my locked bootloader. Anyway, since I only catched a glimpe of both ROMs, I can't post a real review. You should try them both and decide if you like them
MIUI is more... mmm... i-phone style. MiniCMSandwich looks like a Galaxy Nexus
Click to expand...
Click to collapse
i-phone not my taste...
How to revert back to stock rom...

I try both yesterday, MiniCMSandwich i got bootloop.
MIUI can boot but MIUIHome and many other process FC's.
I can realize its because i am noob on Android mod

AyamPushUp said:
I try both yesterday, MiniCMSandwich i got bootloop.
MIUI can boot but MIUIHome and many other process FC's.
I can realize its because i am noob on Android mod
Click to expand...
Click to collapse
You got bootloop and fc's as you did not clear data.
@Till: these roms will have no problems to run on locked bootloader. As the ROMs are compatible with the stock kernel.
To revert back you need to restore the back up using CWM. In this whole flashing the zip and reverting back process, you just are making sure that you do not touch /system. That way, you do not mess up with nAa's CWM (its installed in /system only), and so everything will be fine.
In case you get a bootloop, just flash the ROM again by flashtool, or repair using PCC and all will be fine.
Thanks,
Rick
Sent from my SK17i using XDA

AyamPushUp said:
I try both yesterday, MiniCMSandwich i got bootloop.
MIUI can boot but MIUIHome and many other process FC's.
I can realize its because i am noob on Android mod
Click to expand...
Click to collapse
oh...maybe I just stick with stock rom right now...

DragonClawsAreSharp said:
You got bootloop and fc's as you did not clear data.
@Till: these roms will have no problems to run on locked bootloader. As the ROMs are compatible with the stock kernel.
To revert back you need to restore the back up using CWM. In this whole flashing the zip and reverting back process, you just are making sure that you do not touch /system. That way, you do not mess up with nAa's CWM (its installed in /system only), and so everything will be fine.
In case you get a bootloop, just flash the ROM again by flashtool, or repair using PCC and all will be fine.
Thanks,
Rick
Sent from my SK17i using XDA
Click to expand...
Click to collapse
So after flashing the rom...to revert back to stock rom just restore nandroid backup?...I don't get it about touch the /system...

Till-Kruspe said:
So after flashing the rom...to revert back to stock rom just restore nandroid backup?...I don't get it about touch the /system...
Click to expand...
Click to collapse
See, the nAa's recovery installed on locked bootloaders are installed on chargemon and charger files which are there at /system/bin of your phone memory.
Now, suppose you install a ROM which is based on the Stock Kernel. To do this you flash the zip you got from xda or somewhere. While this zip is being flashed, the /system files of the stock ROM are replaced by the /system files of the ROM you are flashing. This will cause the chargemon and charger files to be overwritten, and so, CWM messes with itself. And rest of the installation will fail, giving you bootloop or brick.
The kamarush ROM, which is supported on locked bootloader, takes care that it doesn't replace the /system. Thus, nAa's CWM remains intact, and you can successfully flash the ROM.
Thanks,
Rick
Sent from my SK17i using XDA

DragonClawsAreSharp said:
you just are making sure that you do not touch /system. That way, you do not mess up with nAa's CWM (its installed in /system only), and so everything will be fine.
Click to expand...
Click to collapse
Not true. Before installing the ROMs, you NEED to wipe /system. You can do it via CWM (Mounts and storage, wipe /system, /cache and /data. Then Wipe dalvik cache in advanced settings). Otherwise, you'll end up with a lot of fc.
Till-Kruspe said:
So after flashing the rom...to revert back to stock rom just restore nandroid backup?...I don't get it about touch the /system...
Click to expand...
Click to collapse
Yes, restore nandroid and that's all. About /system, I already explained that

Feanor88 said:
Not true. Before installing the ROMs, you NEED to wipe /system. You can do it via CWM (Mounts and storage, wipe /system, /cache and /data. Then Wipe dalvik cache in advanced settings). Otherwise, you'll end up with a lot of fc.
Click to expand...
Click to collapse
.
When you are doing a /system wipe using CWM, then CWM knowd how to protect itself. It will not delete the contents of /bin and /xbin files.
Thanks,
Rick
Sent from my SK17i using XDA

Till-Kruspe said:
So after flashing the rom...to revert back to stock rom just restore nandroid backup?
Click to expand...
Click to collapse
Basically, yes.

DragonClawsAreSharp said:
.
When you are doing a /system wipe using CWM, then CWM knowd how to protect itself. It will not delete the contents of /bin and /xbin files.
Thanks,
Rick
Sent from my SK17i using XDA
Click to expand...
Click to collapse
Of course
What I meant is that you HAVE to touch the /system folder. Just touch it the proper way

Feanor88 said:
Of course
What I meant is that you HAVE to touch the /system folder. Just touch it the proper way
Click to expand...
Click to collapse
Yea. Right. You are correct. In the first post where I mentioned not touching /system, I meant that the ROMs which have been made to work with locked bootloader make sure that they do not touch the /system. The zip files have no instruction about clearing data. So all data has to be cleared manually using CWM, and nAa is clever enough to make sure that his CWM knows how to protect itself. . (I sometimes so badly wish that I had the brains of Kamarush and nAa. I could look at the smali code and know what it means. With my current brain, I have to spend a whole week to figure out what's what, and then editing is a separate story ).
Thanks,
Rick
Sent from my SK17i using XDA

Yo HAVE to wipe /system, because the current system will conflict with the new system.
In nAa CWM you wipe the whole /system (with /bin and /xbin) while it's running, and after wipe if you restart you will stuckat SONY logo, so don't reboot just install from zip. It will start Aroma installer and before the installation you have. to choose the locked bootloader version.It will install the ROM with nAa's CWM and now you can reboot and enjoy the ROM.

ZsDaniel said:
Yo HAVE to wipe /system, because the current system will conflict with the new system.
In nAa CWM you wipe the whole /system (with /bin and /xbin) while it's running, and after wipe if you restart you will stuckat SONY logo, so don't reboot just install from zip. It will start Aroma installer and before the installation you have. to choose the locked bootloader version.It will install the ROM with nAa's CWM and now you can reboot and enjoy the ROM.
Click to expand...
Click to collapse
Hmmm. Right. That seems more logical. .
Thank you bro.
Cheers,
Rick
Sent from my SK17i using XDA

ZsDaniel said:
Yo HAVE to wipe /system, because the current system will conflict with the new system.
In nAa CWM you wipe the whole /system (with /bin and /xbin) while it's running, and after wipe if you restart you will stuckat SONY logo, so don't reboot just install from zip. It will start Aroma installer and before the installation you have. to choose the locked bootloader version.It will install the ROM with nAa's CWM and now you can reboot and enjoy the ROM.
Click to expand...
Click to collapse
how to format whole system...

DragonClawsAreSharp said:
Hmmm. Right. That seems more logical. .
Thank you bro.
Cheers,
Rick
Sent from my SK17i using XDA
Click to expand...
Click to collapse
0. Get ROOT and install CWM. -> Only for Locked Bootloader
1. You must do a Full Wipe in CWM (System/Data/Cache/Dalvik-Cache)!
2. Copy the ROM to your SDCard
3. Flash ROM in the Recovery
4. Reboot & enjoy
5. First boot is loooooong
I don't get it in no. 1

I already told you. Start CWM Recovery on boot. Go to "Mounts and storage" and format /system, /data and /cache. Then go back, head to advanced settings and clear dalvik cache. Then install zip.

Till-Kruspe said:
how to format whole system...
Click to expand...
Click to collapse
Here's what he meant.
You just clear everything (in kamarush's thread it's mentioned) and then you do not go for a re-boot. You directly choose the zip you downloaded. Now the zip will ask you if you have locked bootloader or not. If you select locked bootloader, the ROM installation will start with the installation of CWM (which you had cleared along with everything else), and then rest of the ROM will get installed. Then reboot, and everything will be fine.
Thanks,
Rick
Sent from my SK17i using XDA

DragonClawsAreSharp said:
the ROM installation will start with the installation of CWM (which you had cleared along with everything else)
Click to expand...
Click to collapse
I can't agree on this point. You are using CWM to flash the zip, so CWM is still there

Related

CM7 RC1 to Stock ROM

I am currently on CM7 RC1 and planning to go back STOCK ROM.
I have my back-up stock rom via CWM. Would it possible if I flashed my stock rom back-up(via CWM) even if I am currently on CM7 ROM?? Please help to verify. Thank you.
droidtwoseven said:
I am currently on CM7 RC1 and planning to go back STOCK ROM.
I have my back-up stock rom via CWM. Would it possible if I flashed my stock rom back-up(via CWM) even if I am currently on CM7 ROM?? Please help to verify. Thank you.
Click to expand...
Click to collapse
Backup your CM7 in case it ****s up .
-Factory reset
-Wipe both caches
-Format /system
-Restore Stock
-Reboot
Sent from my GT-S5830 using XDA App
EmoBoiix3 said:
Backup your CM7 in case it ****s up .
-Factory reset
-Wipe both caches
-Format /system
-Restore Stock
-Reboot
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
Did this but I'm stuck on "GT-S5830 Galaxy Ace" Screen. Please help.
try to wipe caches..
i remember this happened with me also...
download same fresh rom from sammobile and flash it first with odin and try to restore now..
haven't tried this but may work
madman_amit said:
try to wipe caches..
i remember this happened with me also...
download same fresh rom from sammobile and flash it first with odin and try to restore now..
haven't tried this but may work
Click to expand...
Click to collapse
Do you mean ill wipe caches after I restore??
droidtwoseven said:
Do you mean ill wipe caches after I restore??
Click to expand...
Click to collapse
Try flashing Cf-root
Sent from my GT-S5830 using XDA App
EmoBoiix3 said:
Try flashing Cf-root
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
How come this will help?
Do wiping caches after I restore will solved this? Please help to confirm.
I don't want to do Odin for now
Surefire way to work will be to
1.) Factory reset
2.) ODIN flash stock ROM of same baseband
3.) Flash CWM
4.) Flash stock ROM backup
I just want to confirm that I have the same problem: when I restored my stock-rom-backup using CWM from C7.1, the phone got stuck in the same point as droidtwoseven said.
I also confirm that I restored the previous C7.1 and the phone is working now. However, I would like to know how to restore the stock rom from CWM.
I hope we can find a solution because this seems to be a problem that everyone will have.
Maybe the problem has something to do with the partitions that C7.1 creates (I'm not sure about this, I'm just a noob).
Thank you.
davidteleco said:
I just want to confirm that I have the same problem: when I restored my stock-rom-backup using CWM from C7.1, the phone got stuck in the same point as droidtwoseven said.
I also confirm that I restored the previous C7.1 and the phone is working now. However, I would like to know how to restore the stock rom from CWM.
I hope we can find a solution because this seems to be a problem that everyone will have.
Maybe the problem has something to do with the partitions that C7.1 creates (I'm not sure about this, I'm just a noob).
Thank you.
Click to expand...
Click to collapse
It could well be that stock ROMs are based on rfs file system while CM7.1 is based on ext 4. Maybe a script has to be implemented to convert the file system back to rfs. I am just hazarding a guess.
happily1986 said:
It could well be that stock ROMs are based on rfs file system while CM7.1 is based on ext 4. Maybe a script has to be implemented to convert the file system back to rfs. I am just hazarding a guess.
Click to expand...
Click to collapse
This is a critical issue that I would like to resolve. I can assume that I will have to flash a stock rom with ODIN but I am afraid that ODIN will brick my phone because of problems with the partitions/file system (RFS vs EXT4).
I don't really know if installing cyanogenmod7.1 by clockworkmod4-recovery has change my phone partitions so I am not sure if ODIN can restore a stock rom by the usual way.
Any help with this?
Thank you so much!
By flashing with ODIN, system file system will revert do rfs.
Most of the Custom ROMs are running on ext4 now, and I flashed several times back to Stock with ODIN after running a Custom ROM with ext4fs.

[Q] unlocked bootloader + custom kernel, flash custom rom success.. but stuck

hello..
i've search thru the forum, and my prob is somehow differ than others..
already unlocked bootloader.. apply custom kernel successfully..
step i do to flash rom:
- backup in CWM
- reboot into recovery [power button then repeatedly press volume up]
- [wipe cache partition, advance wipe dalvik cache, battery stat]
- install custom ROM zip from sdcard (with no ERROR reports or problem during flashing)
- reboot into system
still stuck at sony logo.. wait around 1 hour.. nothing happened...
then i remove battery, try to boot into cwm..
success..
but the cwm background pic changed with wording "CWM-based recovery v5.0.2.7 Full (by DooMLoRD)".. not like before.. and i restored back..
the ROM i tried is Pureness build 3 and jjHybrid 3.1.. both give same problem..
check screenshot of my system below.. is there's any problem with my system?
or it is related to odex?
so.. got any idea or possible solution?
or my phone problem itself?
thx in advance...
try other kernel...
1. Pureness build 3 ,Kernel :Night Elfs ICS Kernel mod
2. jjHybrid 3.1,Kernel Use any of Following
a) STOCK Kernel (No OverClocking)
b) shardul_seth Kernel
c) Night-Elf Kernel
d) Adridu kernel
look at specific thread,you will find the answer.
dualsh0ck said:
hello..
i've search thru the forum, and my prob is somehow differ than others..
already unlocked bootloader.. apply custom kernel successfully..
step i do to flash rom:
- backup in CWM
- reboot into recovery [power button then repeatedly press volume up]
- [wipe cache partition, advance wipe dalvik cache, battery stat]
- install custom ROM zip from sdcard (with no ERROR reports or problem during flashing)
- reboot into system
still stuck at sony logo.. wait around 1 hour.. nothing happened...
then i remove battery, try to boot into cwm..
success..
but the cwm background pic changed with wording "CWM-based recovery v5.0.2.7 Full (by DooMLoRD)".. not like before.. and i restored back..
the ROM i tried is Pureness build 3 and jjHybrid 3.1.. both give same problem..
check screenshot of my system below.. is there's any problem with my system?
or it is related to odex?
so.. got any idea or possible solution?
or my phone problem itself?
thx in advance...
Click to expand...
Click to collapse
I see that you are not wiping/formatting your data.. Wiping data is essential when installing a custom ROMs or switching ROMs..
Before wiping cache, format your data first!
iamdchosen1 said:
I see that you are not wiping/formatting your data.. Wiping data is essential when installing a custom ROMs or switching ROMs..
Before wiping cache, format your data first!
Click to expand...
Click to collapse
it is not enough to wipe cache, dalvik-cache, battery stat etc? becoz i already done all that through CWM.
and a noob question, how to properly format the data? phone data or sdcard data?
megatpanji said:
try other kernel...
1. Pureness build 3 ,Kernel :Night Elfs ICS Kernel mod
2. jjHybrid 3.1,Kernel Use any of Following
a) STOCK Kernel (No OverClocking)
b) shardul_seth Kernel
c) Night-Elf Kernel
d) Adridu kernel
look at specific thread,you will find the answer.
Click to expand...
Click to collapse
thx but problem above already appeared when i tried to flash pureness build 3 ROM on night-elf kernel..
dualsh0ck said:
it is not enough to wipe cache, dalvik-cache, battery stat etc? becoz i already done all that through CWM.
and a noob question, how to properly format the data? phone data or sdcard data?
Click to expand...
Click to collapse
The data has to be wiped when you install a custom ROM.. Since some of the data can cause troubles to the new ROM you have installed..
I advice you to do the following when installing a ROM.. Follow step by step..
- Flash the kernel first
- Boot into CWM mode by pressing 'volume down'
- wipe data/factory reset
- wipe cache partition
- wipe dalvik cache
- install custom zip from sd card i.e your custom ROM zip file
- reboot now
there you go now!
PS. Data formatting has to be done in CWM mode and it will not erase your sd data! So relax!
Also, press 'Thanks' if I helped you!
CHEERS!
iamdchosen1 said:
The data has to be wiped when you install a custom ROM.. Since some of the data can cause troubles to the new ROM you have installed..
I advice you to do the following when installing a ROM.. Follow step by step..
- Flash the kernel first
- Boot into CWM mode by pressing 'volume down'
- wipe data/factory reset
- wipe cache partition
- wipe dalvik cache
- install custom zip from sd card i.e your custom ROM zip file
- reboot now
there you go now!
PS. Data formatting has to be done in CWM mode and it will not erase your sd data! So relax!
Also, press 'Thanks' if I helped you!
CHEERS!
Click to expand...
Click to collapse
according to my first post. here
dualsh0ck said:
step i do to flash rom:
- backup in CWM
- reboot into recovery [power button then repeatedly press volume up]
- [wipe cache partition, advance wipe dalvik cache, battery stat]
- install custom ROM zip from sdcard (with no ERROR reports or problem during flashing)
- reboot into system
Click to expand...
Click to collapse
i've already done all wiping in CWM. but still stuck at sony logo.maybe i'll try some other kernel for jjhybrid3.1
Did you tried what I said?
Sent from my MT11i using xda premium
iamdchosen1 said:
Did you tried what I said?
Sent from my MT11i using xda premium
Click to expand...
Click to collapse
one thing.. if i already used custom kernel and i want to change to another custom kernel.. can i just flash new custom kernel on the old custom kernel?
i have suave kernel now.. and i want to change to alliance kernel..
dualsh0ck said:
one thing.. if i already used custom kernel and i want to change to another custom kernel.. can i just flash new custom kernel on the old custom kernel?
Click to expand...
Click to collapse
Yes.
after flashing Alliance1.4 kernel.. my phone got error message "com.android.phone has stopped". what happened?
as before, i just reflash to stock fw.. or there is another solution?
dualsh0ck said:
after flashing Alliance1.4 kernel.. my phone got error message "com.android.phone has stopped". what happened?
as before, i just reflash to stock fw.. or there is another solution?
Click to expand...
Click to collapse
I don't know why you're getting so much errors?!
I flashed everything on one go and all were just fine to work!
Please tell me your exact process of doing all this?
iamdchosen1 said:
I don't know why you're getting so much errors?!
I flashed everything on one go and all were just fine to work!
Please tell me your exact process of doing all this?
Click to expand...
Click to collapse
before this with alliance1.1 and suave6 kernel work with no probs.
must i tell this in every reply?
this is the exact step doing all of this..
flash kernel via fastboot thru command prompt window..
and flash rom thru cwm with this step..
- reboot into recovery [power button then repeatedly press volume up]
- [wipe data/factory reset,cache partition, advance wipe dalvik cache, battery stat]
- install custom ROM zip from sdcard (with no ERROR reports or problem during flashing)
- reboot into system
and chill bro. i have problem here, and i ask about it because i dont know what to do.
and fastboot folder must placed in android-sdk folders or it is not necessary?
bump
Are you sure the kernels are compatible with the custom ROM you are using? Usually the developer suggests some ROMs. Also, you might need a different baseband for the kernels you are using. Which ROM are you using? Some have extra steps you have to perform.
Sent from my MT11i using xda app-developers app
Only boot.img has to be placed in android sdk folder.
Sent from my MT11i using xda app-developers app
Sorry I'm not awake today. Boot.img must be in android sdk and only the fastboot.exe file. I doubt it's got anything to do with that though, if you can successfully flash kernels.
Sent from my MT11i using xda app-developers app
Vampirmaniac said:
Are you sure the kernels are compatible with the custom ROM you are using? Usually the developer suggests some ROMs. Also, you might need a different baseband for the kernels you are using. Which ROM are you using? Some have extra steps you have to perform.
Sent from my MT11i using xda app-developers app
Click to expand...
Click to collapse
yup i'm sure.. because i want to flash night-elf kernel + jjhybrid3.1 rom..
as for now i use stock rom because can't successfully flash any custom rom..
my baseband 8x55A-AAABQOAZM-203028G-72.. it is also related?
HEY EVEN I HAD THE SAME SAME PROBLEM BEFORE...its was that i followed all the steps n still was stuck at bootlogo
even if i tried to go to recovery n flash the rom again , it simply said CANNOT MOUNT SD CARD.
So I tried to format my sd card using SDFORMATTER 3.1 and flashed the om again and :laugh: it WORKED
SO BASICALLY TRY TO FORMAT THE SD CARD USING SD FORMATTER software and not the windows default one.
IT WORKED FOR ME AND HOPE IT WILL FOR YOU ALSO
SD CARD FORMATTER 3.1 link google it
hey guys... really need help here...
i just successful UNLOCKED Bootloader,CWM and install custom kernel..
After fastboot the custom kernel (suave) then enter the CWM to flash custom ROM(Xperia_Ice_Cream_Pureness_build_6.00_NeoV)... wipe all data and other common step.. then i reboot the system
My phone get boot loop after that. So i remove the battery then enter the CWM again.. but the colour change to red and detect my phone as "xperia ARC".. plzzz.. i really stuck here

[Q] Problems with the installation of real ics 6.0

Hello comunity, First of all, I have a WT19 with ICS original + root +version .587. (I have block boot)
I do this, when i try to install the real ics:
1. Mode cwm
2. wipedata/factory reset
3. wipe cache partition
4. Go to advanced: Wipe dalvik cache y (not BATTERY STATS, i don´t know why)
5. Go to mounts and storage: format /cache, format/data y format /system (no FORMAt /SD-EXT, i don't know why too)
6. Next I install zip from sdcard, choose zip from sdcard y begin the installation of realics6.zip.
7. Next i go to REBOOT SYSTEM NOW.
NOTE: I do all of this, but THE BIG PROBLEM:crying:, is when my phone start with the OS, just stay in the image of SONY. And restart and restart....and just stay in the image of sony.
Someone can help me?? Thks a lot!
Usually, i only wipe data, cache, dalvik, n battery.
Never format system. N never got any problem.
Just reflash stock .ftf
Sent from my Nokia 3310 using Tapatalk 2
chepoz said:
Usually, i only wipe data, cache, dalvik, n battery.
Never format system. N never got any problem.
Just reflash stock .ftf
Sent from my Nokia 3310 using Tapatalk 2
Click to expand...
Click to collapse
Funny, the only thing that i restore is system..
Remember that you need to be on stock ICS fw
boliviano12 said:
Funny, the only thing that i restore is system..
Remember that you need to be on stock ICS fw
Click to expand...
Click to collapse
What's funny?
Sent from my Nokia 3310 using Tapatalk 2
Did you flash the custom kernel???
Echelonex said:
Did you flash the custom kernel???
Click to expand...
Click to collapse
He said he has a locked bootloader, and the Real ICS is supposed to work on both locked and unlocked bootloaders, you even have an option to pick whether yours is locked or unlocked during installation.
I have the same problem. My LWW device has blocked bootloader (unlock not allowed), and was running rooted stock 4.0.4 .587 prior to update.
After installing Real ICS r5.2 I'm stuck on the Sony logo.
After installing Real ICS r6 it gets stuck in a bootloop (Sony logo-->Boot animation-->Restart)
Luckily I can still boot into recovery and restore my rooted stock ICS. Later I will try flashing the Real ICS Lite version, though I really wanted the full version.
Since I cannot post in the development section I'm asking you guys to help, please.
Additional info:
- I wiped user data, cache, dalvik cache before updating.
- I don't want to unlock my bootloader (again the Real ICS is supposed to work on locked BL too)
- Yes my stock ICS was rooted, had CWM Recovery installed, backups created.
EDIT: Problem solved, apparently you need to manually format /system along with /data, /cache and /dalvik cache before flashing!

[ROM] Stock Deodexed Rooted 14.1.B.1.510 [08/09]

This is a flashable Stock 14.1.B.1.510 Taiwan rom. It is Deodexed and rooted. Install it in CWM. You can use this as a base for your rom. No need to ask. Share it and modify it and lets start some custom roms.
Download​
It is great to be the first reply
Great Job
Really good news...
Sent from my C6802 using Tapatalk 2
m3dd0g said:
This is a flashable Stock 14.1.B.1.510 Taiwan rom. It is Deodexed and rooted. Install it in CWM. You can use this as a base for your rom. No need to ask. Share it and modify it and lets start some custom roms.Download​
Click to expand...
Click to collapse
Thanks. Tell and how to receive the worker CWM Recovery?
Feodorus 4PDA said:
Thanks. Tell and how to receive the worker CWM Recovery?
Click to expand...
Click to collapse
First unlock your bootloader then flash via fastboot this kernel. When booting press volume up and you are in recovery.
m3dd0g said:
First unlock your bootloader then flash via fastboot this kernel. When booting press volume up and you are in recovery.
Click to expand...
Click to collapse
It's OK, thanks. I thought for Locked Bootloader.
Feodorus 4PDA said:
It's OK, thanks. I thought for Locked Bootloader.
Click to expand...
Click to collapse
the main problem is lockbootloader
thank you m3dd0g !!!
start a revolution for Rom Cook
can i flash 475 HK ?
Will it wipe DATA and/or Internal Storage ?
I tried to flash, but the program said "waiting for device".
What does this mean, I don't have unlock bootloader? or I'm on 475?
satawat.thongsawat said:
I tried to flash, but the program said "waiting for device".
What does this mean, I don't have unlock bootloader? or I'm on 475?
Click to expand...
Click to collapse
yes you need to have unlocked bootloader ( make sure you backup TA before unlocking ) then flash this recovery and flash the rom in cwm.
---------- Post added at 03:19 PM ---------- Previous post was at 03:18 PM ----------
hey mate, tried flashing the rom via krabappel2548's kernel.. in twrp it gives an error of updater binary and it flashes fine in cwm. booting now thanks!
m3dd0g said:
First unlock your bootloader then flash via fastboot this kernel. When booting press volume up and you are in recovery.
Click to expand...
Click to collapse
Thanks for cookrom first ZU
GOF007 said:
Will it wipe DATA and/or Internal Storage ?
Click to expand...
Click to collapse
it will wipe system only. just do a wipe fty reset, wipe cache and dalvik. i did /data too.. and flash the rom.
no need to wipe internal sdcard and the rom will not wipe internal data
androidindian said:
it will wipe system only. just do a wipe fty reset, wipe cache and dalvik. i did /data too.. and flash the rom.
no need to wipe internal sdcard and the rom will not wipe internal data
Click to expand...
Click to collapse
I have just finished flash, all 16Gb of data in sdcard are lost in the clean , of course ex_sdcard not deleted
big said:
I have just finished flash, all 16Gb of data in sdcard are lost in the clean , of course ex_sdcard not deleted
Click to expand...
Click to collapse
Impossible.. I've flashed the rom a few times and it does not wipe data on sdcard.. Did you do it manually in recovery?
Sent from my HTC One using XDA Premium 4 mobile app
I have a rom ready but devdb gives server error.. I'll post it asap
Sent from my C6603 using xda app-developers app
In CWM the external SD isn't found and in TWRP I can't flash any rom, flashing fails right at the beginning, it starts format system and then it says, E: error executing udater binary in zip '/exter... the rest in this row isn't readable
error flashing zip '/external_sd/rom/stock_ C68
updating partition details
Mucho79 said:
In CWM the external SD isn't found and in TWRP I can't flash any rom, flashing fails right at the beginning, it starts format system and then it says, E: error executing udater binary in zip '/exter... the rest in this row isn't readable
error flashing zip '/external_sd/rom/stock_ C68
updating partition details
Click to expand...
Click to collapse
Twrp has issues for now.. Use Cwm.. Put the file inside your internal storage.. Go to install.. Select 0..zip file.. Flash away
Sent from my HTC One using XDA Premium 4 mobile app

(Q) phone stuck in bootloop after flashing. Download and recovery mode working.

tetakpatak said:
Please quote my post and copy&paste whole text into some help thread for your phone, it is better idea as we are now getting off topic here. I'll try to help you there.
Format /system is done in recovery mode under "mount and storage" then after that you can restore your nandroid if it is done with the same recovery you use now. If you're on PhilZ 6, it usually can restore also CWM 6 backups.
Click to expand...
Click to collapse
What does format system do? And please help me load sentinel rom. That's the one I was gonna do.
Okay now for the question... I was running stock 4.1.2 with siyah kernel 6.0 b5. Then I decided to install philz kernel, but ended up in bootloop. Then I tried flashing dorimanx but still in bootloop. All the while I wiped everything before flashing.
Now im stuck as I can boot into recovery via any kernel but ultimately phone is stuck.
What to do?
And can anyone give me steps to install sentinel rom from this stage?
Sent from my Nexus 4 using xda app-developers app
AndroidReborn said:
What does format system do? And please help me load sentinel rom. That's the one I was gonna do.
Okay now for the question... I was running stock 4.1.2 with siyah kernel 6.0 b5. Then I decided to install philz kernel, but ended up in bootloop. Then I tried flashing dorimanx but still in bootloop. All the while I wiped everything before flashing.
Now im stuck as I can boot into recovery via any kernel but ultimately phone is stuck.
What to do?
And can anyone give me steps to install sentinel rom from this stage?
Click to expand...
Click to collapse
Mate, sorry for waiting, I was out of home. We will get your ROM back as soon as the phone boots again.
Don't worry, it doesn't sound serious so far. We have recovery and download mode (so topic name "nothing works" isn't really correct)
Formatting /system wipes all data from the system partition (so your system will be gone then) and it is important to do before installing new ROMs (essencially important for KitKat). It can't do any harm. As you have tried to install other kernels and didn't work we should check first what did you try to flash so far and it didn't boot? Is that what you wrote all what you have tried?
Now let me know please which recovery do you have now and is it the same version like when you have created your nandroid backup? If the recovery is the same, I would indeed try to restore nandroid backup right after wiping /system. Before you wipe the system just let me know: can you use ADB? If yes, check do you have ADB connection in the recovery mode?
tetakpatak said:
Mate, sorry for waiting, I was out of home. We will get your ROM back as soon as the phone boots again.
Don't worry, it doesn't sound serious so far. We have recovery and download mode (so topic name "nothing works" isn't really correct)
Formatting /system wipes all data from the system partition (so your system will be gone then) and it is important to do before installing new ROMs (essencially important for KitKat). It can't do any harm. As you have tried to install other kernels and didn't work we should check first what did you try to flash so far and it didn't boot? Is that what you wrote all what you have tried?
Now let me know please which recovery do you have now and is it the same version like when you have created your nandroid backup? If the recovery is the same, I would indeed try to restore nandroid backup right after wiping /system. Before you wipe the system just let me know: can you use ADB? If yes, check do you have ADB connection in the recovery mode?
Click to expand...
Click to collapse
Will it wipe the internal memory? Or the rom in the phone?
I have cwm based recovery v. 6.0.1.2. Yes I used it to make the backup.
Checking for adb.. How do I do it? .
Sent from my Nexus 4 using xda app-developers app
AndroidReborn said:
Will it wipe the internal memory? Or the rom in the phone?
I have cwm based recovery v. 6.0.1.2. Yes I used it to make the backup.
Checking for adb.. How do I do it?
Click to expand...
Click to collapse
Hi! Internal memory usually shouldn't get wiped by formatting /system, as it is "storage", not part of the system. I would give a try, wipe all: data/factory reset, cache, dalvik cache (advanced) and format /system (mounts and storage). Then back to the main menu --> backup & restore --> restore from (internal or external memory where your nandroid is saved) and choose your backup. It should reboot normally then.
tetakpatak said:
Hi! Internal memory usually shouldn't get wiped by formatting /system, as it is "storage", not part of the system. I would give a try, wipe all: data/factory reset, cache, dalvik cache (advanced) and format /system (mounts and storage). Then back to the main menu --> backup & restore --> restore from (internal or external memory where your nandroid is saved) and choose your backup. It should reboot normally then.
Click to expand...
Click to collapse
Thanks for helping, but I ended up downloading the stock rom and flashing it. Everything was normal. Then I installed cm10.2 so everything's great now. Thanks!
Sent from my Nexus 4 using xda app-developers app
Cool, @AndroidReborn! Now you can install your old ROM again and restore nandroid. Keep that stock FW saved on your PC, so if your phone gets ever again soft-bricked, no problem to revive it again.
I am wondering how nobody here responsed your help prompt, we have in i9000 help threads always handfull people of experience and skills who are ready to help in need. And there are double amount of the SGS2 units sold around the world.... strange.
tetakpatak said:
Cool, @AndroidReborn! Now you can install your old ROM again and restore nandroid. Keep that stock FW saved on your PC, so if your phone gets ever again soft-bricked, no problem to revive it again.
I am wondering how nobody here responsed your help prompt, we have in i9000 help threads always handfull people of experience and skills who are ready to help in need. And there are double amount of the SGS2 units sold around the world.... strange.
Click to expand...
Click to collapse
No idea. The people seem pretty 'busy'. Thanks for helping. Just one teeny tiny last question.. How do I install cm11 or any kitkat rom over this? Cwm is 6.0.4.5 so it's compatible...
Sent from my Nexus 4 using xda app-developers app
If you want to flash kitkat, the first thing you need to do is flash a kitkat compatible CWM (v6.0.4.7). If you try to flash KK with an 'older' CWM, you'll get 'installation aborted....error status 7' or something similar........
I'm currently running @infected_s KK build, and in the OP, you will find download links for the correct CWM, ROM and GApps files.......
Sent from my Infected KitKat bar.....
keithross39 said:
If you want to flash kitkat, the first thing you need to do is flash a kitkat compatible CWM (v6.0.4.7). If you try to flash KK with an 'older' CWM, you'll get 'installation aborted....error status 7' or something similar........
I'm currently running @infected_s KK build, and in the OP, you will find download links for the correct CWM, ROM and GApps files.......
Sent from my Infected KitKat bar.....
Click to expand...
Click to collapse
6.0.4.5 is compatible? I think so ......
Sent from my Nexus 4 using xda app-developers app
I've always read....not.....
In any case, probably best not to risk it......
6.0.4.7 is DEFINITELY KK compatible.... and it'd take a couple of seconds to flash.........
Sent from my Infected KitKat bar.....
AndroidReborn said:
No idea. The people seem pretty 'busy'. Thanks for helping. Just one teeny tiny last question.. How do I install cm11 or any kitkat rom over this? Cwm is 6.0.4.5 so it's compatible...
Click to expand...
Click to collapse
Yes, mate, CWM 6.0.4.5 is capable of flashing KitKat.
It is usually always the same:
download your ROM zip and compatible Gapps
check in the phone (or PC) if the zips are corrupted through download (if they open after clicking them, they are fine)
move the zips to the folder you will flash it from (if you use PC to flash zips with ADB sideload, put them in the sdk/platform-tools folder)
make nandroid backup of your presently used ROM
wipe data/factory reset
wipe cache
wipe dalvik cache (advanced)
format /system (under mount and storage)
flash ROM.zip
flash Gapps
reboot
It is in general always good to read in the development thread of the ROM you attend to flash in the opening post which Gapps are recommended, or if there is some unusual order of flashing (sometimes, developers recommend reboot system after flashing ROM, and after that going to recovery and flash Gapps zip.
Some KitKat ROMs struggle with root access by using Superuser, so SuperSU should be flashed. If SuperSU app from Play Store gives errors by updating binary, you should uninstall SuperSU app then, find in the Chainfire's thread the compatible UPDATE-SuperSu.zip (version for your phone), flash its zip in the recovery, install SuperSU app, update binary (either "normal" or "through CWM/TWRP")

Categories

Resources