Database Info

[Q] Modding From A to B Guide?

Sorry to sound pig ignorant about phones but I am ... my expertise is in PCs. So anyway I want to upgrade the Hero with CyanogenMod.
I backed up my contacts, apps, etc and rooted the phone with unrevoked ... lost everything in memory in the process, but that's OK -- the important stuff is backed up.
Rebooted into stock 21. ROM and skipped all the new user stuff ...
OK, here's where I'm lost ... to load the CyanogenMod ROM I apparently need something like Amon-RA, but to load Amon-RA image file I need to install the SDK pack.
So I downloaded the SDK pack, but it is nothing like what is described in all the install SDK posts I've been able to find. What I have found are instructions about running ASroot and other files that don't exist in the SDK version I have.
So like what do I do now, more important ... is there an A to B thread for doing this mod starting from a stock phone, going to unlocking, than loading SDK, than installing Amon-RA (or equivalent) and than installing CyanogenMOD.
I know all this info is out there, but it seems like most of the files I've found don't interface well in the sense that the ones that talk about doing step one aren't terribly relevant to ones that talk about step 2, etc.
Thanks

Yes. Its a sticky at the top of the page. Search "guides" lol...
Sent from my HERO200 using XDA App

All you need to do with the sdk is download it and extract it. I just put it in the root of my C: drive. Then open a cmd prompt in windows by going to Start > Run > cmd (press enter). Then in the command prompt you need to change directories to the sdk folder you extracted. For example, mine is in C:\android-sdk-windows. I just type "cd c:\android-sdk-windows" then "cd tools" to get into the directory where you can run the adb program. Make sure your phone is in debugging mode by going to settings > applications > development > check the USB Debugging box. Then you can hook the phone up to the usb and run the command "adb devices". If everything is working correctly then you should see a device serial number show up. If that doesn't work make sure you have the htc drivers installed by downloading htc sync from their website and installing it.
Once adb can see the phone then you should run the command "adb shell" and then when you get a $ prompt type su in order to elevate to root. Make sure you put a recovery image on the phones sd card using step 4 from this guide: http://forum.xda-developers.com/showthread.php?t=694572 I think he has a link to download the recovery in that guide but just in case here is a direct download link for the recovery: http://www.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-heroc-v1.6.2.img Feel free to rename it to recovery.img so that the commands in the guide can be used as is.
Now you should be able to start at step nine from the guide in that thread (you should be in an adb shell when you start). It should be the adb command to flash a recovery image. Once you do that installing roms is as simple as putting them on your sd card and booting into recovery to select the flash option.

How do i root with adb?

Hello, i just got my new samsung 7 plus with honeycome 3.2 and im loving it
I want to know what is the step by step instruction to rooting my device using adb?
the root.zip i found on here dont work for me. when i save the file to /sdcard and n reboot n go into wher i applie the zip from sdcard it shows no files at all on my card. i bought the 16gb version of this tab so i dont have the externel sdcard. i thought that i read one the forum you can only use the externel card not the interel. i believe they added the folder /sdcard to the internel drive and thats why it not viewing.

The rooting instructions say to put it on an "external" sdcard for a reason as recovery will not recognize the internal storage. Do you have adb installed on your computer and at least know how to use it? If not it is going to be way easier for you to just go and spend the $10 for an 8 GB sdcard and install it that way.
I can at least get you part way, installing the sdk and jdk. Here are the instructions for installing the android sdk (adb) direct from google. You also need the java jdk installed on your commputer and google has a link in their instructions.
http://developer.android.com/sdk/installing.html
You first need the proper usb drivers installed and not exactly sure on how to do that. I already had the android usb drivers installed on my computer for my phone and I just let the compter install whatever else it needed the first time I connected my tab to it.
You will need usb debugging turned in your settings and then power the tab off. You would then plug the usb cable into the tab and computer then boot it into recovery. Once into recovery Mount/System. You then run adb in a command window and change the drive to the platform-tools directory where adb resides. It would look something like this in a command window (c:\android-sdk-windows\ is how I set my computer up yours may be different):
cd c:\android-sdk-windows\platform-tools
To check and see if your device is recognized by adb run the command:
adb devices
If nothing is listed then adb isn't recognizing the device and you would need to troubleshoot your installation or boot method.
As far as installing the root.zip file I'm not sure as I've never had to do that before as I've always had an external sdcard on my devices. Maybe someone else can take you thru the last step. I believe all you would do is push the file inside the zip folder over to the tab. The su file inside the root.zip folder needs to be in the same directory as adb, platform-tools directory.
adb push su /system/bin
I'm not sure if you need to change permissions on this file or not and that is done thru a chmod command in adb shell but not sure of the proper code to use for the GTab to do this. For my phone setting permissions looks like this:
adb shell
cd /system/bin
chmod 0644 Su
exit
Do not use this chmod as I'm not sure it will work on the GTab or what it will do to it, it just an example.

In summary these are the basic steps you are trying to accomplish:
1. Install Java JDK
2. Install Android SDK
3. Install USB drivers
4. Turn USB debugging on in Tabs settings
5. Boot Tab into recovery while connected to PC
6. Mount/System in recovery
7. ADB push su file to system/bin
8. Set permissions of su???
9. Exit adb
10. Reboot phone and install superuser and busy box from market

Thanks im rooted now. I took the sdcard out of my droidx & it works on my galaxy tab & i used the root.zip file.
Sent from my GT-P6210 using Tapatalk

ronlsjr said:
Thanks im rooted now. I took the sdcard out of my droidx & it works on my galaxy tab & i used the root.zip file.
Sent from my GT-P6210 using Tapatalk
Click to expand...
Click to collapse
Yes any sdcard will do and that is the easiest way. Though I think everyone should learn how to use adb anyways as it is useful especially if you get into modding.

Yes i do want to learn how to use adb. My desire is to become a developer.
Sent from my GT-P6210 using Tapatalk

Just follow the link I provided previously to the android developers site and follow the instructions. You will first have to have Java JDK installed and a link to that is provided on the android developers website in the link. Once JDK is installed download and install the SDK. It will only put the basic functions onto your computer and you will have to install the rest through SDK Manager, this can take a while, up to an hour or so depending on what packages you want to install. At the minimum you would want the Android 3.2 API (GTab 7+ uses this) and the Google USB drivers and then any other API's for phones you may have. I myself installed all the API's as my first phone had Donut (Android 1.6).

I know this may be a stupid question but why root? what special features does it give you? I am not sure If I want to or not.

Anyone? I'm just curious if I should flash a ROM on here or not I just don't know why because it works fine now after the SwiftKey x and other little apps
Sent from my SGH-T869 using XDA Premium App

don't get confused by the lingo...
Noah321 said:
Anyone? I'm just curious if I should flash a ROM on here or not I just don't know why because it works fine now after the SwiftKey x and other little apps
Sent from my SGH-T869 using XDA Premium App
Click to expand...
Click to collapse
There's a difference between "flashing a ROM" and "adding root access".
A custom ROM implies someone has taken the stock software infrastructure, altered/tailored/customized it, and packaged it for others to easily use.
"Rooting" a device just simply gives you access to certain folders, permissions, files, etc.
It's like giving yourself Admin Rights to your work computer (assuming you're over 18 and/or working).
It allows you to do things that the manufacture probably didn't want you to do - like delete "bloatware" (unwanted apps).
If helpful, click "Thanks"

100$ to whoever can help me solve this (NO JOKE)

i have already checked xda for a solution but couldnt find one i even checked google and youtube and still found nothing i am in need help bad. i will even pay someone paypal if they can help me with my phone
i downloaded the matrix rom and i liked it but i wanted to go back to ice cream sandwhich for the day so when i tried to go to recovery it froze on the google screen while trying to get to recovery i kept trying and trying but my recovery wasnt working i couldnt get to it. so i went to titanium back up and clicked un-install all system and data because i thought it was when i restored all system and data from ICS but after i did the uninstall i kept getting a force close alot of things and i got all the way down to one and it was process.android i think and everytime i clicked force close it popped right bacj up instently. so i took out the battery and put it back in and now i cant power on my phone it gets stuck on the matrix screen. can you please help me i can only acces the volume up power button menu.
*solved*

Fastboot OEM lock. Fastboot OEM unlock and start the process all over again. Also wipe everything 3 times.
Including system and boot.
Also double check you're installing all the compatible zips.
Sent from my Nexus S using xda premium

it wont let me do any of that it keeps saying waiting for device then gets stuck on that ive installed pdanet but it keeps giving me a htc sync error =1 and my bootloader and everything was already unlocked i dont know what to do i cant turn my phone on or get to recovery. thats why im paying 100 dollars to anyone who can help me restore my phone and make sure its up and running ive been trying for 2 days now and thats my work phone and everything im stressed

Serious_Beans said:
Fastboot OEM lock. Fastboot OEM unlock and start the process all over again. Also wipe everything 3 times.
Including system and boot.
Also double check you're installing all the compatible zips.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
when i turn on the phone and it keeps trying to load the matrix animation the phone still connects with my computer and says removable disk f but when i try and click on it. it says please insert a disk into removable disk f

Hmm uninstall all the USB drivers and reinstall them
Sent from my Nexus S using xda premium

Serious_Beans said:
Hmm uninstall all the USB drivers and reinstall them
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
at the bottom of my phone screen it says fastboot statud - FAILInvalid command

If you have the SDK installed on your computer. Here is what you need to do in order to get back into recovery.
#1 Boot your phone into bootloader, Vol up and power
-Plug into computer using usb while in fastboot(bootloader) and see if it recognizes it. Type adb devices it should list a serial number for your device.
( My SDK is installed in c:\android\) so you would type something like cd c:\android\tools and hit enter and then type adb devices )
#2 If you have installed sdk and pdanet drivers and your computer still does not see your phone in fastboot is this. Go to the folder where sdk is installed and copy everything excluding the folders that is in the Platform-tools folder into the tools folder. After that download Stock Phone files unzip it into a folder on desktop.
Dont run the script yet, what you have to do is after you unzip the stock look in the folder you just unzipped them in and you should see a file called fastboot, adb, and some other .dll's AdbWinApi.dll and etc move only these 4 files to your sdk tools folder.
#3 Now re open a cmd prompt and go back to c:\android\tools (enter) then type in adb devices and your computer should recognize it this time around.
Then all there is left to do is download the recovery of your choice here's mine Recovery and after you download it rename it recovery. After you rename it move it to sdk tools folder and while still in fastboot(bootloader) type in fastboot flash recovery recovery.img
You should now be able to enter recovery and flash roms again
EDIT #1
If you havent setup SDK here is a wiki guide on how to do so http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK

Make sure you are using the most up to date drivers and then use ADB to install recovery again. If I'm understanding it right I think that's what you need to try.
Sent from my Supercharged MikG'd up EVO 4g while eatin some Chop Suey.
Hit that thanks button if I managed to help.

Envynet said:
If you have the SDK installed on your computer. Here is what you need to do in order to get back into recovery.
#1 Boot your phone into bootloader, Vol up and power
-Plug into computer using usb while in fastboot(bootloader) and see if it recognizes it. Type adb devices it should list a serial number for your device.
( My SDK is installed in c:\android\) so you would type something like cd c:\android\tools and hit enter and then type adb devices )
#2 If you have installed sdk and pdanet drivers and your computer still does not see your phone in fastboot is this. Go to the folder where sdk is installed and copy everything excluding the folders that is in the Platform-tools folder into the tools folder. After that download Stock Phone files unzip it into a folder on desktop.
Dont run the script yet, what you have to do is after you unzip the stock look in the folder you just unzipped them in and you should see a file called fastboot, adb, and some other .dll's AdbWinApi.dll and etc move only these 4 files to your sdk tools folder.
#3 Now re open a cmd prompt and go back to c:\android\tools (enter) then type in adb devices and your computer should recognize it this time around.
Then all there is left to do is download the recovery of your choice here's mine Recovery and after you download it rename it recovery. After you rename it move it to sdk tools folder and while still in fastboot(bootloader) type in fastboot flash recovery recovery.img
You should now be able to enter recovery and flash roms again
EDIT #1
If you havent setup SDK here is a wiki guide on how to do so http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
Click to expand...
Click to collapse
can someone help me threw team viewer and just access my computer threw that and help me that way

Envynet said:
If you have the SDK installed on your computer. Here is what you need to do in order to get back into recovery.
#1 Boot your phone into bootloader, Vol up and power
-Plug into computer using usb while in fastboot(bootloader) and see if it recognizes it. Type adb devices it should list a serial number for your device.
( My SDK is installed in c:\android\) so you would type something like cd c:\android\tools and hit enter and then type adb devices )
#2 If you have installed sdk and pdanet drivers and your computer still does not see your phone in fastboot is this. Go to the folder where sdk is installed and copy everything excluding the folders that is in the Platform-tools folder into the tools folder. After that download Stock Phone files unzip it into a folder on desktop.
Dont run the script yet, what you have to do is after you unzip the stock look in the folder you just unzipped them in and you should see a file called fastboot, adb, and some other .dll's AdbWinApi.dll and etc move only these 4 files to your sdk tools folder.
#3 Now re open a cmd prompt and go back to c:\android\tools (enter) then type in adb devices and your computer should recognize it this time around.
Then all there is left to do is download the recovery of your choice here's mine Recovery and after you download it rename it recovery. After you rename it move it to sdk tools folder and while still in fastboot(bootloader) type in fastboot flash recovery recovery.img
You should now be able to enter recovery and flash roms again
EDIT #1
If you havent setup SDK here is a wiki guide on how to do so http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
Click to expand...
Click to collapse
Dang you must have put this up like 2 second before I posted mine lol
Sent from my Supercharged MikG'd up EVO 4g while eatin some Chop Suey.
Hit that thanks button if I managed to help.

Maybe you should just try Odin.
http://forum.xda-developers.com/showthread.php?t=1022481
DL: http://droidangel.blogspot.com/2011/05/odin-multi-downloader-flasher-program.html
Greetz

OP... check your PM inbox.

Why on earth have you posted this thread 6 times? Lol
Sent from my Nexus S using XDA App

scottypeterson said:
Dang you must have put this up like 2 second before I posted mine lol
Sent from my Supercharged MikG'd up EVO 4g while eatin some Chop Suey.
Hit that thanks button if I managed to help.
Click to expand...
Click to collapse
after i type adb it says adb isnt recognized as a internel or external cammand operable program or batch file

Ok I don't know if you tried this already but do this:
1. download the recovery img from here:
http://wiki.cyanogenmod.com/wiki/Ne...de#Installing_the_ClockworkMod_Recovery_Image
and put it somewhere on ur computer
2. plug phone into comp
3. boot the phone into the fastboot mode with the android guy
4. fastboot erase recovery
5. fastboot flash recovery ____.img
and if you can boot into recovery now, just wipe data, cache, and dalvik cache and flash the ics rom
see if that helps

mathkid95 said:
Ok I don't know if you tried this already but do this:
1. download the recovery img from here:
http://wiki.cyanogenmod.com/wiki/Ne...de#Installing_the_ClockworkMod_Recovery_Image
and put it somewhere on ur computer
2. plug phone into comp
3. boot the phone into the fastboot mode with the android guy
4. fastboot erase recovery
5. fastboot flash recovery ____.img
and if you can boot into recovery now, just wipe data, cache, and dalvik cache and flash the ics rom
see if that helps
Click to expand...
Click to collapse
I suggested this about 7 hours and 3 threads ago.. I think the problem is either he doesn't have the proper drivers or SDK setup properly.
Da_Reaper said:
after i type adb it says adb isnt recognized as a internel or external cammand operable program or batch file
Click to expand...
Click to collapse
This leads me to believe that SDK isn't set up properly. If it's set up correct you should be able to access adb without the phone even connected.

Yes thank you guys i love u all

check your mp , excepted if you found the solution.

$100? Lol
Sent from my Nexus S using XDA App

crump84 said:
I suggested this about 7 hours and 3 threads ago.. I think the problem is either he doesn't have the proper drivers or SDK setup properly.
This leads me to believe that SDK isn't set up properly. If it's set up correct you should be able to access adb without the phone even connected.
Click to expand...
Click to collapse
Yeah excuse me for not reading all 6 threads
Sent from my Nexus S using XDA App

[Q] Root Xoom with linux ?

i ditched windows ages ago and i will never look back i am sick and tierd of waiting on moto uk to push ics. i use to have the dell streak and i rooted that but i was on windows then how do i root my xoom with linux mint is it possible and can any point me in the right direction please

Stand by, I will give you all the tools and options you need to do so, I could draft something tomorrow morning.
Sent from my PG86100 using Tapatalk

Thank you megabiteg Still learning linux but i Love it
megabiteg said:
Stand by, I will give you all the tools and options you need to do so, I could draft something tomorrow morning.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse

well, it isn't that hard since everything you really need on your computer ist fastboot and a way to push a file to an sdcard (fat formatted)...
Just go here, download and install the android sdk from there. Make sure the commands adb and fastboot are in your path. (test by issuing adb devices, shold return a list of attached android devices with usb debugging turned on)
After that, just follow these instructions. I am not sure if you need to run fastboot as root, but you'll see

Cheers for the info just by any chance do you know the commands still learning Linux
llama-power said:
well, it isn't that hard since everything you really need on your computer ist fastboot and a way to push a file to an sdcard (fat formatted)...
Just go here, download and install the android sdk from there. Make sure the commands adb and fastboot are in your path. (test by issuing adb devices, shold return a list of attached android devices with usb debugging turned on)
After that, just follow these instructions. I am not sure if you need to run fastboot as root, but you'll see
Click to expand...
Click to collapse

elsworth1983 said:
Cheers for the info just by any chance do you know the commands still learning Linux
Click to expand...
Click to collapse
thought you ditched windows ages ago?
anyhow... don't have linux set up atm, so this will from memory and might contain some errors... Also, never tried mint, I always stuck to debian or debian-derivates...
anyhow, lets try this:
first, use your package management-system to install a jre (java runtime environment.
If that is set up, install the android sdk:
Code:
$ cd ~
$ wget http://dl.google.com/android/android-sdk_r17-linux.tgz
$ sudo su
[enter your su-password]
# cd /usr/local
# tar xfzv ~[yourusername]/android-sdk_r17-linux.tgz
# ./android-sdk-linux/tools/android
a window should open up and list some files available for download. Just select "Android SDK Platform-tools" and hit "Install 1 package...".
once that's finished (might take a while), close the Android SDK Manager and you should get back to your shell.
Code:
# ln -s /usr/local/android-sdk-linux/platform-tools/adb /usr/local/bin/adb
# ln -s /usr/local/android-sdk-linux/platform-tools/fastboot /usr/local/bin/fastboot
# exit
$ rm android-sdk_r17-linux.tgz
now, connect your xoom to your computer and enable usb debugging in the settings of your xoom. If you issue adb devices, you should get something like
Code:
List of devices attached
043c12343456476547 device
if you receive something like bash: adb: command not found, something went wrong somewhere. Try the same using sudo: sudo adb devices if that doesn't fix it please write another post.
Also, if you encounter an error after entering any of the comments above, please do not continue until you resolved that error. (For example ask for a solution here)
And, since you are still learning to use linux: whenever instructions contain a $ or # at the beginning of a line, DO NOT ENTER THESE. They are just there to tell you to issue that command as normal user ($) or superuser (#)
/EDIT: btw: there may be an easier way to do this if you just want to use adb/fastboot this once: you could try to simply download the adb and fastboot- binaries and put these into the folder with your recovery.img-file. Might work, not sure about that, though. Also, since I don't have linux installed on my machine atm, I can't provide you with a link to these binaries.

cheers for all your help will give this a go "Dont want to back to windows

Android SDK manger log
Error Stopping ADB server failed (code-1)
Connected the xoom and did adb devices and it listed the xoom with no errors in the terminal Thank you again ? Were do i go from here now

glad to read it's working
just follow the instructions in this thread That will help you to install a custom recovery and root your xoom. It will not, however, install a custom rom. To do that, you'd also need to download a custom rom (usually comes in a flashable .zip-file), place that on an acutal sd-card which you're gonna put into your xoom, and install that file from within the custom recovery. Just make sure you grab a rom that works with your xoom (for example, you shouldn't put a us-4g-rom onto a wifi-only-xoom and vice versa)

have i done something wrong
god-WE174AA-ABU-s5306uk god # adb reboot bootloader
god-WE174AA-ABU-s5306uk god # fastboot oem unlock
fastboot: command not found
The problem i seem to be having is when the xoom is on i type <adb reboot bootloader> The xoom reboots to the fastboot screen after that no commands work and when i do ADB devices in the terminal the device list is empty ?

elsworth1983 said:
have i done something wrong
god-WE174AA-ABU-s5306uk god # adb reboot bootloader
god-WE174AA-ABU-s5306uk god # fastboot oem unlock
fastboot: command not found
Click to expand...
Click to collapse
have you done the # ln -s /usr/local/android-sdk-linux/platform-tools/fastboot /usr/local/bin/fastboot? The error you're getting seems to suggest that it can't find the fastboot application? What happens if you type /usr/local/android-sdk-linux/platform-tools/fastboot oem unlock?
elsworth1983 said:
The problem i seem to be having is when the xoom is on i type <adb reboot bootloader> The xoom reboots to the fastboot screen after that no commands work and when i do ADB devices in the terminal the device list is empty ?
Click to expand...
Click to collapse
that is expected. adb is only available while android is booted up, fastboot is the protocol to use while in bootloader mode. As indicated before, I suspect that your computer can't find the fastboot application (on the computer).

Cheers for all the info i went back and started all from the top again only thing i am struggling with is Flashing the recovery now lol i get
god-WE174AA-ABU-s5306uk god # adb reboot bootloader
god-WE174AA-ABU-s5306uk god # fastboot flash recovery recovery-solarnz-100611-1150.img
error: cannot load 'recovery-solarnz-100611-1150.img'
I have it on a memory card which i checked which was working

elsworth1983 said:
Cheers for all the info i went back and started all from the top again only thing i am struggling with is Flashing the recovery now lol i get
god-WE174AA-ABU-s5306uk god # adb reboot bootloader
god-WE174AA-ABU-s5306uk god # fastboot flash recovery recovery-solarnz-100611-1150.img
error: cannot load 'recovery-solarnz-100611-1150.img'
I have it on a memory card which i checked which was working
Click to expand...
Click to collapse
The recovery image needs to be on your pc. It doesn't matter where on your pc as long as you can access it and know where it is.
Fastboot works by sending the image over the usb cable. Once you start flashing roms, those will need to be on your sd card within the xoom.

all i can say is thank you for all the information every 1 is giving me my head is mashed lol so if i put recovery-Tiamat-R4c-100611-1150-cwm.img on the desktop what would the terminal code be
kofrad said:
The recovery image needs to be on your pc. It doesn't matter where on your pc as long as you can access it and know where it is.
Fastboot works by sending the image over the usb cable. Once you start flashing roms, those will need to be on your sd card within the xoom.
Click to expand...
Click to collapse

depends on where your desktop is If it is in ~/Desktop/, then the correct command should be
Code:
fastboot flash recovery ~/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img

error: cannot load '/root/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img'
ARRRR i am really loosing the will to live ;-)

What am doing so wrong its lucky am not bold yet been trying this all day

elsworth1983 said:
error: cannot load '/root/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img'
ARRRR i am really loosing the will to live ;-)
Click to expand...
Click to collapse
if the graphical interface, where do you see the file located?

elsworth1983 said:
error: cannot load '/root/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img'
ARRRR i am really loosing the will to live ;-)
Click to expand...
Click to collapse
Sounds to me like you are running the commands as root. You likely have also downloaded the recovery image as a normal user. This means the '~' shortcut for the home directory is pointing you to someplace where the file is not.
Try using "fastboot flash /home/Your username/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img"

I have put the file on the desktop ? is that what u mean

How to fix a soft bricked device from a flash that failed due to missing files

This guide is meant to less techie people, and written in detail. Please don't mind me if I overexplain. If you have any questions, feel free to comment them.
Also, I am not responsible for anything you do to your phone; you assume your responsibility for anything you do because of this guide.
Scenario:
So, lets say that you tried to flash an zip file on your android using sideload, but the zip required another file to be in the same directory as it, in order to work.
After flashing the zip and getting an error, your phone may not get pass the logo of the brand and be soft bricked.
Also, you formatted your external sd as internal, and cant access your usual location with files in the recovery.
In this case, don't worry, as I'm here to help you unbrick your phone without reinstalling the rom.
Things you will need:
your phone
a computer connected to your phone with an usb cable
the proper drivers for your phone
a custom recovery like cwm or twrp installed on your phone
probably root, although I'm not sure
and finally the adb (android development bridge) utility
Where to get a custom recovery?
- https://www.xda-developers.com/how-to-install-clockworkmod/
or search on xda under at your device's forum
Where to download adb from?
- https://forum.xda-developers.com/showthread.php?t=2588979 (this one comes with the drivers)
- https://dl.google.com/android/repository/platform-tools-latest-windows.zip (just the adb files)
So lets get started:
First, get your phone into Recovery mode (on samsung hold power button volume up and home button), and connect it to your pc with a usb cable.
Open ADB by shift + right clicking the folder platform-tools in witch it is located. Click on "Open Command Prompt window here" or "Open Powershell window here" (depends on your windows settings).
You need to find a location on your phone that is accessible through the flash zip menu from your recovery. (from sdcard / from sdcard1 or whatever your external sd is called)
In my case, i could get to see folder 0 and obb from "flash zip from sdcard".
To find a suitable folder:
In the window, type
Code:
adb.exe shell
if you opened cmd, or
Code:
./adb.exe shell
if you opened powershell.
This will open a terminal that will run commands on your phone.
(Now you can type commands in the cmd window that will be run on your phone.)
Type in
Code:
cd /sdcard/0
to go to the main sd card location that is accessible in recovery when you go to flash a zip from there. (if you can get to another folder where you could a flash a zip from, change the location to that place)
You can use here the command
Code:
ls
to view objects in the folder you are in.
After you are done, type
Code:
exit
to exit.
To solve the soft-brick, you need to reflash the zip, but with the files it needed in the same directory.
Type in the ADB window
Code:
./adb.exe push "location of the file you are sending" "location of the folder you are sending to (eg. /sdcard/0)"
if you are in powershell, or without the ./ if you are in cmd.
Use this until you have sent all the files needed for a successful flash.
Then just use the "flash zip" utility from your recovery with the location you have sent the files to, on your phone, to complete the flash, and solve the half-brick.
Restart your phone and you should be good to go.
Thanks to the following threads, that helped me put this together, and solve this problem on my phone:
https://forum.xda-developers.com/showthread.php?t=1927198
https://forum.xda-developers.com/showthread.php?t=2588979​