Develop Bugs

[Q] Emm... brik! White kindle logo no adb, no fastboot...

Hi,
I've wrote some days ago this post
Hi there!! First of all thanks for the explanation! I've try to understand in wich position is my KF.... but nothing...
A little bit of history:
KF HXD 8,9
I've rooted the KF, after that I've install Safestrap Recovery APK and successfully flash/install 2 different rom into 2 different rom slot not in the stock rom(backed up in the device).
Great! I've tested both and chose one running well. I've chose to delete one and give to the one more space... 7GB.
Well after the installation I've reboot the device........ white fix logo (all white) on screen.... after some reboot pushing the power button (I don't how) it show a screen where I can chose restore device or reboot. I've restored the device to the default factory...
Well now I really don't know what can I do. The command adb devices doesn't recognize any device. Fastboot: ./fastboot getvar product is waiting for the device...
p.s. Only one positive thing is when I plug the KF with the usb in my MAC start Android Transfer Tool.
Any help or suggestions are welcome.
Thanks.
sorry for the bad english
Click to expand...
Click to collapse
and they move me to this section....
Well now I really don't know what I have to do. And in wich state is my kf... brick/no brick
Plase can you suggest me the right way?
Now I'm using an ubuntu 12.04 as pc, there are some tool or script that can I run into ubuntu?
Thanks.

You should be able to get it into fastboot.
Make sure the tablet is off then run the command.
fastboot -i 0x1949 getvar product
Then turn it back on

macman005 said:
You should be able to get it into fastboot.
Make sure the tablet is off then run the command.
fastboot -i 0x1949 getvar product
Then turn it back on
Click to expand...
Click to collapse
I've run the fastboot command from the platform-tools folder into the Android sdk and...
still < waiting for device >

I think it might be a driver issue. If you open the driver manager does something flash on the screen when the tablet turns on?

macman005 said:
I think it might be a driver issue. If you open the driver manager does something flash on the screen when the tablet turns on?
Click to expand...
Click to collapse
with the mac it's start Android Transfer tool but it say that it can't find the device, into ubuntu 12.40 nothing.

[Q] Fastboot can't find device

Hi,
I can not see any device when trying to fastboot on my SM-T805 (the LTE version).
Tried both from Linux and Windows, with the Tablet in Fastboot Mode (Power+Vol Down + Home and then Vol Up to enter), fastboot can not find any device attached.
Code:
[email protected]:~# fastboot devices
[email protected]:~#
Adb can find the device without problems
Code:
[email protected]:~# adb devices
List of devices attached
3204c7aa492181ad device
I've also tried rooting the device with ODIN and that went successfully but no change from fastboot perspective happened.

embrax said:
Hi,
I can not see any device when trying to fastboot on my SM-T805 (the LTE version).
Tried both from Linux and Windows, with the Tablet in Fastboot Mode (Power+Vol Down + Home and then Vol Up to enter), fastboot can not find any device attached.
Code:
[email protected]:~# fastboot devices
[email protected]:~#
Adb can find the device without problems
Code:
[email protected]:~# adb devices
List of devices attached
3204c7aa492181ad device
I've also tried rooting the device with ODIN and that went successfully but no change from fastboot perspective happened.
Click to expand...
Click to collapse
Rumor has it that Samsung disables Fastboot support with newer devices when they are switched from factory debug mode to release mode

lorinkundert said:
Rumor has it that Samsung disables Fastboot support with newer devices when they are switched from factory debug mode to release mode
Click to expand...
Click to collapse
Thanks for your feedbak. If this is the case is there any other possible way to load custom files like the ones needed for instslling ubuntu touch?

lorinkundert said:
Rumor has it that Samsung disables Fastboot support with newer devices when they are switched from factory debug mode to release mode
Click to expand...
Click to collapse
Is this just a rumour or really true? Why would they do that?

FearlessSpiff said:
Is this just a rumour or really true? Why would they do that?
Click to expand...
Click to collapse
Samsung does everything possible to make it difficult for developers to do anything, a Samsung made Nexus has fastboot but the others from Samsung do not.

Jade Remix OS ROM for NEXUS 10

Hi all,
i haven't a Nexus 10 but I want to let you know that Jade Remix OS ROM is now available for flashing on the Nexus 10:
Here is the link to download the ROM: https://drive.google.com/open?id=0B6QbFTXmsda3VDhCMUU3OVg1S2s
Here you'll find screenshots and videos: http://www.jide.com/en/remixos - https://www.youtube.com/channel/UC0U64-AHqJfeAnFJ5vQnM8w/feed
Here is the JIDE forum: https://forum.jide.com/index.php?p=/discussion/601/nexus-10-rom-available-here#Head
This is the greatest "fork" Android base ROM!!
P.S.: I don't want anything, just a Thank You
ROM Installation Instructions
Want to try to flash a Remix OS ROM to other android devices? Yes! We will soon put the Remix OS ROM on the Internet for users to download and flash onto their own device. To start, we will provide the guideline and support to flash the Remix OS ROM on Google Nexus 10.
Disclaimer
Flashing Remix OS ROM on Nexus 10 requires strong android knowledge. Flashing this ROM on Nexus 10 will be at your own risk. You will have to bear responsibility for all the resulting consequences. Jide will NOT be responsible for any damage caused.
Further Note:
Unfortunately, as a startup, we lack the resources to support installation Remix OS ROM on other android devices, thus, we will ONLY provide support for the Nexus 10 device. The Nexus 10 is a touchscreen tablet manufactured by Samsung with direct support from Google. It is the second Nexus tablet. Of course, we will look forward to the support of Remix fans to share with the world about their experience on flashing the ROM on other Android devices.
Installation Instructions
The followings are the steps to install Remix OS ROM: Unlocking the device & Installing image files using fastboot
Unlocking the device
1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging on the device.
3. Connect the device to the computer through USB.
4. From a terminal on a computer, type the following to boot the device into fastboot mode:
- adb reboot bootloader
5. Once the device is in fastboot mode, verify your PC sees the device by typing
- fastboot devices
- If you don't see your device serial number, and instead see "", fastboot is not configured properly on your machine. See fastboot documentation for more info.
- If you see "no permissions fastboot", try running fastboot as root.
6. From the same terminal, type the following command to unlock the bootloader:
fastboot oem unlock
7. A disclaimer will display on the device that must be accepted. Use the volume keys to cycle through the options. Pressing the power button should confirm your selection.
8. If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked. You can confirm this is the case if you see an unlocked icon at the bottom of the Google boot screen during reboots.
9. Since the device resets completely, you will need to re-enable USB debugging on the device to continue.
Installing image files using fastboot
1. Make sure your computer has working fastboot and adb.
2. Download images
- you should have a download link from us in the email. The information of the image zip file:
- Images Zip File Name: images_Nexus_10-5.0.2-B2015070105-signed.zip
- md5: bdb08b6a0508dd1088f177a9e19c2875
- sha1: 9d6df824ef8c32af1a3a9d89e5f870133bcdebf6
3. Unzip the downloaded zip file ( images_Nexus_10-5.0.2-B2015070105-signed.zip ) and go to the folder
4. Connect the Nexus 10 to the computer via USB.
5. Make sure the fastboot binary is in your PATH or that you place the recovery image in the same directory as fastboot.
6. Open a terminal on your PC and reboot the device into fastboot mode by typing
adb reboot bootloader
or by using the hardware key combination for your device while it is powered off.
7. Once the device is in fastboot mode, verify your PC sees the device by typing
fastboot devices
- If you don't see your device serial number, and instead see "", fastboot is not configured properly on your machine. See fastboot documentation for more info.
- If you see "no permissions fastboot", make sure your UDEV rules are setup correctly.
8. Clean the existing data by entering the following command:
- fastboot -w
9. Flash images onto your device by entering the following three commands:
- fastboot flash system system.img
- fastboot flash recovery recovery.img
- fastboot flash boot boot.img
10. Once the flash completes successfully, run the following command to reboot the device into recovery to verify the installation.
- fastboot reboot
Some of the external link of this documents will link to CM website. The installation process is referenced by http://wiki.cyanogenmod.org/w/Install_CM_for_manta

You are the man!

Yea that didn't work for me, no recovery on boot to recovery just blank screen. Also stuck on remix boot logo.

Works for me. You have to fastboot -w to wipe your device, then flash at least the system and boot image through fastboot.

I didn't wipe my device ,didn't wanna lose the sdcard content. I simply did a factory reset from twrp. Question, can it be rooted with cfautoroot like normal android 5.0?

its totally a new dev rom! the best out there! Love this rom!

How to add other languages, for example, russian?

So far I'm loving this rom. The only thing is that I wish there was a way to add widgets.

For some reason i can't hear any media volume whether it be youtube videos, music, or netflix. Any ideas on what might be wrong?

For some odd reason Tapatalk doesn't work on this ROM for me.

How do we root? Anyone know?

I've found this YOUTUBE link, but didn't test yet

EddyTeddy01 said:
For some reason i can't hear any media volume whether it be youtube videos, music, or netflix. Any ideas on what might be wrong?
Click to expand...
Click to collapse
I'm having the same problem, did you ever figure this out?

Corvidd said:
I'm having the same problem, did you ever figure this out?
Click to expand...
Click to collapse
Why is this always a problem with N10 roms?
Sent from my Nexus 5 using Tapatalk

I'm trying to get this ROM off my nexus 10, but I don't have ADB connection for some reason. I don't have TWRP recovery anymore either. Anyone have any tips?

blkhrt13 said:
I'm trying to get this ROM off my nexus 10, but I don't have ADB connection for some reason. I don't have TWRP recovery anymore either. Anyone have any tips?
Click to expand...
Click to collapse
ADB - do you have USB debugging on? is Fastboot not working either? may need to re-install drivers on your PC
TWRP - are you saying it was installed, but you can't access it? unclear on your exact issue.

drewski_1 said:
ADB - do you have USB debugging on? is Fastboot not working either? may need to re-install drivers on your PC
TWRP - are you saying it was installed, but you can't access it? unclear on your exact issue.
Click to expand...
Click to collapse
Okay, I'll power off the tablet, then hold volume up AND down + power and that boots it into.... Recovery I think. When it boots to that, adb and fastboot are connected. I have a Nexus toolkit installed on my pc for flashing etc. Whenever I click flash recovery to reinstall twrp, it reboots the tablet into the OS and that's it. And when it's booted into the OS, there's no adb connection. And USB debugging is on. I finally just gave up.

blkhrt13 said:
Okay, I'll power off the tablet, then hold volume up AND down + power and that boots it into.... Recovery I think. When it boots to that, adb and fastboot are connected. I have a Nexus toolkit installed on my pc for flashing etc. Whenever I click flash recovery to reinstall twrp, it reboots the tablet into the OS and that's it. And when it's booted into the OS, there's no adb connection. And USB debugging is on. I finally just gave up.
Click to expand...
Click to collapse
Power + Vol Up/Down boots to bootloader.
If you have fastboot, then download the TWRP img file to your computer and issue the following command in the bootloader (forget the toolkit)
Code:
fastboot flash recovery <recovery img file name>
then you should be able to get into TWRP by using the Power Up/Down buttons until you see "Recovery" aligned with the Power Button.
press Power and you should be good to go.

blkhrt13 said:
I'm trying to get this ROM off my nexus 10, but I don't have ADB connection for some reason. I don't have TWRP recovery anymore either. Anyone have any tips?
Click to expand...
Click to collapse
I'm in the EXACT same situation. Fastboot and adb not working for this, but all my other android devices are working fine. Luckily I have twrp installed so I'll just flash something else then start over on a diff rom.
Edit: and of course, just like that, I restart one more time and it actually works. very temperamental i guess.

This is a great ROM with fast clean I interface. I used official manta 5.1 from Jide. Unfortunately google device manager now sees my N10 as a Linux device, and google play services will not load properly so I cannot play cloud connected games which is really sad, I will have to back to an android custom ROM..... If you don't need play services give jide a try.. Its a pretty cool concept.

Stuck in Bootloader - adb no devices - can't boot into system or recovery

Hey guys I'm stuck in bootloader on my taimen and I hope someone can help me.
I tried to update my OS from latest Android 9 factory image to Android 10 via bootloader, as I always do.
After executing the command
Code:
./flash-all.sh
I got a message that said that I should download and install the latest platform-tools from googles dev site, what I did. And I think that was my mistake. I downloaded the updated tools and replaced the old ones, while beeing in bootloader on my phone and connected to my MacBook.
Now I have a problem that whenever I try to boot in recovery or system I get the dead android Icon with 'No commands'. That wouldnt be a problem for me, if I could install a new .img to boot into system and start again. But unfortunately I cant find my device via adb. The List of attached devices is always empty.
What I have tried so far to solve this issue:
- tried 2 different cables and all USB ports I have - no success
- restarted adb several times - no success
- added vendor Id to /adb_usb.ini file like described in this post https://stackoverflow.com/a/7136003 - no success
Does anyone have a suggestion what I could try next? Any help is appreciated

Download Homebrew. And install adb in terminal, and try if that works . https://brew.sh/index_sv .
https://stackoverflow.com/questions/31374085/installing-adb-on-macos/32314718#32314718

I'm no expert but I thought that you should use fastboot commands from your MacBook terminal if you are in the bootloader and not adb commands. But I guess the fastboot commands don't work either since you wouldn't have a problem then!
Tips on getting to recovery mode from 'no command' screen:
https://youtu.be/P1RGEle3qN0

Hey guys thanls for your suggestions.
Fortunately I was able to resolve my issue. The problem was that I was on the wrong partition.
After setting the partition back to a with
Code:
fastboot --set-active=a
my device id appeared in the list of attached devices
Code:
fastboot devices
So I was able to reflash the flash-all.sh and now I'm on Android 10.

[GUIDE]UNBRICK NOTE 8 PRO - NO Authorised Service Account - YES Fastboot

Hello everyone.
Yesterday I bricked my Xiaomi Redmi Note 8 Pro, and today I managed to unbrick it without requiring anything special (no need for a Authorized Service Account).
I use Linux, so the scripts inside the Stock ROM end with the .sh file extension. If you're using Windows, use the .bat files.
Phone:
Xiaomi Redmi Note 8 Pro 128GB - Begonia (with NFC).
Bricked state:
Constant boot loop;
No access to bootloader;
No access to system;
Access to fastboot.
Phone requirement:
You must be able to load fastboot mode.
PC requirements:
1. You'll need adb tools (SDK Platform-Tools) to communicate with your phone. Official link is below;
2. Download and unpack the Stock ROM linked below.
Instructions:
1. You need to make sure your phone has some power in it;
2. Unpack the Stock Rom and enter its folder (begonia_global_images_V10.4.2.0.PGGMIXM_20191024.0000.00_9.0_global);
3. Put your phone into fastboot mode (Key Combo: Hold the Power button + Volume Down button until the fastboot logo appears);
4. Connect your phone to your PC;
5. Run the flash_all.* scripts according to your operating system:
5.1. Linux: "./flash_all.sh";
5.2. Windows (untested; I'm not using Windows): Run "flash_all.bat" (How to Run a BAT File on Windows);
6. Wait something between 5min to 10min. It's quite fast, and the flashing process is verbose enough.
7. Profit.
F.A.Q.:
1. How did you find this?
Well, none of the unbrick methods in the forum were working, except for the Authorised Service Account one which I didn' t test. I desperately wanted to unbrick my phone by myself, and I thought that it couldn't get worse (it could with a completely blank screen, but I got away with it).
2. Where did you get the Stock ROM from?
I can't remember. It likely was from a xda forum post but I'm unsure. If I can find the original post containing the Stock ROM I used I'll write it here.
3. Which Miui and Android version did you have prior to the brick?
MIUI Global 11.x + Android 9.
4. Which Miui and Android version does the Stock ROM you installed have?
MIUI Global 10.4.2 + Android 9.
5. Can I install any Stock ROM?
As long as it's compatible with your phone version, yes. I recommend not installing a Android 10 Stock ROM because of this: https://forum.xda-developers.com/showpost.php?p=82743011&postcount=3
6. What if can't enter fastboot mode (phone screen in dead blank)?
You won't be able to unbrick your phone using this method. It is worth trying to enter fastboot mode even though your phone has a dead screen, because fastboot might be working anyway (you'll have to test this yourself, as in trying to load fastboot with a blank screen). Read the next question.
7. How can I test if fastboot mode is working?
"adb devices" returns nothing;
"fastboot devices" returns your device (proof it works). Since "fastboot devices" finds your device, you can run the appropriate scripts.
8. What about your Mi Unlock Status before and after the brick?
Before: Unlocked.
After: Unlocked (I thought it would lock the bootloader again, but it didn't).
9. My phone is bricked and I don't know how much battery my phone has left. What should I do?
You should let it turn off due to 0% battery and charge it fully. I do not recommend you flash like I did, without knowing how much battery I had (yes, I took my chances there). As far as I know, any phone in fastboot mode does not charge its battery.
10. Why is fastboot working in your case?
I don't know. I suspect flashing the preloader and the lk from this OP Redmi Note 8 Pro - The Megathread helped, but it's just a hunch.
11. Will you attempt to flash a Custom ROM again?
After taking a break, yes.
12. Is this phone now unbrickable?
As long as fastboot mode works, perhaps. More feedback is required.
Files:
SDK Platform-Tools (adb/fastboot): https://developer.android.com/studio/releases/platform-tools
Stock ROM used: http://bigota.d.miui.com/V10.4.2.0.PGGMIXM/begonia_global_images_V10.4.2.0.PGGMIXM_20191024.0000.00_9.0_global_270117fdb2.tgz
Feedback:
Due to my job I'm currently very short on time during the week to follow this thread, so it would be immensely helpful to have your feedback on this procedure.
Feedback from people who's phones are bricked with blank screens would be very appreciated, specifically if they can enter fastboot mode without any visual cues from their phones. If any bricked state allows fastboot mode, it seems this phone is easily unbrickable.
Thanks:
strongst for his understanding and in reopening this thread.
Compass.

Thread open again
strongst
Forum Moderator

Hi there,
Is there anyway to fix the hardbrick without the authorized account?? If not how can i find someone to do this for me?

andrewff2 said:
Hi there,
Is there anyway to fix the hardbrick without the authorized account?? If not how can i find someone to do this for me?
Click to expand...
Click to collapse
Yes, if you can access fastboot mode in your phone like I mentioned above. If hardbrick means loss of access to fastboot mode/recovery/system/basically everything, you'll need to find some other unbrick method.
If fastboot mode is working for you, you can unbrick your device by yourself with nothing else than the fastboot command and the Stock ROM. No need for any extra tools/programs.
inb4: The fastboot command is in the SDK Platform-Tools package I linked in the OP.
Compass.

Compass Linux said:
Yes, if you can access fastboot mode in your phone like I mentioned above. If hardbrick means loss of access to fastboot mode/recovery/system/basically everything, you'll need to find some other unbrick method.
If fastboot mode is working for you, you can unbrick your device by yourself with nothing else than the fastboot command and the Stock ROM. No need for any extra tools/programs.
inb4: The fastboot command is in the SDK Platform-Tools package I linked in the OP.
Compass.
Click to expand...
Click to collapse
Yeah i tried this method but fastboot cannot even detect device

andrewff2 said:
Yeah i tried this method but fastboot cannot even detect device
Click to expand...
Click to collapse
That's a shame.
It's worth trying different USB ports, cables etc.
I usually enter fastboot mode first and only then I connect the phone to my PC.
Then "./fastboot devices" and my phone is listed.
Compass.

Compass Linux said:
Yes, if you can access fastboot mode in your phone like I mentioned above. If hardbrick means loss of access to fastboot mode/recovery/system/basically everything, you'll need to find some other unbrick method.
If fastboot mode is working for you, you can unbrick your device by yourself with nothing else than the fastboot command and the Stock ROM. No need for any extra tools/programs.
inb4: The fastboot command is in the SDK Platform-Tools package I linked in the OP.
Compass.
Click to expand...
Click to collapse
Yeah i tried this method but fastboot cannot even detect device in windows appear com5 in Windows but fastboot do nothing just white led that blinks

andrewff2 said:
Yeah i tried this method but fastboot cannot even detect device in windows appear com5 in Windows but fastboot do nothing just white led that blinks
Click to expand...
Click to collapse
I can't give support in this area, but do you have the proper Windows drivers installed?
If you do and it still doesn't work, try a different computer. If you can use a Linux machine somehow it's worth trying. With Linux I didn't need to install anything besides the SDK Platform-Tools package to communicate with my phone.
I think you can unbrick your phone, because fastboot mode is loading (if it's loading it should reply to fastboot commands).
Compass.

Compass Linux said:
I can't give support in this area, but do you have the proper Windows drivers installed?
If you do and it still doesn't work, try a different computer. If you can use a Linux machine somehow it's worth trying. With Linux I didn't need to install anything besides the SDK Platform-Tools package to communicate with my phone.
I think you can unbrick your phone, because fastboot mode is loading (if it's loading it should reply to fastboot commands).
Compass.
Click to expand...
Click to collapse
Thanks for the help man but no the only thing is the white led that sometimes blink nothing more no vibration no sound no screen nothing.....
I'm trying to find someone who can help me with this but no one responds... sad

andrewff2 said:
Thanks for the help man but no the only thing is the white led that sometimes blink nothing more no vibration no sound no screen nothing.....
I'm trying to find someone who can help me with this but no one responds... sad
Click to expand...
Click to collapse
It seems the only solution for you is this (for now): [GUIDE] [begonia] UNBRICK - stuck on DA mode / Authorised Service Account required
Which you've probably read already.
I think you either do that or wait to see if another unbrick method appears.
Compass.

I have the same problem as yours and tried your solution but after i run flash_all.bat it just opens and closes in a split-second and i have no idea whether it works or not. Should I wait a couple of minutes or just try again?

advan93 said:
I have the same problem as yours and tried your solution but after i run flash_all.bat it just opens and closes in a split-second and i have no idea whether it works or not. Should I wait a couple of minutes or just try again?
Click to expand...
Click to collapse
That's not normal.
What you should see are various files being flashed along with their progress meter.
I'm assuming you're double clicking the .bat file. Instead of doing that, open a CMD Prompt and use that instead.
Compass.