Related
Hy,
I'm a noob on this thing of kernels and roms, I've bought a new U8800 and i've been searching here for a guide that explains what to do to install a costum kernel and rom, but never was found hehe ....probably because im not searching in the right spot .... so if someone can help me it would be apreciated....I think i know more or less how to do it but I was reading some posts and some people say that we should make a backup of the stock rom and kernel...in case we would want to get back for warranty... and that i don't know how to do...
Cumps,
Gaspias
Lets begin with kernel now. I assume you are in stock? Serch superboot in modaco. Search x5 section in modaco, and it is one of the stickys. Follow the guide to install it in modaco. It is sticky too, and it is called ultimate guide to ideos x5 u8800. It is made by that-guy
Sent from my Huawei Ideos X5 1.12.9(ret4rt) using XDA App
EDIT: now as I got up even though I am bit sick to get stuff on my X5, let me clean up the post and give you actual instructions:
First of all:
IF YOU DO plan getting a custom rom and a gingerbread system, do not do the superboot thing. it does not help you in installing a rom, and the kernel modifications as long as I know.
First, a clockwork mod for your phone.
What does this do?
We replace stock recovery image, booting into custom one when in case of ideos X5, you press VOLUME UP+Power button to turn on the device. With clockwork mod, you can handle installing custom roms, kernels, and other content.
You can get 4.0.0.5 from http://forum.xda-developers.com/showthread.php?t=1130524 (Again, if someone reports that the 5.x.x.x DOES work so you can actually flash anything with it, say so, and link to it. Still, 4.0.0.5 works for most of stuff and does it job well.
To install it, go through these steps:
- Download the recovery.zip (with your computer of choice)
- Create a folder somewhere practical to back up your old recovery image, I myself made a ideos X5 folder to my C where I gathered a lot of stuff, having a backup image folder and zips for the custom roms.
- Turn off the phone, wait, and boot it by first pressing BOTH volume down and volume up, and then the power button, the screen should slide in pink screen, when it does, plug the phone in to your computer
with usb cable, you should see a drive pop up. NOTE: as I learned myself, there is alternative way to doing this, mainly, a computer free way, but it also resorts in Root browser that may be harder to do without a rooted phone. So, if you have a computer of any sort, do it this way.
- After you do see the drive, open the image folder, plain copy the recovery.img to your computer, to a separate folder somewhere where recommended to back it up - just in case. After that, replace it with the clowckwork mod recovery.img by just plain write and overwrite - good way to know is that the stock official recovery is about ~9 megs large, while ClockWorkMod is ~5 megs. After transfer give it about 20 seconds before you safely yank the USB cord off, and then your battery. Wait 5 secs just for laughs and put the battery in. You can now test the CWM boot by holding VOLUME UP and Power button until the recovery menu comes up. reboot the device after it boots succesfully, you cannot do anything with it, yet.
Now, like I pointed out before I edited, that most of the roms have their own modified kernel already, that they do also update with their release (MIUI, and CM7 as long as geno could work on it) - so flashing your own kernel modification speratedly would be pretty much unneeded.
So, right now, dip in to the ideos x5 android development forum, and just choose either the newest MIUI, from ret4rt, the now halted CM7 by geno - for both these I can report that they do WORK and are usable, and if anything can have a minor trouble or two (for myself, both of these have a crackling sound on higher volumes problem - pretty much you need to keep your media volume at half way if you use pair of earphones or you will hate the sound quality results) - There is also lastly the oxygen build(s) by someone but I will not vouch for nor talk against any of them because I have not tested them, and that said, I also feel liable to mention in any case that you may want it particulally, that there is versions built by people for u8800.
First, though I think you may know them, I run down the CWM navigation, because of it's nature that it is not navigated with touch screen:
Power button = OK, choose.
Volume up goes up in menu.
volume down goes down in the menu.
BACK (touch) button goes back. (remember this, is important with some mispresses in menu)
To install these, put the .zip file of the ROM to some easy path, probably root, of your EXTERNAL SD card. - boot into CWM (though the volume up+power after you shut down your phone) and from there, I myself advice so no troubles com up to wipe your data, wipe your cache, wipe dalvik cache (this option is in Advanced part of the CWM main menu) and after that, start installing by "install zip" and "choose zip file from SD card" - after that browse the ROM zip of your choise and choose it. Install it, and afterwards reboot.
The wipe, you may ask, "is it necessary" not maybe for everything, but advised. my first custom rom installation had nasty habit of not being able to do wifi communication and other stuff, entirely just because I did not wipe before installing it, needing me to do another set of complete wipe and install before I had a usable custom ROM system in my hand, so, be advised.
Original message:
I as someone who went through same thing just a week ago (and already feels like I have done this for a month) can say that xda developers is quite tutorial free, that is to say, instead tellind what to do everyone expects you already DO know.
On emergency total recall: there is a 2.2.2 image from huawei. Unlike custom roms, you boot install it through a dload of huawei's own, by booting the phone to the volplusminus+power mode, it works even if you fukt your recovery image, and installing it pretty much wipes anything you ever done to the phone, leaving no traces of it's modded life. I do not have link for this now, as it was in the chinese site where you can also find the current 2.3.5 betas, sorry.
*edited out for the actual instruction tutorial*
nice tutorial ^^
Thank you very much for the explenation, I don't know how to thank you guys!
With some problems that we have with this roms and kernels, do you think that is worth changing ?
Well the beauty of it is that it's a decision all yours to make. I myself can say that the earphone volume is minor thing that gets my nerves, but with that tradeoff you get slightly more powerful cellphone, a system with UI you choose (I personally liked MIUI for the 24 hours I used it myself) and so on. It is also reversable and some people even make testing roms as their hobby. As there is a thread even now about some mystery ROM from china nobody knows nothing about but bravest get in to it and tell the tale.
Anyway, if you feel you are up to it, do it. Read through the descriptions to see is feature you want to keep broken somehow just in case. MIUI is goos, bit iOS:ey, still quite different os to look and use, CM7 is pretty much stock gingerbread upgrade - and LOADSA ADDITIONS - if you'd like something more of look and usage of stock android.
hey everyone, thanks for the tutorial
I used to have a Windows mobile 6.5, flashing it every time, and just bought my Android today, and searched for a couple of hours until I find this tutorial for a complete - and quite simple!! - full backup of the stock image.
That said, I have just one doubt
Now that i'm about to update my phone to the official Huawei Gingerbread version - before the custom roms, i'll give it a try - do I need the CWM image for it?
Or I can do it simply from the stock rom, with no trouble?
Thanks a million
hmarques said:
hey everyone, thanks for the tutorial
I used to have a Windows mobile 6.5, flashing it every time, and just bought my Android today, and searched for a couple of hours until I find this tutorial for a complete - and quite simple!! - full backup of the stock image.
That said, I have just one doubt
Now that i'm about to update my phone to the official Huawei Gingerbread version - before the custom roms, i'll give it a try - do I need the CWM image for it?
Or I can do it simply from the stock rom, with no trouble?
Thanks a million
Click to expand...
Click to collapse
No. You extract dload folder to internal or external sd and boot your phone while holding volume + and -
Sent from my Derp using XDA Herp
installed 2.3.5 sucessfully!
thanks guys
Hello ,I bought this phone recently and I was quite disapointed. It got really good HW no doubt ,but on the SW side it completly sucks. Camera quality is really poor (some samsung phone(s) uses same camera chip and it takes far more better photos) ,but i dont mind it at all ,im not taking photos very often. Wifi is a disaster because of its low range and it often disconnects from the network ,when the signal is low ,while my Nexus 7 (2012) and my previous tablets had no problem with low signal on wifi. And lastly it has terrible RAM managment. Usually I have ~300MB free RAM ,while my Nexus 7 has over 500 MB and my previous tablet Nextbook Premium 7SE had even +600 MB. It often kills background tasks and service and makes it laggy ,especially when it loads pages on Internet Browser and also because of it sometimes the virtual keyboard wont pop up.
I want to get rid of most of these problems and the bloatware from Sony by installing some custom ROM and kernel. However for this I must root the phone ,unlock the bootloader and flash CWM recorvery and this might be a problem for me ,because I have never done such complicated stuff without some rooting/unlocking BL toolkit. The only android device that I rooted,unlocked BL ,flashed kernels etc... was my Nexus 7 because it is easy and safe to do these stuffs with Nexus Root Toolkit and with TWRP. And so Im gonna need from you to answer these following questions before I start with the procedure:
1. Is my rooting ,unlocking BL ,flashing etc... setup correct?
1. Rooting the phone with FlashTool and with DoomLords easy rooting toolkit
2. Flashing CWM (locked BL edition)
3. Backing up TA directory (where are DRM keys required for functionality of Bravia Engine and for those Sony stuff)
4. Nandroid BackUp
5. Unlocking Bootloader
2. Is it safe to flash Firmware 12.0.A.1.257 in order to root my phone ,even if the phone already had the newest one(12.0.a.2.254)?
3. Is driver for my XSP from Sony PC Companion enough ,or I need to install more drivers? For sure I installed Flashmode and Fastboot drivers from FlashTool folder
4. Should I do nandroid back up before unlocking BL?
5. When I unlock Bootloader ,will it erase the stock ROM with Kernel ,or only data (for example videos ,pictures ,DRM keys?)
6. Will unlocked BL erase the CWM (the one for the locked BL) and root?
7. If something goes wrong while unlocking BL and my device bricks ,will be CWM useful for unbricking?
8. If I want to flash a new ROM ,must I always use FlashTool ,or I can always install them via CWM? If yes ,is the option "wipe data/factory reset" enough for flashing new ROM ,or i need to wipe cache with dalvik too?
9. Do I need microSD card (like a external storage) for flashing new ROM/kernel? Or does the option in CWM "wipe data/factory reset" leave by files like nandroid and ziped ROM / kernels? And is 1GB microSD card enough for nandroid and custom ROMs enough?
10. Whats the percentual chance that my phone will get bricked by doing all of this?
Thank you for answers.
Additional question: I saw on this forum some topics about some offline charging bug. WIll it have negative effect while rooting/unlocking BL?
Exelzior said:
1. Is my rooting ,unlocking BL ,flashing etc... setup correct?
Thank you for answers.
Additional question: I saw on this forum some topics about some offline charging bug. WIll it have negative effect while rooting/unlocking BL?
Click to expand...
Click to collapse
1. Backup TA partition
2. Unlock bootloader
3. Flash CWM with Flash tool (using boot.img from CM)
4. Flash CM rom (Im using ubberlaggydarwin's 29.10.2013 build, which is 100% stable for me.
I did use a SDcard to flash the rom.
If you follow the steps in the differnet tutorials; unlocking BL, flashing CWM, flashing CM, then the chance of messing up your phone is really small. Just READ CAREFULLY and follow the steps in the tutorials carefully That's most important, read more than needed(and because of the questions you've asked it seems youve already informed yourself quiet well, read more ) be careful, and follow the steps, it is just a logical proces and if you keep patience and follow the different tutorials, everything will work out fine, it is not that hard, probably the biggest reason for people messing up is not reading enough/getting enough info and not having enough patience/not being secure enough.
Good luck, and enjoy your CM powered phone within a day
PS: I;ve read that when using an older firmware which does not have the offline charging bug and when you than flash a custom rom, the bug won;t show up, allthough there is no 100% proof for this, for me.. I don't care about offline charging my phone stays on for 2 days easily with average use...
Again, good luck and enjoy
Read up on this http://forum.xda-developers.com/showthread.php?t=2354704 by DooMLord and follow the links. Worked great for me. Just read the instructions carefully.
You can normally get out of trouble by being familiar with flashtool to and having a backup on SD card to flash with CWM
Now using OMNI rom after trying most of the others.
Good luck
Alcatel OT POP C7 (7041x) [BACKUPS/ROOT/CWM/TWRP/TOOLS/DRIVER] [STOCK & MIUI V5 ROMs]
Last Update: Mon. AUG-03-2015
Hello,
I had bricked my "just" 4 hours old C7 a week ago because i was stupid enough to delete the custpacks from root and /system folders without even making a backup.
I had not flashed CWM and only rooted the device with RomasterSu_2.1.4 (aka iROOT, some Chinese one-click root / KingUser app) and i could not revive the phone through MTK Tools, Mobile Upgrade S or adb shell (either device not recognized or it couldn't push files, giving errors).
Today i got a new one, and hell i have not made the same mistake again.
After i unboxed the phone i immediately went into stock recovery and made a backup!
Secondly, i rooted the phone with RomasterSu and installed Uncle MTK Tools and made a IMEI backup (Just incase).
And lastely, i flashed CWM through Uncle and made a Full Backup of the current rom.
For anyone who happens to play with a rooted C7 on stock rom and accidentally bricked it, i will provide my Stock and CWM Backup Recovery's for anyone to use.
note: If you already flashed a custom recovery onto your device (e.g; CWM), the stock backup becomes obsolete! Use CWM instead.
[INFO]
Model: Alcatel One Touch 7041x
Firmware: 4.2.2
Baseband: MOLY.WR8.W1315.MD.WG.MP.V7
Kernel: 3.4.5
Build: 01003
Stock Recovery (Data) Backup (.backup):
- userdata_20100101_000117.backup (.rar / 83MB)
Place Stock Backup (Unpacked) into the root folder of your sdcard.
Reboot phone, Vol+&Power into stock recovery and select "restore user data" (or something alike) and select the .backup file.
New googledrive uploads:
-MIUI V5 (4.8.29) ROM (.zip)
-RootMaster / iRoot & SU (.apk)
-Uncle MTK Tools (.apk)
-CWM & TWRP Recovery (.img)
-Mobile Upgrade S (.exe)
-One Touch Center (.exe)
-USB Drivers (.rar)
-MTK DroidTools (Windows) (.zip)
-SP Flash Tools (.rar)
If you're familiar with flashing, i'd guess installing these files and how to use them propertly are self explainatory.
If not, you can ask me how to write a proper guide...
==============================================================================================================
--UPDATE--
I provided a stock rom and a MiUI V5 rom for people who don't want or prefer to use backup's. A custom Recovery is needed and will not work with stock recovery.
This is a vanila stock rom without the custpack games/apps bloatware. IIRC this rom is already rooted, but if not, you can always use iROOT.
Bare in mind that it's based on the first TCT Firmware build 01001 and not the latest Firmware Upgrade 01003.
The MiUI V5 rom is based on miui 4.8.29 (Jellybean 4.2).
Also, the installers are in Spanish and you can only select a handfull system languages for both roms, but atleast you can use these roms in English.
Both roms work absolutely fine, and faster than stock with custpack bloatware.
Stock (01001) ROM:
https://drive.google.com/file/d/0B_pc8K917q22RlJWNllGV2JLOVE/view?pli=1***
MIUI V5 (4.8.29) ROM:
http://www.mediafire.com/download/9l49h7gisxslx2s/Miui+v5+spanish.Alcatel+7041x.zip***
---UPDATE--- [AUG-03-2015]
KitKat 4.4.x Alcatel C7 (7041x):https://translate.googleusercontent...2.html&usg=ALkJrhh-v6soAAT7XuUrpiK_zGh5bODHaA***
*** I have not uploaded these ROMs, nor am i responsible for any damages or errors that might occur during flash, use at own risk and always make a backup first!
Making any custom changes to your device will void your warranty!
Bump Update!
Added files to google drive;
-MIUI V5 ROM (4.8.29) (.zip)
-RootMaster / iRoot & SU (.apk)
-Uncle MTK Tools (.apk)
-CWM & TWRP Recovery (.img)
-Mobile Upgrade S (.exe)
-One Touch Center (.exe)
-USB Drivers (.rar)
-MTK DroidTools (Windows) (.zip)
- SP Flash Tools (.rar)
https://drive.google.com/folderview?id=0B52SB5R_clyUVTNwVHlwMHpCZWM&usp=sharing
S5 7041X Rom
http://www.htcmania.com/showthread.php?t=976259
How to install stock ROM with Mobile Upgrade S,when installed custom CWM?How back to stock CWM?Mobile Upgrade S does not recognize the phone with custom CWM.Phone must be flashed with SP Flash Tool.After this,Mobile Upgrade S,recognizes phone.
_jussyy said:
http://www.htcmania.com/showthread.php?t=976259
Click to expand...
Click to collapse
Nice ROM,but it kills the battery.
mugy said:
Nice ROM,but it kills the battery.
Click to expand...
Click to collapse
Most roms need some time to settle, after 1 or 2 complete charges your battery should behave normally.
You can also use the 'Greenify' (Permit SU access) to blacklist any app that uses wakelocks or running backround processes.
This will save you some battery...
My best bet is going for the MiUiv5, which always ran fine when i used to own the C7. Never had any issues with that ROM other than a occasional 'SystemUi stopped working' when trying to use the Rom's OTA.
I installed CWM 5.5.0.4 but cannot see internal storage
Do you have any idea?
erdemdengel said:
I installed CWM 5.5.0.4 but cannot see internal storage
Do you have any idea?
Click to expand...
Click to collapse
A bit late but that's because I don't own the C7 anymore and hardly pay attention to these threads anymore, I'm sorry...
I have no idea why it would'nt show up in CWM. I always use TWRP on any device that has it's compatibility over CWM, mainly because of it's touch functions and ext partitioning functions. Normally your internal storage is sdcard0 and your SD is sdcard1, select "mount/unmount" to see whether it's listed or not (I guess you already did that obviously but still....) It should be listed, if not, reflash CWM (try latest available for the tct/alcatel, i don't know which build number out top of my head, or TWRP.
I suggest to switch to TWRP and most likely your problem will be solved.
I don't know where you got your recovery files, but the ones I got in my googledrive are guaranteed working since I tried them both before uploading, if you used my CWM try to reflash it with MobileUncle MTK Tools, but than again pick TWRP instead .
Sent from my ACER LIQUID Z500 using XDA Free mobile app
Bump Update
Sent from my HTC One using XDA Free mobile app
I tried to use both the CWM and TWRP recoveries and neither worked. When it tries to boot into them it just glitches out the boot screen and resets. I flashed them with Flashify if that's a problem. My tablets model is a P310A. So this is the right thread for it right?
It does the same thing when I flash with Uncle MTK Tools.
Update: So it seems that you need to use this recovery if you have a P310A. Sorry for the pointless bump.
White sreen when flashed
After I flash my phone I get white screen logo whitescreen logo etc.
I have the alcatel 7041x
Alcatel one touch pop C7 ,Dutch
It functional in 7040e?
Not reading us b
I can't download backup file
@dragonivell
No! 7041x only. If it would, i would've stated it at the "device compatibility list" (which doesn't exist in this topic, for that reason!)
@pricklain
I'm sorry, somehow the file got removed from my gdrive. Since I don't own this particular device anymore, i cannot re-upload the file in question.
Also, i'm unable to edit the OP for some reason, so i understand any complains about the backup file(s).
Note: I am hardly online on xda these days, so forgive me if my response is a bit late...
@jachthond
Heb je wat meer details wat er niet lukt met flashen, en welke files je daarvoor gebruikt hebt? Mischien kan ik je er door heen loodsen.
Nobody has to Alcatel One Touch Fierce 7024w ?
links please
Ebom
Because this thread was the first one I completly read and looked at many time again, I post my results in short here.
Its posible to "flash" or "download" the KitKat rom from Hungary (or whereever the rom came from) onto a stock Alcatel OT POP C7 (7041X). Note the X, I have only that phone so, find another thread or user if you dont have a x (the kitkat rom is from/for a 7041D, so maybe your in luck too if you have the D version)
https://forum.xda-developers.com/alcatel-pop-c7/help/alcatel-one-touch-pop-c7-kitkat-twrp-t3438624 this other thread has the working rom, tools, and scatter file.
I could write a tutorial, but i based my carefull work on that thread and the links he provided. I also watched the youtube video even tho I dont understand a word thats being said.
Basicly NEVER EVER overwrite or format the phone completly or do sh1t with the preloader. mobile_info we leave alone aswell and we dont like to touch NVRAM aswell. They kinda contain imortant stuff
Basicly i made backups of everything I could or wanted (some thread said "Readback" the preloader can break alcatel phones, Ive succesfully read my whole phone back, but NEVER tried "downloading" or flashing preloader, cause i dont want a brick.) so I have everything saved and i could compare my files against any other rom that ppl uploaded.
KitKat rom from that thread I linked you to, get it, just all of it just in case. then if you compare them using CRC/SHA1 or MD5 against your dumps. hopefully like me, MBR, EBR1 and EBR2 are all the same compared to the kitkat one. so i took the liberty of not flashing them.
left us to do the: UBOOT(lk.bin in my backups), BOOTIMG, RECOVERY, SEC_RO, LOGO, CUSTPACK, ANDROID.
I noticed diferences in the logo, recovery and sec_ro, so I followed the tutorial/video on "downloading" those onto my phone... real simple...
I now have KitKat on my 7041x
Phone calls itself a 7041D now and Gyroscope sensor is not working
simple fix for the phone name is in the build.prop file, either google how to edit that (using root, or adb tricks) or do as I tricked, changed the file inside custpack.img using an hexeditor (HxD is my favorite). When you find a 7041D, replace with X. I suggest you use your brain and computer skills to deduce how to "replace" a character instead of inserting seems to start at offset 0x03356000 (http://www-ccpp.tcl-ta.com/files/ALCATEL_ONE_TOUCH_7041X_KK.xml does excist, so it suggest an official rom either was made or support added anyway).
I replaced budhapest with amsterdam and could change the dualsim to false and compensating the file size change by removing some 0x00 after the file.. but felt it was too risky and only tried the D into X wich was succesfull. ill check if I can find the AcceleroMeter/Gyro? module or fix.
If anyone has a question, sure ask me. but the rom is there, make backups before ANYTHING, and never full format or touch the preloader. ive read it might be able to fix using some Jtag method, but I cant remember the thread and this is quite the old phone by now. if ever, ill try a newer rom, but probably have to make it myself. another kitkat rom Ive found wasnt clean but this one was like it was a OTA, the phone migrated the 58 apps, and all my settings where still there, whatsapp worked right away without trouble and I can now play Pokemon GO (the x version has the 1gig ram )
Bedank @JMailuhu for making this thread and pointing and warning people. within 1 week of fixing this free phone Ive updated to kitkat. Now ill try fixing the accelerometer problem and maybe try other roms (ow well, kitkat does work fine) no root or custom recovery sofar
TLDR: Have a cookie, sorry I talk too much. much better than "ROM NOW" comments
Hello everybody I got brand new Motorola Defy+ and I want to have newest version of android on it. I am not familiar with rooting etc and unsure if this is possible theres instruction in videos description on youtube "How to Install Android Nougat on Motorola DEFY+ (Android 7.1.1/CM14.1)" ( I can not post links) If not I am curious what is the safest and easiest way to root the device and if theres available newer system than KitKat for my device
Moreover I wanted to install roehsoft ram expander as the phone got only 512 MB of RAM but test says it has to have compatible kernel from what I remember. Not sure if I have to install new operating system in the first place and then root the phone or the opposite and what kernel it has to have to work properly. As I said before I am not experienced android user its my first device with this system
Thank you in advance ppl peace!
Amazing, Motorola Defy+ is cool in its segment but can this slim hardware keep up with such a bulky Android version?
It's said in KittyKat threads here phone has a tendency to stutter with KK (as such a demanding OS), and how about Nougat?
Anyway it'd be nice if somebody adjust Nougat to work worth Defy+. Especially it is needed to optimize battery consumption in idle.
And about rooting, you can just run apk called FramaRoot and job is done
Afterwards run SndInitDefy_2.3 and you will have custom recovery installed (CWM), it is just as simple as it!
http://cloud.tapatalk.com/s/5965fe184202f/Framaroot-1.9.3.apk
http://cloud.tapatalk.com/s/5965fe43f2a32/SndInitDefy_2.3.apk
Afterwards, make a nandroid backup and, using already installed custom recovery CWM (which is clumsy, without touch support), you may want to flash TWRP. If so then flash defy_twrp_recovery_2.6.3.0.zip, e.g. from this link:
http://d-h.st/users/tejus.k.v
Although attention: this flashes recovery TWRP to the system partition (probably the phone's recovery partition is to small) overwriting the android system which is already there, so after doing this you must flash some ROM.
It is described in the second post of this KittyKat ROM thread: [ROM] [4.4.2] SlimKat (jordan) [STABLE 4.0] [Weekly 3.85] [Unofficial]
And see Installation Instructions section, good luck! ?
pawwaap said:
And about rooting, you can just run apk called FramaRoot and job is done
Afterwards run SndInitDefy_2.3 and you will have custom recovery installed (CWM), it is just as simple as it!
http://cloud.tapatalk.com/s/5965fe184202f/Framaroot-1.9.3.apk
http://cloud.tapatalk.com/s/5965fe43f2a32/SndInitDefy_2.3.apk
Afterwards, make a nandroid backup and, using already installed custom recovery CWM (which is clumsy, without touch support), you may want to flash TWRP. If so then flash defy_twrp_recovery_2.6.3.0.zip, e.g. from this link:
http://d-h.st/users/tejus.k.v
Although attention: this flashes recovery TWRP to the system partition (probably the phone's recovery partition is to small) overwriting the android system which is already there, so after doing this you must flash some ROM.
It is described in the second post of this KittyKat ROM thread: [ROM] [4.4.2] SlimKat (jordan) [STABLE 4.0] [Weekly 3.85] [Unofficial]
And see Installation Instructions section, good luck!
Click to expand...
Click to collapse
Thank you for your help! My phone dont want to turn on anymore. I've done everything carefully up to the following point"Wipe /data, /cache, and /system in TWRP or use defy_safewipe.zip" (after that I wanted to flash this: "Slim-mb526-4.4.2.build.4-UNOFFICIAL-20140407-2344.zip" cos its ROM right?), but and when it asked me to slide back to the right blue arrow to confirm, my phone booted up and then died after motorola logo. Green led lighted up before death. It seems that it wasnt safe thing despite the name. What to do now? Can I recovery it?
--
UPDATE: ok its working again :angel:, Ive tried combo "up volume" and "power" buton.
Now Ive got no idea what "Gapps" or "Slimroms addons you want" are, but after mad long startup (with SlimKAT logo on the screen), it seems that this system is working. Its much faster than befo I can see. It's RUNNING! :laugh:
--
UPDATE 2: Play Store refuses to open on this new system after I installed it. "Unfortunately, Google Play Store has stopped."
I have just flashed this ROM:
[Kitkat][Nightlies] CM11 Android 4.4 for the Defy(+), it is the most advanced so far as I can see, the freshest release is cm-11-20161124-NIGHTLY-mb52x so half a year old.
If you read instructions on this thread you can see it's installation is somewhat tricky.
It includes rearranging partitions layout and sizes.
If you really want experimenting with flashing Nougat you will probably need the technique to change partitions sizes, and you may edit the values inside the resize.zip according to individual needs (post #5595)
And the half of the links from the first post are empty, however in the middle of the thread there are still working links.
After all it's better to follow this version of installing instructions (post #5584)
Also you can find some files here: http://defy.svolkov.name/quarx2k.ru/
I have done partitions resizing, bootstrap, and managed to flash the first ROM, version: cm11.0-defy-newlife.zip,
however wrongly have done cache & Dalvik reset just after resizing (and before ROM flashing): the result is ROM is working well but cannot boot into recovery anyway (and can't recreate recovery anyway either, even doing:
Code:
cat /sdcard/bootstrap_ext3.img > /dev/block/mmcblk1p1
as suggested in the post: https://forum.xda-developers.com/showpost.php?p=57221743&postcount=6510)
And I'd like have the freshest version, the only way is to flash stock and do everything from a start again. Please if you can, how to flash stock? It is said elsewhere the most critical in it is choosing the right version of sbf file, choosing inappropriate would brick a phone irreversibly! And how to know which one to choose, tutorials here are so convoluted and discussions so chaotic! Afraid of touching anything though!
As far as the ROM itself, although it is the first only cm11.0-defy-newlife.zip it works amazingly well!
It boots quickly, is fast, RAM friendly, nice!
(It has little overclocked processor and this makes using the phone so comfortably, just little overclocked so hardware friendly too!)
pawwaap said:
I have just flashed this ROM:
[Kitkat][Nightlies] CM11 Android 4.4 for the Defy(+), it is the most advanced so far as I can see, the freshest release is cm-11-20161124-NIGHTLY-mb52x so half a year old.
If you read instructions on this thread you can see it's installation is somewhat tricky.
It includes rearranging partitions layout and sizes.
If you really want experimenting with flashing Nougat you will probably need the technique to change partitions sizes, and you may edit the values inside the resize.zip according to individual needs (post #5595)
And the half of the links from the first post are empty, however in the middle of the thread there are still working links.
After all it's better to follow this version of installing instructions (post #5584)
Also you can find some files here: http://defy.svolkov.name/quarx2k.ru/
I have done partitions resizing, bootstrap, and managed to flash the first ROM, version: cm11.0-defy-newlife.zip,
however wrongly have done cache & Dalvik reset just after resizing (and before ROM flashing): the result is ROM is working well but cannot boot into recovery anyway (and can't recreate recovery anyway either, even doing:
Code:
cat /sdcard/bootstrap_ext3.img > /dev/block/mmcblk1p1
as suggested in the post: https://forum.xda-developers.com/showpost.php?p=57221743&postcount=6510)
And I'd like have the freshest version, the only way is to flash stock and do everything from a start again. Please if you can, how to flash stock? It is said elsewhere the most critical in it is choosing the right version of sbf file, choosing inappropriate would brick a phone irreversibly! And how to know which one to choose, tutorials here are so convoluted and discussions so chaotic! Afraid of touching anything though!
As far as the ROM itself, although it is the first only cm11.0-defy-newlife.zip it works amazingly well!
It boots quickly, is fast, RAM friendly, nice!
(It has little overclocked processor and this makes using the phone so comfortably, just little overclocked so hardware friendly too!)
Click to expand...
Click to collapse
Again I want to thank you for your response. On the verion of system Ive installed I cant use my camera for video recording because of lack of some codecs it says and I cant watch YouTube. 'Google Services' crashes. The only way I could download some decent apps was from 'Aptoide'. 'Roehsoft Ram Expander' needed Google services so it wont open (ive download 'Kernel audiutor' however I dont have class 10 card yet so I dont know if its good at all). I wont be fighting with this anymore, I am going to try mentioned 'CM11 Android 4.4 for the Defy(+)'.
So I have to go "Recovery" in this secret startup menu before I install it? I mean do I have downgrade my system before instalation of new one? Or just follow the instructions straight from the beggining I dunno. But I dont want any complicated things you know..
--
The links are dead, but Ive found them files:
defy.7z
Now, you metrioned two rom's but which one is less tricky, cm11.0-defy-newlife.zip or cm-11-20161124-NIGHTLY-mb52x.zip?
You know, I have installed cm-11-20161124-NIGHTLY-mb52x.zip at last, after exciting night of attempting flashing any stock ROM and then following the procedure exactly from the first post of "[Kitkat][Nightlies] CM11 Android 4.4 for the Defy(+)"
and the updated files: new_bootstrap and resize, found here
It costed many efforts of blindly "trial and error" flashing one by one stock ROMs, until found the one which turned on my phone with anything else than black screen!
And everything it was to have possibility of flashing cm-11-20161124-NIGHTLY-mb52x.zip instead of already running cm11.0-defy-newlife.zip.
And you know what? The version cm11.0-defy-newlife.zip seemed running better than the freshest one!
It was, what is most important: faster!!!
And anything else seems the same (so far)!!!
Is the any rationale behind hustle and bustle of flashing the "NIGHTLY" and exactly for what?
Question of stability which user gets know only after some time?
Anyway the speed is everything in such thin hardware like Defy+ and i can't resist an impression cm11.0-defy-newlife.zip is way faster!
And what's more, you probably can flash cm11.0-defy-newlife.zip without the whole convoluted procedure of resizing partitions! (needs checking, if you want simplest way you had better resize partitions )
In fact this version of ROM is the same as:
Quarx said:
8. Install cm11.0-defy-newlife.zip (It's latest cm11 from 23sep with changes for new table)
Click to expand...
Click to collapse
but cm11.0-defy-newlife.zip was to try if the only resizing procedure itself worked at all (and for users to send feedback).
In fact resizing partitions is needed only for the next ROM versions (of which the freshest is cm-11-20161124-NIGHTLY-mb52x.zip):
"the nightlies AFTER 01 Oct are for the new partition table".
(Aha, cm-11-20161124-NIGHTLY-mb52x.zip probably is odexed, while cm11.0-defy-newlife.zip is deodexed, it needs confirmation)
And if you needed flashing stock and had doubts how, then write, I'd gladly help and share the knowledge painstakingly acquired this night.
It is amazingly simple and safe, there're few simple basic things but if you needed found them by yourself in this forum you would probably get panicked
It is about how simple things people can mess up! ?
pawwaap said:
And if you needed flashing stock and had doubts how, then write, I'd gladly help and share the knowledge painstakingly acquired this night.
It is amazingly simple and safe, there're few simple basic things but if you needed found them by yourself in this forum you would probably get panicked
It is about how simple things people can mess up!
Click to expand...
Click to collapse
Thank you my friend. Ive installed cm11.0-defy-newlife.zip. Its fine because my camera can now record videos but still it cant play it. :crying:
YouTube videos also wont load, however internet is fast and so on.
--
Google Play still dont work, same error. I kinda came to terms with it as I have Aptoide, but I want to use YouTube..
And what do you use to watch YouTube videos? Advise third party apps, e.g. SnapTube etc, instead of YouTube application. In fact forgot installing gapps at all and it makes me happy You only now made me think about it In such thin hardware it is better to have microG (μG) (for apps refusing running without Google Services) and/or Yalp Store for Play Market access
If you insist using bulky Google then try opengapps.org
pawwaap said:
And what do you use to watch YouTube videos? Advise third party apps, e.g. SnapTube etc, instead of YouTube application. In fact forgot installing gapps at all and it makes me happy You only now made me think about it In such thin hardware it is better to have microG (μGl) (for apps refusing running without Google Services) and/or Yalp for Play Market access
Click to expand...
Click to collapse
I guess gapps are apps for new software? Ok so now that I have downloaded SnapTube I still cant play any video. Its loading but wont start just like videos on my phone storage or just recorded
Hah I think its a bit off topic what we made here, I should change name of the tread
--
Ive read on some native forum that after codecs instalation he problem disappeared I try to find some
I have just recorded a video of my dog, sent it via email (AquaMail), received it in a mail to myself and played it with system player, pretty well!
It is possible freshest NIGHTLY ROM has issues solved, how to check it (without Google)?
And can you play videos self recorded with this phone?
OpenGapps.org provides you ability to choose what package, how complex (I always choose "pico"), and for what platform (yes, KittyKat is still supported) you download.
pawwaap said:
I have just recorded a video of my dog, sent it via email (AquaMail), received it in a mail to myself and played it with system player, pretty well!
It is possible freshest NIGHTLY ROM has issues solved, how to check it (without Google)?
And can you play videos self recorded with this phone?
OpenGapps.org provides you ability to choose what package, how complex (I always choose "pico"), and for what platform (yes, KittyKat is still supported) you download.
Click to expand...
Click to collapse
OK its seems that Google Play cant be downloaded straight to the phone (.apk) after installing new system but gapps worked for me and I got my Google Play working again now. Still no luck with videos on YouTube but vlc is working on files Ive recorded.
Tritius46 said:
Ive installed cm11.0-defy-newlife.zip.
Click to expand...
Click to collapse
And how have you installed this ROM: with partitions resizing first or on stock layout?
Tritius46 said:
Hah I think its a bit off topic what we made here, I should change name of the tread
Click to expand...
Click to collapse
Yes, you can change for e.g.
"Installing the best ROM nowadays for Defy (+)"
And it is said Defy and Defy+ is the same hardware, just plus is rebranded and has overclocked processor (to 1GHz) and bit bigger battery, see section "Facts" in [GUIDE] All-in-One Defy Beginner's guide
or "Yielding Defy competitive nowadays"
It is still phone unique on the market, searched something for summer, a little waterresistant phone which could suit to any even tiniest pocket. And found Defy is just the only one in this kind, nowadays producers offer big smartphones and if you want something little & watertight then you can buy modern smartwatch - thanx, prefer Defy: bigger battery, faster, and of incomparable comfort of usage, for peanuts! [emoji106]
pawwaap said:
And how have you installed this ROM: with partitions resizing first or on stock layout?
Click to expand...
Click to collapse
Ive just followed the steps here did exactly what is written step by step from the beggining.
I think now the only is playing videos. Videos I have recorded (on the phone) can be played back only in vlc but still with lags. Same for vids online, however if I choose mobile version of YouTube and try to play stream in vlc it worx but very poor quality. I tried many things without any success, for eg. Flash Fox but the problem is rather in system files than settings and apps itself.
In my custom system I could playback any video.
Tritius46 said:
Ive just followed the steps here did exactly what is written step by step from the beggining.
Click to expand...
Click to collapse
It's irrelevant for video playing but I think it is better to follow the first post from the thread and use the files:
new_bootstrap & resize (instead of PrepareZip_1 & PrepareZip_2),
new_bootstrap has different size than PrepareZip_1 and is newer, something has been changed.
Tritius46 said:
I think now the only is playing videos. Videos I have recorded (on the phone) can be played back only in vlc but still with lags.
Click to expand...
Click to collapse
You see, I play with phone system player any videos recorded with phone system camera application without any problem.
Is the newest NIGHTLY ROM better in the sense the issues have been ultimately repaired?
If so, make android backup of data partition, reboot into TWRP, wipe cache, Dalvik, data (factory reset), and flash the newest NIGHTLY!
(Yet if you enjoy playing with comparing the two system you may wait )
And maybe before flashing next ROM do these newer new_bootstrap.zip & resize.zip flashing (just in case: of avoiding extra issues).
Tritius46 said:
Ive just In my custom system I could playback any video.
Click to expand...
Click to collapse
And in Defy?
pawwaap said:
It's irrelevant for video playing but I think it is better to follow the first post from the thread and use the files:
new_bootstrap & resize (instead of PrepareZip_1 & PrepareZip_2),
new_bootstrap has different size than PrepareZip_1 and is newer, something has been changed.
Sent from my E2303 using Tapatalk
Click to expand...
Click to collapse
OK so I will try now cm-11-20161124-NIGHTLY-mb52x with new_bootstrap and resize. Do I have to just install them like before right? It will replace system I have now?
--
UP:
pawwaap said:
wipe cache, Dalvik, data (factory reset), and flash the newest NIGHTLY!
Click to expand...
Click to collapse
Ok I get it
If so, make nandroid backup of data partition, reboot into TWRP, wipe cache, Dalvik, data (factory reset), and only then (but immediately without rebooting after wiping) do these newer new_bootstrap.zip & resize.zip flashing!
The files you can find here
After flashing NIGHTLY successfully, boot it, follow the initial wizard etc, check if it works ok, and if so reboot into TWRP again to restore your data nandroid backup.
If you don't care about previous data give in with it and configure your Android anew
pawwaap said:
And in Defy?
Click to expand...
Click to collapse
Dont get me wrong, I meant my system version android which came to me with my phone purchase (android 2.3.6 or something dont remember). And its definitely not prob with camera but system video player, plus YouTube dont play too so definitely some playback issue..
Omg omg E:Error executing updater binary in zip '/sdcaed/kitkat 4.4/cm-11-20161124-NIGHTLY-mb52x.zip' 'FAILED' what todo? Reboot and try again?
Maybe file was corrupted
Hi everyone,
So couple of year ago I worked at a start-up company that had an Android project. So I'm not new to flashing images (ROM, Recovery, radio...), and I know most basic tools like ADB (and I'm technical person in my daily life). That being said - I remember the pain when the Radio image doesn't fit the firmware, and you have to play around with stuff to make reception work again. or the Recovery image won't fit the ROM etc etc. I'm not sure if any of this probably still happen TODAY, but back then when I got my LG-G2 - I decided not to touch it. I don't need anything besides the basic options (making calls, taking pictures).
I'm still using Stock with 4.4.2 - and the phone is getting lagy each passing day to the point it's time to root it and install a custom rom.
As I mentioned above, I want it to be quick and painless. Sadly, I don't have the time to do insane amount of research right now, mainly because I have a 3 weeks old born at home - and I prefer to use my free time hanging with it that Q&N issues with my phone
So here's what I need your help with:
1. A recommendation for a tool to save all phone settings. Mostly - App settings, and OS settings (even though I probably not going to go for Stock again, but it doesn't hurt to back it up).
2. An instruction how to flash D802 (there' so many options this days...). My Kernel version is 3.4.0.
3. Recommended ROM to use. Here's what I need from a ROM.
a. I probably want to upgrade to more safe rooted Android version (I can't for example handle permissions on 4.4.2).
b. With that, I don't want to install the latest Android only to figure it's running slowly on LG G2, I want the interface to be snappy (the Stock was snappy for a while).
c. I prefer Minimal ROM if possible with Google Apps installed. If I'll need something, I can install it myself.
d. One of the reason I didn't root up until now, was because people mentioned camera quality is meh with non stock roms. If possible, I will like to have a decent Camera quality.
e. I use my phone as a music player often. So good sound quality is important to me (and maybe even build in Parametrized EQ?).
Thank you!
Reading around the forum would have taken just about the same amount of time than writing your post. A post, mind you, that will get you the same as what you can already find with ease.
You managed to write with your kid around. Last time I checked, browsing takes less effort.
Rant out.
Instead of a rant, here's an actual help for people who might find it useful in the future and lack the time to do some proper research (as it took more than the 5 minutes it took me to write the original post). Please note that I won't take any responsibility for possible damages you may do to your system. Please use at your own risk. Also, note that I only tried it on LG G2 802 with Stock Kit Kat (4.2.2) and other version/OS version might not work.
I wasn't clear to me if 'One Click Root' work with Kit Kat bootloader, so I used 'ioroot'. When your done rooting your phone, you will need to flash a TWRP recovery. The easiest way to do it is by using AutoRec. However, the TWRP recovery installed with AutoRec doesn't have Thermal protection, and is dangerous to use according to the forums. So the next thing will be flashing a new TWRP version from the recovery. Blastgater have tweaked TWRP Recovery for LG devices. You can download the latest version here. It's basically a zip file you flash from within your old TWRP.
Regarding ROM, after doing some research - it looks like Lineage will be the best 'all-around' rom to use. Liveage 15/16 were too slow for my liking, so I went with 14.1 (Android 7.1) which was enough for me and snappy to use. However, the tricky part if your plan on using Lineage, is to flash a bootstack as the one coming with Stock won't work. It's just another zip to flash directly from the recovery and can be found here.
So this is just the high-level process, and I highly suggest checking the specific on the links I sent. It also helps if you know how to handle 'adb' and know the basic stuff like what bootloader and recovery are
Good luck.