Related
I just bought a Nexus 5 recently but it's flash memory go corrupt so I request a RMA and got a new one already. However, as the flash memory is corrupted, I can not restore the device to it's original state. I have not flashed a custom rom, but I have unlocked the boot loader, flash custom recovery, root it and flash a new boot animation. What would be the worst thing to happen?
nerodarknight said:
I just bought a Nexus 5 recently but it's flash memory go corrupt so I request a RMA and got a new one already. However, as the flash memory is corrupted, I can not restore the device to it's original state. I have not flashed a custom rom, but I have unlocked the boot loader, flash custom recovery, root it and flash a new boot animation. What would be the worst thing to happen?
Click to expand...
Click to collapse
Unless they can prove that you broke the flash memory by unlocking the bootloader, it'll be fine
rootSU said:
Unless they can prove that you broke the flash memory by unlocking the bootloader, it'll be fine
Click to expand...
Click to collapse
Thank u, it has been troubling me ever since
So, you bought a new nexus 5 before sending the other to RMA and, you want to "clean" the old before sending it ?
Well, can you boot it in fastboot ? If so, try flashtool and flash factory images ?
Charlus97 said:
So, you bought a new nexus 5 before sending the other to RMA and, you want to "clean" the old before sending it ?
Well, can you boot it in fastboot ? If so, try flashtool and flash factory images ?
Click to expand...
Click to collapse
No they sent me a new one alreadt, and now I have to return the broken one to them. About your suggestion, I did try but because the flash memory is corrupted, u can't write or read anything from it, including the OS
Wow. Google sent you a new phone before you've sent them your old ? Never seen that before
But like rootSU said, unless they're able to prove that it's your fault, there's no problem.
But, if you're able to boot into recovery/fastboot, you should be able to restore the orignal recovery & relock the bootloader, no ?
Charlus97 said:
Wow. Google sent you a new phone before you've sent them your old ? Never seen that before
But like rootSU said, unless they're able to prove that it's your fault, there's no problem.
But, if you're able to boot into recovery/fastboot, you should be able to restore the orignal recovery & relock the bootloader, no ?
Click to expand...
Click to collapse
This is how Google does RMA's they send you a new device and put a hold on your credit card equivalent to the price of the device. The hold is removed upon them receiving your old device.
Oh, ok. I used to see RMA like Asus : We pick your device, you wait 3 weeks and, if you're lucky, we will sent it back to you for free.
Just had a doubt about the RMA?
I purchased the device from India and the RMA process is like they pick up the device inspect it and send the replacement.
They collected mine yesterday.
They did mention that the device will be inspected by a technical team,now when i requested them for a replacement over telephone they asked me to send them pictures of the phone and then after reviewing them they notified me that they could now initiate a replacement,so what do they inspect for exactly?
and will they be sending me a new device?
well, I relock it but as soon as I turn it off, it got unlock again, I don't know why
Sonone said:
Just had a doubt about the RMA?
I purchased the device from India and the RMA process is like they pick up the device inspect it and send the replacement.
They collected mine yesterday.
They did mention that the device will be inspected by a technical team,now when i requested them for a replacement over telephone they asked me to send them pictures of the phone and then after reviewing them they notified me that they could now initiate a replacement,so what do they inspect for exactly?
and will they be sending me a new device?
Click to expand...
Click to collapse
They're checking for anything that could would void the warranty, such as user damage or a colourized water damage indicator.
LG RMA works differently from Google RMA. It's the traditional wait a few weeks until your phone is fixed, versus cross shipping of the device so you're never without a phone.
so i was on cataclysm from the beginning and everything worked great. I flashed stock 4.4.4 cause i want to use just xposed with a nice vanilla rom. everything works great except i cant get or place calls. i have sprint lte full bars, can get data and everything send texts/mms, go on facebook, dl stuff, just no calls. wifi or not doesnt matter either. everytime i try to place one it just sits on dialing and i lose all bars and then says can t make call, no connection. once i hang up the bars and lte come back.
I have noticed my network ends up on global sometimes instead of LTE but even when i switch it to LTE it still doesnt work. i have updated prl and profile too. Any ideas? thanks
EDIT: yeah i still cant seem to fix it. I was going to go back to a 4.4.2 rom but for some reason it fails in twrp everytime now... :/ but this is the exact problem i am having in this thread https://productforums.google.com/forum/#!topic/nexus/Or6_6zCtBwc
seems like it might be sprints fault
Did you wipe?
Sent from my Nexus 5 using Tapatalk
rootSU said:
Did you wipe?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
yep cache, dalvik, data. never had this problem with any other roms before? might it be a 4.4.4 issue? cataclysm was 4.4.2
fergdizzle9090 said:
yep cache, dalvik, data. never had this problem with any other roms before? might it be a 4.4.4 issue? cataclysm was 4.4.2
Click to expand...
Click to collapse
did you update the bootloader and radio?
Zepius said:
did you update the bootloader and radio?
Click to expand...
Click to collapse
no i did not, just twrp. would that be the problem?
possibly. you should do it to be safe.
Zepius said:
possibly. you should do it to be safe.
Click to expand...
Click to collapse
do you have to do it when you upgrade android versions? is there any quick link you can post to help me out with it? im not all that familiar with updating those. Ill search around and see what I can find. thanks for the suggestion though
Im thinking about RMAing my nexus 5 though because the power button is very loose and rattles loudly when i tap the screen, dont want a crappy refurb in place of my mint pristine nexus though :/ lol
Rma is always new
Sent from my Nexus 5 using Tapatalk
rootSU said:
Rma is always new
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
oh i didnt know that. well great thanks. Ill give the updates a shot and consider the rma more now i know ill be getting a new phone. just dont want to be without it for a while lol
yeah i still cant seem to fix it. I was going to go back to a 4.4.2 rom but for some reason it fails in twrp everytime now... :/ but this is the exact problem i am having in this thread https://productforums.google.com/fo...ce=footer#!msg/nexus/Or6_6zCtBwc/j5CP8vy4jGAJ
Install 4.4.4 using fastboot. And after make sure you are using the latest version of twrp.
Lokke9191 said:
Install 4.4.4 using fastboot. And after make sure you are using the latest version of twrp.
Click to expand...
Click to collapse
ill have to look up some stuff on fastboot and recovery updates. been a while since ive done anything out of recovery
fergdizzle9090 said:
ill have to look up some stuff on fastboot and recovery updates. been a while since ive done anything out of recovery
Click to expand...
Click to collapse
Section 3 #1 and Section 4 #1
[Resource] All Guides and Info Threads
Lethargy said:
Section 3 #1 and Section 4 #1
[Resource] All Guides and Info Threads
Click to expand...
Click to collapse
oh yeah ok thanks. so you are suggesting just completely restarting and rerooting from absolute stock?
fergdizzle9090 said:
oh yeah ok thanks. so you are suggesting just completely restarting and rerooting from absolute stock?
Click to expand...
Click to collapse
Personally I would flash the factory images again just to rule out software being the issue, if it still happens then I guess RMA or whatever.
Lethargy said:
Personally I would flash the factory images again just to rule out software being the issue, if it still happens then I guess RMA or whatever.
Click to expand...
Click to collapse
yeah i'll give that a try. weird thing is this happened only after i flashed 4.4.4 from cataclysm 4.4.2. i am waiting to hear if an RMA fixes the issue since someone else is already going that route. it sounds to me like it might be sprint
fergdizzle9090 said:
yeah i'll give that a try. weird thing is this happened only after i flashed 4.4.4 from cataclysm 4.4.2. i am waiting to hear if an RMA fixes the issue since someone else is already going that route. it sounds to me like it might be sprint
Click to expand...
Click to collapse
I doubt it is sprint causing this, or it would be all over these forums. I'd definitely install 4.4.4 via fastboot it'll give you the newest radio and the stock recovery. I'm betting this will fix your issue. Then just use fastboot or flashify to install the newest twrp, and flash su in recovery. If this doesn't fix it, it's a hardware issue.
Lokke9191 said:
I doubt it is sprint causing this, or it would be all over these forums. I'd definitely install 4.4.4 via fastboot it'll give you the newest radio and the stock recovery. I'm betting this will fix your issue. Then just use fastboot or flashify to install the newest twrp, and flash su in recovery. If this doesn't fix it, it's a hardware issue.
Click to expand...
Click to collapse
thanks ill try it out when i got a spare moment. now that im thinking of it this all happened after i updated twrp, so could that be the root of all this you think? because i used the twrp app to update it instead of flashing, and i noticed it has been acting extremely weird lately.
You might check your APN settings. I had issues with MMS after flashing 4.4.4.
hsas.69 said:
You might check your APN settings. I had issues with MMS after flashing 4.4.4.
Click to expand...
Click to collapse
ill look into it. people who have this problem said its not the apn though because i get data just fine and i can recieve calls. its only when i am placing a call it goes crazy and disconnects me
EDIT: so anyone know how to get to apn for sprint? its not under mobile networks. is it buried in a dialer menu or something?...
Lokke9191 said:
I doubt it is sprint causing this, or it would be all over these forums. I'd definitely install 4.4.4 via fastboot it'll give you the newest radio and the stock recovery. I'm betting this will fix your issue. Then just use fastboot or flashify to install the newest twrp, and flash su in recovery. If this doesn't fix it, it's a hardware issue.
Click to expand...
Click to collapse
well full reflash of 4.4.4 stock from google through fastboot didnt work :/ i noticed also that it hasnt been connecting during initial setup, i have to connect to wifi. think my phone might be borked :crying:
Hi everyone.
I have the following problem with a Nexus 5: During an update, the system crashed. The phone is now stuck in an endless bootloop, trying to install the update. When left long enough, the update screens eventually come up, but you are immediately blasted with a ton of errors and no matter what you do, you are unable to complete the update. This, however, is not the problem.
I have tried various utilities in order to flash the phone back to factory settings. I have made use of Unified Android ToolKit, as well as Nexus Root Toolkit, but a problem with the phone itself is preventing me from flashing it and the problem is as follows: I can access the phone via USB, as well as the bootloader, but when I unlock the bootloader to start the flashing, it immediately locks itself again and I'm unable to start the flash process.
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?
Mystical_Titan said:
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?
Click to expand...
Click to collapse
If the lock state reverts on a reboot, 99 times out of 100, it means the internal memory has an issue. RMA.
rootSU said:
If the lock state reverts on a reboot, 99 times out of 100, it means the internal memory has an issue. RMA.
Click to expand...
Click to collapse
Thanks for the fast response. :good:
Mystical_Titan said:
Thanks for the fast response. :good:
Click to expand...
Click to collapse
No probs. Sounds like the update got stuck at the bootloader flash and corrupted. It's probably not a fatal NAND issue, rather corrupt partition or two but it usually means sending it in.
You can try the LG flashtool as a last resort before doing so though, as you never know...
You can find a link to it in the sticky thread in my signature. Best to stay away from actual "toolkits" though and either use fastboot manually or LG flash tool, although fastboot probably cant help you here - just saying for future ref...
Mystical_Titan said:
Hi everyone.
I have the following problem with a Nexus 5: During an update, the system crashed. The phone is now stuck in an endless bootloop, trying to install the update. When left long enough, the update screens eventually come up, but you are immediately blasted with a ton of errors and no matter what you do, you are unable to complete the update. This, however, is not the problem.
I have tried various utilities in order to flash the phone back to factory settings. I have made use of Unified Android ToolKit, as well as Nexus Root Toolkit, but a problem with the phone itself is preventing me from flashing it and the problem is as follows: I can access the phone via USB, as well as the bootloader, but when I unlock the bootloader to start the flashing, it immediately locks itself again and I'm unable to start the flash process.
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?
Click to expand...
Click to collapse
happened to me while installing the new SNAPSHOT version of Cyanogenmod, I wiped everything and reflashed it and it works
BruKnowsBest said:
happened to me while installing the new SNAPSHOT version of Cyanogenmod, I wiped everything and reflashed it and it works
Click to expand...
Click to collapse
Can anyone suggest some steps for me to try before I RMA the phone? Although, being unable to unlock the bootloader probably limits my options.
Mystical_Titan said:
Can anyone suggest some steps for me to try before I RMA the phone? Although, being unable to unlock the bootloader probably limits my options.
Click to expand...
Click to collapse
I was stuck in the boot animation and when it opened there was a lot of system errors and it would reboot by itself over and over again.
what fixed it was to do a wipe cache and dalvik and reinstall it
BruKnowsBest said:
I was stuck in the boot animation and when it opened there was a lot of system errors and it would reboot by itself over and over again.
what fixed it was to do a wipe cache and dalvik and reinstall it
Click to expand...
Click to collapse
I tried the 'wipe cache' as well, but it returns a bunch of errors as well. I'm starting to think the NAND is screwed. What is dalvik?
Mystical_Titan said:
I tried the 'wipe cache' as well, but it returns a bunch of errors as well. I'm starting to think the NAND is screwed. What is dalvik?
Click to expand...
Click to collapse
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk
rootSU said:
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I completely forgot that you mentioned the LG Flashtool, I feel like such an idiot. I'll try that tomorrow as a last resort.
No worries
Sent from my Nexus 5 using Tapatalk
rootSU said:
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i thought about LG FLASHTOOL but decided to try reinstaling the rom cuz i had no other option since i forgot to leave a backup rom on the device. So I did it as if I was installing a brand new rom Wiped dalvik, cache and system then reflashed the rom and then the gapps. Even tho it was the same ROM file I had a different outcome. It's working fine now but I did go back to the nightlies after it started working again just to be safe.
Now... people may have a different outcome when trying to solve this issue but this actually worked for me after having a minor heart-attack thinking I was gonna lose all my stuff
BruKnowsBest said:
i thought about LG FLASHTOOL but decided to try reinstaling the rom cuz i had no other option since i forgot to leave a backup rom on the device. So I did it as if I was installing a brand new rom Wiped dalvik, cache and system then reflashed the rom and then the gapps. Even tho it was the same ROM file I had a different outcome. It's working fine now but I did go back to the nightlies after it started working again just to be safe.
Now... people may have a different outcome when trying to solve this issue but this actually worked for me after having a minor heart-attack thinking I was gonna lose all my stuff
Click to expand...
Click to collapse
Yes, but your issue is different to the OP's. His bootloader lock state reverts whenever he changes it. This is a pretty much "fatal" issue. What you did cannot help him unfortunately.
rootSU said:
Yes, but your issue is different to the OP's. His bootloader lock state reverts whenever he changes it. This is a pretty much "fatal" issue. What you did cannot help him unfortunately.
Click to expand...
Click to collapse
oh ok, I misunderstood
rootSU said:
No worries
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It speaks about a KDZ file. What is it and where would I find it?
Mystical_Titan said:
It speaks about a KDZ file. What is it and where would I find it?
Click to expand...
Click to collapse
Not sure, never used it. Are you following the Nexus 5 LG Flash tool guide? If not, have a look. You can get to it via my signature
rootSU said:
Not sure, never used it. Are you following the Nexus 5 LG Flash tool guide? If not, have a look. You can get to it via my signature
Click to expand...
Click to collapse
Well, that's that. This phone is done.
Yup. RMA
Sent from my Nexus 5 using Tapatalk
TL: My efs partition got screwed so my phone doesn't get service which is sad, But when I turn it on, after just working for a few minutes, it just reboots, which is very annoying, does anyone have a solution for this?
Long Version:
I was on the bus home when my phone went out of charge and died, after getting home I plugged it in, but it was stuck on a Loop, which led to me flashing a bunch of Kernels, and ROMs, later one ROM did work and the phone booted up, but my IMEI was gone so I knew my efs partition was screwed, and I just gave up, I still want to use my Nexus 5 as a normal but without the phone feature, which is somewhat okay,
and One weird problem that came to mind is I cannot install any ROM with version 5.0.2, it just won't boot up, but 5.0.1 is okay...but my phone just Reboots every 1-10 mins, I don't know what the problem is, and I don't know how to check whether or not its the power button, anyone have a good idea for solving this ?
You must have corrupted persist partition. Same as here: http://forum.xda-developers.com/google-nexus-5/help/nexus-5-bootloop-t3047895 the strange thing you both have is that you experience reboot. Are you on lollipop rom?
Also to fix persist follow this guide: http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
bitdomo said:
You must have corrupted persist partition. Same as here: http://forum.xda-developers.com/google-nexus-5/help/nexus-5-bootloop-t3047895 the strange thing you both have is that you experience reboot. Are you on lollipop rom?
Also to fix persist follow this guide: http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
Click to expand...
Click to collapse
Yes I'm on a Lollipop rom, and I already applied the presist fix, it didn't change anything.
Did you try to flash stock google image?
Sharo93 said:
Yes I'm on a Lollipop rom, and I already applied the presist fix, it didn't change anything.
Click to expand...
Click to collapse
kirmr said:
Did you try to flash stock google image?
Click to expand...
Click to collapse
Try to flash cache.img in fastboot. If it still does not help, then your EFS is indeed corrupted. I wish I knew a method to fixing efs.
kirmr said:
Did you try to flash stock google image?
Click to expand...
Click to collapse
Yes I already did, I have almost tried everything, short of sending it to repairs which I can't because where I live there is no such place.
bitdomo said:
Try to flash cache.img in fastboot. If it still does not help, then your EFS is indeed corrupted. I wish I knew a method to fixing efs.
Click to expand...
Click to collapse
I already did that...I know the efs is corrupted...the only fix i think is using something like Octoplus Box or something
Sharo93 said:
TL: My efs partition got screwed so my phone doesn't get service which is sad, But when I turn it on, after just working for a few minutes, it just reboots, which is very annoying, does anyone have a solution for this?
Long Version:
I was on the bus home when my phone went out of charge and died, after getting home I plugged it in, but it was stuck on a Loop, which led to me flashing a bunch of Kernels, and ROMs, later one ROM did work and the phone booted up, but my IMEI was gone so I knew my efs partition was screwed, and I just gave up, I still want to use my Nexus 5 as a normal but without the phone feature, which is somewhat okay,
and One weird problem that came to mind is I cannot install any ROM with version 5.0.2, it just won't boot up, but 5.0.1 is okay...but my phone just Reboots every 1-10 mins, I don't know what the problem is, and I don't know how to check whether or not its the power button, anyone have a good idea for solving this ?
Click to expand...
Click to collapse
I have pretty much the same issue you do so I'm going to stay posted here.
Do you have an old TWRP backup?
Try to restore any TWRP backup you made of your phone.
Unless you unchecked If you checked that option before making the backup, the EFS partition should be present in the backup.
Best of luck
Anjo_Smash said:
I have pretty much the same issue you do so I'm going to stay posted here.
Click to expand...
Click to collapse
The efs is not gonna get fixed unless you have special tools for it, but the random reboots have spotted ever since I installed the Pure White ROM
joegestes said:
Try to restore any TWRP backup you made of your phone.
Unless you unchecked that option before making the backup, the EFS partition should be present in the backup.
Best of luck
Click to expand...
Click to collapse
Unfortunately I don't have such a back up, I do however have access to two other Nexus 5s, which i don't want to mess with their IMEI because google might block something and them getting screwed is a no-no...I don't know if my Phone service provider would mind if They see the same IMEI coming up on there system twice, but I don't wanna risk it..
Sharo93 said:
Unfortunately I don't have such a back up, I do however have access to two other Nexus 5s, which i don't want to mess with their IMEI because google might block something and them getting screwed is a no-no...I don't know if my Phone service provider would mind if They see the same IMEI coming up on there system twice, but I don't wanna risk it..
Click to expand...
Click to collapse
Do not try to restore an efs from another device. It won't work and you'll make your problem worse.
Sent from my Nexus 5 using XDA Free mobile app
Sharo93 said:
Unfortunately I don't have such a back up, I do however have access to two other Nexus 5s, which i don't want to mess with their IMEI because google might block something and them getting screwed is a no-no...I don't know if my Phone service provider would mind if They see the same IMEI coming up on there system twice, but I don't wanna risk it..
Click to expand...
Click to collapse
Man that sucks
Lesson learned I guess, always make a full backup of your device in its original factory state when you buy it.
Sorry for your loss
Hi guys
As you probably know by reading the title, i completely messed up. I was on the stock google factory image and decided to flash a custom kernel. I enabled usb debuging and oem unlock. after having unlocked the bootloader, I installed the twrp boot img and then flashed the kernel. All was well when i stupidly decided to lock my bootloader. Things crashed and now when i try to boot into my phone, the google logo appears and 1 seconds later crashes keeps doing it until i turn my phone off. My bootloader is locked and i think usb debuging and oem unlock are also disabled.
The same thing happens when i try to go to the recovery, it just crashes.
Any help would be greatly appreciated guys. thank you !!
Colday96 said:
Hi guys
As you probably know by reading the title, i completely messed up. I was on the stock google factory image and decided to flash a custom kernel. I enabled usb debuging and oem unlock. after having unlocked the bootloader, I installed the twrp boot img and then flashed the kernel. All was well when i stupidly decided to lock my bootloader. Things crashed and now when i try to boot into my phone, the google logo appears and 1 seconds later crashes keeps doing it until i turn my phone off. My bootloader is locked and i think usb debuging and oem unlock are also disabled.
The same thing happens when i try to go to the recovery, it just crashes.
Any help would be greatly appreciated guys. thank you !!
Click to expand...
Click to collapse
I feel bad for you. However, you bricked your Pixel.
As I mentioned yesterday, contact Google for an RMA replacement.
phaino00 said:
I feel bad for you. However, you bricked your Pixel.
As I mentioned yesterday, contact Google for an RMA replacement.
Click to expand...
Click to collapse
I bought the phone on ebay. Could i still get a RMA replacement ?
Colday96 said:
I bought the phone on ebay. Could i still get a RMA replacement ?
Click to expand...
Click to collapse
I don't believe so since you're not the original owner. However, it doesn't hurt to try.
If you bl locked the phone w modified software ur boned. I believe that RMA availability is transferrable from owner to owner, however, I also believe that they will refuse to RMA a phone which technically broke because AVB is doing its job properly. You can try but I'd say your chances are slim. Sorry mate. Also future reference: if you don't have any reason in particular to relock your phone, just don't. You'll save yourself the hassle of having to do it again and it wiping the phone everytime any software thing goes wrong or anytime u want to upgrade custom ROM or kernel or anything of the sort. This goes for any phone not just those with android verified boot.
phaino00 said:
I don't believe so since you're not the original owner. However, it doesn't hurt to try.
Click to expand...
Click to collapse
My seller is about to contact google to get a replacement. do you think google will know if i did something with it i shouldn't have ? Since i can't boot in the recovery, won't they be able to do it either ?
Colday96 said:
My seller is about to contact google to get a replacement. do you think google will know if i did something with it i shouldn't have ? Since i can't boot in the recovery, won't they be able to do it either ?
Click to expand...
Click to collapse
Assume they will.
Colday96 said:
My seller is about to contact google to get a replacement. do you think google will know if i did something with it i shouldn't have ? Since i can't boot in the recovery, won't they be able to do it either ?
Click to expand...
Click to collapse
Yes they will know but they have proprietary software to forcefully unlock/reformat the phone properly if they so choose to actually accept the phone
This just happened to me today, i was trying to reset it because I'm selling this phone and boom.. Brick... Just lost $400 ?
Nandolkz said:
This just happened to me today, i was trying to reset it because I'm selling this phone and boom.. Brick... Just lost $400 ?
Click to expand...
Click to collapse
You can still sell it for around 150 for parts on ebay
Nandolkz said:
This just happened to me today, i was trying to reset it because I'm selling this phone and boom.. Brick... Just lost $400
Click to expand...
Click to collapse
Can't you restore using the stock zips from google?
Poebat said:
Can't you restore using the stock zips from google?
Click to expand...
Click to collapse
I already tried, using both 8.1 and the first Nougat... It says oem can't unlock. I even download the skipsoft app to tryout but fail
Nandolkz said:
I already tried, using both 8.1 and the first Nougat... It says oem can't unlock. I even download the skipsoft app to tryout but fail
Click to expand...
Click to collapse
If you are flashing the latest version of Oreo you don't need to oem unlock. What version of Android were you running before you bricked it?
Poebat said:
If you are flashing the latest version of Oreo you don't need to oem unlock. What version of Android were you running before you bricked it?
Click to expand...
Click to collapse
8.0, well I already tried the dic 8.1 and it didn't work... Let me try the nov build.. or im going to try both let me see what happen.. I'll share the cmd log...
Nandolkz said:
8.0, well I already tried the dic 8.1 and it didn't work... Let me try the nov build.. or im going to try both let me see what happen.. I'll share the cmd log...
Click to expand...
Click to collapse
Okay. If that doesn't work try the 7.1.2 build with the flash-all.bat
Poebat said:
Okay. If that doesn't work try the 7.1.2 build with the flash-all.bat
Click to expand...
Click to collapse
It won't work because his bootloader is locked. I also tried the OTA file and that didn't work either. Do to have usb debugging on ?
Colday96 said:
It won't work because his bootloader is locked. I also tried the OTA file and that didn't work either. Do to have usb debugging on ?
Click to expand...
Click to collapse
He doesn't have a working OS so I doubt it
Here is what is happening to me... Any ideason how to fix it? ?
Nandolkz said:
Here is what is happening to me... Any ideason how to fix it? ?
Click to expand...
Click to collapse
Try flashing the stock rom with fastboot
Poebat said:
Try flashing the stock rom with fastboot
Click to expand...
Click to collapse
Here