Hey guys.
I Deodexed and Zipaligned the leaked Jellybean rom uploaded by Doomlord.
Link: https://docs.google.com/file/d/0BwG6whTUXyqHQ2VVS3E2b09YLUU/edit?usp=sharing
Its for C6603 Phones with Unlocked bootloader and you can install the rom with CWM and TWRP.
Once installed wipe cache and dalvik cache.
For some reason it MAY happen that when you start up the phone the first time the phone keeps hanging
on the bootlogo screen.
When this happens dont do anything because the phone reboots automatically and then starts up fine (No problems after that).
When you already are on 4.2.2 then you have to wipe your phone (Format system)
Because if you wont and install this rom then all the odex files are still on your phone.....
All credits go to Doomlord for uploading the leaked 4.2.2 Jellybean rom.
Please tell me if there are any problems.....
Hope you like it
Thank you!
Can you put the md5sum of the zip file, please ?
Related
intalled AOSP Paradise and gapps on my defy(green lense) and everything seems to be working great except:
1. everytime i turn my phone off when i turn it back on the Mokee logo comes up 1st and then it loads AOSP fine but i have to re-enter all my google info
2. it doesn't save any of my settings.
3. it wont let me download any apps...they start downloading but just sit there downloading and if they do finish, it says cant install, not enough memory but i reformatted the sd partition in recovery before installing AOSP because i knew it didnt have enough memory to even install it.
4. Why does that Mokee screen come on still?
i had the Mokee ROM before but shouldnt that have gone away when i wiped data and cache?
Did i do something wrong on install? i did wipe data/factory reset, wipe cache, flashed ROM, flashed gapps, wipe dalvik cache and rebooted twice. it loads fine and everything seems to be working but i dont like having to start from scratch everytime i turn my phone on.
Help pls...frustrating
Try clean install as said in this thread.
forum.xda-developers.com/showthread.php?p=32093770#post32093770
Make sure you flash new rom before rebooting
Flash SBF and then Flash new ROM
[Q]AOSP Paradise
Euro_Rules said:
Flash SBF and then Flash new ROM
Click to expand...
Click to collapse
ok that fixed boot screen but not the redoing of google, downloading apps or saving settings...any other suggestions?:fingers-crossed:
i figured it out! i was missing the firmware from when i bricked it...so, i found a firmware file, flashed it and now it works like a charm!! yay
Moved to Q&A. Please ask all questions there.
Hey everybody .
I'm new with the Nexus 4 and I just rooted it . I'm currently running Android 4.3 .
and I would Like to istall the latest PA 3.92 , and I saw that there somethings called RADIO and Bootlaoder to Flash .
How to actually flash them ? just by the recovery or some other method ?
by WHAT order should I flash ? Rom first or Radio or Bootloader ?
Thanks . :good:
Cin0 said:
Hey everybody .
I'm new with the Nexus 4 and I just rooted it . I'm currently running Android 4.3 .
and I would Like to istall the latest PA 3.92 , and I saw that there somethings called RADIO and Bootlaoder to Flash .
How to actually flash them ? just by the recovery or some other method ?
by WHAT order should I flash ? Rom first or Radio or Bootloader ?
Thanks . :good:
Click to expand...
Click to collapse
If you are already running Android 4.3, you have the latest bootloader and radio installed. Make sure your battery is charged to at least 50%, perform a nandroid backup, and wipe cache and Dalvik cache. Next install ParanoidAndroid from the zip file, install the latest Gapps from the zip file, wipe cache and Dalvik cache, and reboot.
If you are not running Android 4.3, you should use Clockworkmod or TWRP to install the latest bootloader and radio from the zip files available from ParanoidAndroid before flashing the ParanoidAndroid ROM and Gapss.
BobWalker said:
If you are already running Android 4.3, you have the latest bootloader and radio installed. Make sure your battery is charged to at least 50%, perform a nandroid backup, and wipe cache and Dalvik cache. Next install ParanoidAndroid from the zip file, install the latest Gapps from the zip file, wipe cache and Dalvik cache, and reboot.
If you are not running Android 4.3, you should use Clockworkmod or TWRP to install the latest bootloader and radio from the zip files available from ParanoidAndroid before flashing the ParanoidAndroid ROM and Gapss.
Click to expand...
Click to collapse
Ok Thank you ! :good::good:
I Did the normal OTA update (Ofiicial 4.3) So I have the latest Radio and bootloader is that Right . and I'm good to go flash the PA 3.92 .
Cin0 said:
Ok Thank you ! :good::good:
I Did the normal OTA update (Ofiicial 4.3) So I have the latest Radio and bootloader is that Right . and I'm good to go flash the PA 3.92 .
Click to expand...
Click to collapse
That's right: The OTA installs the .84 radio and makoz20i bootloader, so you are ready to flash ParanoidAndroid 3.92 and Gapps for Android 4.3.
Thanks
Thank You :good::good:
Hi guys,
I'm having a weird problem. I've used a i9100 and i9300 in the past and have flashed hundreds of different ROMs, kernels and recoveries. I was running WanamLite on my i9505 until I wanted to switch to PAC Alpha 4.3. I had a few problems installing it (didn't want to go past the boot logo) but eventually with TWRP it worked. I wasn't too happy with the alpha version (freezes here and there) and switched to Omega 9 4.2.2. Installed Xposed framework, rebooted and got stuck on boot. I couldn't access the recovery immediately, first I had to remove the battery, wait and after a few tries I was in the recovery. Removing Xposed framework, wiping data, cache, dalvik cache didn't help Omega 9 to boot up. I re-installed Omega 9 and did a restart without installing Xposed framework, and it froze on boot. Same thing happened when I installed WanamLite, Echoe and Google Experience ROMs and did a restart after the successful first boot after installation.
The only way to get past this problem is to:
a) flash the pre-rooted, original Samsung MGA ROM
b) enter recovery and wipe data/factory reset
If I skip b) then it will just enter a boot loop (boot halfway, reset, boot halfway, reset...)
It's driving me crazy. I do not want to use the original ROM and have no idea what is causing this behavior. I appreciate your help.
Here the information of the working MGA ROM:
4.2.2
I9505XXUBMGA
3.4.0-1081224
[email protected] #1
JDQ39.I9505XXUBMGA
ifonuser78 said:
Hi guys,
I'm having a weird problem. I've used a i9100 and i9300 in the past and have flashed hundreds of different ROMs, kernels and recoveries. I was running WanamLite on my i9505 until I wanted to switch to PAC Alpha 4.3. I had a few problems installing it (didn't want to go past the boot logo) but eventually with TWRP it worked. I wasn't too happy with the alpha version (freezes here and there) and switched to Omega 9 4.2.2. Installed Xposed framework, rebooted and got stuck on boot. I couldn't access the recovery immediately, first I had to remove the battery, wait and after a few tries I was in the recovery. Removing Xposed framework, wiping data, cache, dalvik cache didn't help Omega 9 to boot up. I re-installed Omega 9 and did a restart without installing Xposed framework, and it froze on boot. Same thing happened when I installed WanamLite, Echoe and Google Experience ROMs and did a restart after the successful first boot after installation.
The only way to get past this problem is to:
a) flash the pre-rooted, original Samsung MGA ROM
b) enter recovery and wipe data/factory reset
If I skip b) then it will just enter a boot loop (boot halfway, reset, boot halfway, reset...)
It's driving me crazy. I do not want to use the original ROM and have no idea what is causing this behavior. I appreciate your help.
Here the information of the working MGA ROM:
4.2.2
I9505XXUBMGA
3.4.0-1081224
[email protected] #1
JDQ39.I9505XXUBMGA
Click to expand...
Click to collapse
This happens with many including me some time with many diffrnt files chainging and overwriting causes the same
Best option as u said above flash stock firmware
Then u can try what I feel will work better in ur case
Root the phone with CF root method
Flash Philz Recovery
wipe cache / dalvik / ix perm and reboot and go ahead with ur Rom flashing
Ok, flashed the stock ROM which was not rooted, then rooted using CF's method and flashed PhilZ. I couldn't find the option to fix permissions in PhilZ recovery, and went ahead with the installation of Omega 9 after wiping. I couldn't even get Omega to boot, previously it worked on the first boot and then no longer after a restart.
I don't know whats going on here.
I'm flashing the pre-rooted MGA now.
ifonuser78 said:
I'm flashing the pre-rooted MGA now.
Click to expand...
Click to collapse
Pre-rooted MGA works fine, but no other custom ROM.
I ran TriangleAway to reset the counter, but that didn't help either. No third party custom ROMs for me. :crying:
Flash latest Philz recovery.
Go to mounts and storage.
MAKE SURE YOU HAVE A ROM ON SD CARD.
Format system, cache, data and preload.
then just to be sure everything is gone I go to wipe /data factory reset and choose the wipe to install a new rom.
Then go to install zip and flash rom.
Once it's flashed you should be good to reboot.
If you're still in a bootloop then go to wipe/data factory reset but choose first option not the one to install rom.
Now reboot again, good to go!
Just a thought, if you're still having trouble flash a AOSP kernel in Philz as you might be trying to boot an AOSP rom with a TW kernel installed
Sent from my GT-I9505 using XDA Premium HD app
Hey guys,
I'm not a total scrub at flashing roms and there's still a bunch of things that I don't understand. I'm pretty positive that I flashed Slimrom correctly but here's the situation.
Started on 4.2.2 Slimrom
Reboot to TWRP recovery
Format factory reset/format data, system, cache, dalvik cache
Flash Slimrom 4.3 stable build 1
Successfully reboots into 4.3
Okay now here's the weird part.
The first time I rebooted back into recovery to flash gapps. After I flashed gapps and tried to reboot into the rom, the phone freezes at the screen with "google" and the unlock sign on the bottom. The only way I can get it to boot into the rom again is if I reformat/reset EVERYTHING (including format data) and reflash 4.3. After a few tries of messing around with not wiping dalvik/cache and stuff I realized that even if I don't flash gapps it still freezes on the google screen. So here's my main problem
After flashing 4.3 slimrom, the phone boots into the rom only once. If I try restarting my phone it freezes on the "google" screen.
Anyone know what I'm doing wrong?
Just to clarify it's a LG Google Nexus 4 mako.
Sorry if I'm being redundant. I just want to give as much detail as possible. If you need anymore info let me know!
Thanks
ms3195 said:
Hey guys,
I'm not a total scrub at flashing roms and there's still a bunch of things that I don't understand. I'm pretty positive that I flashed Slimrom correctly but here's the situation.
Started on 4.2.2 Slimrom
Reboot to TWRP recovery
Format factory reset/format data, system, cache, dalvik cache
Flash Slimrom 4.3 stable build 1
Successfully reboots into 4.3
Okay now here's the weird part.
The first time I rebooted back into recovery to flash gapps. After I flashed gapps and tried to reboot into the rom, the phone freezes at the screen with "google" and the unlock sign on the bottom. The only way I can get it to boot into the rom again is if I reformat/reset EVERYTHING (including format data) and reflash 4.3. After a few tries of messing around with not wiping dalvik/cache and stuff I realized that even if I don't flash gapps it still freezes on the google screen. So here's my main problem
After flashing 4.3 slimrom, the phone boots into the rom only once. If I try restarting my phone it freezes on the "google" screen.
Anyone know what I'm doing wrong?
Just to clarify it's a LG Google Nexus 4 mako.
Sorry if I'm being redundant. I just want to give as much detail as possible. If you need anymore info let me know!
Thanks
Click to expand...
Click to collapse
Are you flashing the right Gapps package? Be sure you are flashing the latest 4.3 one.
abaaaabbbb63 said:
Are you flashing the right Gapps package? Be sure you are flashing the latest 4.3 one.
Click to expand...
Click to collapse
Yep I'm positive. I redownloaded both the 4.3 rom and gapps package multiple times just to make sure. Also it doesn't reboot even if I don't flash gapps. Doesn't boot at all if I flash both the rom then gapps at the same time.
bump
then, wipe data/factory reser and flash the stock rom. the rom might be the problem
davinnwilliam said:
then, wipe data/factory reser and flash the stock rom. the rom might be the problem
Click to expand...
Click to collapse
It works for everyone else though. It's Slimrom 4.3 stable build 1.
Rom isn't the problem.Slim rom beta 1(4.3) is super stable. Use any version of twrp recovery other than 2.6.1.0 and wipe system+data,flash slim rom,flash slim gapps,reboot.
Note: if you flashed franco kernel then this may be the issue for your bootloop also you may want to upgrade your bootloader and radio to 4.3 versions(bootloader more important)
I tried to update my Defy+ MB526 at a newer version of Android (Jelly Bean or more... now it's running with the factory 2.3.6 ) but I have a problem with the installation of CM.
1) I rooted my device with Framaroot "Super SU" and checked wit "Root checker" and it is ok.
2) Then I stored in the SD the CM file.zip (before the 10.2 and after the 11) and the Gapps.zip.
3) I installed the SndinitDefy_2.3.apk
4) I ran the recovery mode, wiped factory/data, wiped cache partition, wiped Dalvik cache
5) Then install zip from SD card, but the file "cm-11-20131229-nightly-mb526.zip" and also the "cm-10.2-20131020-nightly-mb526.zip" aborted the installation with "error status (0)".
I dont' know why.
Please tell me if the procedure I've done is correct. Otherwise write me the correct steps. Thank you. :good:
Ps: system version: 45.0.2310.mb526.retail.en.de
build n°: 4.5.1-134_dfp-231
Flash this - http://forum.xda-developers.com/showthread.php?p=48501247, then reboot and go to recovery again. Then flash CM.
Sent from my Nexus 7 using Tapatalk
Thank you Hotdog.
I tried with flash the Sndinit and after, by the custom recovery, I've flashed the Twrp. After I've started the Twrp recovery and flashed the CM11. It seemed ok but when I rebooted the device to install the Gapps, it has gone in infinity loop.
After that, i made a mistake because i did a completely reset of the device (the total wipe) and after I've reeboted the Defy and it bricked!!!
But with the guide in this forum I un-bricked it (It isn't difficult, it's easy) and then I tried, by the same previous way, to install the CM10.
With the CM10 it works awesome (4.1.2) and the gapps didn't create any problem!
Thank you again and many thanks to all people that everyday helps each other in this forum (especially non-expertised like me!)
:good::good::good::good::good::good::good: