{
"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"
}
On our device, this message pops up after powering on the phone if you are using a custom rom.This is caused by the prop of the vendor.You can get rid of this message by my flashable zip.
Download the zip: https://mega.nz/#!A08QxQyR!TKpozqrGiDLzgHinSIS2yaEU8YEcH5cH_5uqtYf79-k]Mega.Nz
Usage:
- Flash them via TWRP recovery.No need to wipe, just flash and reboot to system.
wzedlare said:
On our device, this message pops up after powering on the phone if you are using a custom rom.This is caused by the prop of the vendor.You can get rid of this message by my flashable zip.
Download the zip: https://mega.nz/#!l4FEgK4T!cXZoZSRLF8LabxfVHZcyef_K9LXp4TxVSfmjLV9fT
Usage:
- Flash them via TWRP recovery.No need to wipe, just flash and reboot to system.
Click to expand...
Click to collapse
thanks a lot for posting, but i receive this error in mega:
Enter decryption key,
the provided key is invalid, please check that the key is correct or ask the creator of the link again.....?
7dwergen said:
thanks a lot for posting, but i receive this error in mega:
Enter decryption key,
the provided key is invalid, please check that the key is correct or ask the creator of the link again.....?
Click to expand...
Click to collapse
Try this : https://mega.nz/#!l4FEgK4T!cXZoZSRLF8LabxfVHZcyef_K9LXp4TxVSfmjLV9fTQk
wzedlare said:
Try this : https://mega.nz/#!l4FEgK4T!cXZoZSRLF8LabxfVHZcyef_K9LXp4TxVSfmjLV9fTQk
Click to expand...
Click to collapse
i get an error saying device or resource is busy when trying this for cm14
mjz2cool said:
i get an error saying device or resource is busy when trying this for cm14
Click to expand...
Click to collapse
No problem, it should still work
wzedlare said:
No problem, it should still work
Click to expand...
Click to collapse
it didn't work on my phone, i tried wiping cache, and then it flashed without errors, but i still get the error after booting the phone
mjz2cool said:
it didn't work on my phone, i tried wiping cache, and then it flashed without errors, but i still get the error after booting the phone
Click to expand...
Click to collapse
Sorry, my mistake, I gave you a wrong package, please try the latest one, It will absolutely solve your problem.
wzedlare said:
Sorry, my mistake, I gave you a wrong package, please try the latest one, It will absolutely solve your problem.
Click to expand...
Click to collapse
thanks, trying it now, hopefully the default ringtones will appear as well, as i couldn't select any ringtone before
-edit- now google play services force quits during first boot. i seem to have a lot of bad luck with this phone, no rom works for me, only stock nougat
mjz2cool said:
thanks, trying it now, hopefully the default ringtones will appear as well, as i couldn't select any ringtone before
-edit- now google play services force quits during first boot. i seem to have a lot of bad luck with this phone, no rom works for me, only stock nougat
Click to expand...
Click to collapse
, wipe required partitions and flash the rom and gapps again, it should fix your problem
Hi i have this message too after powering on the phone,i'm running with cm13 20160802(only rom worked my device).I flashed your file zip "oem fix oneteams" but it dont resolve the problem.Need a help please!How to fix it?
---------- Post added at 04:55 PM ---------- Previous post was at 04:52 PM ----------
it didn't work on my phone, i tried wiping cache, and then it flashed without errors, but i still get the error after booting the phone
My problem solved with fix v2
Related
Hi All,
I'm on 1.25.720.1 Indian Version, unrooted & stock recovery from here : http://forum.xda-developers.com/devdb/project/dl/?id=5178
When I try to update OTA, stock recovery is giving error(image attached)
I have tried almost everything. But no solution. Same error is showing every time.
Please 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"
}
jithumon said:
Hi All,
I'm on 1.25.720.1 Indian Version, unrooted & stock recovery from here : http://forum.xda-developers.com/devdb/project/dl/?id=5178
When I try to update OTA, stock recovery is giving error(image attached)
I have tried almost everything. But no solution. Same error is showing every time.
Please help.
Click to expand...
Click to collapse
You should now change this topic header to [Solved] as you already find a fantastic way to deal with it. Good work dear.
vbrsekhar said:
You should now change this topic header to [Solved] as you already find a fantastic way to deal with it. Good work dear.
Click to expand...
Click to collapse
Thankyou bro.... I forgot about this...
vbrsekhar said:
You should now change this topic header to [Solved] as you already find a fantastic way to deal with it. Good work dear.
Click to expand...
Click to collapse
What was that fantastic way???
spatone said:
What was that fantastic way???
Click to expand...
Click to collapse
It was the stock recovery from king doing the problem.
I found the stock Indian recovery from the OTA .zip itself.
It was with me & I was searching for the solution.
jithumon said:
It was the stock recovery from king doing the problem.
I found the stock Indian recovery from the OTA .zip itself.
It was with me & I was searching for the solution.
Click to expand...
Click to collapse
Even after having flashd the recovery from the OTA update zip, I face an error - "unexpected content in build.prop"
Any ideas how to go about it???
spatone said:
Even after having flashd the recovery from the OTA update zip, I face an error - "unexpected content in build.prop"
Any ideas how to go about it???
Click to expand...
Click to collapse
Have you edited that??
Try to get build.prop from my backup...
(backup your current rom>flash my backup>copy build.prop > reflash your backup >replace the build.prop with the copied one) . I'm on 1.58, that's why I'm not giving mine.
jithumon said:
Have you edited that??
Try to get build.prop from my backup...
(backup your current rom>flash my backup>copy build.prop > reflash your backup >replace the build.prop with the copied one) . I'm on 1.58, that's why I'm not giving mine.
Click to expand...
Click to collapse
I havent modified a single line in build.prop file, and I already am using your 1.50 ROM backup from your thread, so I guess I will skip the 1.58 update and wait for the next update in your thread
The D816 keeps throwing newer problems time and again....anyways thanks for maintaining that thread!
spatone said:
I havent modified a single line in build.prop file, and I already am using your 1.50 ROM backup from your thread, so I guess I will skip the 1.58 update and wait for the next update in your thread
The D816 keeps throwing newer problems time and again....anyways thanks for maintaining that thread!
Click to expand...
Click to collapse
Yeah bro.... Now its having a lagging problem in 1.58.....I'm not experiencing it...but whoever flashed my latest backup is reporting lag.
Me too waiting for the next update.
Hey guys I'm kinda new to Android I've had a chappy phone and now an LG g pad after attempting root about a dozen times I finally managed to get it root now I am trying to get TWRP to backup the tablet and change the boot animation later but every time I tried on my pc it would fail so I installed flashify and tried with that I then I got a boot error saying security issues. The tablet stills boots but I believe the problem is the locked boot loader. Thanks for any help offered.
{
"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"
}
Look at this thread where some options for flashing TWRP are discussed: http://forum.xda-developers.com/lg-g-pad-83/help/recovery-mode-t2880087
Okay thanks ill check it out
Btw i think my boot loader is locked will this affect it?
Thanks
rooing problems
Joshhi said:
Btw i think my boot loader is locked will this affect it?
Click to expand...
Click to collapse
Have you installed root checker or another program to confirm that you do, in fact, have root? Start with that.
If you haven't installed a superuser app to handle permissions, I'd do that as well before trying to install TWRP.
I'll admit I had troubles installing TWRP as well, when looking at the forums, make sure you're downloading the version for your EXACT version of android and firmware, and following the instructions for the right version as well. Good luck!
yojimboj said:
Have you installed root checker or another program to confirm that you do, in fact, have root? Start with that.
If you haven't installed a superuser app to handle permissions, I'd do that as well before trying to install TWRP.
I'll admit I had troubles installing TWRP as well, when looking at the forums, make sure you're downloading the version for your EXACT version of android and firmware, and following the instructions for the right version as well. Good luck!
Click to expand...
Click to collapse
I got it flashed yesterday forgot to post that so i tried to change the boot animation and soft bricked it luckily i backed up
Joshhi said:
I got it flashed yesterday forgot to post that so i tried to change the boot animation and soft bricked it luckily i backed up
Click to expand...
Click to collapse
Will be good if you share how you doit, becouse i have a same problem. Tnx
adler123 said:
Will be good if you share how you doit, becouse i have a same problem. Tnx
Click to expand...
Click to collapse
Do what? Unbricked it or flashed twrp?
Joshhi said:
Do what? Unbricked it or flashed twrp?
Click to expand...
Click to collapse
flashed twrp to v50020d
atomicblue said:
flashed twrp to v50020d
Click to expand...
Click to collapse
I believe it was this
Further in the thread they tell you that you have to change the command from v500-20a to d
http://forum.xda-developers.com/showthread.php?t=2698267
I also think youll have to flash the latest version of twrp from a zip manually
So, recently I tried to use this ROM: http://forum.xda-developers.com/zenfone2/development/stock-rom-ul-z00a-ww-2-20-40-168-t3354526
after revert back from CM13 custom ROM: http://forum.xda-developers.com/zen.../rom-cyanogenmod-13-0-nightly-builds-t3264492
But the result is my phone stuck in Asus logo.
Tried to access recovery by pressing power button + volume up but cannot go into recovery.
Tried to connect phone to PC via USB cable but the phone is not detected (cannot try fastboot from PC).
Here is what I did before my phone bricked:
1. Reboot into recovery (I'm using TWRP)
2. Wipe everything except MicroSD
3. Install SuperSU (downloaded from the thread)
4. Install ROM v168 (downloaded from the thread)
5. Reboot system
After that my phone stuck in Asus logo.
Tried to search solution from many sources still no luck. Already posted in the thread but still no answer from anyone.
Please help because I don't have backup phone :crying:
Thanks.
Did you really flash supersu before you flashed the Rom? That's probably the cause. Have you tried any of the bootloop solutions posted here yet?
Sent from my ASUS_Z00A using Tapatalk
If you cant go recovery try using this method..
It goddamn works ��
Requires sometime to understand it though. But you'll get it ��
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
Vinaygan said:
If you cant go recovery try using this method..
It goddamn works ��
Requires sometime to understand it though. But you'll get it ��
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
Click to expand...
Click to collapse
Yup, tried this method and my phone is resurrected.
But the content of that tutorial was hard to understand at the beginning
kenbo111 said:
Did you really flash supersu before you flashed the Rom? That's probably the cause. Have you tried any of the bootloop solutions posted here yet?
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
I've followed the steps provided in the thread so I assumed that superSU was flashed already.
How to verify if it's flashed or not? Can I verify before moving on to the next step?
My phone is resurrected now thanks to steps provided by summit.
Could it be because I was using TWRP before?
i had problem like you. i dont have bootloader and fastboot. i use xFSTK-Downloader.
success.
i can help you
fb: facebook.com/hieulanhat123
sorry my English i am from vietnam
I tried the summit method on a Win10 machine but it doesn't detect the phone on xFSTK-Downloader, can somebody help me?
This is how the phone looks right now:
{
"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"
}
arturocr said:
I tried the summit method on a Win10 machine but it doesn't detect the phone on xFSTK-Downloader, can somebody help me?
This is how the phone looks right now:
Click to expand...
Click to collapse
Bruh...
I've successfully recovered my phone using xFSTK
On a win10 os
---------- Post added at 02:01 PM ---------- Previous post was at 01:50 PM ----------
arturocr said:
I tried the summit method on a Win10 machine but it doesn't detect the phone on xFSTK-Downloader, can somebody help me?
This is how the phone looks right now:
Click to expand...
Click to collapse
1. Make sure your device shows up for awhile during boot
(when the phone vibrates upon boot)
2. Make sure you selected MOOREFIELDS.
3. Once done selecting the files " change the gp override flag under OPTION to 0x80000807"
Hey there,
I want to switch to these htt ps://download .lineageos. org/oneplus2 LOS 14.1 builds as I'm currently using LOS 14.1 by daktak. (Sorry, not allowed to post links right now..)
There haven't been any updates for almost 3 weeks now and I don't think that this will be updated any further.
Well, simply booting into recovery mode and flashing the newest LOS zip doesn't work for me. I guess it's because I'm not wiping my system partition, just data + dalvik cache... I thought I can simply switch/update from an older version of LOS? Do I really need to wipe everything again so I can install the LOS builds I've mentioned above?
Also I don't really understand the difference between signed and unsigned zips. The zip I want to flash is signed. Is this why I get "Failed to flash" as an error message in recovery? Does "signed" mean, I need to root my OP2 again and my current root will be removed?
Current LOS version 14.1-20170213-UNOFFICIAL-oneplus2 by daktak
Yakumichan said:
Hey there,
I want to switch to these htt ps://download .lineageos. org/oneplus2 LOS 14.1 builds as I'm currently using LOS 14.1 by daktak. (Sorry, not allowed to post links right now..)
There haven't been any updates for almost 3 weeks now and I don't think that this will be updated any further.
Well, simply booting into recovery mode and flashing the newest LOS zip doesn't work for me. I guess it's because I'm not wiping my system partition, just data + dalvik cache... I thought I can simply switch/update from an older version of LOS? Do I really need to wipe everything again so I can install the LOS builds I've mentioned above?
Also I don't really understand the difference between signed and unsigned zips. The zip I want to flash is signed. Is this why I get "Failed to flash" as an error message in recovery? Does "signed" mean, I need to root my OP2 again and my current root will be removed?
Current LOS version 14.1-20170213-UNOFFICIAL-oneplus2 by daktak
Click to expand...
Click to collapse
It is all explained here:
http://lineageos.org/Update-and-Build-Prep/
jhedfors said:
It is all explained here:
http://lineageos.org/Update-and-Build-Prep/
Click to expand...
Click to collapse
Thank you for your quick reply! After some issues using adb I could not fix (but I don't need to as I already did this somehow earlier for CM13) I managed to install LOS14.1 HYPE!
Maybe you could help me with my problem?
"No command 'fastboot' found"... But I can find my phone using adb devices.
Screenshot attached...
{
"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"
}
Yakumichan said:
Thank you for your quick reply! After some issues using adb I could not fix (but I don't need to as I already did dis somehow earlier for CM13) I managed to install LOS14.1 HYPE!
Maybe you could help me with my problem?
"No command 'fastboot' found"... But I can find my phone using adb devices.
Screenshot attached...
Click to expand...
Click to collapse
I am not an expert on adb/fastboot, but is the fastboot binary in the directory? It is also a little difficult to interpret the language in your sceenshot.
jhedfors said:
I am not an expert on adb/fastboot, but is the fastboot binary in the directory? It is also a little difficult to interpret the language in your sceenshot.
Click to expand...
Click to collapse
Right, sorry. It's German and it says that the command "fastboot" either has been written wrong or hasn't been found.
And also: Yes, it is:
I think you need to check your drivers
The device should be connected via adb interface driver or android driver
After that you should be able to see ur device
System / TWRP http://bigota.d.miui.com/8.10.25/miui_HM5Plus_8.10.25_55b500ece7_7.1.zip
System / TWRP http://bigota.d.miui.com/8.10.18/miui_HM5Plus_8.10.18_443e580d5d_7.1.zip
System / TWRP http://bigota.d.miui.com/8.10.11/miui_HM5Plus_8.10.11_87dd95bb99_7.1.zip
System / TWRP http://bigota.d.miui.com/8.9.20/miui_HM5Plus_8.9.20_5dfb75137e_7.1.zip
System / TWRP http://bigota.d.miui.com/8.9.13/miui_HM5Plus_8.9.13_ba9d52cae5_7.1.zip
System / TWRP http://bigota.d.miui.com/8.9.6/miui_HM5Plus_8.9.6_872f93e2fa_7.1.zip
MiFlash / fastboot http://bigota.d.miui.com/8.10.25/vince_images_8.10.25_20181025.0000.00_7.1_cn_8dccda8963.tgz
MiFlash / fastboot http://bigota.d.miui.com/8.10.18/vince_images_8.10.18_20181018.0000.00_7.1_cn_0f8131cdd5.tgz
MiFlash / fastboot http://bigota.d.miui.com/8.10.11/vince_images_8.10.11_20181011.0000.00_7.1_cn_2617acf331.tgz
MiFlash / fastboot http://bigota.d.miui.com/8.9.20/vince_images_8.9.20_20180920.0000.00_7.1_cn_7965674719.tgz
MiFlash / fastboot http://bigota.d.miui.com/8.9.13/vince_images_8.9.13_20180913.0000.00_7.1_cn_bf4958ac0b.tgz
MiFlash / fastboot http://bigota.d.miui.com/8.9.6/vince_images_8.9.6_20180906.0000.00_7.1_cn_0b82cf4b14.tgz
Camerado said:
TWRP http://bigota.d.miui.com/8.7.2/miui_HM5Plus_8.7.2_76770ccbd5_7.1.zip (closed beta)
Click to expand...
Click to collapse
Thanks bro will flash when i will reach home
I'm actually curious but unlocking my bl still needs several hundred hours of waiting.
Anyone tried this? A review and buglist would be much appreciated, and thanks for leaking bro!
Nougat
Any screen problems ? Like overburn ?
vipkokata said:
Any screen problems ? Like overburn ?
Click to expand...
Click to collapse
No, all ok.
Rajce said:
Nougat
Click to expand...
Click to collapse
Yes
When I flashed the rom the first time my phone shut off. The second time it did finish flashing but it won't boot for me.
Am I doing something wrong? I cleared system,data,cache,dalvik.
Please upload to MEGA ... china server is very slow
DeZwarteRijder said:
When I flashed the rom the first time my phone shut off. The second time it did finish flashing but it won't boot for me.
Am I doing something wrong? I cleared system,data,cache,dalvik.
Click to expand...
Click to collapse
Need flash LazyFlasher or Magisk after.
The rom has no gapps, how can I install playstore?
Boots fine! Didn't find much changes other than status bar and volume control animations. No PnP nothing.
---------- Post added at 02:26 PM ---------- Previous post was at 02:25 PM ----------
DeZwarteRijder said:
When I flashed the rom the first time my phone shut off. The second time it did finish flashing but it won't boot for me.
Am I doing something wrong? I cleared system,data,cache,dalvik.
Click to expand...
Click to collapse
Flash magisk after flashing Rom, And it will boot.
{
"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"
}
Version
Will flash today, thanks.
installed via twrp, but system does not boot up, using old boot, but still in loop, any sugestions?
got a solution, patch the boot.img and works!
Well, looks like vince s won't get Oreo-based MIUI after all
Jerome-X said:
installed via twrp, but system does not boot up, using old boot, but still in loop, any sugestions?
got a solution, patch the boot.img and works!
Click to expand...
Click to collapse
Camera has the portrait mode?
moralesnery said:
Well, looks like vince s won't get Oreo-based MIUI after all
Click to expand...
Click to collapse
Public beta will be Oreo based
T-2 said:
The rom has no gapps, how can I install playstore?
Click to expand...
Click to collapse
Search google on mi app store and install the below app.
inouext said:
Camera has the portrait mode?
Click to expand...
Click to collapse
Nope! Same MIUI 9 Camera.