Related
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
So I have an AT&T G4 and I was attempting to root it, something went wrong, when I completed the rooting process I unplugged my phone and got an Authentication fail #11. So I decided I would flash the H810PR ZDK on to the phone hoping I could fix it using this guide (http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848) after I completed that I got nothing..... black screen. Now it wont turn on and when I plug it in hear a failed driver sound and this shows up http://imgur.com/EGgdiYL . I've read like two success stoires of people with my problem actually getting AT&T to replace their phone with my problem under warranty, what can I do?
LunaticHD said:
So I have an AT&T G4 and I was attempting to root it, something went wrong, when I completed the rooting process I unplugged my phone and got an Authentication fail #11. So I decided I would flash the H810PR ZDK on to the phone hoping I could fix it using this guide (http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848) after I completed that I got nothing..... black screen. Now it wont turn on and when I plug it in hear a failed driver sound and this shows up http://imgur.com/EGgdiYL . I've read like two success stoires of people with my problem actually getting AT&T to replace their phone with my problem under warranty, what can I do?
Click to expand...
Click to collapse
Its look like your device's hard brick, nothing can do except changing the device.
faizalotai said:
Its look like your device's hard brick, nothing can do except changing the device.
Click to expand...
Click to collapse
I'm under warranty still, do you think that I can exchange it with AT&T?
LunaticHD said:
I'm under warranty still, do you think that I can exchange it with AT&T?
Click to expand...
Click to collapse
I guess the phone are not booting, as long as there's no showing of leaking or damage..I think its possible to get new one..
Just says the phone not boot after charging or so..
faizalotai said:
I guess the phone are not booting, as long as there's no showing of leaking or damage..I think its possible to get new one..
Just says the phone not boot after charging or so..
Click to expand...
Click to collapse
Correct, it isnt booting at all, so I should just tell them it broke or somthing along those lines?
LunaticHD said:
Correct, it isnt booting at all, so I should just tell them it broke or somthing along those lines?
Click to expand...
Click to collapse
Yup, and pray..
faizalotai said:
Yup, and pray..
Click to expand...
Click to collapse
Okay thank you for the help! I'll probably contact them tomorrow and just tell them it stopped working and hopefully they will just replace it, after all its their fault for not giving us a proper ZDK to fix it ourselves
LunaticHD said:
Okay thank you for the help! I'll probably contact them tomorrow and just tell them it stopped working and hopefully they will just replace it, after all its their fault for not giving us a proper ZDK to fix it ourselves
Click to expand...
Click to collapse
What if I don't have a warranty on my phone?
Who's your carrier?
LunaticHD said:
Who's your carrier?
Click to expand...
Click to collapse
AT&T
I did the same I flash the wrong kdz files.All we need some one to uploads the complete eMMC IMAGE to try to revive the phone
The biggest error, is to not make a backup of your stock system.img before flashing.
I encountered the error #11, and fixed it by flashing back to stock, then flashing the correct rooted system image version.
It's caused by flashing a system image that doesn't match your current installed software version.
Ie- you have 10g installed but attempt to load a rooted 10o system image, or vice versa.
same happen to me but i have no opcion im outside the united states so im stuck with this bricked phone. theres a tool for the lg g3 called boarddiag that only works for g3 maybe in a future g4 is added
Hello everybody!
I tried several methods for repairing my phone, but without success.
* I have not bin files or bak files in /efs folder.
how to fix this issue?
Thanks all
sangtiet said:
Hello everybody!
I tried several methods for repairing my phone, but without success.
* I have not bin files or bak files in /efs folder.
how to fix this issue?
Thanks all
Click to expand...
Click to collapse
Is your phone just rebooting constantly with no signal bars or imei/baseband info showing as unknown in phone status?
droseofc said:
Is your phone just rebooting constantly with no signal bars or imei/baseband info showing as unknown in phone status?
Click to expand...
Click to collapse
Yes, It's.
Rom cook: My phone just rebooting constantly with no signal bars or imei/baseband info showing as unknown in phone status.
Rom stock: My phone unbootable because dm-verity verification failed.
Put your phone in download mode and let it die completely after it dies wait 10 minutes, then plug in to your charger and turn on, it should work
Sent from my SM-N920P using XDA-Developers mobile app
sangtiet said:
Yes, It's.
Rom cook: My phone just rebooting constantly with no signal bars or imei/baseband info showing as unknown in phone status.
Rom stock: My phone unbootable because dm-verity verification failed.
Click to expand...
Click to collapse
^what he said. Deff works.
What did you do to cause it to happen because i can't remember what caused me to get the same thing. I got my battery replaced before i known about the letting the battery die but that do work.
Sent from my SM-G935F using XDA-Developers mobile app
For me just flashing in general. First time was flashing root on stock mm. 2nd time was flashing a kernel on custom rom. 3rd time was flashing root after i had fixed it for the 2nd time so i just let die again and it was good again.
please help me... i have been trying for 2 months now...flashed MM odin from OI6 then tried to flash Smoars Rom.... now efs unable to mount and i tried letting phone die..but i think my situation is different. leeting phone die from download mode is for bootlooping note 5,mine doesnt bootloop.it just doesnt boot.it goes back to recovery and says unable to mount efs..dm verity verification failed..please help me./ ive been looking to 5 forums now and i cant still find a solution
You might want to try flashing stock OGD.
fail...
A.Noob said:
You might want to try flashing stock OGD.
Click to expand...
Click to collapse
failed// SW REV. CHECK FAIL. DEVICE 2 BINARY 1
..i tried OGD,OI6,OK3,PC3 all of them...all of them flashes successfully except OGD.but when its successful it stays on samsung logo..until it dies.then when i open..its the same thing
Checked with Google. Try using this forum (using note 5 rom and twrp) http://forum.xda-developers.com/galaxy-s6/general/how-to-fix-rev-check-fail-device-2-t3146522 or try "Odin flash the team win recovery. Then flash the stock rom." I don't know if either will work, just trying to help.
A.Noob said:
Checked with Google. Try using this forum (using note 5 rom and twrp) http://forum.xda-developers.com/galaxy-s6/general/how-to-fix-rev-check-fail-device-2-t3146522 or try "Odin flash the team win recovery. Then flash the stock rom." I don't know if either will work, just trying to help.
Click to expand...
Click to collapse
tried that too...idk what to do..samsung wont fix it coz i rooted it..sprint wont give me a refurbished one in exchange of this one
redninja007 said:
tried that too...idk what to do..samsung wont fix it coz i rooted it..sprint wont give me a refurbished one in exchange of this one
Click to expand...
Click to collapse
Sprint hooked me up with a brand new one when something happened to mine (software wise) the tech tried flashing everything and claimed it was dead and I used my insurance
Sent from my SM-N920P using XDA-Developers mobile app
nice!
rayraycarter4 said:
Sprint hooked me up with a brand new one when something happened to mine (software wise) the tech tried flashing everything and claimed it was dead and I used my insurance
Sent from my SM-N920P using XDA-Developers mobile app
Click to expand...
Click to collapse
the prob is i dont have insurance..what if i activate y insurance then wait a couple of days then bring it to them?will that work?im dying here i need my note5 back
redninja007 said:
the prob is i dont have insurance..what if i activate y insurance then wait a couple of days then bring it to them?will that work?im dying here i need my note5 back
Click to expand...
Click to collapse
Yeah i didnt have it either but I put it on and then claimed, I never told them I rooted, I said it happened after I took an update
Sent from my SM-N920P using XDA-Developers mobile app
rayraycarter4 said:
Yeah i didnt have it either but I put it on and then claimed, I never told them I rooted, I said it happened after I took an update
Sent from my SM-N920P using XDA-Developers mobile app
Click to expand...
Click to collapse
hahaha that might work! ill try it and i will let u know
...
redninja007 said:
hahaha that might work! ill try it and i will let u know
Click to expand...
Click to collapse
tried it but sprint said. " there is nothing we could do because your phone is rooted"
WTF sprint? really nothing you can do for a 6 years customer that has 5 lines? is there anyone who can help me with this? im frustrated
Being rooted I don't take it to sprint something happens I can't fix I just lose the phone and claim it as lost
?
greco2003 said:
Being rooted I don't take it to sprint something happens I can't fix I just lose the phone and claim it as lost
Click to expand...
Click to collapse
my phone is on lease from sprint.if i claim it as lost should i pay for it?or wll they give me another one?sorry..i dont know what to do anymore...ill give a $50 reward to anyone that could help me fix my phone
HI I have 1+1 and its 2 years 3 month old. Presently its on CM13 MM(oxygen OS I guess) and rooted and have a recovery also. I did root and recovery around 8 months back.
2 days back when mobile was in pocket and 35% battery it went in to bootloop. after lot of stuffs like clearing cache and dalvik cache nothing worked.
Later at night i found out that mobile is working fine when its connected to charging (either by lapi or Mob charger). Hence I didn't go back to old recovery.
yesterday fully drained my battery and later charged to full and found same issue.
I am not able to make out whats the issue and how to move forward if I don't want to loose my resent data state. PLs guys help me to solve this issue.
will do whatever needed to restore my mobile. TIA
Wait I didn't understand what u said ,ur saying that your phone gets stuck in boot loop when its not charging ,what happens when you are changing and then u plug it off ? Does it like reset ?
Hunting_Party10 said:
Wait I didn't understand what u said ,ur saying that your phone gets stuck in boot loop when its not charging ,what happens when you are changing and then u plug it off ? Does it like reset ?
Click to expand...
Click to collapse
see it sounds weird but its true. when i connect charging it boots in normally and normal operation will start as usual. Even after full starting, once I remove charging connection it goes off to boot loop. I didn't do any modification in software also. just did normal downloading off apps.
I saw slimier 2 complaints in Oneplus forum but no one relied for that. even originator has not updated what he did finally. I have asked for reply from them too.
praveen4u13 said:
see it sounds weird but its true. when i connect charging it boots in normally and normal operation will start as usual. Even after full starting, once I remove charging connection it goes off to boot loop. I didn't do any modification in software also. just did normal downloading off apps.
I saw slimier 2 complaints in Oneplus forum but no one relied for that. even originator has not updated what he did finally. I have asked for reply from them too.
Click to expand...
Click to collapse
Try a factory reset?
Mr.Ak said:
Try a factory reset?
Click to expand...
Click to collapse
not tried but red reviews of same case who said factory reset did not help.
I was looking if anyone who faced slimier issue before can help me.
is it related to battery?
praveen4u13 said:
not tried but red reviews of same case who said factory reset did not help.
I was looking if anyone who faced slimier issue before can help me.
is it related to battery?
Click to expand...
Click to collapse
Seems to me like a hardware issue.
Can you be on recovery/fastboot without the need of a charger?
Mr.Ak said:
Seems to me like a hardware issue.
Can you be on recovery/fastboot without the need of a charger?
Click to expand...
Click to collapse
yes, along as i want. No issue to be on recovery/fastboot without charging connected. Only normal boot is having issue.
praveen4u13 said:
yes, along as i want. No issue to be on recovery/fastboot without charging connected. Only normal boot is having issue.
Click to expand...
Click to collapse
Then no issues with hardware....seems like a bad/corrupt frimware.
You need to unlock your bootloader and flash latest Cos13 through fastboot.
How to- https://forums.oneplus.net/threads/...oader-install-custom-recovery-and-root.64487/
To flash Cos13- https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Hope this helps.
Edit:After reading your first post seems like you're already rooted and have Twrp installed,with a unlocked bootloader,obviously.Though I don't able to understand if you're using cm13 or cos13 or oxygen os...
If you don't want to loose your internal storage,you can skip the userdata flash command while flashing Cos13 through fastboot,though,it is recommended to do that command.
You can always go to Twrp and take the backup of your internal storage in pc through MTP or a full backup using ADB.
Mr.Ak said:
Then no issues with hardware....seems like a bad/corrupt frimware.
You need to unlock your bootloader and flash latest Cos13 through fastboot.
How to- https://forums.oneplus.net/threads/...oader-install-custom-recovery-and-root.64487/
To flash Cos13- https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Hope this helps.
Edit:After reading your first post seems like you're already rooted and have Twrp installed,with a unlocked bootloader,obviously.Though I don't able to understand if you're using cm13 or cos13 or oxygen os...
If you don't want to loose your internal storage,you can skip the userdata flash command while flashing Cos13 through fastboot,though,it is recommended to do that command.
You can always go to Twrp and take the backup of your internal storage in pc through MTP or a full backup using ADB.
Click to expand...
Click to collapse
thanks pal. yes bootloader and all is unlocked. will see about this in coming weekend.
can't this problem be fixed if i just move back to old backup?
meanwhile is there any shortcut that reduce the time frame for doing all this on existing data. If anyone knows pls share. If this is the only go then do comment will ask to close the thread.
praveen4u13 said:
thanks pal. yes bootloader and all is unlocked. will see about this in coming weekend.
can't this problem be fixed if i just move back to old backup?
meanwhile is there any shortcut that reduce the time frame for doing all this on existing data. If anyone knows pls share. If this is the only go then do comment will ask to close the thread.
Click to expand...
Click to collapse
Nandroid backup?
Yes if you've one then you can definitely restore it to fix the issues.
Mr.Ak said:
Nandroid backup?
Yes if you've one then you can definitely restore it to fix the issues.
Click to expand...
Click to collapse
bro one more issue started yesterday. I thought to making battery full nil and charge to 100% may help.
Before without charging connected I was able to go in twrp but not now. if i remove charging its going to restart even recovery mode also. When I went to restore old backup in TWRP mobile is auto starting even when charger is connected. but if i dont do anything its staying fine in TWRP lock screen.
without charging connected i can go into fastboot n stay for as long as i want but comp is not detecting mobile even though developer option is ON.
Yesterday thought of restoring old backup which interrupted half within 1min and now if i start mobile while charging its getting struk at 1+1 welcome screen.
I am fully confused like anything..
is it not strange that so many people (including) have started facing this issue suddenly in the past two months?
I too am facing this issue. Has anyone managed to find a fix for the issue?
praveen4u13 said:
thanks pal. yes bootloader and all is unlocked. will see about this in coming weekend.
can't this problem be fixed if i just move back to old backup?
meanwhile is there any shortcut that reduce the time frame for doing all this on existing data. If anyone knows pls share. If this is the only go then do comment will ask to close the thread.
Click to expand...
Click to collapse
Did flashing cos13 fixed the issue? I'm also facing the same issue
piez97 said:
Did flashing cos13 fixed the issue? I'm also facing the same issue
Click to expand...
Click to collapse
flashing and all is time waste. If u r facing similar issue as quoted by me then its a battery problem. if your battery is not changed till now and old one around 2 years or more pls change it.
I wasted lot of time in flashing and lost all my data. I wish someone would have helped me with battery change suggestion. all the best..
praveen4u13 said:
flashing and all is time waste. If u r facing similar issue as quoted by me then its a battery problem. if your battery is not changed till now and old one around 2 years or more pls change it.
I wasted lot of time in flashing and lost all my data. I wish someone would have helped me with battery change suggestion. all the best..
Click to expand...
Click to collapse
But the sad truth is we can't get any original / as good as original replacement. Oneplus stopped production 2years ago. I did a quick google search and found out most of the batteries are ****. As you're name suggests, I think you're from India. Can you please inform me if you find any decent batteries? I will inform you if I find anything good.
Thx
piez97 said:
Did flashing cos13 fixed the issue? I'm also facing the same issue
Click to expand...
Click to collapse
piez97 said:
But the sad truth is we can't get any original / as good as original replacement. Oneplus stopped production 2years ago. I did a quick google search and found out most of the batteries are ****. As you're name suggests, I think you're from India. Can you please inform me if you find any decent batteries? I will inform you if I find anything good.
Thx
Click to expand...
Click to collapse
yes I am from India. I would suggest you first try with replacement battery as everyone sell replacement battery. you can find any of these in ebay. In India Oneplus is ready to arrange a original one costing Rs 1800. They asked me for a week time to arrange original battery. So its upto u to decide to take new one or replacement.
praveen4u13 said:
yes I am from India. I would suggest you first try with replacement battery as everyone sell replacement battery. you can find any of these in ebay. In India Oneplus is ready to arrange a original one costing Rs 1800. They asked me for a week time to arrange original battery. So its upto u to decide to take new one or replacement.
Click to expand...
Click to collapse
I contacted my nearest customer care. They said that they have to analyze the phone and it would take almost 15 days. Did you get a new battery?
praveen4u13 said:
bro one more issue started yesterday. I thought to making battery full nil and charge to 100% may help.
Before without charging connected I was able to go in twrp but not now. if i remove charging its going to restart even recovery mode also. When I went to restore old backup in TWRP mobile is auto starting even when charger is connected. but if i dont do anything its staying fine in TWRP lock screen.
without charging connected i can go into fastboot n stay for as long as i want but comp is not detecting mobile even though developer option is ON.
Yesterday thought of restoring old backup which interrupted half within 1min and now if i start mobile while charging its getting struk at 1+1 welcome screen.
I am fully confused like anything..
Click to expand...
Click to collapse
Same issue, start from 3 days ago...
Without charger or power bank i can't use phone [emoji19]
My phone is old around 2.5+ year
Sent from my A0001 using Tapatalk
Me too having the same issue. Seems like OnePlus one devices have some kind of kill switch to ruin it after 2.5 years. Quite a few number of people seems to have this issue all of a sudden.
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