Hi all!
I have an Samsung A725F but After a new update official Is bricked on start up (Samsung logo), I don't want reset the phone (reset factory), can I have unlock the bootloader without root?
- I have the access on recovery
- I have the access on download mode
- I have the access on adb (from recovery mode-update from adb)
When I go in adb mode on CMD Shell the devices is on sideload(adb devices) but I don't can nothing.
Pls help me.
Am very sorry...the only solution is to loose all data by factory reset that's the only option left . And it's not normal to hang on logo after update
You can download the whole firmware and flash it with Odin. Instead of CSC_, flash the HOME_CSC file so that you don't lose your data. See if that works.
Related
I tried to root my tablet and after I installed TWRP, my friend wiped the device by accident including the system which leaves me without an OS.
We cannot access the recovery mode and we are stuck at the fastboot mode. The tablet also does not show up on the computer when plugged in via USB. Anyone know the solution?
http://techerrata.com/browse/twrp2/flo
fastboot erase recovery
fastboot flash recovery openrecovery-twrp-2.7.1.1-flo.img
And then flash anything you want.
Or use Toolkit http://www.wugfresh.com/nrt/
Check soft bricked/bootloop and "flash to stock + unroot"
Hello i open fastboot to 'unlocked' and my phones slowed down. I have tried everything (xda and google search methot etc.) i cant recovery back. Is there working methot for 6.0 marshmallow, can you help me?
Phone: HTC Desire Eye
Android: 6.0
Fastboot: Unlocked (How do turn lock?) Please help me.
Note: and i cant factory reset now its not working, i cant use trwp recovery (need root).
This forum is so dead, I wonder if we can get more help from One M8
You mean "bootloader", not "fastboot".
To lock (relock) it, you need to connect your phone to PC, run ADB and run this command:
fastboot oem lock
(It will wipe all your data, also)
Also
You don't need root to use TWRP.
Edit.
Oh, i haven't look at date of the Q =__=
Hello all,
I have Zenfone 2 on which I intended to use a custom ROM.
So the first thing was to unlock the bootloader.
On previous occasion, on my Nexus, I had used the - fastboot oem unlock - command and it had worked. So with that in mind, I booted into the bootloader and tried the command, but it failed - saying oem command unrecognized.
Then I searched online and apparently, to unlock the bootloader, Asus has launched an app! But to be able to install the app, I need to get a normal boot happening, which is not happening now.
In between all this, I tried the commands - fastboot flash recovery <recovery.img>, fastboot flash boot <boot.img> too. But none of these were successful, and each of them returned a 'Permission denied' message, probably coz the bootloader was locked.
Now the situation is that -
- Bootloader is locked.
- Phone is stuck in bootloader
- There is no recovery installed. In fact, from the bootloader, when I try to boot into 'Recovery Mode', it goes there for a second and returns back to the bootloader. Doesn't show the normal android image with a 'X' on top.
- There is no root access.
Now I think the first step is to get root access, and for this I want to try the method with installing CWM recovery and SuperSu.
But for this, I need to be able to push the SuperSu.zip to the phone, which I am not able to.
Can somebody please help!
r the drivers for fastboot & adb update to date?
Android version?
If the phone is stuck in bootloader, you can use Asus Flash Tool to flash .raw files and unbrick the phone.
Raw files: https://yadi.sk/d/FijRoAVJtvRiG
AFT: https://yadi.sk/d/NQCiY--IsQjBr (I use AsusFlashToolInstaller1.0.0.14.exe).
you can use Asus Flash Tool to flash .raw files and unbrick the phone.
Click to expand...
Click to collapse
Have to choose wipe the data or not?
hafiz019 said:
Have to choose wipe the data or not?
Click to expand...
Click to collapse
stay away from aft. if will f**k up yor device completely. AFT is too unstable. lot of times it bricks the device to unrecoverable state. tell me the bootloader version, ifwi version shown on screen while in bootloader mode.
HI everyone,
I updated "successfully" from Kitkat to 5.0.2 on my rooted (stock ROM) Nexus 7 second gen.
Unfortunately, when I tried to upgrade to 5.1 everything seem to be normal until the device rebooted and it went through the "update process". 3/4 the way through, the green droid went on his back and the "ERROR" message appeared.
I wiped the cache partition but that doesn't help. I tried to download the update in safe mode, but no success. I also find it odd that each time I reboot my device, I get a message from Android that it is "updating my apps".
If I didn't have any apps and a lot of data on my Nexus, I would wipe the device clean but I'd rather avoid this, if at all possible.
Is there a way to upgrade to 5.1 or reinstall 5.0.2 without losing everything?
Thanks
Michael Carleone said:
Is there a way to upgrade to 5.1 or reinstall 5.0.2 without losing everything?
Click to expand...
Click to collapse
No problem. As you rooted it before then presumably it is unlocked and equipped with custom recovery, so all you have to do is:
boot TWRP
connect PC
transfer data and APKs to PC
flash OS
If you don't have TWRP installed, then boot it like this fastboot boot twrp-3.0.2-0-flo.img
k23m said:
No problem. As you rooted it before then presumably it is unlocked and equipped with custom recovery, so all you have to do is:
boot TWRP
connect PC
transfer data and APKs to PC
flash OS
If you don't have TWRP installed, then boot it like this fastboot boot twrp-3.0.2-0-flo.img
Click to expand...
Click to collapse
Hi,
Thanks for the reply. I rooted with Kingroot. I don't believe I have a custom recovery. The bootloader is locked as shown when I boot into recovery mode.
I want to avoid transferring my data and APK files to my PC.
Should I assume there is no way of reinstalling the OS without wiping out the device?Also, there is no link in the above quote: fastboot boot twrp-3.0.2-0-flo.img
Since I got no other replies, I went and restored to factory image. I do have another question. I hope I get a better response there: http://forum.xda-developers.com/nex...a/nexus-7-2013-wifi-root-marshmallow-t3515072
Thanks for the reply.
Can we compare using fastboot flashing TWRP vs Nexus Root Tool Kit: http://www.wugfresh.com/nrt/? I ended up using this utility instead because it was pretty much one click and it didn't require command lines and for whatever reason, I found instructions using fastboot a bit confusing. Which method is better or has more advantages? I left my bootloader unlocked.
Incidentally, I think there was something wrong with my Nexus image. As a result, I did use Google's instructions on how to flash etc. the OEM image. Instructions weren't ideal but I managed to figure things out: https://developers.google.com/android/images
The instructions are here which I assume would be similar if I wanted to fastboot TWRP?
To flash a system image:
Download the appropriate system image for your device below, then unzip it to a safe directory.
Connect your device to your computer over USB.
Start the device in fastboot mode with one of the following methods:
Using the adb tool: With the device powered on, execute:
adb reboot bootloader
Using a key combo: Turn the device off, then turn it on and immediately hold down the relevant key combination for your device. For example, to put a Nexus 5 ("hammerhead") into fastboot mode, press and hold Volume Up + Volume Down + Power as the device begins booting up.
If necessary, unlock the device's bootloader by running:
fastboot flashing unlock
or, for older devices, run:
fastboot oem unlock
The target device will show you a confirmation screen. (This erases all data on the target device.)
Open a terminal and navigate to the unzipped system image directory.
Execute the flash-all script. This script installs the necessary bootloader, baseband firmware(s), and operating system.
Once the script finishes, your device reboots. You should now lock the bootloader for security:
Start the device in fastboot mode again, as described above.
Execute:
fastboot flashing lock
or, for older devices, run:
fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.
Click to expand...
Click to collapse
Also, I could've sworn that when I rooted KitKat on my Nexus, my data wasn't wiped out. I don't recall doing anything to the bootloader. I can't recall which method I used, but I know for certain I didn't use the Nexus Root Toolkit. I should've recorded my steps when I rooted.
i rooted my nexus 7 using towel root on kitkat .. i unrooted using supersu... and ota untill marhsmallow with out a problem never use kingroot as its so un stable.
I need some help. It seems like I am in a circular conundrum and have tried almost everything. A quick summary of how far I've gone (and searched): gone as far as successfully performing a stock reflash, but the boot loop is still there. I realize this could be a hard failure, but even so, shouldn't there be a log stored somewhere to tell me what failed?
An abbreviated list of things I've tried (many times w/ varying parameters where possible):
- wipe cache
- factory data reset
- reflash stock using ODIN
- flash TWRP (failed: Complete(Write) operation failed)
Here's what I CAN do: boot into download mode, connect with ODIN, boot into recovery mode.
Here's where I get into some circular issues. The next thing to try was unlocking, rooting and installing a custom ROM.
Any of those things seems to require being able to boot or have USB debugging enabled. So to summarize my last known configuration:
(1) USB debugging apparently disabled
(2) Samsung reactivation lock enabled
(3) Encryption probably enabled
So how do I get a custom ROM installed with all these not in my favor?
Unlock bootloader: root and/or adb push access required.
--> I can't adb push because USB debugging disabled.
--> I probably can't adb push to that location/chmod because I don't have root
--> I can't root because it seems all the root methods require a booting device to start with
I CAN/should be able to adb sideload (I have been able to get the device to show up with adb via going into stock recovery then apply update with adb, but not sure what to sideload)
Thanks in advance for any help you can provide!
termiflyer said:
I need some help. It seems like I am in a circular conundrum and have tried almost everything. A quick summary of how far I've gone (and searched): gone as far as successfully performing a stock reflash, but the boot loop is still there. I realize this could be a hard failure, but even so, shouldn't there be a log stored somewhere to tell me what failed?
An abbreviated list of things I've tried (many times w/ varying parameters where possible):
- wipe cache
- factory data reset
- reflash stock using ODIN
- flash TWRP (failed: Complete(Write) operation failed)
Here's what I CAN do: boot into download mode, connect with ODIN, boot into recovery mode.
Here's where I get into some circular issues. The next thing to try was unlocking, rooting and installing a custom ROM.
Any of those things seems to require being able to boot or have USB debugging enabled. So to summarize my last known configuration:
(1) USB debugging apparently disabled
(2) Samsung reactivation lock enabled
(3) Encryption probably enabled
So how do I get a custom ROM installed with all these not in my favor?
Unlock bootloader: root and/or adb push access required.
--> I can't adb push because USB debugging disabled.
--> I probably can't adb push to that location/chmod because I don't have root
--> I can't root because it seems all the root methods require a booting device to start with
I CAN/should be able to adb sideload (I have been able to get the device to show up with adb via going into stock recovery then apply update with adb, but not sure what to sideload)
Thanks in advance for any help you can provide!
Click to expand...
Click to collapse
You'll definitely have to get your device booted in order to root / unlock your bootloader. You need su permission during the adb part of the unlock process which is where the temp root from kingroot comes in to play. I would recommend trying to download and install the full official firmware of BPA1 and flash it in Odin. You won't be able to flash TWRP or anything else until you get your bootloader unlocked and that will require you to be on the BPA1 firmware. So that's where I would start.