yashsingh1/xdaforums huggingface dataset:
[Android General] dimspace:
I will be honest, no idea how to extract them.

but it wont boot into fastboot anyway, repeated tries from adb and it just reboots normally, so its not possible to unlock the bootloader anyway

---------- Post added at 07:36 PM ---------- Previous post was at 07:22 PM ----------

Uk Pixi 4 (6) 9001x

Just rooted successfully with latest Iroot

It installs Kinguser as default permission manager

tested with rootchecker, all there, titanium succesefully ran backup

edit:

then it lost root after reboot

thats annoying

so it needs the bootloader unlocking, but refuses to adb fastboot
[Android General] sparala:
Hi Kirito and hacknmtk and thanks very much for your replies,

I'm running ubuntu 32 bit so the sp flash tool (there is a 32 bit version) and mobile upgrade tool won't work, but i'll try to install a virtual machine or use another person's computer. No need to for a responsibility disclaimer I knew it could happen and that's not the first time that I flash a phone, being that for all my phones for years.

Also, I can't start into fastboot, it really just stops after the alcatel logo and reboots immediately no matter what buttons I*press. I'll copy paste the sequence of commands that I*entered:

$adb reboot-bootloader
$fastboot oem unlock
...
(bootloader) Start unlock flow
$fastboot flash recovery twrp.img
target reported max download size of 134217728 bytes
sending 'recovery' (13432 KB)...
OKAY [ 1.495s]
writing 'recovery'...
OKAY [ 0.586s]
finished. total time: 2.080s
$ fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (13828 KB)...
OKAY [ 1.536s]
writing 'recovery'...
OKAY [ 0.580s]
finished. total time: 2.116s
$ fastboot reboot
rebooting...
OKAY [ 31.086s]
[Android General] kirito9:
Did you try manually going to fastboot using the hardware keys when the device is off? It might not work but worth a try since the other methods don't work.

I can maybe try to port TWRP for your device and then you can root using phh's Superuser.

---------- Post added at 06:05 PM ---------- Previous post was at 05:55 PM ----------

Strange that your fastboot isn't working, it should. The only other option is use SPFT to flash your stock recovery to fix the softbrick.
[Android General] sparala:
Hmm, I just installed spflash on a virtualbox windows xp machine but it's asking for a scatter file. What scatter file am i supposed to use ?*

Also I tried to use the alcatel mobile upgrade tool but even though windows recognizes a «mtp device» the mobile upgrade tool does not recognize the phone when I plug it in, so that it begins to charge (model 5045). Starting the phone has no effect on its discovery by the mobile upgrade tool and it just bootloops immediately after the logo again.

Edit: could it be that my model 5045d, even though it's called pixi 4 (5'') is different from the models for which the recoveries were done here ?*
[Android General] kirito9:
I would suggest using a different PC with windows OS as the default OS. Virtual machine doesn't work so well when connecting with com ports.
[Android General] kirito9:
If the twrp recovery works then you can root using Magisk and forget about Kingroot. It's only temporary anyway.
[Android General] vetooo3001:
waiting for twrp and you very good person my friend

---------- Post added at 08:16 PM ---------- Previous post was at 07:58 PM ----------

my devices desnot work fastboot mode.
[Android General] drmad:
Dont work, dont boot :(

But not brick, only reboot system
[Android General] kirito9:
I'll make a few more builds with the system files you will upload.
[Android General] kirito9:
I'll make a few more builds with the system files you will upload. The good news so far is that it doesn't brick. So others users of the MSM8909 chip may be able to get a custom recovery without bricking.
[Android General] drmad:
Well, these are the system folder.

folder lib: https://drive.google.com/open?id=0B6YC2MyVLdhkdUVLamItbnRBQXM

folder vendor: https://drive.google.com/open?id=0B6YC2MyVLdhkaXhLOW5lRG9adlk

folder sbin: is not in the system but it is out, in file manager, Is it the same or is it a problem? If i can upload after
[Android General] kirito9:
It's no problem, I'll try these files.
[Android General] kirito9:
I've tested the file attached with my own device which has the same /dev/bootimg path. It now detects that path but since Magisk only works with android 5.1+, I can't test to see if it actually goes beyond detecting it.
[Android General] Charles IV:
[MENTION=5515628]kirito9[/MENTION] sorry for the late feedback - i was focusing on real life ;)

A reminder of my situation:

After locking the bootloader to try and test your flashing twrp without unlocking the bootloader theory, i couldn't boot up.

I have now unlocked again, and still can't boot up into an operating system

I am able to flash a boot.img, but not a system.img.

I'm having trouble with SPFT (I'll have another go and feedback if it comes to it)

Mobile upgrade tool is saying my phone's on the latest version (facepalm)

EDIT: i have just tried booting again, and it stayed on alcatel logo before rebooting into recovery

For some reason the recovery was stock, rather than twrp, which i flashed. Maybe it's because the stock recovery is what was included in your backup??? but you backed up from twrp surely :confused:

anyway, in fastboot i flashed twrp, rebooted normally, and it did the same as above, just rebooting twrp instead of stock

another edit: just restored everything but system from twrp backup.

It worked, but after reboot recovery, it booted into stock, so the backup probably includes stock recovery

Finally, restoring your twrp backup didn't work, but i think it gives us more of an idea as to what's going on.

Here's what i found in the log:

tar_extract_file(): failed to extract /system//framework/arm/boot.oat !!!
...
extractTarFork() process ended with ERROR: 255

Full log attached

edit in hide tags
[Android General] drmad:
Folder sbin It does not have files inside
[Android General] kirito9:
No problem. If i need anything else, I'll ask.
[Android General] kirito9:
Since the twrp backup doesn't work neither does flashing with fastboot, SPFT is your only way to restore your system.img. Could you elaborate on the SPFT trouble.
[Android General] Charles IV:
OK, i am using ubuntu 16.04

When I open SPFT, and click on the download tab, i select the scatter file from the SPFT rom on this thread.

As to your instructions, i deselect all apart from system.

From here, i press the download. I have tried several situations, and still nothing happens, the red status bar stays on 0%, 0 B/s, 0 bytes etc
[Android General] kirito9:
Follow this guide to get the preloader drivers installed.
[Android General] Charles IV:
ive followed the guides, bu t still nothing happens. I posted my issue on their thread, but here is what i posted:

when i open flash tool, the progress bar is already there at the bottom (just on 0, of course, however, after progressing onto the other steps, when i click download, nothing happens, i've tried the steps in the tutorial, but it doesn't make a difference.

When i run flash tool with terminal, after clicking download, these three lines appear, and it stays like that. My phone is in recovery mode, and the computer does recognise it (file browser appears and everything)

these are the tree lines that appear:

Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms

edit:

edit: these lines have now appeared:

change@/devices/pci0000:00/0000:00:02.0/drm/card0

change@/devices/pci0000:00/0000:00:02.0/drm/card0

Aaaand i accidentally ^C'ed it when copying it, will start again

another edit: as to someone's instructions on the other thread, in recovery, lsusb shows the phone up as 'Google Inc. Nexus 4 (debug)'. I think this might me the problem, as when it's powered off, it's A 'MediaTek Inc. MT65xx Preloader', but it always reboots itself. aha! with the battery removed, it comes up as 'MediaTek Inc. MT65xx Preloader', will try again ... nope, it's gone again, and bootloader comes up as 'HTC (High Tech Computer Corp.) Dream / ADP1 / G1 / Magic / Tattoo'. will try anyway.

ive attached the recovery log of me trying to flash my cm13 port. I've completed a factory reset as it recommended, and I'm waiting for it to complete the flash, or show an error.
[Android General] Charles IV:
well, spft wasn't working, but i tried flashing the stock rom on this thread, it worked, and ... it's booting.

fingers crossed. right now it's on a black screen!

edit: it went onto an encryptiano screen, but im not sure because i dont speek spanish. It's now doing the boot animation for the second time (it did it twice before, when it was working)

edit:so, the stock rom is working (but in spanish), but my cm13 isn't ...

cm13 is getting error 7, and im too anxious to get the phone working again to check the log

unfortunately, not enough room for twrp backup, and the spft backup is for windows (i cant find the power lead for my laptop, and it's dead)

---------- Post added at 11:10 AM ---------- Previous post was at 10:42 AM ----------

I think there is a bug with the stock rom provided for the pixi 4 4"

There is no setup wizard, or it doens't appear at first boot, or in the app drawer

edit: whoops, i attached the recovery log to the wrong post. It's the one above this one

---------- Post added at 11:35 AM ---------- Previous post was at 11:10 AM ----------

thanks, [MENTION=5515628]kirito9[/MENTION]

i dont know what exactly i did, but after restoring only the boot from the backup, it didn't boot, and i went back to spft.

I then flashed the stock rom, which worked, and after a factory reset, I'm back on my cm13 port, and i need to fix this users thing, because with it, i can only install apps from the playstore on first boot. After a reboot (e.g. installing gapps), it wont work.
[Android General] hectus:
Hi again

I been using the cm13 build now for a while and its been working decent, however i still have some issues with audio, also sounds via bluetooth. I been thinking of flashing the stock 4034x rom in twrp, is this possible? if so, i was planning to have both cm and the stock and just switch via recovery as needed.

Also i wonder if ur planning to do any other builds, like nougat for example, for the 4034? i hope you are since your doing excellent work :)
[Android General] Charles IV:
Is there a stock 4034X rom? i thought it was 4034A or something ...

Or did you mean x as in any letter.

I've built a cm13 rom for 4034X, but you wont like it because bluetooth isn't working at all!

I do want to build los14.1, but i would like to get the cm13 working properly first.

On that note, [MENTION=5515628]kirito9[/MENTION] i saw the repo you stared. I guess these patches are for the device tree, looking at the readme file, but how do you apply it, and what does it do?

Do i clone it into the root of the working tree and run the scripts? and what exactly does it do?
[Android General] hectus:
Hiya

Does your cm13 have any other issues other than no working bluetooth? how is the incall audio quality and gsm signal strength? if thats working good im intrested in trying it.

Im pretty sure i seen a stock 4034x rom on here somewhere, unless its like u say, that the x simply means any version. However i thought it was the X version.
[Android General] Charles IV:
I'm uploading my latest build to android file host now.

However, because it is a spare phone, i haven't tried the other things.

There are a few bugs, although if you only want to try the rom to switch back again, it will be useful to see if you have the same issues.

The main one is that has any real user impact, other than a ui that looks like it hasn't fully loaded (reacent apps etc), after the first boot, you seem to be logged in as the guest user, even though it says it isn't.

This means that: You can only access developer options on the first boot, you can only access recent apps menu on first boot, minor settings (such as don't vibrate on touch) are lost at every boot, a few other things i may be unaware off.

However, this may only be for me.

I would want you to try it, just to see how it is for you.

Make sure you make a backup first, especially of data if you value it.

I built this for my phone with the 4g, 1/2g arrangement, not 8g, 1g so if your's isn't this, it will be interesting to see if you loose half your ram or not, just back up first!

Android file host want's me to create the device, so using mega for mow.

20170601 build: MEGA

edit: [MENTION=5515628]kirito9[/MENTION] i looked through the logcat for the bluetooth problems, looking for why im logged in as guest, i searched for a few things, like permissions, user, guest, etc, but found nothing relevant. I was wondering if there was a way to find out what the actual issue is here.

update: i found the issue on a samsung thread, and following one of the posts there, i opened the google setup wizard with adb. I can now access developer options. I have no idea if this will work after i reboot (doing it now)

another update: ahh, it looks like i will have to run the command every time
[MENTION=8232921]hectus[/MENTION] if you are having this issue, just run

adb shell am start -a android.intent.action.MAIN -n com.google.android.setupwizard/.SetupWizardTestActivity

in adb, or trigger setup wizard another way, e.g. nova launcher, and you should be fine until the next boot
[Android General] dashu42332:
kirito9 i have try the above magisk patch ,but still the same issue cannot mount boot.img. My tab 8063 is marshmallow and it don't have fastboot. I am also attaching the recovery.log
[Android General] Charles IV:
Damn, SIM card isn't working. When i go into mobile networks, or in setup wizard, the sim card isn't recognised is inserted.

I've also realised in theory that we can pull the vendor blobs from cm13 (without things like the scripts cm provides), by looking at my 4034X-vendor-blobs.mk at putting them in the right places?

Also, you were having a conversation with [MENTION=1679926]drmad[/MENTION] about building a recovery, but i was wondering if it was possible to construct more than just a recovery from the cm13 port zip, and aspects inside, to use as reference and hopefully fix the sim and users issue?

Or actually, just had a look at the cm13 port zip, it looks like i don't even need to flash it, just look at the extracted files

edit: all apart from data and wlan

edit: i was looking through another logcat, and i was wondering what i should be looking for in terms of the sim.

I searched for 'sim', and is appears it comes under /agps, but searcing for E/agps didnt bring up anything to do with sim, so i guess were not looking for errors, seeing as the phone doesnt realise a sim is there, so the only thing that seemed strange (that i saw) was

[ 06-11 09:52:25.050 314: 404 D/agps ]
[agps][n][CP] [MD_1] read sim_info_rsp sim_number=2 md_type=0 (0=fdd, 1=tdd) ecid=0 otdoa=0 band_num=0

the 'sim_number=2'

what does that mean, when there's only one sim slot?

Or is sim refering to something completely different
[Android General] Charles IV:
[MENTION=5515628]kirito9[/MENTION]

My brother now need the phone, and seeing as the sim card doesn't work with my cm13, i flashed teh cm13 port, and although it takes a while to recognise, it does recognise. However, due to being incorrectly configured for my device, i flashed my own cm13 boot.img, to stop the reboots. The sim card has stopped working.

I'm stumped, any ideas/help?

I think I'll reverse all the single sim commits in the device tree and make bootimage again, but it shouldn't make a difference. I think the error with teh sim cards right now is that we incorrectly configured system.prop to single sim, and somethings not working.
[Android General] kirito9:
Sorry I haven't been as active as before in recent days but something has come up in my personal life that I won't disclose and will affect my time on XDA, hopefully I won't be gone for long. Anything that I was working on with be hiatus until I return :).
[Android General] Orlandoamg:
boot into custom recovery?

ive unlocked the bootloader on my pixi 4 5010g and flashed twrp 5010 but i cannot boot into twrp from either the phone button combination or via the adb commands. it reboots and right when twrp is supposed to boot, it just reboots and starts up the phone. any help will be greatly appreciated...
[Android General] Charles IV:
We had a similar problem previously ...

Have you tried another recovery?
[Android General] Orlandoamg:
i also flashed the ctr recovery aswell as the stock recovery listed for the 5010 device. the results were all the same. im unable to boot into any recovery. phone starts up and works normally however. any ideas?
[Android General] Charles IV:
Hmm.

Are you running stock ROM?

Could you bot into recovery before you changed it?
[Android General] Orlandoamg:
running stock ROM. dont know if i could have previously booted into recovery mode before having changed it since i never really had a reason to before now...
[Android General] drmad:
GREAT NEWS!

I was able to install and boot TWRP on 9001d !! And I made the definitive root, so I confirm that the following procedure can be performed:

1. Temporary root

2. install twrp

3. definitive root

TWRP ported still has bugs, as soon as I fix, i will post it with the whole procedure in detail.
[Android General] sweet khan:
please help.....

i have Vodafone smart turbo 7 (vfd500) nd hardware same like Alcatel OT Pixi 4-5 (5045) (4G) MT6735

but the TWRP recovery is not woring on my device. when i flash recovery i got some lines on display.

my device is pixi4_5_4g_vf i saw in build info.
[Android General] Charles IV:
Have you tried 'fastboot boot path_to_recovery.img'?

---------- Post added at 03:34 PM ---------- Previous post was at 03:31 PM ----------

Have you tried fastboot boot to boot the recovery image
[Android General] Charles IV:
no, you shouldn't need to.

say the recovery was called recovery.img,

fastboot boot recovery.img

or

fastboot boot ./recovery.img

should be fine
[Android General] marekvidina85:
Not working.

OK, so I write this as owner of a phone I bought 6/2017... and I mean what I write now: anything on this site including this recovery img damages my phone that it was not able to boot rom at all, dont trust anything posted on this website, phone manufacturers have more people making sw updates than these amateurs, anything these guys post up here get obsolete in days after relase and turns into dangerous stuff that can damage your phone. dont download anything, that frinedly advise. These people here know that what they are doing is complete insanity and that it does not make any sense at all, but they spent too much time doing this insanity that they will not admit it. dont get caught by the same scenario, be smarter. Let this site be, they live only by your visit. They think it is ok, that if recovery doeasnt work for you, that you spent whole afternoon repairing your phone. they dont care about this. they are insane. Stop this, leave this page. Ríde a bike, buy a sandwich instead. Have a nice day!

---------- Post added at 06:07 PM ---------- Previous post was at 05:50 PM ----------

OK, so I write this as owner of a phone I bought 6/2017... and I mean what I write now: anything on this site including this recovery img can (did damage to mine few mins ago) damage your phone that it was not able to boot rom at all, dont trust anything posted on this website, phone manufacturers have more people making sw updates than these amateurs, anything these guys post up here get obsolete in days after relase and turns into dangerous stuff that can damage your phone. dont download anything, that frinedly advise. These people here know that what they are doing is complete insanity and that it does not make any sense at all, but they spent too much time doing this insanity that they will not admit it. dont get caught by the same scenario, be smarter. Let this site be, they live only by your visit. They think it is ok, that if recovery doeasnt work for you, that you spent whole afternoon repairing your phone. they dont care about this. they are insane. Stop this, leave this page. Ríde a bike, buy a sandwich instead. Have a nice day!
[Android General] Charles IV:
May i remind you this site is a developer site. On this, and many other threads, people (developers) have worked very hard to deliver content to each other.

When something doesn't work, they work together to fix it.

Would you like to elaborate your problem, so we can help fix it?

p.s. there are so many versions of the pixi 4 (alcatels fault), that sometimes things aren't build perfectly for your device. Generally, however, they work, but not always.
[Android General] kotla85:
Alcatel Pixi 4 (6) 3G - 8050D

Hey there,

I looked over this forum and found out that the CM12.1 ROM might be compatible with my phone (Alcatel Pixi 4 (6) 3G - 8050D). However, I read that the camera might not work and the internal storage might be almost full after changing the ROM and there might be other bugs as well. Can someone confirm these bugs, or can someone give me a proof that it is a stable ROM for my phone?

Thanks in advance!
[Android General] Orlandoamg:
ok i did as requested but all i got was an infinite waiting for device screen...
[Android General] Ruffypp:
i already success rooted my pixi 4 5 4G 5045t,,my problm is,,i unable to r/w to system,so i cant edit or write to system,aslo unable to edit build.prop,but its nothing happen after reboot,bcause a system is read only,,

p.s. im on system root,not systemless
[Android General] sweet khan:
yes i boot the phone to recovery but recovery is not working on my phone display and even touch is also not response on recovery mode.
[Android General] Charles IV:
Run fastboot devices first, and continue disconnecting, reconnecting, rebooting into fastboot again until it comes up with a device. Then run the second command.

It should work if you have the correct stuff on your pc, because fastboot wouldn't have been modified by flashing a rom/recovery.

---------- Post added at 08:20 AM ---------- Previous post was at 08:17 AM ----------

What phone do you have (including model number of you know it), and what recovery did you flash.

Sounds like the recovery isn't the correct one for your phone, so try other ones as well.

---------- Post added at 08:29 AM ---------- Previous post was at 08:20 AM ----------

I don't have your phone, so I don't know if anyone else has tried it out, or if it works.

If it is in one of the op's, it at least mostly works, but it may not work perfectly.

All I can say is make an spft backup and everything of your current configuration, so if something doesn't work, you can restore the backup.
[Android General] kluongo:
has anyone found a successful method to rooting the Alcatel a571vl (NET10). I would greatly appreciate any updates or insights into this model.
[Android General] vetooo3001:
is this working for pixi 4(6) 9001d
[Android General] Charles IV:
i recommend making full backups, then trying it yourself.

That's the best way to find out.
[Android General] Ruffypp:
unknown baseband

hi dev,i have try this rom,the rom was perfect,but the problem only cant detect sim card because of unknown baseband,,how to fixs that??will u update this rom?btw great work dev,thanks
[Android General] Ruffypp:
please fix the baseband unknown
[Android General] Charles IV:
Unfortunately the op on this thread is away right now, but if you could upload a logcat, I think it would help him when he returns.

Also no need to post the same thing twice. Use the edit feature of you want to add information.
[Android General] Zer0Bytes_:
the hell is a resurrection remix rom?
[Android General] CVAngelo:
Lol. It's exactly what the name implies. It's a custom ROM by Resurrection Remix. Didn't know they had one for Pixi 4.
[Android General] Ruffypp:
im sory for tht mate,i dont hv any logcat,,i flash back to stock after seen that bugs,