AL10 was flashed to kangvip b170 L29 eu. All fine few month but emergency calls for my region (UA) not work properly (call to police and listen fire dept answer). I think that problem was in location and try to flash from TWRP ru location file. But after this i see next problems:
- changes ROM ver from b170 to b152 (NXT-C900B152) //only locale file was flashed//
- cant boot now to TWRP (was 3.0.2)
- during boot red letters warning "your device has failed verification and may not work properly"
- when i try to run italian knife (sometime earlier i fix this problem with it) - it looong booting (yellow letters WAIT), and as i detect problem: "device is unauthorised" (see after run a cmd <<adb devices>>). So problem is dual :
1) on phone - i see red letters during booting "your device has failed verification and may not work properly"
2) on PC - device is unauthorised (earlier all was fine), i try to reinstall adb, nothing changed. I try to delete adb keys with their folders, on/off USB debugging switch...
Phone is unlocked and rooted, bootloader shows "phone unlocked".
Trying flash firmware using sdcard upgrade, flash stock recovery but device is rebooting and stops - because probably link path to recovery is broken. Few tools i try stops on <<waiting device>> because dev is unauthorised and i cant receive authorisation by on/off USB debugging
How fix this problems ?
SOLVED BY UPDATING FROM SD CARD TO NEW FIRMWARE, AND NORMAL ASKING FOR RSA KEY I RECEIVED AT LAST !!!
Related
Hello to all.
My first post was about One mini with unlocked bootloader and failed system. Situation changed so I describe all "story" wondering that sb clever would tell me what to do now...
At the beginning, I visited some "specialist", who applied me a fantasy about bootloader rebuilding and took cash for nothing. Because thay said that tried to flash European ROM on device bought in USA with ATT brand and S ON (look attach) I had to learn a little to do anything by myself.
First of all I flashed TWRP Recovery using AllinOne. First CMD window replied "device not found" but second one responded that Recovery was flashed succesfully. In fact TWRP run. And it was all.
Than I tried to do anything by ADB. Drivers were installed correctly but any command form adb responded "device not found"
Device manager showed QHSUSB DLOAD when connected not powered one mini. (Yes I know what it means)
Sideload in TWRP was not working too.
Flashing wih USB OTG mounted under TWRP was not working too.
Newest RUU_M4_UL_K44_SENSE60_MR_Cingular_US_4.13.502.3_ from htc site (.htc.com / us / support / htc-one-mini-att / news / ) was showing connection error at the beginngin but was detecting system version and suggested update. Always failed after reboot.
Today I tried to flash RUU.zip (ver same as installed on my bricked one mini). AllinOne asked about Bootloader lock so I relocked bootloader. Flashing failed so I started mentioned newest original RUU from HTC. Bootloader was rebooted and procedure started. (with unlocked bootloader it failed at this moment) Unfortunaelly it stopped at 95% with comunicate "signature error".
Cell restarted, htc logo appeared ("by android" sign was added) and device manager detected HTC device and mass memory. Unfortunetelly system havent boot up and now manager shows only "not recognized device" but QHSUSB DLOAD not appeared again
What would you advice to do now? Try to update again? When you check Fastboot reply at CMD screenshot than it seems to be ALMOST updated. But still sth is wrong
I read RUU log and edited fonts colour to make it more readable.
I can see that all time ADB has a problem with "adb devices" command and it asks fastboot (i coloured it on pink).
Later it flash two almost 400MB each zip files but after second one gives signature fail. If Update comes from HTC and almost all update was correct what may it mean now?
I attach
1 image with bootloader details when bought broken
2 image of ADB fastboot report after 95% Update to 4.13.502
3 log from Updater
Hi. I had rooted Galaxy S7 (SM-G930F) then I switch off all of Programming Options (including Enable OEM unlock and Debugging USB) and restarted phone. I got "custom binary blocked by frp lock" red message and I couldn't run system. Then I wanted to install clear firmware, I downloaded one and tried to install by Odin. After 5 hours with 95% bar status I restarted my phone. Now I get "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software". Is this end of my phone? Please help.. (sorry for my english)
diego411 said:
Hi. I had rooted Galaxy S7 (SM-G930F) then I switch off all of Programming Options (including Enable OEM unlock and Debugging USB) and restarted phone. I got "custom binary blocked by frp lock" red message and I couldn't run system. Then I wanted to install clear firmware, I downloaded one and tried to install by Odin. After 5 hours with 95% bar status I restarted my phone. Now I get "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software". Is this end of my phone? Please help.. (sorry for my english)
Click to expand...
Click to collapse
Hi
No there is hope still...
How did you root your phone?
Explain what happen with odin , what files did you use and how you flashed.
Options
1 Smart switch you could use it and try to restore firmware
2 Download a different firmware and try to flash with odin again
3 Flash TWRP , root again , flash a custom rom , set OEm unlock , usb debbuging and now try to flash a stock rom again
For root I downloaded Odin and "CF-Auto-Root-herolte-heroltexx-smg930f.tar.md5". Then I switched phone to Download Mode and load AP in Odin, Then clicked start.
After that phone works great, I had root permissions. But then I switched off "Enable OEM unlock" and "Debugging USB" and restarted phone. Then when I tried to start system I could see "custom binary blocked by frp lock" message. I downloaded "AP_G930FXXU1DQB3_CL10422490_QB12410562_REV00_user_low_ship_meta.tar.md5", switched phone to Download Mode and loaded AP in Odin. The progress stopped at 90-99% for few hours, so I switch phone off and unplugged cable. After that I got "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software". Now I can do nothing. Only switch to Download Mode. I used Smart Switch but after putting Model Name and Serial Number and downloading files, I always get error.
/// I use Odin and CSC option (and load "HOME_CSC_OXX_G930FOXX1DQA1_CL10357061_QB12200735_REV00_user_low_ship.tar.md5"). Now I'm in Recovery Menu and can see recovery menu and "E:failed to mount /system (Invalid argument )".
diego411 said:
For root I downloaded Odin and "CF-Auto-Root-herolte-heroltexx-smg930f.tar.md5". Then I switched phone to Download Mode and load AP in Odin, Then clicked start.
After that phone works great, I had root permissions. But then I switched off "Enable OEM unlock" and "Debugging USB" and restarted phone. Then when I tried to start system I could see "custom binary blocked by frp lock" message. I downloaded "AP_G930FXXU1DQB3_CL10422490_QB12410562_REV00_user_low_ship_meta.tar.md5", switched phone to Download Mode and loaded AP in Odin. The progress stopped at 90-99% for few hours, so I switch phone off and unplugged cable. After that I got "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software". Now I can do nothing. Only switch to Download Mode. I used Smart Switch but after putting Model Name and Serial Number and downloading files, I always get error.
/// I use Odin and CSC option (and load "HOME_CSC_OXX_G930FOXX1DQA1_CL10357061_QB12200735_REV00_user_low_ship.tar.md5"). Now I'm in Recovery Menu and can see recovery menu and "E:failed to mount /system (Invalid argument )".
Click to expand...
Click to collapse
Hi
Go to Sammobile and select the firmware according your country ( not necessary , any one will do)
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/
Use AP , BL CP and CSC ( not home_csc)
when using CSC follow this instructions (step 6)
https://www.sammobile.com/forum/showthread.php?t=30800
this will format all partitions
also as a guide check this thread
https://forum.xda-developers.com/galaxy-s7/how-to/official-stock-firmware-update-odin-t3369431
If any error copy Odins log and show us
If this does not work try what i said , TWRP-root-custom rom then back to stock
Ok, I will follow that, but I have to wait becouse downloading from sammobile.com is slow. Please tell me how to turn off phone. I can't do that. When I choose Power off in Android Recovery, the phone restarts. I also tried to click power button for ten seconds, but without reaction.
Under options like "reboot system now", ....., "run graphics test", "power off", I can see:
"No support SINGLE-SKU
Supported API: 3
dm-verity error...
E:failed to mount /system (Invalid argument)"
/// Ok, I should unplug usb cable. Now I can turn off device.
The problem has been solved! I followed your advices (first way) and my phone isn't brick now. Thank you very much!
diego411 said:
The problem has been solved! I followed your advices (first way) and my phone isn't brick now. Thank you very much!
Click to expand...
Click to collapse
Great news mate...
Thanks for letting us know
Hello all,
So I finally got the dreaded FRP lock error when trying to reboot my phone.
Things I've tried to do:
1. Install Smart Switch and enter my model number + S/N and I get an error "This model number cannot be initialized"
2. Install Samsung Kiss update the drivers etc
3. Download stock firmware and try flash through Odin "Device wont recognize on PC or Odin" (But with another phone it will, so USB is fine)
4. Went into the recovery menu, wiped device/cleared cache etc
So the problem is the device is not recognizing on my on Windows 10 + Windows 7 - If I can get the device to recognize i will be able to flash stock firmware and my issue will be resolved.
If anyone has a bypass, or has resolved their issue please let me know - because I have tried everything.
Help please!! "This device is corrupt. It can´t be trusted and will not boot"
Hello everyone!
I have a problem... My Htc u12+ doesn´t start up normally. I have the following message: "This device is corrupt. It can´t be trusted and will not boot"
Can anyone here help me please??
Let me explain what happened and how I messed it up...
I was trying to downgrade from android 9 to Oreo. As I red in other threads, It looked quite easy and just followed the steps:
- I found the latest Oreo version for my dual sim with CID _034
version 1.30.401.2 from here: (Sorry I´m not allowed to post URL´s yet, but it´s the google docs one named "HTC U12+ - RUU/Firmware/Recovery/OTA Collection")
- Once I had it in my computer, I moved it to my SD card and renamed it to: 2Q55IMG.zip
- Then I boot to download mode and had this message:
"Security checking failed DENY
Security Warning
If you flash this phone with any ROM that was not officially released by HTC you take the risk of releasing your personal and financial information to unknown sources"
I had two options at this point: continue / cancel
I thought it was normal so I continued and now my HTC doesn´t boot normally.
I´m stuck in a black screen with different options:
"Reboot, Reboot to Bootloader, Reboot to Download, Reboot to Recovery, Power Down."
I´ve tried all the options but non of them seem to work. When I select "Reboot to Download" I get the same security warning message, but no option of canceling this time.
After the warning It says:
SD not mounted
OTG not mounted
File not mounted
If I plug it to my computer, it make a sound but It doesn´t recognise my HTC
So.... I´m totally lost and have no idea how to fix it.
Your help would be much appreciated
Thank you!!
edit: My computer recognise the device in fastboot mode. So, my U12+ is not dead but I have no idea what to do now.
i think you are going back to far you need 1.53.401.5 then change it to 2Q55IMG.zip and then use SD method
/Bad post.
How did you deal with the problem? I have identical
Revision 1
S7 edge(G935F, exynos model)
Android 8.0.0(Oreo)
rooted = yes, using odin and cf-autoroot file
dev options = turned off
USB debugging = off
OEM unlock = locked
carrier = when bought it isn`t tied to any carriers, now it don`t have any SIM card
SD card = Inside, but broken
What happened?
I try to root the phone. This is the first I`ve root a phone. I follow the instructions exactly and it worked. Then the OS notifies me that I have to restart my phone because of security issues. I restarted it, but it won`t boot. There`s a message in the top corner of the screen that says "custom binaries blocked by FRP", I looked it up and saw how to fix it, found it from imyfone.com (
[2023] Fix “Custom Binary Blocked by FRP Lock” - 100% Work
Stuck on 'custom binary blocked by frp lock' error on your Android device? Find the latest & easiest way here to fix it quickly!
www.imyfone.com
), follow it, when I need to input my carrier and country, imyfone don`t list my country (Indonesia) and don`t have the options to select no carrier so I can`t proceed because it already warns me that if I got the info wrong, I will brick my phone. Then I try to brainstorm an idea by myself and found if I redownloads the rooted tar.md5 to my phone, it will boot again. I boot it to the download mode, prepares Odin, ADB, an USB driver, connect it to this computer and start downloading. Odin says it failed to download but the phone is still stuck on the download mode, and I disconnected the USB several times (What do you need USB for if the download has failed?)
What have I tried? (Not in chronological order)
- ReiBoot, to get out of the download mode and fix the phone
- Factory Reset
- Restarting from the original recovery mode
- redownloads the tar.md5 file to my phone
What I think is the solution?
1. Give up and admit that the phone is broken (not recommended), or
2. Wait until the battery dies and try to boot it again
additional info
[If there`s a need for revision(s) like more infos, just ask in this discussion]
the rooting guide is from tenorshare.com (https://www.tenorshare.com/android-root/how-to-root-samsung-galaxy-s7-or-s7-)