yashsingh1/xdaforums huggingface dataset:
[Android General] Charles IV:
ok

Well, about my situation ...

My dad tried mobile upgrade on his computer, which runs windows, and it took 2 days, but it worked.

The only bad thing is that it's running 4034G rather than 4034X (probably because the cm13 port i was running was 4034G), but it's working fine.

I guess this marks the end of my development for the 4034X, they probably wont trust me to flash cm again, complaining that i broke it.

I'll like to take a backup for this thread, and pull a few things for my own satisfaction etc. that you can have as well.

edit - it's looking less like stock by the second - more like some ported stock, rather than an official oem build, especially is ive now looked at the build.prop

edit:

/system folder: androidfilehost - interesting, the build.prop looks incorrectly configured

twrp backup: androidfilehost - also interesting, the rom is fro the 4034G, the recovery is for the 4034E, just as the one here is, and adb doesn't work, just as the one here! and this is straight from mobile upgrade tool.

If restoring from the twrp backup, tell me if it doesn't work, because i deleted the three data files afterwards. [MENTION=5515628]kirito9[/MENTION] i don't know if your going to be able to use any of this ... but shout if you would like anything else.
[Android General] rayden221:
Does this work for Pixi 4 Plus Power (5023E)?
[Android General] kotla85:
Pixi 4 6 (3G) 8050D TWRP bootloop

I tried to install CM12.1 ROM on my 8050D phone and I stuck by TWRP: Factory Reset / Wipe Data / Cache / Dalvik (image)

Then I rebooted my phone and since then the Alcatel logo appears, than TWRP and the phone reboots again and again (message from TWRP)

I know that I might not have been forehanded, but I can see that there's an SPFT ROM for my 8050D device, is there any chance to load it into my device or to fix this bootloop? --> video

I also tried Alcatel Mobile upgrade tool, but there's an error message: link

thanks everyone!
[Android General] Charles IV:
Try resizing, repairing, changing come system of data (do all three, different orders etc) beware you will lose all data.

I'll have another look later with more ideas.

Edit - from the video, it looks like the os isn't correctly installed, which I had as well. Try the data tricks above, then spft / mobile upgrade tool, keep trying different things, maybe you have a twrp backup you can restore?, Maybe try only restoring bits?

Try different things, but first the data things I posted above.
[Android General] HOLIVUD:
Front Flash not working on 5045X model. Little slow but everything fine.Thanks

---------- Post added at 08:36 AM ---------- Previous post was at 08:34 AM ----------

Front Flash not working on 5045X model. Little slow but everything fine.Thanks
[Android General] Charles IV:
cm13 to test on 4034

Can anyone with a 4034X or similar test a new cm13 build for me?

Although i now can't test them myself, my 4034X is now essentially stock, so im comparing it, and still trying to fix things.

In my new build, i hope to have fixed the issue i had with the sim card. Having a look at the stock build.prop, ive made a few edits. I would be really grateful if someone could see if it works.

I would recommend making a full twrp backup first, so you can completely restore afterwards.

the usual disclaimer stuff applies, but the rom is on androidfilehost

edit- i didn't really explain the issue well did i? basically, before, the sim card wasn't detected, even when it was inserted properly, so if someone could backup, flash, see if the sim card is detected, then either stay and find the other bugs, or restore the backup.
[Android General] Ruffypp:
mate,i thinks that the same issue on cm13 5045 version,,what did u edit on your buildprop,sory for asking mate,

---------- Post added at 11:02 AM ---------- Previous post was at 10:59 AM ----------

didnt u hv any issue on unknown baseband?,, is that rom detect ur sim card?,, i hav flash that rom before,but my phone not detecting sim card because of unknown baseband version
[Android General] vetooo3001:
any news about root 9001d
[Android General] drmad:
I'm able to root 9001d with twrp, but Ithe recovery Is not very stable and i'm trying ti improve it
[Android General] Charles IV:
Because my phone is single SIM, [MENTION=5515628]kirito9[/MENTION] and I changed the dual SIM lines to single SIM. Having a look at the build.prop, I reverted these changes to dual SIM, and added a line so settings only displays single SIM. I will find the commit on github and edit this post with it.

Edit - here's the link: https://github.com/Charles-IV/andro...mmit/148672b4c967e2114551382a6814e5982a8aff52
[Android General] Mariustiberius:
i want to root my alcatel pixi ( 5010x) and i was try with twrp (for 5010) finished with bootloop , now i instaled again stock rom , so who know working twrp for 5010x model , ?
[Android General] Ruffypp:
hv u try rooting using kingroot friend?

---------- Post added at 12:16 PM ---------- Previous post was at 11:56 AM ----------

if i own that 4034 version and im ready to test your work,, :( im using 5045 version,and i hope any dev wants to fix that baseband issue on 5045 custom rom,
[Android General] BoC4RDi:
Hello, i recovered my phone... (pixi 4 4034 e)

Installed the "custom stock" rom from your link (4034a)...

Working fine, but it's only me or the system have a super protection?

everything i try to delete, modify from the root explorer, /system/apps , etc... when i reboot, it revert back the changes... changes made to build.prop too... and apps like Link2sd (to remove system apps) and nothing.

Is it because android 6 ?

How can i get W/R permission and how to change it permanently?

Tried to remove phs supersu from that rom to instal the superSU from chainfire but its not working... keeps "SU binary need to be updated" > "the instalation failed! restart and try again"

2 things: Write protection / SuperSU instead
[Android General] Charles IV:
Eugh, can't concentrate. I had issues changing the build.prop. I had to boot into recovery, adb pull, edit on pc, and push it back.

---------- Post added at 04:53 PM ---------- Previous post was at 04:45 PM ----------

Is your device single or dual SIM? If single, ensure the changes made on the commit are in your build.prop, if dual, ensure the three changed lines that are together are correct according to my system.prop.

I'm not sure about your baseband issue, but it's worth making sure that that is correct.
[Android General] BoC4RDi:
All i can do is to modify things before flash the rom on recovery.. edit build.prop, remove/replace apks, etc.. then flashing it will not revert the changes..

Android 6 and their permissions :crying: :(
[Android General] Charles IV:
Have you tried using terminal? Using an emulator or adb shell.

And are you able to use adb when booted into recovery?

Edit - and what recovery are you using, in the stock recovery for the 4034 (specifically for 4034e, even when using mobile upgrade tool), adb doesn't work, even after enabling adb or sideload. Twrp, however, works fine.

Another edit - and from what I remember, when it tells you to update the su binary, it gives you the option to do it normally, or in recovery. Have you tried both, or does it not give you the option?
[Android General] kernal-sanders:
very weird screen issue

Hi there, I got the Alcatel 4034 that I rooted thanks to your guide. Now that I installed CM and GAPPS, my screen becomes very dim and a portion of the screen is flickering, and the screen is overall very hard to see anything, mostly when It's charging or usb to PC. The lock-screen is just pure white. When my cell screen turns off it becomes white. At times randomly the screen will become extremely dim and only on one half the screen and the other illuminated. It seems to appear like a hardware issue, but the screen worked perfectly with the stock rom it shipped with and it works when I boot into CM until the lockscreen or usb plugs in. What am I doing wrong? I wiped everything except the internal storage and I tried the restoring the boot trick but it just stayed at the boot logo. Luckily I created a backup via TWRP. Now I reinstalled CM and GAPPS and the screen is still going dim on one half and barely visible, very frustrating. Has anybody else experienced this on such a model? Thanks in advance.

UPDATE: I ditched the Alcatel, I now own an LG G5 with Fido, It's not rootable, I heard, and I am worried it will mess up the phone. I have a 2 yr contract to go until I can upgrade to the G6 model.
[Android General] BoC4RDi:
My front camera isn't working on custom stock rom pixi 4 4 from this thread, in any app i tried to switch then get a freeze/force close.

I decided to test and installed a stock firmware from a friend on youtube (4034 F)

it' working great...

I did the root steps carefully, and have success on phh's superuser > then removed it and now with superSU's chainfire..(Thanks to them and for Kirito) on stock rom it works, in the stock mod "Pixi4-4STOCK.zip" i don't had success, may i made mistakes, obviously :silly:

But still with "reboot>back to normal"

i tried to remove with link2sd the "Googleplay music" but when reboot it comes back.

i can't merge updates on system apps, or remove them to update and use as user app.

Anyone can help? send the comands of adb and how to do it (i will search now, probably will found how, and probably will not work because it seems like system is protected from changes (every change= root/recovery/flashables)

i found some tools on this thread (fix sd permissions, init.d,etc) < this can help with this problem?

i remember i had a xperia M2 and needed to create the folder "init.d" on system/etc/security.... Any script to gain permanet edit access?

is only me having this problem? think no because its a stock firm.. :rolleyes:

:confused: How to remove system apps, or edit build.prop and don't get reverted on reboot < that's the question, hope you can understand my problem guys. what ii need to delete, add, script, etc. Thanks in advance.
[Android General] Charles IV:
Wow, you've both got the same phone as me.

[MENTION=8360210]kernal-sanders[/MENTION] I haven't had this issue, and I don't know what it could be. If this is happening with the cm13 on the first few posts, try the cm13 I posted, and see if you have the same issue (and if the SIM card is detected), just make a backup first.

[MENTION=5855209]BoC4RDi[/MENTION] try removing the system so with terminal emulator / adb shell. You'll need to mount system and everything before you rm -rf though. I find app removers sometimes worked, sometimes didn't.

To edit build.prop, I had to boot into recovery, connect to my computer, and adb pull the build.prop, edit the build.prop on my computer, rename the build.prop on the phone, and adb push the build.prop on my computer back onto the phone.

I'm honestly not sure about scripts or link2sd

Mounting system is tricky, so you'll have to Google. When I get back to my pc I'll edit the command I use in.
[Android General] Ruffypp:
dual sim sir,,i tried with no luck,still unknown base band,,
[Android General] BoC4RDi:
The more I move, the worse it gets.

Now it was with the perfect rom, root, xposed, everything working perfectly.

The only thing that hinders is not being able to modify the system files.

So I made the 4 files flash I found around here in this topic:

- cwm-Franco.Dev.Team.init.d.Pack.Installer.zip

- UPDATE-Busybox.Installer.v1.26.2-ALL-signed.zip

- UPDATE-Kernel_init.d_Injector-AK2-signed.zip

- UPDATE-sdcard.Fix.Permissions-signed.zip

To see if it solved the writing problem in the system, but nothing changed and now appeared another problem !!!

"NVRAM WARNING: Err = 0x10"

I have already tried to solve this one from above but all the methods do not work just because I can not modify the files of the system !!!

I have to delete 2 files:

- data / nvram / APCFG / APRDEB / WIFI

- data / nvram / APCFG / APRDEB / WIFI_CUSTOM

Can you or anyone viewing this message tell me how I can delete these files and replace them with the ones I downloaded?

The system is protected against change, so even with root, root explorer on restart it reverses the changes I make at the root of the store

Is it something to do with "Dev block"?

how can I do now? I have to delete the 2 files that are in that folder "data / nvram / APCFG / APRDEB /" WIFI and WIFI_CUSTOM ... and then move the 2 that I downloaded to it. I have to use the PC and ADB ... terminal would be in the cell itself? So it would not work because of the protection.

How to do this? i don't used adb and commands on my life :crying:

Since our device is the same, please send me the commands so I can replace the 2 files.

And also if you know the commands to break this protection in the writing system.

Does yours have this too? I can not even delete the APKs from the system, because they come back on reboot.

Should I change kernel?

I'm a little lay
[Android General] Charles IV:
I don't have your problem, but I did notice that build prop would change back, and deleting system apps sometimes wouldn't work. I'll send commands to mount system, do you have adb installed on your computer?

Use standard Linux commands -

rm -rf /path/to/file

(you'll need to

su

first if deleting system files. Use mv to rename and move. Google to find out the syntax, if you don't know. I'll tell you the command to mount system when I get onto my computer.

Honestly some of the stuff you're talking about note is too complex for me, so wait for [MENTION=5515628]kirito9[/MENTION] to come back, or someone else who knows.

edit - ok, i thought you had to specify the mount point for system, but you dont. this should work:

mount -o rw,remount,rw /system
[Android General] itsfeelipe:
Guys I've just flash the stock rom on my alcatel pixi 4 5 and now I can't flash TWRP on my phone it's says "PMT changed for the rom it must be download again" how do I solve that? I already resert and didn't work it
[Android General] Charles IV:
so you're trying to flash twrp, or a rom in twrp?

if you're trying to flash twrp, how are you doing it?

in fact, what steps are you taking anyway?
[Android General] itsfeelipe:
Well I've just download the stock rom and flashed on my phone using sp flash tool untill here everything it's fine but now I'm trying to flash TWRP but it shows "PMT changed for the rom must be download"
[Android General] Charles IV:
are you using fastboot to flash it (fastboot flash recovery twrp.img etc)?
[Android General] itsfeelipe:
No, I tried only with sp flash tool, I'll try thanks
[Android General] Charles IV:
ok, do a bit of google to get the correct syntax for the command.

I'm not sure if you can flash it in stock recovery, but that would be easier if you can, but do either of these.
[Android General] CVAngelo:
I

You need to use the Write Memory tab of SPFT to flash the recovery image directly to the location of the recovery partition. You must have a checkmark next to the Preloader line on the Download tab, otherwise the Write Memory tab will not function. If you don't have the preloader.bin file, just use the Read Back tab to extract it out of your device. If your version of SPFT is higher than 5.14, you will not be able to use the preloader.bin file you read back from the phone. For higher versions of SPFT, you will need the preloader.bin file (very small size) that you obtain from a download of the stock firmware. The reason is that when you read back any partition, you will be getting the image that's stored there along with all the blank spaces that occupy the remainder of the partition beyond the end of the image that is stored in the partition. Version 5.14 ignores all the blank spaces.

To access the Write Memory tab, hold down the Ctrl-Alt keys then tap the V on the keyboard (so Ctrl-Alt V). You will enter Advanced mode on SPFT. Then click the Window option in the menu and select Write Memory from the drop-down. This will open the Write Memory tab. You then specify the name and location of the recovery image you wish to flash. And the Linear Starting Address (0xNNNNNNNN) where the recovery partition starts on the device. The beginning address for the recovery partition can be found on the Download tab on the line which identifies the recovery partition, or just look it up in the scatter.txt file.

Be extremely careful with the Write Memory tab. You can really muck up your phone because it allows you to bypass the checks and balances of the Download tab (such as PMT has changed for the ROM). You can use this method to flash ANY image to ANY location on the phone. That's why it's risky! But after you get used to it, you will get hooked. I never use the Download tab any more. Lol

The predominant uses of the Write Memory tab are to flash Kernel/Boot, Recovery, your backup of the data partition, or the entire ROM_0 backup of your device (to unbrick it as if by magic). In other words, the Read Back tab allows you to get stuff directly out of the device from any location. The Write Memory tab allows you to put stuff back into the device in any location. These two functions simply act in opposite directions.

One thing I forgot to note is that, when you use the Write Memory tab, you keep the battery in the device at all times. This is different from the procedure for the Download where you first start the flash with the battery out of the phone, then slip it in. The reason is that the Write Memory function loads the preloader AUTOMATICALLY because you had to tell it where the preloader.bin file is (by checking the box on the download tab).
[Android General] itsfeelipe:
Seems complicated, but thanks I'll try
[Android General] CVAngelo:
It's quite simple actually. It's just that the Write Memory tab is hidden and there are a few steps required to unhide the tab. But, it's no more complicated than Read Back which I presume you're already doing to make a backup of your ROM.

Note to EVERYONE who attempts to use the Write Memory tab (or the Download tab): the very first thing you should do before flashing anything to your device is to make a backup of your stock ROM using the Read Back tab.

CAVEAT: AS SPFT IS NOT FULLY COMPATIBLE WITH MARSHMALLOW AND HIGHER, I DO NOT KNOW THAT WRITE MEMORY WILL WORK. IF IT DOESN'T WORK THEN USE THE MIRACLE BOX AS NOTED IN THE FIRST POST. BUT BOTTOM LINE IS THAT YOU SHOULD ALWAYS HAVE A BACKUP OF YOUR STOCK ROM.
[Android General] Charles IV:
Ahh, so you can make a backup with spft without another program.

But then again, when I looked, I couldn't find anything like a read back tab, but I suppose it was because i was looking for something like backup, not read back. I'll have another look and contemplate why they didn't name them flash, backup etc
[Android General] drmad:
Someone can help me with twrp porting for 9001d (qualcomm). I managed to boot the porting made by kirito9 but I can not solve some problems.
[Android General] Charles IV:
I can try, but honestly, im not good at this stuff.

Actually, i dont jnow how to even make a recovery, but tell me the problems and sources, and we'll see.

---------- Post added at 02:58 PM ---------- Previous post was at 02:45 PM ----------

When using readback, I'm unsure of a few things. I'm following this guide, and the first thing that could be device specific that I'm not sure about it step 9.

Are these directions OK? Is there a better guide to follow? Can i follow this and you just tell me what to change. Thanks.
[Android General] CVAngelo:
Yes, the guide is fine. But the starting address and the length of the read back depend on the device, and on what you're trying to do.

If you're making a full backup of your ROM, the starting address is going to be 0x0 regardless of device. The length of the read back should be the starting linear address of the CACHE partition. You can find that in either of two places: 1) Just look at the Download tab and find the line in the table that identifies the CACHE partition. The beginning address is indicated there; or 2) open the scatter.txt file and look for the CACHE partition...there you will also find the linear starting address for the CACHE partition.

That is the hex number to use for the length of the read back that will capture the entire ROM (excluding the cache and userdata partitions which you should never include in the full ROM backup).

If you ever need to read back a specific partition, you simply need to look it up in the scatter.txt file. There you will find both the linear starting address for the petition and the length of the partition. Those are the inputs to use in the Read Back tab in order to pull the partition.

Once you've read back the ROM or any partitions, you can always flash them back later using the Write Memory tab.
[Android General] Charles IV:
Thanks, I find another guide telling me to look at the scatter file and fill in the value (linear address of final partition in scatter file) from there (I'm making a full backup)

Think is though there's a new drop down option above the addresses not covered in the guides. I left it on default, but the options are something like emc_user, boot_0 and boot_1, but I'm not sure, will edit when I get back to pc.
[Android General] CVAngelo:
No need to go past the linear starting address of the Cache partition if you're making a full backup of the ROM.

If you go past the starting address of Cache you will end up including the cache partition and the user data partition in the backup. But when you flash a ROM you are supposed to do a factory reset anyway for a clean install....which will then wipe the cache and user data. So you're just making the ROM backup file way too large unnecessarily! And if you share your ROM that includes userdata with someone else who needs the ROM, they will then have ALL your userdata which may include your personal information including automatic access to your Gmail account! BE CAREFUL!

As I said, you don't need to go past the cache partition. If you want to backup your userdata partition, do it SEPARATELY.
[Android General] Charles IV:
Thanks, but what about the drop down options?

edit:

and also, with the attached scatter file, should the length be 0x72800000?

and the options for the drop down menu are: EMMC_USER, EMMC_BOOT_1 and EMMC_BOOT_2 (attached a screen shot)
[Android General] CVAngelo:
Leave the drop-down option at whatever is the default. Don't mess with the defaults. You're not doing anything with the boot regions.

Yes, the length should be what you indicated as that's what is indicated as the starting linear address of the CACHE partition in the scatter.
[Android General] Mariustiberius:
i was install new (stock) rom o my alcatel pixi (5010x) and now google do not give me to start phone , what i should do ? it is passed 72 hour and still nothing , i cant start my phone and i need it , i think i need rom without gapps ?
[Android General] CVAngelo:
What do you mean when you say that Google does not give you to start phone. Google does not give you what?

Do you mean you forgot the password for your Google account?
[Android General] Mariustiberius:
well i try to install recovery and mess things ,(finished with bootloop) , so i install stock rom , but after install google blocked me to use phone , cant log in on google , cant start phone , but ther is another thing , right now i change my pasword on my google acount from my usless phone , how stupid that can be from google , and i still cant log in , stupid google :)

Well i manage to start my phone with testdpc apk program , it work :)
[Android General] hectus:
Hi again

Now i have tried to flash some of the ported stock roms linked on the first page, i tried to download all the diffrent versions, 2 of them gives me error 7 during instalation, and 2 of the others installs and works fine, but it wont detect simcard. i tried mtk engineering mode and several other "tricks" i read about on the net, but no matter what it wont detect simcard and where i can chose network its totally blank, my imei is also blank.

Any suggestions on what i do wrong or how to fix it?

Thanks in advance
[Android General] viktormax3:
bugs/not working

Show a pink camera

Sim card not inserted/imei blank/ baseband null (alcatel 5045a)