Related
To prevent new users asking the same questions again and again, i decided to write this little FAQ and introduction about ROM flashing.
To all of you who are new to ROM flashing: Don't mind to ask, we all will help you if possible, but you should understood that it is annoying when the same question is asked 20 times a week. So please first search, then ask. Thank you.
If someone finds an error please do not post it, just send me a pm and I will correct it. Additional FAQ entries will be added regulary. If someone likes me to add a question, please send the question and the answer to me via PM and i will add it asap.
Thank you to the whole community, because without all of your information, this FAQ could not be possible.
If you are new to ROM flashing, please read this thread. It will give you information about your device and a short introduction on how to flash another ROM to your phone.
Below you will find the ROM flashing FAQ and the Introduction to ROM flashing.
Please feel free to add links to this thread to your signature using the following code:
[b][url=http://forum.xda-developers.com/showthread.php?p=1790046#post1790043]ROM flashing FAQ[/url][/b]
[b][url=http://forum.xda-developers.com/showthread.php?p=1790046#post1790046]Introduction to ROM flashing[/url][/b]
Click to expand...
Click to collapse
ROM flashing FAQ
ROM flashing FAQ:
Q: What is a ROM?
A: A ROM contains the operating system and often additional software which can be “installed” to your mobile device. Most ROM’s provided by the chefs (people who create cutomized ROM’s) just contain the operating system and additional applications. Shipping ROM’s (ROM’s provided by the manufacturer or official providers) also contain a Radio ROM and a bootloader.
Please notice: A ROM can ONLY be flashed to a device it is made for.
Q: What is a bootloader?
A: A bootloader contains information about your device. It is quite similar to a computer’s BIOS. Official bootloader also have a security option called CID (Carrier-ID) which allows you just to install ROM’s from the provider of your phone. So, if you want to flash another ROM, you first have to turn off this security option by “CID-unlocking” your device. Check the flashing instructions below on how to do this.
Q: What is a Radio ROM?
A: The Radio ROM contains the drivers for the communication devices of your phone. Some ROM’s need one or more specific Radio ROM’s to work properly. Usually the chef, who created the ROM recommends a Radio ROM. But don’t mind, if your Radio Rom does not match, you can always flash another without needing to flash the ROM containing the Operating System (OS) again.
You can check the version of your Radio ROM when you click Start > Settings > System > Device Information or booting your device (there will appear three lines of red text. The Radio ROM version is the number after the R:.
You can download Radio ROM's at the xda-developers FTP-Server in the Uploads/Kaiser/Radio-Folder. Username and password are both 'xda'. To install it, download, extract and execute it. Then follow the instructions on your screen. Flashing a Radio does not delete any files on your device's ROM.
To choose the perfect Radio ROM for you check this thread.
Q: What means CID(-unlock)?
A: All known providers add a Carrier ID to their devices. This CID is added to prevent a device being flashed with a ROM which is not from the provider and/or not designed for your device. Be sure to brick your Kaiser, if you try to flash a ROM designed for a Wizard.
To flash other ROM's, you have to unlock the CID. If you flash another ROM on a CID-locked device, the new ROM will not work properly.
Q: What means SIM-Unlock?
A: Lots of providers want to bind their customers. So they add a SIM-Lock to their devices with only allows to use SIM-Cards using their networks. If you want to use a SIM-Card from another provider, you need to SIM-unlock your device. This can be done by contacting the phone's provider (paid & sometimes free), using a service like www.imei-check.com, or using Jockyw2001's Kaiser SIM Unlocker.
Q: Can I brick my phone by flashing a ROM?
A: To be true… YES. But if you follow all instructions, it is quite implausible that your device bricks.
Q: Does flashing affect the warranty of my device?
A: Yes, but, as long as your device can be flashed again, you will find some help at jcespi2005's thread where you can find dumped original ROMs.
Q: What can I do, if i gain problems with the ROM i flashed to my device?
A: First of all you should inform the creator by posting in the ROM's thread if the problem is not described yet. Then you should wait for an update/fix or, if the issue is a showstopper for you, try another ROM.
Q: Which is the best/fastest/... ROM?
A: Nobody can answer you this properly. There are nearly daily new ROM's here and everybody has different demands to a ROM. If you want to know, which fits best for you, read the ROM description and try the ROM('s). Only you can decide, which ROM is the best (for you).
Q: I own an AT&T Tilt. After flashing another ROM, my hardkeyboard does not work properly.
A: AT&T uses another keyboard layout than HTC. To fix this, install the tilt keyboard fix.cab. You can download it at Dutty's Kaiser CAB Collection.
Q: What is the difference between a hardreset and a softreset?
A: A softreset reboots your device. A hardreset sets all settings back to the ROM's defaults. All of your data, settings and additionally installed programs will be deleted.
Q: What are *.CAB-files and/or how do i use them?
A: Cab-files for WINCE-Devices are different to the files you may have seen (e.g. on your Windows Installation CD). They do not only contain files but also installation information similar like a MSI package. To install them, just copy the *.cab to your Mobile Device and run it from there. Most shipped ROMs delete cab-files after executing, most cooked do not. To be sure, check the registry. If HKLM\Software\apps\Microsoft Application Installer\nDynamicDelete = 0 (DWORD decimal), cab-Files will not be deleted after execution.
Q: I have questions which are not described in this FAQ. What shall i do?
A: First of all search the forum and the wiki (http://wiki.xda-developers.com). Maybe the question has been already answered. If you don't find an answer, create a new thread. As i know from experience, the community will always try to help you as soon as possible.
Introduction to ROM flashing
Introduction to ROM flashing
These are the steps on how to flash your device the first time:
1: CID-unlock your device by following the instructions at pof's HTC Kaiser Hard-SPL v1 - CID Unlock & Flash any ROM to your device (4 free)-thread
This needs to be done to flash a ROM to your device which is not created from your provider (or HTC if you own a device with HTC branding).
Additionally you may check persianowns Kaiser HardSPL Walkthrough Video.
If you are running in a white screen running HardSPL, please read this thread.
2: Search this forum for the ROM, you like to flash. Then download and, if needed, extract it.
3. Check, if your Radio-ROM matches the new ROM. If you don't find any information in the ROM's thread don't mind. You can update your Radio ROM later if you gain any problems.
4. Make sure, your devices battery status is NOT LESS than 50%.
5. Connect your device to your computer and wait until activesync/Windows Mobile Device Center recognizes it
6. Last chance to synchronize and/or backup files. All files and databases will be deleted after performing the next step!
(Optional: If you want to save your text messages and/or eMails, use a tool like DotFred's PIM Backup.)
7. Execute the .exe file you downloaded with the ROM.
8. Follow the instructions and DO NOT disconnect your device until flashing is finished.
9. Disconnect your device from your computer.
10. You need to delete the old activesync/Windows Mobile Device Center partnership, because it thinks, your device is not the same as before... and it is right ^^. Deleting an old partnership is only possible, if the device is not connected.
(Optional) If you want to change the name of your device, do that now by clicking Start > Settings > System > About > Device ID. Enter the new name of your device and click on Ok.
11. Connect your device to your computer, create a new partnership and synchronize. Then configure your device to your needs and if needed install additional software.
Congratulations! You succeed flashing your device!
Great FAQ....simple, concise, and informative
Well done
Excellent post bmueller77!
This should clear up a bunch of the questions that are asked.
thanks for that
its hard to find some basic info on here like this, so can we please sticky
Really Good Thank you...
Can you please make a general version of it and put it in general wiki so that it can benefit all not just kaiser guys
Although I am more interested in HTC Elf Touch version []
you could add my video to it http://www.youtube.com/watch?v=UaCt5pUn6iI
shows how to hardspl
verysmartncool said:
Really Good Thank you...
Can you please make a general version of it and put it in general wiki so that it can benefit all not just kaiser guys
Although I am more interested in HTC Elf Touch version []
Click to expand...
Click to collapse
Let's see. I am already working on a more general FAQ version including info on Windows Mobile but, to be honest, a general flashing introduction would be much more complicated and i want to make it as easy as possible for newbies.
I think it would be better, if someone grabs this thing and would edit it for another device to keep it concise. If anyone is interested, just ask me via PM and i'll send you the whole including vbCode.
persiansown said:
you could add my video to it http://www.youtube.com/watch?v=UaCt5pUn6iI
shows how to hardspl
Click to expand...
Click to collapse
Got it. Thank you.
I have made this thread a sticky upon request.
I feel that this info should be ported to the wiki so that it can be found and edited by all.
At the momnet we have FAR to many sticky's in this section which makes finding anything hard to say the least.
Have a look at the BA section (in my signature) to see what I mean.
Aright, will add a general version to the wiki at the weekend.
Thank You but still have a question
Hi, I just got my HTC TyTn 2 as a present from my dad he got it from orange and got it sim unlocked for me. But I don't like it because Orange has their crappy stuff on it I wont the original stuff from HTC on it like HTC Home etc. I've got my phones detail in my signature can some one plz help i jus want to know if i can use it on my rom n radio version. Thanks.
thx
Super! Thank you!
this thread is awesome...it really help a newbie like me
the wiki is also very helpful
keep up the good work
I've been flashing ROMs for a long time. There is one thing I don't know. Does anyone know what is the reason behind stopping flashing RadioROMs at 95%? Whatever RadioROM I want to flash to my Vario III (keeping the standard T-Mobile ROM) it stops. In the RadioROM thread, there were several cases like mine. Can it be that for being able to flash another RadioROM you have to flash a custom ROM like Dutty or Schaps before flashing the Radio? I cannot recall such problems with Hermes.
Thanks for the guide. Also am not new to this I haven't done this in a while. ROM Flash went without a hitch. Keep up the good work.
haamedullah said:
Hi, I just got my HTC TyTn 2 as a present from my dad he got it from orange and got it sim unlocked for me. But I don't like it because Orange has their crappy stuff on it I wont the original stuff from HTC on it like HTC Home etc. I've got my phones detail in my signature can some one plz help i jus want to know if i can use it on my rom n radio version. Thanks.
Click to expand...
Click to collapse
So long as your phone is SIM unlocked as in you can use any sim card in it then you flash it exactly the same as described in this thread. I flashed mine no problems. Does that answer your question or are you just wanting the home screen without flashing? If so Im not sure if thats possible, I heard some people say that you can enable it on orange phones but I flashed mine before I ever tried it.
Excellent FAQ!
Now i can get my hands dirty with that so called "ROM flashing" .
noobie question, but how do i install a cab file? thanks
I've been getting my feet wet in cooking, mostly thanks to Alex's tutorials and I'm running in to a weird issue. Apps that I have not selected in Package Tools 2.7 are being installed with my ROM. According to the FAQ/QA in the tutorial, Alex says I should just remove those that show up from the packages directory.
My question is why are they showing up? Does anyone know. I assume it's a precondition of either the rom or whatever file is used to make the rom.
Which brings me to the next question, I can't seem to find a good set of threads that describe how the process works other than Axel's tutorial. I'm assuming there is a manifest somewhere that the package tools builds then passes to the cooker. Can someone point me to or outline the actuals steps?
Thanks.
GApps2zip
This script makes an update.zip file that only contains the Google Apps from the HTC release of the 1.5 firmware upgrade for the ADP 1. This update.zip should be flashable on any build and it should work without a problem, but since I'm just a n00b sophomore in highschool, I am naturally poor and can't guarantee anything.
Because there are already a few alternatives to this for Linux and the majority of Android users use Windows, I decided to make this a Windows-only batch script.
You MUST have the Java Runtime Environment installed in order to run this script! The signing utility requires Java and you won't be able to flash an unsigned update. If it doesn't work even if you have Java, you may have to reinstall Java as it is not in your PATH variable for whatever reason.
UPDATE: Updated and, as far as I know, should now work fine with the 1.6 developer images from HTC as well as personal NANDroid backups of most all 1.6 Android ROMs.
INSTRUCTIONS
1) Either do a or b. It is advised to use a personal NANDroid backup (b) as it does not violate any licenses, but it has not been testeda) Google for the file "signed-dream_devphone_userdebug-img-14721.zip" It should be on the HTC support page for the ADP 1, but it wont be the first result in Google. It is not advised to use this method as you need to agree to a license prohibiting modification of the file in order to download it. Rename the file to "backup.zip"b) Restore to a regular build that has all of the Google Apps (like the regular OTA cupcake update) and then run a NANDroid backup. Then make a zip file that only has the system.img file from the NANDroid dump and name the zip "backup.zip"2) If you haven't already, unzip the entire contents of the gapps2zip.zip file into a directory. For sake of simplification, I am assuming it is unzipped to C:\gapps2zip
3) Place the "backup.zip" file in the same directory as the GApps2zip.bat file (C:\gapps2zip) and DON'T rename it or unzip it.
4) Open up a command prompt window (Hit Windows + R, type in CMD, then click OK)
5) cd to the directory in which the GApps2zip.bat file, utils directory and the backup.zip file. For example:
Code:
cd C:\gapps2zip
6)Type in "GApps2zip.bat" (without the quotes) and hit enter. Watch and wait.
7) If all goes well, you should have an update_gapps.zip folder in C:\gapps2zip. Put it on your SD card, make a NANDroid backup, and flash after flashing an AOSP (Android Open Source Project) build that doesn't include the Google Apps.
Credits
Cyanogen for his hard work and dedication
Maxisma for a similar script on which this is based
Google for their ingenious ideas (although their legal department can be a pain)
Everyone who is willing to test this script out
Everyone else xD
Redistribution
Feel free to redistribute the archive wherever you like, but please give me credit along with Maxisma and do not modify the archive in any way.
Great job unk!
amgupt01 said:
GApps2zip - Created by Ankush Gupta (twitter.com/unkzdomain and unkzdomain.com)
This script makes an update.zip file that only contains the Google Apps from the HTC release of the 1.5 firmware upgrade for the ADP 1. This update.zip should be flashable on any build and it should work without a problem, but since I'm just a n00b sophomore in highschool, I am naturally poor and can't guarantee anything.
Because there are already a few alternatives to this for Linux and the majority of Android users use Windows, I decided to make this a Windows-only batch script.
You MUST have the Java Runtime Environment installed in order to run this script! The signing utility requires Java and you won't be able to flash an unsigned update.
This script does NOT work on a build that includes the new market as there are some incompatibilities with the files for it and the ones provided by HTC (namely the MarketUpdater.apk for the new market). This is pretty much doesn't matter however, because all AOSP builds will not include ANY Android market anyways.
INSTRUCTIONS
1) Google for the file "signed-dream_devphone_userdebug-img-150275.zip" (It should be on the HTC support page for the ADP 1, but it wont be the first result in Google)
2) If you haven't already, unzip the entire contents of this zip file into a directory. For sake of simplification, I am assuming it is unzipped to C:\gapps2zip
3) Place the "signed-dream_devphone_userdebug-img-150275.zip" file in the same directory as the GApps2zip.bat file (C:\gapps2zip) and DON'T rename it.
4) Open up a command prompt window (Hit Windows + R, type in CMD, then click OK)
5) cd to the directory in which the GApps2zip.bat file, utils directory and the signed-dream_devphone_userdebug-img-150275.zip file. For example:
Code:
cd C:\gapps2zip
6)Type in "GApps2zip.bat" (without the quotes) and hit enter. Watch and wait.
7) If all goes well, you should have an update_gapps.zip folder in C:\gapps2zip. Put it on your SD card, make a NANDroid backup, and flash after flashing an AOSP (Android Open Source Project) build that doesn't include the Google Apps.
Credits
Cyanogen for his hard work and dedication
Maxisma for a similar script on which this is based
Google for their ingenious ideas (although their legal department can be a pain)
Everyone who is willing to test this script out
Everyone else xD
Redistribution
Feel free to redistribute the archive wherever you like, but please give me credit along with Maxisma and do not modify the archive in any way.
Click to expand...
Click to collapse
when it asks u to replace system.img, do you click yes or no?
Looks interesting ill test it out later
Guyver75 said:
when it asks u to replace system.img, do you click yes or no?
Click to expand...
Click to collapse
You click Yes. You shouldnt have extracted the zip though, but it won't make a difference anyways.
Looks interesting ill test it out later
amgupt01 said:
You click Yes. You shouldnt have extracted the zip though, but it won't make a difference anyways.
Click to expand...
Click to collapse
oh ok, oops. i clicked no. guess ill have to redo it
ok trying to understand this. From what i get is you download, Lets say cm 4.2 without google (made up rom dont go looking for it)
then you flash that to are phone.
next when flash update_gapps.zip
Then we will have a cm rom with google apks?
And in returns the update_gapps is kinda like a theme only adding the needed files?
xile6 said:
ok trying to understand this. From what i get is you download, Lets say cm 4.2 without google (made up rom dont go looking for it)
then you flash that to are phone.
next when flash update_gapps.zip
Then we will have a cm rom with google apks?
And in returns the update_gapps is kinda like a theme only adding the needed files?
Click to expand...
Click to collapse
Exactly. The only thing is that since this uses an official, legal source, it doesn't include the new market and stuff...
Ok cool but once 1.6 adp1 is out we will have to update the script and do this again?
amgupt01 said:
This script makes an update.zip file that only contains the Google Apps from the HTC release of the 1.5 firmware upgrade for the ADP 1.
Click to expand...
Click to collapse
I applaud your efforts to help the community. Many thanks.
For those who think this is proof modding and this community will live on, think again. What he's doing aids and abets violation of Goog's rights. This thread will be locked and the links taken down. Welcome to the new world of Android.
xile6 said:
Ok cool but once 1.6 adp1 is out we will have to update the script and do this again?
Click to expand...
Click to collapse
Well, provided that HTC distributes ADP 1.6 the same way as they are 1.5 and that the file dependencies for closed-source apps are similar, we could just reuse this same script with maybe a few minor modifications.
ytj87 said:
I applaud your efforts to help the community. Many thanks.
For those who think this is proof modding and this community will live on, think again. What he's doing aids and abets violation of Goog's rights. This thread will be locked and the links taken down. Welcome to the new world of Android.
Click to expand...
Click to collapse
How does it aid and abet to violations of Google's rights? I am basically linking to an official mirror (HTC) that is licensed by Google to distribute the files.
@ amgupt01
Thanx now all we got to do is let the builds continue.
great job mr. sophomore, you should get together with cyanogen on this although i'm sure he's probably going to do something similar.
is it safe to sign in to google with the newly created update_gapps2zip?
amgupt01 said:
How does it aid and abet to violations of Google's rights? I am basically linking to an official mirror (HTC) that is licensed by Google to distribute the files.
Click to expand...
Click to collapse
I think the issue is that Google doesnt want its closed source apps put on non google-experience phones. This guy's method allows just that.
Cyanogen's method (from what I can gather) is to run an app on your phone that backs up the apps that you have on your phone (presumably licensed copies that you acquired when you purchased your phone, or during an OTA update), and then restores them after you run his barebones ROM. In this manner, you are only using backed up copies of software you are entitled to use.
I read somewhere (maybe in Google's C&D? I'm to lazy to go look) that Google does not allow these applications to be copied or extracted or something to that affect.
Honestly, why on earth would we expect them to react any differently?! This is a growing pain. We will all be better for it when its passed.
Here's how I'm planning on riding this out:
1. When Cyanogen releases 4.2, I will unroot my phone, and get the most recent OTA update from Tmobile.
1. Install Cyanogen's 4.2 ROM, using whatever method of installation is required to back up my closed source applications and restore them.
2. Continue to update Cyanogens ROMs this way until we discover that our old closed source apps are no longer compatible with our state of the art ROM.
3. Begin to seek out alternative apps, or check progress of the new "Open Android Alliance" or whatever those guys are calling themselves since this whole fiasco started, to see how feasible that option is.
4. Buy a new phone? I mean, how far down the road are we talking here?! And yes, when the time comes, assuming Google doesn't do something completely draconian that makes us pine for the good old days when they sent a C&D to Cyanogen, it will be another Android phone (subsequently rooted, of course)
I don't really see another legal option.
Code:
Cyanogen on twitter
So I think I've come up with a solution that should work and not violate any licenses. Just need to polish it up a bit.about 14 hours ago from twidroid
Thanks for this script.. i am amazed of how fast the community is getting up from the C&D .... Open Android Alliance is kicking off, Maxima is already out with a NO Google ROM, and this script, to get google's apps... wonderful...
amgupt01 said:
How does it aid and abet to violations of Google's rights? I am basically linking to an official mirror (HTC) that is licensed by Google to distribute the files.
Click to expand...
Click to collapse
amg, I'm worried on two fronts.
1, HTC is redist'ing Goog bits. They may very well get a c&d. I can't imagine HTC has a license to freely distribute them to anyone and everyone. I have to believe the license is for use on HTC hardware, not any user worldwide as download and extraction would allow.
2, you are aiding in the grabbing of those bits that a user may not have license to.
Granted, I know the vast majority of us have license. But there a few non-Goog experience phone owners around here. I suspect the mods will lock down.
But again... I think that would be wrong. We have license to the bits and grabbing them from HTC is not a violation IMO. But we'll see.
Thank you.
amg,
From the HTC license page when you download:
-----
You may not copy (except for backup purposes), modify, adapt, redistribute, decompile, reverse engineer, disassemble, or create derivative works of the Google Software or any part of the Google Software. You may only load the Google Software onto the Android Developer Phone 1, and except in conjunction with third party software that makes up the Android system image, you may not combine any part of the Google Software with other software, or distribute any software or device incorporating a part of the Google Software.
-----
So it's clear this is illegal. I think HTC will have to pull this down sooner or later as widespread extraction starts.
btw, I think you're fine. HTC will hear from Goog and this thread will be locked. But otherwise don't worry.
SuperJustKitchen v0.9 Released.
Go to my site: http://justkitchen.info to get the updates and the info. It takes to long to update every device's forum that is supported, and I plan to support all devices, eventually.
Word of warning:
Not all EXT's have been tested or modified for the every device. Please test test and test and then let me know which packages don't work and what YOU've done to fix them. (I don't have time to fix ALL of them by myself.) Some packages will only be compatible with some devices.
(I'm no longer updating each thread separately for each device but just updating my site and posting the release info here. I will only update each thread to say that a new version is out.)
**Warning**
Before using this kitchen, you MUST read the whole thread. Any questions that have been answered will be ignored. This is your only warning.
**Disclaimer**
I am not responsible for any damage that may be done to your phone with a ROM created in this kitchen.
I am not responsible for any damage done to your computer.
I am not responsible for anything... at all.
Introducing SuperJustKitchen!
SuperJustKitchen is based on [http://forum.xda-developers.com/member.php?u=843218"]airxtreme[/URL]'s osKitchen Zero. All credit on for the kitchen backend goes to him.
Features
A completely stripped ROM. (Work in progress for some devices.)
LZX and XPR compression (Also option for No compression.)
Auto clean files that are language specific or DPI specific that your ROM does not need
Auto port missing language MUI files
Automatic rec'loc'ing for devices without native 6.5 nk's
6.1 and 6.5 support
Auto XIP and SYS porting
Auto NBH packing
Tool to convert OEM packages to EXT packages
Auto file conflict fix (don't have to removing older file that conflict (not that there are any. )
Save custom ROM settings (for cooks for multiple ROMs)
Cook multiple languages at the same time with the same ROM settings (Have to add language support yourself. I removed the required MUI's a while back because they made updating the kitchen and adding devices a nightmare.)
MUCH better organization of EXT packages
Active development instead of a program that is no longer being developed
Cleaner and easier to use interface
A built-in and customizable Tutorial section
And more!
Builds included
21056 - WM6.1
23658 - WM6.5 with new redesigned GUI
At the moment, this is an ENGLISH (WWE) only kitchen. This might change...
NOTE: In order for me to keep track of whether my time was well spent or wasted, if you use this kitchen to make a ROM, please either include SJK in the name or just mention that it was SJK cooked in your ROM's thread.
NOTE: This kitchen assumes that you know how to flash through SD, recover from a bad flash and are able to backtrack your steps to figure out how you broke your own ROM. If you do not understand these, please learn them first. Do not PM me asking me. I have written numerous walkthroughs on all these except on how to backtrack your steps. For that, just remember what you're doing as you do it and keep backups.
If you find any issues, PLEASE report them to the bug tracker in my website. It will help me make this kitchen better!
ENJOY!!!
COOL......
Kwel, great booster for new chefs..!!!
error..error....
The elf/elfin side is untested (as I didn't have a tester for it) so let me know if you run into any problems.
Please also post any problems in my bug tracker on my site. Thank you
ivanmmj said:
The elf/elfin side is untested (as I didn't have a tester for it) so let me know if you run into any problems.
Please also post any problems in my bug tracker on my site. Thank you
Click to expand...
Click to collapse
already posted to ur site.....
saurabh88 said:
already posted to ur site.....
Click to expand...
Click to collapse
Please use the bug tracker. (It's one of the links on the site on the left hand side.)
But for now:
ok fine..in windows 7 when i cooked for elfin everythings work fine when i havent include any ext packages... it buikd .nbh but there is update 270error.. ok lets take another look..when i had included most of the ext packsges for first foyr times it gives me oskitchen not responding..after sometime succed in making.nbh file but same 270pdate error..... so what is probleml?... ok if u can plz add function of adding multiple or all ext packages...i have to do it manually.. i think it is promising kitchen but wait...
Click to expand...
Click to collapse
Are you HardSPL'd? If so, do you have the file size limit removed? Also, don't include most of the packages. Your device only has so much space. You're not supposed to include that many programs.
ivanmmj said:
Please use the bug tracker. (It's one of the links on the site on the left hand side.)
But for now:
Are you HardSPL'd? If so, do you have the file size limit removed? Also, don't include most of the packages. Your device only has so much space. You're not supposed to include that many programs.
Click to expand...
Click to collapse
hspl 3.10cmnox...
yes i had remove the file size limit...
file size wa 89mb....
i registered in ur site...ok...
ivanmmj said:
Please use the bug tracker. (It's one of the links on the site on the left hand side.)
But for now:
Are you HardSPL'd? If so, do you have the file size limit removed? Also, don't include most of the packages. Your device only has so much space. You're not supposed to include that many programs.
Click to expand...
Click to collapse
hspl 3.10cmnox...
yes i had remove the file size limit...
file size wa 89mb....
i registered in ur site...ok...but when i go to bug tracker it says helllo guest..i also activate my a.c. but no use..
tried by two gmail &yahoo id but .....
saurabh88 said:
hspl 3.10cmnox...
yes i had remove the file size limit...
file size wa 89mb....
i registered in ur site...ok...but when i go to bug tracker it says helllo guest..i also activate my a.c. but no use..
tried by two gmail &yahoo id but .....
Click to expand...
Click to collapse
It shows that you are registered twice and are activated on both accounts.
I do not have the ability to see passwords. IM me one of the usernames and passwords that you used so I can troubleshoot.
As far as the ROM goes:
If you have an elf, that file size is massive. Remember that the limit only removes the lower limit of a 50mb requirement. The elf doesn't have much space. Do not enable so many things. If you must have all those things, at least enable LZX compression and EXT-UPX compression.
ivanmmj said:
It shows that you are registered twice and are activated on both accounts.
I do not have the ability to see passwords. IM me one of the usernames and passwords that you used so I can troubleshoot.
As far as the ROM goes:
If you have an elf, that file size is massive. Remember that the limit only removes the lower limit of a 50mb requirement. The elf doesn't have much space. Do not enable so many things. If you must have all those things, at least enable LZX compression and EXT-UPX compression.
Click to expand...
Click to collapse
i
i have elfin.....
i had use lzx method....
no one try this?
plz report bugs lol....we got new to try?????
I tried - and already reported into BTS. Corrupted image is reported by RUU everytime I try to flash, does not matter which OS or settings I use. fully unlocked elfin, ipl&spl 3.10
nocturne said:
I tried - and already reported into BTS. Corrupted image is reported by RUU everytime I try to flash, does not matter which OS or settings I use. fully unlocked elfin, ipl&spl 3.10
Click to expand...
Click to collapse
same problem...
even friend of mine from opal have same problem..
dont know y this happen?
wait for the owners.
Looks like there is a corruption somewhere in the kitchen. It is affecting every device. I think it has to do with the executable I changed last minute before updating the kitchen. I'll check myself on my computer.
any update yet?
I've been home sick with the flu so I haven't even touched my computer since. I will let you know more tomorrow. I should get some time to work on it, then.
Get well soon! We are awaiting yout kitchen, seems to be really nice once finished
ivanmmj said:
I've been home sick with the flu so I haven't even touched my computer since. I will let you know more tomorrow. I should get some time to work on it, then.
Click to expand...
Click to collapse
oh sorry to here...get well soon.
i m very eager to try this new kitchen...
Thanks guys.
Do me a favor.
Go to your sources folder and delete the "_Compress" folder then try to cook and flash a ROM. If it works, then that was the problem all along... he moved the folder to another location but the kitchen still reads both.)
OK, so you messed up your device real bad trying to do something and it needs a full flash of the original firmware. Well, lucky you I am here to help you in your journey back to your device's roots, the good old days where everything worked just as it should.
Now, I am gonna be very honest with you about some stuff:
- This is my first XDA post and I really wish it were better formatted;
- English is not my first language, so I really hope this is understandable to everyone; (feel free to correct me)
- I have 0 responsability for whatever you do to your device, so if you f*ck your device up so bad it doesn't even turns on anymore, its not my fault.
!!!!!!! IMPORTANT !!!!!!!
The firmware provided here works ONLY for MOTO E6 PLAY, it WONT WORK with ANY variation. DONT try to install it in any device other than the bali, and if you do, DO NOT BLAME YOUR DEVICE LOSS IN ANYBODY BUT YOURSELF.
Well, that said, the procedure:
Edit:
Apparently, the Bali itself comes in more than one version (not impressive, a detail I definitely should have paid more attention to). There are the
XT2029-1, XT2029-2 and XT2029-3. In the device's configuration app, under System, in Regulatory Information, you can find which one is yours.
First, download the file correspondent to your version from here: https://motostockrom.com/?s=XT2029
Notice that the files that appear for download first aren't the most recent ones. To be certain that you downloaded the most recent build to your version, check it in the ZIP's filename, e.g.: Motorola_Moto_E6_Play_XT2029-3_MT6739_POA29.550-81_2003_20200311_9.0.zip (date is in the YYYY/MM/DD format)
From now on, I'll be making a lot of references to the downloaded file's directory structure. To mitigate any possibility of confusion, I'll be referencing the root of the directory as / and any sub-folder as /Folder/
After that, extract the files from the ZIP. Looking inside /, you'll find the firmware files under /Firmware/ and links to pretty much all you need to flash the original firmware, bootloader, recovery, and even instructions to recover the device's IMEI.
Our device has a MediaTek chipset, so SP Flash Tool is almost the sole thing that is needed to recover a soft broken device (Only problem would be if the devices scatter file weren't available, but fortunately this isn't the case).
Inside the /Driver/ folder, you'll see links to necessary drivers for the computer to correctly identify the device. Follow the links, download and install the drivers.
Refer to the /SP Flash Tool/ directory. Follow the link inside it, download the latest version of the tool for your computer's OS (Windows/Linux);
Now refer to the How To Flash link in /, be it the (Tutorial) or (Video) one, which suits you better. Follow the instructions very carefully and thoroughly and you shouldn't have any major issues flashing the firmware. After the flash is done and the device reboots, congratulations! You've made it! :victory::highfive:
DISCLAIMER:
I like to give credit where its due. Inside /, you'll find a credits file. That website isn't mine, and the development of the file and the tutorial was completely made by them, so all the credits go to the proper owners of the website. I am just sharing it here for the benefit of the community.
Well, if you have any questions, feel free to post a response. I am no Android OS developer myself (though I do develop some other stuff - Java and Python mainly - and am a OS administration and troubleshooting geek, Android is still very shady and very out of my league for me), but I'll be happy to help with anything I can.
Happy Hacking!