yashsingh1/xdaforums huggingface dataset:
[8525, TyTN, MDA Vario II, JasJam Accessories] Gyngabread Man:
i need just the board itself and if you have an extra one the lil wheel too. oh yea i forgot to mention that it would be for an cingular 8525 if that makes a difference
[Elephone P8000] liog:
Anyone can do a twrp for this device (or a porting)?
[Elephone P8000] elerraoind:
I am also curious to know! Let me know if you get to know please.
[Elephone P8000] liog:
Anyone can help us?

Inviato dal mio Elephone P8000 utilizzando Tapatalk
[Elephone P8000] SdtBarbarossa:
is there any sourcecode for this device?
[Elephone P8000] El_Nino9:
I understand you are using your phone.

on the first page on development, you will see a thread stating source code.

also there are other developers working on their own projects and making their code available via GitHub.

please search
[Elephone P8000] SdtBarbarossa:
sounds great :) but i was only able to find a kernrl tree... is there any device tree available? would need that for a working twrp build (or atleast some information about mountpoints and architecture )

maybe someone can give me a stock recovery.img ?
[Elephone P8000] micbanand:
here you go stock recovery from stock rom 09-09-2015

---------- Post added at 16:21 ---------- Previous post was at 16:14 ----------

here you go stock recovery from stock rom 09-09-2015

arh to big. link

https://www.dropbox.com/s/wf6acpiz8yhhuxa/recovery09.09.2015.img?dl=0
[Elephone P8000] pitrus-:
Check out Visi0narys device tree for P8000

https://github.com/visi0nary/android_device_elephone_p8000
[Elephone P8000] SdtBarbarossa:
thank you guys :) give me some time ^^
[Elephone P8000] El_Nino9:
[MENTION=3784300]BlueFlame4[/MENTION] is the owner of visionary i beleive. he's trying to do a lot for the device despite his busy schedule. i'm just happy to see more people trying to develop for the device.

also i'm glad BlueFlame4 is sharing his work. there are a few developers who aren't and i know the reason why. but this isn't the place for such things.

if you do get a TWRP running using his parts of his work i'm sure you'll give right credit. heck, i'm sure he'll appreciate the help if you can lend him a hand with CM lol.

good luck with your attempted
[Elephone P8000] SdtBarbarossa:
unfortunally i do not own this device! but look at my threads... not owning a device doesnt mean i cant help with twrp ;) atleast i will need you guys to test the stuff... visionary did a great job! he almost did 95% of the needed work ... and yes i will give credits.... and i will do pull-requests to his tree ( 1 is already there... its just 1 flag but its more meamt as a "symbolic" pull request that i want to help )
[Elephone P8000] liog:
Can you port twrp touch to elephone p8000?
[Elephone P8000] El_Nino9:
seen your message on the CM Recovery thread. owning the device will make life a lot easier surely?

i can see you work with xperia devices a lot. i wish you all the best with MTK device.

he said he'll try. why ask again :confused:?
[Elephone P8000] liog:
Sorry I'm not english, i don't understand good the last post [emoji3]

Inviato dal mio Elephone P8000 utilizzando Tapatalk
[Elephone P8000] SdtBarbarossa:
WARNING FIRST UNTESTED ALPHA!!!! TEST ON YOUR OWN RISK

- deleted .... buggy

so hereit is ...the first alphabuild... maybe someone experienced test it?

if it doesnt work you can find the stockrecovery.img above

if this works dont use it atm! just post a screenshot here to show me the color and grab the recovery.log to send me!
[Elephone P8000] tiltkoko83:
did not work for me. Black screen for a few minutes, then rebooted. Flashed with rashr
[Elephone P8000] SdtBarbarossa:
ok i need someone with the phone to adb pull me the recovery.log
[Elephone P8000] SdtBarbarossa:
i think it was because of a outcommented (#) boardconfig for recovery init by blueflame4 .... that one should work:

-removed
[Elephone P8000] liog:
It doesn't work... black screen then reboot
[Elephone P8000] SdtBarbarossa:
any recovery.log ? adb acess?
[Elephone P8000] liog:
I flash it with rashr

Inviato dal mio Elephone P8000 utilizzando Tapatalk
[Elephone P8000] SdtBarbarossa:
no i mean please check if you van grab a adb log ;)
[Elephone P8000] liog:
Sorry, i haven't an adb log

Inviato dal mio Elephone P8000 utilizzando Tapatalk
[Elephone P8000] SdtBarbarossa:
it would be really helpful if you or someone else could grab one for me ^^
[Elephone P8000] Baron1971:
Here can you see how to make useful Logs: KlickKlack
[Elephone P8000] SdtBarbarossa:
ok i have compiled a CM recovery from source (just to check if my build enviroment is ok) can someone check it? should work 100% (blueflame4 sources)

https://www.dropbox.com/s/mi11a28hjacdk2t/recovery.img?dl=0
[Elephone P8000] micbanand:
Flashed it with Rashr rebooted to recovery. But it stop at elephone logo.

Tryid from off. Went to bootloader choice. Recovery from there. Stopped there with elephone logo in background.

---------- Post added at 13:28 ---------- Previous post was at 12:48 ----------

is this adblog korrekt??
[Elephone P8000] SdtBarbarossa:
ok wait... i used wrong init.rc ....

try this one

https://www.dropbox.com/s/v5hngz1dykkrjrw/twrp-p8000-a3.img?dl=0
[Elephone P8000] micbanand:
is this adblog korrekt??
[Elephone P8000] SdtBarbarossa:
yes but that logs are from system...

have you tried the last build i posted above?
[Elephone P8000] micbanand:
no luck same as the other one

edit. cant get connection from boot. tells waiting for device. maybe I need another driver? I am on windows 10 x64
[Elephone P8000] micbanand:
log from nr 3 from system. but gues you cannot use it ?
[Elephone P8000] SdtBarbarossa:
if you boot it what happens?

if you have black screen,.... do you have adb acess?
[Elephone P8000] micbanand:
if I choise recovery. waiting

if fastboot. waiting

if normal waiting

cant get acces before eragon is loaded
[Elephone P8000] SdtBarbarossa:
no i mean what exactly happens if you boot the recovery? what do you see on phone?
[Elephone P8000] micbanand:
as I wrote I se the default boot mode. where I can choice. recovery. fastboot. normal.

when I choice recovery. the elephone logo pops up. but I am still in default boot mode. its like it frezes as the logo showes.

like normal. but like itfrezes
[Elephone P8000] SdtBarbarossa:
ok thank you much for testing.... have to have a talk to Blueflame4 before further buildings....
[Elephone P8000] micbanand:
No problem. Glad to test
[Elephone P8000] SdtBarbarossa:
seems like my build envirmoent is really infected.... blueflame4 will build a twrp with my changes on his enviroment... then we will see ^^
[Elephone P8000] El_Nino9:
i'm testing it out now. i have unlocked my bootloader so will fastboot flash, for some reason fastboot boot fails for recoverys i have tried.

i will edit this post with results.

i have some questions regarding builds for someone technical.

the kernel changed for the last 2 versions and elephone updated their source. visi0nary has kept up with latest source which is nice. eragon rom uses old partitions.

now the question i have is where are parameters set for locations of different partitions?

for example, sd card mounts changed between the version if i'm not mistaken. so if i try flash with philz recovery on the latest build, it doesn't see my internal card.

if adb is working on the recovery build i will pull log.

thanks for your efforts. as i said before, mediatek is a different can of worms compared to qualcomm. codeaurora helps a lot.
[Elephone P8000] SdtBarbarossa:
the builds dont work because somehow my enviroment is different from blueflames.... but i pulled my changes to his git and he will build a twrp with that soon (for real i guess the reason why my recoverys dont boot is in my build/core path... but lets not talk about that... )

if partition layouts have changed then you can grab me something so i have a look...

in android system you can do:

adb shell

su

fdisk -l /dev/block/mmcblk0

in recovery (cwm) you can do :

adb shell

parted /dev/block/mmcblk0

p

quit

exit

show me the result of both and i will fix philz for working with both...

and for your question:

partition mountpoints are saved in two ways:

1. fstab files ( for qualcom devices its simply qcom.fstab .... for mediatek its like mt657.fstab )

also twrp uses a own twrp.fstab wich uses another fstab version (its looking quite different from the others... i already created it... see source )

2. init files... some partitions (like trim area for semc flash devices [ xperia L ] are mounted in the init process ... also most /firmware or /modem partitions that are created from more then 1 partition ( modemst1, modemst2 ) are mounted in init files because they need some symlinks....

3. sdcards are mostly mounted in a combined way of both... they are defined in fstab and getting symlinked in init

( for example my xperia T ... it mounts the sdcard0 to /storage/sdcard1/ but for users wich are nonroot there is a symlink to /external_sd )

ok thats the answer to your question... and thats the simple one xD

Edit:

little extra :

they are 2 different ways to define a mountpoint....

lets say you have a partition that is named "cache" and is the 13 partition in table ...

then you can find the partition in 2 ways:

way 1 is the direct way

/dev/block/mmcblk0p13

way 2 is the platform way:

/dev/block/platform/mtk-msdc.0/by-name/cache

ok lets say the cache partition has changed position from 13 to 14 ... the way 1 will not find it (or you may even wipe a wrong partition )

but way 2 will still be compatible :)

ok but lets say the partition stayed on 13 but the name changed from "cache" to "Cache" (yes a uppercase)

then way 1 will still find the partition for both layouts... but way 2 will fail ...

at least way 2 is the SAFER way... because way 2 cant wipe or flash to a wrong partition

but if they did it like in example 2 then way 1 will carry compatibility for old and new partitionlayout...
[Elephone P8000] El_Nino9:
the issue's i'm getting are that when i select recovery from the bootloader, it goes straight into the rom.

when i adb reboot recovery from the rom it reboots back to the rom..

i have adb logcat waiting right after the reboot commands are sent. it just loads the system ones not the recovery ones.
[Elephone P8000] SdtBarbarossa:
yes... seems like i used wrong init again... will have a look tommorrow... may you try alpha 2 ?

https://www.dropbox.com/s/tm4n13guxrqmzy4/twrp-p8000-a2.img?dl=0
[Elephone P8000] SdtBarbarossa:
i would not backup/restore such partition until you know 100% for sure... also you need root to backup it... and root already change it...

thank you for aditional informations about table layout :) they are very useful for me ^^

(fdisk seems not supported in stockrom... parted is recoveryonly ... but your informations are good enought :) )
[Elephone P8000] El_Nino9:
i would back up but not restore lol.

you need root to back it up but rooting the device MIGHT not change it. only bootloader unlocking might change it.

you could obtain root with earlier versions easily without unlocking the bootloader.

i tried fdisk and you are right, doesn't seem supported. i installed busybox today but haven't had a chance to play.

i am unrooting now. but if you require help please let me know.
[Nexus 5 Q&A, Help & Troubleshooting] SekouCheikh:
Hello guys,

I actually wanna flash a factory image on my Nexus 5 which was on lollipop when it got water damaged. Well, actually the phone boots up well, but soon as it gets to the lock screen, the screen turns off and it's all back. So I'm flashing a factory room from Google's website as last alternative after cleaning and etc...

Now my simple questions are:

- Do I need to flash the same and exact stock ROM it came with on day 1? If so, how do I know which one was that?

- Or may I install any factory image from Google? Like Version 6.0.0 (MRA58K) Marshmallow.

Thanks to you all for your time.
[Nexus 5 Q&A, Help & Troubleshooting] Gbooye:
From what have learnt and seen.

You can flash any factory IMG supporting your phone brand . you don't have to go way back to how it started.
[Nexus 5 Q&A, Help & Troubleshooting] beekay201:
Like [MENTION=6334531]Gbooye[/MENTION] said, you can go straight to whatever you want, MRA58N for example.
[Verizon LG G3] Bad Mechanic:
I'm about to get a new LG G3 from Verizon (it won out over the G4 and S5 due to ease of root). Ideally I want to run the stock Lollipop OS with root with all updates frozen. Is that fairly easy to do? If so, how can I go about doing that? I'm been searching through XDA for a couple of days now regarding this, but it's akin to drinking from a fire hose. Any help would be appreciated.
[Verizon LG G3] cbrehob:
Post removed.
[Verizon LG G3] roirraW "edor" ehT:
Depends on what release of Android the G3 you pick up has on it. Don't take any OTAs once you get it. At worst, if it comes with 35B, the latest update - you can't root directly from it. You'll have to use the "return to stock" TOT method to downgrade to 10B. Find the "return to stock" thread in the General section.

What method you use to root depends on the same thing. If the phone comes with 12B, 23C or 24B you'll have to use one of the newer root scripts available in the General section of the non-variant specific G3 sections. If it comes with 10B or you downgrade from 35B, use the Stump app found on XDA with a search.

To install TWRP, if on 10B, just use TWRP Manager to install the latest, v2.8.7.0. I forget what you have to do on 12B. On 23C or 24B, there's two different versions of the "autorec" app you can get from the same section as the newer root scripts mentioned above. Install the correct one, give it superuser permissions, let it take 30 seconds to backup your stock recovery, then press the button to install an older version of TWRP. You can use Quick Reboot app from the Play Store to get into Recovery. From that version of TWRP, flash the latest version.

In the end, you can flash any of the three stock 35B-based ROMs [MENTION=2941286]xdabbeb[/MENTION] 's, [MENTION=5868929]hsbadr[/MENTION] 's JasmineROM 9.0+9.1 update, or [MENTION=1211160]HolyAngel[/MENTION] 's SkyDragon 6.x. Follow the instructions exactly in any of their threads.

---------- Post added at 12:13 PM ---------- Previous post was at 12:12 PM ----------

I've been told that buying/selling on XDA is against their rules, even via PM.
[Verizon LG G3] Bad Mechanic:
Is it possible downgrade or upgrade (depending on which version the new phone has) to 24B, rooting it, and leaving it as is?
[Verizon LG G3] roirraW "edor" ehT:
Yes, although 35B runs a lot better than 23C and 24B. If you did want to be rooted on 35B, JasmineROM is very minimally modified from stock, especially if you don't flash the debloat zip.

If it comes with 35B, you'll have to do as I say and downgrade to 10B first using the TOT method, then you can upgrade to 24B and root, or whatever method you're going to take.
[Verizon LG G3] PiousInquisitor:
Yes. But there is no advantage to doing so. 35B > 24B by a longshot. And Jasmine 9.1 is stock 35B rooted. Save yourself some time and trouble and flash that.
[Android Q&A, Help & Troubleshooting] AeiT:
Over past few years i'm expecting many issues with my android phones ... over time they became laggy and completely useless without our endless system modifications.

What i'm trying to tell is simple and easy ... fones gets older and dies no matter what. Why is that? At this moment my excellent Xcover 2 (phone for hard works) is experiencing terrible battery burn. Its rooted and always was running on stock setup, with link2sd. Over past few weeks android KERNEL started to drain whole battery. Over day he uses average 36-64% battery capacity. I have tried everything uninstalling all my apps, working on old gaaps. Also installed GSam monitor and other similar monitors. Over all my battery condition is perfect ... but kernel itselfs can easily kill phone overnight.

I know that maybe reflashing new rom could fix the problem but its same as windows ... you can't fix it? restart ... still nothing? restart again and then reinstall.

Its boring and terribly annoying. I won't give up.

Today i had idea to reflash only kernel form my present working stock rom.

So i extracted tar.md5 get the boot.img and converted it into tar (trollfactory .bat) then i flashed it using odin and ... it got stuck at checking writing Nand.

Of course this bricked my phone ... but i restored it. Can't do it using adb because using adb bootloader doesn't work, also my devices can't run in fastboot mode.

Situation is still the same ... what should i do ...

-$ Please don't move this thread to xcover section ... nobody will notice it there ... and i strongly believe that applies to every device (since my new s5 still have no issues lol)

and there's still no solution on that.
[Android Q&A, Help & Troubleshooting] ivobrzi:
Hey guys,

I've been trying to root my Lenovo Vibe X2 for some time now it is running android 5.0. I've tryed Framaroot, iRoot, Kingo root, Kingoapp root, Rootgenius and so on but none of them worked for me. Does anybody know how to root it successfully? :confused:

Thanks for your answers in advance :)
[Android Q&A, Help & Troubleshooting] elabjer:
S223 is the last fw that can be rooted ATM
[Sony Cross-Device Development Themes and Apps] sanjoy mahata:
A simplest method of create theme on any rooted Xperia devices as below

1.Open ES File Explorer

2.Go to Local > device >vendor >overlay >framework

3.Copy any theme what u want to change

4.Rename as BlueTheme.apk >BlueTheme.zip

5.Open zip file >select all >Extract

6.Open file BlueTheme >res >drawable-hdpi/mdpi/nodpi/xhdpi/any device

7.Delete semc_bg.png >Replace any image with -same resolution >rename semc_bg.png

8.Same drawable-land-mdpi/...

9.Back >select all(5) files >compress >rename >BlueTheme.zip -BlueTheme.apk

10.Copy to device/vendor/overlay/framework.

Automatically reboot

Best of luck

:D:D:D
[HTC One A9] fred_be9300:
Post here your findings with the A9 in daily use; or discuss methods to improve battery life (settings, etc)

How much screen-on time do you get? How long does your battery last through the day, with what type of usage?

Mention also your ROM version pls.

If possible, post screenshot from GSAM or similar app.

inspired by similar thread for the M9 here: http://xdaforums.com/one-m9/general/battery-sot-t3067585

ps: I am in the process of chosing a new phone, which could very well be an M9 or A9.
[HTC One A9] polarbee:
I'm generally a fairly heavy user and I've been very pleased so far with battery life. This phone and OS have so far been much better at preserving battery when asleep and it charges much faster even from standard chargers.
[HTC One A9] jaypeg123:
Well I am more then pleased, and if you use the phone as a game console only and watch videos, then it uses more power, but it is a phone right?
[HTC One A9] fred_be9300:
Thanks for replies. If possible, please post numbers (screenshots appreciated).

E.g. how much screen on time in a day, how much % left when going to bed without recharging all day.

+ add ROM version, whether 2gb or 3gb RAM...

you know, the essentials to make comments comparable. :)

Personally I am still on a 2.5y old One X+ that I want to replace. I don't game but need about 4h SOT (browsing, social apps, ...) without recharging. Today, I need to recharge every day during the day, and I want to put that behind me. In gsmarena battery test, the One A9 scored barely better than the X+, and worse than M9. That has me worried.

/ Updated to add: I also need all day mobile internet on 3g/4g, and 1 hour streaming radio (tunein radio app) with screen off). Maybe in future all day bluetooth for a connected watch? /

Cheers
[HTC One A9] jaypeg123:
If so then you will be fine with this phone,
[HTC One A9] fred_be9300:
Thx. I updated my requirements though. I'd been too brief :)

besides, this thread is meant to collect data from many users, to provide usage examples to all potential buyers :)
[HTC One A9] muhammaf1992:
From my experience my a9 battery usage is impressive when the screen is off, but when the screen is on it's worse than hTc one M8

in the M8 the SOT I got is between 5 to 7 hours, and in my new a9 the SOT is 4 to 5 hours per full cycle!

this 4 hours screen I used them in 1 day and half, with all time wifi and sometimes 4G Data when I go out.

I will post Gsam battery stats in the next couple days.
[HTC One A9] cpurick:
Marshmallow's doze mode works as advertised, with seemingly infinite standby times. But there's only about four hours of SOT in the tiny battery, maybe almost five if you're miserly.
[HTC One A9] jollywhitefoot:
That's about like my M9, which is what I expected with the A9. M8 was way better on battery than the M9.
[HTC One A9] cpurick:
810 is a battery hog. All that heat is wasted power.

But there's no excuse on the A9. Anybody could tell you a 2150mah battery isn't gonna last long. Would it really have been that big a deal to make the phone 2mm thicker and put a 2500 in it?
[HTC One A9] jollywhitefoot:
Yeah, I agree. Personally, I would rather a phone the same size and the M9, with a 2840 battery, but with the 617 proc. But I'm probably not exactly who HTC was targeting with this device, either.

I was just saying that I think HTC decided that if the A9 battery performance matched the M9 then that was good enough. Once I faced fact that the M8 performance was a thing of the past, the M9 has actually been decent for me, using a custom Rom and flar's ElementalX kernel.
[HTC One A9] muhammaf1992:
Sam battery state

here's a picture with Gsam battery monitor for 1 full charging cycle

[IMG="Battery consumption for htc one a9"]http://s28.postimg.org/qrhq21ulp/Screenshot_20151113_213016.png[/IMG]
[HTC One A9] jkd12589:
Day 1:

I unplugged my A9 at 7am.

3 minutes of scrolling through facebook. Then drive to work.

7pm the phone vibrates and tells me I have 15% battery life.

I made 4 phone calls all less then 5 minutes. Turned the screen on maybe 10 times to do a time check. And spent a good 15 minutes on break scrolling facebook.

12 hours of almost non use...

Then the fast power dump came.

My 20 minute drive home it went from 14% to 2%.

This is crazy.... I may have to return this thing and get my M8 back.