Related
This is for LG G3 D851 ONLY
TOT/KDZ/TWRP Untouched stock restore
IF YOU WANT TO USE THIS GUIDE WAIT UNTIL I HAVE THE LGUP METHOD UP
Who can benefit from this?
Anyone who softbricked with access to download mode [KDZ RECOMMENDED]
Anyone who wants to use the OTA function after root [TWRP RECOMMENDED]
Anyone who needs to send the phone in for repair [TOT RECOMMENDED]
Anyone who wants to be on the most recent firmware [TWRP RECOMMENDED]
Anyone who wants to downgrade *After you update to 20B it is recommended to not downgrade. If you do you WILL have connection problems
Anyone who wants to return to stock from aosp or aokp
Tip: Most of the time TWRP will do what you need without the troubles and baggage TOT and KDZ bring. It will downgrade, upgrade, root, fix soft bricks or just give you a fresh untouched operating system (no personal data left on the phone if you follow instructions). It will also get rid of any proof on the phone that you were rooted (my t-mobile reports root to a remote server nothing can be done about that).
Strengthens and weaknesses for each method click here
TWRP Files/flashing guide Most recent = D85130g_00_0420 (07/05/17)
(This is a WIP)
Download your preferred choice of D851xxx-Untouched_Stock_Restore.zip HERE (Perfect 1:1 image unlike most roms)
Also download and copy superSu & twrp to your external sd if you want root and custom recovery SUPERSU DOWNLOAD AND TWRP-2.8.6.0-d851.zip
Copy D851xxx-Untouched_Stock_Restore.zip to phone (external sd if available)
Reboot into twrp
For firmware update do not wipe! skip to step 8. If you want untouched stock continue with step 4.
If upgrading from kitkat to lollipop wipe system before flashing.
Click [Wipe]
Click [Advanced Wipe] (For full wipe stock restore only)
Select dalvik cache, system, Data, Internal storage (only if you use external for downloaded file) and cache
Click the home Icon in the bottom left
Click [Install]
Select D851xxx-Untouched_Stock_Restore.zip (make sure you select the proper sd card)
If you want root and/or twrp add UPDATE-SuperSU-v2.37.zip to the queue by touching [Add More Zips]
Repeat for TWRP-2.8.6.0-d851.zip
Swipe to install [====>]
Install will now begin, pure stock: system, kernel, recovery, modem and rpm will be installed
After completion click [wipe cache/dalvik] (do not skip especially if you dirty flashed)
Swipe to wipe [====>]
Click [back]
Click [reboot system] (it might say no os but it is wrong you do have a os click restart anyway) [dirty flash will not have that problem]
If your sending for repair or jump do a factory reset with what should now be the stock recovery just to be safe.
DO NOT INSTALL ROOT UNLESS YOU WANT IT TO BE ROOTED
LGUP (KDZ/TOT)
(This is a WIP)
Check back later
KDZ files/flashing guide (Use TWRP if you can)
(This is a WIP)
Here are the KDZ files for the D851 I will keep this up to date as they are released
Make sure you uncompress the file!
Most recent Firmware
D85130g_00_0420 (07/05/17)
Old Firmware
D85130e_00_0711 (08/08/16)
D85130d_00_0404 (05/02/16)
D85120G_00 (10/05/15)
D85120E_00 (06/10/15)
D85120B_00 (04/17/15)
D85110R_00 (12/2/14)
D85110M_00 (09/10/14
D85110C_00 (07/16/14)
KDZ FLASHING GUIDE
For windows vista - windows 8.1
Very buggy on windows 8/8.1 x64 YMMV
Will not work on windows xp or older
Click to expand...
Click to collapse
Download, extract and install LGUnitedMobileDriver
Download, extract and install VBCFJRedist_AIO_x86_x64
Download and extract LG Flashtool 2014.7z (This is not the same flash tool in TOT method)
Download one of the KDZ files from the beginning of the post and extract it in the Flashtool folder
Make sure you are at least at 50% battery
Enter download mode by holding the volume up button + plug the phone into the computer from a powered off state
Run LGFlashTool2014.exe as administrator
select type [CDMA] (Yes CDMA works just fine for our T-Mobile GSM phones DO NOT USE THE OTHER OPTIONS)
phone mode [diag]
reset time [33000]
select the KDZ file you extracted from inside the flashtool folder (D851xxx_00.kdz)
select [normal flash] (no wipe) or [CSE flash] (wipe) (Recommended)
click [start]
Select Country and Language Just leave default selections and click OK (Republic of Korea is the only country and it defaults to English)
It will analyze the phone extract the firmware and upgrade your phone automatically you will see progress on both the computer and phones display once the s/w upgrade percentage gets to about 80% your phone will restart don't freak out all went well and it will boot up to the LG welcome screen and if you selected CSE it will restart one last time
Total flash time for me was 2 minuets 56 seconds
If you use the normal flash you might need to do a factory reset if you get in a bootloop after flash
cse should have 0 problems on boot
Credits:
All credit goes to quangnhut123 for creating this tool you can find his thread HERE
TOT files/flashing guide
(This is a WIP)
Download, extract and install VBCFJRedist_AIO_x86_x64.exe
Download, extract and install LGUnitedMobileDriver
Download and extract lg flash tool (This is not the same flash tool in KDZ method)
Download and extract LG_D851.10C_TOT&DLL.7z
Make sure you are at least at 50% battery (if you can)
Enter download mode by holding the volume up button + plug the phone into the computer from a powered off state
Leave phone plugged in and in pc go to settings/control panel/device manager/ports right click on lgemobile serial port and click properties then select the port settings tab and click advanced then change com port number to 41 and click ok
Unplug phone
Run LGFlashTool.exe as administrator
If you get a DBMS WINDOWS leave it on ?? ?? (Korea Factory) and click ok
Check select manual mode
For DLL click [...] and select the dll from the package you extracted (LGD851_20140611_LGFLASHv160.dll)
If you are getting a model check error download/extract and try this generic LG dll
For S/W click [ADD] and select the tot from the package you extracted (LGD851AT-01-V10c-310-260-JUN-20-2014+0.tot)
Make sure in action mode BOARD DL is selected and in connection mode USB is selected
Click [OK]
Click the [yellow arrow] that is pointing to the right
Wait until Port 1 (COM41) says READY! (could take a couple minutes give it time)
Plug your phone back in and it will start flashing automatically DO NOT UNPLUG THE PHONE
After its done sending the firmware over your phone will reboot into mini os and you will see a blue screen with a big 2 wait until you see a big 3 then unplug the phone and close the lgflashtool program. Your phone might automatically reboot on 3 but it hasn't for me If it doesn't just pull the battery put it back in then power up. After one of the updates this step may be different then described. If you have problems just ask and myself or somebody else will be able to help.
Everything that lives inside the KDZ files except system HERE
(If you want the system.img download the twrp files)
Software version D85130g
Android 6.0.1
July 5, 2017
2G/3G data roaming fix
Google monthly security patch
LG app fix
software stability and software improvements
Software version: D85130e
Android 6.0.1
August 8, 2016
Google security enhancements
Software stability
Software version: D85130d
Android version 6.0
May 2, 2016
Android Marshmallow
Wi-Fi Calling improvements
Software version: D85120g
Android version 5.0.1
October 5, 2015
Messaging security improvements (Stagefright)
Software version: D85120e
Android version 5.0.1
June 10, 2015
Android 5.0 Lollipop
Turns on VoLTE
Wi-Fi Calling 2.0
Software stability
Software version: D85120b
Android version 5.0.1
April 7, 2015
Android 5.0 Lollipop
Turns on VoLTE
Wi-Fi Calling 2.0
Software version: D85110r
Android version 4.4.2
December 2, 2014
Wi-Fi Calling enhancements
Security enhancements
Bluetooth connectivity improvements
Various bug fixes
Software version: D85110m
Android version 4.4.2
September 10, 2014
Wi-Fi Calling enhancements
Security enhancements
Various bug fixes
Software version: D85110c
Android version 4.4.2
July 16, 2014
Original software version
So use this method to flash back to stock?
RMXO said:
So use this method to flash back to stock?
Click to expand...
Click to collapse
Correct it also gives developers a chance to start making stock roms even though we don't have root or a recovery yet.
What is a KDZ file?
wirelessrevolution said:
What is a KDZ file?
Click to expand...
Click to collapse
It holds all of the files and partitions for flashing back to stock.
Updated OP with Flash method!
ThePagel said:
Updated OP with Flash method!
Click to expand...
Click to collapse
thanks OP.
thanks for this OP.
now since TWRP was released for the t-mobile g3, soon enough this kdz package will be converted to a TWRP compatible flash package
TYVM, it worked like a charm.
Thanks for the guide ! Will definitely come in handy
Ok now I'm not sure if im reading this correctly but it says in OP to Download one of the KDZ files from the beginning of the post and extract it in the Flashtool folder from his thread, now when i got o his thread I only see the G2 files not the G3? someone maybe point me to the one i need for the D851?
EDIT: never mind im an idioto! disregard
turilo said:
Ok now I'm not sure if im reading this correctly but it says in OP to Download one of the KDZ files from the beginning of the post and extract it in the Flashtool folder from his thread, now when i got o his thread I only see the G2 files not the G3? someone maybe point me to the one i need for the D851?
EDIT: never mind im an idioto! disregard
Click to expand...
Click to collapse
Ill move the credits to the bottom of the op so no one else can get confused
Mine times out at 2%
Any ideas??
Mikey said:
Mine times out at 2%
Any ideas??
Click to expand...
Click to collapse
what operating system are you on?
Great guide! Just what I was looking for. 2 questions though... Will this unroot your device? (I would presume untouched stock means that, but you know what happens when I presume. I make a pres of you and me). (I'm looking for a reliable to way to uproot, just in case I want to get an OTA). Also, could you link to the G3 drivers in the OP? This is gonna be my go to post if anyone asks me about it...
Sent from my Nexus 10 using XDA Premium 4 mobile app
ThePagel said:
what operating system are you on?
Click to expand...
Click to collapse
Win7 Ultimate 64-Bit
Mikey said:
Win7 Ultimate 64-Bit
Click to expand...
Click to collapse
Worked for me on 8.1 so it should work for you. Install Microsoft c++ runtime 2012 or 2013 then try again. Also make sure you have the proper drivers installed. Ill upload both runtime and drivers when i get home so if you cant find them check back around 6 or 7.
*Edit
Also make sure your running as administrator.
DefinityX said:
Great guide! Just what I was looking for. 2 questions though... Will this unroot your device? (I would presume untouched stock means that, but you know what happens when I presume. I make a pres of you and me). (I'm looking for a reliable to way to uproot, just in case I want to get an OTA). Also, could you link to the G3 drivers in the OP? This is gonna be my go to post if anyone asks me about it...
Sent from my Nexus 10 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks!
It will unroot you and it already saved my butt after I accidentaly formatted most of the partitions on the phone. I plan on uploading the unified lg drivers tonight along with c++ runtime. Im also going to hunt down a nice guide and link to it for flashing via the lg suite if this fails. The lg suite way is a pain in the a** but should work if this one fails.
Mikey said:
Win7 Ultimate 64-Bit
Click to expand...
Click to collapse
ThePagel said:
Worked for me on 8.1 so it should work for you. Install Microsoft c++ runtime 2012 or 2013 then try again. Also make sure you have the proper drivers installed. Ill upload both runtime and drivers when i get home so if you cant find them check back around 6 or 7.
*Edit
Also make sure your running as administrator.
Click to expand...
Click to collapse
If you need drivers for Windows (thanks @autoprime for having these handy!):
Everyone Else: http://downloads.codefi.re/autoprime...Ver_3.11.3.exe
Click to expand...
Click to collapse
UPDATE
1- I downloaded 2013 Runtime 2013 from here: http://www.microsoft.com/en-us/download/details.aspx?id=40784
2- Rebooted my PC
3- Followed the instructions in OP, performing the CSE flash.
4- Received a timeout error really quick but it started to flash.
5- Around 80% the phone went black and never booted to the LG screen, after it hit 100% I unplugged it, removed the battery and rebooted it.
Booting up it entered some mode for a split second and rebooted itself.
Once on homescreen, it rebooted itself one last time.
I'm UnRooted now
I guess i needed to install C++ Runtime
Thanks
I am not currently available i am in bootcamp for the navy.
Note: Ok for anybody browsing this thread right now the 500gb version shield tv seems to be having issues mounting partition now. The 16gb should work correctly though
this is thread on how to root the Nvidia shield android TV on android marshmallow. I do not own the software used here. I also want to state the ota will work with twrp installed but the ota will replace twrp with stock and delete root. this process should still work but if it does not try flashing to stock android lollipop which erases all userdata and then re-upgrade and try again. you will also need a usb mouse for this but it might also work with a keyboard which I did not test.
download twrp and supersu from this pages.
supersu
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
twrp
http://forum.xda-developers.com/shield-tv/general/recovery-twrp-2-8-6-0-shield-tv-variants-t3140926
1. transfer the supersu zip file to the internal storage in any way you want just make sure it is in the internal storage.
2. make sure adb and fastboot work properly on your computer. it does not matter which operating system.
3. reboot nvidia shield android tv to bootloader screen either by making sure usb debugging is enabled and running adb reboot bootloader or using the hardware method I copied from the nvidia site.
HW method:
- Disconnect power cable
- Insert USB OTG cable and make sure to connect other end to a host PC
- Connect power cable to SHIELD
- Quickly start pressing power button for ~3 seconds
- Do not hold the button and connect power supply afterwards
- HDMI TV should be always connected to SHIELD
4. once in the bootloader screen make sure your mouse is hooked up the nvidia shield android tv and on the computer make sure you have a command prompt or terminal open and in the same directory as where your twrp file is located.
5. if on windows run fastboot boot twrp.img, if on ubuntu run sudo fastboot boot twrp.img
note: make sure to replace twrp.img with the name of the downloaded file.
6. if everything is done successfully up to this point you should be in a normal twrp environment.
7. you can flash the supersu zip file like normal and it should take about a minute to finish. if everything was succesfully you should have root access now.
note: if twrp asked you to install supersu do not and also if it displays a screen asking about leaving system read-only tell it to leave read-only
sorry about the disorganization I suck at writing. If someone wants to help me organize this post that would be awesome.
Note: it appears that people with the 500gb version are having issues mounting the partitions to install the supersu.zip
if you have issues try backing your data up and flashing to stock android lollipop and installing the ota without rooting. It is very important that twrp does not mount system read write. If this does not work i will update this post as we figure this out.
P.s. i have the 16gb model shield tv
On either of my Shields, twrp cant mount the partitions to install zip. How were you able to install it?
Same here...can't mount
Izsūtīts no manas Nokia 3310 используя бесплатную xda app
visitor29 said:
Same here...can't mount
Izsūtīts no manas Nokia 3310 используя бесплатную xda app
Click to expand...
Click to collapse
Try flashing the android lollipop and installing the ota without rooting at any point. Also make sure that twrp does not mount system read write
Shadicbypass said:
Try flashing the android lollipop and installing the ota without rooting at any point. Also make sure that twrp does not mount system read write
Click to expand...
Click to collapse
Belive me or not last 24hours i was stuck on 2.1 and 2.0 downgrading (i don't recommend downgrade ). Downgrading to 2.1 or 2.0 make console freezing on welcom screen where need WiFi password setup and Google password details, to get finally till developer debug option . You can't return back on Ota coz twrp can't see your patriots....amd bla bla
I can continue and continue, when you updating Vulcan ota you updating bootloader and new bootloader not works back on 2.1. So don't do downgrade, I'm kind of lucky to didn't brick, but yesterday I kind of reanimated back on vulkan. + there is no yet mm6 os image where you can easily rollback through fastboot.
Izsūtīts no manas Nokia 3310 используя бесплатную xda app
visitor29 said:
Belive me or not last 24hours i was stuck on 2.1 and 2.0 downgrading (i don't recommend downgrade ). Downgrading to 2.1 or 2.0 make console freezing on welcom screen where need WiFi password setup and Google password details, to get finally till developer debug option . You can't return back on Ota coz twrp can't see your patriots....amd bla bla
I can continue and continue, when you updating Vulcan you updating bootloader and new bootloader not works back on 2.1. So don't do upgrade, I'm kind of lucky to didn't brick, but yesterday I kind of reanimated back on vulkan.
Izsūtīts no manas Nokia 3310 используя бесплатную xda app
Click to expand...
Click to collapse
I did ended up having to do downgrade to 2.1 ota and installing the ota to marsgamllow before twrp would install the zip but i thought that was because i accidently told twrp to root my rom when it asked. But i can say it is possible to downgrade as long as you use the full official stock from nvidia's website. It is a pain to do though. It should not be required to root though.
Shadicbypass said:
I did ended up having to do downgrade to 2.1 ota and installing the ota to marsgamllow before twrp would install the zip but i thought that was because i accidently told twrp to root my rom when it asked. But i can say it is possible to downgrade as long as you use the full official stock from nvidia's website. It is a pain to do though. It should not be required to root though.
Click to expand...
Click to collapse
I presume you rooted (loaded supersu.zip) when - when update vulkan ota - before rebooting. Coz after upgrading vulkan and straight rebooting afterwards you loosing twrp. I have vulkan installed and more then 10x I tried playing with twrp loading and give up, but downgrading no no will not gonna go back - enough for me last two days with those experiments ???
Izsūtīts no manas Nokia 3310 используя бесплатную xda app
---------- Post added at 02:28 PM ---------- Previous post was at 02:25 PM ----------
Shadicbypass said:
I did ended up having to do downgrade to 2.1 ota and installing the ota to marsgamllow before twrp would install the zip but i thought that was because i accidently told twrp to root my rom when it asked. But i can say it is possible to downgrade as long as you use the full official stock from nvidia's website. It is a pain to do though. It should not be required to root though.
Click to expand...
Click to collapse
And yes official os from Nvidia Website
Izsūtīts no manas Nokia 3310 используя бесплатную xda app
visitor29 said:
I presume you rooted (loaded supersu.zip) when - when update vulkan ota - before rebooting. Coz after upgrading vulkan and straight rebooting afterwards you loosing twrp. I have vulkan installed and more then 10x I tried playing with twrp loading and give up, but downgrading no no will not gonna go back - enough for me last two days with those experiments ???
Izsūtīts no manas Nokia 3310 используя бесплатную xda app
---------- Post added at 02:28 PM ---------- Previous post was at 02:25 PM ----------
And yes official os from Nvidia Website
Izsūtīts no manas Nokia 3310 используя бесплатную xda app
Click to expand...
Click to collapse
No i followed the directions that i posted the the first post in this thread. I rooted after completly installing the vulkan ota and rebooting and letting it optimize and everything
Shadicbypass said:
5. if on windows run fastboot boot twrp.img, if on ubuntu run sudo fastboot boot twrp.img
note: make sure to replace twrp.img with the name of the downloaded file.
Click to expand...
Click to collapse
I use fastboot flash recovery twrp.img
And it works
1. Update to Murshmallow
2. adb push supers.zip / sdcard /
3. install TWRP fastboot flash recovery twrp.img
4. Flash SuperSU.zip using TWRP
graafi said:
I use fastboot flash recovery twrp.img
And it works
1. Update to Murshmallow
2. adb push supers.zip / sdcard /
3. install TWRP fastboot flash recovery twrp.img
4. Flash SuperSU.zip using TWRP
Click to expand...
Click to collapse
Well i only used the boot command in case someone did not want to permently keep twrp or wanted to keep the stock recovery
Shadicbypass said:
Well i only used the boot command in case someone did not want to permently keep twrp or wanted to keep the stock recovery
Click to expand...
Click to collapse
OK will try after few hours, I'm at work now! Thanks for this
Izsūtīts no manas Nokia 3310 используя бесплатную xda app
same story
have look
make a video for you https://www.youtube.com/watch?v=nScFvuwEDts
just wanna say your tutorial is not for me and i believe not only me one out there with this problem (have same problem downgrading twrp didn't show nothing and etc....long story how i get beck Vulcan, but defiantly will not gonna do again same way )
visitor29 said:
same story
have look
make a video for you https://www.youtube.com/watch?v=nScFvuwEDts
just wanna say your tutorial is not for me and i believe not only me one out there with this problem (have same problem downgrading twrp didn't show nothing and etc....long story how i get beck Vulcan, but defiantly will not gonna do again same way )
Click to expand...
Click to collapse
Hm can you pm me your recovery.log and you try going to stock android 5.1 or nvidia shield android tv version 2.1 fully stock and then update without rooting. You should no issues downgrading because nvidia has a update for the bootloader to downgrade to 2.1 then try to update
Shadicbypass said:
Hm can you pm me your recovery.log and you try going to stock android 5.1 or nvidia shield android tv version 2.1 fully stock and then update without rooting. You should no issues downgrading because nvidia has a update for the bootloader to downgrade to 2.1 then try to update
Click to expand...
Click to collapse
Im dunno get log? nowhere to save if twrp not mount system or data or sdcard etc
Izsūtīts no manas Nokia 3310 используя бесплатную xda app
visitor29 said:
Im dunno get log? nowhere to save if twrp not mount system or data or sdcard etc
Izsūtīts no manas Nokia 3310 используя бесплатную xda app
Click to expand...
Click to collapse
True well try flashing back to stock using the full stock zip from nvidia. It includes the bootloader in the stuff to flash. You just download the zip and run the .bat file as administor after you have put the shield into bootloader mode. Also was twrp able to mount partitions when youbjad lollipop installed because the partition scheme did npt change across versions.
Shadicbypass said:
True well try flashing back to stock using the full stock zip from nvidia. It includes the bootloader in the stuff to flash. You just download the zip and run the .bat file as administor after you have put the shield into bootloader mode. Also was twrp able to mount partitions when youbjad lollipop installed because the partition scheme did npt change across versions.
Click to expand...
Click to collapse
alright will try explain somehow ....
two day ago i downloaded Vulcan developer zip (productionBL-droid-signed-foster_e_hdd-full_ota-41937_664.8257.20160212074447) and installed through twrp ......
1 job done - console boots in v6.0 without root and custom recovery, so i decided i need root....
2 adb sideload supersu.zip (native recovery was been broken)
3. trying twrp - couldn't cant mount cant see (same as now)
4. decided downgraded back to 2.1 through fastboot (nv-recovery-image-shield-atv-pro-upgrade2_1) image from nvidia site
5 after long process console reboot and stuck on NVIDA green logo - taking out power cord and back - problem sorted console boots and first screen shows up where you need choose which controller or remote you need pair....
6. ............and here comes interesting part ...............remote and controller didn't give a life sings at all (only background klicking sound) - just first screen freeze up --- i decided need do again reinstall 2.1 and started process....
7. after long waiting (around two hours) (actually i didn't wait --- left house and return after 5-6h) ---- controller/remote start work....
8. bypass selecting remote screen ................and again interesting part..........choosing wifi network with phenomenal "long delay" with several restarting and finally i approach google account screen and same story there WITH LONG DELAY WITH SEVERAL RESTART i finally boot 2.1
x. and strangest here after this all drama console works without delays or kind of glitch/lags starts and restarts ----- then i saw 11gb instead of 500gb and i did factory reset from settings menu ----and whattt......same "long song agin"--- pairing, WiFi, google account many restarts and here we go 500gb is back
9 (and i decided i need Vulcan back faastboot boot recovery.zip and install vulcan.zip (note: twrp under 2.1 worked fine no hassle without problem) but still didn't worked native recovery (showed me "broken or no command....android man horizontal position with red triangle" something like that)
10 now i have installed Vulcan back and working OK but twrp not
p.s. ill better wait till nvida will publish v3.0 whole os on website and will try fresh reinstall of whole os a. i kind of don't wanna stuck again hours. b. i already did this. c. and i still thinking this is bootloader which is not down gradable (like it is for some phones/devices) coz when i was under 2.1 i could easily do this
http://forum.xda-developers.com/shield-tv/help/hardware-bootloader-access-easy-t3317627
but before Vulcan installing noway u could do that under 2.1
( have look in screenshot i still have some kind of glitch under Vulcan two identical hdd )
and another one post scrip tum : all this mysterious things (reanimating back to life) it took me nonstop two day ------------ whatever--- at least i can watch YouTube and kodi
visitor29 said:
alright will try explain somehow ....
two day ago i downloaded Vulcan developer zip (productionBL-droid-signed-foster_e_hdd-full_ota-41937_664.8257.20160212074447) and installed through twrp ......
1 job done - console boots in v6.0 without root and custom recovery, so i decided i need root....
2 adb sideload supersu.zip (native recovery was been broken)
3. trying twrp - couldn't cant mount cant see (same as now)
4. decided downgraded back to 2.1 through fastboot (nv-recovery-image-shield-atv-pro-upgrade2_1) image from nvidia site
5 after long process console reboot and stuck on NVIDA green logo - taking out power cord and back - problem sorted console boots and first screen shows up where you need choose which controller or remote you need pair....
6. ............and here comes interesting part ...............remote and controller didn't give a life sings at all (only background klicking sound) - just first screen freeze up --- i decided need do again reinstall 2.1 and started process....
7. after long waiting (around two hours) (actually i didn't wait --- left house and return after 5-6h) ---- controller/remote start work....
8. bypass selecting remote screen ................and again interesting part..........choosing wifi network with phenomenal "long delay" with several restarting and finally i approach google account screen and same story there WITH LONG DELAY WITH SEVERAL RESTART i finally boot 2.1
x. and strangest here after this all drama console works without delays or kind of glitch/lags starts and restarts ----- then i saw 11gb instead of 500gb and i did factory reset from settings menu ----and whattt......same "long song agin"--- pairing, WiFi, google account many restarts and here we go 500gb is back
9 (and i decided i need Vulcan back faastboot boot recovery.zip and install vulcan.zip (note: twrp under 2.1 worked fine no hassle without problem) but still didn't worked native recovery (showed me "broken or no command....android man horizontal position with red triangle" something like that)
10 now i have installed Vulcan back and working OK but twrp not
p.s. ill better wait till nvida will publish v3.0 whole os on website and will try fresh reinstall of whole os a. i kind of don't wanna stuck again hours. b. i already did this. c. and i still thinking this is bootloader which is not down gradable (like it is for some phones/devices) coz when i was under 2.1 i could easily do this
http://forum.xda-developers.com/shield-tv/help/hardware-bootloader-access-easy-t3317627
but before Vulcan installing noway u could do that under 2.1
( have look in screenshot i still have some kind of glitch under Vulcan two identical hdd )
and another one post scrip tum : all this mysterious things (reanimating back to life) it took me nonstop two day ------------ whatever--- at least i can watch YouTube and kodi
Click to expand...
Click to collapse
Ok for anybody browsing this thread right now the 500gb version shield tv seems to be having issues mounting partition now. The 16gb should work correctly though
That is correct, The 500gb model doesn't like twrp after marshmellow ota. It can't see partitions anymore. If you try downgrading also, you get those freezes in the welcome setup that visitor29 mentioned. So ota on pro models right now = no root.
We (500gb unit users) need wait official release of marshmallow os img from nvidia and some goodies from developer steel01, but meanwhile who don't wanna loose root and Twrp I recommend better stay on 2.1
Izsūtīts no manas Nokia 3310 используя бесплатную xda app
to late ,but after all the system is pretty responsive, the new feature of the gamepad to navigate to the web browser,wel before rooted no problems at all and my latest antutu was 140000
Official updates for our M2 tablet,
although having installed another
recovery and root access, already.
- Disclaimer
Well, whatever you do with this guide is all up to you and in your own responsibility. You
should have basic knowledge about ADB and flashing, which is explained in many other
threads here on our beloved XDA.
- Issue
When you used this guide (https://goo.gl/r04XjJ) or any other one to give your M2 tablet
another recovery and therefore root rights, you have now the problem, that EMUI will show
you new updates, but you are not able to install them, because of the missing stock recovery,
of course.
- Solution
So, you have to flash back the original stock recovery, getting the official update and then you
can flash back your TWRP recovery.
- Guide
1. You should start your EMUI update programme/app and start the download of your update.
When it is finished, it will ask you to reboot into recovery and install automatically. As you have
no stock recovery I strongly advise not to do so. Usually nothing happens, but there is one case
reported, where it somehow ****ed up the guy's tablet. I am not sure, if that story is true, but
well, I have warned you.
2. Just turn your tablet off after you have finished downloading the update (it will wait now in
the directory "HwOUC" on your tablet and it is called "update.zip" - just let it sleep there).
3. Start the tablet in the fastboot recovery mode, meaning plugging in the USB cable (connected
to the computer) and hold the buttons "power" and "volume down", immediately, until a white
screen appears, which is the fastboot recovery screen. It should tell you, it has the bootloader
unlocked, which is normal, because you did that earlier on with any of the other guides (see above).
4. Copy the downloaded stock recovery of your choice to your ADB directory. In my case this is
"c:\ADB", but this depends on your way of installation.
5. Now open up a command line in Windows (with Windows key + R) and type "cmd") and go to
your ADB directory, using commands like "cd .." and "cd adb".
6. When having arrived in the ADB directory, you have to enter these commands one after the other:
fastboot flash recovery stock-recovery.img
fastboot reboot
If you renamed the recovery file, then you have to consider that in the command, of course.
7. The device will reboot directly into the recovery, because it "sees" the update in the update
directory et voila ... you are getting your awaited update. Sometimes it will boot not into the EMUI
recovery directly, but then you hast have to start the tablet normally, open up the EMUI app and
download the update again and do the OTA update properly with the reboot it tells you to do,
when it is finished.
8. Okay, now you have received your update, but if you want to have back your TWRP, you just
have to turn off your tablet and boot into the fastboot recovery again (see 3.).
9. You have to copy your TWRP recovery to your ADB directory (in my case "twrp.img" in "c:\ADB").
10. Now open up a command line in Windows (with Windows key + R and type "cmd") and go to
your ADB directory, using commands like "cd .." and "cd adb".
11. When having arrived in the ADB directory, you have to enter these commands one after the other:
fastboot flash recovery twrp.img
fastboot reboot
12. The tablet will reboot and you are back to a working lovely updated M2 tablet.
- Root:
If you want to have root rights, I strongly recommend flashing Magisk within TWRP, because it is
just a nice and more modern approach to having root. It works very fine on my M2 10 tablet. The
link for the files and guide is here:
https://goo.gl/UXYk4d
It is very easy. You just flash Magisk 12 in TWRP and then install the Magisk Manager app from the
Play store.
- Files for M2-802L and M2-A01L:
https://ufile.io/0df492 (all four recoveries here)
https://files.fm/u/aajdmadr (all four recoveries here)
https://www.file-upload.net/download-12438839/HuaweiM2recoveries.rar.html (all four recoveries here)
Have fun with your updated tablet. ... and I am happy, if I could help you - any coffee appreciated.
...
..
.
+++ saved +++
Additionally, I can offer you the updates B007 and B010 (most current one) for the
M2 10 LTE (M2-A01L), because I managed to save them/back them up. These are the
European versions of B007 and B010 with all language files, I believe.
So, who is having a M2-A01L and is still sitting on B006 or B007, might try a manual
update, which is as easy as pie. It is just one simple step.
Also, an update from B009 to B010 might be possible.
Of course, I cannot give any guarantee for Huawei's update files, which you will
understand, I guess.
what android version ?? M2-801L, thanks
Eagle-no1 said:
what android version ?? M2-801L, thanks
Click to expand...
Click to collapse
M2-A01L, not M2-801L. For all 8 models you find your ROMs here:
https://forum.xda-developers.com/me...om-8-0-models-stock-marshmallow-roms-t3535466
or
https://forum.xda-developers.com/me...-b207-android-6-0-marshmallow-emui-4-t3533572
or
https://forum.xda-developers.com/mediapad-m2/development/rom-stock-rooted-xposed-t3519031
xsycox said:
Additionally, I can offer you the updates B007 and B010 (most current one) for the
M2 10 LTE (M2-A01L), because I managed to save them/back them up. These are the
European versions of B007 and B010 with all language files, I believe.
So, who is having a M2-A01L and is still sitting on B006 or B007, might try a manual
update, which is as easy as pie. It is just one simple step.
Also, an update from B009 to B010 might be possible.
Of course, I cannot give any guarantee for Huawei's update files, which you will
understand, I guess.
Click to expand...
Click to collapse
I'd greatly appreciate it, if you could share. Got the problem that my A-01L got corrupted. The only official ROM I've been able to find has been B005 what is somewhat old. As it seems to be a pre-release version the tablet doesn't find any updates. Thus I'd like to try to upgrade to B007, or even B010 manually when I'm back home. Currently I'm on a weekend trip as friends of mine are going to marry tomorrow. Thus I'd be able to download them on Sunday evening if you'd provide them.
Regards
Sent from my htc_pmeuhl using XDA Labs
Tried Magisk but can't pass Safetinet test even with Magisk hide enable...
is it working for you?
5m4r7ph0n36uru said:
I'd greatly appreciate it, if you could share. Got the problem that my A-01L got corrupted. The only official ROM I've been able to find has been B005 what is somewhat old. As it seems to be a pre-release version the tablet doesn't find any updates. Thus I'd like to try to upgrade to B007, or even B010 manually when I'm back home. Currently I'm on a weekend trip as friends of mine are going to marry tomorrow. Thus I'd be able to download them on Sunday evening if you'd provide them.
Regards
Click to expand...
Click to collapse
https://forum.xda-developers.com/me...om-official-manual-updates-m2-tablet-t3595211
zedoc said:
Tried Magisk but can't pass Safetinet test even with Magisk hide enable...
is it working for you?
Click to expand...
Click to collapse
I have Magisk running on several devices, including the M2-A01L, but I must admit,
I never got the Safetynet passed, even with Magisk hide enabled.
I just use it as systemless root and with systemless Xposed, which is great.
zedoc said:
Tried Magisk but can't pass Safetinet test even with Magisk hide enable...
is it working for you?
Click to expand...
Click to collapse
xsycox said:
I have Magisk running on several devices, including the M2-A01L, but I must admit,
I never got the Safetynet passed, even with Magisk hide enabled.
I just use it as systemless root and with systemless Xposed, which is great.
Click to expand...
Click to collapse
After enabling magisk hide, you have to reboot your device. Got the 801L working with that and safetynet passes.
Noob Question on recovery files
Hi, and thanks for a incredible well detailed guide for updating. Came here because I haven't found any good recovery files for the wifi model. I've been trying (unsuccessfully may I add...) to install TWRP and magisk. So, my question is: can the recovery files for the LTE model be used on the wifi model? (M2-A01w). Thanks for your help!
myst771 said:
Hi, and thanks for a incredible well detailed guide for updating. Came here because I haven't found any good recovery files for the wifi model. I've been trying (unsuccessfully may I add...) to install TWRP and magisk. So, my question is: can the recovery files for the LTE model be used on the wifi model? (M2-A01w). Thanks for your help!
Click to expand...
Click to collapse
Sorry, I have been on vacation.
To be honest, I am not sure, if the recovery for M2-A01L works on M2-A01w, too, but you can just try it.
I think, there should not be that big a problem, because the recovery has nothing to do with Wi-Fi or LTE, at all. It is just important, that partition tables and drives are accessible the same way and well, I really think, there is not much difference in between the M2 10 models.
From M2 8 to 10 there is a difference, of course. That is why I uploaded both recoveries (for 802L and A01L).
Just use that guide (https://forum.xda-developers.com/mediapad-m2/how-to/guide-unlock-bootlader-twrp-root-huawei-t3322340) without the SuperSU flashing and my recoveries in this guide.
Hi guys,
I need help, I have a M2 10 LTE previously modded with TWRP for root and I've just followed this guide to update from 007 to 010 version.
So I've flashed the stock-recovery, rebooted the tablet, requested the firmware update (I don't know if I got any error during the process) and the tablet has rebooted. Now it's stuck on HUAWEI logo..
I use this tablet for work so I really need to recover it asap.
Please help.
Shocker580 said:
Hi guys,
I need help, I have a M2 10 LTE previously modded with TWRP for root and I've just followed this guide to update from 007 to 010 version.
So I've flashed the stock-recovery, rebooted the tablet, requested the firmware update (I don't know if I got any error during the process) and the tablet has rebooted. Now it's stuck on HUAWEI logo..
I use this tablet for work so I really need to recover it asap.
Please help.
Click to expand...
Click to collapse
Could upload the B010 fullstock ROM/firmware. Thus you could reset the device to the latest stock ROM using the /dload method and gain a factory rested Huawei, as if out of the box. Just quote me if you'd want me to upload and I'll share the link asap. Took that way myself as soon as I found the full stock ROM.
Sent from my htc_ocnuhl using XDA Labs
thanx
Dear xsycox
I have an issue where I updated my W version tablet to L version accidentally and I am having issue getting it back..
I am currently trying to get some help in this thread: https://forum.xda-developers.com/me...-m2-installed-wrong-update-zip-t3563105/page2
Can you please help me out? do you have any idea what ican do to get back to W version?
Thanks!
Now the wait for the developer image
And mine doesn't boot anymore... nice job !
Jems_ said:
And mine doesn't boot anymore... nice job !
Click to expand...
Click to collapse
Care to be more specific?
it get the update , restart several time for it and when it was optimizing reboot and now i'm stuck with the bot down with "no command" under.
Jems_ said:
it get the update , restart several time for it and when it was optimizing reboot and now i'm stuck with the bot down with "no command" under.
Click to expand...
Click to collapse
need more specifics are you rooted? which shield? how were you updating it?
No root just the official 6.1. this is the shield tv pro 2017. the update was the 6.2. I can acces the official recovery. i tried a wipe cache but no luck, now i'm trying to do a factory reset.
Jems_ said:
No root just the official 6.1. this is the shield tv pro 2017. the update was the 6.2. I can acces the official recovery. i tried a wipe cache but no luck, now i'm trying to do a factory reset.
Click to expand...
Click to collapse
Ok well I am on 6.1 developer and I didnt see the 6.2 available until today, I already downloaded and installed the 6.2 on my non rooted 2017 16gb with no problem however for my rooted Shield Pro I will wait for the developer image
okay, when i found no other have same trouble i supposed it was no luck for me... thx for your answer.
jionny said:
Now the wait for the developer image
Click to expand...
Click to collapse
Here we go again!
Please ring a bell once you see or get the full dev firmwares.
sammarbella said:
Here we go again!
Please ring a bell once you see or get the full dev firmwares.
Click to expand...
Click to collapse
sure, will post it as soon as I get my hands on it
Gotta thank Nvidia for the quick updates.
Seriously The Shield TV 2015 was a great investment since I got it on May 2016. I just added the newer controller and it's running great.
Just waiting for Oreo.
Developer image now posted on the Nvidia site.
https://developer.nvidia.com/shield-developer-os-images
tha kid2012 said:
Developer image now posted on the Nvidia site.
https://developer.nvidia.com/shield-developer-os-images
Click to expand...
Click to collapse
Thanks for the heads up!
At last they fixed the user and pass system to download the dev images.
I uploaded the dev images to MEGA, direct links:
- NVIDIA SHIELD TV ANDROID TV 2015 (16GB) Developer Only OS Image 6.2.0 : nv-recovery-image-shield-atv-6.2.0-dev_rooted.zip
- NVIDIA SHIELD TV ANDROID TV 2017 (16 GB) Developer Only OS Image 6.2.0: nv-recovery-image-shield-atv-2017-6.2.0-dev_rooted.zip
- NVIDIA SHIELD TV ANDROID TV Pro (500 GB) Developer Only OS Image 6.2.0: nv-recovery-image-shield-atv-pro-6.2.0-dev_rooted.zip
Use them under your own exclusive responsibility. Flashing the wrong file to a wrong device or using a bad methodology could brick it.
sammarbella said:
Thanks for the heads up!
At last they fixed the user and pass system to download the dev images.
I uploaded the dev images to MEGA, direct links:
- NVIDIA SHIELD TV ANDROID TV 2015 (16GB) Developer Only OS Image 6.2.0 : nv-recovery-image-shield-atv-6.2.0-dev_rooted.zip
- NVIDIA SHIELD TV ANDROID TV 2017 (16 GB) Developer Only OS Image 6.2.0: nv-recovery-image-shield-atv-2017-6.2.0-dev_rooted.zip
- NVIDIA SHIELD TV ANDROID TV Pro (500 GB) Developer Only OS Image 6.2.0: nv-recovery-image-shield-atv-pro-6.2.0-dev_rooted.zip
Use them under your own exclusive responsibility. Flashing the wrong file to a wrong device or using a bad methodology could brick it.
Click to expand...
Click to collapse
No problem at all. Have you upgraded yet and if you did which method did you use? I used FlashFire to upgrade from 5.2 to 6.1. and that worked great so I assume this time will be the same. Assuming you used FlashFire, after hitting the +, flash firmware package and selecting the 6.2 upgrade did you leave all 4 of the boxes in the Partitions window that pops up afterwards (Boot, Recovery, System, Vender) checked or do you have to uncheck one of them before flashing it?
tha kid2012 said:
No problem at all. Have you upgraded yet and if you did which method did you use? I used FlashFire to upgrade from 5.2 to 6.1. and that worked great so I assume this time will be the same. Assuming you used FlashFire, after hitting the +, flash firmware package and selecting the 6.2 upgrade did you leave all 4 of the boxes in the Partitions window that pops up afterwards (Boot, Recovery, System, Vender) checked or do you have to uncheck one of them before flashing it?
Click to expand...
Click to collapse
I'll update later.
Flashfire latest version like the last times, default options for firmware flash (all option but data).
Just flashed successfully with zero problems nv recovery image shield atv pro 6.2.0 here is the file downloaded directly from Nvidia's website I noticed this time data was not even listed none the less flashed flawlessly in about 3-5 min
https://mega.nz/#!QPYQARhS!OJ2LshkGoVH47d6tChlC1vVF7ijPtNST-HNTcm9dIOQ
sammarbella said:
Thanks for the heads up!
At last they fixed the user and pass system to download the dev images.
I uploaded the dev images to MEGA, direct links:
- NVIDIA SHIELD TV ANDROID TV 2015 (16GB) Developer Only OS Image 6.2.0 : nv-recovery-image-shield-atv-6.2.0-dev_rooted.zip
- NVIDIA SHIELD TV ANDROID TV 2017 (16 GB) Developer Only OS Image 6.2.0: nv-recovery-image-shield-atv-2017-6.2.0-dev_rooted.zip
- NVIDIA SHIELD TV ANDROID TV Pro (500 GB) Developer Only OS Image 6.2.0: nv-recovery-image-shield-atv-pro-6.2.0-dev_rooted.zip
Use them under your own exclusive responsibility. Flashing the wrong file to a wrong device or using a bad methodology could brick it.
Click to expand...
Click to collapse
lol you beat me to it, didnt see your post until after I posted mine
jionny said:
Just flashed successfully with zero problems nv recovery image shield atv pro 6.2.0 here is the file downloaded directly from Nvidia's website I noticed this time data was not even listed none the less flashed flawlessly in about 3-5 min
https://mega.nz/#!QPYQARhS!OJ2LshkGoVH47d6tChlC1vVF7ijPtNST-HNTcm9dIOQ
Click to expand...
Click to collapse
Yeah I flashed earlier without any problems as well. Just left everything checked and FireFlash took care of the rest like a champ.
tha kid2012 said:
Yeah I flashed earlier without any problems as well. Just left everything checked and FireFlash took care of the rest like a champ.
Click to expand...
Click to collapse
Okay, so you're rooted and flashed it with the default settings using Flashfire and not data? I tried that last time and something went wrong. I'm rooted, have busybox, adblock, once had TWRP a few updates ago, converted Plex to user app. could any of these steps had caused any problems?
UltraMagnus0001 said:
Okay, so you're rooted and flashed it with the default settings using Flashfire and not data? I tried that last time and something went wrong. I'm rooted, have busybox, adblock, once had TWRP a few updates ago, converted Plex to user app. could any of these steps had caused any problems?
Click to expand...
Click to collapse
Yes I'm rooted on a 2015 16gb Shield and yes I flashed with the default settings, didn't change anything at all. I left everything checked then flashed. Their were only 4 things that popped up in a small window called Partition after I clicked the plus sign, clicked " flash firmware package" then selected the ota zip and they were "Boot, Recovery, System and Vender", their wasn't even a data box in the list. Also I used Fireflash version 0.73, I believe that's the latest version needed to flash.
Hey guys.
Yesterday, I swapped out my Oneplus 6T, and got a new Pixel 3 XL 64GB.
I managed to have no issues unlocking the bootloader, and I do have relative familiarity with adb tools.
I'm running a Dell XPS 13 which has a USB Type C port which I have been using for cmd through Windows 10 in the beginning much to my own success.
After unlocking the bootloader, I had opt'd in for the ota update for Android Q and downloaded without hesitation.
I booted into TWRP, and when attempting to flash through the USB OTG cable it failed. I do not recall, and didn't think to use the webcam on my PC at the time to screenshot the errors.
I can get into the bootloader, however now when I run adb devices nothing appears.
If I boot a TWRP img, go to advanced > adb sideload and run a session. I can then proceed to run adb devices and successfully it reports back my serial number of the device. ( can provide screenshots of this if it's of any assistance )
However, no way have I been able to flash the Factory images, from as early as September 2018 to the latest for Android 9.0, nor have I have been able to reflash the Android Q factory images using cmd and the flash-all.bat
I've also followed this guide step by step uninstalling every ADB and Android related driver prior to installing the "lastest google drivers" https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849/page6
Sending sparse 'vendor_a' 2/2 (193888 KB) FAILED (Error reading sparse file) is where it hangs, and I'm absolutely at a stand still I wouldn't be posting if I hadn't searched and tried everything I could find any way related to it.
Also seems to be missing multiple sig files when running the flash-all.
If anyone can be of assistance it would be greatly appreciated I do not want to have to RMA to Google.
Thanks guys!
You can not adb sideload an ota in TWRP. It has to be the factory recovery.
When you are in the bootloader you need to do fastboot devices to see your device.
Did you get Q running? If you did I would download the factory image for it and edit the flash-all.bat to remove the -w.
Also make sure you have the latest platform-tools. I think they got updated when Q came out.
I've never had a problem but I know a lot of people have problems with C to C cables. May want to try an A to C cable if you can.
hatdrc said:
You can not adb sideload an ota in TWRP. It has to be the factory recovery.
When you are in the bootloader you need to do fastboot devices to see your device.
Did you get Q running? If you did I would download the factory image for it and edit the flash-all.bat to remove the -w.
Also make sure you have the latest platform-tools. I think they got updated when Q came out.
I've never had a problem but I know a lot of people have problems with C to C cables. May want to try an A to C cable if you can.
Click to expand...
Click to collapse
Sadly, I can't get to a USB A to C cable for 6 more days.
I did manage to get to Q, and I don't know what rushed me to thinking I could be flashing twrp on the beta.
I have been using factory images, I haven't sideloaded with adb, as I can't quite seem to figure out the flashing process for TWRP. Is there a method you could recommend we try?
I have the latest tools, and I'm 99.9% positive in one of the 20+ flashes I tried Today of various factory images, flashing the last factory with Q did not solve the trick with or without the -w.
If you are trying to flash from within TWRP, make sure everything is properly mounted.
Sent from my Pixel 3 XL
I think your using an old android Windows platform tools.
The newest version is r28.0.2, that should fix your problem.
Also in android Q with the pixel 3 xl, you can't flash anything with TWRP, the storage is not mounted.
Eudeferrer said:
If you are trying to flash from within TWRP, make sure everything is properly mounted.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
As the other user has mentioned, I may be at a loss at being able to flash with TWRP after installing Q.
Gordietm said:
I think your using an old android Windows platform tools.
The newest version is r28.0.2, that should fix your problem.
Also in android Q with the pixel 3 xl, you can't flash anything with TWRP, the storage is not mounted.
Click to expand...
Click to collapse
Could you give me a detailed step by step, perhaps with the url's for the drivers & SDK tools.
I've used the links provided in the Soft Brick guide, and got the drivers direct from google themselves.
Although when I currently plug in my phone, it does install "Lemobile Android Drivers", the Google Drivers remove this but appear to be older drivers?
Download from here the latest platform tools, then flash all the factory image.
https://developer.android.com/studio/releases/platform-tools
Eudeferrer said:
If you are trying to flash from within TWRP, make sure everything is properly mounted.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Gordietm said:
Download from here the latest platform tools, then flash all the factory image.
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Okay will do, please confirm if this is correct.
Extra Android platform-tools, and factory image to the same folder, then extract the zip file found within the folder itself with the zip found from the Factory Image
I erase system a & b, and boot a & b
Flash-All should work start to finish right?
What are the odd's I'm going to be stuck with a RMA?
I'm sure I've exhausted myself trying this exact process so many times yesterday.
Download platform tools, vr28.0.2
Extract it and put the contents in a folder you'll remember
Download the factory image and extract it.
Put the bootloader, radio, system image zip and flash all.bat files in the same folder as the platform tools.
Connect your phone and put in bootloader mode.
Double click flash all.
Gordietm said:
Download platform tools, vr28.0.2
Extract it and put the contents in a folder you'll remember
Download the factory image and extract it.
Put the bootloader, radio, system image zip and flash all.bat files in the same folder as the platform tools.
Connect your phone and put in bootloader mode.
Double click flash all.
Click to expand...
Click to collapse
This sounds identical to what I've be doing, which has been causing the vendor_a issue, but I will give it another run for you shortly here. Just woke up, and rather be fully awake before I go tackling this.
If you can think of any other method, or even an explanation why the vendor img doesn't seem to work that would be awesome.
Also, there is threads I found through google here on XDA with users have a similar issue hanging at vendor, but not due to the same mistake. I'll find you the URL's shortly here.
It's because you were using r28.0.1 before, download r28.0.2
Gordietm said:
Download platform tools, vr28.0.2
Extract it and put the contents in a folder you'll remember
Download the factory image and extract it.
Put the bootloader, radio, system image zip and flash all.bat files in the same folder as the platform tools.
Connect your phone and put in bootloader mode.
Double click flash all.
Click to expand...
Click to collapse
Gordietm said:
It's because you were using r28.0.1 before, download r28.0.2
Click to expand...
Click to collapse
I've been using r28.0.02 just confirmed by looking at everything I had downloaded for trying to fix this yesterday :/
Ok, go back and flash the march android p factory image. Let it boot up and setup. Enroll the q beta program and update to q with your phone. Try that.
Gordietm said:
Ok, go back and flash the march android p factory image. Let it boot up and setup. Enroll the q beta program and update to q with your phone. Try that.
Click to expand...
Click to collapse
Was on the newest 9.0, updated through Q with the opt in, boot into twrp, flashed it, broke the phone ever since. That's the simplified issue, following the soft brick guide with updated tools & drivers using C to C cable no factory image has worked. All breaking at different points, closest an image got was the newest 9.0 failing at the Vendor img,
Gordietm said:
Ok, go back and flash the march android p factory image. Let it boot up and setup. Enroll the q beta program and update to q with your phone. Try that.
Click to expand...
Click to collapse
I have access to another phone here, and can make a video of what I'm exactly doing?
Would this be of any use to troubleshoot, I really don't want to end up on the path to an RMA.
At this point, you're probably best to talk to someone else who has more experience at this than I do.
Good luck!
Gordietm said:
Ok, go back and flash the march android p factory image. Let it boot up and setup. Enroll the q beta program and update to q with your phone. Try that.
Click to expand...
Click to collapse
Gordietm said:
At this point, you're probably best to talk to someone else who has more experience at this than I do.
Good luck!
Click to expand...
Click to collapse
Haha, well that's def not Google either, they straight up said RMA it.
Thanks for trying bro.
XZeeWhy said:
Haha, well that's def not Google either, they straight up said RMA it.
Thanks for trying bro.
Click to expand...
Click to collapse
The only other thing I can think of is wither the cable or the usb-c port on the computer. You said you can't get to an A to C cable but do you have another computer you could use?
XZeeWhy said:
Was on the newest 9.0, updated through Q with the opt in, boot into twrp, flashed it, broke the phone ever since. That's the simplified issue, following the soft brick guide with updated tools & drivers using C to C cable no factory image has worked. All breaking at different points, closest an image got was the newest 9.0 failing at the Vendor img,
Click to expand...
Click to collapse
After failing on the Vendor image, you can sideload the OTA and that should get you back up and running......for some strange reason I always seem to fail there and sideload the OTA at that point has ALWAYS fixed me.
GL!!
hatdrc said:
The only other thing I can think of is wither the cable or the usb-c port on the computer. You said you can't get to an A to C cable but do you have another computer you could use?
Click to expand...
Click to collapse
There is another PC here, but it doesn't have a Type C port, and I don't have an adapter on hand either.
Certainly willing to give Windows a clean install or do a live boot or install of linux to see if a fresh install or another operating system may help resolve it.
So stock factory images can not be flashed via TWRP?
It does seem to change various images on the device when rebooting to bootloader after using Flash All so I feel like it's getting quite a large amount of the partial install.
If I have boot loader & TWRP, I mean there has got to be a way right?