Possible to make a custom recovery for this device.. - Sprint LG G4

I think it's possible because the amazon fifth Gen, it has a locked bootloader but we were still able to boot into a custom recovery by using the original kernel of the device somehow. I know it's not the same thing but if we have access to do commands we can flash a custom recovery that way. I'll be asking the guy who made the custom recovery on how he did it. Then maybe we can modify the android 6.0 update zip and inject root into it??

I have that device. It requires fastboot i believe.

Not holding my breath

danweb66 said:
I have that device. It requires fastboot i believe.
Click to expand...
Click to collapse
It is possible to nuke the laf and gain access to fastboot. You could then flash your needed commands and restore laf.

tabp0le said:
It is possible to nuke the laf and gain access to fastboot. You could then flash your needed commands and restore laf.
Click to expand...
Click to collapse
I was about to say exactly that. A fun little trick I picked up with my G2 when I bricked it really damn bad and basically had zero options for getting it to boot again without access to fastboot, which was so wonderfully omitted by LG despite the G2 and the Nexus 5 being almost the same phone under the hood, so I was a bit reckless thinking they wouldn't have made the software so drastically different when they're almost identical hardware.
I have a feeling nuking laf and using a kindle method really could work, but unfortunately I don't have a backup phone to move my number over to while I try until I get a replacement Moto X under warranty (that one literally bricked itself within six months running stock)

I don't think the 5th gen fire has 6.0...I may be mistaken tho.

No I'm not saying use fastboot I'm saying flash the recovery using dd commands instead. You can back up the recovery just incase something happensAL and flash that back. Meaning nuking only the recovery partition and flashing a modified boot.img

Interesting, sounds possible but you would think that someone more advanced than us would of considered this.

Awesomeslayerg said:
No I'm not saying use fastboot I'm saying flash the recovery using dd commands instead. You can back up the recovery just incase something happensAL and flash that back. Meaning nuking only the recovery partition and flashing a modified boot.img
Click to expand...
Click to collapse
base_ten said:
Interesting, sounds possible but you would think that someone more advanced than us would of considered this.
Click to expand...
Click to collapse
I'm pretty sure that's what I did for the tmoble version...was side load the recovery with dd commands..I think the twrp recovery needs to made for sprint tho
Edit: http://forum.xda-developers.com/tmo...recovery-twrp-2-8-7-0-touch-recovery-t3164874 there was 2 ways 2 do it one with flashify an the other with dd commands...not sure if it will work for us but who knows...

Hate to resurrect a perfectly dead thread, but I'm guessing no one has tried this with any success?

Ive been looking into things like i know g2 had lokinexploit att g3 images and recoverys are bumped both had lock bls but i dont know yet i just got this g4 last night and ill be stuck with it for at least a year or so so im in for testing i aint worried bout waranty and i got insuarance have in my opinion better tech skills than a lot of people i know so im all game

Related

RAZR recovery on Droid 4?

Anyone tried using the RAZR recovery on the Droid 4? Lookin to do up the Arctic rom, but would feel much better if I could get a nandroid.
EDIT: This is the link to the RAZR recovery I was mainly thinking of: http://forum.xda-developers.com/showthread.php?t=1385283
jgardner said:
Anyone tried using the RAZR recovery on the Droid 4? Lookin to do up the Arctic rom, but would feel much better if I could get a nandroid.
EDIT: This is the link to the RAZR recovery I was mainly thinking of: http://forum.xda-developers.com/showthread.php?t=1385283
Click to expand...
Click to collapse
Why not do the nandroid with safestrap?
I didn't think safestrap was working with the D4?
jgardner said:
I didn't think safestrap was working with the D4?
Click to expand...
Click to collapse
I dont know whats going on lol.....everyone is coming with all these different stories. I used the root exploit that was out and used the safestrap for recovery. I dont think I did anything different than anyone else. And then i took a chance flashing a Razr rom
Oh yeah, the original utility had the safestrap didn't it? The latest utility doesn't anymore (although I think it works).
Sent from my DROID4 using Tapatalk
jgardner said:
Oh yeah, the original utility had the safestrap didn't it? The latest utility doesn't anymore (although I think it works).
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
I took it out until Hashcode brings it out for Droid 4. I've been corresponding with him and if the maker of Safestrap tells you it isn't safe to use on Droid 4 yet then you usually should listen.
All up to your risk though.
I made a nandroid using safestrap, or thought i did. I made my backup so i figured i would try that arctic rom so i followed the directions step by step. After i wiped cache and factory reset i went install from sd and the arctic rom that i know i put on it was not there. So i figured i would flash back to the backup i just made and try the process of putting the arctic on my sd. Some how i ended up bricking my phone and am now stuck in bootloader and my device is looked. Have you or anyone else made an sbf, oneclick recovery or a way to unbrick my D4?
Briteyez83 said:
I made a nandroid using safestrap, or thought i did. I made my backup so i figured i would try that arctic rom so i followed the directions step by step. After i wiped cache and factory reset i went install from sd and the arctic rom that i know i put on it was not there. So i figured i would flash back to the backup i just made and try the process of putting the arctic on my sd. Some how i ended up bricking my phone and am now stuck in bootloader and my device is looked. Have you or anyone else made an sbf, oneclick recovery or a way to unbrick my D4?
Click to expand...
Click to collapse
Not yet. There is a reason we have warnings on these...
I hope we get fastboot yet. You cannot just "make them" they have to be leaked.
FYI Motorola does Fastboot files, not SBF now.
mattlgroff said:
Not yet. There is a reason we have warnings on these...
I hope we get fastboot yet. You cannot just "make them" they have to be leaked.
FYI Motorola does Fastboot files, not SBF now.
Click to expand...
Click to collapse
Im new to root even though i have learned pretty quick. Finally after much pain and suffering got my X's bootloader unlocked and rooted some time in Nov. What does leaked mean and what is the difference between fastboot files and sbf?
---------- Post added at 02:27 AM ---------- Previous post was at 02:24 AM ----------
As far as the warnings i didnt see the warning to not use safestrap till i got on here and it was to late. I figured since i was able to boot into recovery and make a backup i would be ok
Briteyez83 said:
Im new to root even though i have learned pretty quick. Finally after much pain and suffering got my X's bootloader unlocked and rooted some time in Nov. What does leaked mean and what is the difference between fastboot files and sbf?
Click to expand...
Click to collapse
You would be Man of the Year if you did that. You mean you bootstrapped it, right?
Leaked means they have to trickle out from Motorola/Verizon somehow.. either on purpose or by "accident" somebody on the inside putting them out there for use by our wonderful devs.
As for SBF vs fasboot, i dont know exactly the difference but think of them as different types of "recovery" that can be used to fully restore your phone to factory condition.
Briteyez83 said:
I made a nandroid using safestrap, or thought i did. I made my backup so i figured i would try that arctic rom so i followed the directions step by step. After i wiped cache and factory reset i went install from sd and the arctic rom that i know i put on it was not there. So i figured i would flash back to the backup i just made and try the process of putting the arctic on my sd. Some how i ended up bricking my phone and am now stuck in bootloader and my device is looked. Have you or anyone else made an sbf, oneclick recovery or a way to unbrick my D4?
Click to expand...
Click to collapse
Which FASTBOOT error are you seeing? It should be referencing one of the partitions.
Sent from my DROID4 using XDA App
greekchampion04 said:
You would be Man of the Year if you did that. You mean you bootstrapped it, right?
Leaked means they have to trickle out from Motorola/Verizon somehow.. either on purpose or by "accident" somebody on the inside putting them out there for use by our wonderful devs.
As for SBF vs fasboot, i dont know exactly the difference but think of them as different types of "recovery" that can be used to fully restore your phone to factory condition.
Click to expand...
Click to collapse
Yes, i mean bootstrapped and you mean woman of the year, right? My bf said the difference between the two is SBF your makinga mirror image of everything and doing a complete system dump and fastboot is just cutting the power for a split sec. It will clear your immediate cache but some memory is still there.
Briteyez83 said:
Yes, i mean bootstrapped and you mean woman of the year, right? My bf said the difference between the two is SBF your makinga mirror image of everything and doing a complete system dump and fastboot is just cutting the power for a split sec. It will clear your immediate cache but some memory is still there.
Click to expand...
Click to collapse
I cant help unless I know what your error message says when you turn on the phone. :/
Sent from my DROID4 using XDA App
Send me your email addy in a message and ill send you a pic of it
Briteyez83 said:
Send me your email addy in a message and ill send you a pic of it
Click to expand...
Click to collapse
Ok, so it's WEBTOP that is behaving badly.
Let me see if I can get an RSD Lite file for you to try. Do you know how to use that?
Hashcode said:
Ok, so it's WEBTOP that is behaving badly.
Let me see if I can get an RSD Lite file for you to try. Do you know how to use that?
Click to expand...
Click to collapse
No, i dont. Im new to root, just rooted in nov. If you give me something thst would fix it that would be awesome.
Unfortunately, the fix isn't exactly a simple one.
It comes in 3 parts (assuming you're on Windows):
1. You'll need to download and install RSD Lite which is what is used to flash the fastboot restore files from Motorola:
http://dev-host.org/ug07spima1mq/RSDLite5.5.rar
2. Download and install the Motorola USB drivers to recognize your phone in fastboot mode:
http://www.mediafire.com/?z5qpc8v3xza25e6
3. I'm setting up a mini WEBTOP fastboot restore file based on the latest RAZR fastboot files (I say small.. but it's still quite a large download). The version is slightly off from the D4's but it might be close enough, and I think it's worth a shot:
[ Getting this file setup will take me about an hour, but you can get steps 1 and 2 ready for now ]
ALSO KEEP THE PHONE POWERED OFF FOR NOW TO SAVE BATTERY. FASTBOOT WILL NOT PROGRAM WITH A LOW BATTERY.
Hashcode said:
Unfortunately, the fix isn't exactly a simple one.
It comes in 3 parts (assuming you're on Windows):
1. You'll need to download and install RSD Lite which is what is used to flash the fastboot restore files from Motorola:
http://dev-host.org/ug07spima1mq/RSDLite5.5.rar
2. Download and install the Motorola USB drivers to recognize your phone in fastboot mode:
http://www.mediafire.com/?z5qpc8v3xza25e6
3. I'm setting up a mini WEBTOP fastboot restore file based on the latest RAZR fastboot files (I say small.. but it's still quite a large download). The version is slightly off from the D4's but it might be close enough, and I think it's worth a shot:
[ Getting this file setup will take me about an hour, but you can get steps 1 and 2 ready for now ]
ALSO KEEP THE PHONE POWERED OFF FOR NOW TO SAVE BATTERY. FASTBOOT WILL NOT PROGRAM WITH A LOW BATTERY.
Click to expand...
Click to collapse
Thank you so much. My bf is leaving his laptop here so that i can do this since he is building the main cpu right now. Ill makev sure i let you know if this works or not after ive finished. I was going to have verizon send me a new one since i just bought my D4 on the 17th and i have 14 days. But i just dont want to risk my warrenty getting voided. Once again thank you.
Briteyez83 said:
Thank you so much. My bf is leaving his laptop here so that i can do this since he is building the main cpu right now. Ill makev sure i let you know if this works or not after ive finished. I was going to have verizon send me a new one since i just bought my D4 on the 17th and i have 14 days. But i just dont want to risk my warrenty getting voided. Once again thank you.
Click to expand...
Click to collapse
If it works, I'll create a new thread with the instructions as I believe there are a few in your situation.
Yes there is quite a few. Ill let you know as soon as i can

FireTV Partial Bootloader Unlock

Well it's a little early for Christmas... but here is a special gift. This will allow the bootloader to load things from boot or recovery without them needing to be patched. This is not a full unlock and will not enable fastboot boot or fastboot flash. Obviously this will only work if you are rooted.
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Using this tool won't brick your Fire TV, but doing stupid things afterwards might. I will stress here that flashing something bad to boot is a guaranteed way to brick because if the kernel can't boot you have no way to get back to recovery. For testing kernels, it's best to flash recovery to the boot partition and the new kernel to test to the recovery partition.
To use:
Downgrade: You must first downgrade to 51.1.0.2. If you already have CWM installed, you can skip this.
adb push aftv-unlock /data/local/tmp/
adb shell
chmod 755 /data/local/tmp/aftv-unlock
su
/data/local/tmp/aftv-unlock unlock
Afterwards you should see this message:
Code:
Attempting to unlock...
All done!
If not, something went wrong. If for whatever reason you want to relock the bootloader, you can use this command:
Code:
/data/local/tmp/aftv-unlock lock
You can download it here.
WOW, just WOW, awesome work rbox!
I was definitely not expecting this.
rbox said:
Well it's a little early for Christmas... but here is a special gift. This will allow the bootloader to load things from boot or recovery without them needing to be patched. This is not a full unlock and will not enable fastboot boot or fastboot flash. Obviously this will only work if you are rooted.
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Using this tool won't brick your Fire TV, but doing stupid things afterwards might. I will stress here that flashing something bad to boot is a guaranteed way to brick because if the kernel can't boot you have no way to get back to recovery. For testing kernels, it's best to flash recovery to the boot partition and the new kernel to test to the recovery partition.
To use:
Downgrade: You must first downgrade to 51.1.0.2. If you already have CWM installed, you can skip this.
adb push aftv-unlock /data/local/tmp/
adb shell
chmod 755 /data/local/tmp/aftv-unlock
su
/data/local/tmp/aftv-unlock unlock
Afterwards you should see this message:
Code:
Attempting to unlock...
All done!
If not, something went wrong. If for whatever reason you want to relock the bootloader, you can use this command:
Code:
/data/local/tmp/aftv-unlock lock
You can download it here.
Click to expand...
Click to collapse
Congrats to you
And Merry Christmas to us FTV users!
BTW, could you please tell me the console messages for lock failure and unlock failure? (may they never occur)
..
JJ-KwiK said:
Awesome!
Thanks man!
Click to expand...
Click to collapse
maybe we can get some real mods for this device now. different roms and what not.
just ran the unlock and it worked like a charm
Rbox do you know if the bootloader can boot from usb?
Does this require a minimal CWM version of yours?
I installed your Recovery (CWM) - on all 4 of my AFTVs - when you first released it ..
I've not had any reason to upgrade to the latest versions.... I'm just using the heck outta the AFTV as it is built, with all the nice rooted options. I really don't need anything else yet, so ...
with that said " can I just install this unlock-lock feature? "
Truly amazing. Can't wait for full fledged android on this.
Nice to see this, but it doesn't help much when you have a Fire TV with a non-rootable firmware.
jmandawg said:
Rbox do you know if the bootloader can boot from usb?
Click to expand...
Click to collapse
The bootloader will only boot from the boot partition or the recovery partition on the mmc. But I'm working on a boot menu that will allow you to easily boot additional kernels which can then load your os from wherever you want.
toe-rag said:
I installed your Recovery (CWM) - on all 4 of my AFTVs - when you first released it ..
I've not had any reason to upgrade to the latest versions.... I'm just using the heck outta the AFTV as it is built, with all the nice rooted options. I really don't need anything else yet, so ...
with that said " can I just install this unlock-lock feature? "
Click to expand...
Click to collapse
Yes. This is independent of anything. The only dependence is the latest version of CWM requires it.
I installed ccm when you first released it then upgraded to the latest firmware the other night. Thanks a lot btw! But, can I assume (as a novice) this is not something I need to do right now. What I mean is is this just for people that want to experiment with new kernels or is there some advantage I'm missing? Thanks again and sorry if my question is a little too basic for this thread. I'm just genuinely curious.
KLit75 said:
I installed ccm when you first released it then upgraded to the latest firmware the other night. Thanks a lot btw! But, can I assume (as a novice) this is not something I need to do right now. What I mean is is this just for people that want to experiment with new kernels or is there some advantage I'm missing? Thanks again and sorry if my question is a little too basic for this thread. I'm just genuinely curious.
Click to expand...
Click to collapse
If you don't care about updating your CWM version, or using any of the other cool things I'll release in the future that needs it, then no. You don't need to do this.
Thanks for the response. I did, in fact just update cwm and am running your latest fw update. I guess "need" isn't the right word. But if I unlock it tonight the cool stuff is still forthcoming.
Sorry just 2 questions:
1. Unlocking and keeping it unlocked indefinetly is ok?
And here's one that s on a slightly different subject...
2. I noticed updating with your fw saves my settings. Is there a safe way to factory restore using cwm without the risk of losing root?
That's actually the one I'm most interested in now. My aftv has been having issues that are hard to troubleshoot. An option to factory restore would be great. I mostly use it for xbmc so the only thing I care about losing is root. Thanks.
KLit75 said:
Thanks for the response. I did, in fact just update cwm and am running your latest fw update. I guess "need" isn't the right word. But if I unlock it tonight the cool stuff is still forthcoming.
Sorry just 2 questions:
1. Unlocking and keeping it unlocked indefinetly is ok?
And here's one that s on a slightly different subject...
2. I noticed updating with your fw saves my settings. Is there a safe way to factory restore using cwm without the risk of losing root?
That's actually the one I'm most interested in now. My aftv has been having issues that are hard to troubleshoot. An option to factory restore would be great. I mostly use it for xbmc so the only thing I care about losing is root. Thanks.
Click to expand...
Click to collapse
Of course keeping it locked is fine... i wouldn't have released the tool if it wasn't.
As I've stated in MANY OTHER THREADS... factory reset in CWM is perfectly fine and has nothing to do with root.
rbox said:
If you don't care about updating your CWM version, or using any of the other cool things I'll release in the future that needs it, then no. You don't need to do this.
Click to expand...
Click to collapse
That's great. Thanks again
Thanks for this! Was very happy that the AFTV i ordered from eBay was rootable.
at the risk of being "that guy", can someone explain to a relative dummy like me the future potential with an unlocked bootloader? are we talking maybe an Android TV rom down the road? .. Apologies in advance
Hi, I unlocked the bootloader and it was successfully. Thank you rbox
barrist said:
Thanks for this! Was very happy that the AFTV i ordered from eBay was rootable.
at the risk of being "that guy", can someone explain to a relative dummy like me the future potential with an unlocked bootloader? are we talking maybe an Android TV rom down the road? .. Apologies in advance
Click to expand...
Click to collapse
Nothing that people couldn't already do with my old CWM. Custom ROMs and whatnot has been possible for a while. This just makes things a little easier because kernels don't need to be patched.
Yea! Install failed yesterday. I've had SU problems I think. Couldn't get the # prompt. Reinstalled latest ROM and SL'd SU from the store. The Unlock finally took. Thanks.
nice, thanks rbox, you rock.

[Q] URGENT Device boot loop I need urgent help please

I am on my. Way to return the phone to best buy. I was rooted and with an unlocked bootloader and had TWRP. I used the Nexus Toolkit and relocked the phone before flashing stock and now it won't boot. It just shows the team win logo flashing over and over. Please please help as they close in 30 minutes. Also it isn't detected in adb or fast boot.
EDIT: fixed it!
I am at this same point. How did you fix it?
chris23445 said:
I am on my. Way to return the phone to best buy. I was rooted and with an unlocked bootloader and had TWRP. I used the Nexus Toolkit and relocked the phone before flashing stock and now it won't boot. It just shows the team win logo flashing over and over. Please please help as they close in 30 minutes. Also it isn't detected in adb or fast boot.
EDIT: fixed it!
Click to expand...
Click to collapse
TheAnarchist1 said:
I am at this same point. How did you fix it?
Click to expand...
Click to collapse
Going to assume he managed to Re-flash factory images.
Moral of this story is don't use toolkits and learn how to recover from bootloops and read about potential problems that could arise.
ADB is your friend!
TheAnarchist1 said:
I am at this same point. How did you fix it?
Click to expand...
Click to collapse
Hold the power and volume down button until it boots into recovery. Then plug the phone into your computer. Download the stock 5.0.1 zip (luckily I already had it downloaded). Use the toolkit and unlock the bootloader. It will say its successful but the phone will boot loop again. Boot into recovery and should say the bootloader is unlocked. Then flash the stock zip file and it should work! I had to figure it all out as I went because I couldn't figure it out online lol.
radicalisto said:
Moral of this story is don't use toolkits and learn how to recover from bootloops and read about potential problems that could arise.
Click to expand...
Click to collapse
To be fair, I was in a huge rush and relocked the bootloader before flashing stock. Totally a user error and not a toolkit error.
Boot loops
radicalisto said:
Going to assume he managed to Re-flash factory images.
Moral of this story is don't use toolkits and learn how to recover from bootloops and read about potential problems that could arise.
Click to expand...
Click to collapse
Or, the moral is follow the toolkit developer's directions.......
aiiee said:
Or, the moral is follow the toolkit developer's directions.......
Click to expand...
Click to collapse
Yep. That/don't rush when resetting the phone and do it in the wrong order.
aiiee said:
Or, the moral is follow the toolkit developer's directions.......
Click to expand...
Click to collapse
No, it isn't because...
chris23445 said:
I had to figure it all out as I went because I couldn't figure it out online lol.
Click to expand...
Click to collapse
but if a toolkit had never been used in the first place, there would be nothing to figure out as it would all have been learned in the rooting process.
rootSU said:
No, it isn't because...
but if a toolkit had never been used in the first place, there would be nothing to figure out as it would all have been learned in the rooting process.
Click to expand...
Click to collapse
No lol I would have completely been screwed without the toolkit. All that happened was I did the steps wrong and I have no idea how to unlock the bootloader and relock it and root with adb and the toolkit was easier for me. I could have googled the adb thing but it would have been much more of a hassle.
chris23445 said:
No lol I would have completely been screwed without the toolkit. All that happened was I did the steps wrong and I have no idea how to unlock the bootloader and relock it and root with adb and the toolkit was easier for me. I could have googled the adb thing but it would have been much more of a hassle.
Click to expand...
Click to collapse
Thus proving my point.
radicalisto said:
Going to assume he managed to Re-flash factory images.
Moral of this story is don't use toolkits and learn how to recover from bootloops and read about potential problems that could arise.
Click to expand...
Click to collapse
rootSU said:
Thus proving my point.
Click to expand...
Click to collapse
Not in the slightest . Your analysis is flawed. You assume this problem was caused by not understanding the underlying structure but it wasn't. It was caused by failing to follow directions. Which would have caused him problems had he used ADB or not.
aiiee said:
Not in the slightest . Your logic is skewed. Good luck with that.
Click to expand...
Click to collapse
How is it skewed? If, when he first got his phone, he unlocked and rooted in the normal way and not used a toolkit. He would have known how to use fastboot, including how to flash stock and lock the boot loader. He would not have used a toolkit today and wouldn't have used the wrong order and this thread wouldn't exist.
If you're an advocate for the cheat way and the way that makes it harder for us to help people, so be it. But 95%.of us prefer users to learn things properly and not become a burden to the forum. But you can help them all. Good luck with that.
chris23445 said:
No lol I would have completely been screwed without the toolkit. All that happened was I did the steps wrong and I have no idea how to unlock the bootloader and relock it and root with adb and the toolkit was easier for me. I could have googled the adb thing but it would have been much more of a hassle.
Click to expand...
Click to collapse
how to properly root.
1. run the command "fastboot oem unlock" in fastboot. this unlocks your bootloader.
2. flash a custom recovery via fastboot.
3. flash the latest supersu in your new recovery.
4. reboot with root.
5. woohoo!
this takes about 3-5 minutes.
aiiee said:
Which would have caused him problems had he used ADB or not.
Click to expand...
Click to collapse
Adb is absolutely nothing to do with any of this. Another misconception of toolkit users. Which again, proves my point.
aiiee said:
Not in the slightest . Your analysis is flawed. You assume this problem was caused by not understanding the underlying structure but it wasn't. It was caused by failing to follow directions. Which would have caused him problems had he used ADB or not.
Click to expand...
Click to collapse
you dont use adb to root. nor will adb work while you are in the bootloader. fastboot is what you use
simms22 said:
you dont use adb to root. nor will adb work while you are in the bootloader. fastboot is what you use
Click to expand...
Click to collapse
You can use adb. Fastboot is used for the oem i lock and recovery flash. If you want to put the supersu file on the phone without downloading it on the phone you can just adb push and flash in recovery. Done.
Thanks
chris23445 said:
Hold the power and volume down button until it boots into recovery. Then plug the phone into your computer. Download the stock 5.0.1 zip (luckily I already had it downloaded). Use the toolkit and unlock the bootloader. It will say its successful but the phone will boot loop again. Boot into recovery and should say the bootloader is unlocked. Then flash the stock zip file and it should work! I had to figure it all out as I went because I couldn't figure it out online lol.
To be fair, I was in a huge rush and relocked the bootloader before flashing stock. Totally a user error and not a toolkit error.
Click to expand...
Click to collapse
Thanks for the clear explanation.:good:
@rootSU
For those curious. I figured I would check back in with this thread. I did not use a toolkit to begin with. I have the sdk properly set up and know my fastboot and adb commands and the difference between both. What I did:
1. Fastboot oem unlock
2. Fastboot flash recovery recovery.img (it was twrp)
3. Booted into recovery and it would not let me access the recovery, just kept flashing the TWRP splash over and over and over.
The issue I think for me, was that I did not wait until the Nexus had wiped itself and booted back into Android to rebuild the file system. Hence TWRP farting out. I simply started from scratch again, flashed all the proper stuff that was needed and followed steps, and I was alright after that.
I have since returned the device though and exchanged it with a new Nexus 6, because my back cover had started to pop up in the top right corner above the power and volume buttons....but THAT is another story for another thread : p
Cheers all!
PS: It has been a while since I have owned a Nexus device, hence my own failure to follow the rules. Things have changed a bit with this Nexus it seems, and it was my fault. I am all good now though (or I will be after I set up this new Nexus 6)
PSS: No toolkits were used, or will ever be used in the creation and resolution of this debacle. My life is hard enough without blindly wandering through the forest of Android customization with my hand held by a complete stranger.
: p
TheAnarchist1 said:
@rootSU
For those curious. I figured I would check back in with this thread. I did not use a toolkit to begin with. I have the sdk properly set up and know my fastboot and adb commands and the difference between both. What I did:
1. Fastboot oem unlock
2. Fastboot flash recovery recovery.img (it was twrp)
3. Booted into recovery and it would not let me access the recovery, just kept flashing the TWRP splash over and over and over.
The issue I think for me, was that I did not wait until the Nexus had wiped itself and booted back into Android to rebuild the file system. Hence TWRP farting out. I simply started from scratch again, flashed all the proper stuff that was needed and followed steps, and I was alright after that.
I have since returned the device though and exchanged it with a new Nexus 6, because my back cover had started to pop up in the top right corner above the power and volume buttons....but THAT is another story for another thread : p
Cheers all!
PS: It has been a while since I have owned a Nexus device, hence my own failure to follow the rules. Things have changed a bit with this Nexus it seems, and it was my fault. I am all good now though (or I will be after I set up this new Nexus 6)
PSS: No toolkits were used, or will ever be used in the creation and resolution of this debacle. My life is hard enough without blindly wandering through the forest of Android customization with my hand held by a complete stranger.
: p
Click to expand...
Click to collapse
after fastboot oem unlock, you have to reboot once before flashing the recovery. rarely it doesnt stick, so you just flash it again if nothing appears

[Q] Booting to Non-Stock Recovery Without Flashing It

Hey All,
I only recently picked up an XT-1060 (2013 Moto X, Dev Ed) that I plan to set up on my Verizon account. I have some experience with both the Nexus 7 (2012) and HTC's Android variants, and, for those platforms, there are technical advantages to booting to a non-stock recovery image directly from fastboot *without flashing that recovery image to the device*. I did a search of all the Moto X forums for such an alternative, and a cursory look didn't give me anything that jumped off the page regarding whether or not this was even possible.
Which brings me to my question: Assuming that I've already taken care of unlocking the bootloader, can I boot to a non-stock recovery on my new unlocked Moto X without flashing that recovery?
Many thanks!
cheers,
john
What do you mean by flashing?
You can fastboot twrp.img,which is a custom recovery.
Unfortunately, booting a custom recovery isn't possible on the Moto X. Why? I have no idea.
Just think of it as an extra later of security against an inadvertent OTA installation.
Thanks to you both for your kind replies.
nhizzat said:
Unfortunately, booting a custom recovery isn't possible on the Moto X. Why? I have no idea.
Just think of it as an extra later of security against an inadvertent OTA installation.
Click to expand...
Click to collapse
This is a bit of a disappointment. It means that I've got to strip out and save the stock recovery somewhere, then re-flash it to enable OTAs. I tend to stay on the "current-stock-plus-rooted" track. The only reason I need a custom recovery is (1) To root the device, and (2) To do nandroid backups from time to time (and possibly restores).
On devices that allow it, this means that I only need to boot the custom one occasionally, with the side benefit of being able to accept OTAs without problems. At least that's been the case for me so far.
Nicolae-Daniel said:
What do you mean by flashing?
You can fastboot twrp.img,which is a custom recovery.
Click to expand...
Click to collapse
This line doesn't make any sense to me. My typical scenarios are: If I'm trying to boot twrm, say, I'd issue: "fastboot boot twrp.img"; and, if I want to flash it, I'd use "fastboot flash recovery twrp.img". Day to day, the only thing I do with recovery is wipe the system cache, and I can do that with the stock recovery. *Sigh*
Regardless, thanks again you two...
cheers,
john
That's the approach I've always taken with my Nexus 7. All the functionality of flashing a custom recovery with one less variable to worry about.
jrredho said:
Thanks to you both for your kind replies.
This is a bit of a disappointment. It means that I've got to strip out and save the stock recovery somewhere, then re-flash it to enable OTAs. I tend to stay on the "current-stock-plus-rooted" track. The only reason I need a custom recovery is (1) To root the device, and (2) To do nandroid backups from time to time (and possibly restores).
On devices that allow it, this means that I only need to boot the custom one occasionally, with the side benefit of being able to accept OTAs without problems. At least that's been the case for me so far.
This line doesn't make any sense to me. My typical scenarios are: If I'm trying to boot twrm, say, I'd issue: "fastboot boot twrp.img"; and, if I want to flash it, I'd use "fastboot flash recovery twrp.img". Day to day, the only thing I do with recovery is wipe the system cache, and I can do that with the stock recovery. *Sigh*
Regardless, thanks again you two...
cheers,
john
Click to expand...
Click to collapse
I'm guessing you will have to play with stock and custom recoveries for that.
jrredho said:
It means that I've got to strip out and save the stock recovery somewhere, then re-flash it to enable OTAs.
Click to expand...
Click to collapse
You always can take recovery.img from your official firmware zip archive and flash it anytime.
UPD: And i hope you know, that OTA will fail if you modify or remove pre-installed apps using root.
k3nny2k said:
You always can take recovery.img from your official firmware zip archive and flash it anytime.
Click to expand...
Click to collapse
Yes, and this is exactly what I'm trying to avoid!
k3nny2k said:
UPD: And i hope you know, that OTA will fail if you modify or remove pre-installed apps using root.
Click to expand...
Click to collapse
I do know that, yes. My plan is to leave the device largely stock. I just need nandroid backups, a handful of root-requiring apps, and tethering. These are the only reasons that I root. I also do not need moment-to-moment access to a custom recovery.
Anyway, thanks for keeping me on my toes!
cheers,
john

unrootable (prototype N6)

hey everyone just picked up a prototype N6 from a buddy and having serious issues rooting this verion. i have rooted my other N6 with no issues but this build (shamu-userdebug l lrw80j 1454210 dev-keys) just wont seem to work if anyone can point me in the right direction that would be great ty. this version included a power button on the back of the phone which was nice and why it caught my eye.
What have you tried and where does it fail?
Root is usually unlock bootloader, flash recovery, flash supersu from recovery.
The problem you may have if the hardware is different is that the kernel would then be different, meaning there wont be a version of TWRP with a bootable kernel for your device. So just like you cannot run TWRP for a HTC on the Nexus 6, that could be the same case.
oh ok i see what you mean. everytime it gets to the try to temp load twrp it never seems to boot up im using the toolkit .and now it seems that i can't even boot into the system anymore just into fast boot but i can still use the flash boot flash options in root tool kit and i think you are so right about the kernel but just dont know which one to use i tried restoring /baseband /boot/system with a orignal factory 6.0 but individually but not working . is there a different method you think i can try? ty for your help.
sunnybwoy1 said:
oh ok i see what you mean. everytime it gets to the try to temp load twrp it never seems to boot up im using the toolkit .and now it seems that i can't even boot into the system anymore just fast boot. is there a different method you think i can try? ty for your help
Click to expand...
Click to collapse
If you're going to root, recovery is important.
There are apps that can root once booted into android, but you're playing with fire, especially if there hardware is different - as that means you will not have a factory image to flash either. These things are best kept untouched.
Great and I just messed up this systems IMG. cause I'm just stuck at the fastboot now I hope there is away around this. I had a feeling I shouldn't have gotten this version but wanted to be different now it just cost me smfh. Here are the pics of the phone and info
Here are some pics of the phone and build number
sunnybwoy1 said:
Here are some pics of the phone and build number
Click to expand...
Click to collapse
I cant think of a way around it. You could try flashing a stock system.img via fastboot but I cant say I'm hopeful and likely will make things worse. Without custom recovery, it is unlikely that you can repair it.
You can of course try and factory reset it. Who knows, may make it boot?
Yea flashing the system. IMG in fastboot made it worst well I used the new android m system so maybe that's why. Not looking good I hope I can get some answers soon or if maybe someone can mod a system. IMG I can use with this hardware .
sunnybwoy1 said:
Yea flashing the system. IMG in fastboot made it worst well I used the new android m system so maybe that's why. Not looking good I hope I can get some answers soon or if maybe someone can mod a system. IMG I can use with this hardware .
Click to expand...
Click to collapse
I don't think you'll get help here.
to me, it doesnt look like a n6, it looks like a moto x pro..
simms22 said:
to me, it doesnt look like a n6, it looks like a moto x pro..
Click to expand...
Click to collapse
It does, but it definitely does have an engineering bootloader and says shamu XT1103, so it's another one of "those"
danarama said:
It does, but it definitely does have an engineering bootloader and says shamu XT1103, so it's another one of "those"
Click to expand...
Click to collapse
yup. i bet it was the moto x pro, but in development still. they probably used all the shamu software on it at first. im curious whether it would take the moto x pro software.
I'm going to try to flash a stock N6 ROM to see if it will load.
Is this prototype the one with fingerprints sensor on the back?
It has a power button on the back.
sunnybwoy1 said:
Great and I just messed up this systems IMG. cause I'm just stuck at the fastboot now I hope there is away around this. I had a feeling I shouldn't have gotten this version but wanted to be different now it just cost me smfh. Here are the pics of the phone and info
Click to expand...
Click to collapse
PM Me if you decide to "part" with it.

Categories

Resources