Related
Hello everyone, I've been trying to unbrick my ZenFone 2 ZE550ML for at least 5 hours...
(first, the small history...)
I've a french ASUS ZenFone 2 ZE550ML (Z008D) with 2 Go of RAM running latest Lollipop official ROM (I never unlocked bootloader or rooted it)
I suscribed to Asus beta tester program on ZenTalk forum, so I received the Marshmallow upgrade via official OTA last night.
Everything updated normally, I had enough space, update has been completed, I saw the ASUS logo on dark background because it's not unlocked, I saw the message "Optimizing apps..."(ART compiling)... and I successfully booted to Marshmallow... but just one time.
What happened is that my ZenFone 2 is... really... slow... and... with... Marshmallow... it... had... the... same.... slowness... than... with... Lollipop :silly:
And, after playing around with Marshmallow around ten minutes (apps were updating through Play Store), my phone hung, only because of slowness. I could make it sleep (screen turning on/off, that's all, no lock screen), and I could just access to shutdown/reboot menu if I press 3 seconds the Power button. But it was frozen, like it often did in Lollipop.
I waited 15 minutes, because I thought turning off while updating apps like Google Play Services was not a brilliant idea. After 15 minutes of waiting, still frozen, but even more frozen : no power menu, and orange LED was still ON even after disconnecting the charger. I decided to reset my ZenFone 2 by pressing power button 10 seconds.
And... I rebooted it => vibration, then immediately USB logo (when POWER or POWER+UP VOLUME). Nothing more after that. No LED while charging (if I plug it to a charger, it boot loop with USB logo). It's very frustrating because... I saw ASUS logo just before optimization, and I stopped it AFTER update, not during :crying:
(now what I tried)
Today I tried to apply this guide : http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
I managed to install every driver, I downloaded every file/image I could...
Because of USB logo, my device is always recognized as a Moorefield device with known driver
Following the guide, I sent to my phone the basic 4-coulour bootloader using xFSTK, no problem
Here is the problem now : I've a working fastboot menu, fastboot is recognized by my computer, BUT almost every fastboot command fails, because my serial number was set to 0123456789ABCDEF :crying:
-> Fastboot error is systematically : FAILED (remote: flash_cmds error! (this happens after successfully downloading to phone, but it's not applying)
and, I tried "fastboot erase cache" :
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (status read failed (Too many links))
I never had any software mess in my phone :crying:
So I don't know what to do, because I would like to flash only splashscreen, recovery and boot if possible, I don't want to lose data
I'm actually downloading a RAW for WW_ZE550ML_2.20.40.149 that I'll sideload with Asus Flash Tool (without wiping data) if it's the only way to do
Where can I find working images for fastboot that can be flashed on a generic serial number?
Thanks for your answers
Edit 1 : OH WAIT... The fastboot screen on my ZenFone 2 Z008 says :
PRODUCT_NAME - Z00A
VARIANT - ASUS_Z00A
WTF ASUS ?!?!?!?!
The ONLY things I did are : OTA update to Marshmallow (I never had OTA issues before) and sending through xFSTK the FW DNx, IFWI and OS Images FOR ZE550ML given in the guide... What happened?! Please please please, can somebody give me the right files? Thank you ^^
(sorry for eventual bad english, I'm a tired french)
Have you tried to re flash fastboot (fastboot flash droidboot.img)?
About the serial number, I think 0123..DEF is normal because I mine is like yours, too. But everything is fine.
fanfan54 said:
Hello everyone, I've been trying to unbrick my ZenFone 2 ZE550ML for at least 5 hours...
(first, the small history...)
I've a french ASUS ZenFone 2 ZE550ML (Z008D) with 2 Go of RAM running latest Lollipop official ROM (I never unlocked bootloader or rooted it)
I suscribed to Asus beta tester program on ZenTalk forum, so I received the Marshmallow upgrade via official OTA last night.
Everything updated normally, I had enough space, update has been completed, I saw the ASUS logo on dark background because it's not unlocked, I saw the message "Optimizing apps..."(ART compiling)... and I successfully booted to Marshmallow... but just one time.
What happened is that my ZenFone 2 is... really... slow... and... with... Marshmallow... it... had... the... same.... slowness... than... with... Lollipop :silly:
And, after playing around with Marshmallow around ten minutes (apps were updating through Play Store), my phone hung, only because of slowness. I could make it sleep (screen turning on/off, that's all, no lock screen), and I could just access to shutdown/reboot menu if I press 3 seconds the Power button. But it was frozen, like it often did in Lollipop.
I waited 15 minutes, because I thought turning off while updating apps like Google Play Services was not a brilliant idea. After 15 minutes of waiting, still frozen, but even more frozen : no power menu, and orange LED was still ON even after disconnecting the charger. I decided to reset my ZenFone 2 by pressing power button 10 seconds.
And... I rebooted it => vibration, then immediately USB logo (when POWER or POWER+UP VOLUME). Nothing more after that. No LED while charging (if I plug it to a charger, it boot loop with USB logo). It's very frustrating because... I saw ASUS logo just before optimization, and I stopped it AFTER update, not during :crying:
(now what I tried)
Today I tried to apply this guide : http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
I managed to install every driver, I downloaded every file/image I could...
Because of USB logo, my device is always recognized as a Moorefield device with known driver
Following the guide, I sent to my phone the basic 4-coulour bootloader using xFSTK, no problem
Here is the problem now : I've a working fastboot menu, fastboot is recognized by my computer, BUT almost every fastboot command fails, because my serial number was set to 0123456789ABCDEF :crying:
-> Fastboot error is systematically : FAILED (remote: flash_cmds error! (this happens after successfully downloading to phone, but it's not applying)
and, I tried "fastboot erase cache" :
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (status read failed (Too many links))
I never had any software mess in my phone :crying:
So I don't know what to do, because I would like to flash only splashscreen, recovery and boot if possible, I don't want to lose data
I'm actually downloading a RAW for WW_ZE550ML_2.20.40.149 that I'll sideload with Asus Flash Tool (without wiping data) if it's the only way to do
Where can I find working images for fastboot that can be flashed on a generic serial number?
Thanks for your answers
Edit 1 : OH WAIT... The fastboot screen on my ZenFone 2 Z008 says :
PRODUCT_NAME - Z00A
VARIANT - ASUS_Z00A
WTF ASUS ?!?!?!?!
The ONLY things I did are : OTA update to Marshmallow (I never had OTA issues before) and sending through xFSTK the FW DNx, IFWI and OS Images FOR ZE550ML given in the guide... What happened?! Please please please, can somebody give me the right files? Thank you ^^
(sorry for eventual bad english, I'm a tired french)
Click to expand...
Click to collapse
After flashing Z008 with xFSTK IAW the procedure you tried, the product name in fastboot screen is shown as ASUS_Z00A. After flashing with Asus flashtool, the fastboot screen says correct product number Z008 and corect serial number. :good:
I tried to flash boot.img, droidboot.img, system.img and recovery.img because I did not want to lose my data. Unfortunately, my Z008 did not accept the fastboot commands just like you, so I wiped my data. :crying:
It seems that this guy has succeeded to unbrick Z00A without losing his data. I have not tried this procedure in my Z008 using Z008 raw file yet, so I don't know if this is effective for Z008.
http://forum.xda-developers.com/showpost.php?p=67474121&postcount=210
Serial number restored by Asus Flash Tool, now I can flash with fastboot
Hakataben said:
After flashing Z008 with xFSTK IAW the procedure you tried, the product name in fastboot screen is shown as ASUS_Z00A. After flashing with Asus flashtool, the fastboot screen says correct product number Z008 and corect serial number. :good:
I tried to flash boot.img, droidboot.img, system.img and recovery.img because I did not want to lose my data. Unfortunately, my Z008 did not accept the fastboot commands just like you, so I wiped my data. :crying:
It seems that this guy has succeeded to unbrick Z00A without losing his data. I have not tried this procedure in my Z008 using Z008 raw file yet, so I don't know if this is effective for Z008.
http://forum.xda-developers.com/showpost.php?p=67474121&postcount=210
Click to expand...
Click to collapse
Hello,
Thanks for your answers
I let going Asus Flash Tool for 6 hours, I saw in the Task Manager and on my Zenfone that it used fastboot2 to erase partitions.
Phone said O.K
But it's stuck for 6 hours on a500cgfastboot (these files are here : C:\Program Files (x86)\ASUS\ASUS Flash Tool\Google)
So I think I'll have to reboot phone and PC and retry (I checked integrity of the raw with 7-zip (the raw file is actually a zip file which is unzipped in the folder %USERPROFILE%\.fbrawtempdir) but I'll re-download it...)
Maybe serial number just changed...
Edit after reboot : SO COOL
I discovered that a500cgfastboot was stuck because................................... by erasing some partions, fastboot2 restored the right serial number (I had to restart fastboot to see back my legit serial number)... and it restored product name to Z008
And because a500cgfastboot (and other command ran by Asus Flash Tool) have the old serial 0123456789ABCDEF for argument, a500cgfastboot was no longer finding my phone
I'll retry downloading my img files with fastboot... But I saw Asus Flash Tool cleaned system partition too, but I'll try...
Edit after flashing with fastboot
With the right serial number, everything flashed perfectly with fastboot (but there's one problem : in the Mega folder, there is not the system image for Marshmallow)
so, without system image, my phone boots (ASUS logo, etc...) BUT nothing happens after logo because fastboot2 wiped system :crying: :crying:
I have still access to Fastboot, like before bricking (POWER + VOL UP) (but I can't figure out how to enter in recovery, I've just the droid bot with exclamation mark)
(it's unbricked but no system)
fanfan54 said:
Hello,
Thanks for your answers
I let going Asus Flash Tool for 6 hours, I saw in the Task Manager and on my Zenfone that it used fastboot2 to erase partitions.
Phone said O.K
But it's stuck for 6 hours on a500cgfastboot (these files are here : C:\Program Files (x86)\ASUS\ASUS Flash Tool\Google)
So I think I'll have to reboot phone and PC and retry (I checked integrity of the raw with 7-zip (the raw file is actually a zip file which is unzipped in the folder %USERPROFILE%\.fbrawtempdir) but I'll re-download it...)
Maybe serial number just changed...
Edit after reboot : SO COOL
I discovered that a500cgfastboot was stuck because................................... by erasing some partions, fastboot2 restored the right serial number (I had to restart fastboot to see back my legit serial number)... and it restored product name to Z008
And because a500cgfastboot (and other command ran by Asus Flash Tool) have the old serial 0123456789ABCDEF for argument, a500cgfastboot was no longer finding my phone
I'll retry downloading my img files with fastboot... But I saw Asus Flash Tool cleaned system partition too, but I'll try...
Edit after flashing with fastboot
With the right serial number, everything flashed perfectly with fastboot (but there's one problem : in the Mega folder, there is not the system image for Marshmallow)
so, without system image, my phone boots (ASUS logo, etc...) BUT nothing happens after logo because fastboot2 wiped system :crying: :crying:
I have still access to Fastboot, like before bricking (POWER + VOL UP) (but I can't figure out how to enter in recovery, I've just the droid bot with exclamation mark)
(it's unbricked but no system)
Click to expand...
Click to collapse
If you want to use Marshmallow, I recommend to flash pre-rooted lollipop first, then to flash marshmallow. In your situation, you should unbrick your Z008 at first. After that, you can change system to Marshmallow easily.
Pre-rooted Z008 systems are here. http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
In my case, I needed to have rooted and bootloader-unlocked again to enter in recovery.
Yay!
ASUS Flash Tool flashed the 2.20.40.149 successfully
It's saying "Optimizing app 45 of 119", but I think I had 179 when upgrading to Marshmallow...
And my Android was in french before. But I think I'll be able to fix this
I'll check soon if I've still all my data and apps...
(also, I tried to film everything, if it works I could eventually upload a video tutorial )
Thanks
Another problem... Edit 1
Android boots, I haven't any installation "Welcome" popup because I did not reset it, but as a consequence it crashes at start :
"Unfortunately, android.process.media stopped"
"Unfortunately, android.process.acore stopped"
And it reboots
Maybe it's because these are Marshmallow apps... Will I have to reset it?
Or where can I find system.img for Marshmallow?
Edit 2 Just managed to access to recovery menu
Definitely solved
Solved without losing any data (except settings of some non-system apps)
Hello,
I found on ZenTalk (this thread : http://www.asus.com/zentalk/forum.php?mod=redirect&goto=findpost&ptid=78184&pid=392686) a working link to Latest Marshmallow sideload zip for ZE550ML OR ZE551ML. It was the right file, finally.
ZF2/ZE550ML/Z008/Android 6.0.1/WW-4.21.40.54 ~ download --> here.
ZF2/ZE551ML/Z00A/Android 6.0.1/WW-4.21.40.61 ~ download --> here.
Click to expand...
Click to collapse
I sideloaded this file using adb and recovery mode, it worked PER-FECT-LY : my phone just rebooted without any problem, like before the problem. And with latest Marshmallow obviously : I immediately received messages, could access to my pictures, apps, with the same settings than before, in French (just one thing: settings for some non-system apps are reset)
Here is guide of everything I did to unbrick a Marshmallow ZE550ML stuck on USB logo with no bootloader :
(Note: I recommend you to charge your ZenFone for a few hours as soon as you'll get fastboot menu at step 1, so it will not shutdown... Even if it's not turning on the orange LED, it's charging )
(Note also that these are the steps I had to do in order to unbrick MY phone without losing data and installing Marshmallow. For your phone some steps might be unnecessary, if you're lucky... I know this is a very long guide but I had to do this in MY case)
1. Flash basic bootloader with xFSTK Downloader to boot fastboot
I had, first, to switch to advanced startup with support for unsigned drivers (video tutorial here),
install Asus USB drivers (link to Asus USB drivers here - note: video tutorial to install drivers from inf (repeat for every device available : ADB Interface, Bootloader Interface, etc...) )
and IntelSocUSB driver (link to IntelSocUSB driver 1.2.0 - Note: Before finishing IntelSocUSB setup it will ask you to configure a device : you'll have to connect your ZenFone 2 using an USB cable to your computer, while it's displaying USB logo, and WAIT FOR DETECTION IN Device Manager as "Moorefield device" under "Intel Soc" section),
to flash a fastboot bootloader (link to xFSTK_ZE550ML-sal358-amtech.vn for ZE550ML / link to xFSTK_ZE551ML-sal358-amtech.vn for ZE551ML) using xFSTK Downloader (link to xFSTK Downloader 1.7.0) [B
(guides for everything in this step 1: english version - same in vietnamese with screenshots and valid links - detailed PDF for xFSTK with screenshots).[/B] => phone boots on fastboot
2. Flash a lollipop ROM (or Marshmallow raw if you find it) with Asus Flash Tool to repair fastboot info (like serial number) and access recovery if you want to install Marshmallow from a zip
In order to get a working recovery menu (because I found a zip for Marshmallow but no raw, I'll have to install a recovery),
I had to install Asus Flash Tool (link to Asus Flash Tool 1.14 - Note: archive password is www.asus-zenfone.com ),
flash a Lollipop raw (link to WW_ZE550ML_2.20.40.149.raw) on my ZenFone 2 ZE550ML using Asus Flash Tool (Model: ZE550ML - wipe data : no)
(guides for everything in this step 2: english version - same in vietnamese with screenshots and valid links)
BUT because Asus Flash Tool will wipe everything except user data and change your serial number from 0123456789ABCDEF to your legit serial number, flashing will NOT work and process will be ENDLESS because serial number has changed so phone is not found and you're not warned of that by Asus Flash Tool.
After 20 minutes of "OKAY" status displayed in green text on your phone, after 20 minutes of "a500cgfastboot.exe" running in task manager,
I think you can safely unplug USB cable, abort Asus Flash Tool by closing this software, killing "a500cgfastboot.exe",
rebooting phone (notice serial number change in fastboot info on phone's screen) and flash again with same settings but the new serial number (different of 0123456789ABCDEF).
This flash should work, after an hour or less you'll see in Asus Flash Tool that it's finished.
3. Flash Marshmallow zip with adb sideload
Finally, you'll have to shut down your phone,
boot in recovery mode (guide is here),
connect it to computer, select "apply update from adb",
install adb (link to ADB Installer 1.4.3 - Note: install it system-wide but don't install Android USB drivers) on your computer,
download zip OTA for Marshmallow (link to UL-Z008-WW-4.21.40.54-user.zip for ZE550ML / link to UL-Z00A-WW-4.21.40.61-user.zip for ZE551ML),
open a command prompt in the folder where you downloaded files (using "File > Open command prompt > Open command prompt" in the Windows Explorer's ribbon), then type :
Code:
adb devices
to verify that your phone is detected (you should see your serial number in cmd),
then type the following command to flash Marshmallow stock (zip is NOT pre-rooted if you want to root you'll have to do it after) :
ZE550ML
Code:
adb sideload UL-Z008-WW-4.21.40.54-user.zip
ZE551ML
Code:
adb sideload UL-Z00A-WW-4.21.40.61-user.zip
It may take a while decompressing then sending to phone. Then select "wipe cache partition" in your recovery menu,
wait until you see again the menu (so, wait until end of wiping cache), and select "reboot").
Now pray, and your device should magically boot the latest beautiful stock Marshmallow ROM from Asus, with all your data, exactly like before you bricked it.
It worked for me, but with the right new images it should work perfectly for you...
Enjoy this small guide, I hope you'll appreciate hard googling work
Thank you all, my problem is solved
fanfan54 said:
Solved without losing any data (except settings of some non-system apps)
Hello,
I found on ZenTalk (this thread : http://www.asus.com/zentalk/forum.php?mod=redirect&goto=findpost&ptid=78184&pid=392686) a working link to Latest Marshmallow sideload zip for ZE550ML OR ZE551ML. It was the right file, finally.
I sideloaded this file using adb and recovery mode, it worked PER-FECT-LY : my phone just rebooted without any problem, like before the problem. And with latest Marshmallow obviously : I immediately received messages, could access to my pictures, apps, with the same settings than before, in French (just one thing: settings for some non-system apps are reset)
Here is guide of everything I did to unbrick a Marshmallow ZE550ML stuck on USB logo with no bootloader :
(Note: I recommend you to charge your ZenFone for a few hours as soon as you'll get fastboot menu at step 1, so it will not shutdown... Even if it's not turning on the orange LED, it's charging )
(Note also that these are the steps I had to do in order to unbrick MY phone without losing data and installing Marshmallow. For your phone some steps might be unnecessary, if you're lucky... I know this is a very long guide but I had to do this in MY case)
1. Flash basic bootloader with xFSTK Downloader to boot fastboot
I had, first, to switch to advanced startup with support for unsigned drivers (video tutorial here),
install Asus USB drivers (link to Asus USB drivers here - note: video tutorial to install drivers from inf (repeat for every device available : ADB Interface, Bootloader Interface, etc...) )
and IntelSocUSB driver (link to IntelSocUSB driver 1.2.0 - Note: Before finishing IntelSocUSB setup it will ask you to configure a device : you'll have to connect your ZenFone 2 using an USB cable to your computer, while it's displaying USB logo, and WAIT FOR DETECTION IN Device Manager as "Moorefield device" under "Intel Soc" section),
to flash a fastboot bootloader (link to xFSTK_ZE550ML-sal358-amtech.vn for ZE550ML / link to xFSTK_ZE551ML-sal358-amtech.vn for ZE551ML) using xFSTK Downloader (link to xFSTK Downloader 1.7.0) [B
(guides for everything in this step 1: english version - same in vietnamese with screenshots and valid links - detailed PDF for xFSTK with screenshots).[/B] => phone boots on fastboot
2. Flash a lollipop ROM (or Marshmallow raw if you find it) with Asus Flash Tool to repair fastboot info (like serial number) and access recovery if you want to install Marshmallow from a zip
In order to get a working recovery menu (because I found a zip for Marshmallow but no raw, I'll have to install a recovery),
I had to install Asus Flash Tool (link to Asus Flash Tool 1.14 - Note: archive password is www.asus-zenfone.com ),
flash a Lollipop raw (link to WW_ZE550ML_2.20.40.149.raw) on my ZenFone 2 ZE550ML using Asus Flash Tool (Model: ZE550ML - wipe data : no)
(guides for everything in this step 2: english version - same in vietnamese with screenshots and valid links)
BUT because Asus Flash Tool will wipe everything except user data and change your serial number from 0123456789ABCDEF to your legit serial number, flashing will NOT work and process will be ENDLESS because serial number has changed so phone is not found and you're not warned of that by Asus Flash Tool.
After 20 minutes of "OKAY" status displayed in green text on your phone, after 20 minutes of "a500cgfastboot.exe" running in task manager,
I think you can safely unplug USB cable, abort Asus Flash Tool by closing this software, killing "a500cgfastboot.exe",
rebooting phone (notice serial number change in fastboot info on phone's screen) and flash again with same settings but the new serial number (different of 0123456789ABCDEF).
This flash should work, after an hour or less you'll see in Asus Flash Tool that it's finished.
3. Flash Marshmallow zip with adb sideload
Finally, you'll have to shut down your phone,
boot in recovery mode (guide is here),
connect it to computer, select "apply update from adb",
install adb (link to ADB Installer 1.4.3 - Note: install it system-wide but don't install Android USB drivers) on your computer,
download zip OTA for Marshmallow (link to UL-Z008-WW-4.21.40.54-user.zip for ZE550ML / link to UL-Z00A-WW-4.21.40.61-user.zip for ZE551ML),
open a command prompt in the folder where you downloaded files (using "File > Open command prompt > Open command prompt" in the Windows Explorer's ribbon), then type :
Code:
adb devices
to verify that your phone is detected (you should see your serial number in cmd),
then type the following command to flash Marshmallow stock (zip is NOT pre-rooted if you want to root you'll have to do it after) :
ZE550ML
Code:
adb sideload UL-Z008-WW-4.21.40.54-user.zip
ZE551ML
Code:
adb sideload UL-Z00A-WW-4.21.40.61-user.zip
It may take a while decompressing then sending to phone. Then select "wipe cache partition" in your recovery menu,
wait until you see again the menu (so, wait until end of wiping cache), and select "reboot").
Now pray, and your device should magically boot the latest beautiful stock Marshmallow ROM from Asus, with all your data, exactly like before you bricked it.
It worked for me, but with the right new images it should work perfectly for you...
Enjoy this small guide, I hope you'll appreciate hard googling work
Thank you all, my problem is solved
Click to expand...
Click to collapse
Man, Today you saved my life and my phone's life . I had exact same problem like yours and I have tried everything to bring my phone back to life last a few days. Today I just noticed your post and it solved my problem perfectly. Thanks man ,really appreciate it ..
muhammed cy said:
Man, Today you saved my life and my phone's life . I had exact same problem like yours and I have tried everything to bring my phone back to life last a few days. Today I just noticed your post and it solved my problem perfectly. Thanks man ,really appreciate it ..
Click to expand...
Click to collapse
Hello,
Thanks for your great feedback muhammed!
Have a nice day!
help me
fanfan54 said:
Hello,
Thanks for your great feedback muhammed!
Have a nice day!
Click to expand...
Click to collapse
please share to my email link WW_ZE550ML_2.20.40.149.raw
[email protected]
tanks before
iwakpauz said:
please share to my email link WW_ZE550ML_2.20.40.149.raw
[email protected]
tanks before
Click to expand...
Click to collapse
Hello, I already sent it to you by email. Here is the link : https://yadi.sk/d/XAUyR8eRtuKdA
Hello,
Sorry for reviving this thread, but I found myself in the same situation. I followed every step, and it works flawlessly. However, after flashing the stock Marshmallow ROM, unlocking the bootloader, flashing TWRP and reinstalling the stock ROM through there, it always bricks my phone (it's the ZE551ML, by the way), so I can't root my device at all. I wonder if anyone has any way of solving this?
I also found that, after unlocking the bootloader, the serial number appears as 0123456789ABCDEF again. I'm pretty much stuck on the stock ROM at this point, with no way of rooting it at all. I can't flash SuperSU through the stock recovery either, it gives me the "signature verification failed" error.
Thanks a lot in advance.
ayuinaba said:
Hello,
Sorry for reviving this thread, but I found myself in the same situation. I followed every step, and it works flawlessly. However, after flashing the stock Marshmallow ROM, unlocking the bootloader, flashing TWRP and reinstalling the stock ROM through there, it always bricks my phone (it's the ZE551ML, by the way), so I can't root my device at all. I wonder if anyone has any way of solving this?
I also found that, after unlocking the bootloader, the serial number appears as 0123456789ABCDEF again. I'm pretty much stuck on the stock ROM at this point, with no way of rooting it at all. I can't flash SuperSU through the stock recovery either, it gives me the "signature verification failed" error.
Thanks a lot in advance.
Click to expand...
Click to collapse
Hello , Firstly , although not clear when you say > "flashing TWRP and reinstalling the stock ROM through there"
1) You can only back up stock rom and restore from TWRP - you cannot flash stock rom from TWRP .
2) Were you bricked and used xFSTK at some point and did you correct serial before upgrading to M ?
signature failed is normal after unlocking bootloader :good:
timbernot said:
Hello , Firstly , although not clear when you say > "flashing TWRP and reinstalling the stock ROM through there"
1) You can only back up stock rom and restore from TWRP - you cannot flash stock rom from TWRP .
2) Were you bricked and used xFSTK at some point and did you correct serial before upgrading to M ?
signature failed is normal after unlocking bootloader :good:
Click to expand...
Click to collapse
Hello, and thank you for the reply!
I'm rather new to this, so I apologize for the possible incorrect terms... I'll try to describe everything as detailed as possible:
My device got bricked, and I sought a solution for it, thus arriving at this thread.
I did every step the OP described to unbrick the device, using xFSTK, *except* rebooting the device after the first flash with ASUS Flash Tool (because when I did, it'd become unresponsive, so I used the flash tool a second time without rebooting and it recovered my serial number).
Next, I went to recovery and installed the Lollipop .zip through adb sideload.
Afterwards, I installed the Marshmallow .zip through adb sideload again.
It's working great this way, but I wanted to root it, so I rebooted into bootloader, and tried to "fastboot boot twrp.img" with no success.
After reading a few more threads, I figured I had to unlock the bootloader before being able to boot into twrp, so I used the bootloader unlocker.
After unlocking it, I was unable to boot into anything but the bootloader (which I presume is normal), so I tried to boot into twrp through fastboot with no success - I had to use "fastboot flash recovery twrp.img" for it to work.
I went into recovery mode, and twrp launched. Since I presumed I had to install Marshmallow from there, due to unlocking the bootloader, I did - through "install .zip".
And after doing that and rebooting the system, it became unresponsive again, - bricked: black screen, only vibrates - thus returning to its initial state.
ayuinaba said:
Hello, and thank you for the reply!
I'm rather new to this, so I apologize for the possible incorrect terms... I'll try to describe everything as detailed as possible:
My device got bricked, and I sought a solution for it, thus arriving at this thread.
I did every step the OP described to unbrick the device, using xFSTK, *except* rebooting the device after the first flash with ASUS Flash Tool (because when I did, it'd become unresponsive, so I used the flash tool a second time without rebooting and it recovered my serial number).
Next, I went to recovery and installed the Lollipop .zip through adb sideload.
Afterwards, I installed the Marshmallow .zip through adb sideload again.
It's working great this way, but I wanted to root it, so I rebooted into bootloader, and tried to "fastboot boot twrp.img" with no success.
After reading a few more threads, I figured I had to unlock the bootloader before being able to boot into twrp, so I used the bootloader unlocker.
After unlocking it, I was unable to boot into anything but the bootloader (which I presume is normal), so I tried to boot into twrp through fastboot with no success - I had to use "fastboot flash recovery twrp.img" for it to work.
I went into recovery mode, and twrp launched. Since I presumed I had to install Marshmallow from there, due to unlocking the bootloader, I did - through "install .zip".
And after doing that and rebooting the system, it became unresponsive again, - bricked: black screen, only vibrates - thus returning to its initial state.
Click to expand...
Click to collapse
Hi again , yes you did everything right up to a point .
You will have to use xFSTK again , flash in aft after till you see ` RESULT = OK ` after a couple of minutes into flash (serial will be incorrect here) ...
Close aft - force close it - keep phone connected through-out -- do not dislodge data cable--- set everything back up in aft again -- then press vol+ once --- your serial will be corrected -- start the flash and let it finish , it will boot into the system related to the raw you flashed.
upgrade like before BUT when in M , use giovix`s Modder tool to unlock bootloader flash, twrp and root etc.
You will be fine ,just remember to back-up stock rom in TWRP first before installing custom LineageOS ,so you can use` return to stock option ` in modder tool after restoring your stock back-up -- to install future updates :good:
timbernot said:
Hi again , yes you did everything right up to a point .
You will have to use xFSTK again , flash in aft after till you see ` RESULT = OK ` after a couple of minutes into flash (serial will be incorrect here) ...
Close aft - force close it - keep phone connected through-out -- do not dislodge data cable--- set everything back up in aft again -- then press vol+ once --- your serial will be corrected -- start the flash and let it finish , it will boot into the system related to the raw you flashed.
upgrade like before BUT when in M , use giovix`s Modder tool to unlock bootloader flash, twrp and root etc.
You will be fine ,just remember to back-up stock rom in TWRP first before installing custom LineageOS ,so you can use` return to stock option ` in modder tool after restoring your stock back-up -- to install future updates :good:
Click to expand...
Click to collapse
Did everything as you told me, but now whenever I "reboot to system", it boots into recovery every time... :\
To clarify, I used the command "fastboot flash recovery twrp_z00a_v24_repack.img", and then installed the latest .zip of SuperSU in TWRP (Install -> SuperSU.zip).
EDIT: Sorry, I mistook Giovix's bootloader unlocker for their full modder tool, I'll be trying that now.
EDIT 2: You saved my butt! Thank you so much for your help, I managed to succeed in everything, finally!
ayuinaba said:
Did everything as you told me, but now whenever I "reboot to system", it boots into recovery every time... :\
To clarify, I used the command "fastboot flash recovery twrp_z00a_v24_repack.img", and then installed the latest .zip of SuperSU in TWRP (Install -> SuperSU.zip).
EDIT: Sorry, I mistook Giovix's bootloader unlocker for their full modder tool, I'll be trying that now.
EDIT 2: You saved my butt! Thank you so much for your help, I managed to succeed in everything, finally!
Click to expand...
Click to collapse
Marvelous stuff. ,its been a pleasure helping you
Happy flashing
---------- Post added at 02:47 AM ---------- Previous post was at 02:44 AM ----------
PS, should see the lengths some people go to restore serial
Why ? Lol When it
Only takes 3 mins max this way
(I wrote the 'new' version of rooting out of memory / conjecture, it should not do irreversible harm to your tablet, however, always apply common sense and proceed with caution. Caveat - I am neither a developer nor software engineer.)
'New' version of rooting procedures can be carried out with relative ease now that @krustymars has done the heavy lifting and ported TWRP to Teclast X16Plus; applies to both native android 5.1.1 and Remix 2.0.
In his write-up, it wasn't mentioned that TWRP can only be installed if X16 Plus's bootloader is 'OEM unlocked' and ROM will only boot if X16 Plus's boot image is patched (insecured), after the flashing of TWRP.
To unlock is not difficult (fastboot oem unlock), but it will also wipe /data of the ROM (making it unbootable too?). Question mark here as I am uncertain whether this action will render the ROM unbootable or not. For the sake of not doing double jobs, we assume it will.
The third condition for the ROM to first boot properly after flashing is the original recovery must be present (again I am not sure if a patched boot image will do the trick; for the same reason above, we assume it won't)
Therefore the only way out is to ensure the bootloader is not re-locked after the flashing of ROM, for us to be able to flash an effective TWRP AFTER the ROM has finished its first boot.
I believe the above are the main reasons why @stratos7 faced difficulties when intending to root via TWRP.
A simple and rudimentary step by step guide as below (you will LOSE ALL DATA in the tablet, backup all your important stuffs before proceeding):
1) Rename the ROM's original recovery.img to recovery.org. Copy krustymars' TWRP over and rename it recovery.img
This is to ensure that after the flashing, the reboot process will fail and the script will not re-lock the bootloader
2) Flash the ROM as per normal (enter DNX Fastboot by pressing vol+ vol- and power button concurrently, then use Intel Platform Flash Tool Program to flash).
3) After a successful flash, the tablet will enter recovery (TWRP) first time during reboot, and failed. It will be stuck in a boot loop (showing TWRP error).
4) Force shut it by pressing the power button for 10-15secs.
5) Enter fastboot by pressing vol- and power button concurrently.
6) Flash the orginal recovery via adb fastboot.
fastboot flash recovery recovery.img
7) Reboot normally and the ROM will load properly (1st successful boot will take a while; as long as you see the Remix OS logo flashing, all are good).
8) 10x click on Build Number to activate Developer's Menu
9) Activate USB debugging
10) Reboot into fastboot by typing
adb reboot fastboot
11) Check to ensure that bootloader is still unlocked.
12) Flash krustymars' TWRP
fastboot flash recovery TWRP_TeclastX16Plus_by_krustymars.img
13) Flash patched boot image
fastboot flash boot boot.img
14) Choose Recovery Mode, ensure X16 Plus boots into TWRP fine
15) Reboot into ROM from TWRP
16) If you are satisfied that all are fine after rebooting into the ROM, and have copied the latest downloaded SuperSU.zip flashable file into the Internal or Micro SD memory, you can either adb reboot fastboot or shutdown the tablet and vol- power button into fastboot, and then choose Recovery Mode from within fastboot to enter TWRP to flash SuperSU to get root.
Do note that you cannot update binaries within Android, you can update the SuperSU app though if a new version comes up in Play store, just not the binaries. If your binaries become outdated, you will need to flash the latest SuperSU.zip again via TWRP.
The necessary files (minus SuperSU, do grab that from Chainfire's site) - https://www.mediafire.com/?3blso8sjw4kb3e6
Once again, proceed with caution / common sense and the above shouldn't land you in any irreversible situation. All the best!
_____________________________________________________________________________________________________________________________
OLD METHOD
The below instructions for rooting Teclast X16 Plus originated from Teclast's forums. All credits go to the respective creator(s), I merely translated them to post here.
1) Download the standard rooting package from http://www.mediafire.com/download/nrez4ggzau1u8ax/Root.X16Plus.V1.zip
2) Download your corresponding edited boot image file and extracted build prop file (for either Remix OS 2.0 ver B2016062701 or Android 5.1 ver 1.07)
- for Remix OS http://www.mediafire.com/download/b6aazky2y9eqch7/Remix_OS_2.0.zip
- for Android 5.1 http://www.mediafire.com/download/zz40a8cgav385l3/android5.1.zip
3) Download and install Intel's tools and drivers in the order below - http://www.mediafire.com/download/p723or9hxip5eu8/Intel_Flash_Tools.rar
You can omit this step if these drivers are already installed.
- iSocUSB-Driver-Setup-1.2.0.exe
- IntelAndroidDrvSetup1.10.0.zip
- PhoneFlashToolLite_5.5.2.0_win32.exe
4) Download kingroot tool from below, copy the apk file to your X16 Plus and install. There is no need to run the installed app now.
5) Ensure USB debugging is switched on under developer options in your ROM
6) Unzip both the rooting package and your corresponding edited boot image and extracted build.prop files. Cut and paste the unzipped boot image and build prop files into the unzipped rooting package directory.
7) Launch command prompt and change directory to the unzipped rooting package directory
8) Connect your X16 Plus via USB
9) Type and enter - adb reboot bootloader
10) X16 Plus will reboot into fastboot mode
11) Type and enter - fastboot flash boot boot-root.img
12) Type and enter - fastboot reboot
13) X16 Plus will reboot into normal mode, wait for the bootup process to finish
14) Type and enter - su.bat
15) Run the previously install Kingroot app, Kingroot will prompt you to repair root privileges, allow it to do so.
16) Reboot your X16 Plus after the above repair and you will have full root access. If root access is still incomplete, run the above step 14) su.bat command again
Just one thanks cannot say how much grateful I am. THANKS. It work.
Thanks a lot Potatohead ! You rock !
I will try this instruction and post a feedback as soon as possible !
potatohead,
I have just finish to root my tablet. It's very easy and everything is fine.
Once again, thanks a lot ! :good:
great job !!
all are OK under win XP
Thx
Hi @potatohead , Hi @TrYkeR ,
I've just discovered a new firmware V1.07 for our X16 plus on the Teclast website (in the download section) . My tablet is running with the V1.04 version.
Do you know you to flash it, cause TeclastOTA is unable to ugrade it both with the Online mode ("undiscover new version") and the Local mode ?
Reno.
I'm using 1.07, I use a tutorial from their webside.
The big problem is download the firmware, their server sucks a lot. I use jdownload since chrome crash 2 times and do not recover the download
Firmware:
http://pan.baidu.com/s/1nvKVjnF
https://yadi.sk/d/TrUPzmkXsFrXJ (mirror)
here they talk about it:
http://techtablets.com/forum/topic/teclast-x16-plus-i-want-to-change-from-v-1-04-to-v-1-07/
I didn't find the post that I use, but was really easy, like paste the .img files into a folder, put teclast plus in "download mode", they called it diferent, and run an script (.bat)
Hi @TrYkeR,
Thanks for your prompt reply.
I searched for the tuto but I didn't find it too (I already have the V1.07 download). I do not want to do it by myself, i'm not enough confident.
If you find it...
Reno
renofaringite said:
Hi @TrYkeR,
Thanks for your prompt reply.
I searched for the tuto but I didn't find it too (I already have the V1.07 download). I do not want to do it by myself, i'm not enough confident.
If you find it...
Reno
Click to expand...
Click to collapse
I didn't found the exactly post I've use.
Was in this forum:
http://techtablets.com/forum/forums/teclast/general-discussion/page/1/
im new users teclast x16 plus .. is better remixos or android 5.1 firmware 1.0.7 (for drain battery etc..)
Hello friends,
I have the same question.... is better remixos or android 5.1 firmware 1.0.7?
Thanks a lot !!
Renew link
Potatohead, could you please post another link to root.x16plus.v1.zip?
Mediafire removed the file, nowhere else to be found (according to google...)
Thanks in advance!
So did anyone else happen to pick this up from tinydeal while they had it for $79? Not sure if it's arriving with 5.1 or Remix, but this is good to know.
Henk S. said:
Potatohead, could you please post another link to root.x16plus.v1.zip?
Mediafire removed the file, nowhere else to be found (according to google...)
Thanks in advance!
Click to expand...
Click to collapse
As you, I'm looking for this file to root my tablet.
Henk S. said:
Potatohead, could you please post another link to root.x16plus.v1.zip?
Mediafire removed the file, nowhere else to be found (according to google...)
Thanks in advance!
Click to expand...
Click to collapse
bja9 said:
As you, I'm looking for this file to root my tablet.
Click to expand...
Click to collapse
Guys, you can get it here
Link:
pan.baidu.com/s/1eSfpVW2
Password:
xc1u
---------- Post added at 05:20 AM ---------- Previous post was at 05:17 AM ----------
potatohead said:
The below instructions for rooting Teclast X16 Plus originated from Teclast's forums. All credits go to the respective creator(s), I merely translated them to post here.
...
Click to expand...
Click to collapse
I followed the instructions and flashed boot-root.img successfully, however I'm unable to run adb remount in su.bat
it says "remount of system failed: Permission denied", "remount failed"
any ideas?
btc002 said:
Guys, you can get it here
Link:
pan.baidu.com/s/1eSfpVW2
Password:
xc1u
---------- Post added at 05:20 AM ---------- Previous post was at 05:17 AM ----------
I followed the instructions and flashed boot-root.img successfully, however I'm unable to run adb remount in su.bat
it says "remount of system failed: Permission denied", "remount failed"
any ideas?
Click to expand...
Click to collapse
Tank you for the link to the file. It works fine for me !
Rooting in progress.
Did someone sucessfully installed Remix OS 3.0 or W10 ? (W10 i get acpi boot error :/)
I followed the instructions and flashed boot-root.img successfully, however I'm unable to run adb remount in su.bat
it says "remount of system failed: Permission denied", "remount failed"
any ideas?
Click to expand...
Click to collapse
me too...any ideas?
best regards
:good:
..
Hey, I think I read all the threads that could be helpful (development, Q&A, lineageos & cm-installguides, twrp-install and so on), but I don't get my phone to work.
I have a Xperia M2 Dual c2005 and want to get LineageOS working. I have no data left that I would need, so I try to start from new...
Steps already taken:
- unlocked bootloader for both IMEIs https://zifnab.net/~zifnab/wiki_dump/Install_CM_for_nicki.html#What_does_.22unlocking.22_mean.3F --> worked
- flashed boot.img (extracted from lineage-14.1-20170131-nightly-nicki-signed.zip) in fastboot-mode and went to recovery
- wanted to copy zip to device, but adb (also with sudo!) says: unauthorized (Please check the confirmation dialog on your device. ... but there is none)
- in CM-recovery i tried to flash via sideload, but it stops transferring data at around 50% and saying: E: signature verification failed ... and E: error 21
- had the md5sum created and put it in folder, still the same
- also tried, what shouldn't be done fastboot flash boot twrp-3.0.2-0-nicki.img --> doesn't work b/c of FOTA, so how to install twrp?
Any ideas how to install clean lineageOS? Thanks in advance.
...usually this problem cause bad kernel or image .. so wipe format,data,cache,dalvik cache, make factory reset in cwm... boot again to recovery and flash TWRP 2.8.6.0 zip. file via recovery and reboot again to recovery .. now flash latest lineage os , without any extract
.. here is link for twrp..: https://forum.xda-developers.com/xp...very-cwm-twrp-recoveries-custom-roms-t3016507
..dont forget!! flash this 2.8.6.0 version ... if doesnt work this little guide, try to format sdcard via recovery in advanced option "this is partition where is everithyng set on 0 " ... and try again
Thanks a lot! For me it worked the following way, since I didn't have CWM present:
- downloaded TWRP 2.8.7.0 from the link you provided
- extracted FOTAKernel.img
- in fastboot mode: sudo fastboot flash boot FOTAKernel.img
- reboot in recovery (worked well!)
- adb push lineageos14.1.xxx.zip /sdcard/
- install and choose image
Thanks a lot, after a couple of days of trying I do now understand Sony a little more (for my own, I only use Nexus, which works quite simple ).
jeensg said:
Thanks a lot! For me it worked the following way, since I didn't have CWM present:
- downloaded TWRP 2.8.7.0 from the link you provided
- extracted FOTAKernel.img
- in fastboot mode: sudo fastboot flash boot FOTAKernel.img
- reboot in recovery (worked well!)
- adb push lineageos14.1.xxx.zip /sdcard/
- install and choose image
Thanks a lot, after a couple of days of trying I do now understand Sony a little more (for my own, I only use Nexus, which works quite simple ).
Click to expand...
Click to collapse
no problem, iam glad i could help
{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
NOTE
Should you ever face any issues, capture logs. I also need to know what build you're on (build number or at least a date).
Hint: "It doesn't work" is not a bug report and posts like this will be ignored.
KNOWN ISSUEs
The Sony stock camera does not work at the moment.
INFO
This ROM does not use the device trees/kernel from sonyxperiadev (aka SODP). The device tree was made from scratch, and the stock kernel (based off 52.1.A.x.y) has been used.
DOWNLOAD
Official builds
NOTE: Since the official builds are signed, you can't simply upgrade from my unofficial builds -- you can either migrate to an official build using a script or do a clean install.
All unofficial builds
INSTRUCTIONS
Just flash the builds as usual. Make sure to be on the latest stock firmware.
SOURCE
LineageOS
Kernel
CHANGELOG
20210516:
- fixed WiFi display/screen casting
- addressed performance issues and lags
20210515:
- updated to 18.1
- fixed remaining most of the bugs
- set SELinux to enforcing
20201128:
- fixed NFC
20201127:
- initial public release.
Thanks a lot. Great to know you are working on LOS18.
I tried sideloading with the latest LOS17.1 recovery (and LOS 17.1 on the phone, naturally). I get an error. Do I absolutely have to be on stock?
Are you still working on this one?
I am trying to flash a LOS image onto a single SIM Phone, but it always fails with error "unknown fuse request opcode 2016" in the recovery.log, and the system image is empty after the flash.
I am using the latest STOCK TWRP 2020-06-14_21-07-37_twrp_apollo.tar.gz.
It fails on all LOS images I have tried, 18.0 17.1 etc. So far I haven't been able to flash a LOS image at all successfully.
The flash performs normally, but fails with an error after 2-3 minutes, and afterwards the system partition is empty.
The unit is a SONY XZ2 Compact Single SIM.
After discussion with someone, this maybe due to the LOS image having an incorrect System partition size(?). Why does it flash correctly on most people's units, but not on this one?
Anyone has an idea? I am attaching the twrp.log files.
Garfield24 said:
I am trying to flash a LOS image onto a single SIM Phone, but it always fails with error "unknown fuse request opcode 2016" in the recovery.log, and the system image is empty after the flash.
I am using the latest STOCK TWRP 2020-06-14_21-07-37_twrp_apollo.tar.gz.
It fails on all LOS images I have tried, 18.0 17.1 etc. So far I haven't been able to flash a LOS image at all successfully.
The flash performs normally, but fails with an error after 2-3 minutes, and afterwards the system partition is empty.
The unit is a SONY XZ2 Compact Single SIM.
After discussion with someone, this maybe due to the LOS image having an incorrect System partition size(?). Why does it flash correctly on most people's units, but not on this one?
Anyone has an idea? I am attaching the twrp.log files.
Click to expand...
Click to collapse
Hi!
I'got the same situation, with a bad downloaded los.zip file. Maybe it's the problem.
But what i saw in your description, the used twrp. If i known good, for Android 11 the working twrp for coming from stock to los is here what works for me ( apollo ):
" https://androidfilehost.com/?w=files&flid=318609 " ;
And don't flash it to the recovery or boot partitiom, just temperoraly boot it with fastboot.
lba810701 said:
Hi!
I'got the same situation, with a bad downloaded los.zip file. Maybe it's the problem.
But what i saw in your description, the used twrp. If i known good, for Android 11 the working twrp for coming from stock to los is here what works for me ( apollo ):
" https://androidfilehost.com/?w=files&flid=318609 " ;
And don't flash it to the recovery or boot partitiom, just temperoraly boot it with fastboot.
Click to expand...
Click to collapse
Nope, not working.
I flashed a stock image with newflasher and booted to the apps. Original image boots fine.
Then I rebooted into fastboot and did: fastboot boot twrp.img like you suggested.
TWRP runs fine, I wipe the partitions, and flash LOS. No operating system installed afterwards.
I don't think it's a corrupt .zip file, since I tried about 5 different ones.
When flashing I get a message: "Unable to find partition for path /cache" in red colour.
Anyone knows what that means?
Garfield24 said:
Nope, not working.
I flashed a stock image with newflasher and booted to the apps. Original image boots fine.
Then I rebooted into fastboot and did: fastboot boot twrp.img like you suggested.
TWRP runs fine, I wipe the partitions, and flash LOS. No operating system installed afterwards.
I don't think it's a corrupt .zip file, since I tried about 5 different ones.
When flashing I get a message: "Unable to find partition for path /cache" in red colour.
Anyone knows what that means?
Click to expand...
Click to collapse
H
Garfield24 said:
Nope, not working.
I flashed a stock image with newflasher and booted to the apps. Original image boots fine.
Then I rebooted into fastboot and did: fastboot boot twrp.img like you suggested.
TWRP runs fine, I wipe the partitions, and flash LOS. No operating system installed afterwards.
I don't think it's a corrupt .zip file, since I tried about 5 different ones.
When flashing I get a message: "Unable to find partition for path /cache" in red colour.
Anyone knows what that means?
Click to expand...
Click to collapse
Do you disabled the verified boot before rhe whole twrp process?
" fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img "
lba810701 said:
H
Do you disabled the verified boot before the whole twrp process?
" fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img "
Click to expand...
Click to collapse
Yes, I have tried that, too, just now again. As before, not working. I have tried so many things by now. The flash of the LOS image completes, but in step 2/2 I get "Unable to find partition for path /cache" , and it says completed. In the recovery log, there is an error "unknown fuse request opcode 2016" . The system partition is empty after the flash (7MB used).
I wonder, if there is a difference in the partitions on this specific phone. I am attaching the output of the following command:
cat /proc/partitions > /external_sd/partlog.txt
It writes an overview of partitions and their sizes to a file on the SD Card. There are 74 partitions on /sda. I wonder why anybody needs 74 partitions?
Can someone run the same command on their phone with a working and installed LOS and compare it to my file, if there is any difference to a phone that is working (partitions-sizes/-ordering?)?
I run the command from TWRP. Start up recovery TWRP and go to Advanced -> Terminal. There you can run the command.
cat /proc/partitions > /external_sd/partlog.txt
I would appreciate if someone could run that command on a phone where the LOS image works, and compare the file to my file, if there are any differences in the partitioning scheme or sizes. Sizes are important.
Any other suggestions also welcome.
Garfield24 said:
Yes, I have tried that, too, just now again. As before, not working. I have tried so many things by now. The flash of the LOS image completes, but in step 2/2 I get "Unable to find partition for path /cache" , and it says completed. In the recovery log, there is an error "unknown fuse request opcode 2016" . The system partition is empty after the flash (7MB used).
I wonder, if there is a difference in the partitions on this specific phone. I am attaching the output of the following command:
cat /proc/partitions > /external_sd/partlog.txt
It writes an overview of partitions and their sizes to a file on the SD Card. There are 74 partitions on /sda. I wonder why anybody needs 74 partitions?
Can someone run the same command on their phone with a working and installed LOS and compare it to my file, if there is any difference to a phone that is working (partitions-sizes/-ordering?)?
I run the command from TWRP. Start up recovery TWRP and go to Advanced -> Terminal. There you can run the command.
cat /proc/partitions > /external_sd/partlog.txt
I would appreciate if someone could run that command on a phone where the LOS image works, and compare the file to my file, if there are any differences in the partitioning scheme or sizes. Sizes are important.
Any other suggestions also welcome.
Click to expand...
Click to collapse
I attached it, but I'm on 17.1. Maybe help? But first round, it's seems the same except the last two line of the logs... In yours, there are "mcblk0" and "mmcblk0p1" what's missing from mine, but I haven't got sdcard so, maybe thats why.
lba810701 said:
I attached it, but I'm on 17.1. Maybe help? But first round, it's seems the same except the last two line of the logs... In yours, there are "mcblk0" and "mmcblk0p1" what's missing from mine, but I haven't got sdcard so, maybe thats why.
Click to expand...
Click to collapse
Yes, that definitely helps. Thank you. The last two lines is the SDCard, that's correct.
That means my phone has the same ROM size and partition size than yours, so the System partition is the same size.
I find an additional partition in your file in line 19:
254 0 1048576 zram0
I don't have a zram0 partition in my file and my phone.
The question now is: does that make any difference? Can that missing partition on my phone can cause the flash to fail?
After a LOT of trial and error I am making a description, how to get a running LOS on your SONY XZ2 Compact Single SIM (and probably Dual SIM). This is not a description for people, who got it running the easy way. It's for people that tried everything, and can't get it running, and are in desperation and lost.
General description first: The SONY XZ2 Compact is a phone with 2 slots. These phones don't have a recovery partition, so you cannot meaningfully boot into a recovery partition like on old phones. It now has a boot partition (2 of them - slot A and slot B), and you can boot an operating system from these slots. These slots are completely separate, you can boot an operating system in slot A and another separate one in slot B. These slots (from a user perspective) are separate, and there is very little interchange between them (or more or less none).
Prerequisits: TWRP, I used the Version from MartinX 2020-06-14_21-07-37_twrp_apollo.tar.gz , link is here: https://androidfilehost.com/?w=files&flid=306949
Use a STOCK TWRP
Extract the .img files with 7-zip (7-zip.org), until you have the .img file separate.
Newflasher:
[TOOL] Newflasher (xperia command line flasher)
Disclaimer: newflasher tool was made for testing and educational purposes, ME is not responsible for what you do on/with your device using newflasher, you must agree that you using newflasher on your own risk, I am not responsible if you brick...
forum.xda-developers.com
I used v42, probably newer versions work, too, try not to use an older version
Booting into fastboot: hold Volume-UP and then plugging a USB cable to the computer. The blue light should be lit, if fastboot is active, screen stays blank.
Booting into flash mode: hold Volume-DOWN and then plugging a USB cable to the computer. The green light should be lit, if flash mode is active, screen stays blank.
Now let's get to the process of flashing LOS:
Step 1 - Flash an original working SONY image into Slot A:
Boot into fastboot mode, so the blue light is on.
Type:
fastboot reboot bootloader
(Sometimes the computer doesn't recognise the phone after this command, then just unplug the USB, wait until the phone is off, and try again beginning Step 1. It can fail a couple of times, but it will also work in between).
fastboot --set-active=a
fastboot reboot bootloader
You can check that Slot A is active by typing the command
fastboot getvar all
in the output check the line current slot active: a
Run Newflasher (how to use Newflasher is beyond the scope of this post, google it) to flash an original stock SONY image. You need to be in flash mode for Newflasher with the green light lit.
Answer the first question what to do when done with Newflasher with 'p'=Power Off, and all others with 'n'=No.
When Newflasher completes, check the last few lines output, it should say setting slot A active and OKAY. That confirms that you flashed the original SONY image in Slot A.
You now have a fully working operating system in Slot A. However there is a bug in Newflasher and that bug destroys the boot process in Slot B, which means you'll be only able to boot Slot A, booting Slot B will fail.
Should you decide to boot the operating system (you don't have to), make sure you don't set up authentication (pin code, fingerprint), skip setting that up, so your data partition doesn't get encrypted.
Step 2 - Flash an original working SONY image into Slot B:
Boot into fastboot mode, so the blue light is on.
Type (similar to Step 1):
fastboot reboot bootloader
fastboot --set-active=b
fastboot reboot bootloader
You can check that Slot B is active by typing the command
fastboot getvar all
in the output check the line current slot active: b
WARNING: DO NOT BOOT Slot B, as it will fail 2-3 times (you'll notice the phone vibrating upon crash and reboot), because the phone will then put you back on Slot A, and you'll flash Slot A again. Make sure YOU DON'T BOOT the operating system in Slot B, or you'll end up in Slot A again.
Run Newflasher (how to use Newflasher is beyond the scope of this post, google it) to flash an original stock SONY image. You need to be in flash mode for Newflasher with the green light lit.
Answer the first question what to do when done with Newflasher with 'p'=Power Off, and all others with 'n'=No.
When Newflasher completes, check the last few lines output, it should say setting slot B active and OKAY. That confirms that you flashed the original SONY image in Slot B.
You now have a fully working operating system in Slot B. However there is a bug in Newflasher and that bug destroys the boot process in Slot A, which means you'll be only able to boot Slot B.
At this point in time, if you would try to boot into Slot A, it will boot up to the SONY logo, and then crash, and reboot up to the SONY logo, and then crash. Should you get stuck in that loop, insert a USB cable and hold Volume-UP, it'll catch the crashing loop, and you'll end up in fastboot.
Step 3 - Boot the original SONY image up to the home screen where the apps show:
Actually you should be in Slot B already, but if you are not:
Boot into fastboot mode, so the blue light is on.
Type (similar to Step 2):
fastboot reboot bootloader
fastboot --set-active=b
fastboot reboot bootloader
You can check that Slot B is active by typing the command
fastboot getvar all
in the output check the line current slot active: b
Boot the phone's operating original stock image in Slot B, until you are at the home screen with the apps. This sets up all the defaults for your phone, and updates any ROM images in the chips (like modem etc.).
Make sure you don't set up authentication (pin code, fingerprint), skip setting that up, so your data partition doesn't get encrypted.
Power off your phone.
Step 4 - Flash twrp into Slot B
Type (similar to Step 2):
fastboot reboot bootloader
fastboot --set-active=b
fastboot reboot bootloader
fastboot flash boot twrp.img
This will flash TWRP as boot in Slot B. Make sure in the screen output it was flashed in boot_b.
Should you make an error here, start with Step 1. The reason here is, we want LOS in Slot A, and not TWRP.
Boot your TWRP in Slot B.
WARNING: DO NOT flash VBMETA, it'll break the boot process, and you can start from Step 1.
Step 5 - Flash LOS into Slot A
Once TWRP is running, go to Wipe.
WARNING: DO NOT perform factory reset.
Go to Advanced Wipe, and ONLY WIPE 'Data' and 'Dalvic Cache'
WARNING: DO NOT WIPE System or Internal Storage. You'll loose mount points under Linux, and the LOS image flash will fail.
Go back to TWRP home screen.
From there go to Advanced and from there to ADB Sideload.
From the computer start installing your LOS image (sideload).
On the computer type:
adb sideload <Your LOS image>.zip.
ATTENTION: During flashing, the phone will show, which slot it flashes. It should flash and show: "flashing inactive Slot A". If you accidentally flash Slot B, start from the beginning Step 1.
Best results I had with the image from the LOS homepage https://download.lineageos.org/xz2c
Download the zip file, don't unpack it, use adb sideload to upload the zip file.
Forget about the Recovery image on the LOS homepage. You don't need it.
When flashing completes, you can wipe Delvic Cache.
WARNING: DO NOT WIPE 'cache', since a 2 slot phone doesn't have a cache partition, and it will fail to wipe it.
Do NOT install the TWRP app, skip this step.
Reboot
Step 6 - Boot LOS
LOS is in Slot A, TWRP is in Slot B.
You can alternate between the slots from fastboot.
fastboot reboot bootloader
fastboot --set-active=a
fastboot reboot bootloader
A reboot should boot LOS.
ATTENTION: When the LOS image has finished booting and you get to the date/time screen, the LOS will hang a while (30s). Just let it do it's job, I think (not sure), it's creating the data in the user partition. After 30s or so use the back key, and try setting the time again. This only happens on the very first boot.
Let me know as feedback, if I can clarify better or if this description is ok.
Hello,
if there is anything I can help with getting official support for LineageOS 18.1 pls let me know.
Garfield24 said:
After a LOT of trial and error I am making a description, how to get a running LOS on your SONY XZ2 Compact Single SIM (and probably Dual SIM). This is not a description for people, who got it running the easy way. It's for people that tried everything, and can't get it running, and are in desperation and lost.
General description first: The SONY XZ2 Compact is a phone with 2 slots. These phones don't have a recovery partition, so you cannot meaningfully boot into a recovery partition like on old phones. It now has a boot partition (2 of them - slot A and slot B), and you can boot an operating system from these slots. These slots are completely separate, you can boot an operating system in slot A and another separate one in slot B. These slots (from a user perspective) are separate, and there is very little interchange between them (or more or less none).
Prerequisits: TWRP, I used the Version from MartinX 2020-06-14_21-07-37_twrp_apollo.tar.gz , link is here: https://androidfilehost.com/?w=files&flid=306949
Use a STOCK TWRP
Extract the .img files with 7-zip (7-zip.org), until you have the .img file separate.
Newflasher:
[TOOL] Newflasher (xperia command line flasher)
Disclaimer: newflasher tool was made for testing and educational purposes, ME is not responsible for what you do on/with your device using newflasher, you must agree that you using newflasher on your own risk, I am not responsible if you brick...
forum.xda-developers.com
I used v42, probably newer versions work, too, try not to use an older version
Booting into fastboot: hold Volume-UP and then plugging a USB cable to the computer. The blue light should be lit, if fastboot is active, screen stays blank.
Booting into flash mode: hold Volume-DOWN and then plugging a USB cable to the computer. The green light should be lit, if flash mode is active, screen stays blank.
Now let's get to the process of flashing LOS:
Step 1 - Flash an original working SONY image into Slot A:
Boot into fastboot mode, so the blue light is on.
Type:
fastboot reboot bootloader
(Sometimes the computer doesn't recognise the phone after this command, then just unplug the USB, wait until the phone is off, and try again beginning Step 1. It can fail a couple of times, but it will also work in between).
fastboot --set-active=a
fastboot reboot bootloader
You can check that Slot A is active by typing the command
fastboot getvar all
in the output check the line current slot active: a
Run Newflasher (how to use Newflasher is beyond the scope of this post, google it) to flash an original stock SONY image. You need to be in flash mode for Newflasher with the green light lit.
Answer the first question what to do when done with Newflasher with 'p'=Power Off, and all others with 'n'=No.
When Newflasher completes, check the last few lines output, it should say setting slot A active and OKAY. That confirms that you flashed the original SONY image in Slot A.
You now have a fully working operating system in Slot A. However there is a bug in Newflasher and that bug destroys the boot process in Slot B, which means you'll be only able to boot Slot A, booting Slot B will fail.
Should you decide to boot the operating system (you don't have to), make sure you don't set up authentication (pin code, fingerprint), skip setting that up, so your data partition doesn't get encrypted.
Step 2 - Flash an original working SONY image into Slot B:
Boot into fastboot mode, so the blue light is on.
Type (similar to Step 1):
fastboot reboot bootloader
fastboot --set-active=b
fastboot reboot bootloader
You can check that Slot B is active by typing the command
fastboot getvar all
in the output check the line current slot active: b
WARNING: DO NOT BOOT Slot B, as it will fail 2-3 times (you'll notice the phone vibrating upon crash and reboot), because the phone will then put you back on Slot A, and you'll flash Slot A again. Make sure YOU DON'T BOOT the operating system in Slot B, or you'll end up in Slot A again.
Run Newflasher (how to use Newflasher is beyond the scope of this post, google it) to flash an original stock SONY image. You need to be in flash mode for Newflasher with the green light lit.
Answer the first question what to do when done with Newflasher with 'p'=Power Off, and all others with 'n'=No.
When Newflasher completes, check the last few lines output, it should say setting slot B active and OKAY. That confirms that you flashed the original SONY image in Slot B.
You now have a fully working operating system in Slot B. However there is a bug in Newflasher and that bug destroys the boot process in Slot A, which means you'll be only able to boot Slot B.
At this point in time, if you would try to boot into Slot A, it will boot up to the SONY logo, and then crash, and reboot up to the SONY logo, and then crash. Should you get stuck in that loop, insert a USB cable and hold Volume-UP, it'll catch the crashing loop, and you'll end up in fastboot.
Step 3 - Boot the original SONY image up to the home screen where the apps show:
Actually you should be in Slot B already, but if you are not:
Boot into fastboot mode, so the blue light is on.
Type (similar to Step 2):
fastboot reboot bootloader
fastboot --set-active=b
fastboot reboot bootloader
You can check that Slot B is active by typing the command
fastboot getvar all
in the output check the line current slot active: b
Boot the phone's operating original stock image in Slot B, until you are at the home screen with the apps. This sets up all the defaults for your phone, and updates any ROM images in the chips (like modem etc.).
Make sure you don't set up authentication (pin code, fingerprint), skip setting that up, so your data partition doesn't get encrypted.
Power off your phone.
Step 4 - Flash twrp into Slot B
Type (similar to Step 2):
fastboot reboot bootloader
fastboot --set-active=b
fastboot reboot bootloader
fastboot flash boot twrp.img
This will flash TWRP as boot in Slot B. Make sure in the screen output it was flashed in boot_b.
Should you make an error here, start with Step 1. The reason here is, we want LOS in Slot A, and not TWRP.
Boot your TWRP in Slot B.
WARNING: DO NOT flash VBMETA, it'll break the boot process, and you can start from Step 1.
Step 5 - Flash LOS into Slot A
Once TWRP is running, go to Wipe.
WARNING: DO NOT perform factory reset.
Go to Advanced Wipe, and ONLY WIPE 'Data' and 'Dalvic Cache'
WARNING: DO NOT WIPE System or Internal Storage. You'll loose mount points under Linux, and the LOS image flash will fail.
Go back to TWRP home screen.
From there go to Advanced and from there to ADB Sideload.
From the computer start installing your LOS image (sideload).
On the computer type:
adb sideload <Your LOS image>.zip.
ATTENTION: During flashing, the phone will show, which slot it flashes. It should flash and show: "flashing inactive Slot A". If you accidentally flash Slot B, start from the beginning Step 1.
Best results I had with the image from the LOS homepage https://download.lineageos.org/xz2c
Download the zip file, don't unpack it, use adb sideload to upload the zip file.
Forget about the Recovery image on the LOS homepage. You don't need it.
When flashing completes, you can wipe Delvic Cache.
WARNING: DO NOT WIPE 'cache', since a 2 slot phone doesn't have a cache partition, and it will fail to wipe it.
Do NOT install the TWRP app, skip this step.
Reboot
Step 6 - Boot LOS
LOS is in Slot A, TWRP is in Slot B.
You can alternate between the slots from fastboot.
fastboot reboot bootloader
fastboot --set-active=a
fastboot reboot bootloader
A reboot should boot LOS.
ATTENTION: When the LOS image has finished booting and you get to the date/time screen, the LOS will hang a while (30s). Just let it do it's job, I think (not sure), it's creating the data in the user partition. After 30s or so use the back key, and try setting the time again. This only happens on the very first boot.
Let me know as feedback, if I can clarify better or if this description is ok.
Click to expand...
Click to collapse
So this works for 17.1 - but have you tried it on 18.1?
Asking because 17.1 works well for me following the official install method (via stock LOS recovery), whereas 18.1 fails.
landsome said:
So this works for 17.1 - but have you tried it on 18.1?
Asking because 17.1 works well for me following the official install method (via stock LOS recovery), whereas 18.1 fails.
Click to expand...
Click to collapse
It works on my phone, however:
I only have a 18.0 image from Olivier. Link is here: https://androidfilehost.com/?w=files&flid=320371
Use the 700MB image, the 200MB image (dated 20201206) probably won't work, the file size is too small. Not sure what the 200MB image is for. At the time of this post the image that worked was dated 20201205.
Anybody working on a 18.1 image, please post it here? I don't have the expertise to help with 18.1 image.
Directly flashing 18.0 image by Olivier crashed my phone, I am not sure why. There is no real reason I know of, but it did.
I first flashed official LOS 17.1 image from LOS homepage using the method above, and it worked. Boot the image to the home screen to intialise everything on LOS. Should it fail, you have a corrupt LOS image. I only had nightly builds available at the time of this post. Maybe that changes soon...
I then went back to slot B and booted TWRP again. I then sideloaded the LOS 18.0 .zip image from Olivier with adb sideload <imagefile.zip> without wiping anything. Don't wipe any partitions, just flash the 18.0 LOS image over the existing installation in Slot A.
When booting the LOS 18.0 image, it says data corrupt (I don't know why), and it boots into the LOS recovery and asks for a factory reset. Do a factory reset, you'll loose all data on the phone, so backup what needs to be backed up first. You probably need to install the apps again as well.
After the factory reset, the phone boots LOS 18.0 just fine.
I noticed there is no email client in the LOS 18.0 image from Olivier. Should you need it, the following tip:
IMPORTANT: When in TWRP (before you flash LOS 18.0), MOUNT System and Data in the mount menu.
You can then find the apk for the LOS email client in the LOS 17.1 image:
/system/system/product/app/Email/Email.apk
/system/system/product/app/Exchange2/Exchange.apk
Copy these apk in the TWRP file manager to /data/media/downloads
Boot LOS 17.1 and backup these apk files to your PC to install on LOS 18.0. The apk files are in your phone's download directory after the copy operation in TWRP.
The Exchange.apk is an extension package to the Email.apk to add Exchange client functionality.
IMPORTANT: After installing the apk on LOS 18.0, and even before you start them for the first time, go to Settings, and give "Email" and "Exchange" all permissions on your phone. Just allow everything. If you don't do that, the applications will crash upon start.
Hope that helps. Any questions, please ask.
A new build is up, please check the OP. Feel free to test and report bugs - we'd like to enable official 18.1 weekly builds soon.
Olivier said:
A new build is up, please check the OP. Feel free to test and report bugs - we'd like to enable official 18.1 weekly builds soon.
Click to expand...
Click to collapse
Thanks. We appreciate this.
Hi,
I have a problem with Wire application.
Microphone is not working on call and video call.
Microphone is working to record a message. Permissions are OK.
I had the same problem on LOS 17 so I thought upgrade will resolve it. NO.
Did anyone experience the same problem?
Raphos said:
Hi,
I have a problem with Wire application.
Microphone is not working on call and video call.
Microphone is working to record a message. Permissions are OK.
I had the same problem on LOS 17 so I thought upgrade will resolve it. NO.
Did anyone experience the same problem?
Click to expand...
Click to collapse
I have the exact same problem with LOS 17, and with 18 too!
Wire is not only the affected program, skype has for example the exact same issue.
And unfortunately I do not know how to fix it.
Thanks for your reply.
Ok, good to know. I have a Z3 compact on LOS 17 and a Z5 Compact on LOS 15, Wire is working fine.
Microphone is working with whatsapp calls. Maybe Devs are whatsapp shareholders
Raphos said:
Ok, good to know. I have a Z3 compact on LOS 17 and a Z5 Compact on LOS 15, Wire is working fine.
Click to expand...
Click to collapse
I can confirm to that LOS 17 and 18 on other devices have no issues, thus it seems xz2c specific
DISCLAIMER!!!
Any lost data, bricked device or issues caused by attempting everything below is not my fault. You assume responsibility of your own actions. This has ONLY BEEN TESTED ON A BE2026!! You have been warned!
What You'll Need
Full Fastboot/ADB installed, system wide helps
-- My method is use the ADB Quick Installer (here: ADB Reborn), then also download the platform-tools and put everything in the ADB Folder (here: Select for your OS)
A GSI ROM
-- So far, only tested /e/OS DeGoogled GSI ROM, which is Android 10 based. ZERO issues thus far (here, arm64 ab: CLICKY) this rom does have issues with Wifi if you patch the boot.img with Magisk. Recommend testing 11 Based GSI's instead like LeOS which is based off of eOS
GAPPS if you so choose
Stock vbMeta.img
-- found here from OnePlus: OnePlus Software ... just select the Nord N10 and click download. or find it on a post here
Video instructions
text instructions
Instructions
1.) Download your selected GSI ROM, GAPPS (if needed), Magisk Manager, stock firmware and make sure ADB is system wide installed
2.) Unlock your bootloader
-- 2a.) Go to Settings, then About phone, tap Build number a bunch to enable developer settings
-- 2b.) Go back and select System, then Developer Settings, enable USB Debugging and OEM Unlock
-- 2c.) Plug in device, give PC developer control, and reboot to bootloader with "adb reboot bootloader"
-- 2d.) Once in bootloader mode, use "fastboot flashing unlock" to unlock the bootloader. Device will wipe and reboot to system
3.) Plug your Device into your computer, open Command prompt and type the following command. It may ask for Debugging permission on device, select yes
Code:
adb reboot bootloader
4.) Now that you're back on the Bootloader, you can use fastboot commands to get started flashing your GSI, first command to enter is
Code:
fastboot reboot fastboot
5.) You're now in Fastbootd, this allows for easier flashing. You now need your vbmeta.img. Use the command below
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
6.) Reboot fastbootd with the command from step 4, then use the commands below once rebooted
Code:
fastboot erase system
fastboot delete-logical-partition product
fastboot flash system GSI.img
fastboot -w
fastboot reboot
7.) You should now have your GSI flashed onto your device! That simple
Do NOT patch the boot.img with Magisk Manager and flash it. It breaks Wifi and Bluetooth on every single GSI Right now. If I find a work around, I will post it here.
How to Root your GSI Based ROM and keep Wifi Working!!
1.) Go to the PixelExperience ROM page and download just the Custom Recovery (here: PixelExperience Post)
2.) Once you have the recovery, reboot to bootloader
Code:
adb reboot bootloader
3.) Flash the recovery
Code:
fastboot flash recovery recovery.img
4.) Reboot to recovery, then download MagiskManager APK from Github (just follow along, I promise, here: Magisk)
5.) Select Apply Update by USB in the Recovery, and sideload with the Magisk APK (it works, trust me)
Code:
adb sideload MagiskManager.apk
6.) Reboot device, select the Magisk Icon and you're Rooted and ROM'd with working Wifi!
Thanks for the nice guide; I currently have a few problems right with installing this resurrection remix GSI:
1) I can't seem to get gapps installed on the GSI. There's never enough space, and due to the weird way the partitions on the N10 work, I can't resize the system partition in order to fit them in. Do you have any solutions for this problem?
2) I've created an overlay for the N10 in order to obtain auto brightness. It works well, but stops working after the first or second reboot. Again, do you have any solutions for this problem?
Thanks in advance.
Generic123. said:
Thanks for the nice guide; I currently have a few problems right with installing this resurrection remix GSI:
1) I can't seem to get gapps installed on the GSI. There's never enough space, and due to the weird way the partitions on the N10 work, I can't resize the system partition in order to fit them in. Do you have any solutions for this problem?
2) I've created an overlay for the N10 in order to obtain auto brightness. It works well, but stops working after the first or second reboot. Again, do you have any solutions for this problem?
Thanks in advance.
Click to expand...
Click to collapse
Personally I don't use any ROMs that have Google in them at all, so flashing gaps is something I don't think I can help you with. You could try my root method, but instead of flashing for root, Flash the gapps zip file. I found the method to root this completely by mistake. And it just happened to be the only way that worked
I did also notice that no matter what I do the screen is exceptionally bright on this phone even at its lowest setting. I have yet to try to find a solution for this because it discovered that the Sim slot on my phone is bad so I went back to my razor phone because now I have to warranty my phone
KaptinBoxxi said:
Personally I don't use any ROMs that have Google in them at all, so flashing gaps is something I don't think I can help you with. You could try my root method, but instead of flashing for root, Flash the gapps zip file. I found the method to root this completely by mistake. And it just happened to be the only way that worked
I did also notice that no matter what I do the screen is exceptionally bright on this phone even at its lowest setting. I have yet to try to find a solution for this because it discovered that the Sim slot on my phone is bad so I went back to my razor phone because now I have to warranty my phone
Click to expand...
Click to collapse
Ah, I used to own the RP2. Sold it because the battery life for my device was so mediocre. Anyways, I don't think it's possible to install GAPPS separately; they have to be integrated into what GSI I want to install or I just can't get them to fit. It seems like the traditional partitions like system have been combined into a single "super" partition. Also, when your N10 comes back from repair, you can try this overlay I've built. It should fix auto-brightness and maybe fixes the brightness curve(so the lowest setting should be much less bright).
Generic123. said:
Ah, I used to own the RP2. Sold it because the battery life for my device was so mediocre. Anyways, I don't think it's possible to install GAPPS separately; they have to be integrated into what GSI I want to install or I just can't get them to fit. It seems like the traditional partitions like system have been combined into a single "super" partition. Also, when your N10 comes back from repair, you can try this overlay I've built. It should fix auto-brightness and maybe fixes the brightness curve(so the lowest setting should be much less bright).
Click to expand...
Click to collapse
I disable auto-brightness entirely, but its still exceptionally bright. Its so weird. I still have it, haven't sent it in yet, so I'll give it a shot soon
Actually just realized its the GSI I'm using, the sim card doesn't work. Gonna try a different gsi and see what happens
I learned a lot with this tutorial. Thank you very much.
I'll begin to try some GSI roms now and see which one adapts best for me. I don't use Google either, so this GSI project was like finding a gold mine next door ha ha ha.
Thank you again.
EDIT: I was too optimistic, because following this guide only takes me to this error
Code:
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed
What can I do to avoid this?
Thank you again.
bbabel said:
I learned a lot with this tutorial. Thank you very much.
I'll begin to try some GSI roms now and see which one adapts best for me. I don't use Google either, so this GSI project was like finding a gold mine next door ha ha ha.
Thank you again.
EDIT: I was too optimistic, because following this guide only takes me to this error
Code:
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed
What can I do to avoid this?
Thank you again.
Click to expand...
Click to collapse
I suggest this method instead
MetaruSonikkuX said:
I suggest this method instead
Click to expand...
Click to collapse
I tried that method and also failed. I noticed when the script was working that it had the same errors like me: every file the script tried to flash to slot a was followed by FAILED (remote: 'Not enough space to resize partition').
So I decided to restore everything with this tool (and downgrade to Android 11 in the process) and now this guide works as it should. Right now I'm trying to use Havoc OS and the future looks bright
Thank you.
bbabel said:
I tried that method and also failed. I noticed when the script was working that it had the same errors like me: every file the script tried to flash to slot a was followed by FAILED (remote: 'Not enough space to resize partition').
So I decided to restore everything with this tool (and downgrade to Android 11 in the process) and now this guide works as it should. Right now I'm trying to use Havoc OS and the future looks bright
Thank you.
Click to expand...
Click to collapse
Could you post your experience? I tried LoS 18.1 and couldn't get microg installed, then tried AOSP 11 with gapps and kept getting a google authentication error.
MetaruSonikkuX said:
Could you post your experience? I tried LoS 18.1 and couldn't get microg installed, then tried AOSP 11 with gapps and kept getting a google authentication error.
Click to expand...
Click to collapse
You have to use GSIs with GAPPS in them to get gapps for now. no way around it
MetaruSonikkuX said:
Could you post your experience? I tried LoS 18.1 and couldn't get microg installed, then tried AOSP 11 with gapps and kept getting a google authentication error.
Click to expand...
Click to collapse
As KaptinBoxxi says, look for a GSI rom with GAPPS included, otherwise you'll have a lot of problems. I'd start for Pixel Experience but you can look for other roms here: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Generic123. said:
Ah, I used to own the RP2. Sold it because the battery life for my device was so mediocre. Anyways, I don't think it's possible to install GAPPS separately; they have to be integrated into what GSI I want to install or I just can't get them to fit. It seems like the traditional partitions like system have been combined into a single "super" partition. Also, when your N10 comes back from repair, you can try this overlay I've built. It should fix auto-brightness and maybe fixes the brightness curve(so the lowest setting should be much less bright).
Click to expand...
Click to collapse
Is there a tutorial on making these that you followed? The one I found on phh wiki didn't go so well