Database Info

Need help asap!!!!

Okay before I start I know this was really dumb of me to do. I wiped everything in my phone/sd card because something was taking up a lot space and I couldn't figure out why, so i have no roms installed at all. there's no OS running in my phone at all. I have TWRP recovery installed but I can't mount it to my computer to get a rom onto it. Any solutions???? I don't Mind going back to stock, I just need my phone back.

breakfastclubdc said:
Okay before I start I know this was really dumb of me to do. I wiped everything in my phone/sd card because something was taking up a lot space and I couldn't figure out why, so i have no roms installed at all. there's no OS running in my phone at all. I have TWRP recovery installed but I can't mount it to my computer to get a rom onto it. Any solutions???? I don't Mind going back to stock, I just need my phone back.
Click to expand...
Click to collapse
You need to get cwm recovery, then get a usb otg cable, and flash the from from your flash drive. You have to use cwm because I don't think twrp supports usb otg

wstruction said:
You need to get cwm recovery, then get a usb otg cable, and flash the from from your flash drive. You have to use cwm because I don't think twrp supports usb otg
Click to expand...
Click to collapse
Thanks for your reply, In CWM i get "E: Can't mount"....i'm guessing because I have absolutely nothing on my SD card and phone...I can't mount USB storage or anything =/

breakfastclubdc said:
Thanks for your reply, In CWM i get "E: Can't mount"....i'm guessing because I have absolutely nothing on my SD card and phone...I can't mount USB storage or anything =/
Click to expand...
Click to collapse
You need to use adb sideload. You connect it to the computer with bootloader mode on, go to your platform tools file on your computer in the android adb file, shift+right click, hit open command window here, connect phone, type fastboot flash recovery, then whatever the name of the recovery img is. And I forgot to mention that you need to have the recovery img file in the adb folder. Hope this helps

wstruction said:
You need to get cwm recovery, then get a usb otg cable, and flash the from from your flash drive. You have to use cwm because I don't think twrp supports usb otg
Click to expand...
Click to collapse
wstruction said:
You need to use adb sideload. You connect it to the computer with bootloader mode on, go to your platform tools file on your computer in the android adb file, shift+right click, hit open command window here, connect phone, type fastboot flash recovery, then whatever the name of the recovery img is. And I forgot to mention that you need to have the recovery img file in the adb folder. Hope this helps
Click to expand...
Click to collapse
This is a bit confusing now, i went into my "C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools" then open command there? i don't see ADB file

breakfastclubdc said:
This is a bit confusing now, i went into my "C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools" then open command there? i don't see ADB file
Click to expand...
Click to collapse
You won't find adb.exe or fastboot.exe there unless you run the setup for the SDK.
If you are not interested in setting up the SDK, I recommend you just use this http://forum.xda-developers.com/showthread.php?t=2317790.
Also, I'm using CWM v6.0.4.7, and ADB works. I don't need to sideload anything.
I just do adb push xxxxx.zip to /sdcard/0/xxxx
Good luck!

breakfastclubdc said:
This is a bit confusing now, i went into my "C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools" then open command there? i don't see ADB file
Click to expand...
Click to collapse
Yes you go to where you said. Then you flash cwm recovery

[Q] Help please with nexus 5

I was in recovery and accidentaly wiped everything and now i m stuck in recovery and can connect to pc to transfer a new rom.
What do i do now??

DimitrisN5 said:
I was in recovery and accidentaly wiped everything and now i m stuck in recovery and can connect to pc to transfer a new rom.
What do i do now??
Click to expand...
Click to collapse
Now you must work out how to connect to PC to transfer new rom. You can use adb. Loads of guides for adb push about

rootSU said:
Now you must work out how to connect to PC to transfer new rom. You can use adb. Loads of guides for adb push about
Click to expand...
Click to collapse
When i go to mount option i twrp there is a list that says system data etc.but under these there isn't an option to mount

DimitrisN5 said:
When i go to mount option i twrp there is a list that says system data etc.but under these there isn't an option to mount
Click to expand...
Click to collapse
http://lmgtfy.com/?q=adb+push

Is there any chance i cant connect my device to my pc and permanently damage the device??

DimitrisN5 said:
Is there any chance i cant connect my device to my pc and permanently damage the device??
Click to expand...
Click to collapse
Not whilst adb puhsing, no.
If you were fastboot flashing something like a bootloader or radio and disconnected it during teh flash, you could brick your device - but you're not doing that.
adb push is just copying files from your PC to your device.
lets say you have rom.zip on your computer c drive
Code:
adb push c:\rom.zip /sdcard
is all you'd need to do.

[Q]Help! Soft-bricked NEXUS 5. Needs access to internal storage

Hi everyone,
I was on 4.4.2 and wanted to update to 4.4.3. Since I installed Xposed and the OTA package wouldn't install even after I uninstalled the framework, I opted for the factory image. I used the flash_all script that came with the image file and now my phone is stuck at the dancing colors.
Now I think I can probably get the phone to work again is I do a factory reset but I don't want to lose the file on the internal sdcard.
Is there anyway to backup the files on the internal storage?
I've tried ADB but it doesn't list my device either in bootloader or with the phone off or stuck at the dancing colors.
ADB does list my device in recovery mode with the "apply update from ADB" option, but I can't do a adb pull from there. It says:
error: closed.
Any idea?
OR a method to solve the soft-brick situation without wipe the files on /sdcard would work as well.
Thank you.

lgm said:
Hi everyone,
I was on 4.4.2 and wanted to update to 4.4.3. Since I installed Xposed and the OTA package wouldn't install even after I uninstalled the framework, I opted for the factory image. I used the flash_all script that came with the image file and now my phone is stuck at the dancing colors.
Now I think I can probably get the phone to work again is I do a factory reset but I don't want to lose the file on the internal sdcard.
Is there anyway to backup the files on the internal storage?
I've tried ADB but it doesn't list my device either in bootloader or with the phone off or stuck at the dancing colors.
ADB does list my device in recovery mode with the "apply update from ADB" option, but I can't do a adb pull from there. It says:
error: closed.
Any idea?
Click to expand...
Click to collapse
You have lost your internal data after using the factory images...

Primokorn said:
You have lost your internal data after using the factory images...
Click to expand...
Click to collapse
I did? The command in the flash script is
Code:
fastboot.exe -w update image-hammerhead-ktu84m.zip
and from what i can tell from the output it didn't flash userdata.img
Would that mean my files on the internal /sdcard is still in tact?

lgm said:
I did? The command in the flash script is
Code:
fastboot.exe -w update image-hammerhead-ktu84m.zip
and from what i can tell from the output it didn't flash userdata.img
Would that mean my files on the internal /sdcard is still in tact?
Click to expand...
Click to collapse
You need to remove "-w" if you didn't want it to flash your data. Everything's gone now dude..

fxdil said:
You need to remove "-w" if you didn't want it to flash your data. Everything's gone now dude..
Click to expand...
Click to collapse
I see. That solves the problem too, I guess. Thank you for clarifying.
:crying::crying:

Did Advanced wipe without ROM image | Please help

Hi,
I did an advanced wipe wiping everything - Dalvik cache, system, data, internal storage and cache.
Now, when I try to reboot, it says no OS and keeps bringing me back to TWRP. I tried the install feature but looks like there's no file in it either. My PC does not detect my phone as a hardware I think as when I tried to copy the ZIP file to it using another post which I'm not allowed to post here, the cmd commands for adb and mkdir were not recognized.
Can someone please help me salvage my phone?
In case any more details are required about the phone, happy to provide.

dheerajc17 said:
Hi,
I did an advanced wipe wiping everything - Dalvik cache, system, data, internal storage and cache.
Now, when I try to reboot, it says no OS and keeps bringing me back to TWRP. I tried the install feature but looks like there's no file in it either. My PC does not detect my phone as a hardware I think as when I tried to copy the ZIP file to it using another post which I'm not allowed to post here, the cmd commands for adb and mkdir were not recognized.
Can someone please help me salvage my phone?
In case any more details are required about the phone, happy to provide.
Click to expand...
Click to collapse
Go to Device management, you'll find the android composite device there. Change the driver to MTP device.

you can also try using adb sideloas

I assume you use Windows? It's probably just a driver issue. I always install official Google Android SDK, which contains proper USB drivers. Once you install it, your phone should be recognized by PC, while in TWRP.

daedric said:
Go to Device management, you'll find the android composite device there. Change the driver to MTP device.
Click to expand...
Click to collapse
Sorry, but am new to this. Can you please provide instructions to get my phone back to normal.
Thanks in advance

aciupapa said:
you can also try using adb sideloas
Click to expand...
Click to collapse
Sorry, but as am new to this, can you please help with instructions on how can I get my phone back to normal?
Thanks,

focus-pocus said:
I assume you use Windows? It's probably just a driver issue. I always install official Google Android SDK, which contains proper USB drivers. Once you install it, your phone should be recognized by PC, while in TWRP.
Click to expand...
Click to collapse
It is now visible in Android monitor in the studio but still doesn't show up as a connected device on the PC.
Anyways, the cmd doesn't recognize the adb command. can you please help with how can I bring my phone back to normal?

dheerajc17 said:
It is now visible in Android monitor in the studio but still doesn't show up as a connected device on the PC.
Anyways, the cmd doesn't recognize the adb command. can you please help with how can I bring my phone back to normal?
Click to expand...
Click to collapse
You need to add path to adb.exe to Windows PATH variable, then reboot and cmd should recognize adb commands, or you can just navigate to folder with adb.exe in cmd. Then check if adb can see your device, if it does, then just do adb sideload of ROM, and flash your ROM in TWRP.
If it's all too complicated, just return to stock using instructions from Google factory image website.

Put a rom on a flash drive, and connect it to your phone. In TWRP, go into "Mount" options, mount the flash drive (cant remember the exact wording), and then...can't remember quite vividly how, but it's easy from there to navigate inside your flash drive and install the rom.
REMEMBER: the flash drive should be formatted in FAT32 for TWRP to recognize it.

How to transfer Recovery file to the phone? (Serious problem)

I have LineageOS 16.0
I used MutiROM before, uninstalled it, but MultiROM Recovery is still installed.
Today I downloaded update for LineageOS but I got "Updater process ended with ERROR: 7"
Now I can't boot to OS because it boots straight to recovery.
The solution is to flash normal recovery and flash LineageOS zip.
But I can't transfer Recovery.img to my OnePlus One.
While I'm in Recovery, ADB is not working and there's no option to enable it.
And while I'm in Fastboot, PC can't see any fastboot devices.
It's not the PC's fault because it can recognize my Xiaomi Redmi Note 7 in both ADB and Fastboot mode.
So basically I need a way to transfer Recovery.img from PC to OnePlus One.
I can access only TWRP and Fastboot.
I can't do anything over USB cable.
OnePlus One doesn't have microSD card slot so I can't do it that way.
And I tried plugging in USB OTG drive and it phone can't recognize it. It won't even send the power to OTG drive.

eldin90 said:
And I tried plugging in USB OTG drive and it phone can't recognize it. It won't even send the power to OTG drive.
Click to expand...
Click to collapse
Use a low current flash drive, e.g. Transcend JetFlash 380 32 GB USB 2.0 OTG [200mA].

ze7zez said:
Use a low current flash drive, e.g. Transcend JetFlash 380 32 GB USB 2.0 OTG [200mA].
Click to expand...
Click to collapse
I don't think that'll work.
Phone doesn't give power to USB devices at all.
I tried plugging in multiple devices that used to work before (2 different USB thumb drives, both directly via micro USB port and via micro USB to USB 2.0 adapter, tried plugging in another phone, mouse, gamepad, micro USB to Ethernet adapter)
All those stuff used to work before while phone was on. But now they don't get power at all.
I don't know could it be because of Recovery?
I haven't tried plugging in OTG devices while in Recovery before.

eldin90 said:
While I'm in Recovery, ADB is not working and there's no option to enable it.
And while I'm in Fastboot, PC can't see any fastboot devices.
Click to expand...
Click to collapse
After entering:
Code:
adb devices
what you see in recovery mode?
---edit---
Use the USB 2.0 port on your PC.

ze7zez said:
After entering:
Code:
adb devices
what you see in recovery mode?
---edit---
Use the USB 2.0 port on your PC.
Click to expand...
Click to collapse
I don't see anything when I enter adb devices.
When I use any other phone I can see it after entering adb devices. But when I use OnePlus One I can't see anything.
And I only have USB 2.0 ports on my PC.

eldin90 said:
I have LineageOS 16.0
I used MutiROM before, uninstalled it, but MultiROM Recovery is still installed.
Today I downloaded update for LineageOS but I got "Updater process ended with ERROR: 7"
Click to expand...
Click to collapse
Are you sure you have an unmounted system partition before installing the ROM?
This message is the result of a mismatch between the build.prop entry from ROM and the TWRP installer script.

ze7zez said:
Are you sure you have an unmounted system partition before installing the ROM?
This message is the result of a mismatch between the build.prop entry from ROM and the TWRP installer script.
Click to expand...
Click to collapse
System partition is unmounted.
MultiROM TWRP gives me that error only when flashing some ROMs.
And it gives it to those ROMs always, no matter what I do.
Problem is that I only have LineageOS 16.0 zip on the phone and I don't have any other recoveries besides that MultiROM recovery.
Is there any way to boot the OS?
It worked fine before I tried to update it and it looks like all system files are still there.
I guess that failed update shouldn't had deleted any system files because it failed before it started doing anything.
I don't know what's making phone boot directly into recovery.
It won't even try to boot OS.
It goes straight into recovery every time.

eldin90 said:
System partition is unmounted.
MultiROM TWRP gives me that error only when flashing some ROMs.
And it gives it to those ROMs always, no matter what I do.
Problem is that I only have LineageOS 16.0 zip on the phone and I don't have any other recoveries besides that MultiROM recovery.
Is there any way to boot the OS?
It worked fine before I tried to update it and it looks like all system files are still there.
I guess that failed update shouldn't had deleted any system files because it failed before it started doing anything.
I don't know what's making phone boot directly into recovery.
It won't even try to boot OS.
It goes straight into recovery every time.
Click to expand...
Click to collapse
There should always be an original ROM for installation and several recovery versions in the phone's memory.
Now you have the use of restoring rom.
Clear the cache. First, try to recover only the Boot, and if that doesn't help, the entire backup.
You also have a powerful tool in TWRP in the form of a terminal and busybox commands, so act.

ze7zez said:
There should always be an original ROM for installation and several recovery versions in the phone's memory.
Now you have the use of restoring rom.
Clear the cache. First, try to recover only the Boot, and if that doesn't help, the entire backup.
You also have a powerful tool in TWRP in the form of a terminal and busybox commands, so act.
Click to expand...
Click to collapse
I tried wiping Cache and Dalvik / ART Cache
Still boots directly to recovery.
I don't have any backups or recovery installations on phone's memory.
I only have backup from 2 months ago that contains only boot and cache.
I restored it but it still boots directly to recovery.
What terminal commands should I use to fix this?

eldin90 said:
I tried wiping Cache and Dalvik / ART Cache
Still boots directly to recovery.
I don't have any backups or recovery installations on phone's memory.
I only have backup from 2 months ago that contains only boot and cache.
I restored it but it still boots directly to recovery.
What terminal commands should I use to fix this?
Click to expand...
Click to collapse
Since you don't maintain software hygiene, it's probably no better with hardware.
Clean the USB socket without damaging the connection. Clean the Vol- key in several ways.
Check if Odin can see the connection.
I have nothing more to add.

ze7zez said:
Since you don't maintain software hygiene, it's probably no better with hardware.
Clean the USB socket without damaging the connection. Clean the Vol- key in several ways.
Check if Odin can see the connection.
I have nothing more to add.
Click to expand...
Click to collapse
I work at coal coke industry and this happened about a month ago.
While I was charging the phone, coke dust inside the phone started burning and melted charger and USB socket together.
Guy from repair shop opened the phone and replaced USB socket with another one.
Is it possible that he didn't connected it correctly to the motherboard?
Or USB socket that he put wasn't exactly the same as the one that was originally there?
After he fixed it, we only tested can it charge the phone.
I haven't tried connecting phone to PC since then.
Anyways, is it possible to do something with terminal?
There has to be a file or something that's telling the phone to boot straight into recovery, right?
Can I remove or modify that file if it exists so phone boots into OS instead of recovery?
Vol- button isn't the problem.
It worked fine until I tried to update the OS.
And I can boot to Fastboot by holding Power and Vol+ buttons.

eldin90 said:
I work at coal coke industry and this happened about a month ago.
While I was charging the phone, coke dust inside the phone started burning and melted charger and USB socket together.
Guy from repair shop opened the phone and replaced USB socket with another one.
Is it possible that he didn't connected it correctly to the motherboard?
Or USB socket that he put wasn't exactly the same as the one that was originally there?
After he fixed it, we only tested can it charge the phone.
I haven't tried connecting phone to PC since then.
Anyways, is it possible to do something with terminal?
There has to be a file or something that's telling the phone to boot straight into recovery, right?
Can I remove or modify that file if it exists so phone boots into OS instead of recovery?
Vol- button isn't the problem.
It worked fine until I tried to update the OS.
And I can boot to Fastboot by holding Power and Vol+ buttons.
Click to expand...
Click to collapse
Using md5sum check the phone ROM.zip of your Lineage you tried to install. Then check the ROM.zip checksum on the server and compare the checksums. You will learn about the quality of the file.
If someone undertook to replace the usb socket, it is obvious that you should check not only the charging lines, but also the data transmission line.
From that I would repair the OPO.

ze7zez said:
Using md5sum check the phone ROM.zip of your Lineage you tried to install. Then check the ROM.zip checksum on the server and compare the checksums. You will learn about the quality of the file.
If someone undertook to replace the usb socket, it is obvious that you should check not only the charging lines, but also the data transmission line.
From that I would repair the OPO.
Click to expand...
Click to collapse
I did sha256 checksum and it's exactly the same as on the server
https://mirrorbits.lineageos.org/fu...16.0-20191118-nightly-bacon-signed.zip?sha256

Mount System partition
Code:
mount /system
and show:
Code:
grep twrp /tmp/recovery.log
Code:
ls -l /data/media/
Code:
ls -l /data/media/0/
Code:
grep lineage /system/build.prop
Code:
cd /
find . -name recovery*
find . -name *.zip
find . -name *.img
It's not everything. When you're finished we'll go on.

ze7zez said:
Mount System partition
Code:
mount /system
Click to expand...
Click to collapse
I did that
ze7zez said:
and show:
Code:
grep twrp /tmp/recovery.log
Click to expand...
Click to collapse
imageupload
ze7zez said:
Code:
ls -l /data/media/0/
Click to expand...
Click to collapse
This one only shows files and folders from internal memory. Nothing important there
ze7zez said:
Code:
ls -l /data/media/
Code:
grep lineage /system/build.prop
Click to expand...
Click to collapse
ze7zez said:
Code:
cd /
find . -name recovery*
find . -name *.zip
find . -name *.img
It's not everything. When you're finished we'll go on.
Click to expand...
Click to collapse

1. Change /sdcard/recovery.log to a unique name.
2. Make Advanced -> Copy Log (Include Kernel Log)
3. Change /sdcard/recovery.log to a unique name.
4. Make a full backup ROM if you haven't already done so.
5. Wipe -> Advanced Wipe: Dalvik, System, Data, Cache
6. Install lineage without "Reboot after installation is complete".
7. Show messages from the installation terminal.
8. Make Advanced -> Copy Log (Include Kernel Log)
9. Change /sdcard/recovery.log to a unique name.
10. Reboot -> System
??

I did all steps.
After wiping everything and trying to install LineageOS zip I get this (same as before)
When I tried to reboot, TWRP warned me that there are no OS installed. Phone still boots straight to recovery.

eldin90 said:
I did all steps.
After wiping everything and trying to install LineageOS zip I get this (same as before)
When I tried to reboot, TWRP warned me that there are no OS installed. Phone still boots straight to recovery.
Click to expand...
Click to collapse
You have twrp installed for Oneplus 3 (E3004) and you want to upload a ROM for Oneplus One.

ze7zez said:
You have twrp installed for Oneplus 3 (E3004) and you want to upload a ROM for Oneplus One.
Click to expand...
Click to collapse
I have installed TWRP that I downloaded from here
https://forum.xda-developers.com/oneplus-one/development/mod-multirom-v26-t2835738/amp
It's says it's for OnePlus One.
And I used to flash Ubuntu Touch and some older Resurrection Remix and CyanogenMod ROMs with it.

eldin90 said:
I have installed TWRP that I downloaded from here
https://forum.xda-developers.com/oneplus-one/development/mod-multirom-v26-t2835738/amp
Click to expand...
Click to collapse
This is impossible because your TWRP is release 3.1.1-0, which was created after 2017-05-17, which is much later than TWRP from the page you provided.
Show:
Code:
grep fingerprint /sdcard/recovery.log