hi, i am using quiksense 3.0, i would like to ask.....
* Is this normal when i got some Ramdom reboot ?(maybe one day one time)
i dont know i never had that problem. and i am using the latest faux123 kernal
taktak01 said:
hi, i am using quiksense 3.0, i would like to ask.....
* Is this normal when i got some Ramdom reboot ?(maybe one day one time)
Click to expand...
Click to collapse
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
Binary100100 said:
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
Click to expand...
Click to collapse
let me capture my screen for you to check is there something wrong.
otherwise, i am not sure if i flash the kernel successfully.
this is my kernel info.......
{
"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"
}
i tried to flash the boot.img again though easy kernel flasher.it seems not good.
the dos windows show:
--------------------------------------------------
sending "boot" ..... okay
writing "boot" ..... failed ( remote not allowed)
------------------------------------------------------
is this case by my locked bootloader?
can i use CMW recovery to flash the kernel that i need?
thanks
taktak01 said:
i tried to flash the boot.img again though easy kernel flasher.it seems not good.
the dos windows show:
--------------------------------------------------
sending "boot" ..... okay
writing "boot" ..... failed ( remote not allowed)
------------------------------------------------------
is this case by my locked bootloader?
can i use CMW recovery to flash the kernel that i need?
thanks
Click to expand...
Click to collapse
It's mentioned only about 200 times that you MUST have unlocked your bootloader.
Sent from my HTC Amaze 4G using xda premium
oh, this is my bad..... thanks for explain it for me
one more thing, i dont understand if i MUST have to flash the kernel for 2.1.0?
( my quiksense is upgraded from v1.5.1 to v3.0.0 , seems everything is okay except the random reboot situation. )
thanks
taktak01 said:
oh, this is my bad..... thanks for explain it for me
one more thing, i dont understand if i MUST have to flash the kernel for 2.1.0?
( my quiksense is upgraded from v1.5.1 to v3.0.0 , seems everything is okay except the random reboot situation. )
thanks
Click to expand...
Click to collapse
It's fine to go from 1.5.1 to v.3.0.0
taktak01 said:
is this case by my locked bootloader?
can i use CMW recovery to flash the kernel that i need?
thanks
Click to expand...
Click to collapse
Wait a second, how did you flash QuikSense 3.0 without unlocking the bootloader? I assume you have S-Off? In any case, you can flash the faux kernel http://forum.xda-developers.com/showthread.php?t=1359951 from CWM now.
Thanks!
verkion
verkion said:
Wait a second, how did you flash QuikSense 3.0 without unlocking the bootloader? I assume you have S-Off? In any case, you can flash the faux kernel http://forum.xda-developers.com/showthread.php?t=1359951 from CWM now.
Thanks!
verkion
Click to expand...
Click to collapse
More than likely he relocked it. Why anyone would want to do that with the exception of flashing an RUU is beyond me.
And the CWM method of flashing kernels is just a hack that I came up with. It's not really updating the kernel at that point. By this method your kernel isn't updated until AFTER your device has already booted up. So if your device doesn't boot up at all it's probably because you still need to use the fastboot flash method to update the kernel.
Binary100100 said:
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
Click to expand...
Click to collapse
I'm not sure what to take from this? I'm also getting that random reboot on the faux v007 kernel on quiksense..a little more detail could probably set me in the right direction.
I've unlocked and all that good stuff..
James12 said:
I'm not sure what to take from this? I'm also getting that random reboot on the faux v007 kernel on quiksense..a little more detail could probably set me in the right direction.
I've unlocked and all that good stuff..
Click to expand...
Click to collapse
flash faux .008b3 should be more stable
Related
I have a HTC Desire S that's stuck after flashing BOOT.IMG using fastboot option.
My device is
S-ON
Unlocked,
HBOOT 2.00.002
{
"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"
}
In this thread (http://forum.xda-developers.com/showthread.php?t=1390496) it clearly states that since my device is HBOOT 2.00.002 I can't install custom rom using the old-fashioned way and I must flash BOOT.IMG from the rom.
So I did EXACTLY as dtronics said in that thread, ROOTED my device, installed CWM using ROM Manager, and then decided to flash boot.img using fastboot (http://forum.xda-developers.com/showthread.php?t=1752270).
That also completed succesfuly with no errors but now my phone continuously restarts itself into CWM. It can't start the stock rom or the custom.
then after I press (VOL+) + (POWER) keys on this Red icon screen I enter CWM
And now I can't go any further, I'm stuck. Please help!
karabaja2 said:
I have a HTC Desire S that's stuck after flashing BOOT.IMG using fastboot option.
My device is
S-ON
Unlocked,
HBOOT 2.00.002
In this thread (http://forum.xda-developers.com/showthread.php?t=1390496) it clearly states that since my device is HBOOT 2.00.002 I can't install custom rom using the old-fashioned way and I must flash BOOT.IMG from the rom.
So I did EXACTLY as dtronics said in that thread, ROOTED my device, installed CWM using ROM Manager, and then decided to flash boot.img using fastboot (http://forum.xda-developers.com/showthread.php?t=1752270).
That also completed succesfuly with no errors but now my phone continuously restarts itself into CWM. It can't start the stock rom or the custom.
then after I press (VOL+) + (POWER) keys I enter CWM
And now I can't go any further, I'm stuck. Please help!
Click to expand...
Click to collapse
after flashing boot.img
use command fastboot erase cache
and always perform full wipe, erase cache and dalvik cache before installing a fresh new ROM
vivek_bhoj said:
after flashing boot.img
use command fastboot erase cache
and always perform full wipe, erase cache and dalvik cache before installing a fresh new ROM
Click to expand...
Click to collapse
Thanks, I did that, but it wasn't the problem. I just figured it out! The problem was in CWM.
The guide was a bit unclear so I obviously didn't flash it right. This is what I did, i flashed new CWM image using this tutorial (sorry, can't paste outside link), the best and easiest way to do this.
I was really worried I bricked the phone, now everything is working great!! :good:
gist.github.com/1694742
karabaja2 said:
Thanks, I did that, but it wasn't the problem. I just figured it out! The problem was in CWM.
The guide was a bit unclear so I obviously didn't flash it right. This is what I did, i flashed new CWM image using this tutorial (sorry, can't paste outside link), the best and easiest way to do this.
I was really worried I bricked the phone, now everything is working great!! :good:
gist.github.com/1694742
Click to expand...
Click to collapse
Why not use 4ext recovery? 4ext recovery has a tool called HTC Smartflash for S-On devices/HTCDEV Unlocked devices that make flashing a lot easier, so you won't have to run into issues like this.
GazaIan said:
Why not use 4ext recovery? 4ext recovery has a tool called HTC Smartflash for S-On devices/HTCDEV Unlocked devices that make flashing a lot easier, so you won't have to run into issues like this.
Click to expand...
Click to collapse
Not really familiar with using 4ext recovery so I decided to go this way. I'll be changing rom soon, since I'm trying to find the one with best battery life, so then I'll try 4ext too.
{
"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"
}
Recovery
Download
Don't use it if you have HTC One X+ from AT&T
Version 0.3
- Fixed mounting SD card inside recovery
Issues:
- None found yet
How to flash:
- unlock your bootloader via htcdev site
- rename the file to "recovery.img"
- go to bootloader ---> fastboot
- type "fastboot flash recovery recovery.img"
Rooting Tools
Download
How to flash:
- from inside recovery
You flash it all at your own risk!
Thanks to olhel, konsti23 & orb3000 for help in tests
Cool! Thanx!! Go flashing )) Done. Seems everything looks good))
Hmm, cant mount /sdcard
Atze001 said:
Hmm, cant mount /sdcard
Click to expand...
Click to collapse
Yes, I'm working on it.
Does it mean at this stage we cant flash SU?
Thanks Mike,
great that you are working on a custom recovery so that we can flash your custom rom Go ahead...
Atze001 said:
Does it mean at this stage we cant flash SU?
Click to expand...
Click to collapse
Correct. I know where the issue is and I will fix it as soon as possible Without the device it might take bit longer, but I will surely fix it
mike1986. said:
Correct. I know where the issue is and I will fix it as soon as possible Without the device it might take bit longer, but I will surely fix it
Click to expand...
Click to collapse
No Hurry. Great Work :good:
Thanks Mike!
As I am already rooted just to flash recovery and ready to test a custom ROM right?
orb3000 said:
Thanks Mike!
As I am already rooted just to flash recovery and ready to test a custom ROM right?
Click to expand...
Click to collapse
Not yet mate, mounting internal sd card doesnt work yet.
Sent from my HTC One X
Thanks mate, all clear now.
Great work!
Cheers,
Same problem as the other recovery.
Sent from my HTC One V using Tapatalk 2
shubhamchamaria said:
Same problem as the other recovery.
Sent from my HTC One V using Tapatalk 2
Click to expand...
Click to collapse
HTC used different method to manage internal sdcard in the device then one x thats why we have problems.
Sent from my HTC One X
Someone with rooted hox+ can join my IRC channel for few minutes?
Recovery fixed, have fun
Confirmed working!!!!
Doing nandroidbackup to flash custom ROM after!!
Thanks Mike1986 and Lloir!!
building my toolkit now. Thanks Mike and Lloir!
Yeah...so I tried it on the AT&T version of the One X+. CWM installs OK, but when you reboot into recovery you get the following error:
E:Can't mount /sdcard/
Of course now, the phone will no-longer boot into anything other than recovery or bootloader. Any ideas?
orb3000 said:
Confirmed working!!!!
Doing nandroidbackup to flash custom ROM after!!
Thanks Mike1986 and Lloir!!
Click to expand...
Click to collapse
sorry for the dumb question but how to "fashboot" flash recovery?
jimok82 said:
Yeah...so I tried it on the AT&T version of the One X+. CWM installs OK, but when you reboot into recovery you get the following error:
E:Can't mount /sdcard/
Of course now, the phone will no-longer boot into anything other than recovery or bootloader. Any ideas?
Click to expand...
Click to collapse
Flash RUU. I dont think this recovery will work on att variant.
Sent from my HTC One X
How to use by TK
{
"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"
}
Whats new in V6
Updated TWRP to 2.8.6.0
Updated SuperSu to 2.46
Easily copy SuperSu to your Device with “Prepare”
This version don’t come with CM. You can download CM12S and flash with Recovery. Click here for more details
Features
Lock/Unlock Bootloader
Install Custom Recovery (CWM, TWRP & Philz)
Install Stock Recovery
Root Device (Manual)
Note
Please download V6 if you are going to Unlock bootloader, Root, Change Recovery. Because others include CM11S installation files which is huge.
Download Link:
Click Here
Hints (Manual)
Enter fastboot mode: Turn the phone off. Hold volume up + power until the "fastboot" screen appears.
Make sure you have drivers installed.
Looks good!!! Can i do a feature request? Can you add "flash stock img" in newer versions? Thanks in advance.
acuicultor said:
Looks good!!! Can i do a feature request? Can you add "flash stock img" in newer versions? Thanks in advance.
Click to expand...
Click to collapse
You mean latest CM11s?
alex.inthi said:
You mean latest CM11s?
Click to expand...
Click to collapse
I mean full stock rom cm11s no matter which version, i think only XNPH22Q. Is available for flash using fastboot commands.
http://forum.xda-developers.com/showthread.php?t=2765455
acuicultor said:
I mean full stock rom cm11s no matter which version, i think only XNPH22Q. Is available for flash using fastboot commands.
http://forum.xda-developers.com/showthread.php?t=2765455
Click to expand...
Click to collapse
Now you can install CM11S. v2 is up.
alex.inthi said:
Now you can install CM11S. v2 is up.
Click to expand...
Click to collapse
Thanks, you are so fast!!!!
I did not understand if the phone goes offline when it is still turned off and then turn it on in fastboot mode manually.
pablomoreno said:
I did not understand if the phone goes offline when it is still turned off and then turn it on in fastboot mode manually.
Click to expand...
Click to collapse
Turn off the device, then enter fastboot mode (bootloader), connect usb, profit.
Hello
Hello;
i have a Oneplus 64Go.
I have donwload your toolbox.
When i click in Boot Fastboot
The Phone reboot.
and i ask a question in chinese , i click left and then the phone reboot and my phone is whip
Best regard.
Toufic
toufic48 said:
Hello;
i have a Oneplus 64Go.
I have donwload your toolbox.
When i click in Boot Fastboot
The Phone reboot.
and i ask a question in chinese , i click left and then the phone reboot and my phone is whip
Best regard.
Toufic
Click to expand...
Click to collapse
Looks like you just unlocked your bootloader... It's standard procedure is to wipe the phone after that.
Hi! When I start this tooblox and check if the device is attached, I see that it is. But when in fastboot mode, it's not. Help please.
Regards
SWEEEEET NICE :good:
Might be a dumb question, but can this also add support to install color os?
Windows only? It seems to be nohting more than tool that executes adb and fastboot commads, but should be useful for newbies
I can't use Google Play after rooted the phone.
Recovery: CWM
Any help?
Thanks.
Why is the file over 400MB big?
Linux4ever85 said:
Why is the file over 400MB big?
Click to expand...
Click to collapse
App, tools, system image (cm ROM), I think...
Sent from my Sony Xperia™ Z using Tapatalk 4
Would routing wipe my phone and is there any advantages in unlocking the boot loader... Sorry I'm coming an S3 rooting was very simple on it!
Great job OP! It only took me 10 minutes from downloading, to unlocking the bootloader and flashing a Custom Recovery. Thanks
jojohnson250 said:
Would routing wipe my phone and is there any advantages in unlocking the boot loader... Sorry I'm coming an S3 rooting was very simple on it!
Click to expand...
Click to collapse
Yes, unlocking the bootloader then rooting the device will wipe it. You can perform a back up first though. The advantages of rooting are many, to numerous to list here but put simply it allows you to change just about every facet of the phone.
Download:
DOWNLOAD ROM
Kernel source:
Source
DOWNLOAD EAS KERNEL
MAJOR BUGS:
?
other bugs:
Reboot on first recorded fp
If you have FocalTech Panel Keydisabler wont work.
flash on your own risk.
FLASHING
if you are/were encrypted then booting into bootloader and issuing fastboot format userdata is HIGHLY recomended if comming from stock or other roms (this will totaly erase all your userdata).
If you have weird issues follow this guide:
https://forum.xda-developers.com/showthread.php?t=3609786
DOWNLOAD GAPPS
BeansGAPPS
Changelog
Changelog
Build prop editor
recomended for android pay or banking apps. changes userdebug to user in build.prop.
for ota just put it in /sdcard/OpenDelta/flashafterupdate/ folder and it will auto flash after every ota.
Flashable Build Prop Editor/Mod
------------------------------------------------------------
bug reports now open. Please try to include logs.
{
"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"
}
Here he is, best dev ever thank you
Can som1 from the 727 guys do a bootloader getvar all
In 720 there is nothing distinguishable there
Sent from my Nexus 6P using Tapatalk
darkobas said:
Can som1 from the 727 guys do a bootloader getvar all
In 720 there is nothing distinguishable there
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I can do it, but to be honest I do not know how to do it, also I am full stock, locked bootloader and no root. If that works I can get you the information, a little guide will be great :good:
TheDethEgineer said:
I can do it, but to be honest I do not know how to do it, also I am full stock, locked bootloader and no root. If that works I can get you the information, a little guide will be great :good:
Click to expand...
Click to collapse
you have to have adb and fastboot
then>
adb reboot bootloader
fastboot getvar all
fastboot reboot
darkobas said:
you have to have adb and fastboot
then>
adb reboot bootloader
fastboot getvar all
fastboot reboot
Click to expand...
Click to collapse
hope this helps
TheDethEgineer said:
hope this helps
Click to expand...
Click to collapse
Hmm doesn't seem to be any device attached :/
TheDethEgineer said:
hope this helps
View attachment 3974994
Click to expand...
Click to collapse
thanx.... but no luck... this was my hope to create unified 720/727 builds....
Does this mean its strictly a 727 or 720 build?
PeaKay.18 said:
Does this mean its strictly a 727 or 720 build?
Click to expand...
Click to collapse
I think its just a build.prop difference in these two but i cant be sure, i dont have both
but i am pretty sure it wont explode
PeaKay.18 said:
Does this mean its strictly a 727 or 720 build?
Click to expand...
Click to collapse
Insert my screen
darkobas said:
thanx.... but no luck... this was my hope to create unified 720/727 builds....
Click to expand...
Click to collapse
Will a complete boot and system image help? Someone uploaded for the 727 and I saved it. Otherwise I have already flashed the bootloader t unlock . I really want to get the rom going on the 727. Will get the coffee you deserve as well!
zmanfarlee said:
Will a complete boot and system image help? Someone uploaded for the 727 and I saved it. Otherwise I have already flashed the bootloader t unlock . I really want to get the rom going on the 727. Will get the coffee you deserve as well!
Click to expand...
Click to collapse
no, afaik it will work...
darkobas said:
no, afaik it will work...
Click to expand...
Click to collapse
ok well thank you for interest in the phone. Hopefully it keeps building. As far as I know it's just the build prop that makes the difference and then the modem that needs to be flashed for 727 phones (have that if you need also)
zmanfarlee said:
ok well thank you for interest in the phone. Hopefully it keeps building. As far as I know it's just the build prop that makes the difference and then the modem that needs to be flashed for 727 phones (have that if you need also)
Click to expand...
Click to collapse
yeah so, modem u already have and build prop is not mandatory afaik.
edit: Made incorrect assumption
It's been a hassle but I installed on my x727 and flashed the us modem and so far have superior result.
Has been installed on my 720, in addition to the camera you have declared can not work, the other is great. This is a good start! Appreciate your work!
No built-in root program?
I am using the super SU to get permission
I can confirm it works. Still ways to go but impressive. I appreciate the hard work. Wish I could help more
{
"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"
}
OFFICIAL DOWNLOADS FOR SUZU:
https://twrp.me/sony/sonyxperiax.htmltwrp-3.x.x_x-x-suzu.img: Official TWRP image
DEVELOPMENT DOWNLOADS FOR SUZU:
Folder: https://sourceforge.net/projects/loire-development/files/twrp-recovery/suzu/twrp-3.x.x_x-x-YYYYMMDD-suzu.zip: Flashable unofficial TWRP to FOTAKerneltwrp-3.x.x_x-x-YYYYMMDD-suzu.img: Unofficial TWRP image
INSTALLATION
MANUALLY TO FOTAFastboot: Adapt the image name and install this way:fastboot flash recovery twrp-3.x.x_x-x-suzu.imgfastboot rebootFROM EXISTING RECOVERY
Enter to the current recovery
Install flashable TWRP
Reboot/Power off
HOW TO ENTER TO THE RECOVERY:
Power off your phone
Press Power and Vol- buttons at the same time until vibration
Wait for TWRP load
Sources:
TWRP device tree: https://github.com/TeamWin/android_device_sony_suzu/tree/android-9.0Kernel: https://github.com/Chippa-a/kernel-copyleft/tree/34.4.A.2.xxxThanks to the TWRP Team!
Backup-Restore function working fine so far, only issue I am seeing is phone is heating up pretty faster than before while backing up in compression mode.
Another minor thing is that earlier when entering recovery mode a purple light used to blink, now its missing.
Just saw this now and I'm really grateful. Big ups to you, man. Great work.
And I was afraid there would be no 3.2.1 for this device;
@Chippa_a makes it possible - intensified thanks! :highfive::good::good:
Thank you!!
I can't flash the zip because twrp does not give access to that part of the storage, weird.
fusk said:
I can't flash the zip because twrp does not give access to that part of the storage, weird.
Click to expand...
Click to collapse
Weird. Try using flash tool to fastboot the image if the flashable zip doesn't work for you.
Updated from TWRP, backup/restore works, no problems so far apart from it needs more than a minute till TWRP GUI appears after boot. Thanks for update.
Do you use the stock kernel? I installed the recovery built by oshmoun in the omnirom thread. It uses the aosp kernel. It starts faster, has a better sdcard naming and can flash oem images. Maybe you could try this kernel.
I use stock kernel (Pexorom 4.5) so this may be the reason for the delay.
I mean the kernel used with the recovery, not the rom kernel.
I_am_Blackford said:
Weird. Try using flash tool to fastboot the image if the flashable zip doesn't work for you.
Click to expand...
Click to collapse
This is what i did. Download img, place file on phone. Download twrp app, pick choose a file, browse to recovery.img, flash. Power off, boot to recovery = win.
Reboot to system, retry installing new update = great success.
mase76 said:
I mean the kernel used with the recovery, not the rom kernel.
Click to expand...
Click to collapse
Sorry, I didn't get it... kernels everywhere.
However, flashing with fastboot leads to the same delayed start. Strange.
privatim said:
Sorry, I didn't get it... kernels everywhere.
However, flashing with fastboot leads to the same delayed start. Strange.
Click to expand...
Click to collapse
I dont know if there is a connection, but i've tested the recovery with OmniROM 7.1.2, where display is not responding. It can be installed, shows 3.2.1, but display remains dead 4 touch.
Give this one a try:
https://forum.xda-developers.com/showpost.php?p=76440401&postcount=333
mase76 said:
Give this one a try:
https://forum.xda-developers.com/showpost.php?p=76440401&postcount=333
Click to expand...
Click to collapse
Same result, whether fastboot or flashtool, display is dead.
Certainly missed ODM LOIRE v12, v11 is installed.
Not really sure is the latest bootloader.
Does restoring a backup change the bootloader as well?
Edit: Solved: the answer is 'yes'.
3.2.1 does not work @7.1.2 restore because of outdated bootloader.
privatim said:
I use stock kernel (Pexorom 4.5) so this may be the reason for the delay.
Click to expand...
Click to collapse
Moved to XGEN ROM and now TWRP starts without delay. :good:
privatim said:
Moved to XGEN ROM and now TWRP starts without delay. :good:
Click to expand...
Click to collapse
What I do not understand, maybe bootloader or encryption, but why is 3.2.1 not backwards compatible on Suzu?
Is Omni 7.1.2 kernel (more I have not tried) or not current boot loader the reason?
Installed on last nougat internal storage 0 help
Inviato dal mio F5121 utilizzando Tapatalk
I'm glad that you finally managed to crack this damn decryption. I felt really bad with my broken promise of delivering the working build. I'm sorry, guys. @Chippa_a congratulations on your hard work