Database Develop

[Q] i need your help dev,i think my phone got bricked

i am trying to upgrade from ginger bread to jellybean
jelly bean needs a 250mb internal memory for the system so what i did is partition my internal memory using blackrose i did partition it and wipe all the data except the SD after that i notice that the OS is gone so i search for a solution and found this one http://forum.xda-developers.com/wiki/HTC_Nexus_One/Recovery_Images but when i try to command adb devices in cmd ,it didnt displays my device serial or something and if i command adb shell it says error device not found,so i look for another solution,i found solution on fastboot mode,
screenshot of my device when i select bootloader
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i tried
fastboot device
fastboot oem unlock but error occured again it says command error
i tried another
like booting or flashing boot.img and recovery.img
but it both says cannot open boot.img or recovery.img
i think i got my device bricked,anyone can help me please? i cant use my phone now :crying:

If you have blackrose than you have s-off/unlocked bootloader
So you now need to flash a recovery via fastboot and then boot to the new recovery and then flash ROM of choice, do not flash any stock firmware (may have a radio in it which could result in a brick)
http://forum.xda-developers.com/showthread.php?t=2277112
Here are some tips on how to use fastboot properly, if you get stuck and need further help be sure to copy and paste all input/output from cmd/terminal here
Best of luck
Sent from my Nexus 7 using Tapatalk 2

i got this error when trying to unlock bootloader
<bootloader> [ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.16s
Click to expand...
Click to collapse

Again, you have black rose, you do not need to run unlocked command - you have s-off
What you need to do is flash a recovery through fastboot and then boot to new recovery and then flash ROM of choice
Do not run fastboot oem unlock - this will do nothing for you
Do not flash factory firmware with out being sure what you are flashing or this can result in a brick, just flash recovery then ROM
Sent from my Nexus 7 using Tapatalk 2

ok thanks got it fix

Transfert file with ADB

Hi so i flashed the google edition rom and it kept bootlooping, so i went to recovery and wiped everything but it wiped also the ROM file from the sd card now im left with nothing to flash and only recovery i think i have to transfert the file trough ADB if so can anyone give me a tutorial ? i tried adb but there is no devices listed :'( i think its debug mode it wasnt enabled.

JadeAmineHa said:
Hi so i flashed the google edition rom and it kept bootlooping, so i went to recovery and wiped everything but it wiped also the ROM file from the sd card now im left with nothing to flash and only recovery i think i have to transfert the file trough ADB if so can anyone give me a tutorial ? i tried adb but there is no devices listed :'( i think its debug mode it wasnt enabled.
Click to expand...
Click to collapse
USB debugging doesnt matter in custom recovery.
adb push <name of ROM>.zip /data/media/0/
or
adb sideload <name of ROM>.zip
you can always try googling, and come up with a few tutorials:
http://forum.xda-developers.com/showthread.php?t=2317986
http://android-revolution-hd.blogspot.com/2013/12/ow-to-use-adb-sideload.html
http://android-revolution-hd.blogspot.com/2013/12/how-to-copy-rom-zip.html
etc.

This shows device not found when i use adb devices there is nothing

JadeAmineHa said:
This shows device not found when i use adb devices there is nothing
Click to expand...
Click to collapse
Open Device Manager do you see something like:
{
"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"
}
if yes, please go to my guide and check FAQ #2.

nkk71 said:
Open Device Manager do you see something like:
if yes, please go to my guide and check FAQ #2.
Click to expand...
Click to collapse
This is what i see sync manager is installed i tried the fastboot command to get token for boatload unlock and it works but adb is not working, Plase help me i'm stuck :crying: and just to mention that im in bootloader in fastboot usb mode ??

JadeAmineHa said:
This is what i see sync manager is installed i tried the fastboot command to get token for boatload unlock and it works but adb is not working, Plase help me i'm stuck :crying:
Click to expand...
Click to collapse
like i said, just go to my guide and check FAQ #2 (in post #1), http://forum.xda-developers.com/showthread.php?t=2541082
has all the instructions, pictures, etc.

Did anyone ever get this on a tablet? Service can't solve it.

So I have this Asus MeMO Pad 7 which I tried to flash. I can't honestly remember what I did exactly, just followed some commands from tutorials online and I got it bricked.
It looks like the image attached below, the Aptio BIOS on a tablet. Do I need to bother buying an OTG cable and plug in my keyboard? I saw a thread in 2015 with someone having the same issue, but there is no answer.
I know I bricked this tablet, went with it to the service, but I have a feeling they didn't try hard enough or are not knowledgeable.
{
"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"
}

brickedasus said:
So I have this Asus MeMO Pad 7 which I tried to flash. I can't honestly remember what I did exactly, just followed some commands from tutorials online and I got it bricked.
It looks like the image attached below, the Aptio BIOS on a tablet. Do I need to bother buying an OTG cable and plug in my keyboard? I saw a thread in 2015 with someone having the same issue, but there is no answer.
I know I bricked this tablet, went with it to the service, but I have a feeling they didn't try hard enough or are not knowledgeable.
Click to expand...
Click to collapse
Solution for next time: Don't follow random commands from tutorials online.
If you end up in the UEFI setup utility every time you start the tablet, you've likely managed to destroy your bootloader. You could try to buy an OTG cable, plug in a keyboard and an USB stick with a Linux live system and use that to restore it, but generally this is not necessary because these devices come with another recovery mechanism called "DNX mode", that allows restoring the bootloader.
With your tablet turned off, press Volume Up + Volume Down and then the power button. If it displays "Fastboot starting..." there is still hope.
Install Fastboot on your PC. If you haven't done it already, there are many tutorials out there with instructions how to install it. You can take a look at https://wiki.lineageos.org/adb_fastboot_guide.html for example.
Connect the tablet to your PC and on a command line, type "fastboot devices" and check that your tablet shows up.
Download the firmware from ASUS: http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/UL-K013-WW-12.10.1.36-user.zip and extract "esp.zip" and "droidboot.img" from the ZIP. Open "esp.zip" and extract "EFI/Intel/efilinux.efi".
On the command line, switch to the directory where you have extracted "efilinux.efi" and "droidboot.img", then run "fastboot flash osloader efilinux.efi" and "fastboot boot droidboot.img".
With a bit of luck that might bring up Droidboot and allow you to access the recovery to install the stock ROM correctly again... Good luck!

How to block bootloader on xt1799-2

I will try to describe exactly what I did. I warn you that if you want to repeat this, then do everything at your own risk!
Original message
1. The cleanest installation possible​
We do a COMPLETE cleanup and format the DATA in TWRP not lower than version 3.4... then reboot into bootloader and connect to the PC with a good cable. Run Fastboot on the PC in the command line in turn enter the following commands:
fastboot devices
fastboot erase all
fastboot reboot bootloader
2. Install motoXT1799-2_GLOBAL_2021.02.20_oreo.zip​
Use the firmware from here: motoXT1799-2_GLOBAL_2021.02.20_oreo
3. Install Magisk​
The latest version of Magic-v22.0.apk must be installed and Magisk-v22.0.zip
4. Go to the developer menu​
In the developer menu, we give permissions to unlock the OS bootloader, as well as give permission to debug via USB.
5. Run adb Fastboot on the command line​
The phone must be connected to the PC via USB. We enter the command adb devices on the smartphone, a dialog box should appear to allow debugging this device or something like that, respectively, we give permission.
Next, we reboot into the bootloader with the command adb reboot bootloader
6. Blocking​
Previously, we copy the stock recovery.img to the folder with adb Fastboot
Enter the commands:
fastboot flash recovery recovery.img
fastbo fastboot flashing lock
We reboot into the system.
7. Delete Magisk as unnecessary​
To do this, go to the program select delete see two items select first "restore partitions or something like that" then delete.
8. Do a factory reset​
If everything is done correctly, we get a device with Oreo Android 8.1.0 as if it came out of the factory.
{
"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"
}

Flashing stock rom RQ3A.211001.001 on Redfin device using Android Flash Tool partial progress, fails to fastbootd when entering flashboot userspace

{
"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 previously successfully installed and ran lingeageOS for a long time. In attempting to flash stock android, I'm getting a part-way successfully then failing to a screen titled 'fastbootd' when the flash script attempts to enter userspace fastboot. I'm running Arch Linux and have android tools installed locally as well with the android-tools package. I can start the device into fastboot mode and see it on my PC with `fastboot devices`:
$ fastboot devices
13091FDD4000GY fastboot
I would prefer to install android 11, but I've also tried android 12 with the same end failure result.
How can I troubleshoot this further? Any help is much appreciated!

brian_says_yas said:
View attachment 5517961
I previously successfully installed and ran lingeageOS for a long time. In attempting to flash stock android, I'm getting a part-way successfully then failing to a screen titled 'fastbootd' when the flash script attempts to enter userspace fastboot. I'm running Arch Linux and have android tools installed locally as well with the android-tools package. I can start the device into fastboot mode and see it on my PC with `fastboot devices`:
$ fastboot devices
13091FDD4000GY fastboot
I would prefer to install android 11, but I've also tried android 12 with the same end failure result.
How can I troubleshoot this further? Any help is much appreciated!
Click to expand...
Click to collapse
Hi Brian, have you tried a different usb cable? I only use windows so I can help more if you get a windows PC or run windows from a usb. I also unlock the bootloader manually with the ADB tools, first before using the flash tool.

So I switched to a macbook and a different USB cable both at the same time, and it worked. I'm speechless lol. Thank you for your help! Honestly the biggest benefit here is that I don't have to use Android 12 yet which was buggy as hell on my Pixel 6 Pro before someone did me the favor of stealing it in Miami.