Related
Hi! I am unlocked my nexus one and now tried to root it.
I tried with Win XP and Win 7 with the same result.
I can see the device. If i go to the command promt and enter
"adb devices" it shows me the serial - So, usb is not the problem.
I also successfully unlocked it the same way.
Dev. Mode USB is also activated.
As soon I try to root it i.e. with superboot, Android SDK etc. I get the message
"waiting for device" (stays there for ever)
also when I want to lock the device again - same result.
Something must have happened preventing me to access the phone.
Also did a hard reset - without success.
Bottemline I am STUCK. The phone works, but no root .
Versions: ERE27 with 2.1update1
Someone an idea?
Thanks
Try a different USB Port. You can't relock the device.
MatMew said:
Try a different USB Port. You can't relock the device.
Click to expand...
Click to collapse
Well I tried already on different PC's.
FYI - It's not majorly important here, but yes you can re-lock it - The same way you unlocked it.
helipilotx said:
Well I tried already on different PC's.
FYI - It's not majorly important here, but yes you can re-lock it - The same way you unlocked it.
Click to expand...
Click to collapse
Oh really?
Can you provide link proof on how to re-lock the bootloader?
Lol - he thinks you can "re-lock" it.. hahaha..
did u debug ur usb....?
helipilotx said:
Well I tried already on different PC's.
FYI - It's not majorly important here, but yes you can re-lock it - The same way you unlocked it.
Click to expand...
Click to collapse
I think this may qualify for post of the year!
Anyways, why are you even trying to root the stock ROM? Flash a custom ROM, already rooted, with the high memory kernel. As great as the stock ROM is, rooting really doesn't do anything unless you want to mess with the stock ROM... but that is like buying a V8 conversion for a Fiat, then only running 4 of the 8 cylinders.
pjcforpres said:
I think this may qualify for post of the year!
Anyways, why are you even trying to root the stock ROM? Flash a custom ROM, already rooted, with the high memory kernel. As great as the stock ROM is, rooting really doesn't do anything unless you want to mess with the stock ROM... but that is like buying a V8 conversion for a Fiat, then only running 4 of the 8 cylinders.
Click to expand...
Click to collapse
Well, how ever - I'll might be wrong, just saw someone do it on you tube (might was fake)
Anyway, well it does not matter whether I want to root the stock rom or flash a custom rom - my point is it always shows me
"waiting for device"
helipilotx said:
Well, how ever - I'll might be wrong, just saw someone do it on you tube (might was fake)
Anyway, well it does not matter whether I want to root the stock rom or flash a custom rom - my point is it always shows me
"waiting for device"
Click to expand...
Click to collapse
You have to install the correct adb drivers
http://forum.xda-developers.com/showthread.php?t=613217
Eclair~ said:
Lol - he thinks you can "re-lock" it.. hahaha..
Click to expand...
Click to collapse
glad ur soooooooo much smarter
congrats ! A+
helipilotx said:
Well, how ever - I'll might be wrong, just saw someone do it on you tube (might was fake)
Anyway, well it does not matter whether I want to root the stock rom or flash a custom rom - my point is it always shows me
"waiting for device"
Click to expand...
Click to collapse
can you post the video link
helipilotx said:
glad ur soooooooo much smarter
congrats ! A+
Click to expand...
Click to collapse
Out of all the people that basically implied, or thought, what I said you - had to have a 'comeback' to me.. guess its because I said "hahaha," and "lol". If we really could re-lock the bootloader though... i'd be all over that..
TFJ4 said:
You have to install the correct adb drivers
Sorry, this is not the problem. These drivers I downloaded and installed already
As I said I can see the device and was able to unlock it.
- Any other ideas?
Thanks.
Click to expand...
Click to collapse
chronzz said:
can you post the video link
Click to expand...
Click to collapse
Have to look for it again. I saw it on my research to solve this problem I am having. When I find it again i will let you know for sure.
Anymore ideas anyone?
Thanks!
I had this problem yesterday (my first ever ROM flash!). I'm sure you didn't make this mistake, but my phone had to be on the boot (white) screen before it was recognized. When the phone was turned on normally, or off normally, I got the "Waiting for device" message.
FYI: I'm using Linux Fedora Core 12 on my PC.
Just had this problem. Jade this stupid mistake of not doing it while on the bootloader screen.
helipilotx said:
but yes you can re-lock it - The same way you unlocked it.
Click to expand...
Click to collapse
That is THE best post i've ever read... just see the confidence
Perhaps the video he saw was of a holiday phone, in which case
Code:
fastboot oem lock
does work.
No good on our retail ones (yet) though.
helipilotx said:
FYI - It's not majorly important here, but yes you can re-lock it - The same way you unlocked it.
Click to expand...
Click to collapse
Love this post!!! +1 for post of the year!!!!
Hello! I use Google translation, I do not know where I wrote) get to the point I have a very buggy phone does not know what to do ... I have nothing to firmware and kernel did not help ((who knows what to do tell me
benn9 said:
Hello! I use Google translation, I do not know where I wrote) get to the point I have a very buggy phone does not know what to do ... I have nothing to firmware and kernel did not help ((who knows what to do tell me
Click to expand...
Click to collapse
I believe we are getting lost in translation so to speak, let's try for a little more information.
Have you unlocked your boot loader?
Have you rooted your device?
Have put a custom kernel on your device? If so which?
Have you put custom firmware on your device? If so which?
When you say your phone is buggy, that is very vague. What exactly are the issues your experiencing? Is it rebooting, or is it not making to the boot animation and starting at all? Or is this more of a lag issue, feels sluggish and certain applications force close or cause the phone to restart. Have you had issues with the device prior to flashing, if you have flashed a custom firmware already?
With a little more information I'm sure there are a lot of people on the forums that are able to help, but without a little bit of detail as to whats going on the best anyone can say is the standard tech support response: Did you turn the device off and back on again. And I assume that is not the answer you are looking for.
1
barbrick said:
I believe we are getting lost in translation so to speak, let's try for a little more information.
Have you unlocked your boot loader?
Have you rooted your device?
Have put a custom kernel on your device? If so which?
Have you put custom firmware on your device? If so which?
When you say your phone is buggy, that is very vague. What exactly are the issues your experiencing? Is it rebooting, or is it not making to the boot animation and starting at all? Or is this more of a lag issue, feels sluggish and certain applications force close or cause the phone to restart. Have you had issues with the device prior to flashing, if you have flashed a custom firmware already?
With a little more information I'm sure there are a lot of people on the forums that are able to help, but without a little bit of detail as to whats going on the best anyone can say is the standard tech support response: Did you turn the device off and back on again. And I assume that is not the answer you are looking for.
Click to expand...
Click to collapse
Yes, I unlocked bootloader
yes I have is Nameless Rom v7.3
yes I have a hard core at 800MHz
I mean such as logs: twitching, brakes, very long time thinking ...
it happened a month ago, I thought, and did not bother about it, and now I do not like it.
HELP ME PLEASE
You tried flashing ruu? I also had this problem I solved it with ruu but for ruu to work I had to relock the boot loader! You just have to connect your phone in bootloader mode open adb and type fastboot oem lock. Then just install latest ruu!
Sent from my HTC Desire C using xda premium
benn9 said:
Yes, I unlocked bootloader
yes I have is Nameless Rom v7.3
yes I have a hard core at 800MHz
I mean such as logs: twitching, brakes, very long time thinking ...
it happened a month ago, I thought, and did not bother about it, and now I do not like it.
HELP ME PLEASE
Click to expand...
Click to collapse
Honestly, my device won't run the 806 Kernel, and has lots of trouble running the 767 Kernel, it seems some Desire C devices were made to a higher quality than others, looks like I got a Friday Phone!
Did you have it running successfully on the 806 Kernel previously?
On my device the 722 runs smoother than the 600, so I would try flashing that or the 600 stock Kernel and see if that resolves the issues.
1
noahvt said:
you tried flashing ruu? I also had this problem i solved it with ruu but for ruu to work i had to relock the boot loader! You just have to connect your phone in bootloader mode open adb and type fastboot oem lock. Then just install latest ruu!
Sent from my htc desire c using xda premium
Click to expand...
Click to collapse
thank you kind help! further not know what will
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.
Hey guys! So this is a very strange issue. When I power off my nexus, a lot of times I have to wait a good 30 seconds or so before I can power it back on or go into the bootloader. If I power it off, and try to turn it back on fast, it stays black screen almost as of it's frozen or just not responding. I noticed this issue begun when I flashed the radio from N preview 2, and didn't happen before that. My question here, is what could this be? Can the radio really cause odd things like this to happen? Or is there another cause? I am running the newest Android version MOB30I, and have multirom installed with about 4 or so secondaries.
H4X0R46 said:
Hey guys! So this is a very strange issue. When I power off my nexus, a lot of times I have to wait a good 30 seconds or so before I can power it back on or go into the bootloader. If I power it off, and try to turn it back on fast, it stays black screen almost as of it's frozen or just not responding. I noticed this issue begun when I flashed the radio from N preview 2, and didn't happen before that. My question here, is what could this be? Can the radio really cause odd things like this to happen? Or is there another cause? I am running the newest Android version MOB30I, and have multirom installed with about 4 or so secondaries.
Click to expand...
Click to collapse
You flashed Npreview radio on a marshmallow build?
Dead-neM said:
You flashed Npreview radio on a marshmallow build?
Click to expand...
Click to collapse
Yes! Yes I did. Could this be an issue?
H4X0R46 said:
Yes! Yes I did. Could this be an issue?
Click to expand...
Click to collapse
no. as im using the n preview radio on marshmallow, which is the same radio that came out with the last security update.
---------- Post added at 05:48 PM ---------- Previous post was at 05:46 PM ----------
H4X0R46 said:
Hey guys! So this is a very strange issue. When I power off my nexus, a lot of times I have to wait a good 30 seconds or so before I can power it back on or go into the bootloader. If I power it off, and try to turn it back on fast, it stays black screen almost as of it's frozen or just not responding. I noticed this issue begun when I flashed the radio from N preview 2, and didn't happen before that. My question here, is what could this be? Can the radio really cause odd things like this to happen? Or is there another cause? I am running the newest Android version MOB30I, and have multirom installed with about 4 or so secondaries.
Click to expand...
Click to collapse
im going to guess, try a different kernel. as its the kernel that will boot up the device?
H4X0R46 said:
Yes! Yes I did. Could this be an issue?
Click to expand...
Click to collapse
Yes it can. Why did you do that?
Make a backup (android or titatium backup)
Then reflash stock n6 firmware (erase data so put your backup and important files into pc)
Dead-neM said:
Yes it can. Why did you do that?
Make a backup (android or titatium backup)
Then reflash stock n6 firmware (erase data so put your backup and important files into pc)
Click to expand...
Click to collapse
the N radio, is the same exact radio that google released for the may security patch. so the N radio, is the latest official radio for the nexus 6. so no, that wont be the problem.
simms22 said:
no. as im using the n preview radio on marshmallow, which is the same radio that came out with the last security update.
---------- Post added at 05:48 PM ---------- Previous post was at 05:46 PM ----------
im going to guess, try a different kernel. as its the kernel that will boot up the device?
Click to expand...
Click to collapse
I wonder if it is. I'm using the newest Elite kernel for Marshmallow, it's always been my go to kernel. It's strange because after turning the device off, I can't turn it back on instantly, screen stays black as if it's not 100% shut down yet. I have to wait a bit before turning it back on, or entering the bootloader.
simms22 said:
im going to guess, try a different kernel. as its the kernel that will boot up the device?
Click to expand...
Click to collapse
No, it's the bootloader that boots the device.
If he's hitting the power button and unable to get to the "Google" splash screen or the bootloader, the kernel is very irrelevant.
I'd be more curious if he's trying to use the bootloader from the N-Preview 2 with MM. Even though I think it's supposed to be backwards compatible, the bootloader is the only thing that would cause that sort of issue.
*technically* I'm pretty sure that you could format /boot (where the kernel is stored) and still get to your bootloader for fastboot and such. So, the kernel is really irrelevant until after the bootloader does it's thing.
*edit*
also, there's a reason that these are known as "Developer Previews" not "End-User Previews"... If you don't know how to fix weird issues that pop up like that, you should probably avoid them.
Yoinx said:
No, it's the bootloader that boots the device.
If he's hitting the power button and unable to get to the "Google" splash screen or the bootloader, the kernel is very irrelevant.
I'd be more curious if he's trying to use the bootloader from the N-Preview 2 with MM. Even though I think it's supposed to be backwards compatible, the bootloader is the only thing that would cause that sort of issue.
*technically* I'm pretty sure that you could format /boot (where the kernel is stored) and still get to your bootloader for fastboot and such. So, the kernel is really irrelevant until after the bootloader does it's thing.
*edit*
also, there's a reason that these are known as "Developer Previews" not "End-User Previews"... If you don't know how to fix weird issues that pop up like that, you should probably avoid them.
Click to expand...
Click to collapse
Mmm yes after what said simms22 I've check the n preview and the bootloader is xxx.18 instead of last mm which is xxx.17 but a bootloader downgrade is risky right?
@H4X0R46 do you use the .sh file and update your bootloader and radio with n preview?
Dead-neM said:
Mmm yes after what said simms22 I've check the n preview and the bootloader is xxx.18 instead of last mm which is xxx.17 but a bootloader downgrade is risky right?
@H4X0R46 do you use the .sh file and update your bootloader and radio with n preview?
Click to expand...
Click to collapse
It can be. Normally, once you upgrade, you just stick with the new one as they're backwards compatible normally. But, the ones for the Previews aren't always 100%. The whole reason these previews come out is so that developers can start making their apps compatible prior to the official release. Ideally, this is supposed to be done in emulators not necessarily real devices.
If the 30 second delay in powering back on is *that* big of a deal (to him) to risk bricking the phone by downgrading the bootloader and having something go wrong... I say go for it.
Yoinx said:
It can be. Normally, once you upgrade, you just stick with the new one as they're backwards compatible normally. But, the ones for the Previews aren't always 100%. The whole reason these previews come out is so that developers can start making their apps compatible prior to the official release. Ideally, this is supposed to be done in emulators not necessarily real devices.
If the 30 second delay in powering back on is *that* big of a deal (to him) to risk bricking the phone by downgrading the bootloader and having something go wrong... I say go for it.
Click to expand...
Click to collapse
Is downgrading the bootloader really risky? I've done it before without issue and never knew this was risky! Are you supposed to just stay with the newest bootloader if you already flashed it? I always flash the bootloader for the image I'm flashing, even if I'm downgrading.
Dead-neM said:
Mmm yes after what said simms22 I've check the n preview and the bootloader is xxx.18 instead of last mm which is xxx.17 but a bootloader downgrade is risky right?
@H4X0R46 do you use the .sh file and update your bootloader and radio with n preview?
Click to expand...
Click to collapse
I flash each partition manually.
H4X0R46 said:
Is downgrading the bootloader really risky? I've done it before without issue and never knew this was risky! Are you supposed to just stay with the newest bootloader if you already flashed it? I always flash the bootloader for the image I'm flashing, even if I'm downgrading.
Click to expand...
Click to collapse
It's always risky when you're messing with essentially the lowest level software on the device. For instance, lets say that something happens while you're flashing the bootloader and it corrupts. What do you use to reflash it? You can't get to fastboot anymore...
As long as you know what you're doing, don't have corrupt images, and don't lose power or have lightning strike your computer while you're doing it, you would be fine.
The issue is that many/most people on XDA these days have no idea how to recover from problems or even what problems the things that they're doing might cause. So I tend to approach every situation under the assumption that the other poster may not have a full understanding.
No offense intended of course.
Yoinx said:
It's always risky when you're messing with essentially the lowest level software on the device. For instance, lets say that something happens while you're flashing the bootloader and it corrupts. What do you use to reflash it? You can't get to fastboot anymore...
As long as you know what you're doing, don't have corrupt images, and don't lose power or have lightning strike your computer while you're doing it, you would be fine.
The issue is that many/most people on XDA these days have no idea how to recover from problems or even what problems the things that they're doing might cause. So I tend to approach every situation under the assumption that the other poster may not have a full understanding.
No offense intended of course.
Click to expand...
Click to collapse
Alright so that's just to be safe then? My laptop sometimes freezes solid out of the blue, uncommon but does happen, and I always thought "what if I'm flashing stuff?" Scary thought. ESPECIALLY the bootloader! So the danger you're referring to is flashing a bootloader in general, not so much downgrading? Like I said, I always match the bootloader to the version I'm running. This is okay?
EDIT: I ALWAYS ALWAYS ALWAYS check the MD5 checksum for EVERYTHING before flashing. Can never be too safe
H4X0R46 said:
Alright so that's just to be safe then? My laptop sometimes freezes solid out of the blue, uncommon but does happen, and I always thought "what if I'm flashing stuff?" Scary thought. ESPECIALLY the bootloader! So the danger you're referring to is flashing a bootloader in general, not so much downgrading? Like I said, I always match the bootloader to the version I'm running. This is okay?
EDIT: I ALWAYS ALWAYS ALWAYS check the MD5 checksum for EVERYTHING before flashing. Can never be too safe
Click to expand...
Click to collapse
In general, the bootloader needs to match the highest version of android you intend to run. They're typically always backward compatible. On some phones, you can't downgrade the bootloader (at least not easily). This phone you should be fine doing so. However, there's not usually any reason to (backwards compatible afterall).
Yoinx said:
In general, the bootloader needs to match the highest version of android you intend to run. They're typically always backward compatible. On some phones, you can't downgrade the bootloader (at least not easily). This phone you should be fine doing so. However, there's not usually any reason to (backwards compatible afterall).
Click to expand...
Click to collapse
Cool! Thanks for your input on that! Much appreciated! Yea I'm always wary of the bootloader because like you said, it IS the lowest software on the device. Quick question, if that were to get corrupted, does the device just not boot resulting in permanent brick? Or does it boot just no fastboot access? Might be a noob question, but why not ask lol
H4X0R46 said:
Cool! Thanks for your input on that! Much appreciated! Yea I'm always wary of the bootloader because like you said, it IS the lowest software on the device. Quick question, if that were to get corrupted, does the device just not boot resulting in permanent brick? Or does it boot just no fastboot access? Might be a noob question, but why not ask lol
Click to expand...
Click to collapse
Depends, I've never really looked into unbricking this phone. Never had to yet.
Depending on the phone you can use tools like QHUSB and similar which let you reflash partitions just through the USB connection.
I know it's late but it could also be just the rom setup. I know a while ago there were commits that shut the device screen and buttons off before it was done shutting down (to make it appear faster) this made devices seem bricked for a short period. I don't know what ever happen to those commits, so I can't say for sure that it is them. But your issue fits perfectly.
So have I been flashing the bootloader wrong all along? I flashed in twrp a couple times but I try to flash them individually and wipe after flashing.
Sent from my Nexus 6 using XDA-Developers mobile app
Anybody able to find out why? I'm surprised to see I'm not the only one having this issue, it's annoying really.
THIS GUIDE IS NOW OBSOLETE
Links will be added once the new guide using the firehose comes out - No more bricking!
Thanks to everyone who contributed to the firehose!
I just cut and pasted the whole guide into a txt file, which is linked below in case there's ever any purpose of looking at it again.
https://drive.google.com/file/d/1wTRMvweLlsF-3WU9CYlz7X3ZIRE3vtCs/view?usp=sharing
Isn’t Mr. Zhu the author of twrp?
You might want to wait until I get to my computer again as I realized there are a few minor edits that could be helpful. It's not letting me edit it successfully on my phone
Malossi94 said:
Isn’t Mr. Zhu the author of twrp?
Click to expand...
Click to collapse
Yeah but apparently he stopped development, but le Minh sent the Korean fix after that so I'm not entirely sure lmao
antintin said:
Yeah but apparently he stopped development, but le Minh sent the Korean fix after that so I'm not entirely sure lmao
Click to expand...
Click to collapse
Mr. Zhu repaired kor twrp, and my kor skt G8 participated in the repair development:silly:
Malossi94 said:
Mr. Zhu repaired kor twrp, and my kor skt G8 participated in the repair development:silly:
Click to expand...
Click to collapse
Nice! I'll edit as soon as I get on my computer
Hi have followed the guide and got stuck at step 7. I get only the LG V50Thinq powered by android screen and nothing more. It just stays like for the past 30 minutes. I have rebooted several times but the same. i cannot access (or do not know) download mode.
Any help!
So, if your on a korean version that wil be a q version of android vulnerable. Therefore at step 6, you will need a pie kdz to flash those 4 xbl files. Do not make my mistake, you will get bricked ))
Marmalux said:
So, if your on a korean version that wil be a q version of android vulnerable. Therefore at step 6, you will need a pie kdz to flash those 4 xbl files. Do not make my mistake, you will get bricked ))
Click to expand...
Click to collapse
Sorry I'm afraid I don't understand. That's step 4, and you don't need to flash the whole kdz. Only the partitions the guide says to.
antintin said:
Sorry I'm afraid I don't understand. That's step 4, and you don't need to flash the whole kdz. Only the partitions the guide says to.
Click to expand...
Click to collapse
I think he's referring to how its a bit confusing how it says you should use android pie but also implies that you should use latest pre-march firmware, which for korean variant is actually android Q not pie so its little confusing which you should use, i could be wrong though, thanks alot for this guide though!
9RR said:
I think he's referring to how its a bit confusing how it says you should use android pie but also implies that you should use latest pre-march firmware, which for korean variant is actually android Q not pie so its little confusing which you should use, i could be wrong though, thanks alot for this guide though!
Click to expand...
Click to collapse
If someone can't deal with the level of instruction I provided here, I would very much advise against attempting it as it is inherently very risky. Probably not what anyone wants to here, but it is what it is
This is great news. Has anyone Tested using a LOS GSI or AOSP GSI? I am on verizon and have found with another phone that all GSIs on android version 9 and 10 have "No Sim Card" errors and you can not make calls or send texts (strangely you can receive both). This error wasn't seen with other network versions of the phone (palm phone). I am a little hesitant to go through this process to find out if data doesn't work on LOS 17 or AOSP 10. If anyone on verizon tries this out, please report back on how well the GSIs work, or if you find a specific ROM that works on Verizon.
CaptainElwood said:
This is great news. Has anyone Tested using a LOS GSI or AOSP GSI? I am on verizon and have found with another phone that all GSIs on android version 9 and 10 have "No Sim Card" errors and you can not make calls or send texts (strangely you can receive both). This error wasn't seen with other network versions of the phone (palm phone). I am a little hesitant to go through this process to find out if data doesn't work on LOS 17 or AOSP 10. If anyone on verizon tries this out, please report back on how well the GSIs work, or if you find a specific ROM that works on Verizon.
Click to expand...
Click to collapse
I've used a lot of gsis like bless and caos (use those instead of aosp definitely). I haven't had any data issues
antintin said:
I've used a lot of gsis like bless and caos (use those instead of aosp definitely). I haven't had any data issues
Click to expand...
Click to collapse
But I have a sprint model. I'm pretty sure Verizon people have tried it with no issues already though
antintin said:
If someone can't deal with the level of instruction I provided here, I would very much advise against attempting it as it is inherently very risky. Probably not what anyone wants to here, but it is what it is
Click to expand...
Click to collapse
Hi, thank you very much for this tutorial.
It was my mistake and got a permanent brick. It is true that the vulnerable firmware for kor is android Q and i have achieved root after downgrading to a older Q version. My problem was at step 4 because i used the q kdz and i did not download a separate pie kdz for that step.
Now i hope no one else will make my mistake since i really do not see how to get DL mode active or to switch slots without the USB. Only thing i got is the image that precedes the DL mode and the IMEI display. And since the USB is basically dead i think firehose (even if i had it) would not recover my phone.
I have flashed and unlock many phones and this is my first unrecoverable brick. My first LG though and probably the last.
Marmalux said:
Hi, thank you very much for this tutorial.
It was my mistake and got a permanent brick. It is true that the vulnerable firmware for kor is android Q and i have achieved root after downgrading to a older Q version. My problem was at step 4 because i used the q kdz and i did not download a separate pie kdz for that step.
Now i hope no one else will make my mistake since i really do not see how to get DL mode active or to switch slots without the USB. Only thing i got is the image that precedes the DL mode and the IMEI display. And since the USB is basically dead i think firehose (even if i had it) would not recover my phone.
I have flashed and unlock many phones and this is my first unrecoverable brick. My first LG though and probably the last.
Click to expand...
Click to collapse
I'm very sorry to hear that, but the firehose could almost definitely help you unbrick. I tried to clarify more that it has to be a pie kdz now, because before I just wrote "load your pie kdz" and you probably missed that. There should still be a warranty though, so you could try to use that if you'd like. It might say that yours expired on the website, but you can just click past it.
antintin said:
Spoiler
I'm very sorry to hear that, but the firehose could almost definitely help you unbrick. I tried to clarify more that it has to be a pie kdz now, because before I just wrote "load your pie kdz" and you probably missed that. There should still be a warranty though, so you could try to use that if you'd like. It might say that yours expired on the website, but you can just click past it.
Click to expand...
Click to collapse
Thank you antintin for your reply. You bring me some hope. The warranty will not apply because it is stated clearly that any attempt to BL unlock will void it (I got it from a shop in Spain via Ebay).
But the firehose on the other hand.... When do you think it will be available? And how will i ba able to get it?
Thank you very much!
Marmalux said:
Thank you antintin for your reply. You bring me some hope. The warranty will not apply because it is stated clearly that any attempt to BL unlock will void it (I got it from a shop in Spain via Ebay).
But the firehose on the other hand.... When do you think it will be available? And how will i ba able to get it?
Thank you very much!
Click to expand...
Click to collapse
Other people who bricked while different bl unlock methods were tested sent it in for warranty with no issues. The firehose will be available in November at the earliest probably. Proof of purchase from eBay should be enough, but I don't if there's any lg repair centers in Spain that support phones.
antintin said:
Other people who bricked while different bl unlock methods were tested sent it in for warranty with no issues. The firehose will be available in November at the earliest probably. Proof of purchase from eBay should be enough, but I don't if there's any lg repair centers in Spain that support phones.
Click to expand...
Click to collapse
In Spain there are several. But i`m in Ireland, and here is none ))
Successfully rooted korean variant, thanks for the guide! I was wondering if its okay now to update to newest firmware via LGUP upgrade mode? (I really want the system wide accent color customization in newest firmware, among other things) I assume it should be but i really don't wanna have to redo all this so id rather just ask, thanks in advance!