Related
it was in version 5.0.2, with the unlocked bootloader and the camera does not opened, thus did the restoration with fastboot to the same version more displays an error after the restoration process "failed to validate system image - Fasboot Reason: Fail- through from the normal boot mode "not out of this error and not start the system, what do I do?
Downloaded the ROM in this site filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25&page=2
I am Brazilian and smartphone model Moto G xt1033 16GB
Could you tell, what error you are receiving and what system Installation you are trying. are you upgrading to 5.0.2??
bgeke said:
Could you tell, what error you are receiving and what system Installation you are trying. are you upgrading to 5.0.2??
Click to expand...
Click to collapse
it was in version 5.0.2, with the unlocked bootloader and the camera does not opened, thus did the restoration with fastboot to the same version more displays an error after the restoration process "failed to validate system image - Fasboot Reason: Fail- through from the normal boot mode "not out of this error and not start the system, what do I do?
Downloaded the ROM in this site filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25&page=2
I am Brazilian and smartphone model Moto G xt1033 16GB
restaurapc said:
it was in version 5.0.2, with the unlocked bootloader and the camera does not opened, thus did the restoration with fastboot to the same version more displays an error after the restoration process "failed to validate system image - Fasboot Reason: Fail- through from the normal boot mode "not out of this error and not start the system, what do I do?
Downloaded the ROM in this site filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25&page=2
I am Brazilian and smartphone model Moto G xt1033 16GB
Click to expand...
Click to collapse
Not sure
So phone is not booting up now??
Download your Complete firmware and Follow the steps given here http://forum.xda-developers.com/showthread.php?t=2700502. If your firmware have different files, command will vary. Search in xda or google.
This is known issue and I think no exact solution is found. I'm not responsible for any damage. If you get it to work. then post it here. But give more details about your situation.
bgeke said:
Not sure
So phone is not booting up now??
Download your Complete firmware and Follow the steps given here http://forum.xda-developers.com/showthread.php?t=2700502. If your firmware have different files, command will vary. Search in xda or google.
This is known issue and I think no exact solution is found. I'm not responsible for any damage. If you get it to work. then post it here. But give more details about your situation.
Click to expand...
Click to collapse
device is locked status code 2 , as for the unlock code 3 ?
restaurapc said:
device is locked status code 2 , as for the unlock code 3 ?
Click to expand...
Click to collapse
It means bootloader is locked.
bgeke said:
It means bootloader is locked.
Click to expand...
Click to collapse
you need to unlock to install system?
restaurapc said:
you need to unlock to install system?
Click to expand...
Click to collapse
Not required to unlock bootloader for flashing stock ROM. Just try to flash the whole firmware with mfastboot.
bgeke said:
Not required to unlock bootloader for flashing stock ROM. Just try to flash the whole firmware with mfastboot.
Click to expand...
Click to collapse
I'm downloading the rom ASIARETAIL_XT1033_5.0.2_LXB22.46-28_cid7_CFC.xml.zip, if not go right setup with the fastboot is possible to do using the TWRP recovery?
soon put the result of the installation of fastboot
So, my Note 5 somehow got reset with OEM unlock OFF. Also, I was running a modified stock rom at the time. Now my note 5 is a really expensive paper weight unless someone here can tell me why odin won't recognize my phone in download mode anymore. How can i flash a stock rom back to the device if it's not recognized? Also in recovery i get these messages:
1. Update from ADB is disabled
2. Update from External Storage is disabled
3. Apply_Cache is depricated
If I reboot to bootloader i get the charging symbol with:
Kernal ins not seandroid
Custom Binary blocked by frp lock
can someone throw some ideas out there about what I should do?:angel:
kennybrooks said:
so, my note 5 somehow got reset with oem unlock off. Also, i was running a modified stock rom at the time. Now my note 5 is a really expensive paper weight unless someone here can tell me why odin won't recognize my phone in download mode anymore. How can i flash a stock rom back to the device if it's not recognized? Also in recovery i get these messages:
1. Update from adb is disabled
2. Update from external storage is disabled
3. Apply_cache is depricated
if i reboot to bootloader i get the charging symbol with:
kernal ins not seandroid
custom binary blocked by frp lock
can someone throw some ideas out there about what i should do?:angel:
Click to expand...
Click to collapse
reflash the stock rom only with odin! No recovery, no root! Then reflash the rest! Do not try to flash with recovery! Search threads for your note 5 version of firmware. And from now on make sure you keep oem on!
sir0knightfall said:
reflash the stock rom only with odin! No recovery, no root! Then reflash the rest! Do not try to flash with recovery! Search threads for your note 5 version of firmware. And from now on make sure you keep oem on!
Click to expand...
Click to collapse
odin won't recognize my phone! what could that be?
KennyBrooks said:
So, my Note 5 somehow got reset with OEM unlock OFF. Also, I was running a modified stock rom at the time. Now my note 5 is a really expensive paper weight unless someone here can tell me why odin won't recognize my phone in download mode anymore. How can i flash a stock rom back to the device if it's not recognized? Also in recovery i get these messages:
1. Update from ADB is disabled
2. Update from External Storage is disabled
3. Apply_Cache is depricated
If I reboot to bootloader i get the charging symbol with:
Kernal ins not seandroid
Custom Binary blocked by frp lock
can someone throw some ideas out there about what I should do?:angel:
Click to expand...
Click to collapse
This guy can help you out or even me http://forum.xda-developers.com/tmobile-galaxy-note5/general/free-sim-frp-unlock-t3376396
KennyBrooks said:
odin won't recognize my phone! what could that be?
Click to expand...
Click to collapse
Kenny,
The new stock firmware is available here: https://www.androidfilehost.com/?fid=24588232905721433
Unzip it, ODIN flash it.
FRP is automatically activated when you add a Google Account now. Remove the Google account before factory reset, rooting and installing a custom ROM.
PS: I learned the hard way too.
rmarinella said:
Kenny,
The new stock firmware is available here: https://www.androidfilehost.com/?fid=24588232905721433
Unzip it, ODIN flash it.
FRP is automatically activated when you add a Google Account now. Remove the Google account before factory reset, rooting and installing a custom ROM.
PS: I learned the hard way too.
Click to expand...
Click to collapse
Odin won't recognize my phone at all. My computer sees it as "Unknown USB Device (Device Descriptor Request Failed)." how do I fix this?
KennyBrooks said:
Odin won't recognize my phone at all. My computer sees it as "Unknown USB Device (Device Descriptor Request Failed)." how do I fix this?
Click to expand...
Click to collapse
Try going this route and doing an emergency recovery.
http://www.samsung.com/us/sidesync/
rmarinella said:
Try going this route and doing an emergency recovery.
http://www.samsung.com/us/sidesync/
Click to expand...
Click to collapse
should i use download mode or recovery?
I don't recall. Biggest reason I pointed you here is that a proper driver is also included. I think recovery mode though.
My phone is totally ****ed - Device does not have DRK, please install DRK first...
I try to flash stock firmware but this just comes up when it boots. If I leave it a whilst it will just load into the stock recovery and it says 'device does not have drk, contact to SW PL, please flash ENG binary and install DRK'.
Can't find any guides or anything in the internet hmm.
thrutheeyes said:
My phone is totally ****ed - Device does not have DRK, please install DRK first...
I try to flash stock firmware but this just comes up when it boots. If I leave it a whilst it will just load into the stock recovery and it says 'device does not have drk, contact to SW PL, please flash ENG binary and install DRK'.
Can't find any guides or anything in the internet hmm.
Click to expand...
Click to collapse
Hi mate
Check HERE
thrutheeyes said:
My phone is totally ****ed - Device does not have DRK, please install DRK first...
I try to flash stock firmware but this just comes up when it boots. If I leave it a whilst it will just load into the stock recovery and it says 'device does not have drk, contact to SW PL, please flash ENG binary and install DRK'.
Can't find any guides or anything in the internet hmm.
Click to expand...
Click to collapse
Did you ever figure out the fix for the DRK error. I have the S8+ and just got the same thing, and I can't find a fix for it. Sounds like from another thread, that it's going to be pretty tough to overcome.
DRK means BL file
thrutheeyes said:
My phone is totally ****ed - Device does not have DRK, please install DRK first...
I try to flash stock firmware but this just comes up when it boots. If I leave it a whilst it will just load into the stock recovery and it says 'device does not have drk, contact to SW PL, please flash ENG binary and install DRK'.
Can't find any guides or anything in the internet hmm.
Click to expand...
Click to collapse
If you get DRK problem in your samsung mobiles, it means install correct BL file (Ap, Bl, Cp, CSC )
first check your BL file using odin
how to chek:
1 open odin
2 click on BL
3 select correct odin file
4 put your samsung mobile into downloading mode ( volume down + home button + on/off )
5 connect your mobile via original usb cable to your pc or lapptop
6 click start button in odin
if you got error or fail it's not your correct BL file and you i'll get DRK problem
BL file problems :
DRK error
DRK not find
No support single_SKU
supported API: 3
Dm-verity error....
failed code : 0*02
E:failed to find /misc partition
ete.
s6 EDGE
gm0ney1 said:
Did you ever figure out the fix for the DRK error. I have the S8+ and just got the same thing, and I can't find a fix for it. Sounds like from another thread, that it's going to be pretty tough to overcome.
Click to expand...
Click to collapse
Me funciono rooteando el equipo en el s6ede g925t, pero en el g925i no funciono rooteando...
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Nixonkai417 said:
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Click to expand...
Click to collapse
Give the all required information like Brand, model number in your post first.
Huawei honor 5x kiwi L24, I can't really acces the phone so finding some information is impossible. My main issue is when I boot it's failing to verify the Boot.img , recovery.img and system.img . I don't exactly know what all information I can give you
Nixonkai417 said:
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Click to expand...
Click to collapse
First open the tool
Select the update.app file
Then press Ctrl and select the imgs you want
And then right click and click extract selected
Like in here
https://up.harajgulf.com/imagef-149893652739431-png.html
-Hope- said:
First open the tool
Select the update.app file
Then press Ctrl and select the imgs you want
And then right click and click extract selected
Like in here
https://up.harajgulf.com/imagef-149893652739431-png.html
Click to expand...
Click to collapse
I have already done that, I've tried flashing it via SP flash tool but nothing, it won't show up. I've downloaded correct drivers and done what I could but my phone shows up as Lemobile android adb interface. It sometimes shows as a disk drive as well.
When I run CMD command (fastboot flash oem info) it shows everything but the recovery.img system.img and boot.img need verification how can I verify them without the debugging bridge active on the phone.
Nixonkai417 said:
I have already done that, I've tried flashing it via SP flash tool but nothing, it won't show up. I've downloaded correct drivers and done what I could but my phone shows up as Lemobile android adb interface. It sometimes shows as a disk drive as well.
When I run CMD command (fastboot flash oem info) it shows everything but the recovery.img system.img and boot.img need verification how can I verify them without the debugging bridge active on the phone.
Click to expand...
Click to collapse
What do you mean sir
Imgs are already verified cause they are official
And you don't need USB debug in fastboot mode
Your device is not has mtk processor so it won't work
-Hope- said:
What do you mean sir
Imgs are already verified cause they are official
And you don't need USB debug in fastboot mode
Your device is not has mtk processor so it won't work
Click to expand...
Click to collapse
I rooted my phone and was running xenon HD on my Huawei honor 5x, in the midst of switching ROMs I accidently targeted a TWRP recovery.img with the ROM and Gapps.
So what my phone dose now is when it powers on it an all green screen with a red box and a blue box. After a second it come up with " recovery image verify failed, please update to verified images." I can enter fastboot&rescue mode and a Huawei erecovery, but when i do try to download the recovery via WIFI it says package failure.
Nixonkai417 said:
I rooted my phone and was running xenon HD on my Huawei honor 5x, in the midst of switching ROMs I accidently targeted a TWRP recovery.img with the ROM and Gapps.
So what my phone dose now is when it powers on it an all green screen with a red box and a blue box. After a second it come up with " recovery image verify failed, please update to verified images." I can enter fastboot&rescue mode and a Huawei erecovery, but when i do try to download the recovery via WIFI it says package failure.
Click to expand...
Click to collapse
What happens when you try flashing through fastboot
Assuming that your bootloader is unlocked have you tried reflashing twrp?
-Hope- said:
What happens when you try flashing through fastboot
Assuming that your bootloader is unlocked have you tried reflashing twrp?
Click to expand...
Click to collapse
I had unlocked my bootloader but some research I was doing says, when you accidently flash wrong images it can relock the bootloader. I lost the original bootloader code and i don't exactly have the box anymore, so getting a new code will be difficult.
Nixonkai417 said:
I had unlocked my bootloader but some research I was doing says, when you accidently flash wrong images it can relock the bootloader. I lost the original bootloader code and i don't exactly have the box anymore, so getting a new code will be difficult.
Click to expand...
Click to collapse
As long as the bootloader says 'phone is unlocked' then its ok
-Hope- said:
As long as the bootloader says 'phone is unlocked' then its ok
Click to expand...
Click to collapse
I'm my case the bootloader has relocked, so in green it say phone status: locked.
Nixonkai417 said:
I'm my case the bootloader has relocked, so in green it say phone status: locked.
Click to expand...
Click to collapse
I've reread your previous post and you didn't mentioned what happens in the cmd window when trying to flash the files?
-Hope- said:
I've reread your previous post and you didn't mentioned what happens in the cmd window when trying to flash the files?
Click to expand...
Click to collapse
(REMOTE: command not allowed)
I have already sent an email to Huawei support, just waiting on a response to see if they can give me another unlock code. If I'm unable to unlock the boot loader again with the codes, what's my options for unlocling the boot loader without Huawei's help.
Howdy,
I got my s23 plus and I would like to unlock the native call recorder. How can I do it? and is it even possible at this moment?
you need to change CSC to THL
i use automatic call recorder and it works
qwerty1q said:
you need to change CSC to THL
Click to expand...
Click to collapse
Hi,
Can you help me pls?
My model name: SM-916W
Baseband version:
S916WVLU1AWBE
1. Got the latest PS driver from here (developer.samsung.com/android-usb-driver)
2. Got the latest Odin tool
3. Visit SAMMOBILE and downloaded S916BXXS1AWBM for SM-S916B THL
But, Odin gives the error "Fail Auth"
And phone showed me the following error:
Secure check fail: ab1(1)
image extract failed
do you know what should I do?
Karfagen said:
Hi,
Can you help me pls?
My model name: SM-916W
Baseband version:
S916WVLU1AWBE
1. Got the latest PS driver from here (developer.samsung.com/android-usb-driver)
2. Got the latest Odin tool
3. Visit SAMMOBILE and downloaded S916BXXS1AWBM for SM-S916B THL
But, Odin gives the error "Fail Auth"
And phone showed me the following error:
Secure check fail: ab1(1)
image extract failed
do you know what should I do?
Click to expand...
Click to collapse
Have you put the phone in download mode, or in recovery mode?
Pupet_Master said:
Have you put the phone in download mode, or in recovery mode?
Click to expand...
Click to collapse
download mode
Karfagen said:
download mode
Click to expand...
Click to collapse
Well try another USB port or cable.
Check if in OS, adb commands work
If not, it's the PC. If it work then i have no idea actually