This file protects your phone from running below a dangerous level and potentially rendering X10 devices to an unusable or hard brick.
Hello XDA developers
Latest Version 3 :: Please use the latest version and report back the contents of - /data/local/tmp/extract_charger_status.txt - with any issues and state which firmware you were using this with.
I've identified an issue after killing an X10a involving the offline charger. I hope the following can save any further problem's by using the following charger_fix_v3.zip with xRecovery as it is a simple case of rebooting into xRecovery and loading the update. This file is safe for X10 owners as it introduces a stock SE file back to the system, which if not present can render the system a brick.
[ROM] - TripNRaVeR - TripNMiUI - should not be used with this patch as an unknown issue exists with the charger that is currently being researched, until further notice DO NOT apply this update if you are using TripNMiUI or any variant.
There is no SETUID for Android. Android developers state there is no need as Dalvik code will never require elevated or root permissions and hence, it introduces a potential security flaw.
Q: What is it?
A: SE Official charger file - /system/bin/charger - has special permissions which can not be set by root or any other user, the file need's to be moved into place, as it contains setuid or the "Sticky" Unix file system permission.
Wait! How about - chmod 06755 or chmod 04755 - I hear you say? Forget it.. This is not a simple file, it's a Linux binary an ELF Linker file that contains critical system links to (among others//).. the following;
Code:
/sys/class/power_supply/battery/capacity
/sys/devices/platform/msm_pmic_vibrator/enable
/system/bin/chargemon
Nothing special here? Well if you say so! Wait does this look familiar to anyone?
Code:
/sys/class/leds/lv5219lg
RGB LED interface
WLOD (white led of death) issues, or seeing three red blinking led lights
Code:
/sys/class/power_supply/usb/online
/sys/class/power_supply/ac/online
/system/etc/semc/chargemon
This charger file defines the CPU scaling and governor, which is of massive importance to anyone having issues with poor battery life and general performance of their custom rom
For anyone working with customizations around chargemon, you need to include this file and ensure to include - /system/bin/charger - as an entry in any modifications to chargemon right after
#!/system/
It should ALWAYS be the 2nd line in the chargemon file. No questions asked, this file must be optimized and present, it can not be a touch file with any old permission set assigned!
(*ATTN ALL ROM DEVELOPERS*)
Important lesson when handling Android files. You must set the correct permissions and assign the correct security groups - setuid - as they are held in memory. If a part of code executes and is unable to reach the expected memory - WLOD
Not to be patronizing or arrogant, I suspect the issue arrived with Froyo (now in Beta 4), which made it's way via TripNrAvER to a further ROM developers and the issue exists and is present in many (possibly all 2.2.1 Froyo x10 roms) although most user complaint's arrive in strange or hard to understand messages, which is too often interpreted around the forums as just being n00bish and not knowing how to use SEUS or Flashtool...
This thread is specifically for ROM developers and is a deep technical issue. Please do not move this thread to apps or general
/data/local/tmp/charger.tar.gz
Click to expand...
Click to collapse
Thank you DoomLoRD, Androxyde, Bin4y, Zdzihu & Jerpelea for their excellent work and patience, who without their presence and effort on XDA the X10 would never be half of what it is today
EDIT: - v1 was not copying to location correctly - v2 uploaded
updates
Latest! - zdzihu has released a new version which is for Beta 4 variants specifically - http://www.mediafire.com/?5rr5ygl1udldla1
This fix should not be applied on Trip's MIUI ROM until further notice!
Thanks to My_Immortal & kmilof for pointing out that there is an issue with TripNRavER MIUI
Unsure why there was a problem with TripNMui, I will investigate. The permission groups are different and am investigating.
1: Replaces a critical system file with correct system permissions.
How to tell if this exists or if you need this update? It's very easy Using a file explorer (i.e; Root Explorer) also others work, browse to the directory; /system/bin/ <- look for the file charger as @cobrato pointed out, it should be identical.
14356 = Binary file size
-rwsr-xr-x = Unix file permission
The permissions are the important part and during the night it was posed, this could be handled with the following command - busybox chmod u+s - while this is true, it is context sensitive. For example if this command is issued in the context of root, the setuid is included and created for root. This file belongs to a special group which can't be modified. If anything it should reset permissions on a file which exists and enable correct permissions on the charger and enable it to work again.
It appears to have been too late for one x10 last night. I received another P.M of death by USB and the problem is real and has claimed many devices, although I am having a hard time pinpointing what caused it, I'm unable to say that much other than this is potentially a cure if even partial as pointed out by picking up on a modification from DooMLoRD, to optimize offline charging.
To prevent your x10 from battery death after modification, never allow the battery to run below 5% - replacing battery might be the only hope if this happens!
Thanks for your effort in explaining what this zip does.
Not entirely sure what it all means but I understand it to mean everyone on any 2.2 CUSTOM ROM should flash this. I will do so and report back any issues.
PS. I have never had a WLOD FC yet.
BB58 wolfbreak latest update and tweaks test zip. Stock kernal
EDIT: Flashed onto WB ROM...no issues so far.
Sent from my X10i using XDA App
@mrHassell
my question is, do we need to flash this everytime we flash a new rom or is it something that just needs to be done once?
I have said before, but thanks again for your tirelress work, you too give a great deal to our x10 forum, thanks for your hardwork my friend.
smartgardens said:
@mrHassell
my question is, do we need to flash this everytime we flash a new rom or is it something that just needs to be done once?
Click to expand...
Click to collapse
Well if the new Custom Roms that will be developed from now onwards include it you won't need to flash it every time but lets said that you'll be flashing FreeX10Beta4 or WB CM 6 ROMS you'll have to do it every time since those ROMS doesn't include it for now and every time you flash a new ROM it overwrites the existing /system/bin folder...
Jim
not so sure what is the uses.
i flashed this in TripNMiUI FINAL 1.0.63.. after bootanimation screen's turn black, cant do anything =/.
kmilof said:
i flashed this in TripNMiUI FINAL 1.0.63.. after bootanimation screen's turn black, cant do anything =/.
Click to expand...
Click to collapse
I flashed it over Trip's 1.0.2 and everything went fine. Phone booted normally.
I haven't 100% understood what it does, but it certainly did not do me any damage.
Did you make a nandroid before flashing?
My_Immortal said:
I flashed it over Trip's 1.0.2 and everything went fine. Phone booted normally.
I haven't 100% understood what it does, but it certainly did not do me any damage.
Did you make a nandroid before flashing?
Click to expand...
Click to collapse
yup, i did make a nandroid before flashing, i could restore it and the everything went back to normal.
maybe something changed between trip 1.0.2 and 1.0.63
Thank you for this one
I flashed this over reindeiro's scramble ROM without any issues. Thanks for this.
Sent from my X10i using XDA App
Not entiley sure what this is for but still flashed into beta 4 all ok. Thanks
sent from my Z orignal and modded 2.2 powered c64
chiefy009 said:
Not entiley sure what this is for but still flashed into beta 4 all ok. Thanks
sent from my Z orignal and modded 2.2 powered c64
Click to expand...
Click to collapse
Me, too..
Can somebody explain?
Anyways, installed succesfully on Trip's MIUI 0.0.98. (The IRIS one.)
A few people saying their phones have been bricked (thinking they were, you can't brick an x10) and getting either a wlod, or three blinking red led flashes, because their battery level got so low and they were unable to offline charge it.
This fixes it and makes sure that cannot happen.
That is what it is for...
fiscidtox said:
A few people saying their phones have been bricked (thinking they were, you can't brick an x10) and getting either a wlod, or three blinking red led flashes, because their battery level got so low and they were unable to offline charge it.
This fixes it and makes sure that cannot happen.
That is what it is for...
Click to expand...
Click to collapse
I was thinking to be this, I mean not to let the phone to go in soo low battery level.
thats weird, i always drain my battery to completely dead (3 red flashes) when im trying to recalibrate the battery and never ran into this issue. I have however had issues with low battery causing multiple WLOD reboots over and over.
Is this recommended to use for 2.3.3 as well? I will try n flash it now on J's CM7 017 STOCK.
fiscidtox said:
A few people saying their phones have been bricked (thinking they were, you can't brick an x10) and getting either a wlod, or three blinking red led flashes, because their battery level got so low and they were unable to offline charge it.
This fixes it and makes sure that cannot happen.
That is what it is for...
Click to expand...
Click to collapse
I see thanks for explaining.
sent from my Z orignal and modded 2.2 powered c64
flashed fine on Js CM7 017
dunno what's happening, i flashed again in trip 1.0.63, and again black screen after the boot screen. any idea? :E
is it also installed if i include it in a own package who only removes the existing charger in system/bin and then copys the new one or do i have to install the zip you uploaded that it would be installed right?
Related
What this kernel does is provide slightly less voltage to the processor. This should not be dangerous for anyone to try, however it may be unstable or just result in general weirdness on a few phones. If it does, all you have to do is revert back to the kernel you had before.
The upsides to less voltage are less heat as well as less power consumption. That means battery life
Remember, this one is running at stock speeds.
Get it on Koush's RomManager (download RomManager from the market) I'll post changelogs in this thread from now on, but keep the kernel on RomManager.
Changelog 8/29:
Lots of stuff.. I dunno.. Look at the CM6 kernel changelog (I've been working on that).
Biggest thing IMO is the usleep stuff which lowers CPU usage and therefore increases battery life.
Note: only tested on CM6. Let me know if you try it on any other roms.
Link: http://kanged.net/up/files/5/kernels/signed-August26-UV950.zip
Changelog 6/20:
Ermm.. I've been releasing my kernels on twitter.. but I'm finally happy with this one.
-Latest Cyan commits
-Minor voltage tweaking
-erm... yeah I dunno.
Get it here http://kanged.net/kmobs/signed-619UV-34.zip or from RomManager.
Changelog 5/14:
-Reinstated those commits reverted earlier.
-Updated to .33.4
-Only doing a 925mV kernel due to the results from the blind study
Changelog 5/1:
-Reverted the following commits thanks to intersectRaven. I think they were the reason for the excessive battery drain.
27dd25f80402a13f9d5c381eda07b560e5545fcc
1490683fb851b992722cbd175d3df087df833656
f2513498e961966d3209aacfffc43de4f41f2ece
-Updated to latest CM source (minus those commits)
Changelog 4/21:
Fixed the board-mahimahi.c in the 850mV kernel.
OLD updates and changelog:
http://iq0.org/story/yet-another-nexus-one-kernel-now-battery-saving
Note: Now offering a universal update.zip method for flashing the kernel (big thanks to Koush for this one)
Thank you www.tdrevolution.com for hosting my work.
Does it still have the highmem?
GEtting an access denied message, Seems the post doesnt exist
Great job. Will get you a logcat if I get any random weirdness.
Maybe now my battery can last longer then my G1 battery did when I am at work.
Anyone care to make an update.zip for those of us without computers nearby to check this out?
Tested and functional with Enomther 1.61. Thanks a lot
What is the CPU voltage and is the some app that can show it?
Running this new kernel at 576/245 mHz, wifi off, 3G connection, brightness set to automatic. will report back with battery life as soon as it runs out. lol
Off of charger: 11:34AM , Wednesday, February 17, 2010
Battery completely drained: TBA
DocRambone said:
Tested and functional with Enomther 1.61. Thanks a lot
What is the CPU voltage and is the some app that can show it?
Click to expand...
Click to collapse
Hey do report if there is any improvements... meanwhile can someone make it into to an update.zip for us?
mgear356 said:
Hey do report if there is any improvements... meanwhile can someone make it into to an update.zip for us?
Click to expand...
Click to collapse
I will, phone seem ok so far, BenchmarkPi at 2670
No slowdowns or reboots during benchmarks or gameplay. Phone feel cooler tho
I'll give this a shot.
Mi|enko said:
Does it still have the highmem?
Click to expand...
Click to collapse
just flashed it. yes it does. my phone hasnt exploded yet either...
Mi|enko said:
Does it still have the highmem?
Click to expand...
Click to collapse
Yes
To those asking for an update.zip: I don't to package this into something that will be easily flashable by all, including those that may not understand the risks (I don't think there are any with this kernel, but can't be sure). I want there to be some rudimentary knowledge of android before someone goes and flashes this and potentially messes up their phone.
Does that make sense? I feel that there should be a barrier to entry on kernels that OC and the like.
What voltages is it for different MHz?
great job, really need something like this... im trying it out! thanks
DocRambone said:
What voltages is it for different MHz?
Click to expand...
Click to collapse
Its not across the board, and I'm not home right now to tell you, but 245 is at 1.0 vs 1.05 and 998 is at 1.250 instead of 1.275
persiansown said:
Yes
To those asking for an update.zip: I don't to package this into something that will be easily flashable by all, including those that may not understand the risks (I don't think there are any with this kernel, but can't be sure). I want there to be some rudimentary knowledge of android before someone goes and flashes this and potentially messes up their phone.
Does that make sense? I feel that there should be a barrier to entry on kernels that OC and the like.
Click to expand...
Click to collapse
I do understand what your saying, I don't think its that much of a barrier though. There are many instructions throughout these boards that will let anyone who is even remotely interested flash a new kernel and push a .ko to their phone... The only reason why I want an update.zip is so that I can flash this on my phone to test it while I'm at work, it would also be nice to be able to switch quickly between kernels and whatnot. I don't have a computer that I can connect to via USB to run fastboot/adb so the only way I can get these on my phone is via a zip.
I don't think that a developer/hacker can be held responsible for others not knowing what issues can be caused by a voltage/clock tweak - especially with disclaimers up everywhere.
FettsVett said:
I do understand what your saying, I don't think its that much of a barrier though. There are many instructions throughout these boards that will let anyone who is even remotely interested flash a new kernel and push a .ko to their phone... The only reason why I want an update.zip is so that I can flash this on my phone to test it while I'm at work, it would also be nice to be able to switch quickly between kernels and whatnot. I don't have a computer that I can connect to via USB to run fastboot/adb so the only way I can get these on my phone is via a zip.
I don't think that a developer/hacker can be held responsible for others not knowing what issues can be caused by a voltage/clock tweak - especially with disclaimers up everywhere.
Click to expand...
Click to collapse
Oh I understand where you're coming from, and I would make you a private one, but I'm not home at the moment. However, for the general user, if they can't use fastboot, I don't want them anywhere near this. I hope someone makes you an update.zip!
I await the PM's!
Dear lord what am I going to do with this should I get my 2800mah battery? my phone will never die! lol
-Charlie
FettsVett said:
I await the PM's!
Click to expand...
Click to collapse
you can make one yourself.
grab boot.img from cyanogen's rom.
grab split_bootimg.pl from http://android-dls.com/files/linux/split_bootimg.zip
grab persiansown's zImage.
(in linux)
put all three in a folder. let's call it kernel.
while in the kernel folder:
./split_bootimg.pl boot.img
mkbootimg --cmdline 'no_console_suspend=1 console=null' --kernel zImage-persiansown --ramdisk boot.img-ramdisk.gz -o boot-persiansown.img
(in windows)
download this: http://www.sendspace.com/file/kj2wi7
use winrar to open up that up, remove the boot.img in there and replace it with boot-persiansown.img (make sure it is named boot.img)
open up the update-script in META-INF folder (some levels down in there), and remove the format BOOT line (you'll be left with write_raw_image ... line), and save it.
grab this: http://www.relentlessaddictions.com/Androidstuff/signing.zip
unpack to your tools folder in your android-sdk folder distribution, and run autosign.bat. follow the prompts. once setup, you can right click on the .zip file with the boot.img in it to sign it, or you can execute from a cmd prompt: java testsign BOOT-IMG.zip
flash via custom recovery (which can flash .zip's signed with test keys).
you should be all set.
edit: mkbootimg can be found in prebuilt within AOSP distribution, or you can grab this precompiled one: http://forum.xda-developers.com/attachment.php?attachmentid=229872&d=1253485580
NOTE: This will probably no longer be maintained. It was the result of me playing around with the kernel from scratch instead of trying to understand what changes others have made and why they had made them! Now I'm a little more confident I'll probably be using DooMLoRD's kernel as a base for any changes I make to the Ray: [Kernel] [Ray] DooMLoRD's Kernel for Ray
hartej said:
Been playing around with Kernel development and created an overclocked kernel for the 4.0.2.A.0 stock Rom.
There's nothing too speciall in it at the moment, but lets you overclock the Ray to 1.9Ghz using the source released by SE and the modified CPU steps that IF2 posted here: http://forum.xda-developers.com/showthread.php?t=1165355
There's no custom bootloader/Clockwork mod and no additional governers (at the moment) although I may add these in future as I learn more.
It seems to work well enough, and everything seems to be working as standard. I experience random lock-ups at 1.9 and occasionally 1.8Ghz, especially when it goes into/out of sleep when the screen turns off. Lower frequencies seem stable though.
This is released as-is, I'm using it myself but I can't be held responsible for any instabilities or failures you might experience. Just thought it might be of use to some people.
The new .img file can be downloaded from here: http://dl.dropbox.com/u/17615284/4.0.2.A.0-V0.13-2011-12-18.img
Alternatively, I've posted a version of the DooMLoRD kernel for the Ray which has a ton more features. This can be found here: http://forum.xda-developers.com/showthread.php?t=1400121
To install just use fastboot in the usual way. To return to stock, extract kernel.sin from the official update image using WinZip/WinRar etc and flash using fastboot again.
Click to expand...
Click to collapse
I'll post any updates here from now on.
Changelog:
19/12/2011 - V0.13 - As people have quite rightly pointed out, V0.12 boots at 1.8GHz as default, which causes multiple reboots. I hadn't noticed this as I had SetCPU reduce it to 1GHz as soon as the system started. The only change to this version is to have it boot at 1GHz as default, it's up to the user to increase it themselves.
28/10/2011 - V0.12 - Added Clockwork Recovery v5.0.2.6 (Spam Vol[-] when phone starts up, use volume keys to navigate, home to select, back for back)
28/10/2011 - V0.11 - Started playing with the Ramdisk - as a first start I've made it rootable. Things like "Adb remount" work now.
26/10/2011 - V0.1 - intial release
Current version:
~~~~~~~~~
V0.13 can be downloaded here: http://dl.dropbox.com/u/17615284/4.0.2.A.0-V0.13-2011-12-18.img
Older versions:
~~~~~~~~~
V0.12 can be downloaded here: http://dl.dropbox.com/u/17615284/4.0.2.A.0-OverclockV0.12.img
V0.11 can be downloaded here: http://dl.dropbox.com/u/17615284/4.0.2.A.0-OverclockV0.11.img
get new kernel~nice
tested it works really cool
thanks!!!!!
Like it...
thanks
Glad to see the "Recovery option" is available.
I tested v0.11+OC 1.3Ghz -> no problem.
However, v0.12+OC 1.2 or 1.3 -> keep on rebooting.
v0.12+no OC (use default 1Ghz) -> no problem.
im on 012+oc 1.5mhz, still working well....
great works!
great work, thx for your efforts
the included cwm is it dooms latest?
http://forum.xda-developers.com/showthread.php?t=1172885
"[v12 onwards] modified recovery to support /sd-ext backup/restore (remember /sd-ext has to be the 2nd partition on ur sdcard [mmcblk0p2] for this to work)"
if it is not I think that would be usefull with ext support, now you can use a2sd for xperia, bu it is not possible to make nand backup bcs cwm dit not recognize ext partition.
can you add donation possibility, would like to support your work
Thank you a thousand times! :d
2 questions though:
- I have to reroot my phone after this?
- Do I have to rename the download to boot.img?
Thanks 4 sharing!!!
-No
-No
;-)
funiewski said:
great work, thx for your efforts
the included cwm is it dooms latest?
http://forum.xda-developers.com/showthread.php?t=1172885
"[v12 onwards] modified recovery to support /sd-ext backup/restore (remember /sd-ext has to be the 2nd partition on ur sdcard [mmcblk0p2] for this to work)"
if it is not I think that would be usefull with ext support, now you can use a2sd for xperia, bu it is not possible to make nand backup bcs cwm dit not recognize ext partition.
can you add donation possibility, would like to support your work
Click to expand...
Click to collapse
It's not the latest I'm afraid so I doubt the ext backup would work. I'll see what I can do for the next release when I get a chance.
At some point I was also going to see if it's possible to change the MTD partition structure to give more space to /data. At the moment adb reports:
Code:
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock0 400.0M 241.8M 158.2M 60% /system
/dev/block/mtdblock3 420.0M 270.3M 149.7M 64% /data
This means that there's over 150MB of 'free' space in system that could be given over to the data partition instead of being effectively lost. May or may not be possible - don't know enough about the system yet.
As for donations - this is as much a learning experience for me than anything else, and at the moment I'm mostly applying things that others have done instead of making any breakthroughs myself so I wouldn't feel happy taking donations, but the thought is appreciated.
Bazonga said:
Thank you a thousand times! :d
2 questions though:
- I have to reroot my phone after this?
- Do I have to rename the download to boot.img?
Click to expand...
Click to collapse
You'll have to put it into fastboot mode by powering on and holding Vol[+], then flash using "Fastboot flash boot <filename>" - you can rename it or not, provided the <filename> part matches. You shouldnt have to reroot.
kkline38 said:
Glad to see the "Recovery option" is available.
I tested v0.11+OC 1.3Ghz -> no problem.
However, v0.12+OC 1.2 or 1.3 -> keep on rebooting.
v0.12+no OC (use default 1Ghz) -> no problem.
Click to expand...
Click to collapse
That's strange, i've got it overclocked to 1.5Ghz and it seems to be really stable. As far as I'm aware the only change I made between the two was adding clockwork - there shouldn't be any other difference... I'll look into it.
Double reboot only 10 min after flashing and without changing frequencies..
Bazonga said:
Double reboot only 10 min after flashing and without changing frequencies..
Click to expand...
Click to collapse
Without having your device in front of me I don't know how much I can do to help, but I'll look into it once I have the time. Unfortunately I have other things on the go at the moment so it probably won't be till next week.
hartej said:
Without having your device in front of me I don't know how much I can do to help, but I'll look into it once I have the time. Unfortunately I have other things on the go at the moment so it probably won't be till next week.
Click to expand...
Click to collapse
Thanks, I flashed the stock kernel back for now, Ray kept rebooting on me for no reason..
hartej said:
That's strange, i've got it overclocked to 1.5Ghz and it seems to be really stable. As far as I'm aware the only change I made between the two was adding clockwork - there shouldn't be any other difference... I'll look into it.
Click to expand...
Click to collapse
Do you use SetCPU ? (I use SetCPU 2.2.4)
What's the parameters did you use to OC 1.5Ghz ?
"ondemand" ? "powersave" ? "performance" ? or ?
Currently I changed back to V0.11. (it's stable for me)
kkline38 said:
Do you use SetCPU ? (I use SetCPU 2.2.4)
What's the parameters did you use to OC 1.5Ghz ?
"ondemand" ? "powersave" ? "performance" ? or ?
Currently I changed back to V0.11. (it's stable for me)
Click to expand...
Click to collapse
Yup, think I'm on 2.14 though - I doubt this would make a difference but its possible I guess.
I leave everything as-is (So ondemand governor) but reduce the min to 122MHz and increase max to 1.5GHz. Still confused as to why the previous version is more stable for some, but I'll have a look at the differences.
hi! thank you for this kernel.
now question. can you include USB_otg into your kernel? it's realised in DooMLorD kernel for arc (link). is it possible to do this feature for our device?
P.S. sorry for my english, i'm from Russia
vdsirotkin said:
hi! thank you for this kernel.
now question. can you include USB_otg into your kernel? it's realised in DooMLorD kernel for arc (link). is it possible to do this feature for our device?
P.S. sorry for my english, i'm from Russia
Click to expand...
Click to collapse
Don't worry about your English - my Russian is much worse!
I'm developing this for my own uses (selfish I know) while I work out how it's all put together. I'll add OTG to my list although I can't promise anything.
thanks
take it
Tried 0.12 and was really happy there´s clockwork for my ray But I have to go back to stock kernel. v0.12 randomly freezes and then reboots (btw. ray gets hot untill reboot).
I didn´t overclock and use rooted 4.0.2.A.0.42.
Some weeks ago, I decided to overclock my Ace: CyanogenMod-7.1.0-RC1-Cooper-KANG plus ClockWorkMod4. Got the overclocking kernel from ketut.kumajaya and started to play with frequencies while watching CSI Las Vegas.
In general, it's stupid idea to multitask things like this. In my case, I accidentally ticked checkbox "Set at boot", set the frequency to around 870 MHz and my phone rebooted. I have gone into the bootloop, tried almost everything:
-reinstallation of CyanogenMod
-reinstallation of some other ROM i have found on my disk
-cleaning caches, wiping etc
Without sucess of course
I have decided to check, what exactly happened with my phone, so connected it to PC and started logcat. There was a lot of errors related to files on /data partition - it did not mount for some reason. I was able to access shell from Recovery, but it did not helped me too much - /data partition was entirely broken.
I realized that Samsung uses its own filesystem for /data - RFS and I had no tools to work with it - at least did not find them. In such case, I have unpacked one of the older firmwares and found, that it contains files for soome partitions, but not for the /data.
Next steps were fairly simple - go to sammobile.com, download firmwares for my Ace and check, if it contains /data (data.rfs). Eventually found one, flashed it and my phone went back alive.
Don't know if this is best method, but at least it was interesting to investigate
Thnkx for dis info. All d noobs should read dis before flashing d oc kernel.
Sent from GT-S5830 using Grif's Cyanogenmod
domnic79 said:
All d noobs should read dis before flashing d oc kernel.
Click to expand...
Click to collapse
I think, that most of them will read this after the catastrophe...
Regards
SetCPU has a "Safe Mode" flashable zip file
Sent from my GT-S5830 using XDA App
EmoBoiix3 said:
SetCPU has a "Safe Mode" flashable zip file
Click to expand...
Click to collapse
In general, overclocking means that system can work in an undeterministic manner. Especially an overclocked processor can write some garbage to flash - in my case it was /data partition.
Can't belive that any "Safe Mode" could help - if you play with fire, you should be ready for some burns
Regards
Pawel
p.stradowski said:
In general, overclocking means that system can work in an undeterministic manner. Especially an overclocked processor can write some garbage to flash - in my case it was /data partition.
Can't belive that any "Safe Mode" could help - if you play with fire, you should be ready for some burns
Regards
Pawel
Click to expand...
Click to collapse
It reverts the CPU speed back to 787Mhz .
Sent from my GT-S5830 using XDA App
EmoBoiix3 said:
It reverts the CPU speed back to 787Mhz .
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
exactly. it disable/revert the "set on boot" function that cause bootloop
Everyone knows the risks and there are more than enough warning messages floating around highlighting the BLATANT ramifications of over clocking. Call me harsh, but isn't this what we DIDN'T want to see cluttering the forums? Let this be a lesson to anyone else who decides to flash the kernel.
Sent from my GT-S5830 using Tapatalk
well some people need to learn the hard way. some will never learn until the day their devices blown to smithereens on their faces.
jimbo.levy said:
Everyone knows the risks and there are more than enough warning messages floating around highlighting the BLATANT ramifications of over clocking. Call me harsh, but isn't this what we DIDN'T want to see cluttering the forums? Let this be a lesson to anyone else who decides to flash the kernel.
Click to expand...
Click to collapse
completely agrees
an0nym0us_ said:
well some people need to learn the hard way. some will never learn until the day their devices blown to smithereens on their faces.
Click to expand...
Click to collapse
yeah i see LOT OF people just bricking devices and then search for solutions.. but i see that many people search Google and see something and do it on device without confirming that it works or not...
in my opinion rom manager seriously should include warning or some mechanism to warn user that there device is not at all supported.. is there any?? just confirming as i haven't installed that ACE KILLER
madman_amit said:
completely agrees
yeah i see LOT OF people just bricking devices and then search for solutions.. but i see that many people search Google and see something and do it on device without confirming that it works or not...
in my opinion rom manager seriously should include warning or some mechanism to warn user that there device is not at all supported.. is there any?? just confirming as i haven't installed that ACE KILLER
Click to expand...
Click to collapse
Rom manager says ace is supperted in cm7 roms. Bt 99% people bv bricked their fones using this app. So even if it shows samsung galaxy ace in d list, dont use it.
Sent from my GT-S5830 using Grif's CyanogenMod
Dont jus say thanks, use d 'Thanks' button. [XDA-RULE]
EmoBoiix3 said:
It reverts the CPU speed back to 787Mhz .
Click to expand...
Click to collapse
It is good option to have such tool handy, but one can understand, that overclocking can hit the phone in more complex way. This was my case - overclocked system damaged partition /data.
My message is that overclocking is dangerous and one should be prepared for any results including bricking.
Comparing this with usual process of installing new firmware, recovery, bootloaders etc, overclocking is far more dangerous because of uncertainity generated by the unstable processor.
Regards
Hello,
I think I also broke my /data
p.stradowski said:
...
Next steps were fairly simple - go to sammobile.com, download firmwares for my Ace and check, if it contains /data (data.rfs). Eventually found one, flashed it and my phone went back alive...
Click to expand...
Click to collapse
I've tried to download many firmwares, but cannot find any containing that precious data.rfs.
Is there some specific version or link you could give me please ?
Thank you so much !
Hi again,
Answering to myself : S5830XWKPO v2.3.3 makes the trick.
Bye
similar bootloop for CM7.2 perhaps with similar solution?
Hi,
I am having a similar bootloop problem for CM7.2.
I have Odin installed, but I don't think sammobile firmware page currently stocks the appropriate files. Clicking on the links for the files just links to mediafire, invalid or deleted files. for some of those files.
I do however have some backups I made with nandroid which may be incomplete: These are all of the files generated.
cache.rfs.tar data.rfs.tar nandroid.md5 system.rfs.tar
I also just installed Android Developer Tools for Linux.
Can I use any of these things especially data.rfs.tar in Odin to fix my phone.
I just interested in how you loaded the data.rfs.tar into Odin, because I have read it is very sensitive to file order, and Odin is a good canditate mechanism for bricking my phone.
I have CW5 installed. My phone can go into download mode, and I can see corresponding COM ports in Odin.
Sorry I have not posted on the most appropriate topic, but I am interested in the way you solved your problem with logcat, and then flashing data.rfs.tar
BTW: I also found this package somewhere: I think its the whole gingerbread stock rom. Simply adding the zip to the SDCARD and trying to install from SDCARD, after clearing cache etc. wont do anything. Yet on the other hand none of these files are any good for Odin either.
~/Desktop/android_device_samsung_cooper-gingerbread$ ls
AndroidBoard.mk BoardConfig.mk init.gt-s5830.rc liblight recovery sec_key.kl ueventd.gt-s5830.rc
Android.mk camerashutter kernel overlay recovery.fstab sec_touchscreen.kl unzip-files.sh
AndroidProducts.mk device_cooper.mk libaudio prebuilt recovery_kernel setup_fs UsbController.cpp
bdaddr_read egl.cfg libcopybit qwerty.kl recovery.rc setup-makefiles.sh vendor
bluedroid extract-files.sh libgralloc ReadMe sec_jack.kl system.prop vendorsetup.sh
I wonder if anyone knows the best way to get this format of ginger bread to unzip and expand off the sdcard?
Thanks so much for any help, It would be much appreciated (even if the help is just the suggestion that I should repost under a different forum topic).
p.stradowski said:
Some weeks ago, I decided to overclock my Ace: CyanogenMod-7.1.0-RC1-Cooper-KANG plus ClockWorkMod4. Got the overclocking kernel from ketut.kumajaya and started to play with frequencies while watching CSI Las Vegas.
In general, it's stupid idea to multitask things like this. In my case, I accidentally ticked checkbox "Set at boot", set the frequency to around 870 MHz and my phone rebooted. I have gone into the bootloop, tried almost everything:
-reinstallation of CyanogenMod
-reinstallation of some other ROM i have found on my disk
-cleaning caches, wiping etc
Without sucess of course
I have decided to check, what exactly happened with my phone, so connected it to PC and started logcat. There was a lot of errors related to files on /data partition - it did not mount for some reason. I was able to access shell from Recovery, but it did not helped me too much - /data partition was entirely broken.
I realized that Samsung uses its own filesystem for /data - RFS and I had no tools to work with it - at least did not find them. In such case, I have unpacked one of the older firmwares and found, that it contains files for soome partitions, but not for the /data.
Next steps were fairly simple - go to sammobile.com, download firmwares for my Ace and check, if it contains /data (data.rfs). Eventually found one, flashed it and my phone went back alive.
Don't know if this is best method, but at least it was interesting to investigate
Click to expand...
Click to collapse
hello! i had your problem with my ace and i could not find a solution at first but after a while i had worked out a solution. i find this one a bit easier to follow for noobs NOT guaranteed to work. also you will lose ALL DATA
1.flash stock through odin (2.3.5 reccomended)
2.wipe/factory reset
3.flash this: https://docs.google.com/file/d/0B-eHBmC1vSXGc1BRSWlqRW1Nc28/edit - this will root your device
4.afterwards flash this: https://docs.google.com/file/d/0B-eHBmC1vSXGeWNBOXhCVjZTRkk/edit - this will give you cwm
5.turn off then boot into recovery again.
6.wipe data/factory reset, cache, dalvik cache, mount and format system
7. install this ROM: https://docs.google.com/file/d/0B-eHBmC1vSXGVU1TSjdpUlF4MDg/edit
8.boot up your phone. it will take about 5 minutes to boot again, and you will have xperiatized rom. you can now flash whatever rom you like or go back to stock. i hope i have helped you and if i have please hit thanks
Hi,
Thanks for your help and interest.There is no chance that that will work in my situation since I have never succeeded in flashing the stock android from the samsung website. In fact, I have never been able to flash anything with Odin at all. I tried uninstalling and reinstalling Samsung drivers. Uninstalling Kies etc, using specific Samsung data cable. No measure I took was able to satisfy the condition that Odin could flash a ROM onto my Samsung gts-5830, which made me sad for a while.
Also thanks for granting permission to share googledocs files. Unfortunately I was unable to download Root.zip from google docs. Due to following error, but given I can't flash stock Android, the downloading the files will not help anyway. (Browser gives error message
###
# corresponding URL for that Root.zip:
# has resulted in too many redirects. Clearing your cookies for this site or allowing third-party cookies may fix the problem. If not, it is possibly # a server configuration issue and not a problem with your computer.
###
For the Moderator who moved this thread, please contact me.
Click to expand...
Click to collapse
I am currently working on this: It is a work in progress. Many things will be updated as this goes on. I will publish it before it is ready mainly for you to know that I am doing this and to delete it before it is too late if you think it just isn't as good as I imagine it .
It could be useful to note that the dictionary may not be exactly correct, I can make mistakes and you can correct me too, if you are sure of what you say. Also, keep in mind that I define the concepts by what I understand from them and simplifying the language as much as I can for EVERYONE to understand every word.
Click to expand...
Click to collapse
Credits:
ShortFuse.org - SuperOneClick
ClockWorkMod Installer - rect2409, xda user
Contents:
1. Introduction
2. Dictionary -In permanent update as needed-
3. Getting started
/3.1 - Rooting
/3.2 - Getting your Recovery - CWM Recovery
/3.3 - Avoiding Baseband issues --Uncomplete--
1. Introduction:
Hey there, x10 Mini Pro community. First of all, the cheesy part, I would like to say thanks to the developers that have been in the main scenario since I came here, D4, slade, paul, nAa, TheMiltos, and lots of them whose usernames I should start looking for, but it is not like I do not recognize them. First, you may ask why would I make this thread if there is already another one, made by not less than one of the users I mentioned before. Well, I started on this community like on January 2011, when slade's Gingerbread was brand new and the Froyo ROMs were just getting a bit stable and ready for everyday use. I found it pretty difficult to start, since I've noticed that the support for newbies isn't kinda.. "the way" of xda. At least, when I was one of them, I felt pretty alone on this unknown roads, and also felt guilty to send a PM asking for help, not being able to post - and that was just when I finally decided to create an account... I spent hours and hours searching on Google, watching videos on Youtube, trying to understand what did they meant with all this technical language -disregarding the fact that my native language doesn't help at all (Luckily, my English is pretty good)-, reading blogs, and so on. I had to keep this intensive study for several weeks to, finally, get my very first custom recovery installed. And that was just the first step. Besides my own experiences -which are, by the way, the main reason for me to start thinking about a thread like this-, I noticed that all the particular problem solution threads just get lost within a month.
So, what am I looking for with this thread? What are the objectives?
-Full and friendly support for newbies to ask and be answered.
-Freedom to PM.
-Detailed step-by-step instructions, maybe even with screenshots later on.
-Some kind of a "dictionary" with words all over the Android development spectrum.
-Updated information.
-Make all of those lost tutorials and guides spread all over the x10 Mini Pro forums be compressed in one simple and extensive help center.
-End with the experienced ones complaining about newbies questions infinite cycle by creating this "encyclopedia".
-Maybe, just as an early idea, we could create a support team, whose purpose is pretty self-explanatory.
-Hope to add more objectives on the future.
2. Dictionary:
-Android Versions: Check Wikipedia for closer details on each version.
--> Cupcake 1.5: First public version of Android.
--> Donut 1.6: Initially the Stock version for our phones.
--> Eclair 2.1: Updated Stock version for our phones.
--> Froyo 2.2: Follow up to Eclair with some modifications
--> Gingerbread 2.3.x: Most widely used version by the moment.
--> Honeycomb 3.x: Version mostly for tablets
--> Ice Cream Sandwich: 4.0.x: Hybrid version, designed to unify Cellphones and Tablets OS.
--> Jelly Bean 4.1.x: It is still a rumor and it has not be released nor even confirmed yet, but it is still very likely to be true.
-APK: File extension used for Android-based applications. You can use them to install a specific application if you want to install it manually and not from the Market.
-Back-Up: It is a file made via Recovery that saves the ROM along with all the user data (Settings, applications, contacts, text messages...) on your SD to recover it later, just in case that something went wrong. It is sometimes referred as NAND Backup. NOTE: Every Back-Up is pretty heavy, and if you make another does not delete the previous one, so I recommend to delete the old/unneeded ones to save space on your SD.
-Boot: To turn on your phone.
-Bootloader: It is a part of the operating system that boots up your device and sets everything up to load Android, so your phone can boot and start as usual. Unlocking it allows us to flash custom kernel, which usually come with improvements compared to stock one.
-Brick: A Bricked device is a device that won't boot. It can be a full brick, when the phone just does not turns on, or a partial brick, where it turns on but it can not get to fully boot. A partially bricked phone can behave in many different ways while booting, for example, sometimes they get frozen at the Bootloader or sometimes they make a Bootloop. To Unbrick your phone means to get it back to normal from this state.
-CyanogenMod: Most commonly called by it's abreviation, CM. It is the most famous Android-based custom ROM, with both official ports to many devices and unofficial ports to almost every Android phone.
-Flash: To flash. It means to install something on your phone, this something can be a ROM, a Module for that ROM, can be almost anything. Any file we want to flash will be on a ZIP format, and it is made through your phones Recovery.
-Google Apps: Or GApps. Some of the apps developed by Google. They come in packages to flash them via Recovery. These apps include Android Market/Play Store, Google Maps, Youtube, Gmail, etc.
-Launcher: It is the application that is used by Android to show up your apps, homescreens, wallpapers, widgets, etc. Home Replacement Apps are alternative Launchers for you to install on your phone, and they can offer a major UI change (often used for more personalization).
-Overclocking: Commonly abbreviated OC. To overclock something means to make it run faster than the default speed set by the manufacturer. On computers, it can be applied to almost any component, on phones, it almost always is talking about the processor.
-OS: Short for Operative System. It is the "everything" of a computer. Mac and Windows are two really famous OS's you probably have used more than once. Well, Android is an OS too, and there are other OSs alternatives for phones too like Windows Phone, iOS and Symbian. The difference is much more than in the appearance thou, but it doesn't really matters to go further on this. Android haves different versions, and just like Windows haves Windoes 97, Windows XP, Windows Vista or Windows 7; Android has 1.6 Donut, 2.1 Eclair, 2.3 Gingerbread and 4.0 Ice Cream Sandwich (These are just examples, there are more).
-PC Companion, Flashtool, SEUS:
These are three common tools for your computer to update, flash or un-brick (alias revive) your phone.
--> PC Companion: Program by Sony Ericsson to update and save your Rom or parts (settings etc.) or to send media on your device
--> Flashtool: User-made program (credits to Androxyde and Bin4ry) to root, flash and set up many more things on your device.
--> SEUS (or Sony Ericsson Update Service): Program by Sony Ericsson to update or repair your official ROM. This is often the last chance to revive your bricked device, making me think if the "S.E.U.S." acronym is unintended or if it is actually made it to sound like the mythical god Zeus.
-Port: A ported ROM is a ROM, both custom or stock, that is available to some specific phone and someone manages to make it work for another device. Usually it includes changes like matching the desired device's screen and supporting it's own hardware.
-Reboot: Just turning off your device and then turning it back on, waiting patiently for it to completely load everything.
-Recovery: I usually call it a BIOS for my phone. It is not an application like Facebook or SMS, it is a program that can be optionally started while booting by pressing a certain key, in our case, we have to button-mash the "Back" button (Gamers will get that, it means to repeteadly tap the button). Your phone will enter a menu with black background and orange letters. Touch screen is not available here and the Menu button, the left one, serves no purpose at all. To control everything, you use the volume buttons at the side of your phone as Up/Down respectively, the Home button (the middle one) works as Enter and the Back button, the right one, is used to go back, as you might imagine. Recoveries are used to flash any flashable file to your phone. To exit and return your phone to normal, just back until the main menu and select Reboot Phone. It will reboot normally, and CWM will not show up unless you call for it with the back button.
-ROM: Its basically the OS that we install in our phones. It can be Custom or Stock: Stock ROM is the version that came with our phone, created by Google and then modified by your phone's brand company and then by your carrier, to go to your phone on it's original closed package. Also we have Custom ones, that are user-modified versions of Android. Every ROM in xda is a Custom ROM because they are developed by the user who uploaded it. We call it ROM because it resides in the ROM (Read-Only Memory) of our devices.
-Root: The first thing you must do over any Android device to get the full potential of itself, is rooting. Android, in basic terms, is based on Linux. Yes, that OS for computers you've probably heard of (If not, don't worry. You don't need to know about it.). And it is running just in your hand. On Linux, you need to get SuperUser permissions over a set password to make changes on the computer like installing programs and such things. On Android, you do not get his password and by default it is blocked, and rooting your phone means that you get this SuperUser access. Yes, if you are the one who goes exploring the phone 'till the last folder and modifying everything you possibly can, you will surely mess your phone up. But don't worry, if you just Root your phone and let TRUSTED apps to do their stuff, you are safe. What do I mean by trusted? With Root permissions you can do whatever you want on your phone, and so do Applications. You should just install applications whose developer you know you can trust, such as xda or market developed applications. Remember to always check the comments or posts people do reviewing their experience with that application, and beware if anyone tells so. Anyways, people is not that dumb and they have made the phone ASK for your permission before giving any new app the so called Root access.
-Run: To open a certain program or app. Can be used as "Running" for a certain program or app that is actually open, and so on.
-Stock: It refers to something that comes pre-installed on our devices, available when we just get them from the manufacturers.
-UI: The User Interface is the system shown on the screen of a device for you to interact with it.
-Undervolt: Usually abbreviated UV. It is the opposite of Overclocking, and, on phones, it consists of lowering the default voltage of the processor to make it run slower and thus decrease battery consumption.
3. Getting Started:
3.1 - Rooting
Steps:
-You can't imagine how easy and quick rooting can be. The first step, is to enable "USB Debugging" on your phone. I am going to be honest, I don't know what the **** is this, but keep it enabled. Always. Hehe. To do this, go to Settings and then under the Applications tab. Then, scroll down and go to Development. And there it is, you should tap "USB Debugging" once to get it checked and activated.
-Then, you need this software (Don't worry: it is free and very light, and you can just delete it after root). It is called SuperOneClick and this is the lastest version (2.3.3) until now. This is a screenshot of the interface that I grabbed from the original site. Install and open SuperOneClick, and continue to the next step.
-Now, with the USB Debugging enabled on the phone and SuperOneClick running on your computer, grab your USB cable that should have come along with your phone as your charger and connect with it your PC and your phone. On the phone it should show a message asking what to do, you should tap the option to charge the phone (This option is kinda "do nothing", it is the same as charging it from the wall). Now, go to SuperOneClick and click the big "ROOT" button. It should do all the work, so your task is to wait. Wait until it says it is ready and rooted, and then reboot your phone.
-Voile! Your phone is now rooted.
3.2 - Getting your Recovery - CWM Recovery
Steps:
-First, download this little program. It is a small Batch file (Commands for Windows) made by a user on this community called rect2409. On the original thread -Link under credits- you have a Linux version of this program, but I'm afraid have never used it and you will have to figure it out by yourself (Linux experienced-users encouraged to review over here). Extract the ZIP file and go into the folder you just extracted.
-Open install.bat. Batch files can be dangerous on the wrong hands but very useful on the right ones, so if any anti-virus or some kind of a security system tries to block this from working, tell them it is safe. You have my word (It wasn't even uploaded by me, so you can be sure I'm doing no trick here ). It will open a small black window with white text, follow it's instructions and answer it's questions. When it asks you for yes or no (Y/N), you have to write Y for yes or N for no and then press enter.
-When it says "If no errors are listed above then CWM has been installed. Finished.", you can close the window and delete everything you downloaded if you want. Everything you need on your phone is now there, so there's no problem if you want to delete this stuff.
-If you want to access CWM (That's how your new Recovery is called), you have to reboot your phone and at the "Sony Ericsson" text screen, press the "Back" button several times.
3.3 - Avoiding Baseband issues --Uncomplete--
Intro:
Your Baseband is a pretty large code that can be checked on your phone by going to settings and scrolling sown to "About phone". There, just like it says your Android version on a grey section, it should say your Baseband version on another. It should be a large code using both letters and numbers in a format like this ?????-????????-????? (? representing anything and - being itself, whatever it is called -I don't know it's english name-). What really matter are the last three digits, that have to be -015. If you have that, skip this step, because you are already done: The problem is when you have -006 (Like I had) or anything else, if it is possible. The point is that you NEED -015 Baseband version.
Steps:
-Of course, first make sure you have a wrong version of the Baseband, if you have the correct one, skip section.
-When you are sure you need to change your baseband, you have to change your "build.prop". Build.prop is a file hidden by the system, accessible via Root, that holds and manages some information and configuration about the phone. So, the first thing you need to do, is to get...
---To be continued---
Users who have helped:
karthiks.840 - ImInMunichBitch -
Click to expand...
Click to collapse
For Dictionary,
-ROM: Its basically the OS, we call it ROM because it resides in the ROM of our devices.
-Flashing: To install a new ROM. Basically any ROM will be in a zipped format. It can be flashed via any "Recovery".
-Recovery: A piece of program that can be optionally started on booting (In our devices by pressing "Back" button multiple times, when the device is turned on)
Just a quick suggestion: Everything you so far wrote is also applicable to the Robyn (X10Mini, E10i). If you keep it this general, you might consider posting this in the General Section, and maybe a mod could make it a sticky. Since this is not really about actual development, it looks kind of out of place in the development thread.
But keep up the good work
@nico444164: Thanks nico444164! This is probably the BEST thing I have ever seen on XDA - and I've been here since Mikevhl 's FroYo rom early 2011 (he was one of the main devs for x10 mini Pro) , followed by owain94 , slade87 , and paul-xxx who all slowly took over (over their predecessor's) one after another, slowly. I've never seen such a noob-friendly guide here at xda and I agree with your sentiment about it just not "being the way" it is here at xda. Frankly, it should be though and this thread by you is a hopefully a good indicator of/catalyst for xda slowly changing for the better. Cheers nico444164!
Suggestions for dictionary:
CyanogenMod:
Most famous Android-based custom rom of all times with many official and unofficial ports for many Android devices.
Brick:
Device doesn't boot anymore (fullbrick) or partially (halfbrick --> often bootloop to SE logo). Caused by wrong or incompatible changes in system related parts of Android (or many others as we know by now).
Stock:
--> Stock Rom: the operating system of our devices, how we get it from the manufacturer
--> Stock Kernel: same as Rom
Bootloader:
That part of the operating system, which boots up your device and sets everything on boot, so your Android can work as usual.
Unlock it allows us to flash custom kernel with improvements compared to stock one.
PC Companion, Flashtool, SEUS:
All three are tools for your computer to update, flash or revive your phone.
--> PC Companion: Programm by Sony Ericsson to update and save your Rom or parts (settings etc.) or to send media on your device
--> Flashtool: custom programm (credits to Androxyde and Bin4ry) to root, flash and set up many more things on your device
--> SEUS (or Sony Ericsson Update Service): Programm by SE to update your official rom (often the last chance to revive your bricked device)
Back Up:
Same as on a computer; saves the rom and its settings on your SD to recover it, when something went wrong (all usually via Recovery).
Android Versions:
--> Eclair 2.1: Stock version for our phones
--> Froyo 2.2: Follow up to Eclair with some modifications
--> Gingerbread 2.3: Mostly used version for our custom roms
--> Honeycomb 3.x: Version mostly for tablets
--> Ice Cream Sandwich: 4.x: Hybrid version for phones and tablets
APK:
File extension used for android based applications, if you want to install them manually and not from the market.
Launcher, Home Screen Replacement:
The application that is used by android to show up your apps, homescreens etc. Replacement apps take over those things (often used for more personalization).
A2SD, APP2SD, Link2SD:
Apps that allow you to free up your system memory by moving (non system) apps to your SD. Many custom roms implemented this in native settings.
GAPPS:
Commonly used google apps. Often in packages to flash them via recovery after installing a custom rom.
(Market/Playstore, Maps, Youtube etc.)
OC, UV:
-->Overclock (OC): used to get higher cpu values (decrease battery life but may increase performance).
-->Undervolt (UV): used to get better battery life by decreasing the voltage used by the cpu.
Just a few suggestions for this thread here.
I like the idea, would be a good sticky to new users, because this forum is
so high under development that many users forget that new ones may never heard of basic android knowledge.
Corrections are always welcome, hope my english is not that bad
Keep it up.
Marius
karthiks.840 said:
For Dictionary,
-ROM: Its basically the OS, we call it ROM because it resides in the ROM of our devices.
-Flashing: To install a new ROM. Basically any ROM will be in a zipped format. It can be flashed via any "Recovery".
-Recovery: A piece of program that can be optionally started on booting (In our devices by pressing "Back" button multiple times, when the device is turned on)
Click to expand...
Click to collapse
Added! Just changed some words I just thought should make a section for the users that help. Will do that in a few minutes.
SmG67 said:
Just a quick suggestion: Everything you so far wrote is also applicable to the Robyn (X10Mini, E10i). If you keep it this general, you might consider posting this in the General Section, and maybe a mod could make it a sticky. Since this is not really about actual development, it looks kind of out of place in the development thread.
But keep up the good work
Click to expand...
Click to collapse
Actually, that rooting process is kinda global. I thought about making this post a bit more general, but I wanted to start by little and taking my time, so maybe in the future I will ask someone to change it to General and I will add some info about each phone in details, if this gets to grow enough.
Also, I thought maybe this wasn't the place since it is not development, but:
-As a noob, I just checked this thread since I thought the others were exclusive for the Robyn.
-This is still particular to Mimmi.
-I have seen several tutorials and guides related to this on the Mini Pro development section, so I thought that if I am not the only one and it doesn't really hurts to have it here, it should be no problem. Besides, if this didn't work and get to be a real fail, it will just be forgotten with every other old posts out there
nightwing369 said:
@nico444164: Thanks nico444164! This is probably the BEST thing I have ever seen on XDA - and I've been here since Mikevhl 's FroYo rom early 2011 (he was one of the main devs for x10 mini Pro) , followed by owain94 , slade87 , and paul-xxx who all slowly took over (over their predecessor's) one after another, slowly. I've never seen such a noob-friendly guide here at xda and I agree with your sentiment about it just not "being the way" it is here at xda. Frankly, it should be though and this thread by you is a hopefully a good indicator of/catalyst for xda slowly changing for the better. Cheers nico444164!
Click to expand...
Click to collapse
Thanks for your message and support! And yeah, I hope noobs can find their basic ways here on xda, at a single and simple thread, as you might have wanted. I did, at least It would be only better if we could include all this novice people into this real complex world of development, even just as users.
ImInMunichBitch said:
Suggestions for dictionary:
CyanogenMod:
Most famous Android-based custom rom of all times with many official and unofficial ports for many Android devices.
Brick:
Device doesn't boot anymore (fullbrick) or partially (halfbrick --> often bootloop to SE logo). Caused by wrong or incompatible changes in system related parts of Android (or many others as we know by now).
Stock:
--> Stock Rom: the operating system of our devices, how we get it from the manufacturer
--> Stock Kernel: same as Rom
Bootloader:
That part of the operating system, which boots up your device and sets everything on boot, so your Android can work as usual.
Unlock it allows us to flash custom kernel with improvements compared to stock one.
PC Companion, Flashtool, SEUS:
All three are tools for your computer to update, flash or revive your phone.
--> PC Companion: Programm by Sony Ericsson to update and save your Rom or parts (settings etc.) or to send media on your device
--> Flashtool: custom programm (credits to Androxyde and Bin4ry) to root, flash and set up many more things on your device
--> SEUS (or Sony Ericsson Update Service): Programm by SE to update your official rom (often the last chance to revive your bricked device)
Back Up:
Same as on a computer; saves the rom and its settings on your SD to recover it, when something went wrong (all usually via Recovery).
Android Versions:
--> Eclair 2.1: Stock version for our phones
--> Froyo 2.2: Follow up to Eclair with some modifications
--> Gingerbread 2.3: Mostly used version for our custom roms
--> Honeycomb 3.x: Version mostly for tablets
--> Ice Cream Sandwich: 4.x: Hybrid version for phones and tablets
APK:
File extension used for android based applications, if you want to install them manually and not from the market.
Launcher, Home Screen Replacement:
The application that is used by android to show up your apps, homescreens etc. Replacement apps take over those things (often used for more personalization).
A2SD, APP2SD, Link2SD:
Apps that allow you to free up your system memory by moving (non system) apps to your SD. Many custom roms implemented this in native settings.
GAPPS:
Commonly used google apps. Often in packages to flash them via recovery after installing a custom rom.
(Market/Playstore, Maps, Youtube etc.)
OC, UV:
-->Overclock (OC): used to get higher cpu values (decrease battery life but may increase performance).
-->Undervolt (UV): used to get better battery life by decreasing the voltage used by the cpu.
Just a few suggestions for this thread here.
I like the idea, would be a good sticky to new users, because this forum is
so high under development that many users forget that new ones may never heard of basic android knowledge.
Corrections are always welcome, hope my english is not that bad
Keep it up.
Marius
Click to expand...
Click to collapse
Adding them right now And about the last thing you said, yes, it is so hard to join this community as you may all know, at least for users with no knowledge at all over any complex computer language. I consider myself an advanced-user, and even as that I had troubles at getting started. I can't imagine how hard it would be for a non-geek to flash something on their phones! EDIT: Added!
A very good guide for newbies! Will help a lot of people here! Ah, the old days, I remember, the first time I tried installing xREC I messed up and it wouldn't boot, scared the **** outta me xD had to do some reasearch before I could get back to normal. So this would be of great help!! Keep up the effort!
P.S: debugging mode is actually development mode. It allows transfer of data between the PC and the mobile. That's how you are able to run adb commands ( things like rooting, pushing APKs etc.) through the PC onto the phone!
Sent from my U20i using XDA
Wow... The guide is so complete... Even I don't know what I can add there xD
Hmm... How about adding some simple default tricks ?
I found that several user are asking how to backup their data... How about telling them how to upload their phonebook data to gmail and backup their apps through titanium backup ?
I think we can have some "unlocking bootloader" infos in here, as latter ROMs need to have custom kernel installed...
You can refer about the steps to unlocking bootloader in here :
http://forum.xda-developers.com/showthread.php?t=1462278
Hope that helped everyone
speedsys said:
A very good guide for newbies! Will help a lot of people here! Ah, the old days, I remember, the first time I tried installing xREC I messed up and it wouldn't boot, scared the **** outta me xD had to do some reasearch before I could get back to normal. So this would be of great help!! Keep up the effort!
P.S: debugging mode is actually development mode. It allows transfer of data between the PC and the mobile. That's how you are able to run adb commands ( things like rooting, pushing APKs etc.) through the PC onto the phone!
Sent from my U20i using XDA
Click to expand...
Click to collapse
Yees! That old days haha! I did exactly the same, me and my friend got our pretty new phones bricked
, so we were kinda.. O.O! Oh, divine SEUS. And about the Debugging stuff, I will add it tomorrow - Its kinda 2am here and tomorrow is another fun Wednesday to keep the awesome routine, hurray.
StardustGeass said:
Wow... The guide is so complete... Even I don't know what I can add there xD
Hmm... How about adding some simple default tricks ?
I found that several user are asking how to backup their data... How about telling them how to upload their phonebook data to gmail and backup their apps through titanium backup ?
I think we can have some "unlocking bootloader" infos in here, as latter ROMs need to have custom kernel installed...
You can refer about the steps to unlocking bootloader in here :
http://forum.xda-developers.com/showthread.php?t=1462278
Hope that helped everyone
Click to expand...
Click to collapse
It is not a bad idea to add the tricks, but this is quite a big job and I would like to finish keep my objectives clear and then start thinking of adding something else haha And bout the bootloader, yes, it will be added, my plan is to cover every single change available to your phone from complete Stock, Rooting and Installing Recoveries already written. Next I will introduce Custom ROMs, flashing aditional features like Hotfixes or Modules for specific ROMs, unlocking Bootloader, Custom Kernels, and so on. And maybe reviews about the best ROMs for the user to choose from what he best likes. Something like that is what I have in mind by now.
Sent from my U20i using XDA
Install CWM : error: protocol fault (no status)
rooted xperia X10 mini.
USB debug on
phone connected to pc in charge mode.
When I run install.bat for CWM (3.2 in manual), I get an error during first exploit. Here's the complete trace from install.bat:
Code:
ClockWorkMod Recovery Installer for X10 Mini Pro by rect2409.
Requirements and credits are listed in the README.txt file.
Please make sure requirements are met before continuing.
Please make sure that your phone is connected to your PC and USB debugging is en
abled.
Press any key to continue...
Is your device ROOTed? (Y/N):y
Starting ADB Server.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Pushing exploit to gain ROOT access.
426 KB/s (585731 bytes in 1.341s)
error: protocol fault (no status)
Mount system as R/W.
Do you already have a recovery installed? (Y/N):n
Pushing recovery tar file.
1898 KB/s (5027840 bytes in 2.586s)
Pushing chargemon.
130 KB/s (1341 bytes in 0.010s)
Pushing busybox.
2175 KB/s (735308 bytes in 0.330s)
Setting permissions for recovery tar file.
Setting permissions for chargemon.
Setting permissions for busybox.
Mount system as read only.
Reboot phone.
Stopping ADB Server.
If no errors are listed above then CWM has been installed.
Finished.
After the error is displayed, I got sounds on my pc and phone just like when I disconnect usb then reconnect it. Then the program continue (ask whether a recovery is already installed).
I don't think CWM has been installed: actually, when i press back many times on my phone while starting, nothing happens : normal boot from SE.
Can anybody help ?
Looks like you haven't got the adb drivers so its not actually pushing anything. Can't remember how to install the, now but I think its a package included in flash tool that you use.
X10man
Sent from my Nexus 7 using xda premium
x10man said:
Looks like you haven't got the adb drivers so its not actually pushing anything. Can't remember how to install the, now but I think its a package included in flash tool that you use.
Click to expand...
Click to collapse
I have installed drivers found in flashtool drivers 1.0.2, but still get that same error :
Code:
Pushing exploit to gain ROOT access.
1111 KB/s (585731 bytes in 0.514s)
error: protocol fault (no status)
Please help.
Please read this carefully :
- BASE ROM by Kibuuka AOSP ICS 4.0.4
- PORT ROM from Mazda Team Dirt PARANOIDANDROID v0.2.1 for Supersonic aka HTC Evo 4G and Xylograph ParanoidAndroid for HD2
All the Credit and Donate go to :
1. Mazda [Team Dirt] (http://forum.xda-developers.com/showthread.php?t=1714415)
2. Molesarecoming aka PARANOIDANDROID (http://forum.xda-developers.com/showthread.php?t=1717079)
3. Xylograph
3. Kibuuka (you know where to find him)
4. Nop (you know where to find him)
5. TheManii (you know where to find him)
Please do me a favour, hit the THANKS button at least for above name list.
As usually, I take no credit at all for this rom because this is not my work, I'm not build this from the source, all I do is take the 2 rom, combine it, then try to make it boot on my device.
The rom from Mazda was made for running on HTC Supersonic, if running on DS5 sure it will have much problem and bugs.
All I can do just fix as much as I can, I'm not have experience in build rom, so do not expect too much on this rom.
I just want to share, not intend anything by making this, just have fun and feel excited when others ICS rom can running on my old device.
So lets have fun.
Not work
camera
Temporary work
wifi tether (use barnacle wifi tether from playstore)
headphone (use toggle headset2 from playstore, thanks to machbe 1984)
How to
Nandroid back up before flash.
Wipe cache and dalvik cache, factory reset from streakmod recovery
Flash rom
Factory reset from dell recovery
Be patience, phone need longer time to boot up, if it stuck on boot animation, press and hold power button untill phone shutdown and reboot again. This time will boot up.
Download link
http://www.mediafire.com/download/7eq27tblav0qdjt/ParanoidAndroid_Streak.zip
How to have tablet ui
HOW TO MAKE ANY ICS ROM HAVE TABLET UI
Thanks to Veisen for his awesome work, you can follow his thread
http://forum.xda-developers.com/showthread.php?t=1767955
Tools
- Winrar or 7zip
- dex2jar
- hex workshop
- services.jar from ICS rom
How to
- extract services.jar from ICS rom (system/framework)
- use winrar to extract classes.dex from services.jar
- use dex2jar to compile classes.dex [ d2j-dex2jar classes.dex ]
- the result "classes_dex2jar.jar", use winrar to open and extract WindowManagerService.class form classes_dex2jar.jar\com\android\server\wm
- open WindowsManagerService.class in hex workshop, choose replace icon from menu bar, fill the pop up with
Find : 8E0009000A000000821B9900781D36061C36072A2A2A2A1506
Replace : 930009000A000000871B99007D1D36061C36072A2A2A2A1506 8617046E8B
click ok, then choose replace all, after that choose replace icon from menu bar again, fill the pop up with
Find : B11C36061D3607A7FF8B
Replace : B11C36061D3607A7FF86
click ok, then choose replace all
- save WindowManagerService.class
- replace WindowManagerService.class by winrar in classes_dex2jar.jar without compression
- use jar2dex and create new dex file [ d2j-jar2dex classes-dex2jar.jar ]
- rename it to classes.dex
- use 7zip to replace your classes.dex in services.jar
- copy the mod service.jar back to your rom or phone
- in build.prop change density to 128 and reboot.
Now you have tablet phone
I have tested it and the result are
- dpi 128 [phone not work, data and wifi work well]
- dpi 240 [everythings work well]
Feel free to try use other phone.apk and post the result here.
Intriguing concept!
... too bad I cannot flash it. (using ClockworkMod 6.0.1.0)
tried redownloading 3x
Crinos512 said:
Intriguing concept!
... too bad I cannot flash it. (using ClockworkMod 6.0.1.0)
tried redownloading 3x
Click to expand...
Click to collapse
Try use streakmod?
Sent from my Dell Streak using Tapatalk 2
Anybody success flash it ? I'm afraid there is bad upload.
Sent from my PC36100 using Tapatalk 2
Crinos512 said:
Intriguing concept!
... too bad I cannot flash it. (using ClockworkMod 6.0.1.0)
tried redownloading 3x
Click to expand...
Click to collapse
i have flashed it successfully by both StreakMod 0.3.2.8 and ClockworkMod 5.0.2.7
it has some interesting changes
i hope it will be better and better (such as camera and languages)
Yep, was able to flash it too. Preferred the CM9 ROM though! To each his own, I guess!
i always thought that this rom is nice... and ... it is nice..
My friend not believe that my old device can run paranoid android, same like his galaxy note untill I show him. He always laugh at me, said my ds5 is old enough and I should replace it with something new. Ha....this time I beat him
Sent from my PC36100 using Tapatalk 2
nom051205 said:
My friend not believe that my old device can run paranoid android, same like his galaxy note untill I show him. He always laugh at me, said my ds5 is old enough and I should replace it with something new. Ha....this time I beat him
Sent from my PC36100 using Tapatalk 2
Click to expand...
Click to collapse
streak 5 maybe old but it is still competitive hardware... and its large screen always beat others ( <5inch of course)
though i find it nowadays large screen is standard among south koreans...
Crinos512 said:
Intriguing concept!
... too bad I cannot flash it. (using ClockworkMod 6.0.1.0)
tried redownloading 3x
Click to expand...
Click to collapse
Unless OP silently updated, I cannot confirm this.
What I mean is that it installed fine for me with CWM 6.0, though the way it mounts isnt the preferred way long term.
If anything it shouldnt be compatable with streakmod as it's using the newer format/mount syntax (it's rather complicated in how recoveries read the update scripts).
GApps is also included in it, perhaps you should remove it and point users to a Gapps package, either mine or the 'official' CM one.
ParanoidAndroid is a source based rom isnt it?
We do (preferrably) need a source port instead of a hackport as the rom still thinks it's an EVO
Perhaps when Kibuuka gets AOSP more closer to working 100%, we'll have more people building from source instead of hackports.
Unlike the S7/S10 CM9 ports (and this port of paranoidandroid), all the ICS based ones are currently hackports.
The S5 is terribly slow compared to the S7, it has the ram and nand space to run the newest roms, but the cpu is simply overwhelmed by new apps/stuff.
It's still plenty usable, but 1st gen snapdragons simply cant compare to 3rd/4th gen snapdragons (and their equivilent Exynos/Tegra chips).
It doesnt make it useless though, I still use my S5 ocasionally even though my S7 is pretty much better in every way (except size)
Edit: after reviewing this rom with Quadrant, it seems that the IO score is unusually low. This might explain why my S5 seems so slow with it installed, if it really is IO bottlenecked it could be bottlenecking the entire system.
The other scores are comparable with AOSP/ICS, but PA is signifigantly slower even though I did a fac reset before installing.
Hmm.. it seem that baseband ignorance patch is not working.. it gives blink to the light panel... lol... i am using 366bb to see how the call quality goes and it seems fine.. is there anyway to make the ignorance patch work? I pretty much like this rom and the lags is almost gone too..
TheManii said:
Unless OP silently updated, I cannot confirm this.
What I mean is that it installed fine for me with CWM 6.0, though the way it mounts isnt the preferred way long term.
If anything it shouldnt be compatable with streakmod as it's using the newer format/mount syntax (it's rather complicated in how recoveries read the update scripts).
GApps is also included in it, perhaps you should remove it and point users to a Gapps package, either mine or the 'official' CM one.
ParanoidAndroid is a source based rom isnt it?
We do (preferrably) need a source port instead of a hackport as the rom still thinks it's an EVO
Perhaps when Kibuuka gets AOSP more closer to working 100%, we'll have more people building from source instead of hackports.
Unlike the S7/S10 CM9 ports (and this port of paranoidandroid), all the ICS based ones are currently hackports.
The S5 is terribly slow compared to the S7, it has the ram and nand space to run the newest roms, but the cpu is simply overwhelmed by new apps/stuff.
It's still plenty usable, but 1st gen snapdragons simply cant compare to 3rd/4th gen snapdragons (and their equivilent Exynos/Tegra chips).
It doesnt make it useless though, I still use my S5 ocasionally even though my S7 is pretty much better in every way (except size)
Edit: after reviewing this rom with Quadrant, it seems that the IO score is unusually low. This might explain why my S5 seems so slow with it installed, if it really is IO bottlenecked it could be bottlenecking the entire system.
The other scores are comparable with AOSP/ICS, but PA is signifigantly slower even though I did a fac reset before installing.
Click to expand...
Click to collapse
You named it hackport was exactly what I did, honestly this is the first step of porting rom (make it can boot up then see how stable it run) after that there are others step more, I skipped it
I think when the base rom hit something like beta stage, there should be a lot of changes, on that time better to port from the beginning again to hv a better result
On supersonic, we used to put Papasmurfs script (found in HTC supersonic forum) then should hv good result, I hv tried it and rom show much better performance, but browser and gmail fc. (I choose I/O scheduler = SIO).
Sorry for the "Evo" things show up
I hv changed the strings.xml on values folder but always stuck when compile framework-res.apk.
Tried every method and apktool (apktool1.4.2/apktool1.4.3/apktool1.4.3.1/apkmanagers for ics/new aapt from android sdk) found on google still no go.
Sent from my PC36100 using Tapatalk 2
If you simply use pull the our AOSP build's drivers, I'd imagine that rebuilding shouldnt be too difficult as all the hard work is making the drivers work.
It would be similar to a hackport in that you dont build everything, but it means you dont have to worry about missing those strings
We'd lose device specific stuff like dock detection, but those dont work in the first place.
Kibuuka already has the device tree up on his git repo, you could prob just use that and it'd work with a couple changes at most (hopefully, and under the assumption that you can compile android in general)
AFAIK the 'official' apktool doesnt work on API15 apks, it only supports up to API14 (4.0.1-4.0.2).
Someone's supposedly made a mod to support API15, but I havnt tried it.
Hi good work i flashed the rom and it works perfect on my ds5 but just one problem the lights for the 3 softkeys on the ds5 stays on even when you turn the screen off did i do something wrong? Please advice thanks
That's problem on every ics rom for dell streak
SULEY1 said:
Hi good work i flashed the rom and it works perfect on my ds5 but just one problem the lights for the 3 softkeys on the ds5 stays on even when you turn the screen off did i do something wrong? Please advice thanks
Click to expand...
Click to collapse
use rootdim and select night mode #1 or #2 or #3 :good:
How to change at 160dpi?
ikimradio said:
How to change at 160dpi?
Click to expand...
Click to collapse
Use LCD modder. But the dial stops working for me after sometime on that.
ikimradio said:
How to change at 160dpi?
Click to expand...
Click to collapse
goto..
settings > paranoid settings > hybrid settings > global density
and change it to your preferrence...
disable hybrid mode in case the homescreen look big...
i am currently on 120dpi and i have no problem with the dial not working... all works so far...
---------- Post added at 11:36 AM ---------- Previous post was at 11:34 AM ----------
ncik said:
Use LCD modder. But the dial stops working for me after sometime on that.
Click to expand...
Click to collapse
if you really use this rom.. dont use lcd modder.. use the built in dpi changer..