Database Info

Bootloop on all custom ROMs (D2303)

Hey guys,
So I ve tried flashing CM 12.1 as well as 5.X AOSP mainly but also some 4.X versions and so far all of them gave me bootloops.
The steps that are necessary seem to vary depending on who you ask so i was a little confused with that, too.(BL is unlocked)
So what I did was :
1. Flash 18.0.C.1.13 FTF or 18.3.1.C.1.15 via EMMA or FTF as well
2. Update Bootloader via EMMA (tried not to do it for some version, too)
(Also rooted the stock rom after that couple times)
For CM 12.1
3. Flash CM recovery through fastboot with CMD
4.Install CM 12.1 and gapps through recovery. ( Did full wipes before and after and only after and before)
For AOSP
3. Flash boot (for one version also recovery), system and userdata (in this order) through fastboot with CMD.
(No wipes here.)
Always got bootloops after that (let them run for about 10 min)
I may have tried other variations too but those are the ones i can think of. Im not exactly sure how new the device is (used phone) since I ve read that there seems to be an issue with some newer models with the GPIO keys ( no clue what that is ).
I would be happy if anyone could actually confirm that the steps i took were right or wrong and if there are any solutions to it.
I m pretty much a noob and dont have any logs or anything but I can read through Tutorials and provide them if it helps (just link me to it)
Ps.: I have looked through the different topics on here but there is lot of varying information plus a lot of stuff that I simply do not understand so I d be glad if anyone could clarify this for me.:fingers-crossed:

SharxX8 said:
Hey guys,
So I ve tried flashing CM 12.1 as well as 5.X AOSP mainly but also some 4.X versions and so far all of them gave me bootloops.
The steps that are necessary seem to vary depending on who you ask so i was a little confused with that, too.(BL is unlocked)
So what I did was :
1. Flash 18.0.C.1.13 FTF or 18.3.1.C.1.15 via EMMA or FTF as well
2. Update Bootloader via EMMA (tried not to do it for some version, too)
(Also rooted the stock rom after that couple times)
For CM 12.1
3. Flash CM recovery through fastboot with CMD
4.Install CM 12.1 and gapps through recovery. ( Did full wipes before and after and only after and before)
For AOSP
3. Flash boot (for one version also recovery), system and userdata (in this order) through fastboot with CMD.
(No wipes here.)
Always got bootloops after that (let them run for about 10 min)
I may have tried other variations too but those are the ones i can think of. Im not exactly sure how new the device is (used phone) since I ve read that there seems to be an issue with some newer models with the GPIO keys ( no clue what that is ).
I would be happy if anyone could actually confirm that the steps i took were right or wrong and if there are any solutions to it.
I m pretty much a noob and dont have any logs or anything but I can read through Tutorials and provide them if it helps (just link me to it)
Ps.: I have looked through the different topics on here but there is lot of varying information plus a lot of stuff that I simply do not understand so I d be glad if anyone could clarify this for me.:fingers-crossed:
Click to expand...
Click to collapse
Looks all good to me, so it is strange you have bootloops.
I'm very curious on how this topic will end: https://talk.sonymobile.com/t5/Gene...lashing-FXP-AOSP-5-1-D2303/m-p/995182#U995182
Also: can somebody explain on how to get a log when the device is in bootloop? At present my phone works (because of other D2303 model?) but when I had bootloops "adb logcat" was constantly waiting for device...
I'm aware the adb process on the phone gets started early and should connect with the PC, but that didn't work with me at the time.
regards

TrickiePad said:
Looks all good to me, so it is strange you have bootloops.
I'm very curious on how this topic will end:
regards
Click to expand...
Click to collapse
galaxyfreak was kind enough to help me a littlle while trying to flash AOSP and even tho it did work eventually it was very unstable, laggy, and the sensors didnt work since apparently that was the file that caused the bootloop in the first place.
So in short it didnt work and as he said
galaxyfreak said:
I recommend sticking to stock till fix is found
Click to expand...
Click to collapse
Pretty sad but I guess thats the best for now.

TrickiePad said:
but when I had bootloops "adb logcat" was constantly waiting for device...
I'm aware the adb process on the phone gets started early and should connect with the PC, but that didn't work with me at the time.
Click to expand...
Click to collapse
For me it just took a while, so i guess at some time during the bootloop it wont be recognized. However this was for AOSP which i flashed through fastboot.
I tried to do the same for CM which was flashed thorugh recovery and it wasnt recognized by adb either.

Solution is coming soon.

galaxyfreak said:
Solution is coming soon.
Click to expand...
Click to collapse
Is this solution work also on aqua with old period ?

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.

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

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

[Recovery] TWRP for the Nubia Z18(NX606J)

Hey,
youyim123 recently made his TWRP build available that I was trying to compile myself. So without further ado, here is a more or less working TWRP for the Nubia Z18 with instructions of how to install it.
Link to recovery.img
How to install it:
Boot into bootloader using
Code:
adb reboot bootloader
Unlock the bootloader using
Code:
fastboot oem nubia_unlock NUBIA_NX606J
Flash the recovery.img using
Code:
fastboot flash recovery recovery.img
IMPORTANT! Navigate to "reboot to emergency recovery mode". Do not use
Code:
fastboot reboot recovery
as it might not work correctly!
I found disconnecting the device from USB to be more reliable, so do that for stability
If it gets stuck, repeat steps 1 and 4. No need to reflash, just be patient
Language will be Chinese, so change that by using the settings button (second from below on the right)
That's it, you have a working TWRP now Enjoy!
EDIT: DO NOT TRY FLASHING MAGISK AS IT WILL DAMAGE DM-VERITY AND YOU'LL HAVE TO BOOT RESCUE YOUR DEVICE! YOU CAN USE MY recovery script in the bloat remover thread to fix your device
In case you get stuck in a bootloop, repeat the installation guide, then use
Code:
adb push stock.zip /data/media/0
and reflash stock firmware as a last resort until a custom ROM is available.
All credit for this goes to youyim123 and his amazing work! I know he struggled releasing this because his work is often used or redirected without his consent or giving him credit, so I'm grateful he decided to release it.

*reserved*

Can i use this to flash Gapps

aqblwd said:
Can i use this to flash Gapps
Click to expand...
Click to collapse
In theory, yes. In practice, it somehow doesn't give me any GApps when flashing it. I'm trying to cooperate with the OpenGapps team to fix this.

any update info for flashing gapps ? i really want to use my nubia z18 with google environment on it. tks

shevaman7 said:
any update info for flashing gapps ? i really want to use my nubia z18 with google environment on it. tks
Click to expand...
Click to collapse
None yet. I'd say community involvement isn't exactly one of the OpenGapps team's good points
See the Gitter thread for tracking updates here: https://gitter.im/opengapps/general
If you know of any other way to contact them, feel free to do so and send them the logs I attached in the gitter post (same username as here)

shevaman7 said:
any update info for flashing gapps ? i really want to use my nubia z18 with google environment on it. tks
Click to expand...
Click to collapse
You can use google xspace

elnas1369 said:
You can use google xspace
Click to expand...
Click to collapse
EDIT: Okay I tried the app and it's doing something that looks like installing play services? @elnas1369 would you mind explaining what you did in detail? Because most of us probably can't speak chinese and it's not intuitive unfortunately

curtisy said:
EDIT: Okay I tried the app and it's doing something that looks like installing play services? @elnas1369 would you mind explaining what you did in detail? Because most of us probably can't speak chinese and it's not intuitive unfortunately
Click to expand...
Click to collapse
I did it on my Nubia X and it works pretty good, you just have to follow the steps, i've found some tutos on youtube it's very easy. You can search for google xspace installing or something like that

curtisy said:
Hey,
youyim123 recently made his TWRP build available that I was trying to compile myself. So without further ado, here is a more or less working TWRP for the Nubia Z18 with instructions of how to install it.
Link to recovery.img
How to install it:
Boot into bootloader using
Code:
adb reboot bootloader
Unlock the bootloader using
Code:
fastboot oem nubia_unlock NUBIA_NX606J
Flash the recovery.img using
Code:
fastboot flash recovery recovery.img
IMPORTANT! Navigate to "reboot to emergency recovery mode". Do not use
Code:
fastboot reboot recovery
as it might not work correctly!
I found disconnecting the device from USB to be more reliable, so do that for stability
If it gets stuck, repeat steps 1 and 4. No need to reflash, just be patient
Language will be Chinese, so change that by using the settings button (second from below on the right)
That's it, you have a working TWRP now Enjoy!
EDIT: DO NOT TRY FLASHING MAGISK AS IT WILL DAMAGE DM-VERITY AND YOU'LL HAVE TO BOOT RESCUE YOUR DEVICE! YOU CAN USE MY recovery script in the bloat remover thread to fix your device
In case you get stuck in a bootloop, repeat the installation guide, then use
Code:
adb push stock.zip /data/media/0
and reflash stock firmware as a last resort until a custom ROM is available.
All credit for this goes to youyim123 and his amazing work! I know he struggled releasing this because his work is often used or redirected without his consent or giving him credit, so I'm grateful he decided to release it.
Click to expand...
Click to collapse
any news update about stable TWRP for Z18. I have Z18, a very beautiful and strong device

md07 said:
any news update about stable TWRP for Z18. I have Z18, a very beautiful and strong device
Click to expand...
Click to collapse
It is stable. Just make sure to unplug your phone after flashing it as otherwise it will probably get stuck after a few seconds. If you need to have your device connected to your pc, do the following:
Start adb sideload in TWRP, connect your phone to your pc, stop sideload. That way you have a working connection with adb again
Hope this helps!

curtisy said:
It is stable. Just make sure to unplug your phone after flashing it as otherwise it will probably get stuck after a few seconds. If you need to have your device connected to your pc, do the following:
Start adb sideload in TWRP, connect your phone to your pc, stop sideload. That way you have a working connection with adb again
Hope this helps!
Click to expand...
Click to collapse
i read somewhere in Nubia forums (chinese language), some dev is going to release TWRP for Z18, but it need poll to decide.
So that, i dont know this version on XDA is official or unofficial ? And as you said, if it is stable, so can i flash Gaap package to get full Goolge and service for Z18? have you tried ?

Already try few weeks ago, not working...!
The only temperary solution is "Google Space", or just wait for the global version release
As one Dev which working on LOS fot this machine point out that Lineage is very hard to compile since there's no other Dev help him, the System is block by something call AVB2...pretty ironic as this twrp not even let us using Magisk at all!
md07 said:
i read somewhere in Nubia forums (chinese language), some dev is going to release TWRP for Z18, but it need poll to decide.
So that, i dont know this version on XDA is official or unofficial ? And as you said, if it is stable, so can i flash Gaap package to get full Goolge and service for Z18? have you tried ?
Click to expand...
Click to collapse

sky104hk said:
Already try few weeks ago, not working...!
The only temperary solution is "Google Space", or just wait for the global version release
As one Dev which working on LOS fot this machine point out that Lineage is very hard to compile since there's no other Dev help him, the System is block by something call AVB2...pretty ironic as this twrp not even let us using Magisk at all!
Click to expand...
Click to collapse
I tried Gplay space. But all app installed from there seem work slowly and not appear on home screen (must go Gplay space and run app)

md07 said:
i read somewhere in Nubia forums (chinese language), some dev is going to release TWRP for Z18, but it need poll to decide.
So that, i dont know this version on XDA is official or unofficial ? And as you said, if it is stable, so can i flash Gaap package to get full Goolge and service for Z18? have you tried ?
Click to expand...
Click to collapse
Please read the first post precisely and then the post in the nubia forum again. Youyim is the guy who made the poll and he made it public. I simply brought it to a wider audience and link to his official GitHub for the img.
You cannot flash Gapps with this because it errors. I said so a couple of times before and would appreciate a bit of effort reading before asking. You probably spent more time on writing this than you would've reading the first three post entries here, disregarding the fact that I'm trying to reply in detail. It's all in the first post, please read that before asking next time..
To sum up:
- It's the "official" TWRP from youyim, all credit goes to him
- You can not install Gapps with this, I haven't found a resolution for this but am working on an alternative. See my other thread or post #3 here

sky104hk said:
Already try few weeks ago, not working...!
The only temperary solution is "Google Space", or just wait for the global version release
As one Dev which working on LOS fot this machine point out that Lineage is very hard to compile since there's no other Dev help him, the System is block by something call AVB2...pretty ironic as this twrp not even let us using Magisk at all!
Click to expand...
Click to collapse
It's the same dev I'm the guy working on LineageOS as well and yes AVB2 (Basically think of it as Android's answer to secure boot on Computers) is a pain in the a** to deal with. Compiling itself is rather easy compared to the pain that comes after it, it's just killing lots of time and I unfortunately don't have that with a full time job. That's why I tried getting more people involved but (again) failed apparently.
TWRP doesn't have anything to do with Magisk either. Magisk is modifying the boot partition as far as I'm aware (don't hate me topjohnwu) and it relies on either no AVB/DM-Verity or a flag that doesn't work here either. TWRP in contrast just modifies/overrides the boot partition and is (mostly) used to flash many things including Magisk.

I think Z18 not have a global version, so we'll never see international firmware for this product. The only way I hope is some one or some dev support official method for install Google. And hope good news come soon.
Thanks all!

md07 said:
I think Z18 not have a global version, so we'll never see international firmware for this product. The only way I hope is some one or some dev support official method for install Google. And hope good news come soon.
Thanks all!
Click to expand...
Click to collapse
Isn't a global release coming in like 2 weeks or something? At least that's what I read last time I checked
I can tell you an official method. Root your phone and rewrite google services to system. Otherwise wait until developers can take a look at Rom building like I do now or even better, get involved. Being a one man show isn't helping the cause even if you have a couple spectators because it makes you feel more or less like a monkey in a cage

curtisy said:
Isn't a global release coming in like 2 weeks or something? At least that's what I read last time I checked
I can tell you an official method. Root your phone and rewrite google services to system. Otherwise wait until developers can take a look at Rom building like I do now or even better, get involved. Being a one man show isn't helping the cause even if you have a couple spectators because it makes you feel more or less like a monkey in a cage
Click to expand...
Click to collapse
Where did you read about global version Z18??? I checked only on Nubia website, in some global region (like India...) they are only going to release global Red Magic Mars.
I know method get Google and service by rooted and I read in Nubia forums they released tool to root current Version Z18, but I can not download

md07 said:
Where did you read about global version Z18??? I checked only on Nubia website, in some global region (like India...) they are only going to release global Red Magic Mars.
I know method get Google and service by rooted and I read in Nubia forums they released tool to root current Version Z18, but I can not download
Click to expand...
Click to collapse
https://www.gadgetsnow.com/mobile-phones/Nubia-Z18 for instance. India isn't global lol. They mostly just buy masses of phones and then resell. And yeah I can understand they won't release a global version anytime soon. The phone is great but looking at the source code, it's horrible. I even had to submit a patch so they get their build fixed!
As for the download, try the second one. Baidu is blocking anything non China by now afaik. It will also be included in the LineageOS ROM whenever I'll get that done..

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.