yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] alba81:
Hi devs,

hoping on help of people who better know about this materia than me, I hope to create a workaround for OTA repair on faulty Iconia B1-A71 from Acer.

In this case we need devs who has knowledge about stock JB and also testers, who has a B1 with problems on installing OTA Updates with "Invalid partition settings" on FAT.

Status:

More and more user of B1 report the problem of updating their device by OTA. It appears to be a mass problem, which Acer has no solution for.

After checking on rooting issues we already know, that there is a difference in dumchar_info between "normal" and "faulty" B1´s:

Android Partition:

http://xdaforums.com/showpost.php?p=40987372&postcount=197

Normal - android 0x0000000026500000 0x00000000020e8000 2 /dev/block/mmcblk0p3

Faulty - android 0x0000000015e00000 0x00000000020e8000 2 /dev/block/mmcblk0p3

Furthermore there is a difference (and this I assume is the problem for OTA routines) on FAT partition:

Normal - fat 0x0000000148638000 0x00000000882e8000 2 /dev/block/mmcblk0p6

Faulty - fat 0x00000001b0a38000 0x00000000232e8000 2 /dev/block/mmcblk0p6

Those who was in charge of rooting the B1 knows, that we have dumped the android partition by dd using the offset shown in dumchar_info.

In this logic it would be impossible to dump a faulty B1 system.img by using the normal offests - you would not "meet the partition/bits", if you use wrong data.

BUT - as we found out it was possible to dump the system.img from a faulty B1 using the offset of a normal B1! User agentdeep confirms a successful root from scratch on Linux base using the normal offsets: http://xdaforums.com/showpost.php?p=40988791&postcount=202

Now my idea:

- According entonjackson pawitp already assume, that the dumchar_info may be wrong, since otherwise agentdeep would have a bricked device. IF we can proof that OTA checks this value - would it make sense to push a corrected dumchar_info through the ENGMODE backdoor? Anyone out there, who is able to save and extract the OTA, to see the routine?

- If it dont work, does it make sense to try a root from scratch on Linux - and fix the dumchar_info afterwards? Is it possible?

- How can I check a report of existing partitions on Android? Do I have to run busybox from terminal, to start fdisk? I would like to validate the partition information inside the dumchar_info...

This subject may be not as hot as a rooting thread - but more and more user report their problem with update errors, and we may help lots of them ... and show Acer, how this work has to be done... :D

Thank you in advance!
[Android Q&A, Help & Troubleshooting] agentdeep:
Sub.

I would like to try that procedure enton asked me by replacing 15e to 265 in dumchar_info. But knowing there is no way I can restore my nandroid backup if something bad happens, I will hold for now :D
[Android Q&A, Help & Troubleshooting] alba81:
Nice to meet you here, agentdeep :) I was hoping you will join this thread, since you are the one who made me thinking about this solution...

From my point of view the risk of bricking the tab after changing the dumchar_info is ... pretty low. As long as we have a working system you still can switch back to your origin value. But at that point I would also like to get some more background from the Linux masters in here. Currently I have a problem to understand about the dumchar_info - what is it? How it is created? Do I understand right, that it is an output from Linux kernel?

When this file is accessed? On boot? Which result we will have, if we change it? Is it a properties file, used to set up partitions - or just an info? IF it is only an information we can change it without any fear...
[Android Q&A, Help & Troubleshooting] alba81:
https://github.com/ameer1234567890/...To-Gather-Information-About-Partition-Layouts

This page gives us the information, that "fat" is not just the format - it is the internal memory on MTK based devices. Which finally gives me more inscentive to believe that we have an issue with 8gb and 16gb versions. On that I have seen a thread in a different forum, where a user reported to have opened the B1 and found out that there were 16gb internal memory instead of 8gb as shown in the device properties.

Probably we have "masked" 16gb-versions declared as 8gb???
[Android Q&A, Help & Troubleshooting] entonjackson:
1st, thanks for the thread! It's really been time to create one for this issue.

I will put a link on the 1st post of my thread to this one, for people experiencing this issue.

Regarding agentdeep, I also think changing the dumchar_info won't brick the device. But we should first make sure it won't brick.

Although I'm using Linux for like 10 years now, I cannot help a lot at this moment.

But if there will be a solution, I will put it immediatly into my toolkit ;)
[Android Q&A, Help & Troubleshooting] alba81:
So, I made a small calculation for the offsets, and this seems to confirm a wrong information in the dumchar_info:

Normal B1 Offset Android size:

Hex: 26500 Dez: 156928 Multiplied with 4096=642777088 Divided by 1024 = 627.712kB

Faulty B1 Offset Android size:

Hex: 15e00 Dez: 89600 Multiplied with 4096=367001600 Divided by 1024 = 358.400kB

If you take into consideration, that the system.img.gz takes (in packed form!) about 350 MB, unpacked even 627,712kB (size of the parition, see above) - then it appears that the information MUST be wrong - if I am right with my calculation...

Following this we have these values for internal memory on both versions:

Normal B1 Offset FAT size:

Hex: 148638 Dez: 1345080 Multiplied with 4096=5509447680 Divided by 1024 = 5.380.320kB

Faulty B1 Offset FAT size:

Hex: 1b0a38 Dez: 1772088 Multiplied with 4096=7258472448 Divided by 1024 = 7.088.352kB

Anyone with 15e can check available space on internal memory? In fact it should be about 5GB as I remember (have the B1 not with me now).

Maybe I am writing complete bull**** here? Anyone can confirm my calculation..??

Thanks in advance!
[Android Q&A, Help & Troubleshooting] entonjackson:
Yeah internal space is 5.12 GB like posted here in bullbrands post:

Note: this is after swapping internald and external sd...

The calculation looks good, but i don't know why the f... you multiply with 4096 and divide by 1024... I'm working as a developer and now I really feel stupid, because I really just don't know.
[Android Q&A, Help & Troubleshooting] alba81:
Dont worry :) I could explain as follows: 4096 is the qty of bits you write at once on dd, and 1024 - logically to convert bits to KB.

Well, so we see that nothing is right in the dumchar_info, at least on Android and FAT partition, on faulty B1´s. Now we know there is a mistake - and need to validate the right offsets. Anyone has experience with fdisk on Android? Do I have to run it from busybox from terminal emulator?

And can anyone experienced tell us the specifications of dumchar_info? I found out it is a MTK-own chart, which is not existing on other CPU based devices .... which means for me - it can not be that critical in regards to format table, right?

On a rooted device - can we use a log to see when the dumchar_info is triggered?
[Android Q&A, Help & Troubleshooting] entonjackson:
Ah I see. very easy. so bs=4096 is blocksize and well ok 1024 I already guessed could be convertion from bits to bytes. alright.

Then I would say, yes. the calculation makes sense indeed.

Now we only need someone that tries to write the right parition info into dumchar_info.

volunteers hands up! :victory:
[Android Q&A, Help & Troubleshooting] alba81:
The biggest problem on that point is - you need to have either root, or do it by obtaining "temporary backdoor root" through ENGMODE. And the qty of user having root on faulty B1 is still pretty low...
[Android Q&A, Help & Troubleshooting] entonjackson:
i know busybox has fdisk binary.

adb doesn't know fdisk?
[Android Q&A, Help & Troubleshooting] alba81:
Where can I call it thru ADB?

Starting busybox from internal memory thru Terminal Emulator also makes me problems ... permission denied.
[Android Q&A, Help & Troubleshooting] entonjackson:
There is none. I thought fdisk comes with adb, but... no.

But maybe we need no fdisk. If i understood it right, wie only must edit the dumchar_info so the system "believes" it has the right partitions again.
[Android Q&A, Help & Troubleshooting] alba81:
Yes, obviosly the update process checks this value. As you already checked the /proc/emmc shows different values, and /proc/mtd is empty. /proc/partitions contain different information type.

Before changing an important value I think we need to validate that any change in dumchar_info remains after reboot, since the update failure notification appears in recovery mode during update - right?

Edit:

I do not get access to dumchar_info. Going through ES File Manager I set the properties, and even it shows after changing its saved - its not. How can I get the rights? And how I can take the rights for system away to not be able to access it any more? Each time I open the properties of it I see a different date ... is it in permanent access?? Or do I need a different file Explorer?

Edit2:

Wikipedia is my friend. Ok, now I know - dumchar_info is a procfs, generated by the kernel during boot and not saved. So I am affraid ... we are stuck on a faulty kernel issue?

Where does the kernel gain this Information from during boot? Anybody an idea?
[Android Q&A, Help & Troubleshooting] agentdeep:
I hope this helps
[Android Q&A, Help & Troubleshooting] alba81:
Thank you - I will validate later on, once I am at home ... have now only my n8000 with me.
[Android Q&A, Help & Troubleshooting] alba81:
Ok, checked - my version is the same, except:

marsl_lin@BM-1 (after Linux version 3.4.0)

which I think can not be that important, since all other release data is similar. So it is not the kernel we have to fight with - at least...
[Android Q&A, Help & Troubleshooting] alba81:
Ok, so following on this subject we need to see what comes up in the future:

http://xdaforums.com/showpost.php?p=41168837&postcount=295

At least the reason seems to be confirmed from Acer site - a faulty format which is reported.

IMHO it can not be only the update with the problem, the device itself reports a different format in dumchar_info, not the update.

Well - we´ll stay tuned...
[Android Q&A, Help & Troubleshooting] Leach79:
hi there,

i have a faulty B1 with root....also i tried the Factory Reset Workaround several times, it does not work for me....everytime about 10-15% i got the message "partition error...bla".

So if you want me to to test things...go on :)
[Android Q&A, Help & Troubleshooting] 007.4:
I'm new here, however I successfully rooted my device using the "toolkit" even though I have

Faulty - android 0x0000000015e00000 0x00000000020e8000 2 /dev/block/mmcblk0p3

Thanks to Enton.

My internal storage is reported to be just 5.17GB (not 8GB as expected) confirming the figures in a previous post.

I complained to acer support about the size of the internal storage being nearly 3GB short of what it should be and that I thought it was down to a "memory allocation error".

There response was " As you have mentioned in the previous e-mail internal storage shows as a 5.17GB, I would like to inform you that the other space of the unit is occupied by Android Operating System, customer will not be able to use the complete 8GB from the unit, as Operating system needs a space. "

Is this complete and utter BS? I understand 4.1.2 Jelly Bean is just over 200MB.

Can someone please confirm.

BTW if any dumps are required from my "faulty" device (I do not have the partition error though) I'm happy to try.

BTW2 I've installed the new PMTUpdate patch "FixG1PMT" and that did nothing for my problem.
[Android Q&A, Help & Troubleshooting] 007.4:
I've just checked my dumchar_info file and it is now showing the correct value for android

Normal - android 0x0000000026500000 0x00000000020e8000 2 /dev/block/mmcblk0p3

How can this be? According to the discussion above this should not happen?

My Internal SD is still reporting "Total Space 5.17GB" and this is the FAT partition size

fat 0x000000014BA38000 0x00000000882e8000 2 /dev/block/mmcblk0p6

This is different to those reported in first post.
[Android Q&A, Help & Troubleshooting] manepape:
Need help

I had rooted my acer icobnia b1 A71 .Now I can't access recovery mode .It goes off after shoosing [SD image Update Mode] <<== .
[Android Q&A, Help & Troubleshooting] vali stan:
Acer launch Iconia B-710 :(

Sent from my B1-A71
[Android Q&A, Help & Troubleshooting] Wild78:
Hello guys.

In my situation I cannot boot the tablet and got stuck at acer logo...

While I try a recover Wipe does not fix it and New firmware upgrades welcome me with the Invalid Partitions Settings...

I was thinking that maybe in the Firmware Zip file being that an OS filesystem I could change something manually to overcome this issue but got stuck.

What would you suggest ?

Thanks
[Android Q&A, Help & Troubleshooting] jac1502:
as well

I am in the same boat, any help on a bricked B1-710
[Android Q&A, Help & Troubleshooting] jac1502:
Help Please

Bump I need to unbrick 2 B1-710s
[Android Q&A, Help & Troubleshooting] polswell:
hello friend, you could solve the problem of stuck on logo of your b1a71?
[Galaxy S 4 General] jaidev.s:
Dear moderators , will it be possible to make two separate forums for I9500 and I9505? Now everything is mixed up and hence it's very easy for people to get confused and flash wrong mods ,ending up in bricking their phones . With S3 we had separate threads for 9300 & 9305. So please consider making separate forum/thread for 9500&9505 if it is possible.
[Galaxy S 4 General] DjeMBeY:
AGREED!!!

Something must be done.... sooner or later.... better sooner as it's less work for MODERATORS to move all this c**p around... ;)

General Section can stay as ONE for ALL but DEVELOPMENT.... it MUST be DIVIDED!!!

As you said, many people WILL Brick their devices ONLY because we have all MIXED together ...

It's just my PERSONAL and Honest opinion though.... ;)
[Galaxy S 4 General] CLARiiON:
Not a bad idea..
[Galaxy S 4 General] mackann:
yea it would help alot
[Galaxy S 4 General] joelvn:
I support this, it would be way easier to find things especially for your phone!

Flowed from my GT-I9505 using xda-developers app
[Galaxy S 4 General] tryerxda:
I agree.

Makes a lot more sense to keep things organised.
[Galaxy S 4 General] Wiley87:
+1
[Galaxy S 4 General] Higgins12:
Yep good idea otherwise we'll soon see first threads of people who flash the wrong ROM for their device. Oh well on the other hand we'll see those threads anyway

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 General] rinxas:
+1 otherwise we'll see a lot of "bricked my phone" posts on the Q&A section
[Galaxy S 4 General] inolvidable:
+1
[Galaxy S 4 General] cat_baxter:
Agree, please.
[Galaxy S 4 General] rmwolf:
+1
[Galaxy S 4 General] tietherope:
Could the Canadian I337M also get placement somewhere? Whether it be with the AT&T version or alone? Thank you.
[Galaxy S 4 General] no_use_for_a_name:
+1
[Galaxy S 4 General] BoostedSR20:
This.
[Galaxy S 4 General] jay7862:
Please

This is needed urgently.
[Galaxy S 4 General] harise100:
+1
[Galaxy S 4 General] dondavis007:
Yes please!

Skickat från min GT-I9505 via Tapatalk 2
[Galaxy S 4 General] sqnz:
+1

+1

Great idea!
[Galaxy S 4 General] benni_1994:
+1

Would be great!
[Galaxy S 4 General] Jeshter2000:
+1000 needs to be done ASAP...

Sent from my Octaaaa! Gt-I9500
[Galaxy S 4 General] E.Cadro:
The Samsung international moderation team is discussing this.

XDA Moderator
[Galaxy S 4 General] xHausx:
What he said ^^^ :)

Things like this may take awhile to make sure we get everything right, but in the mean time please use the previously created thread to help keep things more organized.

http://xdaforums.com/showthread.php?t=2263500
[General Questions and Answers] slmnshq25:
Hi i seriously need your helps i just rooted my android and the formated cache,partition. now my phone is not booting up just shows the logo. I have a similar phone with me so if i root it and take a backup file and can i restore the same files in my phone will it work,

Or is there any other ways to do that.

My phone is Huawei U8185
[General Questions and Answers] kreatonn:
Back to stock,, and what phone u have??? Please be more details....
[General Questions and Answers] GTIM2L8:
Here is a thread for your phone that lists just about anything you need.

Just read through it and select the proper ROM and try reinstalling before you do anything to your other phone.

http://xdaforums.com/showthread.php?p=28201813

this should help you get your phone working again.

I also found another thread that mat help:

http://xdaforums.com/showthread.php?t=2118463
[General Questions and Answers] freakboy13:
Edit: sorry posted in wrong section mods delete comment if need be
[General Questions and Answers] Mr.crowbar:
If you have some sort of recovery on there, I suggest you wipe and flash a stock rom. Then figure out what went wrong.
[Galaxy S III Themes and Apps] winuxguy:
Hi ALL!

Ever wanted to have a real bass boost effect on your Galaxy S3 GT-I9300? Sure you have heard off beats bass mods but have they ever worked for you?

So far, I have been tinkering around on Sony Audio effects mod, Beatsbass mods and none of them gave me the best bass boost I ever wanted until I tried using this one small library and audio config. I have created a flashable zip for this so just flash it via clockwork recovery.

Requirements for Your Satisfaction:

- Android default MusicFX

- Google Play Music app

- Remove other soundfx modifications

- Stock kernel (may work with other kernels but not tested)

- Stock ROM (may work with other ROMs but not tested)

- Android Jelly Bean ROM(really, who still uses ICS on S3 GT-I9300?)

Whats Diff/New:

- 6 Graphical Equalizer for frequencies: 15Hz, 62Hz, 250Hz, 1kHz, 4kHz, and 16kHz

- Lower and "real" Bass Boost effect

Compromises:

- No presets available. (You may try the settings I have in the screenshot)

- 3D Effect is not as cool as SRS but stereo range is wide on this mod. (the 3D effect only adds echo. The reason for that is to make sure that the bass boost is not overpowered - not sure if that is right description to it.)

Ever since I discovered the rich bass boost plus clear audio on this mod I made, I have been listening to music all day with my S3 plus an Audio-Technica ATH-SJ33 headset, I felt like I have the whole 5.1 Sound System in my head.

Hope you'll love the effects.

Added Android JB 4.3 version.

Fixed the Android JB 4.3 version flashable zip file.

Added support for Android KitKat 4.4 version.
[Galaxy S III Themes and Apps] winuxguy:
High Quality = High Quality

And yes, you'll need a headset/earphones that can handle low frequencies like 5-10Hz with high tolerance as this can relatively damage "cheap" headsets.

WARNING: Do not expose your ears to very high volume with this mod for a very long time.

Or your ears will explode!
[Galaxy S III Themes and Apps] AngryB:
Can you make this for CM 10.1?
[Galaxy S III Themes and Apps] Destroyedbeauty:
Using this on UltimaROM 12.0.1 and playing modern swedish death metal with low end frequencies at pretty high levels (not selfdistorted but close) is freaking enjoyable thru my Koss headphones. Good work, dude! You gived me an reason to get some extra boner from now on.
[Galaxy S III Themes and Apps] winuxguy:
Thanks for the feedback.

Good to hear that it works and I'm glad your happy with the result. Koss headphones are also good (I have their prodj100). Thanks for the feedback... :D
[Galaxy S III Themes and Apps] winuxguy:
Try it and write some feedback

Hi AngryB feel free to try it on your present CM ROM and just make sure you backup. Destroyedbeauty has tried it on a non-stock ROM and it worked great for him.
[Galaxy S III Themes and Apps] Destroyedbeauty:
Oops, dude.. UltimaROM is an stock based ROM with AOSP look :D
[Galaxy S III Themes and Apps] winuxguy:
Oops, my bad.
[Galaxy S III Themes and Apps] sardr2d2:
Tried on Omega 4.1.2 JB.

It works, but I dont have the equaliser settings. But nvm. More bass is always welcome. :laugh:
[Galaxy S III Themes and Apps] jinosong:
Does this work with Bluetooth headphones also?
[Galaxy S III Themes and Apps] Gorgtech:
Nice Mod but this one can´t compete with AndiP´s Boeffla Soundengine :good:
[Galaxy S III Themes and Apps] winuxguy:
I haven't tried but feel free to try. I only use wired headset for music to get the highest quality...:)
[Galaxy S III Themes and Apps] winuxguy:
Thanks for the feedback.
[Galaxy S III Themes and Apps] winuxguy:
You need to have the android default musicfx.
[Galaxy S III Themes and Apps] winuxguy:
Works great with the leaked 4.2.2!
[Galaxy S III Themes and Apps] furiify:
Tried to install it via TWRP on my null_ rom running with Siyah Kernel.

TWRP told me the installation was complete but I can't find anything on my smartphone?

Seems like it didn't work.

But even tho nice work :*
[Galaxy S III Themes and Apps] maxibat92:
Does this work with the 4.3 stock android version?
[Galaxy S III Themes and Apps] r.fans:
Does it works on 4.4.2?
[Galaxy S III Themes and Apps] winuxguy:
Unfortunately not. I'll try to see if I can make it work on 4.4.2.
[Galaxy S III Themes and Apps] winuxguy:
Doesn't work on 4.3 either. I'm sorry to disappoint you guys...
[Galaxy S III Themes and Apps] Jacker75:
i9305

Is it compatible for i9305?
[Galaxy S III Themes and Apps] winuxguy:
I can't say for sure as I do not have the device to test. Create a NAND backup and test it but please make sure you are installing the the one for JB 4.3 if you are on 4.3. This may not work on KK 4.4.2 yet.
[Galaxy S III Themes and Apps] winuxguy:
I've added a version that works with JB 4.3. Be sure to do a NAND backup before flashing. ;)
[Galaxy S III Themes and Apps] JyRo:
Softbrick

Second zip attached will cause Softbrick -_-" coz it will overwrite your build.prop with only one line

WARNING!!
[Galaxy S III Themes and Apps] winuxguy:
I've fixed that now. I am very sorry mate.

Cheers!
[Galaxy S III Themes and Apps] winuxguy:
Android 4.4 support added

I now have a working mod for Android KitKat version. Please let me know if it works.
[Micromax A116] kumar abhishek:
MIUI 5 V3.7.26 Latest​

Extra Features :

-> New Baseband

-> Faster And Smoother

-> Pre-Rooted

-> busybox

-> Performance Tweaks

-> Faster Streaming

-> Net Speed Tweaks

-> No Delay In Making Call

-> Battery Tweaks

-> Proximity Tweaks

-> More RAM Free

-> Signal Tweaks

-> Better Responsiveness & Speed

-> Enabled 270 Degree Rotation

-> Ziplagined and Deodexed

-> AD Block host by default

-> Gps.cofig added

Download : https://mega.co.nz/#!8UV0iI6C!HgVfO0AEGa6cEOVmMhewfVu0xbgmVi8C0Z0pVzLal8Y

Bugs :

1. Only First Sim Works As Data.

2. SystemUI Fc On Reboot. Dont Panic and Bypass It.

Kernel Sources : http://yadi.sk/d/fmIOi_ee6ADpi

How To Flash :

( You Can Take CMW Backup for Revert back to your old system )

1) Download Rom.zip File

2) Put into External/Internal SD Card

3) Go To CMW Recovery

4) Wipe Data/Factory Reset And Wipe Partition

5) From Advance Menu Do Dalvik Catch Clear

6) From Advance Menu Do Battery State Clear

7) Go in Mount And Storage select FORMAT SYSTEM

8) Select Intall From SD and Select File And Click YES

9) Select Rom.zip And Select YES

10) SystemUI FC once. Dont panic :)

Update Log :

06/05/2013: Announced V1

21/07/2013: Announced V2

27/07/2013: Released V2

Credits:

Base Rom- Amoi N828 Devs

Testing, Screenshots and Much More - Mohammad Abdul Sajid

Declaimer :

I Will Not Responsible For Any Brick or Any Problem So Flash At Your Own Risk.

Thank You.

Press Thanks button if I helped!! :D
[Micromax A116] kumar abhishek:
Changelog : ​

V2

1. Stable Release

2. 4.2.1 Based

V1

1. Initial Release
[Micromax A116] kumar abhishek:
Reserved For Patches
[Micromax A116] djkrish5610:
Screen shots & features !!!
[Micromax A116] kumar abhishek:
Screenshots posted

Features -miui :P
[Micromax A116] mohsin2cool:
Thanks for ur work ,much appreciated

Sent from my Micromax A116
[Micromax A116] Anands3:
it is based on 4.1.2 so performance of this ROM same as jellyxperia?

Jellyxperia is Benchmark for A116..:laugh::laugh:
[Micromax A116] mohsin2cool:
link plz