yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] YarsRevenge78:
I will give it a try after I get home. I would think the update binary that came in the OTA should would work. Maybe the problem is TWRP. If I get the same errors I will try the CWM that you made.
[General Questions and Answers] tone602:
I think the ota update didnt go through. When I check for updates again it still says update available. The downloaded update pkg is still there. When I hit install it checks for firmware and then reboots to twrp and does nothing else. Maybe twrp is preventing the ota update from installing? It's been so long since ive done an ota update.

Can you compare the screen shot I posted of About device to yours and see if anything is different?
[General Questions and Answers] YarsRevenge78:
OTA .zips will only flash from stock recovery, which I highly advise against doing. The Alcatel Idol 3 recently lost fastboot with an OTA.

Once we can get something flashable in TWRP we will let you know
[General Questions and Answers] :
Yea, its starting to sound like it didnt get flashed. Maybe a good thing.

Sent from my T-Mobile Onetouch Pixi 7
[General Questions and Answers] :
If youre rooted you dont have to worry about accidentally downloading the update.

Sent from my T-Mobile Onetouch Pixi 7

---------- Post added at 05:59 AM ---------- Previous post was at 05:39 AM ----------

Hey, I was thinking. If we lose fastboot, can't we still use adb to install twrp?
[General Questions and Answers] tone602:
Strange mine didn't have that message. Mine shows this.
[General Questions and Answers] :
Just for giggles I went ahead and restored my stock /system. It downloaded the update, but when it tried to install it the tablet rebooted itself and went to twrp. So im suspecting the ota update won't install unless you're stock and have stock recovery.

Sent from my T-Mobile LG G3
[General Questions and Answers] YarsRevenge78:
Yeah, OTA.zips require stock recovery to flash.
[General Questions and Answers] :
That's good though. I've been trying to figure out what partition has the fastboot commands. Google hasn't been much help.

Sent from my T-Mobile LG G3
[General Questions and Answers] :
The only thing I can really find is the fastboot protocol is in the firmware somewhere. And the android app for fastboot is located in /system.

Sent from my T-Mobile LG G3
[General Questions and Answers] tone602:
Wish I could be more help to you guys
[General Questions and Answers] :
Just sit tight until we can figure this out.

Sent from my T-Mobile LG G3, SlimLP 5.1.1 beta 0.7
[General Questions and Answers] YarsRevenge78:
It can't be in system. You can format /system and still fastboot, right? I'm almost certain fastboot stuff is in another partition.
[General Questions and Answers] :
Nah, there's a fastboot app in the /system dir, but the fastboot protocol is somewhere in the firmware section. I just dunno which partition gets patched and turns fastboot off. Could be /modem, /sdb1, /hyp etc. We could probably just replace the files and not flash any of the partitions, but we'll be behind on our firmware. And also there's a 50-50 chance that some of the new files might rely on the updated firmware.

Sent from my T-Mobile LG G3, SlimLP 5.1.1 beta 0.7
[General Questions and Answers] YarsRevenge78:
I saw in the idol 3 forum they basically left out all partitions involved in booting to make sure fastboot wasn't broken, but that sort of seems like not really upgrading the firmware to me.

I wonder if the OTA just locks the bootloader, requiring it to be unlocked again in order to use fastboot. I don't really want to flash the update to findout however.
[General Questions and Answers] :
If fastboot gets broken, you can't unlock the bootloader. It sounds like they just updated the apps and /system. If you look at the ota updater-script Alcatel has /modem listed as firmware. Next to using a hex editor and looking through files for fastboot strings not sure how else to safely keep our fastboot.

Sent from my T-Mobile LG G3, SlimLP 5.1.1 beta 0.7

---------- Post added at 12:47 AM ---------- Previous post was at 12:26 AM ----------

It sucks the idol 3 guys have been having to find out stuff the hard way, but atleast it gives us a heads-up.
[General Questions and Answers] YarsRevenge78:
we should probably finish this discussion here: http://xdaforums.com/general/help/t-mobile-alcatel-pixi-7-9006w-safe-to-t3201317 and stop cluttering up the rot thread.
[General Questions and Answers] tone602:
Is it possible to unroot and put the stock bootloader back on to

Flash the update at this time? Then try to unlock the bootloader to root again?

I can try since I got 2 tablets
[General Questions and Answers] kaerlighed:
Does this method work for those who have already taken the update?

I just got the pixi 7 from tmobile, and it has already been updated. Does this method still work? Many thanks!
[General Questions and Answers] YarsRevenge78:
Nobody has unrooted, updated, and then attempted to re-root for fear of breaking fastboot. If your device came with the update, I say go ahead and give it a shot. It can't hurt anything. If you are still able to fastboot TWRP and root, then everyone else should be safe to update.
[General Questions and Answers] tone602:
I tried on one of mine to unroot, flash the stock recovery to update it. The stock recovery.img and boot.img would not flash so TWRP is still installed. I also tried to lock the bootloader and unlocked it again too.

It seems that the size of the stock recovery is different than the twrp.
[General Questions and Answers] :
You're using the wrong commands. To flash its fastboot -i 0x1bbb flash boot boot.IMG or

Fastboot -i 0x1bbb flash recovery recovery.IMG

If you want to flash.
[General Questions and Answers] tone602:
thank you,

I was able to unroot from the settings within Super SU:

- then rebooted to bootloader in adb.

-flashed the boot.img using "fastboot -i 0x1bbb flash boot boot.IMG" , waited for successful message

-then also flashed the recovery using " Fastboot -i 0x1bbb flash recovery recovery.IMG" and waited for successful message

-then locked the bootloader back to stock using "fastboot -i 0x1bbb oem lock"

-checked the device info to make sure it was locked

-unplugged the usb and held down the UP and Power button to reboot. It rebooted into the Rom.

When I try to install the update it reboots to the Alcatel screen (bootloader) and hangs there and does nothing. I have to hold the UP and Power buttons again to reboot into the Rom and it seems that the update was not successful.

Do you think im missing a step or something else i should try?
[General Questions and Answers] :
You have to keep the bootloader unlocked. Could be why you're having issues.
[General Questions and Answers] YarsRevenge78:
Or...you tried to mix the stock boot.IMG with the updated everything else?
[General Questions and Answers] tone602:
I just unlocked the bootloader again and reflashed both the boot and recovery.img and tried to update again. Still reboots to bootloader mode instead of recovery to finish the update?

Not sure but I redownloaded the stock img's that were on the post.
[General Questions and Answers] YarsRevenge78:
If you are going to flash the stock boot.IMG you should probably flash /system as well.
[General Questions and Answers] tone602:
ok i found the one you posted here.

https://www.androidfilehost.com/?fid=24052804347811978

I will download and flash that as well.
[General Questions and Answers] :
I think to update using stock ota you have to use the stock recovery. I still have a feeling it'll break fastboot though. I've been busy fixing my G3 roms. I haven't had a chance to work on our tablet much.

Sent from my T-Mobile LG G3
[General Questions and Answers] tone602:
I tried updating the ota but the stock recovery, boot, and system img with full wipe didn't work.

It still will reboot to the bootloader and hang.
[General Questions and Answers] YarsRevenge78:
Are you able to fastboot all of the stock files and get a bootable stock system at all?
[General Questions and Answers] tone602:
Yes I did fast boot all the stock files but something is making it boot to the bootloader instead. For example, when I tried to erase data from the rom it rebooted to the bootloader as well. I would have to hold the up and power.

I also tried to erase system, boot, and cache with fastboot but got waiting for device everytime.

I reinstalled the twrp and that wiped the user data when it first starts. Now everything is back on with twrp and root but no luck with update.
[General Questions and Answers] :
Im currently working on a modified update.zip Im hoping will work for us.
[General Questions and Answers] petrov.0:
Ok guys, I watch this thread from time to time :) ... I didn't read all of course, but I see that you are wondering how to prevent the removing of the fastboot commands and how to flash the update. In the development section of the Idol, there is a script which removes these patches from the update file (I'm its author). The update then can be flashed through TWRP. You must restore the backup of your system image before the installation of the upgrade. Good luck.
[General Questions and Answers] :
We found out our latest update doesn't remove fastboot, but you never know about future otas. Thanks for popping in and giving a heads up on your script!

Sent from Tmobile G3, SlimLP 5.1.1 beta v0.8
[General Questions and Answers] petrov.0:
You also can use it to remove the patches/scripts which overwrite the custom recovery. BTW what's the problem to flash the update through the TWRP recovery ?
[General Questions and Answers] :
It wouldn't flash the ota update without being stock and having stock recovery.

Sent from Tmobile G3, SlimLP 5.1.1 beta v0.8
[General Questions and Answers] petrov.0:
Really ? Even with the backup of the system image and upgrade through TWRP ... there is a log, what does it say ?
[General Questions and Answers] :
It probably was something I didn't do right. I just went back to stock system.IMG and stock recovery. Booted up the system. Took the ota in android and installed and everything was fine. Still has fastboot. At least this time. Alcatel is probably following the idol3 forums, but not the T-Mobile pixi 7 forum. [emoji16]

Sent from Tmobile G3, SlimLP 5.1.1 beta v0.8
[General Questions and Answers] petrov.0:
With the stock system image the update can be flashed through TWRP too. You just need to find where the downloaded file is :D :D ... The recovery will be overwritten if you reboot straight away after the installation ... but that's a different topic.
[General Questions and Answers] :
I was able to use fastboot to add twrp back to the recovery partition no problem after the update. I got lucky on this ota that's all.

[emoji16]

Sent from Tmobile G3, SlimLP 5.1.1 beta v0.8
[General Questions and Answers] lazarus0000:
Oh well...

Tried and failed... Not at all familiar with ADB and when I tried to get it to work (as best as I could figure), it never recocgnized my device. Tried installing drivers but don't know that I was able to do that either.

I hate feeling like I've been surpassed but I'm pretty sure I can't do this one. I thought the Samsung Note 3 on verizon was a pain, but I got that one done. This is too much for me!

I'll continue lurking! Ha!
[General Questions and Answers] tone602:
Did you make sure that you have usb debugging enable on the tablet settings?
[General Questions and Answers] lazarus0000:
I have developer options enabled and USB Debugging checked. I think it's the Alcatel drivers but I'm not sure. Also, I noted earlier in the thread that people had difficulty getting ADB to recognize the Pixi but their fixes quickly descended into a form of geekspeak that is equal to me trying to decipher Greek while the other person is speaking Mandarin... Beyond my limited intellect here!
[General Questions and Answers] :
Sorry I haven't been around I'm having issues with my buildbox. Once I get Linux reinstalled and my build box and get my android build environment resetup I'll have more time for our tablets.

Sent from Tmobile G3, SlimLP 5.1.1 beta v0.8
[General Questions and Answers] PalmCentro:
Some time?

lol years!

Thank you!!
[General Questions and Answers] bada44:
Can somebody post the link to the factory image TW RP is reporting no OS installed I have tried several images none of them seem to work Thanks
[General Questions and Answers] tone602:
Post #45 on this thread
[General Questions and Answers] :
I'm still around. Havent been able to get cm to boot on our tablets yet. I'm also waiting for alcatel to release our kernel.
[General Questions and Answers] bada44:
I have tried all those files with no success
[General Questions and Answers] tone602:
I used this thread too

http://xdaforums.com/showthread.php?t=3201317
[General Questions and Answers] bada44:
What am I doing wrong?Even after all stock files were installed including recovery. Device only boots into TWRP!

C:\Users\BADA\Desktop\fastboot ADB>fastboot -i 0x1bbb devices

548ed841 fastboot

C:\Users\BADA\Desktop\fastboot ADB>fastboot -i 0x1bbb oem unlock

...

OKAY [ 0.000s]

finished. total time: 0.000s

C:\Users\BADA\Desktop\fastboot ADB>fastboot -i 0x1bbb oem device-info

...

(bootloader) Device tampered: false

(bootloader) Device unlocked: true

(bootloader) Charger screen enabled: false

(bootloader) Display panel:

OKAY [ 0.016s]

finished. total time: 0.016s

C:\Users\BADA\Desktop\fastboot ADB>Fastboot -i 0x1bbb flash recovery stock_recovery.img

target reported max download size of 268435456 bytes

sending 'recovery' (32768 KB)...

OKAY [ 1.047s]

writing 'recovery'...

OKAY [ 0.656s]

finished. total time: 1.703s

C:\Users\BADA\Desktop\fastboot ADB>Fastboot -i 0x1bbb flash system stock-system.img

target reported max download size of 268435456 bytes

erasing 'system'...

OKAY [ 1.125s]

sending sparse 'system' (262141 KB)...

OKAY [ 9.133s]

writing 'system'...

OKAY [ 29.272s]

sending sparse 'system' (239542 KB)...

OKAY [ 8.465s]

writing 'system'...

OKAY [ 30.333s]

sending sparse 'system' (234857 KB)...

OKAY [ 8.196s]

writing 'system'...

OKAY [ 29.979s]

sending sparse 'system' (256663 KB)...

OKAY [ 8.965s]

writing 'system'...

OKAY [ 31.692s]

sending sparse 'system' (259619 KB)...

OKAY [ 9.075s]

writing 'system'...

OKAY [ 32.491s]

sending sparse 'system' (260497 KB)...

OKAY [ 9.030s]

writing 'system'...

OKAY [ 32.588s]

sending sparse 'system' (165605 KB)...

OKAY [ 5.669s]

writing 'system'...

OKAY [100.445s]

finished. total time: 346.536s

C:\Users\BADA\Desktop\fastboot ADB>
[General Questions and Answers] tone602:
Make sure the file names match the commands. I noticed when I did mine they didn't.

Fastboot -I 0x1bbb flash recovery stock_recovery.img

Fastboot -I 0x1bbb flash system stock_system.img
[General Questions and Answers] AlanWinslow:
Thanks

THANKS,

Groovy. Please keep on it.

:)
[General Questions and Answers] cammykool:
Hoi there! just got mine from the black friday deal. all seems well!

These links are returning a 404.. any reason why?

Also what is the procedure for taking the ota mine keeps bugging me about?
[General Questions and Answers] byawww432:
success!

I don't have photobucket anymore and I am a forum noob so I couldn't think of an easy way to embed the photo
[General Questions and Answers] preston2146:
If anyone can help.....

adb reboot-bootloader reboots tablet but stays on splash screen.

Am I doing something wrong?

When on splash, if I attempt fastboot -i 0x1bbb devices, nothing happens. If I try fastboot -i 0x1bbb devices while device is just normally on, I just get 'waiting for device'.

adb reboot-bootloader doesn't seem to be actually booting up my tablet fully and will only stay on the alcatel splash screen. All drivers are installed, I'm in the proper directory in command prompt that have adb/fastboot files.

Thanks guys!
[General Questions and Answers] crashnova:
same with me.
[General Questions and Answers] titanshadow:
Sorry to intrude on your thread. I have the Sprint model for this tablet. I am not a developer but I have spent a lot of time rooting on Android... My basic question is, will this process work with the Sprint model? It is model 9007T with board msm8909 (Qualcomm Snapdragon). I haven't found a source for how to restore my device if I screw it up though and I was hoping to debloat this thing since it only leaves 4Gb for user apps in the internal memory and I can't move apps to the SD Card.

Any help would be appreciated.
[General Questions and Answers] blastradius14:
Ensure your drivers say ADB Bridge or something similar to this. Just because your ADB drivers worked flawlessly for when the system was booted, the bootloader may confuse Windows. Just find it in the driver manager and force it to use any of the ADB drivers presently on your computer. I use the Google drivers for the ADB, unmodified and still function just fine.

I found where the silly update app throws the update.zip > /data/data/com.android.jrdfota/download/

Putting stock recovery on, with stock system allowed the system to update.

The bootloader remained unlocked.

The adb access for fastboot was still there. I pushed twrp and rooted.

Good to go.
[General Questions and Answers] blastradius14:
I would add a picture to describe how to fix a driver issue in Windows, but I've posted less than 10 posts...

So, try to follow along.

A. Several easy ways to get to driver manager.

1: Click on the Windows Explorer button default from Windows. Win7-10 has this, it looks like a folder. On the left column, you'll see My Computer, This PC, or something like this. Where you can find your hard drives, removable media, etc. Right click on My Computer / This PC / whatever and click manage.

2. If for some reason you've removed Windows Explorer button, but have a start button, you can still right click on my computer / this pc and click manage.

3. If for some reason you have none of these options because you have mutilated your desktop, or simply do not have a start button, Hold down the windows key on the keyboard and press R, type devmgmt.msc and press enter.

B. Click Driver Manager.

1. Inside,

if

you've installed an ADB driver, and have an android connected, with ADB bridge enabled, you

should

see ADB Interface as a section, near the top.

If you have a device connected, and ADB is enabled on the android device, but the ADB doesn't show, and a yellow triangle/unknown device appears below in "Other Devices", this is likely your offending ADB device.

2. Right click that yellow device, and update driver. Browse my computer > Let me pick > ADB Interface > pick one
[General Questions and Answers] :
I don't think this will work because the T-Mobile tablet uses a different msm chipset.
[General Questions and Answers] :
here's the device tree and vendor blobs for our device. Those of you interested in helping port our device to cm feel free to help!

https://github.com/aclegg2011/proprietary_vendor_alcatel

https://github.com/aclegg2011/android_device_alcatel_9600w
[General Questions and Answers] Mr. Barker:
Thanks for the root instructions! :cool:
[General Questions and Answers] OriginalHardwyre:
My device is recognized just fine while the tablet is booted into the OS... but the second I reboot into the bootloader, windows stops recognizing the device AT ALL. I tried reinstalling drivers and even manually selecting the driver from file... it refuses to acknowledge that the drivers that WORK AFTER THE TABLET BOOTS INTO THE ROM are the same required to recognize it while in recovery mode. Windows 7 x64.
[General Questions and Answers] Doyle524:
Does this mean that the last thing we need before we can make and port ROMs is the kernel source?
[General Questions and Answers] :
Yes. We need some files for a custom kernel to boot correctly on our tablets.
[General Questions and Answers] Doyle524:
Is that something we should pester Alcatel about, or is it possible to reverse engineer it? And for the laypeople here, what can we do to help out?
[General Questions and Answers] tat2edfreeky1:
How to manage root on a 9006w Pixi while totally screwing up...

Ok so I buy a used Pixi yesterday it's updated all the way 5.0.2 and the first thing I do is unlock the developer settings and turn on debugging. Then I download Kingroot and let it run...root achieved. So far so good but I want SU and TWRP on it so off to XDA forums I go. Cool I see aclegg2011 already has figured out on post 45 how to do it. I download the stock boot, stock recovery and TWRP recovery. I already have fastboot and SU 2.46zip from beating my head on my Verizon Note 2 for 8 hours+ so I'm thinking I'm ahead of the curve :cool: . I plug the Pixi into my Dell laptop running Windows 10, the tablet shows right up in Windows Explorer, going great so far! Copy SU and TWRP onto the Pixi's internal storage...put the first command into fastboot window and nothing. Won't read the tablet...dang! Off to device manager there's my old friend the yellow triangle. Back to the posts I go. Hey look YarsRevenge78 made a driver for the problem awesome. Go to install the driver and nope, no way forget it Windows won't let them install. Seriously? you have got to be kidding. Off to bang my head on it for a while, change compatability...nothing. Go through and unblock every file in properties...nope forget it. Back to the forum again, hey here's a nifty trick to turn off that stupid Security that's hosing me. Finally get the drivers installed and hey look the yellow triangle is gone. ADB still won't see the darn tablet!!!! At this point I am sick of this tablet already, but I'm stubborn and no tablet and uppity Dell laptop are going to beat me. I remember a program I got off Google Play for my Note 2 after I finally won that battle. I'm like what have I got to lose? Keep in mind I got no Bootloader Unlocked and no TWRP recovery on the blankity-blank tablet yet!!! Google Play here I come ready or not lol. i download Rashr, rename TWRP recovery just recovery.img copy it on the tablets internal storage, flash it via Rashr. Then when i boot to recovery with Rashr, TADA TWRP recovery. Flash SU 2.46 and reboot Pixi. You'd think It would be over, mission accomplished right? Uhuh SU won't update the binaries! ARRRRGGGGHHH thump my head a couple times on the wall because man it feels just so darn good. Luckily I had SU 2.61 from earlier adventures of the same kind, binaries didn't wanna update on the Note 2 either. Flash that with Rashr and finally all rooted and SU is a system app. all without unlocking bootloader. :confused::confused:
[General Questions and Answers] Mr. Barker:
Is it possible to change the bootlogo on this device?

Not the boot animation, but the simple white-on-black text logo that appears when you push the power button.

I didn't find instructions anywhere and I also couldn't locate the bootlogo file using Root Explorer...

Help appreciated, thx.
[General Questions and Answers] DJ_SpaRky:
I recently got a notification to download a newer update. I'm in the process of reverting to stock and allow the update to proceed. I would like to get a stock system image once that has completed. Please advise the best way to do this so that I can share it.

Thanks.
[General Questions and Answers] titanshadow:
I have posted here before. I have a 9007t model of this tablet (Sprint) and I finally got the device rooted, so now I'm trying to find a custom recovery to install. Would the one posted here work? I believe I have backed up the stock recovery and thus can (in theory) go back if something bad happens. Problem is that I'm not entirely sure and want to get a little information before I make the plunge.
[General Questions and Answers] AladinTECH:
Can someone send me guide to root Alcatel Pixi 4 7" Model 9003X
[General Questions and Answers] EarthboundHero:
Anyone one know the best way to update to the latest OTA after rooting?