Alcatel One Touch Pixi 3 (7) Model 9007T - Soft Bricked - Android Q&A, Help & Troubleshooting

I have two of the units mentioned in the thread title. One simply is stuck at the Alcatel logo after a reboot. I can get into the stock recovery, have done a factory reset (plus cache), but still just stuck at the logo. I've also popped it open and unplugged the battery (it's the attached kind), but still back at a logo after everything was back together.
I mentioned that I had two because the other one is working fine and available to use for a firmware dump. The issue I'm running into is that a cat /proc/mtd command returns no partitions (just blank) and there is no emmc on this unit. From what I've read, bad Chinese firmwares sometimes do not report out partition tables from mtd. So, all the guides I've found for using MTK Rom Studio, MTK Droid Tools, and SP Flash Tool don't work for me (at the moment) because I cannot produce a firmware.info or scatter file, due to mtd not populating the required info. Also, from what I gather, there is no firmware file available for this. I've tried using the Mobile Upgrade program from Alcatel, but it reports that the ROM is the most up-to-date and then quits. Yay.
Any help or insight would be greatly appreciated. I'm not desperate or anything; just hoping to get this one back working is all.

---

my_former_self said:
I have two of the units mentioned in the thread title. One simply is stuck at the Alcatel logo after a reboot. I can get into the stock recovery, have done a factory reset (plus cache), but still just stuck at the logo. I've also popped it open and unplugged the battery (it's the attached kind), but still back at a logo after everything was back together.
I mentioned that I had two because the other one is working fine and available to use for a firmware dump. The issue I'm running into is that a cat /proc/mtd command returns no partitions (just blank) and there is no emmc on this unit. From what I've read, bad Chinese firmwares sometimes do not report out partition tables from mtd. So, all the guides I've found for using MTK Rom Studio, MTK Droid Tools, and SP Flash Tool don't work for me (at the moment) because I cannot produce a firmware.info or scatter file, due to mtd not populating the required info. Also, from what I gather, there is no firmware file available for this. I've tried using the Mobile Upgrade program from Alcatel, but it reports that the ROM is the most up-to-date and then quits. Yay.
Any help or insight would be greatly appreciated. I'm not desperate or anything; just hoping to get this one back working is all.
Click to expand...
Click to collapse
I'm not sure how to fix your device without knowing more about it. Is it possible you could provide the firmware dump of the one that is working? I was interested in using such to get a working TWRP recovery going for this model. With a working recovery, might be able to do more for your bricked unit.
I can provide some of the images - a noted exception is for the System partition, as I have already mucked with that one while doing my experimentation with my own.
If you already have the working one rooted, I would suggest just using dd and looking under /dev/devices/by-name (I think that is what it is called) which should provide you access to the partitions you need and what they are called.

---

titanshadow said:
I'm not sure how to fix your device without knowing more about it. Is it possible you could provide the firmware dump of the one that is working? I was interested in using such to get a working TWRP recovery going for this model. With a working recovery, might be able to do more for your bricked unit.
I can provide some of the images - a noted exception is for the System partition, as I have already mucked with that one while doing my experimentation with my own.
If you already have the working one rooted, I would suggest just using dd and looking under /dev/devices/by-name (I think that is what it is called) which should provide you access to the partitions you need and what they are called.
Click to expand...
Click to collapse
Thanks for the reply. Let me see what I can do. This model is very odd, I have to admit. The fact that it does not use emmc, but instead mtd, yet a cat /proc/mtd produces nothing is baffling to me.

---

my_former_self said:
Thanks for the reply. Let me see what I can do. This model is very odd, I have to admit. The fact that it does not use emmc, but instead mtd, yet a cat /proc/mtd produces nothing is baffling to me.
Click to expand...
Click to collapse
What you're trying to do is for older MTK phones....as in like everything not just the cat /proc/mtd.
What you have to do it make a backup of your working tab and flash the brick tab with the back up.
Here's some links that can help you:
MTK Preloader drivers for Win 7- https://thebroodle.com/microsoft/win...rs-in-windows/
MTK Preloader drivers for Win 10- http://laurentiumihet.ro/windows-10-...tion-tutorial/
How to create a scatter file- https://androidmtk.com/create-scatte...or-mtk-devices
How to make a backup of your phone/ROM- https://forum.hovatek.com/thread-526.html
After making a backup, restore your ROM_0 backup using this method-----> http://forum.xda-developers.com/showpost.php?p=65784715&postcount=953
Check out this thread as it relates to all things Pixi----> http://forum.xda-developers.com/android/general/root-alcatel-one-touch-pixi-34-official-t3193624
Good luck

---

Can I get a copy kind that back up

---

kirito9 said:
What you're trying to do is for older MTK phones....as in like everything not just the cat /proc/mtd.
What you have to do it make a backup of your working tab and flash the brick tab with the back up.
Here's some links that can help you:
MTK Preloader drivers for Win 7- https://thebroodle.com/microsoft/win...rs-in-windows/
MTK Preloader drivers for Win 10- http://laurentiumihet.ro/windows-10-...tion-tutorial/
How to create a scatter file- https://androidmtk.com/create-scatte...or-mtk-devices
How to make a backup of your phone/ROM- https://forum.hovatek.com/thread-526.html
After making a backup, restore your ROM_0 backup using this method-----> http://forum.xda-developers.com/showpost.php?p=65784715&postcount=953
Check out this thread as it relates to all things Pixi----> http://forum.xda-developers.com/android/general/root-alcatel-one-touch-pixi-34-official-t3193624
Good luck
Click to expand...
Click to collapse
Thanks. Sorry for the ridiculous delay; life happened. Anyways, I cannot create a scatter file (from the working unit), just as before.; it gives me no partitions.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

---

Alcutel pixi 3 (7) 4G 9007T tablet soft bricked
decided to play around with cleaning up the bloatware and Sprint installed junk on my Alcutel one touch pixi 3 (7) 4G 9007T tablet running originally android 5.1.1 , and ended up soft bricked stuck in a loop cycle of optimizing/staring apps, have scoured XDA and every other resource i have seen and for every device but this one there seems to be a fix, a stock rom, etc ,... one good thing is i am able to factory reset to at least enable debugging for adb access (though fastboot wont detect it) and hence cant get the device into a fastboot mode or unlock the loader.
Is there any compatible roms or recoveries out there for this particular device
Recovery <3e> Android L(not sure how to get a recovery log dump for providing more info)
I used nobloat app from google play had things pretty well cleaned up but thought to see how far i could go and i used the backup function in the app, but evidently i deleted something I shouldn't have and of course after trying a factorry rest the nobloat backup would be gone even if i could get botted back up)
after recovery I do get through the intitial setup, wifi, google account login etc,.. (using safemode) but if i use google backup files it gets to the loop fast, so i try to skip all that being restored, and am able to get to the settings to enable developer mode /debugging mode but once I exit that its a blank screen outside the clock showing then it reboots and keeps in the abov mentioned loop.
(as i mentioned adb detects the device but fastboot won't it just stuck on "waiting for any device"