I've been digging around all day for an answer, but I can only find what to do for an FRP error if you're locked out of your phone, nothing about installing custom recoveries and roms.
Downloaded all the latest, and some older in case, recoveries, auto roots, and unlockers + roms even though I never got that far, lol. Tried Odin 3.11 and 3.10, nothing older yet because I'm just annoyed now.
So, I reboot into bootloader with adb or pressing buttons, Odin detects the phone fine, thow the recovery into the AP section, hit start, it starts the flash, I see a touch of a progress bar, and I get the "Custom binary blocked by frp...." error at the bottom of the info lines at the top. Phone locks up, I'll reboot with vol-/pwr or just pull the battery, and it reboots fine.
So, what do I have to do to get around this FRP so I can install a new recovery/rom? I'm really sick of 6.0.1 just not working right or doing anything it promised =/
Mage42384 said:
I've been digging around all day for an answer, but I can only find what to do for an FRP error if you're locked out of your phone, nothing about installing custom recoveries and roms.
Downloaded all the latest, and some older in case, recoveries, auto roots, and unlockers + roms even though I never got that far, lol. Tried Odin 3.11 and 3.10, nothing older yet because I'm just annoyed now.
So, I reboot into bootloader with adb or pressing buttons, Odin detects the phone fine, thow the recovery into the AP section, hit start, it starts the flash, I see a touch of a progress bar, and I get the "Custom binary blocked by frp...." error at the bottom of the info lines at the top. Phone locks up, I'll reboot with vol-/pwr or just pull the battery, and it reboots fine.
So, what do I have to do to get around this FRP so I can install a new recovery/rom? I'm really sick of 6.0.1 just not working right or doing anything it promised =/
Click to expand...
Click to collapse
Have you turned off Factory Reset Protection (reactivation lock)? :silly:
nine5raptor said:
Have you turned off Factory Reset Protection (reactivation lock)? :silly:
Click to expand...
Click to collapse
Well that does seem like it would fix the problem doesn't it? Of course, can't find how to do that
Mage42384 said:
Well that does seem like it would fix the problem doesn't it? Of course, can't find how to do that
Click to expand...
Click to collapse
Settings - security - reactivation lock. Untick the box
nine5raptor said:
Settings - security - reactivation lock. Untick the box
Click to expand...
Click to collapse
Not there
Mage42384 said:
Not there
Click to expand...
Click to collapse
I'm trying to upload a screenshot....stupid app failing. What OS version?
Edit: nevermind, I see 6.0.1 which is what I'm on
nine5raptor said:
I'm trying to upload a screenshot....stupid app failing. What OS version?
Edit: nevermind, I see 6.0.1 which is what I'm on
Click to expand...
Click to collapse
Was hoping it was that when I first saw it earlier, but not showing in security, developers, or searches
Should be attached now.
My current security screen
Mage42384 said:
My current security screen
Click to expand...
Click to collapse
Do you have OEM unlock at the bottom of developer options?
And my builds and versions since that's probably a question coming up soon
nine5raptor said:
Do you have OEM unlock at the bottom of developer options?
Click to expand...
Click to collapse
That I do have have (^_^)
Mage42384 said:
That I do have have (^_^)
Click to expand...
Click to collapse
So they dropped their reactivation lock on the T3 variant...interesting. OEM unlock should allow you to proceed.
Samsung and all their silly variants....just to confuse us.
Reactivation Lock is Samsung's proprietary variant of the OEM unlock Google already provides.
nine5raptor said:
So they dropped their reactivation lock on the T3 variant...interesting. OEM unlock should allow you to proceed.
Samsung and all their silly variants....just to confuse us.
Reactivation Lock is Samsung's proprietary variant of the OEM unlock Google already provides.
Click to expand...
Click to collapse
Not sure if it's all T3s, seen a bunch of posts today about the T3 using the Samsung security version, but this is a very late model, lol. Think I bought this a little over 6 months ago
I'll see if I have time tomorrow to try it out, but def let you know by Thursday. Thanks for the help =)
Mage42384 said:
I'll see if I have time tomorrow to try it out, but def let you know by Thursday. Thanks for the help =)
Click to expand...
Click to collapse
Hope it works out for you. Sorry for all the confusion searching menus.
nine5raptor said:
Hope it works out for you. Sorry for all the confusion searching menus.
Click to expand...
Click to collapse
No worries, it got done lol. Spent 6 hours at work today finding all the wrong answers xD
nine5raptor said:
Hope it works out for you. Sorry for all the confusion searching menus.
Click to expand...
Click to collapse
Ok, installation works...but when I try to go to recovery, I just get the dead droid pic saying no command now =( Back to digging through forums, unless you have any advice for that, lol
Mage42384 said:
Ok, installation works...but when I try to go to recovery, I just get the dead droid pic saying no command now =( Back to digging through forums, unless you have any advice for that, lol
Click to expand...
Click to collapse
After flashing twrp, don't let it boot system. As soon as it reboots, pull the battery. Then boot into twrp. For some reason, MM changed the process and now you cannot boot into system before booting twrp for the first time.
nine5raptor said:
After flashing twrp, don't let it boot system. As soon as it reboots, pull the battery. Then boot into twrp. For some reason, MM changed the process and now you cannot boot into system before booting twrp for the first time.
Click to expand...
Click to collapse
Ah, it does that first boot restore recovery thing that my HTC's used to do...but with those, you'd get one shot into recovery at any time if I remember right (could be 3 weeks later, but only once, lol)
Related
K first off Yes I did do my research here looking to see if my problem was solved but just wanted to make sure by posting and explaining my situation. So pretty much, my nexus was having some issues and so I decided to flash the factory image. Everything all stock by the way. So I unlocked the boot loader flash everything manually and come to find that it kept spinning at the dots. It was probably at least 20 mins so I got pretty impatient. Went into stock recovery, wiped data and cache then proceeded to reboot. And here's probably where I screwed up. Got worried again to I went to fastboot, locked the damn boot loader, and wiped again and restarted into the endless swirl of the google dots.
Now, is there anything constructive, rather than bashing me, someone could provide me with? Thanks so much guys. Never thought this would happen with a nexus device.
http://forum.xda-developers.com/showthread.php?t=3059518
via fastboot(while in the bootloader), try this..
fastboot format userdata
fastboot format cache
fastboot reboot
jiv101 said:
http://forum.xda-developers.com/showthread.php?t=3059518
Click to expand...
Click to collapse
Has this been successful to you? I remember reading that earlier today but seems a bit confusing. Not too sure how it works. Would you be able to explain a little more?
jiv101 said:
http://forum.xda-developers.com/showthread.php?t=3059518
Click to expand...
Click to collapse
simms22 said:
via fastboot(while in the bootloader), try this..
fastboot format userdata
fastboot format cache
fastboot reboot
Click to expand...
Click to collapse
I can try this. About how long should I wait afterwards? That way I don't get impatient again
Sorry I never tried it
BraddahBoi808 said:
I can try this. About how long should I wait afterwards? That way I don't get impatient again
Click to expand...
Click to collapse
that other way, i have no idea. the way i posted, maybe 10-12 minites. well, if it boots.
Alright, I'll try out both. Thanks guys
Alright so nothing has worked so far. Anyone else know what I should do, or am I now forced to send it in for service?
BraddahBoi808 said:
Alright so nothing has worked so far. Anyone else know what I should do, or am I now forced to send it in for service?
Click to expand...
Click to collapse
There is nothing else you can do.
Can you unlock again or are you stuck locked.
toknitup420 said:
Can you unlock again or are you stuck locked.
Click to expand...
Click to collapse
Its not possible to unlock unless you boot into android and set "enable OEM unlock" but he cannot boot into android.
There is nothing at the moment he can do.
rootSU said:
Its not possible to unlock unless you boot into android and set "enable OEM unlock" but he cannot boot into android.
There is nothing at the moment he can do.
Click to expand...
Click to collapse
I wasn't sure if OEM unlock would untick itself since he never actually booted the os. I thought that only became unchecked when you boot the os. I do agree with you though. He's most likely SOL. I haven't seen anyone on XDA yet that's had any real success after being stuck in bootloader with locked bootloader.
toknitup420 said:
I wasn't sure if OEM unlock would untick itself since he never actually booted the os. I thought that only became unchecked when you boot the os. I do agree with you though. He's most likely SOL. I haven't seen anyone on XDA yet that's had any real success after being stuck in bootloader with locked bootloader.
Click to expand...
Click to collapse
I think you're right. If its ticked and you boot, I think it unticks it at boot. Whether a loop is enough to do that I don't know.
But another thing is that the default setting is unticked anyway. Until 5.1 at least to me, "allow OEM unlock" seems to be window dressing. I never needed to use this to unlock so I imaging for most people this setting remains untucked
rootSU said:
I think you're right. If its ticked and you boot, I think it unticks it at boot. Whether a loop is enough to do that I don't know.
But another thing is that the default setting is unticked anyway. Until 5.1 at least to me, "allow OEM unlock" seems to be window dressing. I never needed to use this to unlock so I imaging for most people this setting remains untucked
Click to expand...
Click to collapse
Yeah is normal to be unticked in 5.1. It won't affect anything though. But. If you relock without ticking it first and you can't boot to os then you're screwed. From what I've seen.
toknitup420 said:
Yeah is normal to be unticked in 5.1. It won't affect anything though. But. If you relock without ticking it first and you can't boot to os then you're screwed. From what I've seen.
Click to expand...
Click to collapse
Yes absolutely.
But what I meant is I never ticked mine in 5.0 and was still able to unlock. So since we could unlock without ticking it before 5.1, I imagine most people never ticked it before updating.. Then things changed.
Damn, I had a bad feeling about it as soon as it didn't start after 20 mins. So best bet would be to RMA it then and hope they fix it or should I try and go further than that by asking for a replacement since it still is under warranty and to bootloader is "locked"? lol
Sending it in for RMA. Getting a replacement device
Hi!
I was installing TWRP on my Nexus 6 just to try it out. Wasn't planning on rooting, just getting my "tap to wake" active. I followed the instructions for unlocking my Nexus 6 through the Dev Options. Then i continued to install a factory image and TWRP. It was all going good until I decided to lock the bootloader again. Now it's on a loop, where however I start the phone, it just goes to the TWRP startscreen and starts blinking at a slow pace.
Is there a way to enable the "allow OEM unlock" option in the Dev Options from a command line? Please can someone help? I really need to fix this, I got this phone yesterday and I feel so bad right now.
Thanks for any answers you might have.
/Diego
Sound like you have a bricked phone... There's a forum about it already started
jiv101 said:
Sound like you have a bricked phone... There's a forum about it already started
Click to expand...
Click to collapse
Can u link it please?
Format cache and userdata via fastboot. If that doesn't work, nothing you can do. Send for warranty
DiegoValdes said:
. It was all going good until I decided to lock the bootloader again.
Click to expand...
Click to collapse
Words to live by
Sent from my Google N6 on VZ
I never found a solution but luckily the place where I bought it felt sorry for me and gave me a new one with at new receipt. I don't feel like I deserve it though. Never again will I mess with the phone, stock for life.
Thanks for replying people! I appreciate it, truly.
Take care!
/Diego
Just don't relock the bootloader and we can get you out of any other issue [emoji6]
Sent from my Google N6 on VZ
Read, read, succeed.
http://forum.xda-developers.com/showthread.php?t=3067302
DiegoValdes said:
I never found a solution but luckily the place where I bought it felt sorry for me and gave me a new one with at new receipt. I don't feel like I deserve it though. Never again will I mess with the phone, stock for life.
Thanks for replying people! I appreciate it, truly.
Take care!
/Diego
Click to expand...
Click to collapse
Don't do that. This is part of learning. Sure its stinks that you messed you're phone up. But now you know what you did wrong so just don't do it again. Lol. We've all bricked one or two devices, it comes with the territory. I'm glad the store helped you out though. That's really cool of them.
I soft bricked a phone once and it took me a few days to figure it out. I think the worst part was my wife asking me things like; how much did that phone cost? Aren't computers kind of your job? What number should I call you on?
Sent from my Google N6 on VZ
Is there any solution for bootloop and locked bootloader ?
Thanks !
usernome said:
Is there any solution for bootloop and locked bootloader ?
Thanks !
Click to expand...
Click to collapse
If you have stock recovery, first try clearing the cache via recovery. If that doesn't work, factory data reset from stock recovery.
If TWRP is installed, reflash your ROM. Or factory reset option.
Otherwise,
fastboot format userdata
fastboot format cache
usernome said:
Is there any solution for bootloop and locked bootloader ?
Thanks !
Click to expand...
Click to collapse
All else fails. Grab this and go back to stock. Then use it to upload your bootloader and root.
http://forum.xda-developers.com/showthread.php?t=2947452
Use the Tool Kit
Sent from my HTC6535LVW using Tapatalk
DiegoValdes said:
Hi!
I was installing TWRP on my Nexus 6 just to try it out. Wasn't planning on rooting, just getting my "tap to wake" active. I followed the instructions for unlocking my Nexus 6 through the Dev Options. Then i continued to install a factory image and TWRP. It was all going good until I decided to lock the bootloader again. Now it's on a loop, where however I start the phone, it just goes to the TWRP startscreen and starts blinking at a slow pace.
Is there a way to enable the "allow OEM unlock" option in the Dev Options from a command line? Please can someone help? I really need to fix this, I got this phone yesterday and I feel so bad right now.
Thanks for any answers you might have.
/Diego
Click to expand...
Click to collapse
What demon possessed you to relock your bootloader??!?!?
Also, even if twrp doesn't start "fully", it should still give you access through ADB, which is all you need to wipe your data partition. I'm not sure why people recommend wiping your cache partition, it won't do you any good.
sorry if this has been covered but i cant find anything the same as my situation and im pretty stuck.
I have just bought a nexus 6 and the phone prompted me to update to 5.1 so i have, once it restarted i am now stuck in a boot loop with it saying optimizing apps then restarts and the same again, i have tried booting into recovery and wipe data but just get the same.
I have tried using nexus root toolkit (wugsfresh) however cannot find fastboot connectivity so im stuck there.
The phone is not rooted and i cant seem to get access through adb ( i have not turned usb debugging on as the phone is new)
I really am not too clued up so im sorry if i need things explaining abit more.
Thanks in advance
viper1402 said:
sorry if this has been covered but i cant find anything the same as my situation and im pretty stuck.
I have just bought a nexus 6 and the phone prompted me to update to 5.1 so i have, once it restarted i am now stuck in a boot loop with it saying optimizing apps then restarts and the same again, i have tried booting into recovery and wipe data but just get the same.
I have tried using nexus root toolkit (wugsfresh) however cannot find fastboot connectivity so im stuck there.
The phone is not rooted and i cant seem to get access through adb ( i have not turned usb debugging on as the phone is new)
I really am not too clued up so im sorry if i need things explaining abit more.
Thanks in advance
Click to expand...
Click to collapse
flash a factory image, your update went no good. if you havent ever done this, i DO NOT RECOMMEND using a toolkit. toolkits are good for people who know what they are doing. if you dont kniw, you will remain clueless, and could make things much worse.
simms22 said:
flash a factory image, your update went no good. if you havent ever done this, i DO NOT RECOMMEND using a toolkit. toolkits are good for people who know what they are doing. if you dont kniw, you will remain clueless, and could make things much worse.
Click to expand...
Click to collapse
am i able to flash a factory image without being able to connect the device via adb? i just wasnt able to find the device on it
Thanks for the reply
viper1402 said:
am i able to flash a factory image without being able to connect the device via adb? i just wasnt able to find the device on it
Thanks for the reply
Click to expand...
Click to collapse
factory images are only flashed while youre in your bootloader, via fastboot. thetes a stick for directions in the general thread.
simms22 said:
factory images are only flashed while youre in your bootloader, via fastboot. thetes a stick for directions in the general thread.
Click to expand...
Click to collapse
right got it sorted thanks for the help now its saying i have an update for 5.1.1 is it worth doing this or is there a strong chance it will bootloop again ?
viper1402 said:
right got it sorted thanks for the help now its saying i have an update for 5.1.1 is it worth doing this or is there a strong chance it will bootloop again ?
Click to expand...
Click to collapse
I'd suggest avoiding the OTA's and fastboot flash the latest factory image. LMY48I
IMHO....
viper1402 said:
right got it sorted thanks for the help now its saying i have an update for 5.1.1 is it worth doing this or is there a strong chance it will bootloop again ?
Click to expand...
Click to collapse
is it worth it? YES! if you want, you can flaah the factory image for 5.1.1 instead of taking the ota. but chances are that the ota will be fine.
viper1402 said:
right got it sorted thanks for the help now its saying i have an update for 5.1.1 is it worth doing this or is there a strong chance it will bootloop again ?
Click to expand...
Click to collapse
How did u get it sorted? I just had a friend call me with exactly the same problem! He's not very tech savvy so it's proving difficult talking him thru it, so if u found an easy solution for me to pass on that would be great ?
boxa72 said:
How did u get it sorted? I just had a friend call me with exactly the same problem! He's not very tech savvy so it's proving difficult talking him thru it, so if u found an easy solution for me to pass on that would be great
Click to expand...
Click to collapse
As stated before. Forget OTA. Unlock bootloader and fastboot flash the images manually. Do not take OTA with bootloader locked. If OTA fails have to RMA. No fix.
I had the same issue today and like PRDOG1 said I was talking to him on my forum post. As soon as you get the phone unlock that bootloader, then just do flashes through the bootloader. It is safer, and as long as that bootloader is unlocked you can go ahead and load up any image you want thats factory and you will be fine.
Well it should be fine then coz the carriers in Aussie don't lock bootloaders. I just told him to bring the phone to me n I'll re-flash a stock image for him but I thought u may have found another way as I'm more familiar with Samsung and Windows than I am with Nexus. It seems pretty common this bootloop stuff after OTA with the N6.
Sent from my SM-G920I using Tapatalk
I suspect you are confusing carrier SIM lock with bootloader lock.
Carriers do not usually do anything with bootloader lock - they may force a SIM lock to their SIM cards however.
On the Nexus 6 however, unlocking the bootloader is pretty easy (assuming you can boot to the OS and select the option to allow OEM unlock). I'd recommend leaving the bootloader unlocked and flashing twrp asap, in case of any issues later.
Altho in Australia they don't carrier lock bootloaders the software comes locked for security reasons. If he didn"t unlock prior to the OTA update it is bricked and will require RMA.
I just bought myself an almost mint condition Nexus 6 (build MRA58R). It's running Marshmallow and I tried rooting it today. After I researched how to go by obtaining root I tried it out, felt very confident, didn't come across any errors. But then when I was booting back up, a screen with red letters saying something about my phone being corrupted was not allowing my phone to boot. Naturally, first I panicked. Afterwards I researched, found and then executed a manual flash of system, boot, bootloader, cache and recovery images. Then, my phone was back up and running. Discouraged and defeated, here I am knowing I could've done some better things with my time than mash commands into a terminal to fix my nooby mistake for a few hours. How should I approach obtaining root on my phone if at all possible with my model?
meeniemuffin said:
.... But then when I was booting back up, a screen with red letters saying something about my phone being corrupted was not allowing my phone to boot.
Click to expand...
Click to collapse
You could bring Google to court when your device is working 100% and the message says it is corrupt. Read the OP of this link. http://forum.xda-developers.com/showthread.php?t=3059493
meeniemuffin said:
I just bought myself an almost mint condition Nexus 6 (build MRA58R). It's running Marshmallow and I tried rooting it today. After I researched how to go by obtaining root I tried it out, felt very confident, didn't come across any errors. But then when I was booting back up, a screen with red letters saying something about my phone being corrupted was not allowing my phone to boot. Naturally, first I panicked. Afterwards I researched, found and then executed a manual flash of system, boot, bootloader, cache and recovery images. Then, my phone was back up and running. Discouraged and defeated, here I am knowing I could've done some better things with my time than mash commands into a terminal to fix my nooby mistake for a few hours. How should I approach obtaining root on my phone if at all possible with my model?
Click to expand...
Click to collapse
-enable "OEM unlocking" in developer options
-unlock bootloader
-flash TWRP using fastboot
-flash a custom kernel
-flash SuperSU 2.52
-KEEP BOOTLOADER UNLOCKED
-KEEP "OEM unlocking" ENABLED
---------- Post added at 09:50 AM ---------- Previous post was at 09:42 AM ----------
NLBeev said:
You could bring Google to court when your device is working 100% and the message says it is corrupt. Read the OP of this link. http://forum.xda-developers.com/showthread.php?t=3059493
Click to expand...
Click to collapse
There's nothing mentioned there.
Droidphilev said:
There's nothing mentioned there.
Click to expand...
Click to collapse
Hmm, here the links works. It is a link to a stock rom that is already rooted.
The rom is updated with the latest security OTA.
Full name of the OP.
[ROM]【6.0_r3】Stock MRA58R [Lite] - 【Marshmallow】【hC kernel】- 11/05/15
NLBeev said:
Hmm, here the links works. It is a link to a stock rom that is already rooted.
The rom is updated with the latest security OTA.
Full name of the OP.
[ROM]【6.0_r3】Stock MRA58R [Lite] - 【Marshmallow】【hC kernel】- 11/05/15
Click to expand...
Click to collapse
It indeed works but i thought it would bring to a page about the court thing you have mentioned.
Droidphilev said:
It indeed works but i thought it would bring to a page about the court thing you have mentioned.
Click to expand...
Click to collapse
No I was joking, sorry. But there is something serious behind the joke.
Here on XDA there are too many posts/questions about the 'corrupt message'.
The distance between ' customizing the phone' and 'Google' is growing.
NLBeev said:
No I was joking, sorry. But there is something serious behind the joke.
Here on XDA there are too many posts/questions about the 'corrupt message'.
The distance between ' customizing the phone' and 'Google' is growing.
Click to expand...
Click to collapse
Aha! i saw you posting this before but never knew that it was a joke
I didn't even need to read all this stuff. First thing I did was get into developer mode and almost instinctual that I turned on OEM unlocking before setting about unlocking the bootloader.
Sent from my Nexus 6 using Tapatalk
Yeah I bought my N6 recently and had a bad first time experience too. I ended up using a toolkit to root and all that, didn't need a custom rom so I kept it stock with TWRP and I'm very happy. Since then, I rooted some of the old devices I had laying around (you can check my signature), so I should be more prepared next time I need to update. My problem is I didn't really understand the commands, what did what and what exactly was required for root. Now that I have had plenty to practice with I'm pretty comfortable with commands and recoveries. Practice makes perfect I guess
NLBeev said:
No I was joking, sorry. But there is something serious behind the joke.
Here on XDA there are too many posts/questions about the 'corrupt message'.
The distance between ' customizing the phone' and 'Google' is growing.
Click to expand...
Click to collapse
Pretty much the trend. I bet by Android 7.0, rooting will be impossible.
shadowcore said:
Pretty much the trend. I bet by Android 7.0, rooting will be impossible.
Click to expand...
Click to collapse
I hope not. Google's software and design will be the weak point. Google could not give us some simple options like a dark interface, reboot options and dpi settings.
So, people, to sum it all up... The road to obtaining root on this Marshmallow enabled phone is?
If bootload is locked, unlock it - This will erase everything backup your device
1. Get modified boot.img for your version, flash it
2. Flash twrp
3. Flash SuperSu 2.52
meeniemuffin said:
So, people, to sum it all up... The road to obtaining root on this Marshmallow enabled phone is?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=63999613&postcount=3
!!!
Droidphilev said:
http://forum.xda-developers.com/showpost.php?p=63999613&postcount=3
!!!
Click to expand...
Click to collapse
Sorry! Slow to learn over here. I still have a question...do I need a custom kernel and flash stock rom? Or just a custom stock ROM thats already prerooted? Both, perhaps? Would I have to flash Twrp in order to even do this?
meeniemuffin said:
Sorry! Slow to learn over here. I still have a question...do I need a custom kernel and flash stock rom? Or just a custom stock ROM thats already prerooted? Both, perhaps? Would I have to flash Twrp in order to even do this?
Click to expand...
Click to collapse
You have a stockrom now, right?
if you want to keep that for now then this is the easiest way. The TWRP step is there to be able to flash the custom kernel. (and of course make backups and flash other roms in the future)
Droidphilev said:
You have a stockrom now, right?
if you want to keep that for now then this is the easiest way. The TWRP step is there to be able to flash the custom kernel. (and of course make backups and flash other roms in the future)
Click to expand...
Click to collapse
I had an epiphany earlier. I did everything....it all hit me at once. I finally managed to get Pure Nexus ROM working. Time for a test drive.
Thanks for the advice.
meeniemuffin said:
I had an epiphany earlier. I did everything....it all hit me at once. I finally managed to get Pure Nexus ROM working. Time for a test drive.
Thanks for the advice.
Click to expand...
Click to collapse
enjoy!
but DO NOT forget to keep "OEM unlocking" enabled!
(it will save you when you ever get locked out from your google acoount because you became aflashoholic)
Hello. I have unlocked bootloader successfully (it says "unlocked" at screen and also "tampered"). I have all the fastboot/adb software on my windows pc and can communicate with the phone. I flash recovery via fastboot and it is successful...includes a "recovery" option under bootloader options but it just flashes a disclaimer screen and quickly goes back to bootloader screen. Without custom recovery I cannot root this phone which is my goal. I have tried to reflash other recovery images, including cmw and twrp - I believe cmw is on it now but it won't open.
Hoping someone can assist me with this.
Thank you
belowHeights00 said:
Hello. I have unlocked bootloader successfully (it says "unlocked" at screen and also "tampered"). I have all the fastboot/adb software on my windows pc and can communicate with the phone. I flash recovery via fastboot and it is successful...includes a "recovery" option under bootloader options but it just flashes a disclaimer screen and quickly goes back to bootloader screen. Without custom recovery I cannot root this phone which is my goal. I have tried to reflash other recovery images, including cmw and twrp - I believe cmw is on it now but it won't open.
Hoping someone can assist me with this.
Thank you
Click to expand...
Click to collapse
Reflash whichever recovery you plan to use then remove the battery and put it back in then hold the volume down button and then press and hold the power button at the same time and the phone should then boot to recovery. Make a backup after so you have something to fall back on just in case.
MrMike2182 said:
Reflash whichever recovery you plan to use then remove the battery and put it back in then hold the volume down button and then press and hold the power button at the same time and the phone should then boot to recovery. Make a backup after so you have something to fall back on just in case.
Click to expand...
Click to collapse
Thanks for the reply! I just now gave that a shot but it had no effect.
belowHeights00 said:
Thanks for the reply! I just now gave that a shot but it had no effect.
Click to expand...
Click to collapse
Are you actually holding both buttons down at the same time until the screen turns on? Don't let them go hold them both down until your screen lights up. Then select recovery but if it doesn't work then try below.
Try flashing this version of twrp https://twrp.me/devices/htcdesire510usa32bit.html ... If you're not in the USA I need to know.
Flashing twrp didn't change anything unfortunately. I recently tried re-locking my bootloader and attempted to flash stock images back to the phone but when I press "yes" to the question about voiding the warranty before unlocking the bootloader again...the disclaimer just flashes and the phone won't let it.
Also, I cannot seem to restore it to stock through the menu...nor the bootloader screen.
So now I have "tampered" and "Relocked" banners on top of bootloader screen.
One the upside, the phone itself works fine (I currently only use it for wifi).
Only thing I can think of is I originally flashed a corrupt recovery img (or incompatible version).
Hoping you or someone else has any ideas as to how to get this thing working again. I'd be happy with reverting completly back to stock and starting the process over..
belowHeights00 said:
Flashing twrp didn't change anything unfortunately. I recently tried re-locking my bootloader and attempted to flash stock images back to the phone but when I press "yes" to the question about voiding the warranty before unlocking the bootloader again...the disclaimer just flashes and the phone won't let it.
Also, I cannot seem to restore it to stock through the menu...nor the bootloader screen.
So now I have "tampered" and "Relocked" banners on top of bootloader screen.
One the upside, the phone itself works fine (I currently only use it for wifi).
Only thing I can think of is I originally flashed a corrupt recovery img (or incompatible version).
Hoping you or someone else has any ideas as to how to get this thing working again. I'd be happy with reverting completly back to stock and starting the process over..
Click to expand...
Click to collapse
What service provider are you using?
Don't toss the unlock code you got from HTC you're gonna need the very first one you got keep it forever.
I'm using Boost but I think I figured it out. It ended up being a corrupt download of cmw. I actually used an ruu to get back stock and now the whole process went smoothly. Just looking for a rom that fits...got any recommendations in that area?
belowHeights00 said:
I'm using Boost but I think I figured it out. It ended up being a corrupt download of cmw. I actually used an ruu to get back stock and now the whole process went smoothly. Just looking for a rom that fits...got any recommendations in that area?
Click to expand...
Click to collapse
Not really since everyone has their own tastes but I'd advise you to create a backup in your recovery so you can use it in case something goes wrong. Currently me and a friend are working on CM13/12..
MrMike2182 said:
Not really since everyone has their own tastes but I'd advise you to create a backup in your recovery so you can use it in case something goes wrong. Currently me and a friend are working on CM13/12..
Click to expand...
Click to collapse
Funny enough I never made a backup before and constantly have to re-locate stock images due to soft bricking. I now am making backups so as not to go through that again.
I have a question perhaps you could answer -- if I install a rom that doesn't include any additional tweaks such as extended personaliation options in settings (transitions, etc, etc.)..is there a mod I can flash to achieve that?
belowHeights00 said:
Funny enough I never made a backup before and constantly have to re-locate stock images due to soft bricking. I now am making backups so as not to go through that again.
I have a question perhaps you could answer -- if I install a rom that doesn't include any additional tweaks such as extended personaliation options in settings (transitions, etc, etc.)..is there a mod I can flash to achieve that?
Click to expand...
Click to collapse
For extended personalizing other than developer options, I'd use Xposed.
MrMike2182 said:
Not really since everyone has their own tastes but I'd advise you to create a backup in your recovery so you can use it in case something goes wrong. Currently me and a friend are working on CM13/12..
Click to expand...
Click to collapse
How have you started working on that, i gthink i should join too. Are you working on the USA model or UK? (X86 or X64)
Zubagy said:
How have you started working on that, i gthink i should join too. Are you working on the USA model or UK? (X86 or X64)
Click to expand...
Click to collapse
The USA model because myself and rb don't have the EU phone to even test anything on it.. We still have a lot of booting problems right now. I'd say if you wanted to help I'd have to ask what you know about building roms from source? Have you done it before?
P.S: There's already a CM-12.1 available for the EU model although it does have some issues.. You should read about it if you want to try it..
MrMike2182 said:
The USA model because myself and rb don't have the EU phone to even test anything on it.. We still have a lot of booting problems right now. I'd say if you wanted to help I'd have to ask what you know about building roms from source? Have you done it before?
P.S: There's already a CM-12.1 available for the EU model although it does have some issues.. You should read about it if you want to try it..
Click to expand...
Click to collapse
Not really, But perhaps it time to learn
Zubagy said:
Not really, But perhaps it time to learn
Click to expand...
Click to collapse
It's pretty cool and fun once you get the hang of making things and seeing them function right, and the other thing is... You'll need a pretty decent computer to compile/build with and it'll need to have at least 4GB ram (more is better) and about 50 to 100 GB hard drive space for building your rom plus the CM source code needs to be on your system too...
MrMike2182 said:
It's pretty cool and fun once you get the hang of making things and seeing them function right, and the other thing is... You'll need a pretty decent computer to compile/build with and it'll need to have at least 4GB ram (more is better) and about 50 to 100 GB hard drive space for building your rom plus the CM source code needs to be on your system too...
Click to expand...
Click to collapse
I guess then am good to go, are those the only requirements....... i dont have any source code though
Zubagy said:
I guess then am good to go, are those the only requirements....... i dont have any source code though
Click to expand...
Click to collapse
Well how fast is your internet? By the way.. I'm using a Linux operating system... What are you using? It cannot be done on Windows unless you use a VM.
Hey, I also faced this problem but I find the solution and successfully flash twrp
Hey, I also faced this problem but I find the solution and successfully flash tarp recovery.
belowHeights00 said:
Hello. I have unlocked bootloader successfully (it says "unlocked" at screen and also "tampered"). I have all the fastboot/adb software on my windows pc and can communicate with the phone. I flash recovery via fastboot and it is successful...includes a "recovery" option under bootloader options but it just flashes a disclaimer screen and quickly goes back to bootloader screen. Without custom recovery I cannot root this phone which is my goal. I have tried to reflash other recovery images, including cmw and twrp - I believe cmw is on it now but it won't open.
Hoping someone can assist me with this.
Thank you
Click to expand...
Click to collapse
MrMike2182 said:
Well how fast is your internet? By the way.. I'm using a Linux operating system... What are you using? It cannot be done on Windows unless you use a VM.
Click to expand...
Click to collapse
Sorry for the delay, yes.... i am using vm ware... my net is not that fast... but it can get things done.