Bad blocks. Need help - HTC Pico (Explorer)

Hi there people,
I have a problem with my htc explorer, I have two bad blocks in userdata and system and no rom is working correctly gb roms are slow CM roms are fast but major things doesnt work correctly.(like wifi) Is there any way to mark the bad block "bad" so that the phone doesn't use it and the problems doesn't occur. I dont have any nand problem(i had but right now it is fine), my internal storage is just fine. I heard that the phone itself mark the bad block but in my case i am having problems with the bad blocks.
I have done all kind of wipes through recovery. even washing machine wipe(just kidding)
So any buddy help here.

If this doesn't help......... somebody with more knowledge should share something
http://forum.xda-developers.com/showthread.php?p=38098622

shortyoko said:
If this doesn't help......... somebody with more knowledge should share something
http://forum.xda-developers.com/showthread.php?p=38098622
Click to expand...
Click to collapse
checked that before but doesnt resolve my problem.

abache said:
checked that before but doesnt resolve my problem.
Click to expand...
Click to collapse
You install recovery-clockwork-5.0.2.8-pico...and then you look if with "adb devices" command your phone is in list...First this.

Mionetto80 said:
You install recovery-clockwork-5.0.2.8-pico...and then you look if with "adb devices" command your phone is in list...First this.
Click to expand...
Click to collapse
I have cmw recovery and my phone is listed.

abache said:
I have cmw recovery and my phone is listed.
Click to expand...
Click to collapse
Search on the internet aromafm-1.80.zip. Now in the root of your sdcard you copy the file zip and flash_erase file (or mounting directly into the phone or takeing off the sd). In the recovery in mount section... mount the system dir (mount system). Then you select install zip "aromafm-1.80.zip". The file explorer starts. Move the file flash_erase in the directory /system/xbin, check if flash erase has 755 permissions always with the explorer. With this...missing little. Tell me when you did ...

I don't think you have a problem in the first place.
You're just paranoid of bad blocks.
~just my psychological diagnosis.
Bad blocks are marked bad.. there's nothing you can do to change that. And Wi-Fi is a known bug. ~try kernel 2.6 for Wi-Fi.
Sent from my HTC Explorer A310e using xda app-developers app

Already did the cute prince recovery procedure. 
 @BANNED : i dont know but after using the cm roms for 1 day the whole rom start to force crashes like every single thing.

abache said:
Already did the cute prince recovery procedure.
@BANNED : i dont know but after using the cm roms for 1 day the whole rom start to force crashes like every single thing.
Click to expand...
Click to collapse
mightbe script problem
try to get a log
Sent from my HTC Explorer A310e using xda app-developers app

BANNED said:
mightbe script problem
try to get a log
Sent from my HTC Explorer A310e using xda app-developers app
Click to expand...
Click to collapse
I have tested on mounts2sd and intext script. my bad i have deleted the recovery.log but i am sure i have read a bad block at userdata and system in recovery.log.

abache said:
I have tested on mounts2sd and intext script. my bad i have deleted the recovery.log but i am sure i have read a bad block at userdata and system in recovery.log.
Click to expand...
Click to collapse
No try to get a log, when all apps force closes
Sent from my HTC Explorer A310e using xda app-developers app

Logcat.
i have attached the logcat please have a look.

abache said:
i have attached the logcat please have a look.
Click to expand...
Click to collapse
When was the log taken?
@ what time after boot?
@ that time, what were you doing ~which app are you in?
What memory script were you using?
Post a screenshot of /cache partition now with diskusage app from play store.
Sent from my HTC Explorer A310e using xda app-developers app

Try to wipe cache and dalvik from recovery menu...
Reflash with a clean install if the problem persists..

Your dalvik cache is the culprit here..
Possible explanation is that the script you're using, has peoblems building the dalvik at the new place, ie, sd-ext..
What you can do is, go script-free for a couple days.. See if the FC problem persists...
ғг๏๓ ҭђє ғเรђ™

How does overclocking PLL2 create bad blocks on NAND?
Can bad blocks get created even when the processor is running at a higher clock rate and no I/O operations are taking place? Most users have damaged frequently used partitions (system, userdata and cache)
I wish someone could inspect bad blocks (data and OOB data) with JTAG

Sachin Thomas said:
How does overclocking PLL2 create bad blocks on NAND?
Can bad blocks get created even when the processor is running at a higher clock rate and no I/O operations are taking place? Most users have damaged frequently used partitions (system, userdata and cache)
I wish someone could inspect bad blocks (data and OOB data) with JTAG
Click to expand...
Click to collapse
It pains my heart everytime i read/hear/see JTAG...
My theory for nand "burning" is that the read write speeds dont match with the new clock speed, and they just..... Stop working...
M still looking for an explanation.. Maybe nhb can explain...
ғг๏๓ ҭђє ғเรђ™

May be the process which marks blocks bad is at fault.

legen_dary said:
It pains my heart everytime i read/hear/see JTAG...
My theory for nand "burning" is that the read write speeds dont match with the new clock speed, and they just..... Stop working...
M still looking for an explanation.. Maybe nhb can explain...
Click to expand...
Click to collapse
In that case, can't we programmatically switch to a safe PLL2 value before a write operation and restore the higher value once the operation is completed?
Once you had said that the NOOP I/O scheduler reduces the probability of NAND burn. I also experienced it, I could play TR2 at 800 MHz for at least 30 minutes (although I don't overclock anymore and wouldn't recommend anyone to do it)

Sachin Thomas said:
In that case, can't we programmatically switch to a safe PLL2 value before a write operation and restore the higher value once the operation is completed?
Once you had said that the NOOP I/O scheduler reduces the probability of NAND burn. I also experienced it, I could play TR2 at 800 MHz for at least 30 minutes (although I don't overclock anymore and wouldn't recommend anyone to do it)
Click to expand...
Click to collapse
About the PLL2 stuff, you'll have to talk to the pros.. I dont know anything, and I mean anything at all, about all this..
Regarding the memory loss, my system memory is 135 mb now, instead of the 150 mb... Couldnt recover it... So i too, dnt overclock anymore.. I still recommend it, but only for short periods of time.. Like if you wanna play a game, switch to oc, but then switch back.. Prolonged use, i would prevent..
ғг๏๓ ҭђє ғเรђ™

Related

[TOOL] G2X Cleanup Batch *** WARNING *** WILL FORMAT INTERNAL SD

If you are going to flash and ICS ROM after this tool please make sure to first install a GB then ICS otherwise your SD card will not be accessible. I am trying to find a fix but it has been illusive. This statement will be removed once a fix has been found and OP updated.
Now with CWM Touch!
This method uses NVFLASH to recreate all partitions and formats them, thereby getting rid of the file allocation pointers and hence renders data inaccessible without effort.
Note: I have never seen a file come back to life or its data affect other files without effort on the users part or a temporary glitch once the partitions and pointers have been overwritten. Please post a reply with evidence if you have seen it.
Benefits:
The contents of the zip file can be used to super clean G2X before a new ROM flash. This tool recreates all the partitions in the phone so wipes the pointers to all files (everything). The method it employes has existed from before. The files here will stop short of pushing a ROM, so that you can push your favorite ROM.
Prerequisites:
G2X (Will not work on O2X due to different partition table)
Desire to have a clean install of your favorite ROM
Backup your data
*** WARNING ***​
This tool will wipe both phone internal memory and internal SD card. External SD card content is safe.
Don't say you haven't been warned!
What to do:
Download the attached Zip file.
Take out the battery (assuming you have backed up your data on external SD card, computer or elsewhere), connect the device via USB while holding VOL+ and VOL- together. Don't let go of the volume buttons until the device is recognized.
(I typically leave Device Manager open to see when it shows up in the list under "USB Controllers").
Launch flash.bat, sit back and wait until the process finishes (generally a good idea to open a command prompt, CD to the directory and then run the file).
Unplug, put battery in, reboot into CWM recovery (pushed by this tool) by holding VOL- first, then pressing and holding POWER).
Flash your favorite ROM.
Enjoy!
I made this package because I could not get the bluetooth to work with G2x GB 2.3.3 (and below). The issue was a disconnect problem where both the phone and headset would still think they were connected but in audio would not be routed for a call or media. After this procedure my phone has not had an issue for almost 3 weeks now. I have tried it with two ROMs and 3 different headsets without any issues.
I guess I will not toss this phone after all .
Putting it out there in the hope that it may help others solve some of their issues as well. I suspect bad data stays in places not touched by other methods.
Your comments are most welcome.
[Update]
Klathmon has made an newer version with CWM 5.0.2.8. RP by Klathmon can be found here:
http://forum.xda-developers.com/showpost.php?p=24768294&postcount=66
I have tested the windows version but linux one is untested. Use at your own risk.
[Update]
Now with CWM Touch!
Thanks to everyone who has contributed on this thread with a drive to positive change! You work/comments/suggestions are very much appreciated.
References:
http://forum.xda-developers.com/showthread.php?t=1248644. This link was the inspiration for the current work.
Link to CWM Touch development thread. I took the image posted there: http://rootzwiki.com/topic/22984-recovery-touch-enabled-cwm-5813/
[EDIT] The zip file should be fixed now. Darn work machine does something to the upload.
was just about to flash the new hellfire rom and saw this tool! will try it out and see how things go
edit: yeah corrupt zip on my end too.
The zip file seems to be corrupt. Could you re-upload plz
worked great on my end, no problems.
khanggle said:
worked great on my end, no problems.
Click to expand...
Click to collapse
The real test is how stable your ROM would stay with this method to wipe than any of the other methods.
I guess only time will tell .
wow this method really blaze hellfire much thanks to your( you) & (rom dev)
Ohh I like this. Thank you for sharing .
This thing is faster than nullifier, and I especially like how you don't need to be in CWM to use it. It just seems like doing it in "update mode" would allow better manipulation of the phone's internals.
so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)
dodgefan67 said:
so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)
Click to expand...
Click to collapse
He states in OP that it doesn't write anything, therefor doesn't "nullify". It formats and partitions.
dodgefan67 said:
so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)
Click to expand...
Click to collapse
Actually you are right. Deleting, recreating and formatting partitions does not get did of the 1s and 0s, so in that sense the data is still there. However the pointers are gone, and hence even though the data is still there it can't be accessed without effort.
What do you think the nand has on it when the device is shipped... I can assure you its not ask zeroes!
Sent from my LG-P999 using XDA
mansa_noob said:
Actually you are right. Deleting, recreating and formatting partitions does not get did of the 1s and 0s, so in that sense the data is still there. However the pointers are gone, and hence even though the data is still there it can't be accessed without effort.
What do you think the nand has on it when the device is shipped... I can assure you its not ask zeroes!
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
Well no, it has a next to worthless version of android Also, the point he was trying to get across is that it would be better for you to present the script for what it is and not try to compare it to other scripts that do something entirely different. You do kind of imply that you accomplish the same thing as the Nullifier script and more, when in fact you simply do something different.
Some may and probably will prefer your script, at least for specific purposes, while others will prefer the Nullifier script.
MWBehr said:
Well no, it has a next to worthless version of android Also, the point he was trying to get across is that it would be better for you to present the script for what it is and not try to compare it to other scripts that do something entirely different. You do kind of imply that you accomplish the same thing as the Nullifier script and more, when in fact you simply do something different.
Some may and probably will prefer your script, at least for specific purposes, while others will prefer the Nullifier script.
Click to expand...
Click to collapse
Done. OP updated to reflect. Thanks for clarifying that. It was not my intention to state that this tool does anything any other does, or does not.
I think we are all trying to do the same thing... get rid of the issues when swapping ROMs like _____. I can't seem to think of a good analogy here .
thanks for clarifying the OP, that makes much more sense
and no i wasnt trying to say you were reinenting the wheel, just trying to understand what your tool is actually doing
and also i do understand that it would take effort to get data off any type of storage device once the partition has been erased. i deal with wiping hard drives in a data center all the time. we use a DOD wipe tool that writes 1s and 0s over a drive a minimum of three full times to eradicate the data
but with this tool doing it outside of CWM, it sounds like it may do a better job of it
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?
dodgefan67 said:
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?
Click to expand...
Click to collapse
There is no need to push CWM 5.02. As I said in the OP it is a mod of the script found in the reference. In that script it was pushing default recovery. Since the recovery partition is being overwritten as well you will loose existing one and you need a recovery to be able to push a new ROM. Hence the need to push recovery (instead of using super one click).
As long as the recovery is not bigger than the partition that holds it we should be able to push a newer version. However I can't leave it empty or people will look for me with a shotgun (myself included ).
dodgefan67 said:
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?
Click to expand...
Click to collapse
I was thinking the same thing but seems easy enough .. add the cwm img to the dir and edit the .cfg file. Hopefully that should get the new CWM flashed
So would it be benefitial or pointless to nullify to clear the data then run this script for a... super clean?
Sent from my LG-P999 using XDA
mansa_noob said:
There is no need to push CWM 5.02. As I said in the OP it is a mod of the script found in the reference. In that script it was pushing default recovery. Since the recovery partition is being overwritten as well you will loose existing one and you need a recovery to be able to push a new ROM. Hence the need to push recovery (instead of using super one click).
As long as the recovery is not bigger than the partition that holds it we should be able to push a newer version. However I can't leave it empty or people will look for me with a shotgun (myself included ).
Click to expand...
Click to collapse
ahhhhhh now i understand. my eyes have been opened LOL
---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------
PL0X_Kleiner said:
So would it be benefitial or pointless to nullify to clear the data then run this script for a... super clean?
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
i think it would be pointless unless you are super paranoid
dodgefan67 said:
ahhhhhh now i understand. my eyes have been opened LOL
---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------
i think it would be pointless unless you are super paranoid
Click to expand...
Click to collapse
Nobody is twisting any arms here... Use it if you want to, don't if you don't want to.
I saw benefit so posted so that others may benefit as well.
Sent from my LG-P999 using XDA
Ok so question, why are you killing all the data on your internal SD card? Why not just the individual partitions that the phone uses? Your destroying data that don't need to be destroyed before flashing a rom...
Sent from my LG-P999 using xda premium
It does not have to be destroyed. I just haven't had a chance to test without recreating emmc yet.
Next step. Likely tomorrow. Would like to test before release.
Sent from my LG-P999 using XDA
[edit] BTW, I do want to restate that there is some data that needs to be destroyed which is not being taken care of by other methods. I don't believe it is in the emmc, but rather it resides in one of the other partitions. Most methods out there are only working in the /data, /system and /cache domain.
My original problem (bluetooth disconnect) which happens to be a problem for some in the community even now was only completely fixed by this method.

[Q] Is it possible to disable "Cell standby" app on a damaged phone?

My i9103 lost its IMEI by itself (100% stock phone). I tried to fix it in some service shops, but they all failed. It's hardware problem, they say. Since I cannot contact samsung to repair my phone, I am using it as a "tablet", and I'm ok with that
However, since the phone is damaged, battery consumption is huge. "Cell standby" and "Dialer" consume most of the battery. For example, after 6 hours "Cell stanby" - 73%, "Dialer" - 7%, "Display" - 5%, "Phone idle" - 2%.
Now the phone is rooted, with stock 2.3.6 rom. Whatever I tried to flash, some stock or custom roms, the problem was the same. The phone is in "airplane" mode, but once activated it cannot be deactivated. Turning off the radio from the config fail.
Is there any possibility to disable (remove) those applications from the Android using terminal emulator on rooted device?
Thanks!
Re: [Q]
Like what applications??
Sent from my GT-I9103 using Tapatalk HD
kataria.vikesh said:
Like what applications??
Click to expand...
Click to collapse
"Cell standby" and "Dialer". They consume too much battery, and I do not use them.
LeGrr said:
"Cell standby" and "Dialer". They consume too much battery, and I do not use them.
Click to expand...
Click to collapse
That's system applications buddy. Try to wipe cache and dalvik cache from cwm.
Sent from my GT-I9103 using Tapatalk HD
kataria.vikesh said:
That's system applications buddy. Try to wipe cache and dalvik cache from cwm.
Click to expand...
Click to collapse
As I already said, I tried to flash all possible roms, wiping cache and everything was the number one in to-do list.
That is the main reason why I posted question here. Maybe somebody know something about system applications, and how to do some hocus-pocus witchcraft on a rooted device If the question was so simple, I would handle it myself, probably
LeGrr said:
As I already said, I tried to flash all possible roms, wiping cache and everything was the number one in to-do list.
That is the main reason why I posted question here. Maybe somebody know something about system applications, and how to do some hocus-pocus witchcraft on a rooted device If the question was so simple, I would handle it myself, probably
Click to expand...
Click to collapse
Ohhhhhhh.. Actually i didnt read that so much. Let wait for some magician here for doing magic with system applications.
Sent from my GT-I9103 using Tapatalk HD
You can use the Titanium Backup to freeze the dialer app.(Phone.apk or Phonesky.apk maybe )
The-Droidster said:
You can use the Titanium Backup to freeze the dialer app.(Phone.apk or Phonesky.apk maybe )
Click to expand...
Click to collapse
Thanks, I did it and so far it's much better. I have to test it for longer time, after charging
Why dont you try restoring your IMEI by yourself??
Might help you out..
There are a lot of threads here that help you in retreiving lost imeis..
Sent from my GT-I9103 using xda app-developers app
The-Droidster said:
You can use the Titanium Backup to freeze the dialer app.(Phone.apk or Phonesky.apk maybe )
Click to expand...
Click to collapse
but what if he will not able to call after freezing the phone.apk..??
DeepankarS said:
Why dont you try restoring your IMEI by yourself??
Might help you out..
There are a lot of threads here that help you in retreiving lost imeis..
Click to expand...
Click to collapse
Contact user "Odia" via PM & wait patiently for his response (I.e you send a PM & wait for a reply, you don't send any 'reminders') & he may be able to fix it for you for a small 'donation' (Tho I'm not even sure if he still does this kind of thing).
If EFS backup is not there then its not possible to restore IMEI, only way is to go to SSC....
kataria.vikesh said:
but what if he will not able to call after freezing the phone.apk..??
Click to expand...
Click to collapse
When he is not having IMEI then what is the point in having phone.apk which is use less.....
mj.vikram said:
Contact Odia via PM & wait patiently for a response (I.E you send a PM & wait for a reply, you don't send any 'reminders') & he may be able to fix it for you for a small 'donation' (Tho I'm not even sure if he still does this kind of thing).
If EFS backup is not there then its not possible to restore IMEI, only way is to go to SSC....
When he is not IMEI then what is the point in having phone.apk which is use less.....
Click to expand...
Click to collapse
Are you MJ..?? Coz I didn't understand you today..??
kataria.vikesh said:
Are you MJ..?? Coz I didn't understand you today..??
Click to expand...
Click to collapse
what happen dude, i am the same...
"Odia" is user name on XDA he have one tool which will write IMEI number even though you dont have EFS backup , i heard he took small donations and corrected the IMEI for Galaxy S2 user's, so i asked him to contact ODIA.....
now that I have seen this thread, I want to be safe be backing up my efs folder.. But can anyone tell me how to make a backup of it? Do I just copy that folder and paste it onto an external SD or is it something different?
pankajramnani said:
now that I have seen this thread, I want to be safe be backing up my efs folder.. But can anyone tell me how to make a backup of it? Do I just copy that folder and paste it onto an external SD or is it something different?
Click to expand...
Click to collapse
Use EFS back up pro best app ....
http://forum.xda-developers.com/showthread.php?t=1724440
Sent from my GT-I9103 using Tapatalk 2
mj.vikram said:
what happen dude, i am the same...
"Odia" is user name on XDA he have one tool which will write IMEI number even though you dont have EFS backup , i heard he took small donations and corrected the IMEI for Galaxy S2 user's, so i asked him to contact ODIA.....
Click to expand...
Click to collapse
No buddy, not like that. I was wondering coz My Lil bro did the same (means typed something which was become questions to all peoples).
BTW use orange backup. Coz I have seen that it takes backup of /efs.

[Idea] dual boot

This is just one of my crazy thoughts,
It might be just an idea for devs...
As in computers,
Y can't we do dual partition, along with the existing one, such that flashing 2 different Roms in those 2 partitions..
And while booting with an option of swapping partitions,
Can't we use 2 Roms @ a time....
I know RAM will get ****ed up...
But just a curiosity to know, wether it's possible
Or
Had anyone tried this already!!!!
swaroopg551 said:
This is just one of my crazy thoughts,
It might be just an idea for devs...
As in computers,
Y can't we do dual partition, along with the existing one, such that flashing 2 different Roms in those 2 partitions..
And while booting with an option of swapping partitions,
Can't we use 2 Roms @ a time....
I know RAM will get ****ed up...
But just a curiosity to know, wether it's possible
Or
Had anyone tried this already!!!!
Click to expand...
Click to collapse
I don't think that it's even possible without S-OFF just a guess ...
Sent from my HTC Explorer A310e using xda app-developers app
swaroopg551 said:
This is just one of my crazy thoughts,
It might be just an idea for devs...
As in computers,
Y can't we do dual partition, along with the existing one, such that flashing 2 different Roms in those 2 partitions..
And while booting with an option of swapping partitions,
Can't we use 2 Roms @ a time....
I know RAM will get ****ed up...
But just a curiosity to know, wether it's possible
Or
Had anyone tried this already!!!!
Click to expand...
Click to collapse
I am not saying it is impossible
But how it could be possible bcoz the system partition our pico is not enough for that
And for using two roms we have to make two sd-ext partitions and also we have to flash the whole rom except boot.img to the sd-ext partitions
And it is not possible till now
Bcoz we have to keep many file in system partition like lib ,bin,xbin
Sent from my HTC Explorer using xda premium
its definitely bro, but its damn hard, we need to have atlest 3(maybe 4 partitions in sd-card) one for system,one for data one for cache ...
And then the hardest part of all a switching mechanism ... many devices have switching mechanism such as multirom of nexus .. but as our pico boot partition is very small .. a whole lot of tweaking is needed to be done obtain dual boot... i'll try to work on it after fall july (exams this month !!)
ayushrox said:
its definitely bro, but its damn hard, we need to have atlest 3(maybe 4 partitions in sd-card) one for system,one for data one for cache ...
And then the hardest part of all a switching mechanism ... many devices have switching mechanism such as multirom of nexus .. but as our pico boot partition is very small .. a whole lot of tweaking is needed to be done obtain dual boot... i'll try to work on it after fall july (exams this month !!)
Click to expand...
Click to collapse
I think we can create multiple boot partitions on SD card and flash our utility (which has a GUI that shows the list of all ROMs) on our real boot partition. This master utility should read and copy the contents of the corresponding boot partition of the selected ROM on SD card into 0x12c08000 physical and jump into it (not sure whether this jumping can be performed at a higher level, but we've done that at assembly level for S-OFF)
Is it possible to make sd-ext partition as
Boot partition?
If yes then it is easy to make multiswitch roms
But i think our pico's performance will degrade and also sd card life will also degrade
Sent from my HTC Explorer using xda premium
So... So...
option 1:
kexec_hardboot needed
multirom needs to be ported :fingers-crossed:
^Above two, which would take some time...
option 2:
In the meanwhile, it is possible to... boot two ROMs, with a derped boot.img. If two ROMs use the same kernel, it can be used to dual boot the two ROMs. And, yes, 4 partitions in sd-card (fat32>data>system>cache) required. switching ROMs could be done using the terminal emulator. bla bla, and stuff. and, I am doing serious talk here.
so, two options. the first one: real dual booting, devs need to work on it, and get the kexec hardboot patch onto our kernels first.
the second: namesake. a fake troll dual_boot, but still dual_boot is achieved (like i could, on the same pico).
And, life of sdcard... can't say. class 4, mine didn't get damaged, because i dual boot using the second option
vineethraj49 said:
option 1:
kexec_hardboot needed
multirom needs to be ported :fingers-crossed:
^Above two, which would take some time...
option 2:
In the meanwhile, it is possible to... boot two ROMs, with a derped boot.img. If two ROMs use the same kernel, it can be used to dual boot the two ROMs. And, yes, 4 partitions in sd-card (fat32>data>system>cache) required. switching ROMs could be done using the terminal emulator. bla bla, and stuff. and, I am doing serious talk here.
so, two options. the first one: real dual booting, devs need to work on it, and get the kexec hardboot patch onto our kernels first.
the second: namesake. a fake troll dual_boot, but still dual_boot is achieved (like i could, on the same pico).
And, life of sdcard... can't say. class 4, mine didn't get damaged, because i dual boot using the second option
Click to expand...
Click to collapse
that's what i am talking about if we put kexec hardboot in the boot.img won't it become too big for our boot partition ?
@ayushrox
hey, apart from pico, can we apply the idea of dual boot in other high end android ? u mentioned about "nexus", above in your post.
prabhat228 said:
@ayushrox
hey, apart from pico, can we apply the idea of dual boot in other high end android ? u mentioned about "nexus", above in your post.
Click to expand...
Click to collapse
yeah its fairly possible its even done on many devices for example nexus 7 : google multirom ...
there you will see a dual booting feature based on kexec hard boot..
not actually...
ayushrox said:
that's what i am talking about if we put kexec hardboot in the boot.img won't it become too big for our boot partition ?
Click to expand...
Click to collapse
Only required files are config'ed in kernel. the kexec binaries are separate, afaik.
Don't you know about boot manager app. Go check it in Google play store. It is not possible to make choose a rom to boot at startup as it comes in PC, but using boot manager, it's possible to select which rom you want to open after reboot.
But you will need to do partitions of your sd card. Maximum 4 roms are supported. The number of partitions depends upon how many roms you want to have.
Click thanks of I helped
Sent from my HTC Explorer A310e using xda app-developers app
Does it work?
Yashas123 said:
Don't you know about boot manager app. Go check it in Google play store. It is not possible to make choose a rom to boot at startup as it comes in PC, but using boot manager, it's possible to select which rom you want to open after reboot.
But you will need to do partitions of your sd card. Maximum 4 roms are supported. The number of partitions depends upon how many roms you want to have.
Click thanks of I helped
Sent from my HTC Explorer A310e using xda app-developers app
Click to expand...
Click to collapse
*no_offence_meant*
Does it actually work? Did you try it?
I was struck with the values, :silly: but ended up in a re-flash!
If it does work, waiting for a tutorial on how it worked for you on pico. :laugh:
vineethraj49 said:
*no_offence_meant*
Does it actually work? Did you try it?
I was struck with the values, :silly: but ended up in a re-flash!
If it does work, waiting for a tutorial on how it worked for you on pico. :laugh:
Click to expand...
Click to collapse
Soon i'll put new thread on the tutorial. I am busy with my studies right now, so it might take a little bit of time.:good:
It's even done on a note 2 with the devil kernel just check it out and it's has been working till now.. It's a bit complicated and time consuming but possible.
Sent from my GT-N7100 using xda premium

[MOD][K2_CL][K2_U][K2_UL]Bind InternalSD With Phone Storage

Also, by the way guys, I posted this mod because I could never get the vold.fstab mod to work on ICS. so if you are on JB I would totally recommend the vold.fstab swap mod over this one.
BOOST MOBILE ONLY K2_CL
https://db.tt/nRbob3sP
I've found and mod a file by simonsimons34 that you add to /system/etc/init.d that will bind(merge) your phone storage with internal sd
If you kernel supports it
This is what I used to add init.d
https://play.google.com/store/apps/details?id=com.init.d_installer
Download this file and put it in your init.d folder and set permissions to rwx r-x r-x.
This bind(merge) your internal sd and phone storage.
K2_U & K2_UL ONLY
https://db.tt/vLu7IK5k
download this file and place it in your
init.d folder AND TAKE THE 'K2_UK2_UL' OFF THE END OF THE NAME
it should look like this
99binddata
And set permissions to rwx r-x r-x
And reboot.
Is bussybox required?
I have only these kernel and root no bussybox and s-off
http://forum.xda-developers.com/showthread.php?p=41684667#post41684667
Woooo, sounds awesome !
Anyone tried it ? Screen captures ?
I don't think you need busybox, you can use chmod in a adb shell, but I might be wrong.
Yes you need busy box
And screen shot only shows calculating.....
I think some form of edited vold.fstab is needed to actually show the bind.
I think?
Kajry said:
Is bussybox required?
I have only these kernel and root no bussybox and s-off
http://forum.xda-developers.com/showthread.php?p=41684667#post41684667
Click to expand...
Click to collapse
This is what I used to add init.d
https://play.google.com/store/apps/details?id=com.init.d_installer
russellvone said:
Yes you need busy box
And screen shot only shows calculating.....
I think some form of edited vold.fstab is needed to actually show the bind.
I think?
Click to expand...
Click to collapse
Actually, I think there's a big error here... the bind options doesn't merge two devices (of different filesystem, most of all).
What the bind option does, is to allow the mount of a device in more than one location, so what you'll have using this script is to see your internal sd partition mounted as data partition, which could be very dangerous! Casue you'll have a fat32 filsystem mounted in a place where android expects an ext filesystem.
there are ways to merge filesystems (like unionfs), but I don't think there's an android implementation... and are quite unstables at current stage of development
you shouldn't risk to brick your phone, at most you could end by wiping your system partition and reinstall your rom if your phone shouldn't boot anymore though I'd be very surprised if this would work o.o
don't mess things too much!
madpausa said:
Actually, I think there's a big error here... the bind options doesn't merge two devices (of different filesystem, most of all).
What the bind option does, is to allow the mount of a device in more than one location, so what you'll have using this script is to see your internal sd partition mounted as data partition, which could be very dangerous! Casue you'll have a fat32 filsystem mounted in a place where android expects an ext filesystem.
there are ways to merge filesystems (like unionfs), but I don't think there's an android implementation... and are quite unstables at current stage of development
you shouldn't risk to brick your phone, at most you could end by wiping your system partition and reinstall your rom if your phone shouldn't boot anymore though I'd be very surprised if this would work o.o
don't mess things too much!
Click to expand...
Click to collapse
Also, this is information is good, thank you for your post.
I always try and verify mods and/or scripts before posting.
That means, I am running this script right now and have been since last night and I don't have any issues at all. I would never post something that I haven't tried for myself.
And to prove is working, if anybody has an app that they have tried downloading but had the 'not enough space' error, post it here and I will download it.
russellvone said:
I always try and verify mods and/or scripts before posting.
That means, I am running this script right now and have been since last night and I don't have any issues at all. I would never post something that I haven't tried for myself.
And to prove is working, if anybody has an app that they have tried downloading but had the 'not enough space' error, post it here and I will download it.
Click to expand...
Click to collapse
I'm sorry, I didn't meant to offend you.
What I said is that this will hardly merge two filesystems.
If you have a total of about 8gb of internal storage, then I'm wrong
But, most likely, you'll only have your sdcard mounted as data partition, which might give some problems.
I'm downloading modern combat 4 right now, and if it installs correctly that means this is working. It is 1.92 gb in size and you can see from the screen sit that I only have 1.14 gb of space and 886mb available shown but I have this script running so..... We'll see.
Ps I'm not taking offence at all, it's healthy to object something if its not proven.
:thumbup:
russellvone said:
I'm downloading modern combat 4 right now, and if it installs correctly that means this is working. It is 1.92 gb in size and you can see from the screen sit that I only have 1.14 gb of space and 886mb available shown but I have this script running so..... We'll see.
Ps I'm not taking offence at all, it's healthy to object something if its not proven.
:thumbup:
Click to expand...
Click to collapse
I just realized, I made a big mistake... I always thought that we had 4gb of dedicated data storage and most of it was eaten by sense stuff... Looking at the partition table right now, I see we only have 1gb of data storage o.o
Which means this script is actually useful, cause will make use the 4gb of internal sdcard, instead of our 1 gb of data!!!!
Seems like is working!
Question about boost mobile version
russellvone said:
K2_U & K2_UL ONLY
https://db.tt/vLu7IK5k
download this file and place it in your
init.d folder AND TAKE THE 'K2_UK2_UL' OFF THE END OF THE NAME
it should look like this
99binddata
And set permissions to rwx r-x r-x
And reboot.
Click to expand...
Click to collapse
But your phone is Boost. So do you know if anything like that works with boost k2_cl version? Thanks in advance
My phone is K2_CL
the first post (OP) has the boost file
^^did it work? Did you download and install the game okay?
Burginthorn said:
^^did it work? Did you download and install the game okay?
Click to expand...
Click to collapse
Look at post #12
It downloaded and installed, and plays smooth as ever.
So the extra data doesn't show up in settings correct?
Sent from my Nexus 7 using Tapatalk 4
No just shows calculating......
russellvone said:
K2_U & K2_UL ONLY
https://db.tt/vLu7IK5k
download this file and place it in your
init.d folder AND TAKE THE 'K2_UK2_UL' OFF THE END OF THE NAME
it should look like this
99binddata
And set permissions to rwx r-x r-x
And reboot.
Click to expand...
Click to collapse
Hi ive got a UK HTC One SV LTE unlocked and i believe it is the k2ul version, is this mod compatible with the phone or is it boost only?? will it work with stock kernel or will i have to have a custom kernel to get this to work? and is this mod different to this thread http://forum.xda-developers.com/showthread.php?p=46524538#post46524538 ?? this thread says bind and that one is a swap one?? im confused

Delete bloatware

Hi guys.
Just finished rooting my phone but I can't figure out how to delete the bloatware like Lounge and Facebook.
After root, all I can do still is disable them.
Any thoughts?
krankenator said:
Hi guys.
Just finished rooting my phone but I can't figure out how to delete the bloatware like Lounge and Facebook.
After root, all I can do still is disable them.
Any thoughts?
Click to expand...
Click to collapse
How have you rooted?, as on the xa root is only available via unlocked bootloader. If you can't delete system apps you don't have full root with r/w access. Either Sony RIC is still active or your doing something seriously wrong. Is the system mounted r/w if so deleting them shouldn't be a problem.
Sent from my Xperia XA using XDA Labs
aidy.lucas said:
How have you rooted?, as on the xa root is only available via unlocked bootloader. If you can't delete system apps you don't have full root with r/w access. Either Sony RIC is still active or your doing something seriously wrong. Is the system mounted r/w if so deleting them shouldn't be a problem.
Sent from my Xperia XA using XDA Labs
Click to expand...
Click to collapse
I rooted using this guide starting with unlocking the bootloader. http://forum.xda-developers.com/xperia-xa/how-to/f31xx-how-to-root-xperia-xa-noob-t3430170
Everything seemed to check out. I had root status, but could not delete them.
Only thing I can think is that in SuperSU I did not check the "Enable su during boot" or the "Full unroot"
krankenator said:
Hi guys.
Just finished rooting my phone but I can't figure out how to delete the bloatware like Lounge and Facebook.
After root, all I can do still is disable them.
Any thoughts?
Click to expand...
Click to collapse
You have to delete them from /system/app and some in /system/priv-app.
rrvuhpg said:
You have to delete them from /system/app and some in /system/priv-app.
Click to expand...
Click to collapse
I thought it might be something like that but where would I access that?
I tried using ES File Explorer but it didn't work.
I still "facebook-stub.apk cannot be deleted.
So I tried using the file manager in TWRP but same thing.
krankenator said:
I thought it might be something like that but where would I access that?
I tried using ES File Explorer but it didn't work.
I still "facebook-stub.apk cannot be deleted.
So I tried using the file manager in TWRP but same thing.
Click to expand...
Click to collapse
That's strange, in TWRP try mount /system rw in the mount menu (no problem on XA), under Android try with Root Explorer or Root Browser. Tried myself the 2 ways without problem.
rrvuhpg said:
You have to delete them from /system/app and some in /system/priv-app.
Click to expand...
Click to collapse
What about Titanium Backup? He can't use that to remove system apps?
Rafixxxx said:
What about Titanium Backup? He can't use that to remove system apps?
Click to expand...
Click to collapse
Probably yes, I don't use any uninstaller, just a root browser or TWRP.
[/COLOR]
rrvuhpg said:
Probably yes, I don't use any uninstaller, just a root browser or TWRP.
Click to expand...
Click to collapse
I dont want create new thread, anyway had one question for You @rrvuhpg
Stock XA kernel can handle swap file and work good with fast sd card?
Ofc i mean add RAM.
Rafixxxx said:
[/COLOR]
I dont want create new thread, anyway had one question for You @rrvuhpg
Stock XA kernel can handle swap file and work good with fast sd card?
Ofc i mean add RAM.
Click to expand...
Click to collapse
Zram is already in the stock kernel it was on all lollipop(mid-range Xperias)and I've seen the files while exploring the system with a file manager this device has plenty of ram if that's what you mean.
Adoptable storage has already been done aswell see the thread but it doesn't read the gb of the device correctly it's just a random selection of numbers with a - in front of it.
Sent from my Xperia XA using XDA Labs
Rafixxxx said:
[/COLOR]
I dont want create new thread, anyway had one question for You @rrvuhpg
Stock XA kernel can handle swap file and work good with fast sd card?
Ofc i mean add RAM.
Click to expand...
Click to collapse
Kernel seem to have full support but I don't know why you want to increase RAM, XA use zram as swap, you can change the size up to 1Go with a good kernel manager app. I don't know if you can move swap path Look at my screens if it can help you
rrvuhpg said:
That's strange, in TWRP try mount /system rw in the mount menu (no problem on XA), under Android try with Root Explorer or Root Browser. Tried myself the 2 ways without problem.
Click to expand...
Click to collapse
That worked. Both Root Browser and mounting the system in TWRP worked. Thank you.
Consequently, ES File Browser seems to be working now too. I guess it didn't have root access before.
rrvuhpg said:
Kernel seem to have full support but I don't know why you want to increase RAM, XA use zram as swap, you can change the size up to 1Go with a good kernel manager app. I don't know if you can move swap path Look at my screens if it can help you
Click to expand...
Click to collapse
That's awesome ! So if I make root and use good kernel manager I can extend total ram to 3gb total? Just asking for sure, had rooted all previous phones but still feel like 'noob' haha So if I already wasting Your time i wanna understand everything :>
edit: I wanna up to 3gb because some Hi-End games had low fps, 20~ and phone is hot as hell I can cook an egg on it ^^ for example ( CSR Racing 2)
I hope increase RAM can help a little, but maybe I am wrong :/ Maybe it's depend on CPU..
Rafixxxx said:
That's awesome ! So if I make root and use good kernel manager I can extend total ram to 3gb total? Just asking for sure, had rooted all previous phones but still feel like 'noob' haha So if I already wasting Your time i wanna understand everything :>
edit: I wanna up to 3gb because some Hi-End games had low fps, 20~ and phone is hot as hell I can cook an egg on it ^^ for example ( CSR Racing 2)
I hope increase RAM can help a little, but maybe I am wrong :/ Maybe it's depend on CPU..
Click to expand...
Click to collapse
Yes and no, by default zram is set to 922 MO/1000 on XA...
Hi-end games need a strong GPU like on PC, our Mali-T860 is not very good as mentioned in Antutu. You can tweak CPU governor or I/O scheduler for one or two more FPS and make your phone hotter a little more
Safer way is to tweak the game itself with GLTools app, results are not always good but it can help.
Edit: If you want to answer or have other questions please PM me to avoid off topic or open a new one for device/games tweaks

Categories

Resources