[Q]Flash stuff using a phone

[Q]Flash stuff using a phone - LG G Watch

Its really a pain in the butt whenever I want to flash system imgs to my watch, either using fastboot or twrp, is there a way to send files to the watch using an android phone or at least adb/fastboot compatible methods...

You can flash with fastboot from a computer with an unlocked bootloader.

Related

[Q] Stuck in HTC startup screen while booting

Well, I have to ask for help right here because Goole/Yahoo/Wiki DIDN'T help. Although it's a bit long but please read it
Here's my problem:
At the last time that my phone is still being functional, I was playing the game "Contract Killer" and "Facebook", "Internet" were running in the background.
Suddenly, it shut off with showing "power off...(Sth like that). This is obviously a normal situation when the battery is out of power. I took it to charge as usual and went to sleep.
Next day, I waked up and tried to boot up my HTC EVO 3D...
First time: Stuck in the startup screen without playing the HTC opening sound track( The phone used to be in Silent Mode)
Second time: I pulled out the battery and put it back and boot again. Still stuck in the startup screen but this time it play the HTC opening sound track...
I've got a lot data in the internal memory and I've never BACKUP before.....
Is there anyway that can boot up my phone without losing the data???
Oh...my phone has never been rooted.

Anyone know the problem??? (

I dunno, kinda sounds like a Hard Reset/Factory Reset is in order. Did you take the battery out for a while and then try to reboot?

There's no way unless u can take to service provider an have them extract it
Sent from my PG86100 using XDA App

i had that kind of a problem once but i was on a CUSTOM ROM so i'm not sure it will work for you and I'M NOT SAYING this method is THE SAFEST.
so 1st thing i did was.. i panic'd... 2nd, i started googling and when all the signs pointed me to a boot up problem i opened the zipped rom, i extracted the boot.img, connected the phone to the pc in fastboot mode and flashed the boot image. after that it started with no problems, all my data was there. what do anyone else suggest? would it be okay to flash boot.img (stock one) on a stock rom?

I would suggest the following:
If rooted with custom recovery:
1. Pull out the battery
2. Replace the battery, and access recovery and do nandroid backup, you will only need the user data.
3. wipe, wipe, wipe
4. install the ROM you had and let it boot
5. reboot in to recovery and restore you DATA ONLY
If not rooted:
1. Install custom recovery
2. go to rooted instructions
IF this doesn't work you can get the .img files from the forums of the ROM you had or stock if that was what you had and only install the boot.img and system.img and try to see if you get the phone to boot with your data in there.
let me know if anything helps.
PS. There is a great risk that you won't be able to recovery your apps data but lets try and hope for the best.

This sounds like a battery, cable, or AC adapter problem to me. You can get a cheap replacement battery on eBay for a few bucks and see how that works out. Also try different wall pieces, micro USB cables, and power outlets.
If none of that has worked, then you more than likely have a corrupted boot image. You can mount the EMMC (internal flash storage) onto a Linux distribution (like Ubuntu or Fedora) via usb and copy your data to a safe place like a flash drive or HDD. Then do an RUU (there are tutorials on this in the development thread) to restore the phone to stock, then of course pull whatever is needed from the data you saved.
Now if absolutely none of this has worked at all, you have malfunctioning hardware. Your only option at this point is to go to a Sprint store to have your data transferred over to a new replacement phone.
Hope this helped mate.
Sent from a Shooter running Android 4.0.3 via XDA Premium.

megabiteg said:
I would suggest the following:
If rooted with custom recovery:
1. Pull out the battery
2. Replace the battery, and access recovery and do nandroid backup, you will only need the user data.
3. wipe, wipe, wipe
4. install the ROM you had and let it boot
5. reboot in to recovery and restore you DATA ONLY
If not rooted:
1. Install custom recovery
2. go to rooted instructions
IF this doesn't work you can get the .img files from the forums of the ROM you had or stock if that was what you had and only install the boot.img and system.img and try to see if you get the phone to boot with your data in there.
let me know if anything helps.
PS. There is a great risk that you won't be able to recovery your apps data but lets try and hope for the best.
Click to expand...
Click to collapse
First of all, thanks for helping~ I would like to know that will my data lose if install the custom recovery? Seems like a huge risk...
Besides, I am a little confused about using the .img to boot my phone.......

MikeyCriggz said:
This sounds like a battery, cable, or AC adapter problem to me. You can get a cheap replacement battery on eBay for a few bucks and see how that works out. Also try different wall pieces, micro USB cables, and power outlets.
If none of that has worked, then you more than likely have a corrupted boot image. You can mount the EMMC (internal flash storage) onto a Linux distribution (like Ubuntu or Fedora) via usb and copy your data to a safe place like a flash drive or HDD. Then do an RUU (there are tutorials on this in the development thread) to restore the phone to stock, then of course pull whatever is needed from the data you saved.
Hope this helped mate.
Sent from a Shooter running Android 4.0.3 via XDA Premium.
Click to expand...
Click to collapse
I was once using Nokia N900, and it is very easy to flash the rom meanwhile i can keep everything in the emmc remain unchanged! Since ANDROID is based on Linux, I am sure your way will be damn work! Any software or environment would i need to do these stuffs? Thx at all!!
:

All in all, I do care the messages in the phone only. That is what i really want.

Nokiawithandroid said:
All in all, I do care the messages in the phone only. That is what i really want.
Click to expand...
Click to collapse
Well if you can somehow get ADB access to your phone you can try to backup the following file:
/data/data/com.android.providers.telephony/databases/mmssms.db
This is there database that contains all your messages (SMS / MMS).
Flashing the boot.img file is easy, if you have the phone in fastboot (and it indicates the usb connection on the phone too) then you can just flash this way:
fastboot flash boot [location of boot.img]\boot.img
You will not loose any personal data, there that the partition affected by the boot.img is not the same as the one affected by /data. This also apply to the recovery section of the phone, in case you want to load a custom recovery:
fastboot flash recovery [location of recovery.img]\recovery.img
Hope this helps, if you need any more help let us know.

HELLO?

megabiteg said:
Well if you can somehow get ADB access to your phone you can try to backup the following file:
/data/data/com.android.providers.telephony/databases/mmssms.db
This is there database that contains all your messages (SMS / MMS).
Flashing the boot.img file is easy, if you have the phone in fastboot (and it indicates the usb connection on the phone too) then you can just flash this way:
fastboot flash boot [location of boot.img]\boot.img
You will not loose any personal data, there that the partition affected by the boot.img is not the same as the one affected by /data. This also apply to the recovery section of the phone, in case you want to load a custom recovery:
fastboot flash recovery [location of recovery.img]\recovery.img
Hope this helps, if you need any more help let us know.
Click to expand...
Click to collapse
How can i get to access my phone by ADB?
I am totally new for all these...

Nokiawithandroid said:
How can i get to access my phone by ADB?
I am totally new for all these...
Click to expand...
Click to collapse
This can get you acquainted with ADB
http://forum.xda-developers.com/showthread.php?t=1241935
Props to Droidzone for putting it all together.

If not rooted:
1. Install custom recovery
2. go to rooted instructions
IF this doesn't work you can get the .img files from the forums of the ROM you had or stock if that was what you had and only install the boot.img and system.img and try to see if you get the phone to boot with your data in there.
Can i do the above things while i can't get connect USB with my phone - -?

Nokiawithandroid said:
If not rooted:
1. Install custom recovery
2. go to rooted instructions
IF this doesn't work you can get the .img files from the forums of the ROM you had or stock if that was what you had and only install the boot.img and system.img and try to see if you get the phone to boot with your data in there.
Can i do the above things while i can't get connect USB with my phone - -?
Click to expand...
Click to collapse
If you remove the battery off your phone and then you reinsert it back, press PWR+Vol UP to access the bootloader.
While in the Bootloader access fastboot and ensure to have the USB connected. from there, you can run any fastboot command you need, like loading custom recoveries or anything else.

WOW! I am approaching the target. To be clear, fastboot command stands for using ADB access?
AND:"While in the Bootloader access fastboot and ensure to have the USB connected. from there, you can run any fastboot command you need, like loading custom recoveries or anything else." means my phone can connect the computer by using "press PWR+Vol UP to access the bootloader"??? The bloody bootoader??
I am sure i'm almost there!!!!! THANKSSWSSSS

Nokiawithandroid said:
WOW! I am approaching the target. To be clear, fastboot command stands for using ADB access?
AND:"While in the Bootloader access fastboot and ensure to have the USB connected. from there, you can run any fastboot command you need, like loading custom recoveries or anything else." means my phone can connect the computer by using "press PWR+Vol UP to access the bootloader"??? The bloody bootoader??
I am sure i'm almost there!!!!! THANKSSWSSSS
Click to expand...
Click to collapse
Fastboot is a different command center from it counterpart adb. From fastboot you use only commands related to the flashing img files and more.
Just use fastboot /? From the command prompt to see a quick help of all what fastboot can do for you, but the main thing you'll need from this command is the ability yo flash a new boot, and maybe system image to get your phone back up and running.
Sent from my PG86100 using Tapatalk

megabiteg said:
Fastboot is a different command center from it counterpart adb. From fastboot you use only commands related to the flashing img files and more.
Just use fastboot /? From the command prompt to see a quick help of all what fastboot can do for you, but the main thing you'll need from this command is the ability yo flash a new boot, and maybe system image to get your phone back up and running.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Oh..damn.....the voyage is lengthy
What equipment/environment do i need?
My target: 1)Back up the Message Database 2) Run this bloody phone.
Difficulties: 1)S-ON 2)command 3) environment 4) Flashing a new (boot?image?)

megabiteg said:
Fastboot is a different command center from it counterpart adb. From fastboot you use only commands related to the flashing img files and more.
Just use fastboot /? From the command prompt to see a quick help of all what fastboot can do for you, but the main thing you'll need from this command is the ability yo flash a new boot, and maybe system image to get your phone back up and running.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Any thread for that?

[q] help!!!!!! Bricked e3d recovery jacked up stuck in bootloader!!!

For people who came for an answer, here it is.
download android sdk
download fastboot drivers
get clockworkmod img and rename to imgfile.img
put img in adb tools
put adb, adbwinapi, fastboot, and the img file in c:/Android
plug your phone to the computer
enter the bootloader
click on recovery or fastboot doesnt matter since both will now take you to fastboot
goto computer
type in run in start menu
type cmd in run and hit enter
type cd c:\Android
type fastboot boot imgfile.img
you are now in recovery
go to mounts and storage and mount your device as a disk drive
download any rom to your computer doesnt really matter and put in on your sdcard. If you already have a rom on there then just use that.
unmount your phone
go to wipe data/factory reset and when it finishes flash the rom
once rom is done flashing reboot into android again.
your phone is partially fixed
now go to the market (if you flashed cm then flash the gapps.zip) and download "rom manager"
Then click on download clockworkmod 5.0.0.2 or something like that (first option)
Now go to rom manager and restore your backup that u made (If there was 1 before)
now it will be fixed and your bootloader will take u to recovery instead of fastboot when you click recovery xD
thanks xda
I flashed a rom and the rom must have been corrupted or something and now my phone is stuck rebooting and when I try to go to recovery or any option it takes me to fastboot so now my phone is basically bricked

Your phone is not bricked since your still able to turn it on.
Can you enter fasboot USB?
Send from my Evo 3D using Tapatalk

well it doesnt really turn on its a boot loop but whatever and fastboot is weird it doesnt want to work.

If your bootloader is unlocked make sure you flash the boot.img through fastboot and make sure you wipe
Sent from my ADR6425LVW using XDA

fastboot doesnt work I already tried too flash it

Guys please help!!!!!!!!!!!!!!!!!!

What do you mean by fastboot is wierd. Did you pull the battery?

fastboot doent work cmd always says waiting for device

if i click recovery it takes me to fastboot, btw.

Have you tried an ruu?

anobahar said:
fastboot doent work cmd always says waiting for device
Click to expand...
Click to collapse
Do you have the proper drivers installed
Sent from my ADR6425LVW using XDA

Are you S-Off or S-On? If S-Off, download a PG86IMG.zip of a recovery, and use your bootloader to flash recovery. From that point, just restore a backup or reflash a ROM. If you're not S-Off, I'd say you should try running an RUU, since you can't get fastboot to work. But I think you need to relock your device to run an RUU (if you're S on/ HTC Unlocked), so you'd still need fastboot. Do you have a different USB cable to try? I've seen them fail before even though they still work to charge.

k2buckley said:
Are you S-Off or S-On? If S-Off, download a PG86IMG.zip of a recovery, and use your bootloader to flash recovery. From that point, just restore a backup or reflash a ROM. If you're not S-Off, I'd say you should try running an RUU, since you can't get fastboot to work. But I think you need to relock your device to run an RUU (if you're S on/ HTC Unlocked), so you'd still need fastboot. Do you have a different USB cable to try? I've seen them fail before even though they still work to charge.
Click to expand...
Click to collapse
Sounds like the drivers arn't installed right.. Like you said if he is S-ON and relocked he can run a RUU exe if he is CDMA...

If you are s off then you just need to reload another recovery. And then access a backup of a rom! Or just flash a new one. I had a issue just like this yesterday where my recovery was broken for some reason and had to go from twrp. 2.1 back to 1.1.1 and load another rom.
Sent from my PG86100 using xda premium

Well i put the sdcard in a bberry but a pg6img.img in my sdcard but bootloader doesnt do anything

I am cdma, s-off unlocked with revolutionary kernel 1.4

oops not kernel hboot

Ok, fail, i dont think i hav fastboot drivers downloading now

now cmd is stuck on "sending recovery"

Did you place a copy of the img into your fast boot folder and one in your adb tools folder ???
#Root-Hack_Mod*Always\

I ****ed up...

So I relocked my bootloader after upgrading to marshmallow and forgot that I did that..... I tried to flash a stock boot img so I could utilize the ota, and it sort of bricked my tablet. Being a total dumbass I didn't realize that was the problem. Having had a similar issue before on my galaxy s4 where I follow a similar solution. I already have twrp installed, and it was asking for encryption for which there was none. So I wiped data and formatted to get past the encryption. On my s4 I was then able to reinstall the stock firmware and software. However when I tried to push the bootloader to my nexus I got this weird error.. can someone pleeeeeeease spare me and help me out. This tablet is my lifeline for college...
Don't get me in trouble for posting this image please lol, I just don't have enough posts. http ://i67.tinypic.com/v80vwl.jpg[/B][/B]
I figured it out, I was just being dumb. I just needed to use the fastboot commands and not try to use twrp

tdct12 said:
So I relocked my bootloader after upgrading to marshmallow and forgot that I did that..... I tried to flash a stock boot img so I could utilize the ota, and it sort of bricked my tablet. Being a total dumbass I didn't realize that was the problem. Having had a similar issue before on my galaxy s4 where I follow a similar solution. I already have twrp installed, and it was asking for encryption for which there was none. So I wiped data and formatted to get past the encryption. On my s4 I was then able to reinstall the stock firmware and software. However when I tried to push the bootloader to my nexus I got this weird error.. can someone pleeeeeeease spare me and help me out. This tablet is my lifeline for college...
Don't get me in trouble for posting this image please lol, I just don't have enough posts. http ://i67.tinypic.com/v80vwl.jpg[/B][/B]
I figured it out, I was just being dumb. I just needed to use the fastboot commands and not try to use twrp
Click to expand...
Click to collapse
If your able to access the bootloader menu or the fastboot menu, you could flash the stock and would fix the brick,soft brick or boot-loop.
Head to Google developer nexus image. Download the factory image of your devices on your devices. Extract all the files and copy paste the fastboot and adb files. Head to your devices and open the fastboot menu.
Type the following commends to restore your devices if the flashall did not work.
Fastboot oem unlock
Fastboot flash bootloader bootloader....
Fastboot reboot-bootloader
Fastboot erase boot
Fastboot flash boot boot.img
Fastboot erase recovery
Fastboot flash recovery recovery.img
Fastboot erase system
Fastboot flash system system.img (this could take up to 15 minutes, don't do anything to stop the process you can make your devices and a worst state)
Fastboot erase cache
Fastboot flash cache cache.img
Fastboot erase vendor
Fastboot flash vendor vendor.img
Fastboot reboot
This should fix your devices. I did not and it save each time I broke my device or anything similar.
If you want after all that. You can enter the following commends to relock your devices but don't make the same mistake you did before. If you want to avoid that same mistake just don't enter the commends.

What the guy above me said, also pro tip, some times not all the files will extract just keep extracting till all the image files are there.

Softbrick with no custom recovery

I messed up i tried to reflash my phone back to stock from marshmallow rom on the thread here but i lost custom recovery and only thing i can get into is download mode, how can i fix this? I have abd install on my pc got the system image boot and recovery img but don't know what 2 do. Please help

xavier55 said:
I messed up i tried to reflash my phone back to stock from marshmallow rom on the thread here but i lost custom recovery and only thing i can get into is download mode, how can i fix this? I have abd install on my pc got the system image boot and recovery img but don't know what 2 do. Please help
Click to expand...
Click to collapse
Your phone is in fastboot mode, not download mode. Small, but distinct difference.
Since you've installed a custom ROM, your bootloader should be unlocked. However, it may be a good idea to issue the oem unlock command through fastboot anyways. Use "adb reboot bootloader" and "fastboot oem unlock" to ensure that your bootloader is unlocked.
Now, since your phone is in fastboot mode, you can do one of two things: 1. Flash a custom recovery and restore your device to stock, or 2. Flash a custom recovery and continue using a custom ROM. Either way, you will need to install TWRP or another custom recovery image of your choice. The TWRP thread is located here: http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-unofficial-twrp-t3239740 Since you're already in the bootloader/fastboot mode, all you would need to do is download TWRP and use "fastboot flash recovery twrp.img" and then "fastboot boot twrp.img" to install TWRP. Please note that the 'twrp.img' will vary depending on which version you download, it will probably look more like 'twrp-2.8.7.1-h901.img'. You can just rename the file or use the full file name in the fastboot commands.
Once in TWRP, you can flash whatever ROM you want. To restore your phone to stock, go to this thread and flash the .zip in TWRP http://forum.xda-developers.com/tmo.../lg-h901-stock-images-device-restore-t3241170 after doing the standard wipe procedure. :good:

soltheman said:
Your phone is in fastboot mode, not download mode. Small, but distinct difference.
Since you've installed a custom ROM, your bootloader should be unlocked. However, it may be a good idea to issue the oem unlock command through fastboot anyways. Use "adb reboot bootloader" and "fastboot oem unlock" to ensure that your bootloader is unlocked.
Now, since your phone is in fastboot mode, you can do one of two things: 1. Flash a custom recovery and restore your device to stock, or 2. Flash a custom recovery and continue using a custom ROM. Either way, you will need to install TWRP or another custom recovery image of your choice. The TWRP thread is located here: http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-unofficial-twrp-t3239740 Since you're already in the bootloader/fastboot mode, all you would need to do is download TWRP and use "fastboot flash recovery twrp.img" and then "fastboot boot twrp.img" to install TWRP. Please note that the 'twrp.img' will vary depending on which version you download, it will probably look more like 'twrp-2.8.7.1-h901.img'. You can just rename the file or use the full file name in the fastboot commands.
Once in TWRP, you can flash whatever ROM you want. To restore your phone to stock, go to this thread and flash the .zip in TWRP http://forum.xda-developers.com/tmo.../lg-h901-stock-images-device-restore-t3241170 after doing the standard wipe procedure. :good:
Click to expand...
Click to collapse
I'm kinda in the same boat now except that I already received the replacement device. Need to re-lock the old V10, but adb won't recognize my device at all. Any more option when that's the case? I can get into both download mode and fastboot. Phone is recognized by LGUP in download mode, but not by adb in fastboot mode for some reason.
(I've verified connection and driver using the other V10, the other V10 is recognized just fine)

baymon said:
I'm kinda in the same boat now except that I already received the replacement device. Need to re-lock the old V10, but adb won't recognize my device at all. Any more option when that's the case? I can get into both download mode and fastboot. Phone is recognized by LGUP in download mode, but not by adb in fastboot mode for some reason.
(I've verified connection and driver using the other V10, the other V10 is recognized just fine)
Click to expand...
Click to collapse
Yep. Your phone boots and everything, correct? Just factory reset it (Settings > Backup & Restore > Factory data reset). After its been reset, unlock it, turn on Developers Options, and enable USB debugging. After usb debugging is turned on, connect the v10 to your PC and be sure to hit "Always allow" when prompted by your phone. ADB should now be able to see your device.
If you can't get it to boot up, try restoring through LG UP/Bridge. I don't use any of LG's software, so I'm not sure what those apps can do and whether or not you'll be able to restore through them.
If nothing else, your phone is recognized in fastboot mode, so you can always manually flash the stock system images as well. You want to use the "fastboot flash boot boot.img", "fastboot flash recovery recovery.img", and "fastboot flash system system.img" commands After downloading the stock system images located in this thread: http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-img-files-boot-recovery-t3238638
If you haven't ever flashed system images from fastboot, please read this first, as I am not responsible if your phone turns into a paperweight! https://developers.google.com/android/nexus/images#instructions While the instructions are for nexus devices, it works pretty much the same, except you'd want to use the individual commands instead of a flash-all script.
Hope this helps!

soltheman said:
Yep. Your phone boots and everything, correct? Just factory reset it (Settings > Backup & Restore > Factory data reset). After its been reset, unlock it, turn on Developers Options, and enable USB debugging. After usb debugging is turned on, connect the v10 to your PC and be sure to hit "Always allow" when prompted by your phone. ADB should now be able to see your device.
If you can't get it to boot up, try restoring through LG UP/Bridge. I don't use any of LG's software, so I'm not sure what those apps can do and whether or not you'll be able to restore through them.
If nothing else, your phone is recognized in fastboot mode, so you can always manually flash the stock system images as well. You want to use the "fastboot flash boot boot.img", "fastboot flash recovery recovery.img", and "fastboot flash system system.img" commands After downloading the stock system images located in this thread: http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-img-files-boot-recovery-t3238638
If you haven't ever flashed system images from fastboot, please read this first, as I am not responsible if your phone turns into a paperweight! https://developers.google.com/android/nexus/images#instructions While the instructions are for nexus devices, it works pretty much the same, except you'd want to use the individual commands instead of a flash-all script.
Hope this helps!
Click to expand...
Click to collapse
Thanks for the follow up! No the phone would not boot at all and kept stuck at boot loop. I ended up just doing the OEM Lock and call it a day, the old device just won't boot to anything at this point.
I tried fastboot flash recovery recovery.img but it's giving some kinda kernel panic message and I was never able to get into recovery. This reminds me of the time when my Note 3 eMMC was fried, it wouldn't give a device ID to adb.

I think I am in the same boat too. I've been OEM unlocked yet recently my phone won't keep the TWRP recovery and keeps putting me into bootloop. I can't install a ROM and only thing I can do is fastboot mode. What did you do OEM lock the device? I am hoping that solution will get rid of that message bootloader unlocked during the bootloop and then I can try and get it serviced.

Unbricking a OnePlus X

Hi guys!
I´m kinda desperate right now. I ****ed up and when drunk I uninstalled OxygenOs and tried to update my recovery and I bricked my phone.
The phone right now can´t boot into the recovery (Volume down + power does nothing) but I can boot into fastboot mode. Also booting normally does nothing since no OS is installed.
Is there any way/guide to maybe solve this? I tried to follow the Hard Unbrick guide but can´t make it work (The pressing volume up step does nothing).
I apologize in advance because I imagine that this might already be posted by other people.
Thank you in advance,
craked5!

Just simply:
1.boot into fastboot mode
2. Download Recovery eg. TWRP
3. Connect phone to pc
4. In command line type (make sure you have fastboot drivers installed)
fastboot flash recovery recovery.img
recovery.img must be the name of your recovery file name.
After that you have working recovery

This is a link to both unbrick mini and full with some instructions.
https://goo.gl/zYnkQ1

What if the bootloader was never unlocked and you are in the same situation? A friend sent me his plus X to see of I could get it going again. It can only boot to fastboot. No recovery, and apparently no OS. I'm not even sure what they wetter trying to do with the device since he is not that savvy with adb or fastboot. . I just want to get the device back to stock for him.
I ran the command "fastboot oem device-info" and from what I can see the bootloader was never unlocked.
Sent from my A0001 using XDA Premium HD app

glockman4519 said:
What if the bootloader was never unlocked and you are in the same situation? A friend sent me his plus X to see of I could get it going again. It can only boot to fastboot. No recovery, and apparently no OS. I'm not even sure what they wetter trying to do with the device since he is not that savvy with adb or fastboot. . I just want to get the device back to stock for him.
I ran the command "fastboot oem device-info" and from what I can see the bootloader was never unlocked.
Sent from my A0001 using XDA Premium HD app
Click to expand...
Click to collapse
Mega Unbrick Guide is your only option....

That's what I thought. It's toast then...lol.. My guess is someone didn't check the OEM unlock switch in developers options and then tried following some guide some where. These phones are so easy to work with. But to screw this device up this bad is messed up. Thanks for your help.

Better Mobile App

welcome