Good night friends.
I was installing the last stockrom when at the end it appeared this message: "your device software can not be checjed for corruption. Please lock the bootloader."
After that recovery mode does not start. Thanks for the help.
Hi, please describe what error happened when you try boot recovery.
Try redownload de rom
icarolessa said:
Good night friends.
I was installing the last stockrom when at the end it appeared this message: "your device software can not be checjed for corruption. Please lock the bootloader."
After that recovery mode does not start. Thanks for the help.
Click to expand...
Click to collapse
Im pretty sure you get the message anytime you flash even if its stock. from what ive read online its caused from the bootloader signatures and rom signatures not matching. once we are all on the newest updates/ best custom roms and rooted we can install a custom boot screen to remove the dumb error.
azazelcrey said:
Im pretty sure you get the message anytime you flash even if its stock. from what ive read online its caused from the bootloader signatures and rom signatures not matching. once we are all on the newest updates/ best custom roms and rooted we can install a custom boot screen to remove the dumb error.
Click to expand...
Click to collapse
How to install a custom screen?
icarolessa said:
How to install a custom screen?
Click to expand...
Click to collapse
You need Root, google "android custom boot screen".
azazelcrey said:
You need Root, google "android custom boot screen".
Click to expand...
Click to collapse
I solved the problem, I downloaded the rom again and it worked. It may have been some corrupted file. My cell phone is root, I'm going to test this method to change the home screen.
Related
Hi.
Just tried to root my Htc one using this method: HTC One M7 How To ROOT EASIEST METHOD.
Unlocked the boot loader successfully.
Then downloaded newest TWRP Recovery Image openrecovery-twrp-2.6.3.0-m7.img
Followed the instructions
One thing was suspicious when entering fast boot:
*** Tampered *** <- dont't know if it's good or no ?
*** Unlocked ***
On top of the screen It wasn't shown tampered only unlocked ?
But everythinh went well, entered recovery mode using image and install the superuser.
And reboot. The su app was there, but after checking on two apps - phone wasn't rooted.
So download old image from TWRP 2.5.0.0
And after flashing it and enter the screen when u see buttons Install, Wipe,Backup ...
the Screen it's Freezed. Swipe to Unlock is not working.
And after hitting the power button the home button and < Blinking.
Also fastboot is not working. [ waiting for device ] only.
So how to restart it so i can flash a newer image to try root it again ?
Or maybe something different is wrong ?
Thank's
adascezary said:
Hi.
Just tried to root my Htc one using this method: HTC One M7 How To ROOT EASIEST METHOD.
Unlocked the boot loader successfully.
Then downloaded newest TWRP Recovery Image openrecovery-twrp-2.6.3.0-m7.img
Followed the instructions
One thing was suspicious when entering fast boot:
*** Tampered *** <- dont't know if it's good or no ?
*** Unlocked ***
On top of the screen It wasn't shown tampered only unlocked ?
But everythinh went well, entered recovery mode using image and install the superuser.
And reboot. The su app was there, but after checking on two apps - phone wasn't rooted.
So download old image from TWRP 2.5.0.0
And after flashing it and enter the screen when u see buttons Install, Wipe,Backup ...
the Screen it's Freezed. Swipe to Unlock is not working.
And after hitting the power button the home button and < Blinking.
Also fastboot is not working. [ waiting for device ] only.
So how to restart it so i can flash a newer image to try root it again ?
Or maybe something different is wrong ?
Thank's
Click to expand...
Click to collapse
It's not frozen, the old version uses different touchscreen drivers that why you can't press anything.
Use adb to reboot, and flash an up to date version of TWRP or CWM:
"adb reboot bootloader"
that will get you back to FASTBOOT USB.
nkk71 said:
It's not frozen, the old version uses different touchscreen drivers that why you can't press anything.
Use adb to reboot, and flash an up to date version of TWRP or CWM:
"adb reboot bootloader"
that will get you back to FASTBOOT USB.
Click to expand...
Click to collapse
Thank's for quick help.
It worked.
But flashed openrecovery-twrp-2.6.1.0-m7.img so the older one and still not rooted.
Try also with other images from TWRP. still nothing.
app keep saying that my phone is not rooted correctly
Any solution what's wrong ?
adascezary said:
Thank's for quick help.
It worked.
But flashed openrecovery-twrp-2.6.1.0-m7.img so the older one and still not rooted.
Try also with other images from TWRP. still nothing.
app keep saying that my phone is not rooted correctly
Any solution what's wrong ?
Click to expand...
Click to collapse
Try downloading this http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip and flash it in TWRP recovery.
Hit the thanks button if i helped
nkk71 said:
Try downloading this http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip and flash it in TWRP recovery.
Hit the thanks button if i helped
Click to expand...
Click to collapse
Great that solved my problem. Thank U. Can't locate that button. But will try harder.
Now I'm trying to install busybox wchich is failed of course because life would be to easy.
Already dig out that this is probably the read write protection problem and to solve this need to add new kernel module
or change my custom rom.
For me better will be adding the module only to install busybox from this solution:
http://forum.xda-developers.com/showthread.php?t=2230341&page=3
But where find command prompt ? Should go to recovery mode ?
Or maybe install the custom rom to avoid future problems?
But which one ?
adascezary said:
Great that solved my problem. Thank U. Can't locate that button. But will try harder.
Now I'm trying to install busybox wchich is failed of course because life would be to easy.
Already dig out that this is probably the read write protection problem and to solve this need to add new kernel module
or change my custom rom.
For me better will be adding the module only to install busybox from this solution:
http://forum.xda-developers.com/showthread.php?t=2230341&page=3
But where find command prompt ? Should go to recovery mode ?
Or maybe install the custom rom to avoid future problems?
But which one ?
Click to expand...
Click to collapse
Didnt know about the busybox problem oops
Anyway, what's your goal? Custom ROM, Stock ROM, etc??
If you want to stay fully stock, you could use one of the "Guru Reset" ROMs: http://www.htc1guru.com/downloads/stock-rom-downloads/ (I believe those include superuser etc. which you can select during flashing in AROMA)
Otherwise, the custom ROMs out there are all great, it's all personal preference. They each have their own "pros and cons" IF we can say that, but they are all excellent.
You'll have to experiment to see which one works for you
nkk71 said:
Didnt know about the busybox problem oops
Anyway, what's your goal? Custom ROM, Stock ROM, etc??
If you want to stay fully stock, you could use one of the "Guru Reset" ROMs:
link (I believe those include superuser etc. which you can select during flashing in AROMA)
Otherwise, the custom ROMs out there are all great, it's all personal preference. They each have their own "pros and cons" IF we can say that, but they are all excellent.
You'll have to experiment to see which one works for you
Click to expand...
Click to collapse
Well i don't know what I'm looking yet. Change from Ios to android.
By now trying to finish setting up my phone so can start using it.
When was searching forum just found the solution - someone had the same problem installing busybox.
That's way came up with that solution to solve my problem.
If someone have solution how to install busybox.
Was trying two different busy boxes both are crashing after install.
Don't want start another topic
Ok there is solution for that too.
http://forum.xda-developers.com/showthread.php?t=1929852
Thank you for your help.
Now can read more
warning
ensure the partition listed below is the correct one for your device if you do not verify this then you risk bricking on some devices it is impossible to flash recovery while in android if flashing doesnt work for you then please flash recovery a differnt way .
if=#file# of=/dev/block/mmcblk0p18"}
if i click yes it say succsfully and it dont work
on other version its way
i test it on 4.2.2 now i update it to 4.4.2
its not work any way
this error out for me when i want to install custom recovery becouse the recovery not work i want to install other one
lg g2
vs98024A
any help here ??
theghostbh said:
any help here ??
Click to expand...
Click to collapse
Trying to install a recovery on 4.4.2? Use Autorec, grab the proper version for your phone model, install the app, run it, enjoy.
when i install it say successfully install but if i go recovery mod it be black screen and out for me this type
boot certification verify
Secure booting error!
Cause: boot certification verify
and retrun to full black
theghostbh said:
when i install it say successfully install but if i go recovery mod it be black screen and out for me this type
boot certification verify
Secure booting error!
Cause: boot certification verify
and retrun to full black
Click to expand...
Click to collapse
Sounds like something is hosed up in the recovery partition, short of returning the phone to stock and starting over, not sure what else you can do.
You did use Autorec specifically for the VS980 right? There's a file for each phone model.
i fix it thanks for help
Flashed the M preview two days ago, working completely fine. I rebooted the phone for some reason, and there was an error right after the Google screen stating "Your device has failed verification and may not work properly"
I know people have been getting this, but I haven't seen anything on how to get rid of it. The phone still boots and operates fine after the message started popping up, but its a bit annoying. I thought if I just formatted all the partitions on my phone that would go away. Apparently not. After formatting in TWRP, I wanted to see if that would pop up even after I wiped everything, and it does.
Does anybody know how to get rid of this error?
RealROGWaffle said:
Flashed the M preview two days ago, working completely fine. I rebooted the phone for some reason, and there was an error right after the Google screen stating "Your device has failed verification and may not work properly"
I know people have been getting this, but I haven't seen anything on how to get rid of it. The phone still boots and operates fine after the message started popping up, but its a bit annoying. I thought if I just formatted all the partitions on my phone that would go away. Apparently not. After formatting in TWRP, I wanted to see if that would pop up even after I wiped everything, and it does.
Does anybody know how to get rid of this error?
Click to expand...
Click to collapse
its a normal m error. flash a custom kernel to get rid of it. despair has one, elite has another, and there are more out there.
RealROGWaffle said:
Flashed the M preview two days ago, working completely fine. I rebooted the phone for some reason, and there was an error right after the Google screen stating "Your device has failed verification and may not work properly"
I know people have been getting this, but I haven't seen anything on how to get rid of it. The phone still boots and operates fine after the message started popping up, but its a bit annoying. I thought if I just formatted all the partitions on my phone that would go away. Apparently not. After formatting in TWRP, I wanted to see if that would pop up even after I wiped everything, and it does.
Does anybody know how to get rid of this error?
Click to expand...
Click to collapse
This error is often a result of system/bootloader mismatch. Do you have 5.1.1 with M bootloader?
simms22 said:
its a normal m error. flash a custom kernel to get rid of it. despair has one, elite has another, and there are more out there.
Click to expand...
Click to collapse
Awesome, thank you very much.
cam30era said:
This error is often a result of system/bootloader mismatch. Do you have 5.1.1 with M bootloader?
Click to expand...
Click to collapse
Nope, running M with the M bootloader.
Did you flash TWRP recovery or the M (factory) recovery?
If TWRP, did you allow it to try and flash SU?
I didn't have that error until flashing TWRP and allowing it to try and root upon exiting TWRP.
I was a able to clear it by flashing a different kernel, booting to TWRP, and wiping caches (I didn't do a Factory Reset).
jasoraso said:
Did you flash TWRP recovery or the M (factory) recovery?
If TWRP, did you allow it to try and flash SU?
I didn't have that error until flashing TWRP and allowing it to try and root upon exiting TWRP.
I was a able to clear it by flashing a different kernel, booting to TWRP, and wiping caches (I didn't do a Factory Reset).
Click to expand...
Click to collapse
everyone who flashed m without a separate kernel got that error. its a m thing for now.
my phone wont boot up after it flashes that.. dont know what to do..
dave2metz said:
my phone wont boot up after it flashes that.. dont know what to do..
Click to expand...
Click to collapse
what did you flash? .img files or via twrp flashable zip? did you flash the bootloader? you have to or it won't ever boot.
simms22 said:
what did you flash? .img files or via twrp flashable zip? did you flash the bootloader? you have to or it won't ever boot.
Click to expand...
Click to collapse
My device keeps flashing as well. I fastboot .img files
I only had this error when I flashed twrp. When I was stock M and no twrp didn't have this issue
md1008 said:
I only had this error when I flashed twrp. When I was stock M and no twrp didn't have this issue
Click to expand...
Click to collapse
Same... flashing twrp kills my M install. Say's it's booting but all I get is a black screen.
Now it's my turn to join. Any fixes for those that won't boot up at all? I think I may have a brick. How did you get out of this?
sbrownla said:
Now it's my turn to join. Any fixes for those that won't boot up at all? I think I may have a brick. How did you get out of this?
Click to expand...
Click to collapse
you have to flash the m bootloader before flashing m, or it will never boot up.
Since pepole have no knolege of what they are doing and kind of blame me for it i will not provide the images anymore.
Please lock this thread.
Thank you so much!
Question: Do we have to flash the stock recovery after flashing the rooted system image? I prefer to have TWRP recovery anyways.
akarol said:
Thank you so much!
Question: Do we have to flash the stock recovery after flashing the rooted system image? I prefer to have TWRP recovery anyways.
Click to expand...
Click to collapse
worst case just reflash TWRP =]
akarol said:
Thank you so much!
Question: Do we have to flash the stock recovery after flashing the rooted system image? I prefer to have TWRP recovery anyways.
Click to expand...
Click to collapse
You can use whatever recovery you would like, the system image does not affect the recovery in any way.
Thanks - flashed your bootloader files which got me out of a never ending boot animation issue
j32olger said:
Thanks - flashed your bootloader files which got me out of a never ending boot animation issue
Click to expand...
Click to collapse
The bootloop have nothing to do with my bootloader files, they are completley stock from the ota file!
If you installing the new bootloader files on older roms you are asking for troubles.
Boot the watch in bootloader mode and flash the files as described and you watch will work.
Af if it bootlooping run a "Fastboot -w" after flashing.
Greetings, Is the newly released OTA compatible with your rom?
drmcatchr said:
Greetings, Is the newly released OTA compatible with your rom?
Click to expand...
Click to collapse
No ota files will only work with stock untouched rom.
bunny0007 said:
No ota files will only work with stock untouched rom.
Click to expand...
Click to collapse
Are you planning on releasing a pre-rootet image of the latest ota?
Would be greatly appreciated!
2k4ever said:
Are you planning on releasing a pre-rootet image of the latest ota?
Would be greatly appreciated!
Click to expand...
Click to collapse
Have added it today.
I tried this using the update (LCA44B) and now the watch doesn't even turn on. No LG logo or anything.
GuiyeC said:
I tried this using the update (LCA44B) and now the watch doesn't even turn on. No LG logo or anything.
Click to expand...
Click to collapse
And you did follow the instuctions?7
Flash bootloader stuff
Flash system image
Flash boot image
Have testet it serval times without errors.
bunny0007 said:
And you did follow the instuctions?7
Flash bootloader stuff
Flash system image
Flash boot image
Have testet it serval times without errors.
Click to expand...
Click to collapse
Yep, just like in the steps, the thing did show a FAILED (anti-rollback) when flashing the 'aboot'. I just used everything that was on the zip, now the watch doesn't even show the LG logo, I've tried plugging it on and off and keeping the reset button pressed for a while. I really don't know what else to try.
I'm waiting for it to run out of battery, but I don't even know if it's "on".
GuiyeC said:
Yep, just like in the steps, the thing did show a FAILED (anti-rollback) when flashing the 'aboot'. I just used everything that was on the zip, now the watch doesn't even show the LG logo, I've tried plugging it on and off and keeping the reset button pressed for a while. I really don't know what else to try.
I'm waiting for it to run out of battery, but I don't even know if it's "on".
Click to expand...
Click to collapse
Did just ran it on my own watch and everything working.
If you aboot fails flashing your watch might have another problem, i assume that your watch have an unlocked bootloader??
bunny0007 said:
Did just ran it on my own watch and everything working.
If you aboot fails flashing your watch might have another problem, i assume that your watch have an unlocked bootloader??
Click to expand...
Click to collapse
Yes, it had the boot loader unlocked, and I can't try again flashing the aboot because I can't get it to recovery mode or fast boot mode or anything.
Who can I get the images from?
bunny0007 said:
Since pepole have no knolege of what they are doing and kind of blame me for it i will not provide the images anymore.
Please lock this thread.
Click to expand...
Click to collapse
By people, do you mean 1 person ???
Pretty unfair for other, isn't it ?
I am looking for bootloader files for the G Watch R to flash over what I believe to be a corrupt bootloader on my device. It will only boot when on the charging stand, and so far I have only been able to get it to boot to 5.0.1 successfully. Once the device tries to pull down the OTA update it reboots and proceeds to run the update and then it fails and powers off.
Currently I can access fastboot and I can get it to boot a stock recovery and twrp with the 5.0.1 boot.img flashed to my device.
Can anyone who has downloaded the original package from this thread PM me the files? I need to reflash my bootloader files to attempt to fix a booting issue with my watch. Any help would be appreciated and I will not hold anyone accountable if I hard brick my device.
fnj00 said:
Can anyone who has downloaded the original package from this thread PM me the files? I need to reflash my bootloader files to attempt to fix a booting issue with my watch. Any help would be appreciated and I will not hold anyone accountable if I hard brick my device.
Click to expand...
Click to collapse
Hi there ,
Why don't you try this one ??
http://forum.xda-developers.com/g-w...edroid-r-urbane-port-v1-0-0-june-6th-t3128850
Hey all,
So I posted what I did to **** everything up the other day: https://forum.xda-developers.com/ta...ie-tried-to-root-device-t3655848?goto=newpost
I read about 70 different forums posts and concluded (somehow) that i needed to try and flash "twrp_3.1.0" for my T810. Well, for some reason it worked. I now have twrp on my boot-looped device.
Now, I'm trying to install a different recommendation which is the "SuperSU-v2.76" ROM through dragging it onto my tablet via My Computer (Since Odin refuses to load it)
Guess what? Ran into another problem when doing this. My T810 will no longer connect with my PC. It is stating "Device driver software was not successfully installed"... throwing out an error message MTP USB Device Failed.
I came up with the wise idea to simply put the SuperSU file on my brand new 128gb micro SD card. I found a USB adaptor for the card, plugged it into my PC and now My Computer is stating that the Micro SD card only has 1.67mb of space available. Did a bunch of research and found out that the USB adaptor actually has a limitor pre programmed into it so that you cannot adapt large SD cards..
I'm striking out guys. I need help. I'm able to navigate the twrp menu.. is there an option on this screen that will help me? I cannot think of what needs to be done next to get this Tab working....
also
.... yes I have the Samsung USB driver installed for my particular device....
So I ended up running to the store and I bought a 16gb micro SD. It worked, I was able to run the SuperSU-v2.76 flash on my device. Geuss what happened next?
Bootloop again.
Currently trying another suggestion which calls for restoring the tablet to an original OEM flash. Going to try installing the "5.0.2_T810XXU1AOG6_T810XAR1AOG6_XAR" flash and ill post what happens........
NOPE! No good. twrp does not recognize booting MD5 files.... I'm stuck again.
dyrewolv said:
Click to expand...
Click to collapse
You need to flash this version of SuperSU.
http://download.chainfire.eu/1122/SuperSU/SR3-SuperSU-v2.82-SR3-20170813133244.zip
ashyx said:
You need to flash this version of SuperSU.
http://download.chainfire.eu/1122/SuperSU/SR3-SuperSU-v2.82-SR3-20170813133244.zip
Click to expand...
Click to collapse
Hey ashyx,
How does that version of SuperSU differ from the one I just tried to flash?
What causes the tab to bootloop in the first place?
Thanks for your help!!
dyrewolv said:
Hey ashyx,
How does that version of SuperSU differ from the one I just tried to flash?
What causes the tab to bootloop in the first place?
Thanks for your help!!
Click to expand...
Click to collapse
Difficult to explain, but it should prevent the bootloop.
Samsung and Google's updates can break root, so new patched versions need to be released to overcome the issue.
You should consult the Supersu beta thread for the changelog.
ashyx said:
Difficult to explain, but it should prevent the bootloop.
Samsung and Google's updates can break root, so new patched versions need to be released to overcome the issue.
You should consult the Supersu beta thread for the changelog.
Click to expand...
Click to collapse
gotcha. I'm 100% brand-new to rooting. After I get SuperSU rooted onto my tab... Can I proceed with installing other custom ROMs?
What's the standard procedure for rooting/flashing devices from one ROM to the next?
I must be ****ing up bad because the last (4) ROM's I've tried have all bootlooped.
I did notice that I forgot to enable developers options when my tab was still OEM.. haven't been able to boot into a menu to change it though
dyrewolv said:
gotcha. I'm 100% brand-new to rooting. After I get SuperSU rooted onto my tab... Can I proceed with installing other custom ROMs?
What's the standard procedure for rooting/flashing devices from one ROM to the next?
I must be ****ing up bad because the last (4) ROM's I've tried have all bootlooped.
I did notice that I forgot to enable developers options when my tab was still OEM.. haven't been able to boot into a menu to change it though
Click to expand...
Click to collapse
You don't need root to be able flash custom roms but you must enable OEM UNLOCK in developer settings or you will encounter FRP Lock and won't be able to boot until you flash the stock firmware.
You will also need to patch dm-verity before installing anything custom. SuperSU and Magisk already do this or you can can flash my boot patch which also disables forced encryption.
ashyx said:
You don't need root to be able flash custom roms but you must enable OEM UNLOCK in developer settings or you will encounter FRP Lock and won't be able to boot until you flash the stock firmware.
You will also need to patch dm-verity before installing anything custom. SuperSU and Magisk already do this or you can can flash my boot patch which also disables forced encryption.
Click to expand...
Click to collapse
I tried flashing stock firmware in Odin via the file "5.0.2_T810XXU1AOG6_T810XAR1AOG6_XAR" which I found on the stock firmware forum for the T810. Odin failed during the flash...
If I get SuperSU working can I enable OEM UNLOCK?
What is dm-verity?
dyrewolv said:
I tried flashing stock firmware in Odin via the file "5.0.2_T810XXU1AOG6_T810XAR1AOG6_XAR" which I found on the stock firmware forum for the T810. Odin failed during the flash...
If I get SuperSU working can I enable OEM UNLOCK?
What is dm-verity?
Click to expand...
Click to collapse
I suggest you flash the latest Marshmallow or Nougat update.
Dm-verity is a security mechanism.
http://updato.com/firmware-archive-select-model?q=Sm-t810&exact=1
ashyx said:
I suggest you flash the latest Marshmallow or Nougat update.
Dm-verity is a security mechanism.
http://updato.com/firmware-archive-select-model?q=Sm-t810&exact=1
Click to expand...
Click to collapse
I'm confused. So I should continue with trying to get the correct version of SuperSU flashed first..right? Then figure out what I need; Marshmallow or Nougat? I haven't even got the tablet to get past the Samsung logo, I cannot enable OEM Unlock.. Last night when I tried flashing stuff Odin did not want to cooperate. I get a "FAIL! Complete (Write) operation failed" message. Tried to flash the stock ROM file I listed below with both re-partition unchecked and checked with no success.
dyrewolv said:
I'm confused. So I should continue with trying to get the correct version of SuperSU flashed first..right? Then figure out what I need; Marshmallow or Nougat? I haven't even got the tablet to get past the Samsung logo, I cannot enable OEM Unlock.. Last night when I tried flashing stuff Odin did not want to cooperate. I get a "FAIL! Complete (Write) operation failed" message. Tried to flash the stock ROM file I listed below with both re-partition unchecked and checked with no success.
Click to expand...
Click to collapse
It probably fails because you can't downgrade.
It's up to you to whether to flash MM or NN.
You will need to update first and then flash twrp and then supersu.