Develop Bugs

[Q] Is my Gnex motherboard faulty?

Hi guys,
I can't flash any ROM/Kernel/whatever file via Bootloader/ODIN & Recovery. Worst still I can't access Recovery now.
My Nexus can goto Bootloader or ODIN mode but once i started to push files to it, it will just freeze. Please refer below for photos:
{
"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"
}
BEFORE
AFTER
My Gnex was on the latest Paranoid ROM and Franco kernel.
Timeline:
1. It just went into bootloop when I am just browsing the internet.
2. Went to Recovery to clear cache. (that's my mistake, should have waited longer for my device to boot :crying
3. Still bootloop.
4. Went to recovery to flash stock kernel as I suspect it's kernel fault.
5. Kernel flash failed as it the operation was aborted and restarted. Bootloop again.
6. Done battery pull and went to Recovery to Restore my backup Nandroid.
7. Flashing halfway and it frooze.
8. Can't access Recovery anymore.
9. Tried to restore stock rom using ODIN. Failed at NandWrite as the screen froze as the above image.
10. Tried WugfFresh to restore back to stock rom and failed again as the screen froze.
So guys, can i conclude that my motherboard is the culprit here?
Thanks in advance.

Are you able to get into the bootloader? Have you tried manual fastboot flash of factory images?

ual4720 said:
Are you able to get into the bootloader? Have you tried manual fastboot flash of factory images?
Click to expand...
Click to collapse
Hi,
Yes, I am able to get to bootloader.. the problem is when i start to do fastboot flash the factory images (using WugFresh).. the screen will start to freeze with double image as per my 1st post...
:crying:

d3vils said:
Hi,
Yes, I am able to get to bootloader.. the problem is when i start to do fastboot flash the factory images (using WugFresh).. the screen will start to freeze with double image as per my 1st post...
:crying:
Click to expand...
Click to collapse
Sound like there is a possibility of corrupt nand partition .... though that is usually unlikely unless you are an extreme flashaholic ... but still possible
but the guy above is suggesting use the fastboot commands manually rather than using the toolkit as it sometimes makes a difference
As in manually flash the recovery in the bootloader then see if you can get into recovery, but there are many avenues that you can take to see where you can get with this. There are many places that explain how to do this step by step on the web.
Also you should always try switching usb ports and usb cables as sometimes it will cause issues
I know i used the same usb port with the same usb cable to flash my n7 and gnex multiple time then one day it just stopped working switched the port and cable then it started working again.
But other than that I don't know much about is a possible JTAG but I really doubt that will help at all since the device does does get into bootloader and odin just freezes....

cmaag said:
Sound like there is a possibility of corrupt nand partition .... though that is usually unlikely unless you are an extreme flashaholic ... but still possible
but the guy above is suggesting use the fastboot commands manually rather than using the toolkit as it sometimes makes a difference
As in manually flash the recovery in the bootloader then see if you can get into recovery, but there are many avenues that you can take to see where you can get with this. There are many places that explain how to do this step by step on the web.
Also you should always try switching usb ports and usb cables as sometimes it will cause issues
I know i used the same usb port with the same usb cable to flash my n7 and gnex multiple time then one day it just stopped working switched the port and cable then it started working again.
But other than that I don't know much about is a possible JTAG but I really doubt that will help at all since the device does does get into bootloader and odin just freezes....
Click to expand...
Click to collapse
corrupt nand partition... that's an interesting theory... will explore on the solutions on the manual fastboot commands...
thanks!!

Blank screen after logo (white Kindle orange Fire) Trouble restoring in adb, fastboot

A friend asked me to look at his 8.9 HD. It boots to the Kindle Fire screen, which I believe is stock from what I've researched, and then the screen is blank. I've tried holding power button for 20 seconds, 40 seconds, 120 seconds and always boots to this. Tried charging and turning on ect ect and always the same. I'm on 7 64-bit. When I run the kindle fire usb driver installer I get an error near the end about it not installing correctly (I click allow when it starts and check Trust Amazon). Then I tried Soupkit inside Ubuntu. Somehow I once got it to go into fastboot mode, the only change I've ever seen on this tablet, but can't do it again.
I've rooted/restored HTCs Samsungs LGs Motorolas.....never had this much trouble with a device. I think the main issue is its not on long enough for drivers to install or fastboot to catch it. The one time it did work I believe I ran "fastboot -i 0x1949 getvar product" in Ubuntu and it said waiting for device and then it caught it on reboot. Again, can't replicate this. Also not sure what to do then. Not really looking to root or whatnot, just fix it to stock. If I have to install TWRP or something to do this so be it.
Please help....

Also I've been trying the Kindle Fire First Aide, stuck on waiting for device. I get an error every now and then for the device, jem-pvt-prod-04 no driver found. I've tried 2 or 3 different Kindle Fire HD downloads plus the ones in the First Aide.

Ok finally able to reliably get into Fastboot in Windows. Now I tried the restore option with the First Aide but getting errors and after running it nothing has changed.
{
"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 realize I'm talking to myself but hopefully someone will see I'm trying and not just OMG someone fix this kthxbi. Since I can get into fastboot I tried the SRT tool, which didnt really have a 'restore' option, and nothing changed. I found 8.1.4. recovery, boot, and system IMGs (https://drive.google.com/folderview?id=0B4lZEJI5lYeMNGdXMHI3T3pKM2c&usp=sharing) and pushed them (see pic below). Now I'm stuck booting into the Stock recovery.

Tried First Aide and still stuck in Recovery. I've tried doing it erasing the data/cache and not erasing. Both give me this

Got it finally fixed by flashing TWRP (after hunting down the files) and then using Restore 2 Stock here, https://www.perfectlyandroid.com/forum/showthread.php?t=618

How to flash TWRP for 8.9 HD?
indigoataxia said:
Got it finally fixed by flashing TWRP (after hunting down the files) and then using Restore 2 Stock here,
Click to expand...
Click to collapse
Indigo, can you please point me in the right direction for finding the TWRP recovery files for the 8.9 HD? And what commands did you use to flash them? Something like "fastboot flash recovery recovery-prod.img -i 0x1949" ?
I've been following the same path as you... first tried First Aide, which got me into Fastboot, but won't actually restore to stock. Then tried flashing boot and recovery images found on XDA, but that didn't seem to help things. I think my Kindle is in the same state yours was, so would be really useful to get more detail on how you finally solved it with TWRP and Restore 2 Stock.
Thanks!
Joe

Indigo, never mind. I successfully found, flashed, and ran TWRP on my Kindle 8.9HD. But for some reason when I try to run the Restore 2 Stock program, it "Cannot find a device in TWRP mode". I can actually run Restore 2 Stock while starting the Kindle in fastboot, and then Restore 2 Stock finds the device and kicks it into TWRP mode, but as soon as that happens Restore 2 Stock somehow loses its connection to the Kindle and pops up the "Cannot find a device in TWRP" error message.
So I need to keep troubleshooting.

Screwed up Google Pixel need some help.

So things pretty much went from bad to worse. I downloaded Google's .img file and ran the Universal Android Utility and thought that by running it it would do what it says by putting a fresh image on the phone and relock everything down and I would have to start all over. Nope my phone gave me the middle finger and the Utility turned around and failed 98% on its way through saying you might want to reboot your phone and go back into bootloader mode and try again and that its possible it was the USB. Tried twice, but the 2nd time it left me with a suprise, it rebooted the phone stayed locked on the Google Splash screen forcing me to reboot in to bootloader mode then I noticed it locked the bootloader, and I cannot run the unlock bootloader the classic way or the new VZ one that I used in the first place and when an attempt is made it will say device not found, I am assuming after running the system image from google it turned off USB debugging again. So all my phone can do is go into bootloader mode or if I try to start it up it says "this device is corrupt and cannot be trusted, hit power to to pause boot" and then the phone shuts down. So Flar2 suggested that I create this QA for assistance and said people here would be able to help me out in here. "If you still have the bootloader, you can flash the factory images and it'll be fine". So if anyone can tell me how with instructions on how to specifically flash the factory image and has a link to it I would be most grateful and gladly tip. Google's site explanation on how to do is absolute trash. Its the Verizon Pixel XL
{
"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"
}

Im amusing you unlocked your bootloader already
Did you down load the updated tools from here
http://forum.xda-developers.com/showpost.php?p=69239012&postcount=27
And the fresh factory image from
https://developers.google.com/android/images#marlin
I've seen a few people running into trouble flashing the factory image using the wrong ADB/Fastboot tools . I have not flashed the factory image yet so dont know the exact steps. the page with the image files directions say something about a flash-all script, I think you have to put all the file into the directory with the updated tools

@razor237 The bootloader was unlocked but after running the stock google image, the bootloader locked itself and I am confused as how to even flash anything when the bootloader is locked. The I did download from you second link, thats the image that started all this trouble. I keep getting device not found because I know usb debugging isnt turned on and I have no idea how to get around this.

Thats Odd , so when you boot into the bootloader and read all the text i think is says Device is UNLOCKED does yours say LOCKED?
Do you get the first boot screen saying your device cant be verified press power button to pause boot?
Did you use the other ADB/FastBoot tools ....the minimal tools are not the correct ones for image flash i think

I used the ADB/Fastboot tools you had linked. The bootloader does say LOCKED. If I try to just power on the device it will say "Your device is corrupt. It cant be trusted and may not work properly." So Flar2 said that as long as you can get into fastboot you are fine, but if you try and flash anything at all, everything kicks back saying FAILED because the bootloader is locked. In one way shape or form it says that I need to unlock the OEM. Apparently and I am guessing here, that Devs definitley know a way to push a factory image even when the bootloader is locked, I just dont know how.

So your bootloader is locked , you don't see the little unlock symbol on the Google screen ( or can't you even get this far ? ), if you don't even have an unlocked BL your royally screwed
Seems like your in RMA land now, but more interestingly that whatever ADB tookit you used does not support the new partitions of the new images for pixel this could very well be the root cause of the issue.
Frankly i'd not use any ADB tools to flash an image unless its downloaded via the SDK for that API and device considering this conundrum, but then hindsight is a wonderful thing

I was able to flash the Stock Image on my Pixel last night "Unlocked International Model"
My steps:
Download and install the Minimal ADB and Fastboot
Download the correct Image file from Google "from link above"
Extract the Image Zip file to my Minimal ADB and Fastboot directory
Put my phone into bootloader mode
Ran the "flash-all" command with Minimal ADB and Fastboot
Took like 5min for it to finish
Pretty weird how yours relocked bootloader. Mine didn't

Have you tried sideloading an ota with adb from https://developers.google.com/android/ota ?

Black screen - Bricked

Ok, so this is how it went.
I uninstalled Magisk 18.1 via TWRP using the latest uninstaller zip. Unfortunately, my phone would not boot any more. Not in to the the system, not into recovery.
So I went to fastboot and tried to boot the TWRP image (fastboot boot twrp-3.2.3-0-daisy_zero.img). It loaded TWRP and then in the TWRP recovery, because it was set to boot at slot B, I changed it in TWRP to boot into slot A. After I restarted the phone, there is only the black screen. I can't reset the phone, I can't get in to fastboot, nothing. Basically it is bricked. It won't even show that it is charging.
Can anything be done? I have broken my system before, but always had no problems with restoring it with flashing threw fastboot. But now I can't get to fastboot.
I was using stock rom with Pie v 1.0.4.0.
Really appreciate the help.

zk_eu said:
Ok, so this is how it went.
I uninstalled Magisk 18.1 via TWRP using the latest uninstaller zip. Unfortunately, my phone would not boot any more. Not in to the the system, not into recovery.
So I went to fastboot and tried to boot the TWRP image (fastboot boot twrp-3.2.3-0-daisy_zero.img). It loaded TWRP and then in the TWRP recovery, because it was set to boot at slot B, I changed it in TWRP to boot into slot A. After I restarted the phone, there is only the black screen. I can't reset the phone, I can't get in to fastboot, nothing. Basically it is bricked. It won't even show that it is charging.
Can anything be done? I have broken my system before, but always had no problems with restoring it with flashing threw fastboot. But now I can't get to fastboot.
I was using stock rom with Pie v 1.0.4.0.
Really appreciate the help.
Click to expand...
Click to collapse
That´s really strange... Will windows detect the phone when you connect it?
Maybe you´re in edl-mode. If yes, you could get out of it by pressing pwr for more then 10 seconds.
If that doesn´t help and you will not be alble to do anything (incl. going to fastboot) you can restore you phone by going to edl by usng the test point method. But thant will break your warranty - you have to open the phone...
If you want to do it you need to do the following.
1. Download latest fastboot rom and MiFlash
2. Install MiFlash, unpack fastboot rom and selct extracted folder in MIFlash.
3. Open your phone: https://www.youtube.com/watch?v=PmpHdqRUlDA
4. Remove the metal cover over the mainboard
5. Remove battery
6. short these both pins: https://www.youtube.com/watch?v=mhsRv42rsqI
7. connect your phone to pc (in device manager you should see "qualcomm qdloader 9008"
8. In MiFlash click on refresh (now you should see something with com-port)
9. On the lower right corner you can selct "clean all", "save user data" and "clean all and lock" - if you were on 10.0.3.0 before, you can select "save user data" if not, you have to wipe by selecting "clean all". Now click "flash"
I did this once and needed a few tries... It´s a bit tricky to connect both pins and then the phone to pc - after the 4th try I got it running.
I had the problem of locked bootloader and a not booting phone...

Hi!
Yes, Windows detects the device. I can see the phone in the device manager by the name Qualcomm HS-USB diagnostics 900E (COM10).
If I hold power on and volume up or down, I can hear via Windows sound that it gets reconnected. So there is some life still in it.
The device is also detectable by MiFlash tool. But unfortunately since I can't get into Fastboot, I can't flash it. I've been trying to flash it, but this is where I get (it just stays here no matter how long I leave the device):
{
"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 know about the method you posted. I still have a year and a half warranty on the phone. So I will sent it on repair and see what they will say. Maybe the won't notice and I will be able to keep my warranty.

i am in the same situation right now, after try to update the twrp, what tool you use to open the phone?.

I think you can also use the deepflashcable for the same effect.

Flash protocol/files because of bootloop : soft brick :(

What I've got:
T800 (wifi) updated by mfg. NOT rooted, all is stock (new in 2015 and I've never messed with the OS) and last version was marshmallow 6.0.1 (def marshmallow but version is strictly from memory).
Problem:
Couple of days ago, tab went into endless boot. It would show the android screen then samsung screen then it would load and all looked ok. This would last for maybe 30 seconds then rebooted into the android screen then samsung screen etc. : endless loop.
What I did:
Did some research and booted into recovery mode. Only cleared the cache then rebooted/or shutdown several times. Same looping. Tried cache clear 3-4x with no success. Once I got into the desktop, it lasted ~30 seconds and then booted me out again.
Alright, I bit the bullet and did a factory reset. Well, now it only gives me the android screen and then the samsung screen. Then cycles over again. I cannot get to the desktop anymore, at all.
Found a thread regarding looping but then the threads about upgrading to nougat by @Schischu --> https://forum.xda-developers.com/galaxy-tab-s/development/rom-android-7-nougat-t3449078 then part 2 https://forum.xda-developers.com/galaxy-tab-s/development/rom-t3498956 and then another one by someone else in regards to upgrading past 7.0 (which I'm not ready to do).
The instructions as posted
INSTALLATION INSTRUCTIONS
Cleaning System
This step is only necessary on the initial installation.
Reboot into recovery. Go into wipe menu. Select "Advanced Wipe". Check
Dalvik Cache
System
Cache
Data
and wipe them. Don't reboot just yet.
Install this ROM
Go into Install
Flash aosp-XXX.zip
On initial installation it is necessary to Reboot to Recovery. Don't skip this step!
(E:unknown command [log] messages can be ignored.)
Install Google Apps and SuperSU
Go into Install
Flash GAPPS.zip
Flash SuperSU.zip
Reboot to System
Click to expand...
Click to collapse
I've got a few questions as I am a TOTAL newb at this.
1)I've got the following files:
a) aosp_chagallwifi-userdebug-20161116.zip
b) open_gapps-arm-7.0-nano-20191002.zip
c) SuperSU-v2.82-20170528234214-TEST-1.zip
d)twrp_3.0.3-1_sm-t800_10217.tar
Are these the correct files? Do I need any more?
2)when I start the process, do I need to put the ZIP file on an SD card then insert that in the tab?
OR do I unzip the file and put that on the SD card?
OR can I just leave them in a folder (on PC desktop) and access them from there?
3)do I put ALL those files at the same time on the SD card or are they accessed one at a time?
Because I can get the android/samsung splash screen I assume I've still got the correct (ie 6.0) bootloader in place. Correct?
If thats true, then again (q.1): am I ready to start the process?
I figure I should do this to get nougat rather than going through the same procedure to just re-load marshmallow.
Any thing else I should know or have missed?

First some pessimism: when a factory reset doesn't work, it's very likely to be a hardware problem.
But let's assume flashing a new rom can do the trick.
I haven't played around with this tablet, or even another Samsung device, so I'm no expert either, but I think I can guide you a bit.
You'll have to start by installing a custom recovery like TWRP. The one you've found is very old, I would assume that you can find a newer one.
People talk about using a PC program called Odin for flashing recovery, maybe you can search for that. Or read here:
https://wiki.lineageos.org/devices/chagallwifi/install
where they use an equivalent program called Heimdall.

Thanks for the info and link.
Started to look at odin but not having any experience or sure of the files needed, I thought I'd wait and see who might respond.

Interesting times. Was able to find the correct file for odin to use. Appears to be successful but I don't know.
This screen shot is what I got after trying to install gapps.zip
{
"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"
}
It says chagall BUT that was b4 I was successful with odin. The error message is the same for Gapps flash. Also, same
error message for SUPERSU
The previously posted instruction said to reboot to recovery. I can only do that if I power down then back to recovery. I do have
an option "reboot to bootloader". Is that the same??

I should mention that I tried the AOSP file (first post) and odin wouldn't accept it. Per instructions I found for odin, the file should end .tar.md5 which I did find
T800XXU1CPK2.tar.md5
Both gave me the same error message though.
+++++++++++++++
I can't install twrp on the tab as its not accepting input so I'm installing android studio on my PC and trying that way.

Well, it must be something else. Although I couldnt load the nougat version with odin, I successfully loaded marshmallow ("PASS" in odin).
https://samfrew.com/download/Galaxy__Tab__S__10.5__-WiFi-__/3klk/XAC/T800XXS1CRI5/T800XAC1CRI5/
BUT I still have the endless boot loop. Plugging in the power cord shuts it off/puts into charging mode.
Do you think it's still a hardware issue?

If you've got an SD card installed, try removing that.
But really, you've reached the end of my knowledge, so let's hope someone else chips in.