Develop Bugs

[Q] help! kindle fire bricked

ok here is how it went.... i had installed cm 10 android 4.1 rom and also flashed change_to_nexus.zip. While flashing, i chose the wrong rom to flash which was my backup for stock software for kindle fire. i then installed my back up cm 10 rom. i later found out that i had deleted twrp and fff when i had flashed my stock software then cm 10... after a week of trying to find out how to get trwp.. no results.. i got frustrated and started deleting random files and one was the systems file. (dont ask why) thi forced close everything, making me reboot. from there it boots up in regular kindle fire logo, quicky flashes a whit light, then goes to a backlit screen. i drained the battery and stuff like that but no help. i try to reinstall twrp with kfu but it doesnt reconize my kindle fire. i go to devmanager and it shows up as a disk drive, amazon file-cd gadget usb device. i got to devices and printers it shows up as android. nothing reconizes my kindle fire. im only 13... dont want my parents to know cause theyll get mad. any help would be well appriciated.
thanks,
gboy

pics
i attached some pictures

You have a device with a broken system booting with the stock bootloader. You'll need to get it to boot into fastboot mode to fix it. There's a remote chance you'd be able to change bootmodes through adb shell, but I doubt it. The only likely way you will get this fixed is by either utilizing a factory cable or opening up the back of the case. The following will spell out the details...
http://forum.xda-developers.com/showthread.php?t=1668159
If any part of that is confusing to you, you need to read the first 3 posts here...
http://forum.xda-developers.com/showthread.php?t=1552547

hmmm
kinfauns said:
You have a device with a broken system booting with the stock bootloader. You'll need to get it to boot into fastboot mode to fix it. There's a remote chance you'd be able to change bootmodes through adb shell, but I doubt it. The only likely way you will get this fixed is by either utilizing a factory cable or opening up the back of the case. The following will spell out the details...
http://forum.xda-developers.com/showthread.php?t=1668159
If any part of that is confusing to you, you need to read the first 3 posts here...
http://forum.xda-developers.com/showthread.php?t=1552547
Click to expand...
Click to collapse
well i im 13 so i cant get the factory cable without my parents knowing... and i have tried to open the back... its super hard.. can u tell me how to open the back without scratching it.

walkthrough
kinfauns said:
You have a device with a broken system booting with the stock bootloader. You'll need to get it to boot into fastboot mode to fix it. There's a remote chance you'd be able to change bootmodes through adb shell, but I doubt it. The only likely way you will get this fixed is by either utilizing a factory cable or opening up the back of the case. The following will spell out the details...
http://forum.xda-developers.com/showthread.php?t=1668159
If any part of that is confusing to you, you need to read the first 3 posts here...
http://forum.xda-developers.com/showthread.php?t=1552547
Click to expand...
Click to collapse
could u give me a walkthrough how i would use command prompt and adb shell to unbrick.... please make so i can understand. thanks. i'm pretty sure i have everything downloaded that i need. also is there any chance i could fix the driver to one that kfu would reconize?

http://forum.xda-developers.com/showpost.php?p=31141110
Start at post #83 and read on.

?
soupmagnet said:
http://forum.xda-developers.com/showpost.php?p=31141110
Start at post #83 and read on.
Click to expand...
Click to collapse
sorry for my stupidity.. still dont understand what im supposed to be reading from the link you gave me.

Sorry, I keep forgetting Tapatalk is a little different from the webpage.
http://forum.xda-developers.com/showthread.php?t=1869297&page=9

83
soupmagnet said:
http://forum.xda-developers.com/showpost.php?p=31141110
Start at post #83 and read on.
Click to expand...
Click to collapse
when u say 83 and on.. u mean 83-1 or 83 up?

Why would you read from #83 going backwards?
{
"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"
}

soupmagnet said:
Why would you read from #83 going backwards?
Click to expand...
Click to collapse
ok ill do the back cover way.. can u give me info or post how to open the back besides using something sharp... bcause it scratching my kindle

Plastic tools are by far the best even a really stiff guitar pick will work just don't go all the way with it rather take several careful passes around the device...of course you are just removing the back cover http://m.youtube.com/#/watch?v=MGLn1TVAITQ&desktop_uri=/watch?v=MGLn1TVAITQ

firekit
ok so i guess i gotta download it to fix it if im gonna do it the back cover way. instructions on taking the backcover... without scratching...?

yay
yay got it opened... now wht???

try
when i try to download the ubuntu.. it gets corrupted at the end. i also dont know wht to do now with the back cover pryed open.

http://forum.xda-developers.com/showthread.php?t=1869297&page=9
Start at post #83 and read on.

ubuntu keeps getting corrupted on 32 and 64...

There isn't much we can do about that. That's a problem with your computer or your flash drive.

lol.. didnt have enough space on my flash drive... lets try agian...

If your not going this route you should be its all set up
Here try this iso http://db.tt/KDNzyCTP
Instructions:
1. Download this http://www.pendrivelinux.com/ use universal usb installer
2. Download iso
3. Preformat usb in windows
4. Select try unlisted Linux iso from the very bottom of dropdown in universal usb installer
5. Select iso
6. Select usb drive letter
7. Tick format
8. Create
9. Eject safely and remove
10. Shut down computer
11. Insert and power on computer
12. Select boot from usb and use..
different build but thread found here http://forum.xda-developers.com/showthread.php?t=1882565

[Q] Display progressively locks up after time

I have an old Droid Incredible, I was using a rather unstable version of AOKPs ICS ROM until today when I finally found Tiny's CM10 ROM. After fiddling around for a while I have a problem that just won't seem to go away. Everything loads fine, it's functional for a while then after a couple of minutes the system begins to freeze, usually it's the app in the foreground, I can no longer back out or go to the home screen but I can still usually drop the notification bar and change settings using those widgets but after time this too freezes. If I don't turn the screen off before the full freeze takes effect it stays on indefinitely until I pull the battery, if I turn the screen off before the full freeze takes effect and I try to turn it on again the display remains unlit but the soft buttons will turn on and off as expected no matter how many times I press the butt, they also time out as they should. Unfortunately I tried backing down to CM7.2 just to work with something I know is stable, but the effects happened on it as well. I'm guessing hardware issue. Until about 30 minutes ago I had been using Clockwork Recovery to do all of my ROM swapping and now I have TWRP. I dunno if maybe I wasn't wiping enough with Clockwork and this caused the issue to persist to the older Gingerbread install or if I'm **** out of luck and some of my hardware is going back. Maybe I need to flash my radio, I haven't ever done that, it's that same version I have had since I rooted my phone two years ago.
{
"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 4:23 AM
I rebooted into recovery and wiped the cache and dalvik-cache after the most recent reset. So far it's smooth sailing, we'll see how long that lasts. Also battery is reading at 84%

Update 12:35 PM 12.24.12
Well, after running fine all night, installing a few apps and what not I did a nandroid backup and rebooted. Everything seemed fine but Scalado Album froze so I pulled the battery, thought it was just an issue with that app since I've been having some problems with it for a while now. After the reboot I had another system freeze. Can't really pinpoint why it happens sometimes but doesn't happen other times.

Can you try to wait a few minutes for it to reboot on its own? Then you can try to grab a last_kmsg after the next freeze.
Sent from my Galaxy Nexus using Tapatalk 2

Well I may have found a way around the problem but it isn't a true fix. It appear the freezes do not happen if I reboot my Incredible while it's plugged into a computer, wall outlet might work but I haven't tested it yet to make sure.
I'm going out of town for a few days and since I have found a temporary fix (fingers crossed) I'll try to do a little bit more experimenting and see if I can get the SDK and ADB installed to get you some proper logs. I'm a bit new to trouble shooting aside from wiping and doing a fresh install but I'll see what I can manage.
Also, I just wanted to say thank you for your work. Your CM10 ROM is running super smooth and I couldn't live without it!

Zero_FeniX said:
Well I may have found a way around the problem but it isn't a true fix. It appear the freezes do not happen if I reboot my Incredible while it's plugged into a computer, wall outlet might work but I haven't tested it yet to make sure.
I'm going out of town for a few days and since I have found a temporary fix (fingers crossed) I'll try to do a little bit more experimenting and see if I can get the SDK and ADB installed to get you some proper logs. I'm a bit new to trouble shooting aside from wiping and doing a fresh install but I'll see what I can manage.
Also, I just wanted to say thank you for your work. Your CM10 ROM is running super smooth and I couldn't live without it!
Click to expand...
Click to collapse
You don't really need a computer at all to get a logcat; you can get all the log files you need right from the phone. Install a terminal emulator on your phone (Android Terminal Emulator by Jack Palevich is a good one). Open the terminal and type in
Code:
cd sdcard
..and hit enter. This will take you to the root of your sdcard. Then, type in
Code:
logcat > logcat.txt
...and hit enter. This will dump the output of logcat into a text file named 'logcat.txt' on the root of your sdcard. You can either close the terminal to end the capturing of logcat, or you can try to crash your phone and pick up the logcat after it reboots.
Also, as tiny said, if your phone totally freezes it should reboot on its own after a few seconds or maybe a minute or two. If it's a hard reboot (if you see the white htc boot screen), copy off /proc/last_kmsg and post that too. You can get that with CM File Manager if you enable root access in its settings.

Bricked LG G3 - Need help!

Hi guys, I recently decided that i would root my phone and try and install cyanogenmod (new to me) as my phone seemed quite sluggish with LG's own bloatware on it. I followed the steps from LGG3ROOT and everything seemed to work well, and at the last stage when it asked me to then remove my battery and restart the phone... the phone just stayed on the lg page - never logging into the android system.
Ive tried to plug the device into multiple machines and each time the machines have issues with the device and it says the device has issue starting (10).
Im not really sure what else i can do as the phone seems bricked. Any help would be very much appreciated as i need access to the phone and i assume the warranty is now void.
Thanks in advance.

Walshinho said:
Hi guys, I recently decided that i would root my phone and try and install cyanogenmod (new to me) as my phone seemed quite sluggish with LG's own bloatware on it. I followed the steps from LGG3ROOT and everything seemed to work well, and at the last stage when it asked me to then remove my battery and restart the phone... the phone just stayed on the lg page - never logging into the android system.
Ive tried to plug the device into multiple machines and each time the machines have issues with the device and it says the device has issue starting (10).
Im not really sure what else i can do as the phone seems bricked. Any help would be very much appreciated as i need access to the phone and i assume the warranty is now void.
Thanks in advance.
Click to expand...
Click to collapse
can you post
the guide that you used to root
your phone variant
and whether it boots into download mode
what firmware version you were running

the guide i followed was this (exactly) http://highonandroid.com/android-smartphones/how-to-root-lg-g-flex-2-g2-g3-on-lollipop/
i have a UK D855
I can get it to download mode (but cant get to recovery with the power and down buttons)
unsure exactly which firmware, i hadn't played around with the phone until this happened.
when i let the phone get stuck on the lg page the windows pc seems to recognise the device, if i put it in download mode it comes up with the device error that it is there but cannot be run.
Thanks.

You probably have either
1) A bad usb cable
2) Or your drivers arent properly installed
You are plugging it into a USB2.0 port right?

I installed the drivers from the universal LG driver tool from their site, it worked find with the phone (or so it showed) before this issue, i've also tried a different cable and a different machine for it to come up with that same driver problem (10). Ive also tried uninstalling the driver software and reinstalling, is there a way to get rid of all traces of the bad drivers? thanks again for replying

Error Image
{
"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"
}

Working Fine
This is when the device isn't put into download mode and instead is left to try and boot (where it is stuck on the LG 'life's good' page).

Any idea guys? Im having no luck with any info im getting online at the moment and i'm really in need of this phone to work.
Thanks in advance.

Can you expand the "android device" section.
See if it's android adb

sorry, i think i quite understand. Which part should i expand on?
Thanks

In
device manager, look up Android device.

Update
The phone will now only go straight to firmware update and will never go or show the download mode as it has before. This is causing my LG Flash Tool to come up with 'cant change to download mode' and im not sure why or how this has happened.

The phone is now appearing fine on the device list. Its just the last of download mode. Is there a way to force it in cmd?

Please some screenshot again. The one I linked would be fine for adb

I see you can boot on download mode, so you can restore your G3 by applying a kdz firmware with flashtool2014: http://forum.xda-developers.com/showthread.php?t=2785089
On download mode the G3 is recognized only in ports (com&lpt)

What's the Expected Level of Support from Google Support?

TL;DR: Really three questions
What kind of effort can/should we expect from Google Support?
Is there an escalation support path for real troubleshooting?
What's the best course of action to attempt to determine root cause?
The Setup
While driving to work this morning my stock Pixel 2 XL (locked, not rooted etc.) entered a boot loop then settled on this error (image):
Code:
Android Recovery
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device
I couldn't do much since I was driving but I selected 'Try again' a number of times when traffic stopped before giving up.
When I arrived at work I continued fiddling with it for a few hours, select 'Try again', power off, power on, fastboot etc.
Although debugging was enabled prior, could only see a device in fastboot or when in adb sideload mode.
When I attempted to go into recovery mode it would just take me back to the same screen.
I just assumed I'd have to wipe and start over
About 2 hours ago I was getting ready to factory reset/wipe the phone but thought I'd try fidgeting once more like I had been doing all day.
I don't know what I did but it booted to a screen displaying this error:
Code:
No valid operating system could be found.
The device will not boot.
Visit this link on another device
g.co/ABH
{
"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"
}
Then the phone turned off.
I turned it back on, and I don't think I did anything differently, and suddenly it booted normally.
The only unusual thing I saw was a notification stating that Android was finishing up system updates - or something to that effect.
With the phone up, I backed up what little data had not yet been backed up, booted into safe mode then booted back into normal mode.
So far so good...?
My Complaint
I contacted Google support earlier in the day and the experience was just sad.
The person said that I would need to factory reset my phone.
But then quickly said that before doing so I would need to backup my data.
So I asked "How?" and they said "plug it into your machine and you can see it on your computer"
I went along with their script, specifically asking for detailed step by step instructions on what to do, how to do it and what to look for.
When I said it didn't work they said I would have to take it to a repair center first to get it repaired then once fixed I could back it up then perform the factory reset.
*smh*
Later, about 2.5 hours ago now, once the phone came back up, I backed up what little data needed backing up and contacted support a second time.
This time, the person said: "Now, if we need to restart the phone and check if the boot looping is triggered or not. If it does, then we need to do some troubleshooting steps here."
So I naturally asked "What are the troubleshooting steps if it enters into that state again?" but they couldn't provide any.
I just want to know root cause. Since this was an OS boot problem, surely there's a log somewhere that might reveal what happened or at the very least provide a clue. Right?

Pixel 2 XL (rooted) bootlooping to TEAMWIN splash after factory reset

I am helping someone with this phone, so I don't have all the details, but I know the phone was rooted and most likely it was running stock Android 10. It had been working fine until a factory reset (from Android settings I am assuming) was done on it.
1. Now when it turned on, it displays the "Bootloader unlocked" warning:
{
"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"
}
2. After the message, it goes to the Google logo for a second and then to the TEAMWIN splash screen, and it just stays there. I have to long-press the power button to power it off.
3. I can get into the bootloader using the power and volume-down keys, and the "Barcodes", "Restart bootloader" and "Power off" option work, but "Start" and "Recovery mode" just take me back to step 1 and then 2.
So, I cannot get into "Recovery mode". I have also connected the phone to my pc (Ubuntu), but the OS does not detect it, so I cannot use fastboot either.
Any ideas on how to fix this?

If you cant connect to it via fastboot while its in bootloader mode things are grim, thats your best bet at fixing it...
Connect to PC and flash the Android 10 stock ROM by running flash-all.bat while phone is at bootloader
Without editing the flash-all.bat file to remove the -w flashing stock ROM will format user data
Thats it
The state of the phone in the pic does not inspire confidence....
Im starting to think the two things are related....

73sydney said:
If you cant connect to it via fastboot while its in bootloader mode things are grim, thats your best bet at fixing it...
Connect to PC and flash the Android 10 stock ROM by running flash-all.bat while phone is at bootloader
Without editing the flash-all.bat file to remove the -w flashing stock ROM will format user data
Thats it
The state of the phone in the pic does not inspire confidence....
Im starting to think the two things are related....
Click to expand...
Click to collapse
After connecting a working and identical phone to my PC, I found out that the reason my PC didn't detect this phone was that the USB port on phone was dirty and the connector didn't go all the way in.
After I cleaned the USB port I was able to flash the stock ROM to it. I was getting an error mid-way through, so I removed the "-w" as per your advice, tried again and it worked. The phone works now. Thank you 73sydenay!

I would like to mark this thread as solved, but I am not sure how to do that, I don't see an option to edit the title.

droidmart said:
I would like to mark this thread as solved, but I am not sure how to do that, I don't see an option to edit the title.
Click to expand...
Click to collapse
Hi,
You could press edit > advanced and edit your title with:
[SOLVED] Pixel 2 XL (rooted) bootlooping to TEAMWIN splash after factory reset
Cheers...
Sébastien.