Related
I made a wipe data/factory reset while on CWM Touch (I didn't know about the issues yet) and, of course, it didn't work. So now, everytime I try and flash an Odin ROM (because it doesn't work with the recovery), it gets stuck at data.img/datafs so there's no way I can boot my phone although it does have recovery, download and it gets to the Samsung bootscreen (I flashed a stock ROM).
Has anyone got any ideas on how to fix this? Thanks
Tried clearing cache and data while on recovery? Which rom/kernel are you on?
Sent from my GT-N7000 using XDA
praetorius said:
Tried clearing cache and data while on recovery? Which rom/kernel are you on?
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
I was on AOSP ICS v04 with the infamous AbyssNote 1.2 kernel (but I don't have the same factoryfs problem as the others) with Touch CWM (that's where the problem comes from I believe) and the only problem is that neither Odin nor CWM can access the /data partition. So a wipe doesn't work.
I fear the nearest Samsung service is the way to go for you, mate. Your data partition is corrupted beyond repair.
Believe me, the guys affected with Angelom 1.2 had tried everything, including jigging, jtagging and nothing helped unbrick their phones. It looks like replacing the motherboard is the only solution.
Sorry to have to tell you this.
chasmodo said:
I fear the nearest Samsung service is the way to go for you, mate. Your data partition is corrupted beyond repair.
Believe me, the guys affected with Angelom 1.2 had tried everything, including jigging, jtagging and nothing helped unbrick their phones. It looks like replacing the motherboard is the only solution.
Sorry to have to tell you this.
Click to expand...
Click to collapse
Are you sure? Even though it's never stuck at factoryfs and it only bootloops? Because the problem is I have no service center I can go to so sending it via La Poste (in France) isn't exactly what I'd call safe... Or is there a way to send iut directly to Samsung and get a new one?
Up.............
Since it looks like a partition problem - have you tried using stock .pit file and repartition with ODIN ?
Akiainavas said:
Since it looks like a partition problem - have you tried using stock .pit file and repartition with ODIN ?
Click to expand...
Click to collapse
Yes I did. Well I think imma have to send it to a samsung repair center. How long does it take to get a new Note?
Hi, I had a similar problem and here's what I did. I flashed a stock rom (doesn't have datafs so it worked fine) then it rebooted into recovery which complained about /data partition. So I did wipe data and rebooted.
Hope this helps.
nico53laval said:
Yes I did. Well I think imma have to send it to a samsung repair center. How long does it take to get a new Note?
Click to expand...
Click to collapse
According to warranty agreement:
"Repairs are done as fast as possible, but within 14 days time."
no id agree with what the guys have told you, looks like a service center job, did you just flash this recently or were you one of the users who flashed it weeks back, and youve only just attempted a wipe now??
Just out of curiosity, if people have this kernel installed, can they flash to a diff kernel b4 trying a wipe, or will that not work.
graemeg said:
Just out of curiosity, if people have this kernel installed, can they flash to a diff kernel b4 trying a wipe, or will that not work.
Click to expand...
Click to collapse
You're fine if you don't do any wipes prior to flashing another kernel. However, wipe anything and it's curtains.
chasmodo said:
You're fine if you don't do any wipes prior to flashing another kernel. However, wipe anything and it's curtains.
Click to expand...
Click to collapse
Exactly :/ I was fine for weeks then I wiped before installign another ROM and boom...
dirk271 said:
Hi, I had a similar problem and here's what I did. I flashed a stock rom (doesn't have datafs so it worked fine) then it rebooted into recovery which complained about /data partition. So I did wipe data and rebooted.
Hope this helps.
Click to expand...
Click to collapse
Too late ^^ I sent it to a repair center.. But I don't think it would have worked. I already did a wipe on a tock rom with stock recovery and it worked but the phone still couldn't boot.
Akiainavas said:
According to warranty agreement:
"Repairs are done as fast as possible, but within 14 days time."
Click to expand...
Click to collapse
The problem is that in France the repair centers have an agreement with Samsung but they're not directly related to Samsung so do you think it'll only be 14 days (even though I might neeed a new mobo or a new phone)?
Not sure how youre postal system works there but make sure you get recorded delivery or france similar so you have proof of posting etc.
Also considering the issue ive read most times lads have had a quick turn around, but who knows, depends how fast samsung receive it, i would suggest UP TO 2 weeks, more likely a week, but then it me be 2 week, depends what they have to do to repair it.
I recently took a phone to the o2 shop to be repaired, i received it back via post 4 days later, that was really fast, and im quite lucky here that theres an abundance of walk in repair centres around the uk, it just made me wonder if there one close to you and would it be economical to take it in person, samsung repair shop where i live if ya take your phone in by hand theyll usually say come back in a couple of hours and then they fix it there and then, that would be better for you because you arent messing around with posting then, i know a lot of countries guys dont have that option but i would have thought france and germany would be similar to the uk as they are both quite large mobile manufacturing countries so my fingers are crossed for you that you can find a quick solution.
No idea mate, but you shouldn't wait more than 2 weeks. The repair will take one hour probably, the rest is testing, posting, filling papers etc.
You'll probably have it back after 1 week or so. So let's hope you'll received it fixed as soon as possible.
nico53laval said:
Exactly :/ I was fine for weeks then I wiped before installign another ROM and boom...
Click to expand...
Click to collapse
Oh, I see. Should've read angelom 1.2 thread first.... sorry
Good luck with service.
dirk271 said:
Hi, I had a similar problem and here's what I did. I flashed a stock rom (doesn't have datafs so it worked fine) then it rebooted into recovery which complained about /data partition. So I did wipe data and rebooted.
Hope this helps.
Click to expand...
Click to collapse
what stock rom? which version you used?
stubled upon this article instructing users on how to get rooted and install ClockWorkMod through ROM Manager? what? are those guys kidding us.. they just want users to brick their mobiles..
so, androidauthority.com - follow this and you got a bricked mobile.
don't kill the business and do not brick users mobile phones.
your article leads users to brick their mobile, which is not kindly at all. or maybe that website is just anti-LG, could be?
Your article is BS and is lousy journalism and untrustworthy.
extract from their article
You can also download ROM Manager and flash the latest ClockworkMod Recovery, as it should only be a matter of time before we start to see custom ROM’s.
Click to expand...
Click to collapse
- this WILL brick users mobile, if possible.
At least they also mention to update supersu ... something I didn't know
Btw: How does CWM work? I have it on my old 2X, but I never quite understood how it works, where it installs itself and why it is model dependent...
voon said:
At least they also mention to update supersu ... something I didn't know
Btw: How does CWM work? I have it on my old 2X, but I never quite understood how it works, where it installs itself and why it is model dependent...
Click to expand...
Click to collapse
CWM resides on the 'recovery' partition of the handset. A recovery is used to recover your phone in the event of a failure, or to flash an update. CWM overwrites your 'stock' recovery, and allows you to issue more commands to the phone. The largest benefit to CWM, however, is that it can flash unsigned packages, which is how you install a custom, non-OEM verified ROM
Hope this helps!
This is so true. It happened with the nitro HD as well. They instructed is to push the recovery image to the secondary boot loader causing us to get permabricked; I had to send my phone to lg repair.
Sent from my LG-P930 using xda premium
i would have no problems if they instructed on the rooting part alone, but they moved on to how easy it was to get cwm working, thats a bummer.
but ok, i admit, that koush probably would not allow ANY user to install a cwm on a model they did not support anyways. but leading some users to believe it would work.
Dexter_nlb said:
stubled upon this article instructing users on how to get rooted and install ClockWorkMod through ROM Manager? what? are those guys kidding us.. they just want users to brick their mobiles..
so, androidauthority.com - follow this and you got a bricked mobile.
don't kill the business and do not brick users mobile phones.
your article leads users to brick their mobile, which is not kindly at all. or maybe that website is just anti-LG, could be?
Your article is BS and is lousy journalism and untrustworthy.
extract from their article
- this WILL brick users mobile, if possible.
Click to expand...
Click to collapse
Hey Dexter. I write for Android Authority. I did not write he article, but I will look into what you have mentioned and make sure the article gets updated. We can't publish content that could potentially harm a users device due to incorrect instructions. I wish I would have found this earlier. Maybe next time you could reply in the comments on said article so we could resolve the issue. Thanks again for the heads up!
Dexter_nlb said:
stubled upon this article instructing users on how to get rooted and install ClockWorkMod through ROM Manager? what? are those guys kidding us.. they just want users to brick their mobiles..
so, androidauthority.com - follow this and you got a bricked mobile.
don't kill the business and do not brick users mobile phones.
your article leads users to brick their mobile, which is not kindly at all. or maybe that website is just anti-LG, could be?
Your article is BS and is lousy journalism and untrustworthy.
extract from their article
- this WILL brick users mobile, if possible.
Click to expand...
Click to collapse
Dexter, I wrote the article, and it was an honest mistake to include the CWM part. I have addressed the issue in the article. Trust me, I intend to help people, and our website is far from "anti-LG" and I am even further away from "wanting users to brick their mobiles". It was just an incorrect statement, and I meant no harm by posting. My apologies, this was my fault not the fault of Android Authority.
*edit* - also, I do not have the device on hand as I sent it to a co-worker, but could you explain to me why the flashing of CWM would brick your phone? I'm almost positive I did it, and my phone was perfectly fine.
-Clayton Ljungberg
ljungberg3 said:
*edit* - also, I do not have the device on hand as I sent it to a co-worker, but could you explain to me why the flashing of CWM would brick your phone? I'm almost positive I did it, and my phone was perfectly fine.
-Clayton Ljungberg
Click to expand...
Click to collapse
Tegra3 devices got a SBK(secure boot key) + encrypted partitions and it has a checksum of boot/recovery partitions, so if changed/updated the device will go into a brick state,claiming you cannot boot (RED big warning).
so with additional hacks , experienced users can unbrick the device using firmware upgraders. but otherwise just sending it back to the shops is the only way out, for regular owners without xda experience.
currently o4x is a locked device for boot and recovery partition changes, so no writing of recovery partition unless its signed with the signature key, which no one would own unless developing for o4x internals.
note/fyi,
the CWM i did, is not an image and its only bootstrap based, using a trick to re-load init process, so it retain the original recovery partition.
Dexter_nlb said:
Tegra3 devices got a SBK(secure boot key) + encrypted partitions and it has a checksum of boot/recovery partitions, so if changed/updated the device will go into a brick state,claiming you cannot boot (RED big warning).
so with additional hacks , experienced users can unbrick the device using firmware upgraders. but otherwise just sending it back to the shops is the only way out, for regular owners without xda experience.
currently o4x is a locked device for boot and recovery partition changes, so no writing of recovery partition unless its signed with the signature key, which no one would own unless developing for o4x internals.
note/fyi,
the CWM i did, is not an image and its only bootstrap based, using a trick to re-load init process, so it retain the original recovery partition.
Click to expand...
Click to collapse
Well thank you for clarifying, I must have also installed the bootstrap based CWM, as I did have CWM recovery. I downloaded and assumed that I updated cwm through rom manager. Again, to clarify - I meant no harm in posting the article. I am not anti-LG, and I don't want users to brick their phones. I can say for a fact that the root guide is solid other than the CWM reference (which was one sentence within the entire article, mind you)
ljungberg3 said:
(which was one sentence within the entire article, mind you)
Click to expand...
Click to collapse
all it takes is a one-liner!
As i also mentioned previously, i found the article ok, if it was not for the mention of cwm was next step to get it rollling. but good is that you corrected it.
Dexter_nlb said:
all it takes is a one-liner!
As i also mentioned previously, i found the article ok, if it was not for the mention of cwm was next step to get it rollling. but good is that you corrected it.
Click to expand...
Click to collapse
Yes, I did correct it. We want to help our readers as much as possible. I hope that you can hold our website in higher regard than you did previously, when you posted the thread.
ljungberg3 said:
Well thank you for clarifying, I must have also installed the bootstrap based CWM, as I did have CWM recovery. I downloaded and assumed that I updated cwm through rom manager. Again, to clarify - I meant no harm in posting the article. I am not anti-LG, and I don't want users to brick their phones. I can say for a fact that the root guide is solid other than the CWM reference (which was one sentence within the entire article, mind you)
Click to expand...
Click to collapse
Just thinking...
Could it be that you got hold of one of the developer models, and that's why you were able to install CWM via rom manager??
When we first tried to get root, someone made a guide on here. Turned out it only worked for him because he had an unlocked developers phone running software version V08(someting more I don't remember)...
But as I said, just a thought!!!
m_primdahl said:
Just thinking...
Could it be that you got hold of one of the developer models, and that's why you were able to install CWM via rom manager??
When we first tried to get root, someone made a guide on here. Turned out it only worked for him because he had an unlocked developers phone running software version V08(someting more I don't remember)...
But as I said, just a thought!!!
Click to expand...
Click to collapse
I don't have the phone anymore... but I did have a device sent directly from LG as a review device. So, it could have been a dev model.
I always use http://tutznet.com and XDA Developers website for Android Tuts, I have been reading this Android Authority site for a while, looks like one of their writer wrote this crappy article without knowing about it.
Utkarsh.bhatt12 said:
I always use http://tutznet.com and XDA Developers website for Android Tuts, I have been reading this Android Authority site for a while, looks like one of their writer wrote this crappy article without knowing about it.
Click to expand...
Click to collapse
Good one. I wrote the first article on the web about how to root the Optimus 4X HD. I even made the video that is in the article, so don't tell me I don't know what I'm doing.
Yes, you read correct, I want to hard brick my phone not unbrick it but at the same time not leave traces of evidence of tampering. An unusual request it may be, but I have tried everything but just cannot get the damn thing to brick. I wanted to brick it and then experiment on possible ways to unbrick it. And then if all failed, I was going to send it back to Samsung to see if they find any traces of deliberate tampering. Come on geniuses...I know you're out there somewhere
Rom manager flash the wong recovery fr other devce
Sent from my GT-S5830 using xda premium
DeadSp1d3r said:
Rom manager flash the wong recovery fr other devce
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
+10000000 it's so easy
Thanks. Just downloading a Rom for the S5830i to try out. Wouldn't you be able to re-flash the correct rom this way and get it to work again? Also if it does brick this way, would it leave traces when Sammy Techs investigate?
Gizmotech said:
Thanks. Just downloading a Rom for the S5830i to try out. Wouldn't you be able to re-flash the correct rom this way and get it to work again? Also if it does brick this way, would it leave traces when Sammy Techs investigate?
Click to expand...
Click to collapse
if you use rom manager samsung will not find out anything
if you flash other devices rom like acei on ace then it might brick but not for 100% sure but there is lots and lots of change that it will brick since it uses other flash scripts and binarys
Gizmotech said:
Yes, you read correct, I want to hard brick my phone not unbrick it but at the same time not leave traces of evidence of tampering. An unusual request it may be, but I have tried everything but just cannot get the damn thing to brick. I wanted to brick it and then experiment on possible ways to unbrick it. And then if all failed, I was going to send it back to Samsung to see if they find any traces of deliberate tampering. Come on geniuses...I know you're out there somewhere
Click to expand...
Click to collapse
Just download a galaxy s3 ROM and kernel...bricked right there.
Sent from my SAMSUNG-SGH-I747 using xda premium
Ok Just tried to load up the firmware file for a Ace Plus on odin 4.38 but it wont accept it and comes back with "out of memory" error on the PC screen. Will try Rom Manager.
Bingo! Bricked it. I take it there's no way that I can attempt to revive it? Also I hope there is no traces of CWM Rom Manager, Superuser or Busybox
I don't know about the traces. But the only way to revive it is JTAG or replacement motherboard.
Sent from my GT-S5830 using xda premium
Next time, I'd rather make a backup in CWM and then restore it from another Recovery. What this does is delete the boot.img, so now your phone can't do anything and Samsung can't get any logs etc. from the device.
Also REMEMBER! Play dumb when taking it to the Samsung store! Don't mention Roms etc..
PulseDroid said:
Next time, I'd rather make a backup in CWM and then restore it from another Recovery. What this does is delete the boot.img, so now your phone can't do anything and Samsung can't get any logs etc. from the device.
Also REMEMBER! Play dumb when taking it to the Samsung store! Don't mention Roms etc..
Click to expand...
Click to collapse
Or rename a text file to boot.img and flash it as a ROM. This gives a totally faulty ROM.
Sent from my GT-S5830 using xda premium
Thanks guys, gonna give it in to service today and will keep you guys updated. I like the above method as it definitely would not leave traces of CWM, Superuser or Busybox. Duh, why didn't I think of that:silly: but too late now. maybe next time or someone else.
Gizmotech said:
Thanks guys, gonna give it in to service today and will keep you guys updated. I like the above method as it definitely would not leave traces of CWM, Superuser or Busybox. Duh, why didn't I think of that:silly: but too late now. maybe next time or someone else.
Click to expand...
Click to collapse
Do you not ever think there is someone in samsung softwere development reading this...
Sent from my GT-S5830
Best way to hardbrick your phone is to use rom manager
I got transformed into a potato while writing this post
athe_s said:
Do you not ever think there is someone in samsung softwere development reading this...
Sent from my GT-S5830
Click to expand...
Click to collapse
I do. That's the good thing about having a screen-name
Updates!!!
Gizmotech said:
Thanks guys, gonna give it in to service today and will keep you guys updated.
Click to expand...
Click to collapse
Any updates dude?
Wow. No wonder phone manufacturer doesn't honor warranty nowadays.
Seriously if u want to do such scam u should do it quietly without creating thread asking howto do so.
This is nice.... You can brick your phone in the last month of you year warranty and get a new phone/motherboard
Once my friends phone switched off suddenly... Non rooted stock
It happened suddenly and also out of warranty
She had to pay 5k to the Samsung people to get it repaired... And the plus point she got 14GB internal memory with the new motherboard
Her phone was the Samsung galaxy S i9000
it would've been done in free if she had warranty
So maybe you might get the GT S5830i.. The new version mother board or something
Best of luck
Gizmotech said:
Yes, you read correct, I want to hard brick my phone not unbrick it but at the same time not leave traces of evidence of tampering. An unusual request it may be, but I have tried everything but just cannot get the damn thing to brick. I wanted to brick it and then experiment on possible ways to unbrick it. And then if all failed, I was going to send it back to Samsung to see if they find any traces of deliberate tampering. Come on geniuses...I know you're out there somewhere
Click to expand...
Click to collapse
ohh !!!! so easy !!! install rom manager... 100% sure samsung won't find out what went worng with your ace ...
ysrini said:
Any updates dude?
Click to expand...
Click to collapse
Yes, the phone was repaired. They apparently replaced the motherboard.
an0nym0us_ said:
Wow. No wonder phone manufacturer doesn't honor warranty nowadays.
Seriously if u want to do such scam u should do it quietly without creating thread asking howto do so.
Click to expand...
Click to collapse
I would have done it quietly if I didn't need the help. Duh! Besides, I doubt this is the reason why they don't honour warranty. I think it is more to do with that they are greedy corporate companies who would rather save at any cost irrespective of whose fault it is. I mean why should they penalise someone because of something someone else done? After all you are all paying customers. They scam people everyday and no one complains. I guess people only complain when it happens to them. You can buy a new phone and have it go faulty within 2 months. Do you think you can get a new phone under warranty from them? No it will be a refurbished one and doesn't mater how much you scream and shout for a new one, they don't care. A neither do I.
jumbobombo said:
So maybe you might get the GT S5830i.. The new version mother board or something
Best of luck
Click to expand...
Click to collapse
No, I think it is the same motherboard. What I don't understand is, whether it is the same motherboard they repaired or a replacement one, as this phone was initially locked to the Three network. I had it unlocked. So a new motherboard would have meant that the phone would be locked again. But when I received it back, it would still accept any sims.
Hello,
I followed this thread to root my phone. http://forum.xda-developers.com/showthread.php?t=2186368
Then i installed this custom recovery http://forum.xda-developers.com/showthread.php?t=2187363
Then i wanted to overclock using this kernel http://forum.xda-developers.com/showthread.php?t=2172888
But my phone need's unlocked bootloader in order to do this. (and i don't want to unlock it)
Any kernel that allow overclock with locked bootloader ?
Thanks
Im afraid not,AFAIK there is only one kernel that allows overclocking,and that is the DoomKernel by the awesome DoomLord
....
Then i'll wait a way to unlock bootloader without loosing warrantly thanks
Poustic said:
Then i'll wait a way to unlock bootloader without loosing warrantly thanks
Click to expand...
Click to collapse
You will be waiting for a looong time. No one has managed to get the DRM keys back after relocking the bootloader.
Poustic said:
Then i'll wait a way to unlock bootloader without loosing warrantly thanks
Click to expand...
Click to collapse
You may actually want to have a good read of the terms and conditions of the Sony website for unlocking. It doesn't specifically mention that it breaks your warranty. It states that if your phone is send back for repair, it has to be on stock firmware. IF you are unable to do this they will charge you a service fee to have a technician repair the software (I'm guessing J-tagging or something more professional?). They do mention the fee for that was expensive. So basically if say for example you permanently lost radio (signal) because of a hardware issue that you in no way caused by flashing some ROM or tweak that messes with the drivers for that, it should be fine. It's a hardware thing - you didn't cause it. If you hardbrick your device and they have to bring it back from the dead, they'll charge you. If you overclock it like a mofo and burn out the CPU they will likely charge you for the initial software flash and charge you again for either repair/replacement of the logic board or complete phone.
That's the gist of it from memory. There may of course be some little clause or something that they could get out of it if they wanted that I skimmed too quickly, but you'd probably find if it's a genuine problem from them they would repair it. If you'd clearly messed with it and stuffed it, they wouldn't. Sounds like a normal warranty to me
EDIT: just had a quick gander at it again and here we go "Please note that you may void the warranty of your device and/or any warranty from your operator if you unlock the boot loader". I think the key word from that would be "may".
and also " In addition, if you brick the device, it is your own responsibility. " The same thing could be said with a locked bootloader and you stuffed something up trying to root it or hack it in some other way.
ROMAur allows to to change the cpu speed, how well this works is another thing. I have heard somewhere that there is some type of throttling within the standard kernel which still prevents the phone reaching the full potential, but custom kernel gets around this.
I have rechecked this and they have removed the overclock in the downloadable version
danw_oz said:
I have rechecked this and they have removed the overclock in the downloadable version
Click to expand...
Click to collapse
So where i can get the overclock version please ? Cause in the official thread look's like it was removed indeed http://forum.xda-developers.com/showthread.php?t=2167064
Poustic said:
So where i can get the overclock version please ? Cause in the official thread look's like it was removed indeed http://forum.xda-developers.com/showthread.php?t=2167064
Click to expand...
Click to collapse
I will have a look to see if I still have that version
Thank you i wonder why they removed it :silly:
Poustic said:
Thank you i wonder why they removed it :silly:
Click to expand...
Click to collapse
Probably because it didn't work properly, I have had a look and just cleaned those up about 5 days ago, on all my devices
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!