Hi all,
I recently decided to put a custom ROM on my DX.
I was on stock ROM (of course) with JB 2.20.401.5
To get my new ROM, I did :
- unlock bootloader (hboot 1.25 with windroid tool) --> OK, "unlocked"
- install custom recovery --> OK, TWRP 2.6.3 installed
- full wipe (factory reset in recovery) --> OK
- flash ROM (mySENSEdx+ RC3.0) --> "failed", so I had to uncheck "zip file signature verification" to start install
- install finished
- reboot bootloader --> OK
- flash boot.img with "Install Boot.img.bat" file --> OK
- reboot --> OK
- When phone started, I'm still on stock ROM, with "low internal memory" message (guess it is because of flashing boot.img)
So, question is : what am I doing wrong or forgetting?
P.S. I forgot : I also tried to flash superuser.zip to get root but It failed. Superuser app is installed but I don't have root though
Change recovery , use TWRP 2.5 !!!
pirlouit2 said:
Hi all,
I recently decided to put a custom ROM on my DX.
I was on stock ROM (of course) with JB 2.20.401.5
To get my new ROM, I did :
- unlock bootloader (hboot 1.25 with windroid tool) --> OK, "unlocked"
- install custom recovery --> OK, TWRP 2.6.3 installed
- full wipe (factory reset in recovery) --> OK
- flash ROM (mySENSEdx+ RC3.0) --> "failed", so I had to uncheck "zip file signature verification" to start install
- install finished
- reboot bootloader --> OK
- flash boot.img with "Install Boot.img.bat" file --> OK
- reboot --> OK
- When phone started, I'm still on stock ROM, with "low internal memory" message (guess it is because of flashing boot.img)
So, question is : what am I doing wrong or forgetting?
P.S. I forgot : I also tried to flash superuser.zip to get root but It failed. Superuser app is installed but I don't have root though
Click to expand...
Click to collapse
If the installation says ''failed'' it probably didn't flashed properly. Redownload rom and try again. And the internal memory problem is because of the failed installation, the boot.img has nothing to do with the phone's memory
Have you tried to format system before you installed ROM? I do it every time I flash a new ROM, just to be sure...
abatt said:
Change recovery , use TWRP 2.5 !!!
Click to expand...
Click to collapse
TWRP 2.6.3.0 works good, never had any problems with flashing, wiping and backups
GtrCraft said:
If the installation says ''failed'' it probably didn't flashed properly. Redownload rom and try again. And the internal memory problem is because of the failed installation, the boot.img has nothing to do with the phone's memory
Click to expand...
Click to collapse
I tried to redownload. I also tried with fullmix ROM. Same thing.
I thought that boot.img modified boot partition. Maybe I was wrong
dansou901 said:
Have you tried to format system before you installed ROM? I do it every time I flash a new ROM, just to be sure...
Click to expand...
Click to collapse
Will try again with TWRP 2.5 and wiping system. Stay tuned...
Aaaaaaaaannnnnnnndddd............ working.
Thanks to all of you, guys.
Related
Hi folks,
I'm trying to get a new custom recovery on my phone. Im on FW 2.3.5.
I've downloaded Rom Manager, and all looks fine. When i try to boot into recovery mode to install a custom rom it doesnt say cwm recovery... it says Android recovery.... and i cant install a custom rom from there. Yes. My phone is rooted, and i granted Rom Manager SU access
It says in red..... E:failed to verify whole-file signature
E:signature verification failed
I'm sure if i first upgrade my FW to ICS or JB then there would be no problem.
However. Im affraid that if i update, my touch wont work. I broke my phone 2 months ago, and got it repaired. But the touch wouldnt work unless they downgraded it to 2.3.5. (a mainboard issue due to custom rom. They said)
I really want to try to have a custom rom and see if the touch works in here, or if im stuck using FW 2.3.5
Do i need a new kernel where the CWM recovery is already included or what?
Model: GT-I9100
Current kernel: XWKI8
Edit
Is it possible for me to flash with a custom rom differently?
Maybe connect to Odin and press the "phone" button and choose a custom rom? Or another program.
Sorry if this is a stupid question, but im kinda new to this
AlcoD said:
Hi folks,
I'm trying to get a new custom recovery on my phone. Im on FW 2.3.5.
I've downloaded Rom Manager, and all looks fine. When i try to boot into recovery mode to install a custom rom it doesnt say cwm recovery... it says Android recovery.... and i cant install a custom rom from there. Yes. My phone is rooted, and i granted Rom Manager SU access
It says in red..... E:failed to verify whole-file signature
E:signature verification failed
I'm sure if i first upgrade my FW to ICS or JB then there would be no problem.
However. Im affraid that if i update, my touch wont work. I broke my phone 2 months ago, and got it repaired. But the touch wouldnt work unless they downgraded it to 2.3.5. (a mainboard issue due to custom rom. They said)
I really want to try to have a custom rom and see if the touch works in here, or if im stuck using FW 2.3.5
Do i need a new kernel where the CWM recovery is already included or what?
Model: GT-I9100
Current kernel: XWKI8
Click to expand...
Click to collapse
Don't use ROM Manager, as it is not fully compatible with our phone.
You have to flash a kernel containing the CWM recovery you want/need, or alternatively you can flash only the (temporaily) CWM recovery.
Have a lok here => http://forum.xda-developers.com/showthread.php?p=28178105
In first post Method 1 > Instruction 2.
Just download and flash "cwm-touch-6.0.1.2-i9100.zip" in stock recovery:
1. Put the previously downloaded cwm-touch-6.0.x.x-i9100.zip file on your external sd card.
2. Boot into stock recovery (volume up+home+power), and select "apply update from external storage". Now select the cwm-touch-6.x.x.x-i9100.zip file you copied in previous step (this step gives a temporary flash that will disappear after reboot)
You get CWM recovery interface (this custom recovery is temporary, not permanent)
3. Inside CWM, select "install zip from sdcard". Then, select "choose zip from sdcard". Now, scroll down to the custom ROM zip file and hit power button to install it.
Good luck !
It_ler said:
Don't use ROM Manager, as it is not fully compatible with our phone.
You have to flash a kernel containing the CWM recovery you want/need, or alternatively you can flash only the (temporaily) CWM recovery.
Have a lok here => http://forum.xda-developers.com/showthread.php?p=28178105
In first post Method 1 > Instruction 2.
Just download and flash "cwm-touch-6.0.1.2-i9100.zip" in stock recovery:
1. Put the previously downloaded cwm-touch-6.0.x.x-i9100.zip file on your external sd card.
2. Boot into stock recovery (volume up+home+power), and select "apply update from external storage". Now select the cwm-touch-6.x.x.x-i9100.zip file you copied in previous step (this step gives a temporary flash that will disappear after reboot)
You get CWM recovery interface (this custom recovery is temporary, not permanent)
3. Inside CWM, select "install zip from sdcard". Then, select "choose zip from sdcard". Now, scroll down to the custom ROM zip file and hit power button to install it.
Good luck !
Click to expand...
Click to collapse
I found a new kernel and now i have CWM.
Thanks a lot for the fast reply
Edit
I was right. The touch wont work on new rom.
Now i just have to test loads of roms to see which ones work
Hi friends, my Xperia ray stuck at boot loop, which was stock ICS non rooted devices,
For that flashed gb firmware using flashtool, after that its worked well,
then I began root,
-bootloader unlocked - Success
-Rooting for firmware(4.0.2.A.0.62) - Failed, (with this method point No-2a,
-Then, flashed a ICS kernel on GB firmware(4.0.2.A.0.62) - Successkernel taken From this thread
-After flashing kernel flashed a ROM via CWM - Success Flashed ROM thread
-then pressed power button to boot the devise, its showing old GB Boot logo, and stuck at boot loop
My question is..
-For flashing kernel and ROM is required Root on stock?, but i have unlocked bootloader only, due to failed to root
-then how to root device on GB firmware
-or please explain in your way
Did you do the correct wipes before installing the Rom???
Sent from my SK17i using Tapatalk 2
thippesh said:
Hi friends, my Xperia ray stuck at boot loop, which was stock ICS non rooted devices,
For that flashed gb firmware using flashtool, after that its worked well,
then I began root,
-bootloader unlocked - Success
-Rooting for firmware(4.0.2.A.0.62) - Failed, (with this method point No-2a,
-Then, flashed a ICS kernel on GB firmware(4.0.2.A.0.62) - Successkernel taken From this thread
-After flashing kernel flashed a ROM via CWM - Success Flashed ROM thread
-then pressed power button to boot the devise, its showing old GB Boot logo, and stuck at boot loop
My question is..
-For flashing kernel and ROM is required Root on stock?, but i have unlocked bootloader only, due to failed to root
-then how to root device on GB firmware
-or please explain in your way
Click to expand...
Click to collapse
First: you can't root stock gb .62 LINK
Which gb rom do you want to use?
thippesh said:
Hi friends, my Xperia ray stuck at boot loop, which was stock ICS non rooted devices,
For that flashed gb firmware using flashtool, after that its worked well,
then I began root,
-bootloader unlocked - Success
-Rooting for firmware(4.0.2.A.0.62) - Failed, (with this method point No-2a,
-Then, flashed a ICS kernel on GB firmware(4.0.2.A.0.62) - Successkernel taken From this thread
-After flashing kernel flashed a ROM via CWM - Success Flashed ROM thread
-then pressed power button to boot the devise, its showing old GB Boot logo, and stuck at boot loop
My question is..
-For flashing kernel and ROM is required Root on stock?, but i have unlocked bootloader only, due to failed to root
-then how to root device on GB firmware
-or please explain in your way
Click to expand...
Click to collapse
Here is what to do -
1. Make sure that you are on an ICS Kernel. If not, use the command fastboot -i 0x0fce flash boot boot.img
2. Copy ROM to SD Card.
3. Boot into CWM and select "Wipe data/factory reset" and "Wipe cache partition". Then go to advanced and wipe dalvik cache and battery stats.
4. MOST IMPORTANT - Go to mounts and storage and select "Format /system".
5. Choose "Install Zip from sd card."
6. Install the Rom and enjoy a blazing fast Xperia
thippesh said:
Hi friends, my Xperia ray stuck at boot loop, which was stock ICS non rooted devices,
For that flashed gb firmware using flashtool, after that its worked well,
then I began root,
-bootloader unlocked - Success
-Rooting for firmware(4.0.2.A.0.62) - Failed, (with this method point No-2a,
-Then, flashed a ICS kernel on GB firmware(4.0.2.A.0.62) - Successkernel taken From this thread
-After flashing kernel flashed a ROM via CWM - Success Flashed ROM thread
-then pressed power button to boot the devise, its showing old GB Boot logo, and stuck at boot loop
My question is..
-For flashing kernel and ROM is required Root on stock?, but i have unlocked bootloader only, due to failed to root
-then how to root device on GB firmware
-or please explain in your way
Click to expand...
Click to collapse
The thread you referenced contains both a GB kernel and an ICS kernel. Make sure you get the right one. It looks to me like you flashed the GB kernel and you get a boot loop because the ICS ROM and the GB kernel are incompatible. Here is a list of kernels: http://forum.xda-developers.com/showpost.php?p=36177584&postcount=2
Make sure that you flash the kernel with fastboot and then flash the ROM, wipe cache and dalvik cache and then reboot.
Thank you friends
Now its working fine
Sent from my One V using xda app-developers app
Hey guys
I'm trying to flash my S II I9100G with cMIUI, which doesn't work. The phone gets stuck during booting right after the installation. I've been messing around with this problem for a couple of hours by now, been googling a lot and yet I have not found a solution.
What I did in order to flash the ROM:
1) I installed the latest German stock ROM (ICS) using Odin.
2) I followed this tutorial (root using SU-BB-Installer.zip and flash CWM recovery kernel 6.0.1.2 via kTool): http://forum.xda-developers.com/showthread.php?t=2065581 So far everything works fine. I have root access now.
3) Downloaded the cMIUI 2.10.19 zip from http://forum.xda-developers.com/showthread.php?t=1804619
4) When I tried to flash cMIUI from Recovery and toogle signature verification "on", it told me "signature verification failed". I ignored that message and installed it anyway.
5) Installation ran smoothly. After finishing it, the phone wanted to reboot. It now got stuck in the booting screen. I can not get the ROM booted.
I don't think it's cMIUI-caused, because I tried to flash a clean CM10 and still had the same problem (even though it didn't fail signature verification). Here are some more things I tried:
- installed clean stock ROM via Odin, again. Then followed all above steps exactly as described above, except for using Odin for flashing CWM Recovery instead of kTool
- again, clean stock ROM. After rooting, I then tried to install cMIUI via ROM Manager v5.5.2.3. Unfortunately, ROM Manager doesn't identify CWM recovery and keeps asking me to install the Recovery-System with ROM Manager. When I try that, there apparently "is no official CWM Recovery available" for my model. So, ROM Manager is no option
As described in the following thread, I can not use the ClockworkMod Recovery 6.0.1.2 kernel on aosp based ROMs like cMIUI and CM: http://forum.xda-developers.com/showthread.php?t=1631934 So that probably is the cause of my problem. Can you tell me what kernel I can use, instead? Or is there another way to flash that ROM? Via Odin, for example...
Thanks for your help in advance. Very much appreciated!!
Regards,
Daniel
What Codeworkx is saying in that thread is, that you cannot use that kernel when you are already on a aosp based rom. So you can use that recovery.
Something you didn't mention, did you do a full wipe from within the recovery? If you didn't do that, then thats probably the source of your problems.
1. Flash a stock rom true Odin.
2. Flash the recovery (you don't need to root your rom after)
3. Wipe system/factory reset
4. Wipe cache.
5. Download the rom again to make sure you the download went well.
6. Toggle signature verification off.
7. Flash Miui
8. Reboot and wait.
Lennyz1988 said:
What Codeworkx is saying in that thread is, that you cannot use that kernel when you are already on a aosp based rom. So you can use that recovery.
Something you didn't mention, did you do a full wipe from within the recovery? If you didn't do that, then thats probably the source of your problems.
1. Flash a stock rom true Odin.
2. Flash the recovery (you don't need to root your rom after)
3. Wipe system/factory reset
4. Wipe cache.
5. Download the rom again to make sure you the download went well.
6. Toggle signature verification off.
7. Flash Miui
8. Reboot and wait.
Click to expand...
Click to collapse
Thank you so much! Wiping helped. :good: Why didn't I try that before :silly:
Awesome, now I can finally enjoy cMIUI. It's really great! (except for crashing galery/camera app when starting cam from lock screen. but who cares )
Thanks dude! :highfive:
Hello,
I have just successfully rooted my S3 using "Heimdall Frontend" following the tutorial here:
However I found initially when leaving "No Reboot" unchecked I was unable to boot into CWM until I checked no Reboot then once the flash was complete I manually went into CWM by holding the recovery keys.
I then installed the SuperSu zip file on my SD card and rebooted my phone into it's newly rooted state.
HOWEVER.. I went to boot my S3 into CWM Recovery to flash a custom ROM and I'm only able to boot into the standard android recovery.. It says on the tutorial that versions 4.1.2+ need to tick "No reboot" otherwise the newer firmware simply wipes over CWM recovery every reboot..
I was under the impression that CWM was there as a safety net in case my phone ever played up and needed to be unrooted?
read this http://forum.xda-developers.com/showthread.php?t=1911726
UPDATE: After using ROM Manager to boot into CWM to create a backup, it gave the option to "Fix reflashing to original recovery after reboot"
Is it a good idea to have CWM permanently flashed as my recovery? How would I revert back to the stock recovery should I want to unroot the device?
Thanks
iamtherealmungo said:
UPDATE: After using ROM Manager to boot into CWM to create a backup, it gave the option to "Fix reflashing to original recovery after reboot"
Is it a good idea to have CWM permanently flashed as my recovery? How would I revert back to the stock recovery should I want to unroot the device?
Thanks
Click to expand...
Click to collapse
You need to read the faqs and guides its all posted and has been asked multiple times .
Hey Guys,
I'm having a bit of an issue. Currently I was running STOCK Android 4.3 JB, have been for a while, it started to get a bit slow & I was wanting to fresh install, but also try out a 5.0 lollipop ROM. I've rooted my phone in the past and installed custom ROMs before without a problem (Revolution Remix + Cyanogenmod 11), however, I decided to try Liquidsmooth 5.0 lollipop. i followed this video,
https://www.youtube.com/watch?v=QquFDFEEKlI
http://forum.xda-developers.com/galaxy-s3/development/rom-liquidsmooth-lollipop-4-0-b1-t2980477
I downloaded both files and copied them onto my MicroSD card.
I backed up my data (contacts, images, files etc..)
Booted into "Recovery Mode", wiping Cache & factory Reset
When to install from SD, located file and it started reading/installing (sorry can't remember exactly what it did), but during process it failed. I went back into Android (had to setup again), Went and made sure Developer Mode and USB Debugging was on, still didn't work.
Went to make sure CWM was installed/update, which it said it was (possibly from previous custom installs?), tried updating, failed. It said
Went and installed 'SuperSU' from Play store, but got this error.
Decided to try re-install STOCk 4.3 JB, I
made sure USB Debugging was on
loaded Odin 3.07 (or was it 3.09) and loaded 4.3 Firmware under PDA (left everything else as is)
Started and let it do its thing. It finished/PASSED and phone restarted.
i went back into the phone, installed ROM manager & SuperSU again to give it another shot... but same problem again, getting the error above.
I'm not sure what's happened and I'm not sure what "solutions" to search for... anyone have any suggestions?
At this stage I'm thinking of just going back to STOCK 4.3, then maybe try again (either with Liquidsmooth lollipop, or, Slimkat 4.4)
Thanks guys, any help would be super appreciated,
Regards,
~ Dave
Le Widget said:
Hey Guys,
I'm having a bit of an issue. Currently I was running STOCK Android 4.3 JB, have been for a while, it started to get a bit slow & I was wanting to fresh install, but also try out a 5.0 lollipop ROM. I've rooted my phone in the past and installed custom ROMs before without a problem (Revolution Remix + Cyanogenmod 11), however, I decided to try Liquidsmooth 5.0 lollipop. i followed this video,
https://www.youtube.com/watch?v=QquFDFEEKlI
http://forum.xda-developers.com/galaxy-s3/development/rom-liquidsmooth-lollipop-4-0-b1-t2980477
I downloaded both files and copied them onto my MicroSD card.
I backed up my data (contacts, images, files etc..)
Booted into "Recovery Mode", wiping Cache & factory Reset
When to install from SD, located file and it started reading/installing (sorry can't remember exactly what it did), but during process it failed. I went back into Android (had to setup again), Went and made sure Developer Mode and USB Debugging was on, still didn't work.
Went to make sure CWM was installed/update, which it said it was (possibly from previous custom installs?), tried updating, failed. It said
Went and installed 'SuperSU' from Play store, but got this error.
Decided to try re-install STOCk 4.3 JB, I
made sure USB Debugging was on
loaded Odin 3.07 (or was it 3.09) and loaded 4.3 Firmware under PDA (left everything else as is)
Started and let it do its thing. It finished/PASSED and phone restarted.
i went back into the phone, installed ROM manager & SuperSU again to give it another shot... but same problem again, getting the error above.
I'm not sure what's happened and I'm not sure what "solutions" to search for... anyone have any suggestions?
At this stage I'm thinking of just going back to STOCK 4.3, then maybe try again (either with Liquidsmooth lollipop, or, Slimkat 4.4)
Thanks guys, any help would be super appreciated,
Regards,
~ Dave
Click to expand...
Click to collapse
First of all and most important don't use rom manager! it causes more problems than anything else.The best way to install custom roms is to use Cwm,PhilZ or Twrp to install anything!
Flash superSU zip in recovery from here >> http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1 << SuperSU forum here >> http://forum.xda-developers.com/showthread.php?t=1538053 << Technically you should not need to flash SuperSU because nearly all custom roms come with root built in so you could flash a custom recovery then wipe and flash your rom (but I can see you have been having problems doing that)
What you should do is
(1) Flash a custom recovery with Odin (Recommend PhilZ)
(2) Reboot to custom recovery
(3) Wipe phone
(4) Install custom rom (which is already rooted) from Ext SD card
(5) Reboot (If you get bootloop factory reset/ wipe cache
Also to note PhilZ recovery (which I think is better as more options and is based on Cwm) as a option to fix root in settings.
tallman43 said:
First of all and most important don't use rom manager! it causes more problems than anything else.The best way to install custom roms is to use Cwm,PhilZ or Twrp to install anything!
Flash superSU zip in recovery from here >> http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1 << SuperSU forum here >> http://forum.xda-developers.com/showthread.php?t=1538053 << Technically you should not need to flash SuperSU because nearly all custom roms come with root built in so you could flash a custom recovery then wipe and flash your rom (but I can see you have been having problems doing that)
What you should do is
(1) Flash a custom recovery with Odin (Recommend PhilZ)
(2) Reboot to custom recovery
(3) Wipe phone
(4) Install custom rom (which is already rooted) from Ext SD card
(5) Reboot (If you get bootloop factory reset/ wipe cache
Also to note PhilZ recovery (which I think is better as more options and is based on Cwm) as a option to fix root in settings.
Click to expand...
Click to collapse
hi tallman, much appreciated for the reply
For some reason I couldnt get Philz Custom Recovery to work with odin, kept getting an error :/ . So I ended up trying TWRP, which worked, I booted into it then installed Liquidsmooth + gapps, all installed ok, but all up it was the same process you mentioned, which I greatly appreciate.
So running Liquidsmooth 5 now with TWRP recovery, though will likely give Philz recovery a shot down the track
Le Widget said:
hi tallman, much appreciated for the reply
For some reason I couldnt get Philz Custom Recovery to work with odin, kept getting an error :/ . So I ended up trying TWRP, which worked, I booted into it then installed Liquidsmooth + gapps, all installed ok, but all up it was the same process you mentioned, which I greatly appreciate.
So running Liquidsmooth 5 now with TWRP recovery, though will likely give Philz recovery a shot down the track
Click to expand...
Click to collapse
Good to hear it's working Yes it's worth persevering with PhilZ it's a good recovery although Twrp is not bad either:good: