Database Info

Half bricked Xoom, deleted everything - help appreciated

Hello,
again i need help I have unlocked the bootloader on my Xoom, the i have flashed TWRP and downloaded a Rom and the Gapps. I copied the gapps onto the device and followed instructions which came with the rom. I was instructed to wipe "system" too which i did.
Of course that deleted the downloaded rom and gapps too. Now i have TWRP and was excited to mount USB storage and just copy over again the rom and gapps but unfortunately there is no mount as USB option.
What and how is the smartest way to go about it? I wanted to sideload over ADB but the device is not found. I have really tried everythin in my knowledge, hope someone can help
cheers

Come on guys, really need help here. My kids are killing me for the damn thing

I have same problem.......it's an issue of twrp !

Have you tried a micro sd card? (copy the rom and gapps there from a pc then put it in the Xoom, etc...)
Worst case, you should be able to grab the stock images http://forum.xda-developers.com/wiki/Motorola_Xoom and fastboot flash the device back to stock.

Have the same problem
dosada, could you solve the problem?
airesch, I tried to mount sd card but it is impossible. How can I return to stock without ADB because computer is not recognized?

hbtwender said:
dosada, could you solve the problem?
airesch, I tried to mount sd card but it is impossible. How can I return to stock without ADB because computer is not recognized?
Click to expand...
Click to collapse
Stock flash doesnt require adb, just fastboot mode. You may need to still install a driver, but if you can boot into recovery then the xoom should also be able to boot into fastboot mode and be recognized by a pc. If the instructions on the link I gave arent enough, I will see if I cant find something tomorrow when I am on a pc.
Sent from my GT-N8013 using XDA Premium 4 mobile app

hbtwender said:
dosada, could you solve the problem?
airesch, I tried to mount sd card but it is impossible. How can I return to stock without ADB because computer is not recognized?
Click to expand...
Click to collapse
NOTE: This WILL erase everything remaining on the device. In the case of the above, I don't know that you have much choice, just be forewarned.
Lord AIO toolkit has all the tools you need (look at the second post if you need the Windows driver.) Extract both the stock image zip and the toolkit (unless you have the sdk, in which case as long as you can find fastboot.exe you should be fine,) to somewhere convenient. Install the windows driver if you never have before and reboot your pc.
1. Boot your Xoom in fastboot mode: Power+Vol+ until it says: Starting Fastboot protocol support (you may need to tap the Vol+ instead of holding it the whole time, my Xoom has always been a bit picky about the buttons.)
2. Connect the usb to the pc
3. In a Command prompt window, go into the extracted version of the toolkit above (or if you have the sdk, just go to where you have fastboot.exe from it)
4. Run the following commands (replacing the files at the end with the full extract path from your stock image zip extract)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
"fastboot reboot" if you want to stay unlocked or "fastboot oem lock" if you want to re-lock and follow the prompts. The Xoom will get OTA updates even if it's unlocked, so there should be no reason to re-lock unless you need to send it in for service.
The driver isn't what I used to use, but it *should* work, and the instructions should be correct as far as I can remember. As long as you don't flash the wrong image to the wrong place/run out of power during flashing/disconnect during a flash then none of this should permanently damage the hardware and should get you a working device again. It's just that it's been so long since I have personally done any of this that I have forgotten more than I ever knew .

Solved
airesch said:
NOTE: This WILL erase everything remaining on the device. In the case of the above, I don't know that you have much choice, just be forewarned.
Lord AIO toolkit has all the tools you need (look at the second post if you need the Windows driver.) Extract both the stock image zip and the toolkit (unless you have the sdk, in which case as long as you can find fastboot.exe you should be fine,) to somewhere convenient. Install the windows driver if you never have before and reboot your pc.
1. Boot your Xoom in fastboot mode: Power+Vol+ until it says: Starting Fastboot protocol support (you may need to tap the Vol+ instead of holding it the whole time, my Xoom has always been a bit picky about the buttons.)
2. Connect the usb to the pc
3. In a Command prompt window, go into the extracted version of the toolkit above (or if you have the sdk, just go to where you have fastboot.exe from it)
4. Run the following commands (replacing the files at the end with the full extract path from your stock image zip extract)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
"fastboot reboot" if you want to stay unlocked or "fastboot oem lock" if you want to re-lock and follow the prompts. The Xoom will get OTA updates even if it's unlocked, so there should be no reason to re-lock unless you need to send it in for service.
The driver isn't what I used to use, but it *should* work, and the instructions should be correct as far as I can remember. As long as you don't flash the wrong image to the wrong place/run out of power during flashing/disconnect during a flash then none of this should permanently damage the hardware and should get you a working device again. It's just that it's been so long since I have personally done any of this that I have forgotten more than I ever knew .
Click to expand...
Click to collapse
Hey airesch, thank you for your support. I couldn´t follow yours suggestion because my xoom was not recognizing the PC or MAC. However I discovered that my sdcard was broken. When I´ve tried a new one with ZIP files inside it works perfectcly and I could return to my old room doing flah in the recovery mode of TWRP2.2.
It is important to note that my Xoom did not find .IMG files inside the card but only ZIP ones. Any way it worked perfectly and I hope this solution will serve to other in solving his/her problems.
Many thanks

Well, that works too, and that was closer to what I originally suggested (tho I didn't expect you had a bad sd card.)
And yes, recoveries generally don't support IMG files directly, you need to have a specially crafted zip to flash those in. IMG files directly are for fastboot/pc tool flashing.
Congrats on fixing it.

[Q] Google OG Pixel problems soft bricked

Hello everyone,
I have an OG Pixel 5'', the stock Android was 7.1.2 and I updated it to Android 8.1 Oreo. Bootloader is unlocked, and I am able to install a TWRP 3.2.1-0 no problems. Phone at the time worked well. Now I have tried to flash an ElementalX Kernel on my device. This worked and I managed to boot. However, a message "There is an internal problem with your device, please contact the manufacturer". There is a thread to fix this and I should have done my research better.
Anyway, I went into TWRP and did a complete wipe of the phone, thinking that I could have just boot into TWRP again and copy the stock flashable zips to reflash the ROM.
It turns out that:
a) TWRP doesnt work. I.e when I got into fastboot mode (Power + Volume Down) and selected Recovery, the phone flashed to screen with Google image and then flashed back into the one with the green Android.
b) I managed to boot twrp via fastboot from my computer. So I booted into fastboot mode, and then on my computer, did: fastboot boot <twrp3.2.1.zip>. This worked and I managed to get into TWRP again. However, I cannot transfer file to flash. I.e when the phone showed up on my computer in TWRP, I cannot drag and drop anything into mounted folder.
I have tried the following to get stock ROM from this website: https://developers.google.com/android/images
a) I decided to look at ADB Sideload. So from the above website, I downloaded the zip files under Full OTA Images and then in TWRP, I went into Advance and chose ADB SIdeload. On my computer, I did "adb sideload name_of_zip_file_downloaded". The process started but ended very quickly, the finished time was 0.00 second, which means that nothing happened. Clearly, TWRP console showed that it is unable to mount /data and other folders. I guess the reason is that I am running a "live" TWRP? I checked by going back to TWRP mainscreen and tried to mount. However, all hard drives show 0MB (OTA USB and the main drive).
b) I used factory images approach by downloading zip from the same website, but this time under Factory Images. For this one, I unzip the files to a separate folder. Then I did flash-all.sh script but it said that my fastboot is too old.
So... to fix fastboot, I tried: (I am on Ubuntu 16.04.02)
a) Remove whole android fastboot with sudo apt-get remove, then reinstalled => Did not work. Still fastboot is too old
b) Download entire Android SDK from here: https://developer.android.com/studio/install.html. Fastboot still didnt work
c) From the Android Studio website, I tried to download just the command line tools. However, I could not find the folder with fastboot in it. A Google search shows that the fastboot and adb should be in platform-tools folder. Couldnt find any
Once again, I apologize for a very very long thread (It's 5am and I am trying to figure this thing out). Please, let me know if you guys can offer any help. Any help is greatly appreciated. FYI, I am coming from a Moto Z Play, and if things happen I would just boot into TWRP and copy the zip over. Clearly, this is not the case. This is my 1st Pixel as well.
Please let me know and thank you very very much.

Installing ex messes with the boot.IMG you need to reflash twrp after. Also don't manually flash stock zips that doesn't even make any sense. Download the latest android sdk or base platform tools then get the latest factory image and extract it into platform tools. Then go into fastboot and manually flash the official factory image

To use fastboot on ubuntu you have to put sudo infront of the command: sudo fastboot ........, Because of a permissions thing.
Sent from my Google Pixel using XDA Labs

Thank you everyone. I have managed to reflash the OS. Gonna stay with stock kernel

maxwell0312 said:
Thank you everyone. I have managed to reflash the OS. Gonna stay with stock kernel
Click to expand...
Click to collapse
I personally recommend using a custom kernel just make sure to follow the OP exactly. As the kernel and twrp are usually stored in the boot.img together and the kernel overwrites the boot.img the problem was likely that you just did things in the wrong order which would cause twrp to be removed. Typically the order of installing custom stuff from stock goes this way: flash_all to restore stock boot.img, boot twrp, factory wipe, flash rom, flash twrp, boot rom, reboot into recovery, flash kernel, flash twrp, reboot system, reboot recovery, flash magisk. Some rooms vary as they may require you to do things like flash a vendor img or delete the vendor overlay folder(always follow OP).

help with rooting a oneplus 6 using linux terminal (not windows)

This is my first time rooting a phone but Im defiantly in over my head and think i almost broke the oneplus 6 when i was trying to enter commands in the linux terminal. So far I have unlocked bootloader and am currently stuck trying to figure out a) what exactly the twrp recovery really does, b) which is the right files to download, c) the proper commands to flash custom recovery in a linux terminal. Thanks in advance to anyone who can help me.

Command you need is fastboot boot (recovery name). Replace recovery name with whatever you called the download of the twrp image file.
Twrp is necessary to flash custom ROMs, kernels and magisk.
After flashing rom you need to flash twrp zip of your choice to maintain recovery otherwise it is overwritten by stock recovery.
There is a helpful guide I will post the link to
Here
https://r.tapatalk.com/shareLink?ur...share_tid=3792643&share_fid=3793&share_type=t
Sent from my ONEPLUS A6003 using Tapatalk

The commands for Linux and Windows are nearly identical. You just need to use the Linux version of adb instead of adb.exe.
TWRP is a custom recovery. It's similar to the GRUB bootloader for Linux, but more touch interface friendly. It allows you to make edits to the system, backup the system, and install custom zip's for the system.

keep getting error
when i run command to flash recovery (sudo fastboot flash twrp-3.2.1-0-enchilada.img) i keep getting this error:
unknown partition 'twrp-3.2.1-0-enchilada.img'
error: cannot determine image filename for 'twrp-3.2.1-0-enchilada.img'

Instead of trying to flash twrp from fastboot do a sudo fastboot boot <image name> then flash the zip while in twrp...
Sent from my ONEPLUS A6003 using Tapatalk

Thanks bkeaver for the advice and im glad to say I finally got that phone rooted. One more obstical I experienced was the phone not booting into twrp instead it was locking up on a screen that said Qualcomm crash dump mode. I unplugged and rebooted by holding the power button. From what I could read online it had to do with compatibility issues with Android pie. The Blu_Spark TWRP img and zip files seemed to do the trick. Anyone else who is experiencing the same issues I suggest you read this page: google.com/amp/s/amp.reddit.com/r/oneplus/comments/9iid4e/unable_to_flash_recovery

Linux_fart_18.3 said:
when i run command to flash recovery (sudo fastboot flash twrp-3.2.1-0-enchilada.img) i keep getting this error:
unknown partition 'twrp-3.2.1-0-enchilada.img'
error: cannot determine image filename for 'twrp-3.2.1-0-enchilada.img'
Click to expand...
Click to collapse
Did you even try to read man page? Just use right syntax, which is identical in Windows BTW.
fastboot flash partition [filename]
http://manpages.ubuntu.com/manpages/xenial/man1/fastboot.1.html

Linux_fart_18.3 said:
From what I could read online it had to do with compatibility issues with Android pie.
The Blu_Spark TWRP img and zip files seemed to do the trick.
Anyone else who is experiencing the same issues I suggest you read this page: google.com/amp/s/amp.reddit.com/r/oneplus/comments/9iid4e/unable_to_flash_recovery
Click to expand...
Click to collapse
In oxygen OS ver.9, you must download "twrp-3.2.3-x_blu_spark_v9.86_op6.img" and "twrp-3.2.3-x_blu_spark_v9.86_op6.zip" from https://forum.xda-developers.com/devdb/project/?id=27466#downloads ,
and launch twrp from this command "fastboot boot twrp-3.2.3-x_blu_spark_v9.86_op6.img".
After your device boot trwp, you can install "twrp-3.2.3-x_blu_spark_v9.86_op6.zip" from your device's internal storage (if you copy into it) or adb side-load mechanizm.
Once zip installed, you don't need to run fastboot to boot twrp recovery (only you reboot the device to fastboot mode and select recovery, trwp boot up).

What's a syntax?
davfiala said:
Did you even try to read man page? Just use right syntax, which is identical in Windows BTW.
fastboot flash partition [filename]
http://manpages.ubuntu.com/manpages/xenial/man1/fastboot.1.html
Click to expand...
Click to collapse
rhetorical question in the title and fyi I will never claim to be very tech savvy thanks for the info though

Badly f*d Op7Pro. Need help to revert to stock

Hi,
First of all, yes, I have checked the other threads that talk about reverting to stock and I am still stuck.
So I installed Kang OS which is Android 11, and now I want to revert to stock. I have tried downloading multiple different versions of the fastboot ROM from the page https://androidfilehost.com/?w=files&flid=294300 and run the flash all batch file and every time I am either getting stuck in a boot loop or getting the Verity Crash Dump Screen. I have managed to reach the fastboot screen, and I am waiting on the fastboot screen, for someone to show me some way.
Thanks in Advance.

If you used a pin then your storage is encrypted and the rom you are trying to flash can't use it, that's why you're most likely stuck at boot.
I ran into the same issue and posted about it in the same thread. I think we will need a new version of TWRP as 3.4.0-0 would not accept my pin which had not changed.
To fix your issue, sadly, you'll need to wipe your storage:
Boot the phone into fastboot mode
Attach your USB cable to the phone/PC
Download and unzip the file I've attached (ADB/Fastboot)
Launch an elevated command window in the folder you extracted the attached zip to
Try the command fastboot devices and ensure that it reports the device correctly, if not then you need to install the latest OnePlus drivers
Type the following in the command window : fastboot -w (This will wipe the storage)
Try your rom again (TWRP should remain as the recovery if you had flashed it already, if not then copy the latest TWRP img file to the same folder as the ADB/Fastboot tools, use fastboot and type boot twrpfilename.img this will make the phone boot into TWRP recovery, you can then copy over the TWRP zip and flash it to recovery using the booted version of TWRP)
Once you've done the above you shouldn't really need to use the fastboot scripts as the latest rom should just flash from TWRP.

Get msm download tool for guacamole which is the codename of the op7p. I know the shorts with the global version I am unsure if this works with T-Mobile or others?

MSM is a bit of a severe fix when they've already confirmed they can still get fastboot, MSM is for completely bricked phones that can't access anything. Wiping the storage and going to fastboot will allow them to just flash recovery then flash the stock rom. Way easier.

Boot into twrp. Then format data. Phone will boot then.

Need help restoring my pixel 5

Good morning all I need some help unbricking my pixel 5. I have exhausted all possible avenues that I'm aware of to restore my phone out of bootloop. At the time I messed it up I was attempting to use twrp. In an attempt to fix the phone I tried flashing the system,and boot to no avail repeatedly getting the error "boot.img missing command-line or os version" as well as using the flash all from the stock firmware file. The current active slot is b and the a/b partition thing is new to me so I'm sure somewhere along the way I missed something. Any help is greatly appreciated .

Could you try this fastboot command and see if it works?
fastboot --set-active=a

I did try that however I'm not sure i was doing it correctly is it typed the way you typed it out?

Reboot the phone into the bootloader, look up how to do that if you don't know how, and then manually flash a rom or use the Android Flash Tool. The latter option is recommended if you are a novice.

I wouldn't say I'm novice lol but more out of the game too long either way thank you for your assistance I will try that as soon as I get a chance and report back

UPDATE your advice worked and I was able to reboot properly thank you in a side note is it impossible at this time to install twrp on a pixel 5?

musiv2 said:
UPDATE your advice worked and I was able to reboot properly thank you in a side note is it impossible at this time to install twrp on a pixel 5?
Click to expand...
Click to collapse
Yes. The Pixel series, as with most A/B devices, do not have a bespoke recovery partition. The recovery kernel is compressed into the boot image. TWRP does not support compression in this way so it cannot be used as a replacement for the stock recovery. The only effective way to use TWRP is to live boot the image, use TWRP to do whatever you need to do, without installing it to /boot.
BTW the next time you need to restore your phone you can use the Android Flash Tool.

Ok thank you for the explanation as I stated before I am new to the a/b partitioning way of android life so I have alot to learn

I used twrp in the past( on no A/B devices) but would recommend learning fastboot/adb. First step: always make sure USB debugging is enabled after every flash. This will make it so you can fix a lot of mistakes and recover your device. It's the first thing I do after every boot on a new install.
Here's the commands to flash stock to both slots. NOTE: this is for android 13. 12 and before will be a little different. Bootloader, radio and rom names should be exact to file, this is just for example.
fastboot --slot=all flash bootloader bootloader.img
fastboot reboot bootlaoder
fastboot --slot=all flash radio radio.img
fastboot reboot bootlaoder
fastboot --slot=a --skip-reboot update stock-image.zip
fastboot reboot bootlaoder
fastboot --slot=b --skip-reboot update stock-image.zip
fastboot -w
fastboot reboot
One final note: I put slot a first but I always start with the active slot(it's in the bootloader screen). If you want the android 12 instructions, let me know but it's not much different, you just use the stock recovery.