[HELP] [BRICKED] LG G3 D855 EU bricked, Fastboot mode only - G3 Q&A, Help & Troubleshooting

Hi all!
LG G3 D855, EU, Lollipop I think 5.0.1
I'm trying to find a solution for this, but I can't...
I tried to disable root with super su, and update OTA, ofcourse it didn't went through, as in LG PC suite it said that is updating, but over the night it didn't update, just rebooted my PC somehow and then I found out that I can't boot up my LG G3 D855 anymore.
What can I try?
Is there any step by step unbricking tutorial for this case?
Can't get into download mode...
It's hanging at fastboot: processing commands
Please if anyone can point me to some solution.
Thank you!

Download and extract this and run: "run this"

bender_007 said:
Download and extract this and run: "run this"
Click to expand...
Click to collapse
On a microSD card? Also, should I format it? NTFS, FAT32, exFAT? Or?
As I have two 64GB microSD cards, one is empty, and another is that one I used in LG G3, I'd like not to use that one, to be sure that I don't lose what's on it...
Thanks

vedranius19 said:
On a microSD card? Also, should I format it? NTFS, FAT32, exFAT? Or?
As I have two 64GB microSD cards, one is empty, and another is that one I used in LG G3, I'd like not to use that one, to be sure that I don't lose what's on it...
Thanks
Click to expand...
Click to collapse
Download on computer, extract on computer.
Make sure lg drivers are installed
Connect lg to computer, let it display fastboot mode..
run run_this.bat and sit back

bender_007 said:
Download on computer, extract on computer.
Make sure lg drivers are installed
Connect lg to computer, let it display fastboot mode..
run run_this.bat and sit back
Click to expand...
Click to collapse
OK, I needed to run it as Administrator to get it working.
Now I'm at Firmware Update screen, what next? How should I update it?
LG PC Suite didn't worked for me, as I was rooted, tho I turned off root with SuperSU and I also had enable Debugging mode.

vedranius19 said:
OK, I needed to run it as Administrator to get it working.
Now I'm at Firmware Update screen, what next? How should I update it?
LG PC Suite didn't worked for me, as I was rooted, tho I turned off root with SuperSU and I also had enable Debugging mode.
Click to expand...
Click to collapse
Try booting up first..
Refer to this OP by @hyelton

bender_007 said:
Try booting up first..
Refer to this OP by @hyelton
Click to expand...
Click to collapse
How to boot up if it automatically goes (not connected to PC) to Firmware Update mode?
EDIT1: Problem with KDZ is that it doesn't have firmware for my LG G3 type, EU D855 32GB, only 16GB, and then I tried going TOT route, but when I've got to the point where I need to set my LG G3 into Download Mode with "Power up + connect to PC" then I got stuck with this first problem (firstboot)...
EDIT2: Maybe I should go with TOT route then, as it seems that I didn't had installed drivers properly. Do you think if there's a way to not wipe internal storage somehow?
And forgot to ask, is there an update for LG G3 D855 for Android 6.0? Or still none?

6 is still to come. We have plenty of links for 32gb, look up lgfirmware or check by entering your imei
You have to be in firmware upgrade mode to flash kdz/tot
Poslano sa mog LG-D855 koristeći Tapatalk

wont pass erasing aboot
i rooted my phone and erased apps now i cant access google services and most app force close. im trying to flash back to stock firmware and i cant access download mode. ive been trying to fix this for the passed 2 months now and ready to smash the stupid thing lol.

No problem.
Root your device and flash the partition in android directly.

This happened to me today, I installed a bad rom.
I simply help down power and back button. Then did factory reset.

Phone is not detected and stuck at 'erasing..'
bender_007 said:
Download on computer, extract on computer.
Make sure lg drivers are installed
Connect lg to computer, let it display fastboot mode..
run run_this.bat and sit back
Click to expand...
Click to collapse
I tried the above, it says 'erasing..' but it wont go to the next command.

I can provide you the one for 858hk, why did you even try the one for d855 ?
But anyway if it´s stuck at a command then no use of it, you would have to open it.
Try manually entering: fastboot erase boot

Stuck at command
{
"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"
}
bender_007 said:
I can provide you the one for 858hk, why did you even try the one for d855 ?
But anyway if it´s stuck at a command then no use of it, you would have to open it.
Try manually entering: fastboot erase boot
Click to expand...
Click to collapse
I tried manually but it still showing stuck.. I tried with D858Hk files and for any command it stucks.= here... Drivers issue?

Try another driver package. But if it doesn't work then you have to open it and shortwire
Poslano sa mog LG-H815 koristeći Tapatalk

Related

Formated my SD Card now I am stuck!

So heres the deal, I formated my SD card, so now, there is nothing on the ouya... I still have recovery, but I don't see the big exclamation point and the ouya lettering, wich I trully belive that my litle box is bricked.
My ouya doesn't appear in device manager, nor does it work with adb...
My question is, is there a way to install OTA and/or Custom Roms via OTG?
Thank you. and please help me!
New developments...
My device manager detects an unknown device, however, when I try to install the drivers it won't let me, says that the device could harm my PC.
Il_Padrino said:
So heres the deal, I formated my SD card, so now, there is nothing on the ouya... I still have recovery, but I don't see the big exclamation point and the ouya lettering, wich I trully belive that my litle box is bricked.
My ouya doesn't appear in device manager, nor does it work with adb...
My question is, is there a way to install OTA and/or Custom Roms via OTG?
Thank you. and please help me!
Click to expand...
Click to collapse
Hi,
In al my desperation i also formatted my SD. When the Ouya booted i had nothing more than a black screen.
I rebooted into recovery .. sideloaded the latest OTA and this worked for me (after that i installed the stock plus rom)
But my point of view is "when the device is still being detected by a computer, its possible to recover )
Greetz
I did the same, to be clear: i did wipe data and dalvik to flash a ROM and when y tried to flash i got an error. I dont know how but i missclicked on a keyboard test and dont know how to get out so i had to reboot. The result is a black screen and the device detected as MTP device...
Im trying to get on recovery with the keyboard but it dsnt works :/
tupie said:
I did the same, to be clear: i did wipe data and dalvik to flash a ROM and when y tried to flash i got an error. I dont know how but i missclicked on a keyboard test and dont know how to get out so i had to reboot. The result is a black screen and the device detected as MTP device...
Im trying to get on recovery with the keyboard but it dsnt works :/
Click to expand...
Click to collapse
lel, everytime ill visit a thread to help somebody, their problem seems to be directly releated to the one i had a few days ago.
try to list the device via adb, if it doesnt show up, click this link and scroll down to my second post, it seems recovery, fastboot, and normal operation have 3 different hardware id's.
OPTIONAL
ArdDarvis also pointed out that you can add the id instead of replacing it, just seperate them with a comma like this:
Code:
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2836&PID_0010, USB\VID_18D1&PID_D001
report back and let us know if it worked.
iAmSmokey said:
lel, everytime ill visit a thread to help somebody, their problem seems to be directly releated to the one i had a few days ago.
try to list the device via adb, if it doesnt show up, click this link and scroll down to my second post, it seems recovery, fastboot, and normal operation have 3 different hardware id's.
OPTIONAL
ArdDarvis also pointed out that you can add the id instead of replacing it, just seperate them with a comma like this:
Code:
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2836&PID_0010, USB\VID_18D1&PID_D001
report back and let us know if it worked.
Click to expand...
Click to collapse
Tnx for the help but my problem wasnt like your. I just wiped my data partition. I finally fixed it using the alt+i+imprscrn keys to get on CWM and restoring from backup.
Tnx a lot anyway dude
I went ahed and installed the drivers anyway, and I got a "google device" and not OUYA, my box isn't detected when I try to sideload OTA!
my device manager shows this...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I need help, please...
That may still work like that. My OUYA is detected by Windows 7 home premium 64bit very similarly and I was able to access it using the one click test version.
Go ahead and try to get on to recovery
Sent from my SCH-I535 using Tapatalk 4 Beta
Il_Padrino have you tried reinstalling the driver? also the image is a little small :S
iAmSmokey said:
Il_Padrino have you tried reinstalling the driver? also the image is a little small :S
Click to expand...
Click to collapse
I did. says it's a generic google device, doesn't recognizes being an ouya...
Il_Padrino said:
I did. says it's a generic google device, doesn't recognizes being an ouya...
Click to expand...
Click to collapse
It shouldn't matter. You just need to connect via adb, have you tried to list adb devices from the command prompt?
As I said, that is how my computer lists it and I was able to root it using the test version of the tool kit.
Sent from my SCH-I535 using Tapatalk 4 Beta
TadeoNYC said:
It shouldn't matter. You just need to connect via adb, have you tried to list adb devices from the command prompt?
As I said, that is how my computer lists it and I was able to root it using the test version of the tool kit.
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
my device is listed and connect, however, when I try to sideload the OTA it gives me it shows E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
I tried installing CWM again, and even pushing the boot.img into ouya, but when I go and change the drivers from adb to bootloader the ouya restarts and the alt+prt sc+I method doesn't work...
Just came to realize that all the directories in my memory are gone I tought that it was like the phones, that if you formated the SD Card it would be rebuilt with the standard directories,
Is there any way to create directories trough adb?
Can anyone send me a backup of their system?
or
Do I have a brick?
Il_Padrino said:
my device is listed and connect, however, when I try to sideload the OTA it gives me it shows E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
I tried installing CWM again, and even pushing the boot.img into ouya, but when I go and change the drivers from adb to bootloader the ouya restarts and the alt+prt sc+I method doesn't work...
Just came to realize that all the directories in my memory are gone I tought that it was like the phones, that if you formated the SD Card it would be rebuilt with the standard directories,
Is there any way to create directories trough adb?
Can anyone send me a backup of their system?
or
Do I have a brick?
Click to expand...
Click to collapse
nothing is bricked as long as you still have a recovery installed.
either CWM or Stock, download this: http://devs-ouya-tv-prod.s3.amazonaws.com/ota/RC-OUYA-1.0.356-r1_ota.zip
1.) Then bring your Ouya into recovery, turn it on and hold alt+prt sc+I several times until the Ouya Logo and a exclamation mark shows up, then press HOME.
2.) Do a factory reset
3.) navigate to apply update from ADB, plug your Ouya into USB and use "ADB sideload RC-OUYA-1.0.356-r1_ota.zip"
4.) after a reboot your Ouya should work again.
If you had CWM and applying the OTA update bricked your Ouya, repeat these steps with the Stock recovery, if it didn't flash the stock recovery, try looking for the stock recovery that you can flash with CWM.
This was the case for me, flashing the OTA update with CWM bricked it, but it was fine after I flashed with stock.
My drama is over...
I come to accept it. My OUYA is 100% bricked has I lost recovery from my litle box...
It was fun, but now is over.
:crying:

Instaled wrong ROM, how reinstal? P6-C00

I have Huawei P6-C00. It is Dualsim, china version. I tried instal CyanogenMod 10.1 for p6-u0. Now I can start my phone. When it starts I see:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried instal it by Recovery but I have only this options:
When I conected my phone to computer by USB:
I have clear ROM for my version but I can't instal it. How I can do this? Please help me.
aknorts said:
I have Huawei P6-C00. It is Dualsim, china version. I tried instal CyanogenMod 10.1 for p6-u0. Now I can start my phone. When it starts I see:
I tried instal it by Recovery but I have only this options:
When I conected my phone to computer by USB:
I have clear ROM for my version but I can't instal it. How I can do this? Please help me.
Click to expand...
Click to collapse
dissconnet it from the usb port and if you have the update.app in the dload folder in your SD card, the update should work
It is Dualsim model, It has not SDcard. In place SD slot is second simcard.
Any other solution this issue?
From here
http://dl-uk.huaweinews.com/index.php?dir=Roms/Ascend-P6/
I have oryginalny ROM for this phone, but I don't idea how I can instal it.
Do You have access to external memory via USB?
So, can You use it as mass storage?
If yes, then create a folder on the internal storage vith the name DLOAD and put the official ROM (the file called UPDATE.APP) in it.
Power off your P6.
Hold both vol up and vol down. Turn it on and hold all the three keys (power on, vol up, vol down). When You see Huawei logo, release the Power key, but still hold the vol buttons, untill You see that the update starts.
This is how I could go back to stock ROM from MIUI..
1. No I has not access to external memory via USB. When I tried connect it. I have communicat: http://oi42.tinypic.com/102kz04.jpg
2. No I cant use it as mass storage.
3. When I hold all three keys I see: http://oi44.tinypic.com/jv0xug.jpg
If you can't help I will go to servis with Jtag, but how they open this phone? They can open phone?
aknorts said:
1. No I has not access to external memory via USB. When I tried connect it. I have communicat: http://oi42.tinypic.com/102kz04.jpg
2. No I cant use it as mass storage.
3. When I hold all three keys I see: http://oi44.tinypic.com/jv0xug.jpg
If you can't help I will go to servis with Jtag, but how they open this phone? They can open phone?
Click to expand...
Click to collapse
ur problem isn't that big, u just need to put the firmware file on your internal storage, u might try to flash TWRP via fastboot and u can access your internal storage from it with usb
7OOKA said:
ur problem isn't that big, u just need to put the firmware file on your internal storage, u might try to flash TWRP via fastboot and u can access your internal storage from it with usb
Click to expand...
Click to collapse
adb does not work in stock recovery I think...
edit: oops, my bad. He should be able to do it in the download mode
Thanks for answers.
I am noob, how do it?
aknorts said:
Thanks for answers.
I am noob, how do it?
Click to expand...
Click to collapse
first follow this amazing guide : http://techglen.com/2013/10/01/abd-and-fastboot-guide/
then continue with TWRP guide
Hey, thanks for your help. I do exacly what is in turtorial. But where can I take the recovery_original_flashable.img? It is in ROM? Where?
aknorts said:
Hey, thanks for your help. I do exacly what is in turtorial. But where can I take the recovery_original_flashable.img? It is in ROM? Where?
Click to expand...
Click to collapse
that if you will flash stock recovery, but i guess u will flash TWRP, so after finishing the 1st guide go straight to TWRP thread and download it from there
Good luck
Ok, thx. I did this. But all time I has comunicat: "wait for device" and nothing happend.
aknorts said:
Ok, thx. I did this. But all time I has comunicat: "wait for device" and nothing happend.
Click to expand...
Click to collapse
i will assume that u followed the fastboot guide to the letter and everything went fine, open driver tools and uninstall the drivers and reinstall it, then connect the device to the pc and hold power and vol - buttons till the device reboots then release the power button and keep holding vol - for few seconds (2 or 3) then your pc should recognize ur device as an "adb interface" then u can flash the recovery straight (fastboot flash recovery recovery.img)
if that won't work then u did something wrong in setting fastboot
I tried in two PC and I did step by step. Really I don't know what is wrong.
Probably will not work, but try this one: http://forum.xda-developers.com/showthread.php?t=2618253

[Tools] SRK Tool - ROOT/Recovery/Utility/Unbrick/Fix/Backup [20150502]

I don't respond for What-So-Ever done any damage to your Phone, You must accept this risk with yourself..
This is mini SRK Tool that contain only all stuffs of D802 small size
Download link :
SRKtool_1.0.8_d802_droidth.zip
SRKtool_1.0.7_d802_droidth.zip
SRKtool_1.0.6_d802_droidth.zip
For full package visite this thread :
[TOOLS] SRK Tool 2.0 - Tool for LG Mobile - 20150501
Change log :
1.0.8
- Add Manual Root
- Add change logs
1.0.7
- Add Fixed Stuck 2,49 Percent When flash firmware kdz
1.0.6
- initial version
[LGG2-D802] How to Root Stock Lollipop Firmware with SRK Tool
{
"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"
}
Update manual root
Nice work somboons! This is really useful
Update VDO : [LGG2-D802] How to Root Stock Lollipop Firmware with SRK Tool
Can i root n instal twrp with this tool on 30b?
amazing , thanks you .
Hi, I'm hoping someone can help me with my LG G2.
- I can't access recovery or download mode
- I get the multiple drive letters and the one containing the "image"-folder
- I can see the phone-memory in disk management
- It doesn't however show up as anything but "unknown device" under "other devices", nothing under ports
Please help! What can I do when my phone doesn't show up as anything but "unknown device" in device manager?
I managed to get my phone detected as QHSUSB_BULK and ran the fix using this tool. The operation seemed to go well, no errors and said "DONE" at the end. I then disconnected, restarted and tried to enter the download mode. It was still the same though. No download mode, showed multiple drive letters and the "image"-folder, QHSUSB_BULK i device manager.
Any ideas what I can do?
EDIT: It does seem to have made some difference after all. I now get into recovery (well, "Factory data reset"-thingy, no recovery loads). Can I some how flash TWRP and then CM from here?
I got demigod crash handler error and a mate who had this problem told me that this tool can help me.
I tried to use it, but SRK displays "waiting for device" and nothing happens after that. The PC doesn't recognize the phone.
tommy paradise said:
I got demigod crash handler error and a mate who had this problem told me that this tool can help me.
I tried to use it, but SRK displays "waiting for device" and nothing happens after that. The PC doesn't recognize the phone.
Click to expand...
Click to collapse
Screen shot please in device manager too maybe you have to shot circuit.
Sent from my LG-H818 using Tapatalk
I can only enter download mode but no recovery. Is there anyway to fix this issue as i have to flash rom from my recovery. It helped previously with fastboot mode. Now i can enter only download mode. and i dont know how to enter fastboot mode manually. Please help!
beandroid9 said:
I can only enter download mode but no recovery. Is there anyway to fix this issue as i have to flash rom from my recovery. It helped previously with fastboot mode. Now i can enter only download mode. and i dont know how to enter fastboot mode manually. Please help!
Click to expand...
Click to collapse
I sugest, return to stock rom , flash kdz, than root and install new TWRP recovery problem solved.
---------- Post added at 11:53 AM ---------- Previous post was at 11:51 AM ----------
By the way, can this tool fix problem with 32 gb lg g2 d802, becomes 16 gb after bad update ? thanks
4. Fixed Recovery Mode - via fastboot mode (No Recovery,Can't Boot)
not working on D802 32GB stuck on fastboot mode
please please please help help...........
Thank you for the tool, really helped me a lot as I rooted my G2, without much ground work flashed a recovery image and everything was just not good after that.
My D802 isn't recognized by my win7 pc. Unable to do anything with you app. My phone can't boot in any mode however fastboot, download mode or recovery
Édit : i found and could boot on download mode. Well, I could flash by lg flash the lp kdz on my d802. But now i am unable to root it
Edit : problem solved ??
Thanks a lot. I fixed my LG G2 D801 with this tool
Sent from my SM-N910C using Tapatalk
Hello, I need root phone is this work on 4.4.2 / D80220c-466-92 / 32gb phone?
I saw that root + twrp is only for Lollipop ... am i wrong?
LG-G2-802 error native opening
I need help,
srk tool cant writh or read the *.img file the the Picture
Thanks
For D802 V30C on android 5.0.2 - 32GB couldn't find a working solution to root & TWRP together, but this app on manual mode I managed to get to root stage, then I had to manually push the TWRP through ADB which I downloaded from TWRP site. (pushed but did not work)
How and where;
I downloaded the image and placed it in the root of my /sdcard folder and renamed it to twrp.img. then Ran the following commands via adb shell.
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
then I tried the second option (auto root & TWRP) on the ROOT menu, and it worked. :angel:

Bricked ZL550 - Any ideas?

I bricked my U.S. market ZL550 Zenfone 2. My bad, I spent the last two weeks desperately trying everything I could think of to get Link2SD to mount an Ext2 or 4 partition on my SDXC card, and I wasn't at all surprised when it hung on the Asus logo while booting on Saturday.
Anyway, I can't get it to boot normally again. Using fastboot, I flashed recovery, boot and droidboot from the latest Asus ROM, Z008-WW-2.18.40.7, but when I try to flash the system image zip, I get a bunch of errors and a "fail" message on the phone.
I tried sideloading the image with adb but adb won't connect to the phone in recovery mode. Also tried copying the image zip to the SD Card but that wouldn't load, it would only look for MOFD_SDUPDATE.ZIP.
I can return it, I'm not exactly thrilled with it anyway. Anyone have any ideas of what I might try before sending it back?
Thanks! Carl
ConnCarl said:
I bricked my U.S. market ZL551 Zenfone 2. My bad, I spent the last two weeks desperately trying everything I could think of to get Link2SD to mount an Ext2 or 4 partition on my SDXC card, and I wasn't at all surprised when it hung on the Asus logo while booting on Saturday.
Anyway, I can't get it to boot normally again. Using fastboot, I flashed recovery, boot and droidboot from the latest Asus ROM, Z008-WW-2.18.40.7, but when I try to flash the system image zip, I get a bunch of errors and a "fail" message on the phone.
I tried sideloading the image with adb but adb won't connect to the phone in recovery mode. Also tried copying the image zip to the SD Card but that wouldn't load, it would only look for MOFD_SDUPDATE.ZIP.
I can return it, I'm not exactly thrilled with it anyway. Anyone have any ideas of what I might try before sending it back?
Thanks! Carl
Click to expand...
Click to collapse
I'm surprised!! Why do you need link2sd??? with 32 GB Internal, I have 118 Apps installed along with movies and music. Still I have space( I have not used SD Card).
Anyways,
From what you mentioned, you seem to have a ZE551ML. And you Installed Z008-WW-2.18.40.7. It should be Z00A and not Z008. Please download the correct firmware and try out.:good:
Thumb-rule,
ZE550ML = Z008
ZE551ML = Z00A
I guess thats what you did Wrong
Thanks for pointing that out! It's actually a 16GB 550.
I'd go and connect it to pc on fastboot and wipe everything via command. Ex. Fastboot erase system, data, cache. Then flash a stock Rom from Asus via adb sideload
ConnCarl said:
Thanks for pointing that out! It's actually a 16GB 550.
Click to expand...
Click to collapse
for MOFD_SDUPDATE.zip to work, you need to place it on the external sd card and reboot into recovery. It will automatically start to install.
Placing it on the Internal card wont help.
---------- Post added at 08:58 AM ---------- Previous post was at 08:57 AM ----------
lordpipa said:
I'd go and connect it to pc on fastboot and wipe everything via command. Ex. Fastboot erase system, data, cache. Then flash a stock Rom from Asus via adb sideload
Click to expand...
Click to collapse
I wouldnt recommend that.
He is unable to use adb properly. And if he messes up something, he might even lose his warranty
lordpipa said:
I'd go and connect it to pc on fastboot and wipe everything via command. Ex. Fastboot erase system, data, cache. Then flash a stock Rom from Asus via adb sideload
Click to expand...
Click to collapse
Tried all that. Many times.
ConnCarl said:
Tried all that. Many times.
Click to expand...
Click to collapse
When i restored from stock via ADB, I was going from a preroot, bricked, because I updated and was getting the little error bot.. After i sideload the image, i still had to factory reset. I'm just guessing, but you did try and do the factory reset after fastboot/ADB.
godgib said:
When i restored from stock via ADB, I was going from a preroot, bricked, because I updated and was getting the little error bot.. After i sideload the image, i still had to factory reset. I'm just guessing, but you did try and do the factory reset after fastboot/ADB.
Click to expand...
Click to collapse
I can't sideload the image, because I can't connect with ADB.
ConnCarl said:
I can't sideload the image, because I can't connect with ADB.
Click to expand...
Click to collapse
but you can get into recovery, it's just when you click on "ADB update" your computer doesn't see the phone, that's my understanding...
Right, correct. I can get into recovery, and fastboot works, but not ADB.
ConnCarl said:
Right, correct. I can get into recovery, and fastboot works, but not ADB.
Click to expand...
Click to collapse
It sounds like you still in fastboot and not recovery. This is what recovery looks like and then you put in it "Apply update ADB sideload."
{
"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"
}
Yep, that is exactly what it looks like. But when I try to sideload, it times out. ADB won't see the phone.
ConnCarl said:
Yep, that is exactly what it looks like. But when I try to sideload, it times out. ADB won't see the phone.
Click to expand...
Click to collapse
I'm pretty sure if it timse out using ADB sideload then it should also timeout when you type ADB deviecs, but try it you should see your serial number sideload.... If you don't then
1. Make sure you have ADB 1.42 with intel drives 1.9
2. Use the stock cable.
3. In device manager make sure there's no unknown Android devices.
4. if ADB still doesn't work then try and flash via fast boot a new boot.img and recovery.img.
5. If you do get to the point where you can sideload...
6. Downloaded the ASUS firmware with WW not CN.
7. Also make sure the firmware package doesn't have ext .zip.zip, because of unknown file ext in windows.
Not sure if this works but you can give it a try.
Have you boot it with Temp CWM?
Delete all cache, including those of under advanced section
install zip file should work to install your full rom. since you stated you cant adb to detect.
Thanks everyone for all the suggestions!
I was just sort of reviewing godgib's screen grab when it slowly dawned on me that at least part of the solution had been staring me in the face all along.
It had never occurred to me that adb might not be able to connect even though fastboot could. Then when I read "you need adb 1.0.32 or newer to sideload to this device", it started to make sense. I upgraded adb and connected but still couldn't sideload. After reviewing godgib's methodical list, I realized it was a driver problem. Once I squared that away, sideload went without a hitch.
Interesting side note...I don't know what build I had originally, but it had to be at least a month old or so. I figured I might as well get the latest release, so I went with Z008_WW_2.18.40.7, and I updated boot/droidboot/recovery while I was at it. The funny thing was that when it booted, it was set for 250 dpi and everything was tiny.
Luckily, since adb was finally working (thanks again godgib) I was able to send "adb shell wm density 480" to put it back to normal.
Thanks again, everyone!
Carl
Glad you got it working...
Sent from my ASUS_Z00AD using XDA Free mobile app
godgib said:
Glad you got it working...
Sent from my ASUS_Z00AD using XDA Free mobile app
Click to expand...
Click to collapse
Appreciate that.
Of course now auto-rotate is borked. I'll have to either wait for a patch or downgrade.
Did you ever figure out the sdcard problem? I just got the same card and want to do the same thing. But the phone wont see the second partition at all.
i have similar problem too

Question Red Warning and UnWorking Lockscreen. 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"
}
Hello, dear owners of this beautiful device.
After an unsuccessful attempt to get root, such a warning appeared, plus the ability to lock the screen disappeared. As a result, I didn't get root either and problems arose)
Could you show the instructions how to fix everything step by step and get root? Thanks)
Hey, so I have the same problem as you. I was installing the patched boot.img file when I rebooted, but there was no magsik app. After I tried to flash the same file again, except I put in some vbmeta file because some website said so, now my phone's files are corrupted. I got into fastboot mode and put through recovery mode, and did a data wipe and one final reboot, but even that did work because it said my phone is corrupt. The last thing I will try is to install TWRP, remove the old data, and install the update to restore the previous ROM files. I'll let you know if anything works. Just try ur methods and let me know if they worked. Sure is an expensive paperweight if it doesn't work...
redmgicUSER8 said:
Hey, so I have the same problem as you. I was installing the patched boot.img file when I rebooted, but there was no magsik app. After I tried to flash the same file again, except I put in some vbmeta file because some website said so, now my phone's files are corrupted. I got into fastboot mode and put through recovery mode, and did a data wipe and one final reboot, but even that did work because it said my phone is corrupt. The last thing I will try is to install TWRP, remove the old data, and install the update to restore the previous ROM files. I'll let you know if anything works. Just try ur methods and let me know if they worked. Sure is an expensive paperweight if it doesn't work...
Click to expand...
Click to collapse
did anything happen?
Stusick said:
Did anything happen?
Click to expand...
Click to collapse
Nothing yet... I'm trying to contact the support team. They can only do so much remotely
i have this error also what should i do?
the phone not boot up
the red warning are stuck
yakir150 said:
i have this error also what should i do?
the phone not boot up
the red warning are stuck
Click to expand...
Click to collapse
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot
[email protected] said:
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot
Click to expand...
Click to collapse
okay i try it and still no luck the same problem
yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
Download global V3.19 rom from: https://rom.download.nubia.com/Europe&Asia/NX729J/V319/NX729J.zip
Download QPST and QFIL flash tool from: https://www.mediafire.com/file/220h5xaxi1gd55m/QPST_2.7.496.zip/file. Install the driver (provided in the download) and these two programs.
You could then flash this rom V3.19 using QFIL flash tool. If you can flash this rom successfully your phone will work.
[email protected] said:
Download global V3.19 rom from: https://rom.download.nubia.com/Europe&Asia/NX729J/V319/NX729J.zip
Download QPST and QFIL flash tool from: https://www.mediafire.com/file/220h5xaxi1gd55m/QPST_2.7.496.zip/file. Install the driver (provided in the download) and these two programs.
You could then flash this rom V3.19 using QFIL flash tool. If you can flash this rom successfully your phone will work.
Click to expand...
Click to collapse
my phone is eu and using 4.18
can i use 3.19?
it's ok?
yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
For QFIL, use Flat Build and in the configuration use ufs. Good luck!
yakir150 said:
my phone is eu and using 4.18
can i use 3.19?
it's ok?
Click to expand...
Click to collapse
Your version V4.18 will be replaced by V3.19. This V3.19 version can be flashed through edl mode. I could not find V4.18 in this format. The two roms are very similar. They are both global roms.
[email protected] said:
Your version V4.18 will be replaced by V3.19. This V3.19 version can be flashed through edl mode. I could not find V4.18 in this format. The two roms are very similar. They are both global roms.
Click to expand...
Click to collapse
okay i will try and let you know
thank you very much
yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
If QFIL does not work, you need to do side load the rom multiple times again then it might work!
turn off the red rm8 notification (Your device is broken. It is unreliable and may not work)
- enter command on PC: adb reboot "dm-verity enforcing"
- on phone for rooted device with termux: reboot "dm-verity enforcing"
izsdeaman said:
turn off the red rm8 notification (Your device is broken. It is unreliable and may not work)
- enter command on PC: adb reboot "dm-verity enforcing"
- on phone for rooted device with termux: reboot "dm-verity enforcing"
Click to expand...
Click to collapse
The command on PC shows "Too many arguments." The Termux one works. Thanks!
[email protected] said:
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot
Click to expand...
Click to collapse
Tahnk you very very very much.

Categories

Resources