I am trying to install the jellybam 3.0.0 rom and am having no luck. I tried just following inst and that didn't work after about 45 sec the android guy fell over and a red triangle popped up. Then I saw you might have to change to siyah 4.3.3 so I downloaded the zip without micswap and flashed it after the Jellybam rom. Still no luck the rom loaded, but when I rebooted the ics symbol showed up then phone turned of. Can someone tell me how to get this to work. I have the ported version and works fine.
Any help would be greatly appreciated. Also thanks for all you guys and gals do your awsome.
Can't install Jellybam???
fountain79 said:
I am trying to install the jellybam 3.0.0 rom and am having no luck. I tried just following inst and that didn't work after about 45 sec the android guy fell over and a red triangle popped up. Then I saw you might have to change to siyah 4.3.3 so I downloaded the zip without micswap and flashed it after the Jellybam rom. Still no luck the rom loaded, but when I rebooted the ics symbol showed up then phone turned of. Can someone tell me how to get this to work. I have the ported version and works fine.
Any help would be greatly appreciated. Also thanks for all you guys and gals do your awsome.
Click to expand...
Click to collapse
I had the same error....i guess you must be getting a "status 7" error while flashing jellybam.....
I used to run SHOstock3 rom v1.4, and i got the same error while flashing jellybam, so i follwed the method given by one of the experts...
1. I did a factory reset, and flashed jellybam, after which i got a status 7 error...
2. I restored the rom via CWM
3. Flashed siyah v3.4.2 with micswap..
4. since that was siyah ics, i could not use my phone, but i was able to flash jellybam over it.....
5. Im running Jellybam without any bugs...
So basically, you can do a full wipe, flash siyah, and then flash J'bam......else use an older version of siyah like i did....Hope u r problem is solved....
Thanks
Aayush_13 said:
I had the same error....i guess you must be getting a "status 7" error while flashing jellybam.....
I used to run SHOstock3 rom v1.4, and i got the same error while flashing jellybam, so i follwed the method given by one of the experts...
1. I did a factory reset, and flashed jellybam, after which i got a status 7 error...
2. I restored the rom via CWM
3. Flashed siyah v3.4.2 with micswap..
4. since that was siyah ics, i could not use my phone, but i was able to flash jellybam over it.....
5. Im running Jellybam without any bugs...
So basically, you can do a full wipe, flash siyah, and then flash J'bam......else use an older version of siyah like i did....Hope u r problem is solved....
Click to expand...
Click to collapse
Trying now...
Its working
Aayush_13 said:
I had the same error....i guess you must be getting a "status 7" error while flashing jellybam.....
I used to run SHOstock3 rom v1.4, and i got the same error while flashing jellybam, so i follwed the method given by one of the experts...
1. I did a factory reset, and flashed jellybam, after which i got a status 7 error...
2. I restored the rom via CWM
3. Flashed siyah v3.4.2 with micswap..
4. since that was siyah ics, i could not use my phone, but i was able to flash jellybam over it.....
5. Im running Jellybam without any bugs...
So basically, you can do a full wipe, flash siyah, and then flash J'bam......else use an older version of siyah like i did....Hope u r problem is solved....
Click to expand...
Click to collapse
Thanks again for sharing the info very helpful.
did that work
fountain79 said:
Thanks again for sharing the info very helpful.
Click to expand...
Click to collapse
Hi All
Did the method of installing Siyah Kernel and then flashing JellyBam work to resolve "error code 7" issue ??
Hey friend. I formatted cache, system etc. When I tried to install CM9, It says installation aborted. Or when I flashing the kernel, in the past it was coming freeXperia logo, now nothing but senseless lines comes. What should I do ? What should I flash to open my xperia ?
I managed to install a CM9 kernel but still does not install rom. Any help ?
I solved it by installing a new kernel.
hello i'm newbie
Hello there,
I have recently attempted to install a custom ROM on my Xperia U . I rooted using bin4ry , then unlocked bootloader. Everything was fine up to that point. Then I tried to use RecoverX to install CWM. The tool said it was a success, but device could not boot into recovery.It looked like the tool did nothing. I then found a custom kernel by AOKP that had CWM Recovery in it. I flashed and got recovery , but stuck in bootloop. I recovered from this by flashing B.10 stock firmware on my Xperia U using flashtools. I am now looking for ways to install CWM recovery safely.
What's the best way to install CWM in my current situation?
What caused the bootloop I experienced(out of curiosity)?
digar4o said:
Hello there,
I have recently attempted to install a custom ROM on my Xperia U . I rooted using bin4ry , then unlocked bootloader. Everything was fine up to that point. Then I tried to use RecoverX to install CWM. The tool said it was a success, but device could not boot into recovery.It looked like the tool did nothing. I then found a custom kernel by AOKP that had CWM Recovery in it. I flashed and got recovery , but stuck in bootloop. I recovered from this by flashing B.10 stock firmware on my Xperia U using flashtools. I am now looking for ways to install CWM recovery safely.
What's the best way to install CWM in my current situation?
What caused the bootloop I experienced(out of curiosity)?
Click to expand...
Click to collapse
AOKP is not stock rom..
so its kernel is also not based n stok rom...thats why you got bootloop...
just download kernel which is based on sock rom like trancsend kernek...or phantom...
if you have jb then experimenatal kernel will be best....
and use flashtool to flash kernel...it is the easiest way to flash kernel..
all this kernels are prerooted and has cwm 6.x.x recovery.....
you will get this kernels in devlopment section....
Thank you!
Got it working!
I started off by installing transcendence kernel for stock ROMs. That went flawlessly and so I was presented with CWM recovery(which I started by repeatedly pressing Vol- when the transcendence logo comes up). Went to look for a ROM and found MIUI v4 for Xperia U, followed the instructions and flashed with CWM recovery.Very beautiful ROM. I got all my files from the Xperia U Development section.
Thanks for your help and a big thank you to the developers who make this possible. highfive:
digar4o said:
Got it working!
I started off by installing transcendence kernel for stock ROMs. That went flawlessly and so I was presented with CWM recovery(which I started by repeatedly pressing Vol- when the transcendence logo comes up). Went to look for a ROM and found MIUI v4 for Xperia U, followed the instructions and flashed with CWM recovery.Very beautiful ROM. I got all my files from the Xperia U Development section.
Thanks for your help and a big thank you to the developers who make this possible. highfive:
Click to expand...
Click to collapse
Most kernels nowadays have light notification or vibration or borh for the time you need to press the volume button for cwn, if yours does you only need to press it once within 3 seconds.
------------- SOLVED! --------------
Hello all,
First of all I want to say I'm pretty new to flashing ROMs etc.
Currently I'm at stock 4.3 Jellybean and I want to flash my SGS3 to the new CM 11 ROM.
I rooted my phone following this tutorial: vvvvvv.telefoonrooten.nl/samsung/samsung-galaxy-s3-root/ (sorry if its in Dutch, but it uses the CF-Root-SGS3-v6.3 and Odin).
After I rooted I copied both the CM11 ROM and GAPPS to my external SD, I went to recovery and tried to install the new custom ROM but I got an error (status 7) and it was aborted.
Also if I try to reboot it won't boot normally as it should be but it goes back to recovery mode automatically...
I fixed to get back to Jellybean by flashing the stock rom (unrooting?) it via Odin.
Anyone else got the exact same problem as I do and knows a solution to be able to flash CM 11?
Thanks in advance,
Steelbear
Steelbear said:
Anyone else got the exact same problem as I do and knows a solution to be able to flash CM 11?
Click to expand...
Click to collapse
please read the thirst post in a rom/kernel/whatever thread. and maybe if you havent done it already you should also read the stickies in general section.
FAQ (Read before post !!)
- If you obtain Error 7 when you tried to install ROM in CWM or TWRP
Install the latest version of CMW or TWRP
Click to expand...
Click to collapse
BTW latest philz touch recovery works too
Since you went back to stock and you already know how to root, I suggest you go to Play Store and download ROM Manager to help you install latest CWM recovery on your device.
Or you can simply go to CWM website, pick the version of the recovery for your phone and flash it via Odin.
Hope it helps.
Steelbear said:
Hello all,
First of all I want to say I'm pretty new to flashing ROMs etc.
Currently I'm at stock 4.3 Jellybean and I want to flash my SGS3 to the new CM 11 ROM.
I rooted my phone following this tutorial: vvvvvv.telefoonrooten.nl/samsung/samsung-galaxy-s3-root/ (sorry if its in Dutch, but it uses the CF-Root-SGS3-v6.3 and Odin).
After I rooted I copied both the CM11 ROM and GAPPS to my external SD, I went to recovery and tried to install the new custom ROM but I got an error (status 7) and it was aborted.
Also if I try to reboot it won't boot normally as it should be but it goes back to recovery mode automatically...
I fixed to get back to Jellybean by flashing the stock rom (unrooting?) it via Odin.
Anyone else got the exact same problem as I do and knows a solution to be able to flash CM 11?
Thanks in advance,
Steelbear
Click to expand...
Click to collapse
I had the same problem the fix is quite easy
flash the latest CWM 6.0.4.4 and flash cm11 it will work fine
Blackwolf10 said:
I had the same problem the fix is quite easy
flash the latest CWM 6.0.4.4 and flash cm11 it will work fine
Click to expand...
Click to collapse
Indeed it worked! I found it out myself yesterday. Went to the CWM site and downloaded the latest version (6.0.4.4.) and flashed it through Odin. But thanks for your input anyways (to all who replied) !
An alternative solution that I often use is to open the Updater Script in META-INF folder in the ROM's zip and delete first lines, where it gets device model as property.
Obviously it's an UNSAFE operation (because that lines avoid to install ROMs of other phone on mine) but when I'm sure that ROM I've downloaded is for my phone I do it and it works
moto e condor not booting after installing cm12 on the device. i have followed all the correct procedure but the device is stuck at the cm symbol while bootings. It blinks and blinks. I have waited for almost 2 days but no result. Please help!!!
i have not installed gapps in the process could it be the problem?? :crying::crying:
thanks in advance..:good:
pravardhan96 said:
moto e condor not booting after installing cm12 on the device. i have followed all the correct procedure but the device is stuck at the cm symbol while bootings. It blinks and blinks. I have waited for almost 2 days but no result. Please help!!!
i have not installed gapps in the process could it be the problem?? :crying::crying:
thanks in advance..:good:
Click to expand...
Click to collapse
may be that is the problm,again go to recovery format factory reset and then install cm12 and install gapps and then reboot,make sure gapps for lollipop u install
I don't think so. I installed cm12 without gapps worked fine. But still. Try every option u can to restore your phone. Maybe u need to flash gapps for newer version of cm12. Let us know if anything worked for you. Your info coold help others. Good luck mate.
pravardhan96 said:
moto e condor not booting after installing cm12 on the device. i have followed all the correct procedure but the device is stuck at the cm symbol while bootings. It blinks and blinks. I have waited for almost 2 days but no result. Please help!!!
i have not installed gapps in the process could it be the problem?? :crying::crying:
thanks in advance..:good:
Click to expand...
Click to collapse
may be the downloaded file is corrupted while it was downloaded, happened to me also. download the file again and do a 'clean' installation.
flashing gapps have no connection whatsoever with rom installation. :good:
Install CM11, boot it up once, then install CM12+gapps without wiping.
pravardhan96 said:
moto e condor not booting after installing cm12 on the device. i have followed all the correct procedure but the device is stuck at the cm symbol while bootings. It blinks and blinks. I have waited for almost 2 days but no result. Please help!!!
i have not installed gapps in the process could it be the problem?? :crying::crying:
thanks in advance..:good:
Click to expand...
Click to collapse
Flashing a ROM without gapps will not cause any bootloop issue
how ever you can try these two :
1. If you are using the 27th March build, don't use that, there's some problem with that, if you clean flash that zip, it ll result into a bootloop, use the 28th March build instead
2. If you are still facing a bootloop, make sure that you are using the TWRP 2.8.5 version
Sent from my Moto E using XDA Free mobile app
pravardhan96 said:
moto e condor not booting after installing cm12 on the device. i have followed all the correct procedure but the device is stuck at the cm symbol while bootings. It blinks and blinks. I have waited for almost 2 days but no result. Please help!!!
i have not installed gapps in the process could it be the problem?? :crying::crying:
thanks in advance..:good:
Click to expand...
Click to collapse
Hi, first of all, download the latest build, do a clean flash of all partitions, data, system, cache & dalvik, if you don't wanna loose your data make a backup and restore it only when you have booted your device at least once to make sure it boots, and as recommendation flash a custom kernel after verifying the boot, tell us how it goes Luck!
I tried all the options. I installed the latest build. I cleared cache, dalvik cache, factory reset, etc. But no use its always gets the same situation. Due to the bootloop the device was not detected in Pc so I transferred the cm12 zip to external so card and tried installing it from their. Could dis be a problem?? ? This time I also installed gapps. Please help I want my device back:crying:
pravardhan96 said:
I tried all the options. I installed the latest build. I cleared cache, dalvik cache, factory reset, etc. But no use its always gets the same situation. Due to the bootloop the device was not detected in Pc so I transferred the cm12 zip to external so card and tried installing it from their. Could dis be a problem?? ? This time I also installed gapps. Please help I want my device back:crying:
Click to expand...
Click to collapse
re store back to stock rom 4.4.4. do not flash stock 4.4.2
Where can I find the stock rom 4.4.4?? What if I flashed into 4.4.2??
pravardhan96 said:
Where can I find the stock rom 4.4.4?? What if I flashed into 4.4.2??
Click to expand...
Click to collapse
find stock rom 4.4.4 somewhere on xda developer site or google u will get it, if u flash android 4.4.2 and then update to android 4.4.4 through sofware update. ur moto e get potentially bricked because u have unlocked the bootloader, when u update stock rom replace the bootlaoder. then u cannot recover ur loving moto e,,then u have only one option to change the motherboard
pravardhan96 said:
Where can I find the stock rom 4.4.4?? What if I flashed into 4.4.2??[/QU
Click to expand...
Click to collapse
pravardhan96 said:
Where can I find the stock rom 4.4.4?? What if I flashed into 4.4.2??
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-e/development/downgrade-5-0-x-to-4-4-4-stock-firmware-t3031073
This you can do if you have installed soak test via putting it in your sd card or installed via OTA(ie if you have updated your bootloader) and make sure drivers are installed
Hope it helped
I believe I have the same problem. I tried going from stock 4.4.4 to cm12. Tested april 1st and april 2nd builds and I always get stuck in boot screen animation for nearly one hour.
Whenever I install the rom I get the following message "detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system". I used sideload and the external SD.
Will it brick if I try installing CM11 now after a wipe? Will it be considered a downgrade (even if I never properly booted)?
Sorry if it seems I'm hijacking this thread, but I believe we both have the same problem. I necessary I'll create another topic.
Thanks
Sarmatios said:
I believe I have the same problem. I tried going from stock 4.4.4 to cm12. Tested april 1st and april 2nd builds and I always get stuck in boot screen animation for nearly one hour.
Whenever I install the rom I get the following message "detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system". I used sideload and the external SD.
Will it brick if I try installing CM11 now after a wipe? Will it be considered a downgrade (even if I never properly booted)?
Sorry if it seems I'm hijacking this thread, but I believe we both have the same problem. I necessary I'll create another topic.
Thanks
Click to expand...
Click to collapse
no, you can flash cm11, provided you have never flashed the soak test zip anytime before
and about the bootloop, try using the previous version of TWRP, many people have stated that when they tried flashing with the previous version of TWRP it didn't result into bootloop
Hit Thanks if that was helpful
Quick update, with a solution.
Indeed I changed the recovery for TWRP and chose to clean the system in addition to cache, data and dalvik. After that I installed CM12 through sideload and this time it worked fine. Even if I still got the message "detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system".
Hope this helps OP as well!
Hi
Hi Guys, I am facing this problem too and not able to boot and stuck on CM bootlogo. I am using TWRP 2.8.5.0, if any previous version of TWRP solves this issue then please let me know which version of TWRP to be flashed and where to download it from. My device is not is usable condition right now.
MrJukeHardbane said:
Hi Guys, I am facing this problem too and not able to boot and stuck on CM bootlogo. I am using TWRP 2.8.5.0, if any previous version of TWRP solves this issue then please let me know which version of TWRP to be flashed and where to download it from. My device is not is usable condition right now.
Click to expand...
Click to collapse
Try to flash twrp 2.7 version
suresh.anthati said:
Try to flash twrp 2.7 version
Click to expand...
Click to collapse
Flashing 2.7.1.0 is not helping too and still stuck on bootlogo after flashing 03 April cm12 nightly
Sent from my HTCSensation using XDA Premium 4 mobile app
Hi,
I facing the same issue. Roms tested:
cm-12.1-20150411-UNOFFICIAL-condor.zip
cm-12.1-20150412-ROBBIEL811-UBER4.8-condor.zip
cm-12-20150411-NIGHTLY-condor.zip
with recoveries:
twrp2.8.5.0-condor.img
cwm_6051_condor.img
cwm_6050_condor.img
All combinations fail to boot. Tested in CWM with sideload and SD, format all, and nothing.
After all test, still can't boot.
BTW, Bootloader xt1021 5009. Is there any newer version ?
(My MotoG bootloader has to be upgraded to run latest versions)
---------- Post added at 08:12 PM ---------- Previous post was at 07:22 PM ----------
The last option is recover it from paperweight; downgrade to 4.4.4 (RETESALL_XT1021_4.4.4_KXC21.5-40_cid7_CFC.xml.zip)
In fastboot:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot erase cache
fastboot erase userdata
fastboot reboot
After all, is working again, in stock rom.
glococo said:
Hi,
I facing the same issue. Roms tested:
cm-12.1-20150411-UNOFFICIAL-condor.zip
cm-12.1-20150412-ROBBIEL811-UBER4.8-condor.zip
cm-12-20150411-NIGHTLY-condor.zip
...
Click to expand...
Click to collapse