Related
Hey guys.
I'm new to this forum... and am posting this as I no longer know what to do, and need some guidance.
First I'll say that I've looked ALL OVER this forum and others, but couldn't solve my problem.
...So I subscribed in the hopes that someone will be able to more properly guide me.
------------------------------------------
So, first thing's fisrt - the story from the beginning:::
My device is an OPPO Find7 (QHD Version)
I've been using Cyanogenmod 11 for many months and without any problems.
Few days ago I installed the first nightly update of CM12 - and phone went into boot loop.
I had to restore to the ColorOS backup that was saved on my phone... Reinstalled CM11 and all is good.
Later I again updated to CM12 - and again was forced to revert back to Backup and then to CM11 due to bugs (phone wouldn't wake up after being locked, etc)
Anyway, There were three nightly build of CM12 to that point,and the last one was working in a relatively stable manner,
exept two bugs.
1. Contact names didn't appear when mamkiing to receiving a call - even though they were saved on the phone.
But this bug can be overlooked.
2. This one was more cirtical - - For some reason the phone said that I have no more free
space (even though I had 20+GB), thus preventing me from installing or updating
anything.
I figured that, perhaps, becuase of all the re-installs that I've done - my system memory got clogged.
So I decided, with more haste than thought, to perform a full wipe...SDcard and all, which consequently also removed
my ColorOS backup and everything, basically.
-----------------------------------------
The currrent outcome of what I did:::
Phone has no OS installed on it, and PC doesn't llow my to put files in there.
I can currently boot in three different states:
1. Normal boot with power button - - - OPPO logo appears - followed by a black
screen PC recognizes that I've connected a device, tries to install MTP Device and
evetually fails.
2. Power Button + Vol Up - - - Fastboot screen.
3. Power button+Vol-Down - - - Boots into the Gummified Team Win Recovery 2.7.1.0
In here, several things need to be mentioned.
- In the "Mount" section, I can choose which Partitions to mount to unmount, but
don't actually have the "Mount" button inside... So I can't mount.
- ADB Sideload doesn't work. When activating - it says "Starting ADB Sideload
Feature and just goes on forever, until I cancel it - and it says that it failed.
--------------------------------------------------
What I tried doing:::
Tried to use the Recovery Installer for OPPO, which is the exe that is available on the internet, that comes with drivers and all - and open command line with various options.
Tried installing the stock Color OS recovery, but when booting into it I still get the teamwin recovery
I am unsure how to proceed.
Is there a way to fix my phone?
I have my CM11 working version and gapps ready - just need to place it in the phone somehow.
Any help?
Outblaze713 said:
Hey guys.
I'm new to this forum... and am posting this as I no longer know what to do, and need some guidance.
First I'll say that I've looked ALL OVER this forum and others, but couldn't solve my problem.
...So I subscribed in the hopes that someone will be able to more properly guide me.
------------------------------------------
So, first thing's fisrt - the story from the beginning:::
My device is an OPPO Find7 (QHD Version)
I've been using Cyanogenmod 11 for many months and without any problems.
Few days ago I installed the first nightly update of CM12 - and phone went into boot loop.
I had to restore to the ColorOS backup that was saved on my phone... Reinstalled CM11 and all is good.
Later I again updated to CM12 - and again was forced to revert back to Backup and then to CM11 due to bugs (phone wouldn't wake up after being locked, etc)
Anyway, There were three nightly build of CM12 to that point,and the last one was working in a relatively stable manner,
exept two bugs.
1. Contact names didn't appear when mamkiing to receiving a call - even though they were saved on the phone.
But this bug can be overlooked.
2. This one was more cirtical - - For some reason the phone said that I have no more free
space (even though I had 20+GB), thus preventing me from installing or updating
anything.
I figured that, perhaps, becuase of all the re-installs that I've done - my system memory got clogged.
So I decided, with more haste than thought, to perform a full wipe...SDcard and all, which consequently also removed
my ColorOS backup and everything, basically.
-----------------------------------------
The currrent outcome of what I did:::
Phone has no OS installed on it, and PC doesn't llow my to put files in there.
I can currently boot in three different states:
1. Normal boot with power button - - - OPPO logo appears - followed by a black
screen PC recognizes that I've connected a device, tries to install MTP Device and
evetually fails.
2. Power Button + Vol Up - - - Fastboot screen.
3. Power button+Vol-Down - - - Boots into the Gummified Team Win Recovery 2.7.1.0
In here, several things need to be mentioned.
- In the "Mount" section, I can choose which Partitions to mount to unmount, but
don't actually have the "Mount" button inside... So I can't mount.
- ADB Sideload doesn't work. When activating - it says "Starting ADB Sideload
Feature and just goes on forever, until I cancel it - and it says that it failed.
--------------------------------------------------
What I tried doing:::
Tried to use the Recovery Installer for OPPO, which is the exe that is available on the internet, that comes with drivers and all - and open command line with various options.
Tried installing the stock Color OS recovery, but when booting into it I still get the teamwin recovery
I am unsure how to proceed.
Is there a way to fix my phone?
I have my CM11 working version and gapps ready - just need to place it in the phone somehow.
Any help?
Click to expand...
Click to collapse
Do you have an OTG Usb drive. If so, you can use it with Nameless TWRP. Copy the Installation files into the USB drive and plug the usb drive into the phone. Now boot into Nameless recovery. It will show USBOTG. You can install the CM11 from USBOTG.
Flash Nameless recovery using Fastboot.
Download Nameless Recovery from HERE.
soft brick
This link explains how to restore our find 7 to factory settings:
oppoforums.com/threads/guida-riportare-il-find-7-7a-nello-stato-dacquisto-con-il-firmware-sahara.24561
if phone doesn't start try it i've use it several times and it works fine
I might just be reposting what dracula6mt was talking about, but there's an English post with full brick recovery here: http://www.oppoforums.com/threads/guide-how-to-recover-your-bricked-find-7-7a.23067/. I've used it before and it works perfectly. Just make sure you follow it exactly as written!
Bug
same bug report
for retrive your data just open the gummy twrp recovery, go on mount --> sd card and internal memory... in this way when you connect the phone to pc you will be able to see what's inside and try to rescue your data. in the same way you can send files to it.
I suggest you to get back your files, reboot the phone in fastboot mode (hold power and volume +) and just flash a recovery, it depends about what you want to install:
twrp for custom roms https://dl.twrp.me/find7/
colorOS stock recovery http://community.oppo.com/en/forum.php?mod=viewthread&tid=17397&extra=
you have to install fastboot on your pc and do from a command prompt:
fastboot devices
this will check if your phone is connected
fastboot flash recovery nameoftherecoveryfile.img
that will flash the recovery, only check the name of the .img file you want to install
be carreful, twrp has only a version for both find7s (QHD) and find7a while colorOS recovery 1.0 is different, unified for both models in 1.2 if i remember right...
after that you just have to put on your external storage the rom you want to use, wipe all except the external sd card, and flash...
Outblaze713 said:
Hey guys.
I'm new to this forum... and am posting this as I no longer know what to do, and need some guidance.
First I'll say that I've looked ALL OVER this forum and others, but couldn't solve my problem.
...So I subscribed in the hopes that someone will be able to more properly guide me.
------------------------------------------
So, first thing's fisrt - the story from the beginning:::
My device is an OPPO Find7 (QHD Version)
I've been using Cyanogenmod 11 for many months and without any problems.
Few days ago I installed the first nightly update of CM12 - and phone went into boot loop.
I had to restore to the ColorOS backup that was saved on my phone... Reinstalled CM11 and all is good.
Later I again updated to CM12 - and again was forced to revert back to Backup and then to CM11 due to bugs (phone wouldn't wake up after being locked, etc)
Anyway, There were three nightly build of CM12 to that point,and the last one was working in a relatively stable manner,
exept two bugs.
1. Contact names didn't appear when mamkiing to receiving a call - even though they were saved on the phone.
But this bug can be overlooked.
2. This one was more cirtical - - For some reason the phone said that I have no more free
space (even though I had 20+GB), thus preventing me from installing or updating
anything.
I figured that, perhaps, becuase of all the re-installs that I've done - my system memory got clogged.
So I decided, with more haste than thought, to perform a full wipe...SDcard and all, which consequently also removed
my ColorOS backup and everything, basically.
-----------------------------------------
The currrent outcome of what I did:::
Phone has no OS installed on it, and PC doesn't llow my to put files in there.
I can currently boot in three different states:
1. Normal boot with power button - - - OPPO logo appears - followed by a black
screen PC recognizes that I've connected a device, tries to install MTP Device and
evetually fails.
2. Power Button + Vol Up - - - Fastboot screen.
3. Power button+Vol-Down - - - Boots into the Gummified Team Win Recovery 2.7.1.0
In here, several things need to be mentioned.
- In the "Mount" section, I can choose which Partitions to mount to unmount, but
don't actually have the "Mount" button inside... So I can't mount.
- ADB Sideload doesn't work. When activating - it says "Starting ADB Sideload
Feature and just goes on forever, until I cancel it - and it says that it failed.
--------------------------------------------------
What I tried doing:::
Tried to use the Recovery Installer for OPPO, which is the exe that is available on the internet, that comes with drivers and all - and open command line with various options.
Tried installing the stock Color OS recovery, but when booting into it I still get the teamwin recovery
I am unsure how to proceed.
Is there a way to fix my phone?
I have my CM11 working version and gapps ready - just need to place it in the phone somehow.
Any help?
Click to expand...
Click to collapse
There is a much easier way :
http://www.androidbrick.com/ultimat...ide-snapdragons-are-unbrickable-qhsusb_dload/
mail me to : [email protected], greetings.
os_man said:
There is a much easier way :
http://www.androidbrick.com/ultimat...ide-snapdragons-are-unbrickable-qhsusb_dload/
mail me to : [email protected], greetings.
Click to expand...
Click to collapse
I know you, you are every where in all sites when searching for brick solutions...and are just thinking of earring money....fuuuii you rotten bastard,I want you too get your greedy as out of here, right now
And reporting this too forum admin right away, so they lock your ip right away
Greedy bastard, seen hundreds of posts, where people begged for the password you locked the rar file with, and only giving it when they pay you....gonna say it again.....
**** OFF
spoonymoon said:
I know you, you are every where in all sites when searching for brick solutions...and are just thinking of earring money....fuuuii you rotten bastard,I want you too get your greedy as out of here, right now
And reporting this too forum admin right away, so they lock your ip right away
Greedy bastard, seen hundreds of posts, where people begged for the password you locked the rar file with, and only giving it when they pay you....gonna say it again.....
**** OFF
Click to expand...
Click to collapse
Every human beeing who can communicate gets the password for free, especialy OPPO and OPO owners, every e-mail i get starting with "Pasword pleaseee pleaseee pleaseee" gets different behaviour of course. OH, and every CLEVER people already knows the tool in my article, i mentioned it a couple of times, for stupids like you its impossible to see of course. I helped hundreds of people for free and sometimes i request for donation, ITS MY VERY COMMON RIGHT + to help those i want and not to help to those that i dont want.
Greetings from TURKEY you silly Viking.
spoonymoon said:
I know you, you are every where in all sites when searching for brick solutions...and are just thinking of earring money....fuuuii you rotten bastard,I want you too get your greedy as out of here, right now
And reporting this too forum admin right away, so they lock your ip right away
Greedy bastard, seen hundreds of posts, where people begged for the password you locked the rar file with, and only giving it when they pay you....gonna say it again.....
**** OFF
Click to expand...
Click to collapse
Taken from my article ( for those who can read ) :
Please Stop asking for password without reading the article completely till the end, THIS TOOL WONT WORK UNLESS YOU HAVE THE NECESSARY SERVICE ROM ! Try sharing your phone model first and also try to share the service ( QPST ) Rom if you have it so more people can use it, THANK YOU.
os_man said:
Every human beeing who can communicate gets the password for free, especialy OPPO and OPO owners, every e-mail i get starting with "Pasword pleaseee pleaseee pleaseee" gets different behaviour of course. OH, and every CLEVER people already knows the tool in my article, i mentioned it a couple of times, for stupids like you its impossible to see of course. I helped hundreds of people for free and sometimes i request for donation, ITS MY VERY COMMON RIGHT + to help those i want and not to help to those that i dont want.
Greetings from TURKEY you silly Viking.
Click to expand...
Click to collapse
Hahaha,if so why, don't you post a link here, on mega or something, instead of all this " mail me" crap??? That would be a honest thing too do, instead....
And no, it's not common too sort in who and which, you want to help out, at least not here on XDA, we help every body, with no exceptions.
I say again, give us this file freely or I report you too forum admins.
My x9076 is bricked because of me making a lvm error, but I'd rather have it semi Working, with messed up partitions, like now, than pay our beg some guy like you for something that not working any way.
Last chance give this freely or get locked out from xda
EDIT: believe me, this turk psyko, has NOTHING not known already, regarding unbricking devices, there´s hundreds of posts here and on oppo forum about people having storage issues etc, not one ever mentioned anything about any other tools than those oppo them selves gave us, there is NO other working ways not known as this cracy dude claims, he´s just running a scam and wants 20$ for nothing - OS_MAN is a fraud dude all over.
EDIT 2: Silence from sir os_man tells the truth....
spoonymoon said:
Hahaha,if so why, don't you post a link here, on mega or something, instead of all this " mail me" crap??? That would be a honest thing too do, instead....
And no, it's not common too sort in who and which, you want to help out, at least not here on XDA, we help every body, with no exceptions.
I say again, give us this file freely or I report you too forum admins.
My x9076 is bricked because of me making a lvm error, but I'd rather have it semi Working, with messed up partitions, like now, than pay our beg some guy like you for something that not working any way.
Last chance give this freely or get locked out from xda
Click to expand...
Click to collapse
Never threaten a Turk Do whatever you can !
If XDA will lock me becouse of you, let it be
And i dont think that you can help anybody with that brain of yours, you even cant rescue your unbrickable Oppo..
spoonymoon said:
I say again, give us this file freely or I report you too forum admins.
Click to expand...
Click to collapse
When asking for help in a free space and for free, sometimes some manners can really make a huge difference. I think you fail to understand that even though you have a problem and someone might have a solution, that someone has no obligation whatsoever to share their time and the fruit of their research with you, especially so when threatened.
Hmm, considering the files and how-to's for unbricking a Find7 are freely available from Oppo forums (and here, I believe), I'm pretty suspicious of anyone doing ANYTHING other than giving them away freely. The files I downloaded and have used, a few times now, were free and had no passwords on zip/rar archives.
As for 'fruits of research', this guy wasn't the guy who put up the how-to's or did the initial research on it so, in my books, he doesn't get the credit, be it kudos OR cash money.
Some folks seem to literally want something for nothing. No harm in asking for donations, sure, but don't be at all surprised if I tell you to go f*** yourself. That's not how this game works, we all stand on each other's shoulders.
hope someone can help me. have unlocked my bootloader and did an update kdz i did a hardreset and now when i boot up my phone it says
THIS DEVICE WAS RESET. TO CONTYNUE SIGN IN WITH A GOOGLE ACCOUNT THAT WAS PREVIOUSLY SYNCED ON THIS DEVICE.
i put my email address in and password and it just take me back to the wifi screen it just keeps looping back like this, ive read this in a new thing with android 5.1 and after 72 hours i can login but its been like 4 days now and still cant use my g4 is there anything i can do to get my phone working again.
any help would be great
Try to connect to different wifi if then your phone will sync with google account.
its been almost aweek now with out my g4 still cant get past this tried kdz updates 10b 10c and still no joy can anyone help sort this
gavo84 said:
its been almost aweek now with out my g4 still cant get past this tried kdz updates 10b 10c and still no joy can anyone help sort this
Click to expand...
Click to collapse
Call in for a replacement.
BAD ASS NOTE 4 & LG G4
ive gone and unlocked the bootloader
gavo84 said:
ive gone and unlocked the bootloader
Click to expand...
Click to collapse
...?
gavo84 said:
ive gone and unlocked the bootloader
Click to expand...
Click to collapse
So you probably unlocked it to be used on other carriers as only the H815 can have an unlocked bootloader.
Just a small sugestion. Have you tried to create a new google account and sync with it to see what happens?
tried that and just tried it again with new account still in a loop. i unlocked the bootloader for root now when u unlock the boot loader lg remove warranty
anyone out there that can help.
https://youtu.be/ukE0mA7yFIM
Did you try clearing cache all google related apps like google service framework ?
what i have done is hardreset not sure how i can clean cache all google related apps like google service framework, as thats the only screen i can see i posted a video of whats happening, i have been on the pgone to google then its not them ring lg, i spoke to lg and emailed them a video waiting for a call back off them.
Maybe try booting into recovery in order to wipe EVERYTHING (and I mean everything possible).
Then boot back into download mode and flash the STOCK .kdz file (the one that your phone came from your carrier with, 10a/b which it was depending on how long you have had your phone).
If that does not work maybe try to build or get a custom AOSP Rom that does not have the GAPPS and see if you can just by-pass the issue all together by booting with having to deal with google apps (you would still need a work around for getting Gapps to work, but at least you would know exactly what the problem is and could boot into a working phone in the mean time).
Weird. Might be that 72 hour sign in feature (cough* bug *cough) thing because it looks like it might be kicking it back on the server side.
1) Did you try signing in on mobile data?
2) Do you have a nandroid, TB, or LG backup that you can restore?
2) Try bypassing the setup screen (keep tapping Next or Skip) and just get to the home screen. Then goto Settings ---> Accounts and add your account. This way you can get a usable device.
ive tried STOCK .kdz 10a/10b/10c
i dont have a nand backup
ive tryed using other wifi and my mobile internet.
google say its not them and im still waiting for lg to even look at the video they asked for..
is there any roms even out there for the g4 i cant find any. over a week now with out my g4.
AOSP Rom i wouldnt know where to start on building one i no longer have root or TWRP after flashing kdz
cant get the phone in adb mode developer as i cant get past the wifi screen as seen in video and cant get USB debugging.
gavo84 said:
hope someone can help me. have unlocked my bootloader and did an update kdz i did a hardreset and now when i boot up my phone it says
THIS DEVICE WAS RESET. TO CONTYNUE SIGN IN WITH A GOOGLE ACCOUNT THAT WAS PREVIOUSLY SYNCED ON THIS DEVICE.
i put my email address in and password and it just take me back to the wifi screen it just keeps looping back like this, ive read this in a new thing with android 5.1 and after 72 hours i can login but its been like 4 days now and still cant use my g4 is there anything i can do to get my phone working again.
any help would be great
Click to expand...
Click to collapse
Did you buy phone new, from where?
the phone is on a 24 month contract from o2 i got the phone from the carphone warehouse
ive just got off the phone to LG still not looked at the video they asked for i have been told to wait 7 working days WHAT thats gonna be like two weeks with a none working phone.
Weird, it's like you got a refurbished phone, and the old google account was not removed the correct way (remove google account before the phone is reset). If you reset phone without removing your account you get exactly what has happened to your phone. I see it all the time on the Nexus 6 forum.
Hi all
I have had this ZUK2 phone around 8 months, and really to be honest i don't like it, and regret my purchase, i purchased it from Gearbest in China and since day one never gelled with it.
It is bog stock except what G/B loaded on it, issues... has pop ups/spam, some of the text is still in Chinese etc, some of the apps don't work, i cannot delete them
Anyway, as a phone works great, so i lived with it, but now i have kinda "bricked" it [blue screen with logo]. The phone had a ZUK official update app on it but it never worked in AUS as needs to be in China to work..... so fast forward
While @ Shanghai airport wifi internet the update did load and that is where and when it "bricked" [blue screen/logo] happened, it never opened after the download, in-fact i could not even turn the phone off to get on the plane, and it was getting mighty hot [shades of Galaxy Note 7 ] who's idea of non remove battery?
So now i do not understand anything about Twerp?/India Rom, USB blahhblahhblah, i took it to the local guy, he only does Iphones and Samsung, dead end
What i want to do, is ask nicely if anybody here is AUS has the knowledge to reload all the software back onto the phone, latest ZUK update and latest android version and make it work... Even pay a fair and reasonable fee [plus return post] to fix my sick phone and make it work, would be kool!!
I know i have lost all my photos, contacts, apps etc, does not matter, moving on, just want it to work
Thanks if anybody can reach out and help
With regards :good:
Lot6
LOT6 said:
Hi all
I have had this ZUK2 phone around 8 months, and really to be honest i don't like it, and regret my purchase, i purchased it from Gearbest in China and since day one never gelled with it.
It is bog stock except what G/B loaded on it, issues... has pop ups/spam, some of the text is still in Chinese etc, some of the apps don't work, i cannot delete them
Anyway, as a phone works great, so i lived with it, but now i have kinda "bricked" it [blue screen with logo]. The phone had a ZUK official update app on it but it never worked in AUS as needs to be in China to work..... so fast forward
While @ Shanghai airport wifi internet the update did load and that is where and when it "bricked" [blue screen/logo] happened, it never opened after the download, in-fact i could not even turn the phone off to get on the plane, and it was getting mighty hot [shades of Galaxy Note 7 ] who's idea of non remove battery?
So now i do not understand anything about Twerp?/India Rom, USB blahhblahhblah, i took it to the local guy, he only does Iphones and Samsung, dead end
What i want to do, is ask nicely if anybody here is AUS has the knowledge to reload all the software back onto the phone, latest ZUK update and latest android version and make it work... Even pay a fair and reasonable fee [plus return post] to fix my sick phone and make it work, would be kool!!
I know i have lost all my photos, contacts, apps etc, does not matter, moving on, just want it to work
Thanks if anybody can reach out and help
With regards :good:
Lot6
Click to expand...
Click to collapse
In all-in-all honesty I can do it remotely for you on a live-call and remotely doing everything on your PC with your phone connected via USB cable. No need. Zuk Z2 has really friendly procedure to do it all, return to stock or the stock-android experience.
In-Technical Terms:
I have to unbrick your phone by restoring it to stock firmware, then unlocking its bootloader, downloading nad running TWRP recovery on it and then to a tailored firmware of your needs without any Chinese bloatware/adware.
Free of cost ofcourse.
I understand all the issues related to privacy etc but I assure you everything I'd do remotely, you'll be able to do it yourself once you see how its done. No gimmicks involved.
I have my brother who lives near NSW but he works double shifts and hardly has any time to fiddle around with stuff other than his work, eating and sleeping. I'm from Pakistan btw.
PM me and I'll get your phone fixed without charging you a single penny, using your own PC remotely and your very own hardware. With every instruction to fix it by yourself if in-case a problem arises in future.
dark_prince said:
In all-in-all honesty I can do it remotely for you on a live-call and remotely doing everything on your PC with your phone connected via USB cable. No need. Zuk Z2 has really friendly procedure to do it all, return to stock or the stock-android experience.
In-Technical Terms:
I have to unbrick your phone by restoring it to stock firmware, then unlocking its bootloader, downloading nad running TWRP recovery on it and then to a tailored firmware of your needs without any Chinese bloatware/adware.
Free of cost ofcourse.
I understand all the issues related to privacy etc but I assure you everything I'd do remotely, you'll be able to do it yourself once you see how its done. No gimmicks involved.
I have my brother who lives near NSW but he works double shifts and hardly has any time to fiddle around with stuff other than his work, eating and sleeping. I'm from Pakistan btw.
PM me and I'll get your phone fixed without charging you a single penny, using your own PC remotely and your very own hardware. With every instruction to fix it by yourself if in-case a problem arises in future.
Click to expand...
Click to collapse
Hello D/P. :good:
That is very very nice offer from you, i am touched by your kind assistance
I will see if any local folk come back to me, also i emailed G/B in China but due to Chinese New Year have not had a reply back as yet, they may well have a contact/agent in AUS to sort this out.
Once again many many thanks
L
LOT6 said:
Hello D/P. :good:
That is very very nice offer from you, i am touched by your kind assistance
I will see if any local folk come back to me, also i emailed G/B in China but due to Chinese New Year have not had a reply back as yet, they may well have a contact/agent in AUS to sort this out.
Once again many many thanks
L
Click to expand...
Click to collapse
Hello man, your problem is that you installed official update on custom ****ty Chinese rom.
Probably you had MM ROM, with a lot of bloatware
It doesn't surprise me you don't like the phone, which is BTW great
I can send you my instructions, you need 1h time, patience, and some computer knowledge. Windows 10 would be nice.
If you don't have these requirements than try with those local gys but probably all of them will tell you, how's your phone name, ZuuuK, what?
And I also recommend custom rom. You would like this phone much more than you like it now. I had same opinion like you when I got it. Was so bored with stupid ZUI system. Than I realized how strong support this phone has and started flashing custom roms, which literally made me love this phone
C'ont
vuckovic_stefan said:
Hello man, your problem is that you installed official update on custom ****ty Chinese rom.
Probably you had MM ROM, with a lot of bloatware
It doesn't surprise me you don't like the phone, which is BTW great
I can send you my instructions, you need 1h time, patience, and some computer knowledge. Windows 10 would be nice.
If you don't have these requirements than try with those local gys but probably all of them will tell you, how's your phone name, ZuuuK, what?
And I also recommend custom rom. You would like this phone much more than you like it now. I had same opinion like you when I got it. Was so bored with stupid ZUI system. Than I realized how strong support this phone has and started flashing custom roms, which literally made me love this phone
Click to expand...
Click to collapse
Hello. many thanks for the reply
Yes, i agree, i updated in China on a international/export tweaked phone
Anyway been phone-less for near a month, interesting
On the 23rd Chinese New Year is over, i will see what G/B come back with.
And yes, if not too much trouble please post here or email me the step by step instructions, cannot hurt to at least have a look and see, many thanks for this.
PS/ Looks i am one of very few who purchased a ZUK2 in AUS
Thanks again champ
To be honest the experience of Zuk Z2 Plus with ZUI ROM ( STOCK ROM ) is worst, it's worst that i ended up unlocking bootloader, installing TWRP and flashing a Custom RoM on Day 1 itself
This phone is a beast, it's like this phone was made to run on Custom Roms.
I'd say you should once you'll be able to bring the phone back to life, unlock the bootloader and flash a TWRP and install some nice OREO ROM for example AEX 5.2 by Davidevinavil.
Also, Can you try this:
*Phone must be switched Off*
Press and Hold Volume Up and Down button
And at the same time plug in the Charger USB cable in your phone.
Tel me what it shows
kubersharma said:
To be honest the experience of Zuk Z2 Plus with ZUI ROM ( STOCK ROM ) is worst, it's worst that i ended up unlocking bootloader, installing TWRP and flashing a Custom RoM on Day 1 itself
This phone is a beast, it's like this phone was made to run on Custom Roms.
I'd say you should once you'll be able to bring the phone back to life, unlock the bootloader and flash a TWRP and install some nice OREO ROM for example AEX 5.2 by Davidevinavil.
Also, Can you try this:
*Phone must be switched Off*
Press and Hold Volume Up and Down button
And at the same time plug in the Charger USB cable in your phone.
Tel me what it shows
Click to expand...
Click to collapse
Hi
Not sure that can be done as when i turn on the phone, as its flat, but when charged it starts ok, goes on blue/screen logo, and that's all
But THEN it wont switch off, i have to wait till it flattens the battery [it gets very hot BTW] and then back to square one
The only way i could turn it on is charge it first, i swear this phone has a devil inside it
Any of your Indian brothers here in AUS have this phone?
Many thanks for your support!
Regards
Charge it a bit, like 30 mins
Unplug and try to press all Power, Volume (up & down) together for like 5-10 seconds
It should switch off, but don't press anything after that it'll wake up again if you do.
If you are successful to switch it off , you can try the above method i mentioned in my previous post to bring it to Fastboot/bootloader mode.
After that it's all easy to get started
Detailed post to go back to stock (before bootloader unlock -> TWRP Recovery -> Custom ROM):
https://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-z2131-only.104/
To Summarize:
1. Preparing
- Have pre-requisite software (QPST flashing software)
- Have all the drivers installed (ZUK Usb drivers, as well as Qualcomm QHUSB Drivers, detailed instructions are within the post)
- Have the Firmware file downloaded which u will install on your phone via QPST Flashing software: In your case, it's indian QPST flash-able firmware: https://mega.nz/#!4xIGVSJQ!iN2JUA_eyYX9m35Pt3ife9iIBcGi_9CNPWUUqxpkFiY which is marshmallow
- Extract the above firmware into some place safe where you will navigate later when giving the software instructions to make your phone reborn.
2. Making phone ready
- Make sure your phone was put to charging for atleast an hour before carrying out the next steps
- While your phone is turned off, Press and hold Vol - and Power button together and quickly insert the USB cable (which is already connected to your PC). If that's successful you can check the connection by going to Device Manager or simply checking status of QPST software
Rest of the instructions are on the main post which i linked earlier. It's really easy to do if you know your ways around using windows
In-case something is ambiguous to you, you can ask me directly. I've sent you my skype id on PM
LOT6 said:
Hello. many thanks for the reply
Yes, i agree, i updated in China on a international/export tweaked phone
Anyway been phone-less for near a month, interesting
On the 23rd Chinese New Year is over, i will see what G/B come back with.
And yes, if not too much trouble please post here or email me the step by step instructions, cannot hurt to at least have a look and see, many thanks for this.
PS/ Looks i am one of very few who purchased a ZUK2 in AUS
Thanks again champ
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=74992814&postcount=5659
Here Is my instructions
Other members told you how to get in fastboot
There reboot into edl mode (mode for qfil, to flash stock ZUI rom)
Everything you have in those instructions mate
Use Google translate, read slow, I believe in you
Its not hard, just do it slowly, don't jump over some step cuz you will have bricked phone
Wish you luck Aussie
And I believe you are maybe 0.01 % of people having ZUI phone done there ))
Download QPST once ,install it and open "QFIL.exe" , connect your Phone to PC via USB, if the QFIL app shows that a port has been connected , then this is same case as mine and you can easily make the phone work like a beast again in one hour!
Side note - Also download and install ADB , Qualcomm USB and Zuk USB drivers and then check again! You will need these all eventually!
Which city in AUSTRALIA???
gargdada said:
Which city in AUSTRALIA???
Click to expand...
Click to collapse
In Melbourne, but i will post it [pay both ways] to any city in AUS.
Thanks
PS. Still no contact from seller
ok try this
Download Tool All in one:
https://www.androidfilehost.com/?a=show&w=files&flid=38683http://
OR
https://forum.xda-developers.com/on...ol-tool-one-driversunlocktwrpfactory-t3398993
Download Mi flash tool:
https://androidmtk.com/download-xiaomi-mi-flash-tool
Stock firmware:
http://www.mediafire.com/file/f86cs94nt19762z/Lenovo_Zuk_Z2_Z2132_EN_OPEN_USER_Q01080.2_N_ZUI_2.5.104_ST_170418_QPST.zip
7zip:http://7-zip.org/a/7z1801-x64.exe
Download Unlock_Bootloader Image: https://forum.xda-developers.com/lenovo-zuk-z2/how-to/how-bootloader-zuk-z2-pro-t3415392
Download TWRP:https://dl.twrp.me/z2_plus/twrp-3.2.1-0-z2_plus.img.html
Download ADB Drivers:https://www.dropbox.com/s/mcxw0yy3jvydupd/adb-setup-1.4.3.exe?dl=0
Install 7 zip Then mi flash tool then Tool All in one Extract stock Also install ADB drivers firmware with 7 zip.
you can send me a message in WhatsApp(+917077307772)Also I can help you with remotely.
Hey Yo!
were u able to fix your phone.. i rooted mine and installed custom rom in less than half an hour.. super awesome phone now.. BTW people who are abusing zui so much i didn't find it that bad... although the notification bar sucked big time with double notification and no reply .. rest all was ok .. like you could work your way around.. i use nova launcher may be thats why.:silly:
sanjay.2704 said:
Hey Yo!
were u able to fix your phone.. i rooted mine and installed custom rom in less than half an hour.. super awesome phone now.. BTW people who are abusing zui so much i didn't find it that bad... although the notification bar sucked big time with double notification and no reply .. rest all was ok .. like you could work your way around.. i use nova launcher may be thats why.:silly:
Click to expand...
Click to collapse
No, still done nothing, really want somebody in AUS to do it for me, will reward them
Thanks
LOT6 said:
No, still done nothing, really want somebody in AUS to do it for me, will reward them
Thanks
Click to expand...
Click to collapse
sorry bro.. As one prev post mentioned 0.01% may be using zuk them too not many would have rooted.. It is really simple to do.. Remote access or do it on your own is the only way ahead or get new phone.. But why u would get a new phone when u have such awesome device?? Lemme know if I can be of any help..
Check out my battery usage. Phone on for 36 hours and counting..used 2030 mah out of 3500 mah..
Stand by for 20 hours out of those 36 ..ie no touching at all
Hey mate, Z2 user in Australia here. It's probably just the two of us.
Custom ROMs are messy and prone to unexpected issues. At some point you're going to have to fiddle with it when it spontaneously bricks. If you weren't the one to set it up, you'll find it tricky or impossible to do maintenance/fixes yourself.
My advice is (especially for a phone worth as little as this one is) - follow the relatively straightforward guides on flashing stock, unlocking the bootloader, and loading on a new ROM. It shouldn't take more than an hour. I don't recommend sticking with the stock China ROM.
If you really **** it up and have no idea what you've done wrong, I'd be happy to take a look at the phone (for free). Though I'm in Sydney, not Melbs.
Passa91 said:
Hey mate, Z2 user in Australia here. It's probably just the two of us.
Custom ROMs are messy and prone to unexpected issues. At some point you're going to have to fiddle with it when it spontaneously bricks. If you weren't the one to set it up, you'll find it tricky or impossible to do maintenance/fixes yourself.
My advice is (especially for a phone worth as little as this one is) - follow the relatively straightforward guides on flashing stock, unlocking the bootloader, and loading on a new ROM. It shouldn't take more than an hour. I don't recommend sticking with the stock China ROM.
If you really **** it up and have no idea what you've done wrong, I'd be happy to take a look at the phone (for free). Though I'm in Sydney, not Melbs.
Click to expand...
Click to collapse
Lol, about what custom rom are you talking about ?
Final nougat releases are great, especially AEX, Viper etc
This phone with Zui is catastrophic, no wonder for such bad comment's
Couldn't believe how good it is with custom roms, using it for months now like that, nothing messy here, Don't spread desinformations please
If he sends you phone, put him latest AEX OREO with GZR Gapps
Also Google camera, BSG versions from 4pda , I'm using v1a and it's great
vuckovic_stefan said:
Couldn't believe how good it is with custom roms, using it for months now like that, nothing messy here, Don't spread desinformations please
Click to expand...
Click to collapse
Lmao, the only thing missing from this comment is an Androidify profile pic.
OP, you're gonna wanna be confident enough to flash your own custom ROM updates and suss out any issues that crop up. Chinaphones, even higher tier ones like the Z2, are not set-and-forget devices.
I started updating the phone to the Jan 2019 update from the Dec 2018 update (I just like having the latest updates) It rebooted into bootloader via ADB just fine. I then ran the flash all.bat without the -w so it wouldnt wipe the phone out completely. It started updating and rebooting just like normal after the bootloader and radio parts. It made it close to the end of the system update and did not reboot the phone. It went back to the bootloader which I thought was odd. Fastboot can no longer see the phone in Fastboot devices. When starting the phone it reboots back into bootloader saying load failed. It also will not boot into recovery (which I expected from the update and not getting to flash twrp back in yet) I have rebooted the phone and my computer as well. I tried my other phone to check the cable and it found it in ADB and Fastboot just fine. I do have the latest SDK installed. Any help would be greatly appreciated.
---Solution---
Chilipepprflea said:
I know this is probably too late for you guys, but maybe it will help someone else. Fastboot commands would result in "waiting on any device" and my Pixel 2 wouldn't boot out of the bootloader. I thought it was done for good based on this thread and others I've read...until I came across this Reddit https://www.reddit.com/r/GooglePixel/comments/b25nso/error_slot_unbootable_load_error/
I did what this guy did and held the power button (ended up being for a couple minutes in my case) and it vibrated and all is good again! adb recognized my phone and I was able to flash again.
Click to expand...
Click to collapse
You'll have to go back into bootloader and do a stock flash follow the steps on googles site. go back to 8.0 or whatever you were on before, make sure that boots up fine. You must not have had updated your sdk before trying to update to 9.0
I was going to just reflash everything but when I do fastboot devices its just blank as if the phone does not exist. Also the computer doesnt do its chime when I plug the USB in while its in bootloader. When the phone is off and I plug it in it shows the charging icon for a split second then boots into bootloader saying ERROR: Slot Unbootable: Load Error. If I try to do any commands in fastboot it just says "waiting for any device"
I was already on 9.0 and was just pushing the January security patch when it stopped near the end of the update. Now I can not get fastboot to even see the device.
Try removing all drivers and fastboot files on your pc. Sounds like you just flashed the wrong file. Were you rooted with magisk? or just on a stock rom. re download the full image and try and re flash. https://developers.google.com/android/images
Because of the slots (a and b) alot of people seem to have trouble flashing things. I have even messed things up as well. On the Pixel devices I havent been able to not go back into stock setups. Even if it took removing all files and starting over.
---------- Post added at 04:19 AM ---------- Previous post was at 04:18 AM ----------
I will keep checking back over here to see if you have any issues.
So I just tried what you had said. Deleted all the SDK files and uninstalled the drivers, rebooted computer and phone redownloaded everything and still can not find the phone via fastboot... magisk was installed but I was doing the full image install without the -w so it would not wipe. it was almost done with it and never actually booted into android it just stayed on the bootloader which I found strange. That is when I noticed that the phone could no longer be found via fastboot devices. I have tried different cords different ports and even a different computer and still have the same result. It did update the bootloader and radio portions of the update. I feel like if I can get fastboot to start working I can save this thing.
I got caught up with friends that came over. You have tried everything I would have tried. Which is good cause you seem to know what you are doing, but not good that it hasnt been resolved. Have you looked at this guide? https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Coolpente said:
I started updating the phone to the Jan 2019 update from the Dec 2018 update (I just like having the latest updates) It rebooted into bootloader via ADB just fine. I then ran the flash all.bat without the -w so it wouldnt wipe the phone out completely. It started updating and rebooting just like normal after the bootloader and radio parts. It made it close to the end of the system update and did not reboot the phone. It went back to the bootloader which I thought was odd. Fastboot can no longer see the phone in Fastboot devices. When starting the phone it reboots back into bootloader saying load failed. It also will not boot into recovery (which I expected from the update and not getting to flash twrp back in yet) I have rebooted the phone and my computer as well. I tried my other phone to check the cable and it found it in ADB and Fastboot just fine. I do have the latest SDK installed. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Are you *sure* it will not boot to recovery? If you're not used to the stock recovery it can fool you. Many ppl see the dead android and stop there. If you can get into the stock recovery you can try sideloading an OTA via adb (which only works in recovery). I would also be trying different computers and cables. If you cannot use fastboot -and- you have no working recovery you might be dead in the water.
OMG @Coolpente!!!! THIS....HAPPENED...TO....ME!!!!
Holy crap! I can't believe this happened to someone else! I thought it was just me and my bad luck!
I literally was doing the same thing (only difference was on my gf's pixel 2 [walleye])! And those who have seen me around this forum the last year know that I am very knowledgeable and don't make the simple and "noob" mistakes! I've literally have helped and recovered people in this/our position -- so it is doubtful there was a amateur or novice mistake made in the updating process or "stone un-turned" in the recovery process!
So here is what happened to me, particularly, and my observations on it...
- When "crap hit the fan", it was very peculiar that fastboot would identify the phone's serial number as "??????????" (when running the command "fastboot devices"). Only after rebooting and disconnecting/reconnecting the usb cable did it (fastboot) simply just stop detecting. To make sure that my computer, usb port, cable, and fastboot is working correctly and able to process properly, I would make sure the fastboot process/server was not running, then I would actually run the command "fastboot getvar all", and as it would "would for device", I would plug in the phone, nothing would happen, then plug in my phone [taimen] (not my gf's walleye), and it would detect it and display all the pertinent information and device details, I would then unplug it from my phone, run the same getvar command, and lastly replug it into the phone (broken gf's walleye) with no detection or success.
- What's also interesting and of note is that when loading straight into the bootloader (via button combination), it displays no error in the list of device details. But when booting into the recovery (note: I, like the OP, had the TWRP custom recovery already flashed and installed) and also the system and/or from a power-off state, it states in red colored font and yellow background, "ERROR: Slot Unbootable: Load Error". Even more than that is when attempting to boot into Download mode, it states a different error (but in the same font style), "ERROR: Operation Denied"!
- I also attempted to manually change the slot in attempts to address the "slot unbootable..." "...load[ing] error", but -- due to either fastboot not detecting or the device not connecting properly I imagine -- without fastboot properly detecting, the commands wouldn't work and execute properly anyway. I've even taken steps further and attempted to format and custom "re-size" partitions. But, for the aforementioned reasons (presumably), it and attempts at commands like it wouldn't likely work and execute, again as previously reasoned. Also, in attempt to tackle the "slot" aspect of the issue, I tried Deuce's script; but as Deuce's script is, simply put, based off of the flash-all.bat that ends up being an advanced batch (pun intended) of commands that manually and individually flashes the stock images/partitions to the partitions of the device -- so, in essence, uses fastboot and since fastboot can't work.... I even found and attempted to use the (hardly heard of; at least to me) tool Skipsoft Android Toolkit (which looks genuinely super dooper awesome btw...)... all for naught :crying: ...
You know, after a year with the Pixel 2 (XL), and after coming back from messing my phone up (15+ times), and actually purely bricking it once (had to get it replaced), I always thought that, as long as one could access the device via the bootloader, one would always have hope (at least in the Pixel's case). So, it's curious but agonizingly ironic being able to access the bootloader (which was not the case in my one and only instance of bricking my device and having a completely "lost cause") just for me not to be able to do anything about it and/or fastboot to not be able to properly connect and send commands to it...
But to me and Coolpente (and anyone else who this may have happened to) I ultimately can't think of anything else that can be done at this point. To re-iterate, I/we had the most up-to-date platform-tools (r28.0.1), it has been proven that the usb cord, port, computer, and drivers are all working as I was able to get the "getvar all" command to work on another pixel mere seconds before attempting the same on this (broken) device, and even attempted all tools available...
Unfortunately, @Coolpente, it does look as if our phones are irrevocably "bricked" and it's all rather doomed and attempting to get it repaired/replaced by the manufacturer ("The Big G") is the only recourse we may have :crying::crying::crying:
I wrote this (very long) post in hopes of giving as much information and details as possible in the desperate hopes that any other solutions might be brought up...
simplepinoi177 said:
OMG @Coolpente!!!! THIS....HAPPENED...TO....ME!!!!
Holy crap! I can't believe this happened to someone else! I thought it was just me and my bad luck!
-- SNIP---
I wrote this (very long) post in hopes of giving as much information and details as possible in the desperate hopes that any other solutions might be brought up...
Click to expand...
Click to collapse
I am so glad I am not the only one that his has happened to! I have rooted several phones as well as almost bricking the one that ultimately bricked... (not up to date sdk tools) You have word for word the exact same thing that is happening to me. no recovery no booting and no download mode just the bootloader which is not found by fastboot. I thought at first it may have been the usb port in the phone disconnecting somehow but when plugging it in from a completely off state it does show the charging battery screen for a split second then boots into bootloader saying it can not load that slot. I am not very fluent in the disassembly of phones like this or I would check to see if the data parts of the USB port are not connected to the board.. It kills me that the phone is not even a year old and something like this would happen.. I have since gotten a replacement phone but I am very interested in seeing if there is a way to fix it in the near future outside of sending it in.
Coolpente said:
I am so glad I am not the only one that his has happened to! I have rooted several phones as well as almost bricking the one that ultimately bricked... (not up to date sdk tools) You have word for word the exact same thing that is happening to me. no recovery no booting and no download mode just the bootloader which is not found by fastboot. I thought at first it may have been the usb port in the phone disconnecting somehow but when plugging it in from a completely off state it does show the charging battery screen for a split second then boots into bootloader saying it can not load that slot. I am not very fluent in the disassembly of phones like this or I would check to see if the data parts of the USB port are not connected to the board.. It kills me that the phone is not even a year old and something like this would happen.. I have since gotten a replacement phone but I am very interested in seeing if there is a way to fix it in the near future outside of sending it in.
Click to expand...
Click to collapse
I know it is highly unlikely, but I'm hanging in there hoping for the same thing as well...
Yeah, it's troubling that this is can be happening coming from very "seasoned" users!
I was considering the same that it feels more like a hardware issue since everything seems to work on the computer end as well as everything working on another pixel device, BUT I can't see how a failed "fastboot" command and process can effect any kind of hardware or physical connections ("data parts")?!
If anything, I believe it has to do with the sequence of events of how things crapped out... I believe that, in some random manner, the bootloader -- which gets flashed and updated first; referencing the script in the flash-all.bat -- gets replaced, but isn't installed/initialized/"placed" properly -- but curiously enough, is installed "properly" enough that it can be re-entered after turning the device off -- that most everything works BUT the all important fastboot connection/interface/detection! That's why I attempted to manually flash the bootloader image ("fastboot flash bootloader bootloader.img"), but, "head-bangingly" poetic in its irony of course, fastboot is required to accomplish this ("this" being fixing freaking "fastboot"! :crying: )
I'm terrified to update my own Pixel at this point.
Unfortunately, this seems to have only been documented in our two cases (so far)...I wonder if it's even worth creating a Google support ticket in attempts to bring it up to them in hopes that they fix whatever might be causing this -- hopefully assisting and saving others from this disaster -- and/or even pull the update until it is stable (although, like I stated, it seems not a prevalent enough issue that many either have successfully updated via this image and process or most haven't brought it up anywhere) and/or keep it from happening in the next update.
In any case, here's hoping ("pray for the best, expect the worst" kind of scenario is most likely appropriate) any kind of solution materializes, or, at the very least, can be shown as a "word of warning" and caution about the (this, specifically) update....
simplepinoi177 said:
OMG @Coolpente!!!! THIS....HAPPENED...TO....ME!!!!
Holy crap! I can't believe this happened to someone else! I thought it was just me and my bad luck!
I literally was doing the same thing (only difference was on my gf's pixel 2 [walleye])!
Click to expand...
Click to collapse
Find a new girlfriend, your problem will be easily solved.
simplepinoi177 said:
I know it is highly unlikely, but I'm hanging in there hoping for the same thing as well...
Yeah, it's troubling that this is can be happening coming from very "seasoned" users!
I was considering the same that it feels more like a hardware issue since everything seems to work on the computer end as well as everything working on another pixel device, BUT I can't see how a failed "fastboot" command and process can effect any kind of hardware or physical connections ("data parts")?!
If anything, I believe it has to do with the sequence of events of how things crapped out... I believe that, in some random manner, the bootloader -- which gets flashed and updated first; referencing the script in the flash-all.bat -- gets replaced, but isn't installed/initialized/"placed" properly -- but curiously enough, is installed "properly" enough that it can be re-entered after turning the device off -- that most everything works BUT the all important fastboot connection/interface/detection! That's why I attempted to manually flash the bootloader image ("fastboot flash bootloader bootloader.img"), but, "head-bangingly" poetic in its irony of course, fastboot is required to accomplish this ("this" being fixing freaking "fastboot"! :crying: )
I'm terrified to update my own Pixel at this point.
Unfortunately, this seems to have only been documented in our two cases (so far)...I wonder if it's even worth creating a Google support ticket in attempts to bring it up to them in hopes that they fix whatever might be causing this -- hopefully assisting and saving others from this disaster -- and/or even pull the update until it is stable (although, like I stated, it seems not a prevalent enough issue that many either have successfully updated via this image and process or most haven't brought it up anywhere) and/or keep it from happening in the next update.
In any case, here's hoping ("pray for the best, expect the worst" kind of scenario is most likely appropriate) any kind of solution materializes, or, at the very least, can be shown as a "word of warning" and caution about the (this, specifically) update....
Click to expand...
Click to collapse
I have considered going to a custom rom and avoiding the stock rom completely... Which would avoid ever needing to use fastboot to update in the future.. but its to late for one phone but not to late for the other. I havent even looked into roms since CM broke down...
Coolpente said:
I have considered going to a custom rom and avoiding the stock rom completely... Which would avoid ever needing to use fastboot to update in the future.. but its to late for one phone but not to late for the other. I havent even looked into roms since CM broke down...
Click to expand...
Click to collapse
Yeah....but, if you think of it, I've been updating by way of Full Factory images via fastboot for over a year (14 months to be exact), so the last 13 times and 13 out of 14 times it worked perfectly....so, pure statistics, I wonder if swearing off fastboot forever is truly pertinent just yet...
Well, at least the pixel 2's been out for....14 months, apparently...so there seems to be a lot of good, stable custom ROMs that have been long in development to choose from, if anything... **~shrugs~**
simplepinoi177 said:
Yeah....but, if you think of it, I've been updating by way of Full Factory images via fastboot for over a year (14 months to be exact), so the last 13 times and 13 out of 14 times it worked perfectly....so, pure statistics, I wonder if swearing off fastboot forever is truly pertinent just yet...
Well, at least the pixel 2's been out for....14 months, apparently...so there seems to be a lot of good, stable custom ROMs that have been long in development to choose from, if anything... **~shrugs~**
Click to expand...
Click to collapse
As far as statistics are concerned yea I have been updating 2 pixels by full factory images for the last year and one has survived all 12 months while the other made it through 11 of 12. but in fear of bricking another pixel device knowing this could potentially happen again... it feels as if going to custom roms would for sure be the safest method and still keep root. Of course losing root and going pure stock would be 100% the best... I love having root and dont want to lose it.
Coolpente said:
As far as statistics are concerned yea I have been updating 2 pixels by full factory images for the last year and one has survived all 12 months while the other made it through 11 of 12. but in fear of bricking another pixel device knowing this could potentially happen again... it feels as if going to custom roms would for sure be the safest method and still keep root. Of course losing root and going pure stock would be 100% the best... I love having root and dont want to lose it.
Click to expand...
Click to collapse
Yeah, I see what you're saying and in the exact same boat (2 pixels, gf's is a walleye, mine's a taimen, both have been updated monthly with no issues or def bricking issues, so 14 of 14 and 13 of 14...)...
But I guess that's definitely one of the "safest" methods, just that support for ROMs come and go (hell, even one of the original custom kernels [Flash] is EOL)...but Pixel 2 is only a year "in" and Google will continue to support it for the foreseeable future so it may look like regular support for walleye/taimen-related mods will continue to get regular updates and support as well...
But still, as I enjoy our conversations, it also serves to "bump" this thread as well...
Anyone have any idea on how to reinstall bootloaders, switch slots, enter custom recovery, flash anything all without -- and this is key -- fastboot (because fastboot will not detect and connect with the device)?!?!
I just tried to update to Feb from Jan and this happened to me....
Anything I can do about it?
James1258 said:
I just tried to update to Feb from Jan and this happened to me....
Anything I can do about it?
Click to expand...
Click to collapse
Awww crap! Super sorry to hear that! As you can see, not a lot of ideas or thoughts were submitted, and haven't been in a long while, so there doesn't seem to be much/anything that can be done it seems...
If you truly have the exact same thing, then that means that the USB connection is not working, so, you're not able to get into the recovery nor able to run any commands, so the only recourse it seems me and @Coolpente is to contact Google and attempt at a RMA...
But, as this is a third instance -- there may be more; I'm convinced there are, they just have not spoken up here specifically -- I wonder if this is something to be brought up to Google Support (https://productforums.google.com/forum/#!forum/phone-by-google) and their support forums? I mean, although this might not be a widespread widely known issue, this issue does make the device completely unusable and able to be rescued! For me, that's a serious matter -- as most other issues you can learn to live with it (while still being able to use the device for the most part) and/or it's something that can be worked on, repaired, debugged, etc. -- that needs to be attended to, dealt with, or at the very least brought to their attention.
simplepinoi177 said:
Awww crap! Super sorry to hear that! As you can see, not a lot of ideas or thoughts were submitted, and haven't been in a long while, so there doesn't seem to be much/anything that can be done it seems...
If you truly have the exact same thing, then that means that the USB connection is not working, so, you're not able to get into the recovery nor able to run any commands, so the only recourse it seems me and @Coolpente is to contact Google and attempt at a RMA...
But, as this is a third instance -- there may be more; I'm convinced there are, they just have not spoken up here specifically -- I wonder if this is something to be brought up to Google Support (https://productforums.google.com/forum/#!forum/phone-by-google) and their support forums? I mean, although this might not be a widespread widely known issue, this issue does make the device completely unusable and able to be rescued! For me, that's a serious matter -- as most other issues you can learn to live with it (while still being able to use the device for the most part) and/or it's something that can be worked on, repaired, debugged, etc. -- that needs to be attended to, dealt with, or at the very least brought to their attention.
Click to expand...
Click to collapse
I just contacted Google for an RMA. Hope it doesn't occur on the phone that will be shipped to me. Now I am without a phone for a couple weeks...
James1258 said:
I just tried to update to Feb from Jan and this happened to me....
Anything I can do about it?
Click to expand...
Click to collapse
Did you also ran the flash all without - w?
Sent from my Pixel 2 XL using Tapatalk
Greetings,
General
I've been all over the Internet trying to gain access to more information about how to repair my LG G4. Well... Let's start from the beginning.
Story
I have an LG G4, it's old and I've had it for over 4-5 years now... I can't exactly remember how long I had it for. It still works, just needs a new battery and cable (cats chewed the cable and batteries don't last when you forget to disconnect them from the device, leave it plugged in for weeks and let it completely die for longer then a week).
I recently saw a video about the Pine phone and the fact that it was able to run a linux mobile distribution and when I looked into installing a custom OS into LG G4, it was possible... If I manually ported it myself.
I actually got fairly far using my Xubuntu system with configuring and compiling, the trouble I ran into was that I couldn't root or fastboot my device.
So, now here's where the problem began, I have a LG G4 factory reset and when I load up the Recovery mode, it brings up the android guy with their chest open and an exclamation mark in a yellow triangle, no message. After attempting to boot into recovery mode, I wait a little while and the phone automatically resets back to normal. When I use ADB to force the phone into fast boot, it skips it and starts the phone normally.
Now I'm on a mission to find a way to either fix the boot or flash the firmware (in hopes that it fixes the boot/recovery).
I have already tried:
Installing LGFlashTool
Versions, 2.0.1.6, 2.0.1.9, Year: 2014 and 2.0.2.5. Other than year 2014, the other ones were installed from LGFlashTool.com
Since Xubuntu can't run these files properly, I just ran them on my wife's Windows computer
I installed the LG Mobile Drivers and LGFlashTool had registered that it was the correct DLL but, it didn't seem to find the phone
Year 2014 LGFlashTool had found the phone but, I may have had the incorrect kdz file.
The Flash starts and the phone goes to firmware update, but the phone stops at zero and sits there while the program crashes saying that there was an error (in which no means to read, understand or locate the description of this error) and to try again by unplugging and removing the battery.
This version was downloaded from xda-developers.com
Conclusion
Once I can get into fastboot, I'll be able to root my phone and attempt to install the mobile OS I have ready.
Otherwise, I think I might be able to install a microSD card with the OS but, I don't think that will work if I can't get into the option to boot from a separate location (I believe that's called fastboot). But, then again... I think the phone needs to be rooted first... Then that brings me to the previous issue.
Details and Information
The phone details (as far as I see) are:
When I remove the battery I can see:
FCC ID: ZMFH810
IC ID: 2703C-H812
Model Number: LG-H812
I'm not exactly sure what KDZ file I got but the name is: PR H810PR10a_02.kdz, I also have the _04.kdz
I'm using H815 as my compile for the mobile OS, I may switch to H810 when I get back to that point.
Useless information: I still have the original leather backing... Removed from the phone because I didn't like it. If I find it, I can ship it to someone.
That's about it... I am very terrible about research and using Google properly (I have no idea why, I think it's a terrible flaw to have but, I have it). So, if you find the solution by typing words I didn't use or finding a similar post, I am very sorry. Hope I have everything posted here to help solve the issue, linking to posts that can resolve the issue or posting questions on what I might be missing will help.
Thanks in advance for the support of this community,
Lilrock
Lilrock said:
Greetings,
General
I've been all over the Internet trying to gain access to more information about how to repair my LG G4. Well... Let's start from the beginning.
Story
I have an LG G4, it's old and I've had it for over 4-5 years now... I can't exactly remember how long I had it for. It still works, just needs a new battery and cable (cats chewed the cable and batteries don't last when you forget to disconnect them from the device, leave it plugged in for weeks and let it completely die for longer then a week).
I recently saw a video about the Pine phone and the fact that it was able to run a linux mobile distribution and when I looked into installing a custom OS into LG G4, it was possible... If I manually ported it myself.
I actually got fairly far using my Xubuntu system with configuring and compiling, the trouble I ran into was that I couldn't root or fastboot my device.
So, now here's where the problem began, I have a LG G4 factory reset and when I load up the Recovery mode, it brings up the android guy with their chest open and an exclamation mark in a yellow triangle, no message. After attempting to boot into recovery mode, I wait a little while and the phone automatically resets back to normal. When I use ADB to force the phone into fast boot, it skips it and starts the phone normally.
Now I'm on a mission to find a way to either fix the boot or flash the firmware (in hopes that it fixes the boot/recovery).
I have already tried:
Installing LGFlashTool
Versions, 2.0.1.6, 2.0.1.9, Year: 2014 and 2.0.2.5. Other than year 2014, the other ones were installed from LGFlashTool.com
Since Xubuntu can't run these files properly, I just ran them on my wife's Windows computer
I installed the LG Mobile Drivers and LGFlashTool had registered that it was the correct DLL but, it didn't seem to find the phone
Year 2014 LGFlashTool had found the phone but, I may have had the incorrect kdz file.
The Flash starts and the phone goes to firmware update, but the phone stops at zero and sits there while the program crashes saying that there was an error (in which no means to read, understand or locate the description of this error) and to try again by unplugging and removing the battery.
This version was downloaded from xda-developers.com
Conclusion
Once I can get into fastboot, I'll be able to root my phone and attempt to install the mobile OS I have ready.
Otherwise, I think I might be able to install a microSD card with the OS but, I don't think that will work if I can't get into the option to boot from a separate location (I believe that's called fastboot). But, then again... I think the phone needs to be rooted first... Then that brings me to the previous issue.
Details and Information
The phone details (as far as I see) are:
When I remove the battery I can see:
FCC ID: ZMFH810
IC ID: 2703C-H812
Model Number: LG-H812
I'm not exactly sure what KDZ file I got but the name is: PR H810PR10a_02.kdz, I also have the _04.kdz
I'm using H815 as my compile for the mobile OS, I may switch to H810 when I get back to that point.
Useless information: I still have the original leather backing... Removed from the phone because I didn't like it. If I find it, I can ship it to someone.
That's about it... I am very terrible about research and using Google properly (I have no idea why, I think it's a terrible flaw to have but, I have it). So, if you find the solution by typing words I didn't use or finding a similar post, I am very sorry. Hope I have everything posted here to help solve the issue, linking to posts that can resolve the issue or posting questions on what I might be missing will help.
Thanks in advance for the support of this community,
Lilrock
Click to expand...
Click to collapse
Well first of all you need to unlock your phone. H812 can't be unlocked officially though. Check my sig for the only unofficial one. Once unlocked you can flash custom ROMs but first of all you should read about ARB (antirollback) also in my sig and ensure you understand the risks all this brings. Gl.
steadfasterX said:
Well first of all you need to unlock your phone. H812 can't be unlocked officially though. Check my sig for the only unofficial one. Once unlocked you can flash custom ROMs but first of all you should read about ARB (antirollback) also in my sig and ensure you understand the risks all this brings. Gl.
Click to expand...
Click to collapse
Thanks for the positive feedback, I will attempt to fix my phone with your solution. This phone is technically almost garbage and when I fully update the phone, it runs like trash. So, if I can install a custom ROM, it may run a little better or have the tools I would personally like in a phone.
I'll let you know the details of my attempt,
Lilrock
You might be able to use:
GitHub - Lekensteyn/lglaf: LG Download Mode utility and documentation
LG Download Mode utility and documentation. Contribute to Lekensteyn/lglaf development by creating an account on GitHub.
github.com
It is more reliable then the factory tools when it works.
SkewedZeppelin said:
You might be able to use:
GitHub - Lekensteyn/lglaf: LG Download Mode utility and documentation
LG Download Mode utility and documentation. Contribute to Lekensteyn/lglaf development by creating an account on GitHub.
github.com
It is more reliable then the factory tools when it works.
Click to expand...
Click to collapse
Which is included in mAid (https://maid.binbash.rocks).. ... Even with a UI...
Thank you very much with your support. I was able to unlock, bootloader and install the image installer.
I'm on the verge of compiling and installing Ubuntu Touch on my LG G4 H812.
Hope you guys proceed with everything you're doing right!