[ROM[6.0.1][VFD-1400][OFFICIAL] Vodafone Prime Tab 7 - Miscellaneous Android Development

Pretty tricky to find anything for this tablet, but I managed to find a way to get an official image.
What you need:
Alcatel Mobile Upgrade Q 5.1.7 (or newer), get it here.
This will overwrite all your data on the device.
1. Install Mobile Upgrade Q
2. Run "C:\Program Files (x86)\Mobile Upgrade Q\tool\usb_driver\installdriver\DriverInstaller.exe" to install the USB Drivers.
3. Enable USB Debugging
4. adb reboot edl
5. Mobile Upgrade Q and select "VF1400" (note it also lists 9030G and 9030Q, the unbranded variants of this tablet (yet unreleased?), but unfortunately you can't flash these, it will just download the Vodafone branded image)
6. It will download the image files into "C:\Program Files (x86)\Mobile Upgrade Q\bin\download" (note while it's downloading the image files, these are just filled with 0s)
7. After it downloaded the image it starts flashing ("initialisation") and you can copy the files to some place safe (from bin\VF1400-2AVDXXX), it deletes some after it's done
B1BEB0B0CD00.mbn is the boot image, R1BEB0B0CD00.mbn the recovery. Some of the files have partition information, probably can use these to flash with QPST.
Going to have a look into compiling a TWRP, now that I have the kernel

Also, Alcatel seems to have released a *very incomplete* kernel source (build scripts and other things missing) over at https://sourceforge.net/projects/alcatel/files/, see OT_VDF_1400_20160520.tar.xz.
A bummer since the kernel in the official image seems to have all kinds of debugging stuff enabled.

Some more findings. You can coax SUGAR QCT_SP (and maybe Alcatel Mobile Upgrade Q 5.1.7?) into flashing any images.
Before starting SUGAR QCT_SP, copy your backup of the VF1400-2AVDDE1 folder into bin/. It should flash these files.
I flashed a ported recovery, but I couldn't boot it (always boots stock recovery). I guess because of secure boot? Read something about the recovery-from-boot.p file...
Don't worry about bricking, you can get the tab into edl mode with an edl cable. http://xiaomitips.com/guide/miui-deep-flash-engineering-cable-solution-to-non-edl-device/

Some progress, if anyone cares :laugh: (doubt it).
Flashed boot with altered build.pros, selinux is off, but adb root kills the adbd.
Same on recovery, but kind of pointless with zip verification. Now it's either compile a recovery or add a custom key too boot and sign the supersu zip myself.
Also flashed a slimmer system, minus all the google apps I don't use anyway. Stock image carries 1GB of empty space that is being flashed every time

One more interesting thing: You can get into fastboot by flashing a recovery with the wrong kernel and then booting to recovery. Fastboot is crippled though and does nothing useful, can't even flash with it.
Btw to turn off the device if you are stuck in a bootloop to recovery: With usb cable unconnected, hold Power and Volume down. It screen goes black after 5 sec, keep holding the buttons. It should come up again and very shortly after, let go of the buttons screen when the screen goes black a second time.

So, at the moment there is no way to root?
Geeting the device tomrrow

Yes there is. After getting rid of selinux, you can get temporary root using dirty cow, or bake supersu into the boot or system image.
Also I'm working on porting a recovery. It works, more or less already.

I just flashed SuperSU via the recovery I ported. Seems to work

Nice! Is it possible to Upload your Recovery? Simply flash via Fastboot?

gella1992 said:
Nice! Is it possible to Upload your Recovery? Simply flash via Fastboot?
Click to expand...
Click to collapse
I can upload it later.
Fastboot is crippled and you can't boot into it directly, at least on mine. Try booting into it (hold power + vol down). Otherwise see my earlier posts on how to do the initial flash. A little inconvenient, but it's only once
Will post detailed instructions with the recovery.

gella1992 said:
Nice! Is it possible to Upload your Recovery? Simply flash via Fastboot?
Click to expand...
Click to collapse
https://forum.xda-developers.com/android/development/recovery-vodafone-prime-tab-7-t3548560

Working on a frankenkernel with some salvaged parts from the incomplete kernel source from alcatel: https://github.com/852Kerfunkle/android_kernel_vodafone_vfd1400
Works for booting into recovery.

While trying some things with caf android builds, I flashed aboot, thinking I could always get back into download mode with the makeshift EDL cable. Turns out you can't.
Do not mess with aboot unless you are 100% sure (unlike me). The device will only register as HS-USB Diagnostic 900E. Even with an EDL cable.
For anyone who did: your device is not dead, but it's a bit of a mission.
1. Take of the back cover: Remove the screw behind the sim/sd latch and open the device with one of these plastic opener thingies, start at the latch.
2. Bridge the pin marked on the image (take a cable and connect the pin to the ground of the usb connector, i.e. the metal bit).
3. Plug in the usb cable.
4. It should register as HS-USB QDloader 9008 (assuming you have the right drivers).
5. Flash with Sugar.

Hopefully everything is working great again!
Do you think it would be possible to port a Lineage OS to this Tab?
I know how to compile from source, but actually not developing a Rom

gella1992 said:
Hopefully everything is working great again!
Do you think it would be possible to port a Lineage OS to this Tab?
I know how to compile from source, but actually not developing a Rom
Click to expand...
Click to collapse
Yeah it's working alright again, thanks
I tried, no luck yet. Am stuck on a crash in libsdm. Once I had it boot to the point where it was initialising the apps (dexopt or whatever?), but it crashed right after.
For now I am focusing on codeaurora android. If I get that working, maybe the caf parts can be used to make a working LineageOS build.
I also have little to no idea how to do anything android related, so most of the time is spent reading and googling silly errors. Just give it a go, if you get stuck I can help out with what I found so far.

At the moment I am busy. Will give it a try when I have more time :fingers-crossed:

fused#1 said:
Working on a frankenkernel with some salvaged parts from the incomplete kernel source from alcatel:
Works for booting into recovery.
Click to expand...
Click to collapse
Are you still working on this ?
I'm currently considering the option of running a git diff against the CAF msm-3.18 "LA.UM.5.1-03210-8x37.0" TAG/branch, which the released incomplete kernel source appears to be based on.
Then going through the patches and applying them one by one on the newest CAF 8937 TAG/branch.
Although getting LA.UM.5.1-03210-8x37.0 to work with the patches applied would be nice already.
My ultimate goal is OMNI, im not interested in CM/Lineage.
Problem is at the moment i don't have much time for this.
But we'll see :good:

nevexc said:
Are you still working on this ?
I'm currently considering the option of running a git diff against the CAF msm-3.18 "LA.UM.5.1-03210-8x37.0" TAG/branch, which the released incomplete kernel source appears to be based on.
Then going through the patches and applying them one by one on the newest CAF 8937 TAG/branch.
Although getting LA.UM.5.1-03210-8x37.0 to work with the patches applied would be nice already.
My ultimate goal is OMNI, im not interested in CM/Lineage.
Problem is at the moment i don't have much time for this.
But we'll see :good:
Click to expand...
Click to collapse
Hey,
That's pretty much what I was doing before I got caught up in other stuff
Was stuck at trying to figure out how to actually build caf android. Which of the files on the rom belong the the proprietary blobs and how to properly include them in the makefiles so it actually builds...
Hit me up with a PM, maybe we can coordinate our efforts :fingers-crossed:

Thanks for this Guide, but I have a quick question:
I am currently trying to restore my VF-1497 to a stock rom with Mobile Upgrade Q 5.1.7, but the Upgrader always kicks my Tablet out of edl, and throws the error:
'There is no greater version available to upgrade your phone, actual version of your phone is the latest'
Is there any way to restore this device back to stock?
Thank you in advance

ASP
Hi is there a custom "clean" firmware for vdf1400 that can go instead of the latest 6.0.1 150fkg1

Related

Installing Cupcake on your ROOTED G1 (or Dev phone)

Edit 4/16/2009: New build published on my website:
http://www.koushikdutta.com/2009/04/have-you-cupcake-and-eat-it-too.html
The linked instructions on my blog will stay up to date, I can't guarantee this post will. I recommend going to my site to get full up to date instructions: http://www.koushikdutta.com/2008/12/building-android-source-and-deploying.html
Summary:
This is simply a build of the Android source tree with the Maps application included. Note that this does not have Gmail, YouTube, Market, or IM.
This is just a preview of what is to come in the next OTA update. I would not say this is a really usable build by any means.
Here is the list of new features: http://source.android.com/roadmap/cupcake
Installation prerequisites:
You must have a rooted (or a dev) phone.
Installation:
Install the JesusFreke's RC30 V1.3. This will give you a root shell root access in recovery mode. A root adb shell is required for the next step. http://forum.xda-developers.com/showthread.php?t=443713
Install the engineering boot loader. http://forum.xda-developers.com/showthread.php?t=455860
Download the cupcake installation images to your computer. Extract them to a folder somewhere. http://koushikdutta.blurryfox.com/G1/cupcake.zip
Start your phone up into fastboot mode. You can do this by shutting your phone off, and holding camera and power. You will see Androids on skateboards.
Connect your phone to your computer. Press the back button on your phone until your screen says FASTBOOT.
Go to a terminal on your computer and navigate to your extracted files and type:
chmod a+x fastboot
./fastboot flash system system.img
./fastboot flash boot boot.img
./fastboot flash userdata userdata.img
./fastboot reboot
If your phone hangs for a long time while flashing or rebooting, unplug and reconnect your phone. I run into this issue, and that is how I work around it.
Done!
Do it Yourself Instructions
Follow these instructions to get the Android source: http://source.android.com/download
Follow these instructions to target Dream hardware and generate the images: http://source.android.com/documentation/building-for-dream
At the time of writing, the Android Dream build was broken. I needed to do the following to make it work:
Several (relatively minor) changes in the Dream audio driver code to fix compilation issues.
Copied libOmxCore.so to mydroid/out/target/product/dream/system/lib (this was a missing step in the Building for Dream documentation, and something that should be in the HTC provided script)
Patching in Maps (or other files) into your system.img
Copy Maps.apk from a Android Dev Phone 1 into mydroid/out/target/product/dream/system/app
Copy com.google.android.maps.jar from a from a Android Dev Phone 1 into mydroid/out/target/product/dream/system/framework
Delete mydroid\out\target\product\dream\obj\PACKAGING\systemimage_unopt_intermediates\system.img
Delete mydroid\out\target\product\dream\system.img
make
Eeeeexcellent. I'm assuming this wipes all the settings from your phone, yeah?
IzzeLing said:
Eeeeexcellent. I'm assuming this wipes all the settings from your phone, yeah?
Click to expand...
Click to collapse
Yes. You can also undo all changes by just reflashing JF's RC30 image.
For those who are already running cupcake, how is the updated browser with the new javascript engine? Is it much faster than rc30?
Nice walkthrough. I resynced with the repo after jbq announced cupcake was merged in but still had some issues with the radio for some reason. At this point I figure i'm just going to wait it out for the official update, as my G1 is still my daily driver.
One note on the installation instructions: I believe you have to hook up the USB before pressing the back button for FASTBOOT to show up. I'm sure most folks interested in this will figure it out easily enough. Also, i'm glad you had a positive experience with flashing from VMware. After learning an expensive lesson in the past i've always booted into real Linux for any kind of flashing or development operation.
jashsu said:
Also, i'm glad you had a positive experience with flashing from VMware. After learning an expensive lesson in the past i've always booted into real Linux for any kind of flashing or development operation.
Click to expand...
Click to collapse
With the NAND backup/restore tool and some basic knowledge of how this all works, I'm not too worried about bricking the G1. I actually erased the system partition and booted just to see what would happen, hehe.
And even if I do brick it, I have a another backup G1 on my desk.
jashsu said:
Nice walkthrough. I resynced with the repo after jbq announced cupcake was merged in but still had some issues with the radio for some reason. At this point I figure i'm just going to wait it out for the official update, as my G1 is still my daily driver.
One note on the installation instructions: I believe you have to hook up the USB before pressing the back button for FASTBOOT to show up. I'm sure most folks interested in this will figure it out easily enough. Also, i'm glad you had a positive experience with flashing from VMware. After learning an expensive lesson in the past i've always booted into real Linux for any kind of flashing or development operation.
Click to expand...
Click to collapse
Hmm, I tested calling and it worked fine for me. Are you sure you made a Dream targeted build?
Koush said:
With the NAND backup/restore tool and some basic knowledge of how this all works, I'm not too worried about bricking the G1. I actually erased the system partition and booted just to see what would happen, hehe. And even if I do brick it, I have a another backup G1 on my desk.
Click to expand...
Click to collapse
Infernix's nand scripts in conjunction with the engineering bootloader do provide a significant safety net for installing custom Android builds.
Hmm, I tested calling and it worked fine for me. Are you sure you made a Dream targeted build?
Click to expand...
Click to collapse
Yeah I performed the steps on the build-for-dream page. I think it was more of a matter of just needing to blowing away my local repository and getting the entire thing fresh? The keyboard is nice. I'm also optimistic about the new JS engine, but imo some kind of ad-blocking ability would be much more low hanging fruit in terms of speeding up pageloading.
How is the camera so far in cupcake?
Wow, I just put this on my phone and you arent kidding when you say it is not usable by any means. The APNs arent even programmed in
I installed it to play with it and the new on screen keyboard is nice. I cant wait for this to be live, and of course, ill wait until there is a hacked way to update to the new version. If you plan on keeping root, DO NOT get this OTA when it comes out.
For some reason I can't get fastboot to recognize my device... It just gets stuck at the waiting for device task. Tried it across my laptop, desktop, and VM Linux, so must be me doing something wrong.. Any clues? I've tried removing/plugging in the G1 and it is definitely in FASTBOOT mode.
jashsu said:
Nice walkthrough. I resynced with the repo after jbq announced cupcake was merged in but still had some issues with the radio for some reason. At this point I figure i'm just going to wait it out for the official update, as my G1 is still my daily driver.
One note on the installation instructions: I believe you have to hook up the USB before pressing the back button for FASTBOOT to show up. I'm sure most folks interested in this will figure it out easily enough. Also, i'm glad you had a positive experience with flashing from VMware. After learning an expensive lesson in the past i've always booted into real Linux for any kind of flashing or development operation.
Click to expand...
Click to collapse
IzzeLing said:
For some reason I can't get fastboot to recognize my device... It just gets stuck at the waiting for device task. Tried it across my laptop, desktop, and VM Linux, so must be me doing something wrong.. Any clues? I've tried removing/plugging in the G1 and it is definitely in FASTBOOT mode.
Click to expand...
Click to collapse
Make sure that in your Ubuntu VM, "High Composite Device" is checked in the removable devices list. Then unplug it, and plug it back in.
Koush said:
Yes. You can also undo all changes by just reflashing JF's RC30 image.
Click to expand...
Click to collapse
Im trying this now and it isnt working. It reflashed, but im stuck on the android screen with android just sitting there flashing...
Help?
staulkor said:
Im trying this now and it isnt working. It reflashed, but im stuck on the android screen with android just sitting there flashing...
Help?
Click to expand...
Click to collapse
Did you successfully flash all three files?
Regardless, the initial boot takes quite a while (several minutes). It needs to optimize all the APK files using DexOpt.
Koush said:
Did you successfully flash all three files?
Regardless, the initial boot takes quite a while (several minutes). It needs to optimize all the APK files using DexOpt.
Click to expand...
Click to collapse
You may not have understood me correctly. I got cupcake installed and working! But it just isnt usable as an every day phone. Im trying to go back to JF's RC30 but it wont. It flashed successfully, but now when I turn on the phone, it is stuck at the android loading screen. I have rebooted the phone a few times and its been sitting here for 15 minutes.
staulkor said:
You may not have understood me correctly. I got cupcake installed and working! But it just isnt usable as an every day phone. Im trying to go back to JF's RC30 but it wont. It flashed successfully, but now when I turn on the phone, it is stuck at the android loading screen. I have rebooted the phone a few times and its been sitting here for 15 minutes.
Click to expand...
Click to collapse
Oh, I see. Make sure you hard reset too. If hard resetting does not work, I'll give you a boot.img and recovery.img to flash.
You can hard reset holding Power and Home. Then press Alt-L to bring up the menu, and Alt-W to wipe.
Koush said:
Oh, I see. Make sure you hard reset too. If hard resetting does not work, I'll give you a boot.img and recovery.img to flash.
You can hard reset holding Power and Home. Then press Alt-L to bring up the menu, and Alt-W to wipe.
Click to expand...
Click to collapse
Why didnt i think of that, lol. JF RC30 update + hard reset = revert back from cupcake. Thanks man, I owe you
If not recognizing the device go into full root mode.
Sudo su and try again
So is the phone useable after flashing this "homemade" cupcake?
LGSilva said:
So is the phone useable after flashing this "homemade" cupcake?
Click to expand...
Click to collapse
You can call and such, but a lot is missing. Read the post!

[Q] Stuck booting

Hello, my name is Shagington
I have been slowly unlocking the potential of my tf700t, yet I have come to a point where I am stuck loading the android OS. The problem started when I installed xposed to gain the ability to modify the permission of apps. Now it just sits with the loading circle spinning around and 'round. I tried wiping from the bootloader yet the same thing happens. While looking into the bootloader more, I found twrp installed after what I thought were many failed attempts. I tried a wipe from that as well and the same thing happens. I was thinking about just flashing a stock (rooted) rom with twrp but I am afraid of getting into a worse spot than I already am in, any help is appreciated.
Thanks, Shag
You need to post your bootloader version (read the tiny script when you boot with Power and Volume Down) and your recovery version.
That will determine what you can flash or what type of repair you can try.
Do you have fastboot and adb setup on your PC?
Check if you have a fastboot connection when booted into the bootloader and adb when booted into recovery.
See if you can capture a logcat of the boot process in adb.
Then report back.
Whatever you do, do not use the Wipe Data option from the bootloader!!!!!!!!!
Thank you for the quick reply berndblb, it seems im on build us 10.6.1.14.8-20130514. I just reformatted my pc to windows 10 tech preview so im not quite sure how that will work with adb but I will give it a go tomorrow. Will any custom rom work with the current build i have?
Thanks again, Shagington (Newbington)
shagington said:
Thank you for the quick reply berndblb, it seems im on build us 10.6.1.14.8-20130514. I just reformatted my pc to windows 10 tech preview so im not quite sure how that will work with adb but I will give it a go tomorrow. Will any custom rom work with the current build i have?
Thanks again, Shagington (Newbington)
Click to expand...
Click to collapse
Yes, there are. You are one version behind to the latest (and last) bootloader 10.6.1.14.10. Might be a good idea to update to the latest while you're at it...
Which recovery and version thereof did you flash?
Once we are sure that you have compatible software installed you can flash a bootloader/TWRP package to get you up to date, but let's resolve your current pickle first.
berndblb said:
Yes, there are. You are one version behind to the latest (and last) bootloader 10.6.1.14.10. Might be a good idea to update to the latest while you're at it...
Which recovery and version thereof did you flash?
Once we are sure that you have compatible software installed you can flash a bootloader/TWRP package to get you up to date, but let's resolve your current pickle first.
Click to expand...
Click to collapse
Thanks again for responding good sir, I am on twrp 2.8.5.0, which still loads just fine.
-shagington
When you install xposed it puts an emergency uninstall zip on the internal sdcard partition. Try flashing that from twrp to reverse it out.
Be careful with xposed it can sofbrick easily as you have found out.
shagington said:
I just reformatted my pc to windows 10 tech preview so im not quite sure how that will work with adb
Click to expand...
Click to collapse
I tried the first Win10 preview, and I just had to connect the tablet and run adb.exe - it worked fine with the automatically installed drivers.
Thanks for the replies guys, I couldnt find any zips on my internal, I looked through almost every folder. After looking through the adb tutorials, it is a little to intimidating for me. Kinda sad, I was under the impression that now I have twrp I could just throw some other rom on quickly or even a download a backup from someone else with the same versions to recover and be done with it. I think im just going to leave it soft bricked for a while and use my nexus 7 for now. Appreciate the help guys, it's just a little over my head.
-Shag

Won't upgrade Factory Software, Wont enter recovery. Hangs on boot

First off, my tablet isn't bricked. I can boot it up fine. But when I try to install the factory downloaded software it just hangs on boot indefinitely. Similar things happens if I try to enter recovery. It goes fine until I have to press Volume ^, then it just freezes and I have to hold down the power key for 10 seconds. I've searched around and all I can find is threads from people stuck in a boot loop. Any help appreciated
A little more information. This tablet has been sitting for a while because it was such a disappointment. Before I decided I was fed up with it, it looks like I unlocked and rooted it. Iooks like I may have also tried to install Clockwork Mod on it. Trying to fix it has reminded me of why I stopped using it in favor of my nexus 7. The UI feels like it was designed specifically to make people not want to use tablets.
The problem probably is the How.
And unfortunately you don't give us any info on that.
Why do want to flash stock if you hate it so much?
If you have CM on there you should have a custom recovery installed.
Which one?
What's the bootloader version?
And lastly, you can boot into fastboot mode? The screen with the 3 icons?
If yes, almost anything is fixable.
But you need to give us more info.
berndblb said:
The problem probably is the How.
And unfortunately you don't give us any info on that.
Why do want to flash stock if you hate it so much?
If you have CM on there you should have a custom recovery installed.
Which one?
What's the bootloader version?
And lastly, you can boot into fastboot mode? The screen with the 3 icons?
If yes, almost anything is fixable.
But you need to give us more info.
Click to expand...
Click to collapse
@berndblb. Thanks for the reply. It has been so long since I did anything with this tablet that I completely forgot what I had been doing since the last time I was trying to make up for it deficiencies. I seem to have gotten everything sorted. Uninstalled then reinstalled Busybox & Supersu. Then used TWRP's apk to re-install custom recovery 3.0. Install said it failed, but when I booted into the bootloader I could actually make a selection, instead of it hanging indefinitely while it tried to load the recovery. Win for me I guess. Finally able to make a backup which always feels good. The whole point of this is to install a custom ROM so that my tablet becomes more than a really expensive coffee table decoration.
The current install on my device is. Android 4.1.1, Kernel 3.1.1, & build 10.4.4.23-20121171
Any suggestions on moving forward and a recommendation on a clean ROM would be appreciated. But I can always take the time to read as well.
RussTdesign said:
@berndblb. Thanks for the reply. It has been so long since I did anything with this tablet that I completely forgot what I had been doing since the last time I was trying to make up for it deficiencies. I seem to have gotten everything sorted. Uninstalled then reinstalled Busybox & Supersu. Then used TWRP's apk to re-install custom recovery 3.0. Install said it failed, but when I booted into the bootloader I could actually make a selection, instead of it hanging indefinitely while it tried to load the recovery. Win for me I guess. Finally able to make a backup which always feels good. The whole point of this is to install a custom ROM so that my tablet becomes more than a really expensive coffee table decoration.
The current install on my device is. Android 4.1.1, Kernel 3.1.1, & build 10.4.4.23-20121171
Any suggestions on moving forward and a recommendation on a clean ROM would be appreciated. But I can always take the time to read as well.
Click to expand...
Click to collapse
The first thing you should have done is upgrade your bootloader to the latest version. I would not actually use TWRP 3.0 for anything at this point if I were you. I have no idea if TWRP 3.0 works with that ancient JB 4.1 BL you got there, but I would not chance it. As a matter of fact, since you have to flash either stock rom or just the bootloader (and for both you use your recovery) I would highly recommend you flash an older TWRP version that is compatible with your BL. That combo - BL and recovery - is nothing you want to screw around with. You should go back to TWRP 2.4.1 or so.
TWRP Manager forced the latest TWRP version (developed for MM roms) on you and that's why I hate these apps! They do not check for compatibility at all....The proper way to flash a recovery is in fastboot and in fastboot only.
so I am going to give you a bunch of links and a general plan of attack, but you will have to do a fair share of reading.
First things is: Get fastboot working on your PC!!!!!! The first part of this guide I wrote way back tells you how: http://forum.xda-developers.com/showthread.php?t=2688891
Once you got that working flash TWRP 2.4.1 - instructions on how to are in the same thread. Reboot the tablet, then boot into TWRP.
Now flash the latest bootloader (Packaged with a slightly younger TWRP version from here: http://forum.xda-developers.com/transformer-tf700/general/firmware-10-6-14-10-twrp-t2867157
Reboot the tablet, then boot back into TWRP.
Now you again need to update your recovery to a version you can use with a current rom. I'd recommend this baby and it comes in a zip you can flash in your current recovery: http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395
Flash the Kang recovery, then reboot and boot back into TWRP.
Format your data partition in TWRP. It takes an hour or so but it does a great job of leaving you with a clean slate for the new rom and is required before you flash a major change (which you are doing in any case).
Now you are ready to flash a rom.
I am going to recommend a really old one and a really new one. There are plenty of others to choose from in the Development section, but none of them is still under active development.
CROMi-X Resurrected. Based on Asus stock anno JB 4.2.1 but modded and fine tuned to the gills. LMK still puts out an update now and then, but those are more fine tunings of the fine tuning. Very slight changes - nothing major is going to happen here anymore. But it's a very stable and well working rom for those that actually like the Asus interface. http://forum.xda-developers.com/tra...pment/cromi-x-5-4-resurrected-tweaks-t3273515
KatshMallow by Timudru. Yeah, Android MarshMallow for the TF700. Most Android users are still dreaming about MM and you can rock it on this ancient machine. And it's a beauty, just absolutely unbelievable what Tim has cooked up for this hardware. Trust me! Fantastic rom! http://forum.xda-developers.com/transformer-tf700/development/rom-t3282166
For both of them you should convert your data partition to f2fs which you can do in recovery. Instructions are here: http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
Actually, for CROMI-X Resurrected you don't have to do this - it's build into the rom installer.
You could try to short cut all this and just flash a new bootloader/recovery combo in your current TWRP 3.0. Maybe it works. Maybe it hardbricks your tablet. Nothing worse than trying to do something substantial (like flashing a bootloader) in an incompatible recovery....
Ok, now I shut up and let you read.
Have fun!
@berndblb thank you so much. I really appreciate you taking the time to help me out with this. This isn't my first time to the rodeo, but I'm def not ever going to ride in the pros. Trying to install a custom rom an this tablet has really shown my how much I don't know. I'm going to follow your instructions. I will get back later and let you know how it goes.
RussTdesign said:
@berndblb This isn't my first time to the rodeo, but I'm def not ever going to ride in the pros. Trying to install a custom rom an this tablet has really shown my how much I don't know. I'm going to follow your instructions..
Click to expand...
Click to collapse
I could tell. That's why you got the self-help version
I know how it feels. After 3 years I am fairly proficient on this device. But I still felt like a total n00b when I got the first Nexus! :cyclops:
So much of this stuff is so device specific... takes a while to sink your teeth into.
Enjoy.
berndblb said:
I could tell. That's why you got the self-help version
I know how it feels. After 3 years I am fairly proficient on this device. But I still felt like a total n00b when I got the first Nexus! :cyclops:
So much of this stuff is so device specific... takes a while to sink your teeth into.
Enjoy.
Click to expand...
Click to collapse
I have fast boot running and back-checked it via the fastboot devices. I downloaded twrp-2.4.1.0-tf700t.blob. the tried to load it. I keep getting a FAILED( command write failed (Invalid Argument)). Any thoughts
Plenty. Unfortunately Windows is very finicky with fastboot...
If push comes to shove you may want to try a Linux live CD or distribution and I'll add a link later, but try this first: and try "fastboot reboot" to see if you can execute anything.
Sure you got the original cable?
Reboot pc and tablet
Try a different USB port
Connect the tablet booted into fastboot and check the entry in Device Manager for problems.
Now we're getting desperate....
Boot into Android, check if you have a data connection by push/pulling a small file which you put into the same directory.
adb devices
adb push filename /sdcard/
adb pull /sdcard/filename
adb reboot-bootloader
Then see if you can do anything in fastboot.
http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
berndblb said:
Plenty. Unfortunately Windows is very finicky with fastboot...
If push comes to shove you may want to try a Linux live CD or distribution and I'll add a link later, but try this first: and try "fastboot reboot" to see if you can execute anything.
Sure you got the original cable?
Reboot pc and tablet
Try a different USB port
Connect the tablet booted into fastboot and check the entry in Device Manager for problems.
Now we're getting desperate....
Boot into Android, check if you have a data connection by push/pulling a small file which you put into the same directory.
adb devices
adb push filename /sdcard/
adb pull /sdcard/filename
adb reboot-bootloader
Then see if you can do anything in fastboot.
http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
Click to expand...
Click to collapse
Got fastboot running properly on my work computer with windows 7. I've gotten everything installed up to formatting the data partition. Doing that now. Super stressful & hard not to mess with it while it makes its way through a hour long process.
What did the trick to get fastboot working?
berndblb said:
Plenty. Unfortunately Windows is very finicky with fastboot...
If push comes to shove you may want to try a Linux live CD or distribution and I'll add a link later, but try this first: and try "fastboot reboot" to see if you can execute anything.
Sure you got the original cable?
Reboot pc and tablet
Try a different USB port
Connect the tablet booted into fastboot and check the entry in Device Manager for problems.
Now we're getting desperate....
Boot into Android, check if you have a data connection by push/pulling a small file which you put into the same directory.
adb devices
adb push filename /sdcard/
adb pull /sdcard/filename
adb reboot-bootloader
Then see if you can do anything in fastboot.
http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
Click to expand...
Click to collapse
Looks like I got it sorted. Decided on going with the KatKiss rom. And the performance is night and day. Thanks so much for all your help. Next time I will probably do more reading before I try anything more... But then again I tell myself I will read the instructions before I start assembling ikea furniture & never do. So only time will tell. Anyway. Thanks again.
berndblb said:
What did the trick to get fastboot working?
Click to expand...
Click to collapse
Installing it on a different computer. This one runs windows 7. My laptop runs windows 8.1, could be as simple as that. But who knows.

Fairphone Brick Fastboot / ADB

Hi there,
I looked at a lot of places but I cannot find decent info. Or the Info I search .
So maybe someone can point me to, or may be this thread could be the one...
(And if I missed a post with the right answer, I apologise in front)
So lets face it, I bricked my Fairphone 2. Yep. Whoehoew. :highfive:
What did i do:
Flashed the latest twrp 3.2.2 recovery
Flashed Lineage os 15.1 with gapps pico and su addon
Playing around. Nice working phone. (it is my second, the first one was stolen )
I tried to encrypt my phone. But I encountered the camera reboot to recovery problem. so no encryption. (and really, this is an old bug...?)
Few days later I update lineage os. I just read about the flashlight on workaround. So I tried. And yep, it worked, straight to twrp.
But.
my guess is that now two things happen at the same time. a sort of postponed encrypting. And a non understanding update.
A least. I see the twrp logo. and that is it. If i reboot nothing happens. no os.
I can boot into adb and fastboot, at least, my macbook running high sierra shows the device with adb devices and fastboot devices.
If i am in fastboot, and try to overwrite twrp it stil reboots to twrp 3.2.2.0, so it seems to do nothing. (even an "update" to twrp-3.2.2-0-FP2 does nothing)
It looks like all is locked. My guess is that os wise usb debugging is off? Or that all is hanging an some corrupted mangle between code.
Is there a way to hard format the phone? Do I use software for that? Are I unaware of some "magic" fastboot commands?
Any help is highly appreciated
I also post this at the FF2 Community. But I will post back and forth whatever solution i find.
Cheers,
Vincent
victor-zorro said:
Hi there,
I looked at a lot of places but I cannot find decent info. Or the Info I search .
So maybe someone can point me to, or may be this thread could be the one...
(And if I missed a post with the right answer, I apologise in front)
So lets face it, I bricked my Fairphone 2. Yep. Whoehoew. :highfive:
What did i do:
Flashed the latest twrp 3.2.2 recovery
Flashed Lineage os 15.1 with gapps pico and su addon
Playing around. Nice working phone. (it is my second, the first one was stolen )
I tried to encrypt my phone. But I encountered the camera reboot to recovery problem. so no encryption. (and really, this is an old bug...?)
Few days later I update lineage os. I just read about the flashlight on workaround. So I tried. And yep, it worked, straight to twrp.
But.
my guess is that now two things happen at the same time. a sort of postponed encrypting. And a non understanding update.
A least. I see the twrp logo. and that is it. If i reboot nothing happens. no os.
I can boot into adb and fastboot, at least, my macbook running high sierra shows the device with adb devices and fastboot devices.
If i am in fastboot, and try to overwrite twrp it stil reboots to twrp 3.2.2.0, so it seems to do nothing. (even an "update" to twrp-3.2.2-0-FP2 does nothing)
It looks like all is locked. My guess is that os wise usb debugging is off? Or that all is hanging an some corrupted mangle between code.
Is there a way to hard format the phone? Do I use software for that? Are I unaware of some "magic" fastboot commands?
Any help is highly appreciated
I also post this at the FF2 Community. But I will post back and forth whatever solution i find.
Cheers,
Vincent
Click to expand...
Click to collapse
Try reflashing it with the factory original firmware using their own flashing tool.
Once you got it working with that, then you can try flashing it with whatever you want.
Till then, there just too many variables with custom ROM.

Several Questions

I'm interested in building an updated, de-googled, de-bloated, ROM for a TCL A30 , model TCL5102D, mt6762/6765. First off was whether to post in tha Alcatel Section. My understanding is that Alcaltel is no more and those phones are now marketed as TCL. Prior Alcaltel posts may be helpful - perhaps the moderators could rename the section "Alcaltel/TCL" rather than adding a New TCL section.
I fouund mtkclient in the forum and it works on my device. I have not TWRP rooted it yet but have pulled boot.img, vbmeta.img and the entire system image. I have also found the TCL source code site, downloaded an earlier device with Mediatek Helio 22P chips and adb pulled /proc/config.gz. GPL source for my specific device has yet to be published by TCL.
I've yet to pull the vendor blobs and have only found guides in the Lineagos documentaion. It's pulling from a zip'd image rather than a device and TCL does not have images for any of their current phone. Also could not find a dump for this particular phone.
My first challenge is trying to build the kernel. The TCL source code, kernel 4.19.127, is not structured like the AOSP kernel source and aarch64, gcc builds hang up on the lcdscreen driver. The screen driver was backported in later 4.19.x versions which built with the config.gz and upstream kernel.org source.
What I'd like to do is to do is update the TCL source to the latest stable 4.19 code base but my web searches have not come up with any examples on how to do this. Could also build with the AOSP 4.19-stable source with the pulled config.gz - chances that it would work?
If I can prebuild the kernel, then make a decision in regards to a LineageOS build vs a GSI build. Maybe even build within GrapheneOS (uses prebuild kernels).
Where, in the forum, should I start the line of questions? Can anybody point me to a guide on howto build an kernel with an up-to-date source?
hi, your best place to go would be here and here
I have a TCL a30 android 11. I'm looking for any possible way to unlock the bootloader and install custom recovery. This all started with trying to use a visible sim card in the phone and me not being able to change the APN settings. I've been working on a way for a while now and have gotten absolutely nowhere. If anyone has any insight, it would be greatly appreciated.
danvep5014 said:
I have a TCL a30 android 11. I'm looking for any possible way to unlock the bootloader and install custom recovery. This all started with trying to use a visible sim card in the phone and me not being able to change the APN settings. I've been working on a way for a while now and have gotten absolutely nowhere. If anyone has any insight, it would be greatly appreciated.
Click to expand...
Click to collapse
TCL A509DL NO FASTBOOT-ABILITY??
Hey there guys and girls. I just bought a cheap TCL A509DL to experiment with and immediately hit a roadblock of megalithic proportions...no fastboot mode available on this cracker-jack prize equivalent phone. Seriously...no way to boot into...
forum.xda-developers.com
971shep said:
TCL A509DL NO FASTBOOT-ABILITY??
Hey there guys and girls. I just bought a cheap TCL A509DL to experiment with and immediately hit a roadblock of megalithic proportions...no fastboot mode available on this cracker-jack prize equivalent phone. Seriously...no way to boot into...
forum.xda-developers.com
Click to expand...
Click to collapse
I'm working on how to get the device to be recognized in mtkclient. Regardless of what button combination I use, the device fails to be recognized. Any specific way it needs to be done on the TCL A30?
I took the phone apart to look for some test points and I can't find any. Did anyone have success in getting this device to work with mtkclient? I've tried every button combination possible. If anyone has any insight it would be greatly appreciated. This is getting extremely frustrating. Been trying for the past week. Once I get passed that point we will be good to go but I'm at a wall right now.
danvep5014 said:
I took the phone apart to look for some test points and I can't find any. Did anyone have success in getting this device to work with mtkclient? I've tried every button combination possible. If anyone has any insight it would be greatly appreciated. This is getting extremely frustrating. Been trying for the past week. Once I get passed that point we will be good to go but I'm at a wall right now.
Click to expand...
Click to collapse
I start mtkclient with the phone connected via usb but powered off. Mtkclient messages that it is trying to establish a connection. Then just power up with the power key only. You should get messages that you connected in brom mode.
I was finally able to get it. Had to use adb reboot edl. Did the trick. Now I'm trying to build a rom with oxygen os but i keep getting stuck in a boot loop.
Boot loops can have many causes.. In the case of a custom rom, it is often that boot verification of the file systems fails, ie a file system checksum is different. In the thread I linked above, the way around this was to overwrite the three different vbmeta.* files with a blank file..

Categories

Resources