Database Users

[Q] help me please!!!???

so a buddy of mine rooted his wifes eris, and sorta messed up the root, he can get to clockwork mod and all, BUT any rom he tries to flash will say error at line 9 or line 6 not enough space on device, aborting operation....
he also failed to make an nand back up so basically we are stuck in clockwork
someone help! how do we either fix this to flash a rom or unroot/return to stock this device??
we have tryed the RUU method but it doesnt reconize the drvice because we are in clock work
and we have try the pbm img but s=on so were locked out

If s=on then i dont think he got root

Cyostrife said:
If s=on then i dont think he got root
Click to expand...
Click to collapse
he followed the method on theunlockr.com
worked just fine for his eris, but his wifes is giving said errors...
with just bootloader and cwm avalible what can we do to fix this?

mytouchguy said:
he followed the method on theunlockr.com
worked just fine for his eris, but his wifes is giving said errors...
with just bootloader and cwm avalible what can we do to fix this?
Click to expand...
Click to collapse
How full is the battery? I get errors if I try to flash and the battery is ~30% or less.

lp4261 said:
How full is the battery? I get errors if I try to flash and the battery is ~30% or less.
Click to expand...
Click to collapse
not sure, i was doing a remote help, i do alot of rooting for tmo phones ive just never seen this error... i plan to go help him in person just trying to get some advice
will it still charge with no rom? if so ill have him charge it overnight

mytouchguy said:
not sure, i was doing a remote help, i do alot of rooting for tmo phones ive just never seen this error... i plan to go help him in person just trying to get some advice
will it still charge with no rom? if so ill have him charge it overnight
Click to expand...
Click to collapse
I would assume so, but I'm still a novice. I just noticed this from my own experience.

lp4261 said:
I would assume so, but I'm still a novice. I just noticed this from my own experience.
Click to expand...
Click to collapse
what type of errors have you seen?
his says not enough space on device... could this relate the cwm bricking devices?
more so is the device bricked at this point or are we still ok?

mytouchguy said:
what type of errors have you seen?
his says not enough space on device... could this relate the cwm bricking devices?
more so is the device bricked at this point or are we still ok?
Click to expand...
Click to collapse
if u can power the device on , i believe it aint bricked

Can he get to hboot and usb from there. if so let me know and also can he get to recovery...
Sent from my froshedyo using XDA App

mytouchguy said:
what type of errors have you seen?
his says not enough space on device... could this relate the cwm bricking devices?
more so is the device bricked at this point or are we still ok?
Click to expand...
Click to collapse
That sounds like the type of stuff i would get. that or a push file via adb thing. It doesn't sound like a clockwork bricking. The problem with CWM is that it doesn't have the verification step that amon-ra does. Are you flashing roms from these forums? I trust the devs here, but I don't think I would flash a rom that isn't from here w/o a recommendation from one of the devs. I would plug the phone in and let it go for a bit and try again after it has a charge.

lp4261 said:
I would assume so, but I'm still a novice. I just noticed this from my own experience.
Click to expand...
Click to collapse
tazzpatriot said:
if u can power the device on , i believe it aint bricked
Click to expand...
Click to collapse
yes we can power on we can use cwm mod hell we can place a pbmimg on the sd card, it just wont read it because s=on at the time
in doing a massive google search
any chance this would work
http://www.droidforums.net/forum/hacking-help/37717-unroot-unbrick-using-sbf-post-ikithme.html
if not anyone got any ideas?

3 more questions
a: is there a way to get s=off without android loaded, between just the bootloader and cwm avalible? this way we can hopefully just use the pbmimg
B: is there a way to replace cwm with amon ra in this current state to use flashback21? http://forum.xda-developers.com/showthread.php?t=792026
and this is a really crazy thought but can we take the backup we created tonight from his eris... both phones are EXACTLY alike, purchased at the same time and all...and use it to flash in cwm to recover the dead phone?

there is way to flash S=OFF through recovery. Flash the file from here..

In order to use a nandroid from a different phone you need to change a few things to make it work. I read it somewhere. If I find it ill let ya know
Sent from my KaosGingerbread using XDA App

CCCP4ever said:
there is way to flash S=OFF through recovery. Flash the file from here..
Click to expand...
Click to collapse
This is only supposed to work if you have bootloader version 1.49. If you're lucky like me and have 1.47 it won't work. That's according to bftbo. He's tried both.

lp4261 said:
This is only supposed to work if you have bootloader version 1.47. If you're lucky like me and have 1.49 it won't work. That's according to bftbo. He's tried both.
Click to expand...
Click to collapse
ill have this on standby, idk what bootloader he has we kinda gave up for the night

erismaster said:
In order to use a nandroid from a different phone you need to change a few things to make it work. I read it somewhere. If I find it ill let ya know
Sent from my KaosGingerbread using XDA App
Click to expand...
Click to collapse
awesome ill do a little looking myself and see, but thanks. figured it was a crazy but possible idea

mytouchguy said:
ill have this on standby, idk what bootloader he has we kinda gave up for the night
Click to expand...
Click to collapse
here's bftbo's answer to my question:
http://forum.xda-developers.com/showpost.php?p=10501766&postcount=69

within moments i found this...
anyone know how to achive this? both phones in this instance are the droid ERIS
http://androidforums.com/incredible...ansferring-nandroid-backup-another-phone.html

lp4261 said:
here's bftbo's answer to my question:
http://forum.xda-developers.com/showpost.php?p=10501766&postcount=69
Click to expand...
Click to collapse
any way to roll back the bootloader as he mentioned in the event that he has 1.49?
and this is a really stupid question , but im so brain fryed... how do we check his bootloader version?

[Q] CWM Recovery Errors

I understand that there are similar threads out there but I still can't seem to figure it out. I apologize ahead of time for any wrong terminology, I'm pretty new to all of this. To give a background on what happend, I started my day off by rooting my phone with the following link (I had tried a different method with visionary plus and terminal but it wouldn't work)
http://forum.xda-developers.com/showthread.php?t=858996
this method worked just fine and gave me s=off, currently what I have is as followed:
Glacier PVT ENG S-OFF
HBOOT-0.85.2007 (pd1510000)
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
After gaining my root I was excited to try and flash a new rom. I installed the clockwork rom manager from the market, flashed the recovery then backed up my current in case of future problems.
Next step for me was to flash a new rom. for this I followed
http://forum.xda-developers.com/showthread.php?t=1070444
everything seemed to be going fine, phone restarted and I sat waiting (since I read the first boot could take 10min or so) after at least an hour I began to worry. Nothing happened, just stayed on the mytouch 4g startup screen and never changed.
I rebooted into recovery to try again, I can get into my hboot and into clockwork Mod Recovery v3.0.2.4 just fine. but there are a whole bunch of errors I cant fix. When clockwork starts I get the errors
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
If I try to format anything (cache, system...) it will say
Formatting /cache... (or system depending on what I am trying)
Error formatting /cache! (or system)
If I try to restore to a previous time it will start to do the restore, it will first do the boot which goes fine, but when it tries to format the system during the restore it fails just like if trying to format it individually.
At this point I would just like to get my phone working, any help would be much appreciated. (please try and use details so I can follow... still trying to learn alot)

I hate to be the bring of bad news, and remember don't kill the messenger, but it sounds as if your phone is truly bricked. There have been several threads on this already. As i know you are aware of. And very few, if any, have recovered.
There is a thread Posted here that boils down to the fact if the VISIONary.apk & root.sh method do not work then you have a bad eMMC.
Since it appears your phone does have a bad eMMC, hope you have insurance on it.

neidlinger said:
hope you have insurance on it.
Click to expand...
Click to collapse
neidlinger- i happen to have bought the insurance for 6 bucks a month or whatever it was - they said it extends the mfr warranty another year and then it gives you drop-in-toilet etc insurance with around a 120$ deduc.
I'm with t-mobile and got the phone thru the mail. If I take this back to a local TMO store for warranty claim, there's no difference is there? (i.e. you dont have to follow the mail route just because that's how you got it originally)
also- would these cache mount or failed -pu errors, essentially beyond repair - are we getting these to be recognized as hardware failure (i.e. no deductabel and counted as a mfr defect) or are these coming up as TMO insisting on counting them as some user fault, requiring the deductable to be paid??

acsi007 said:
neidlinger- i happen to have bought the insurance for 6 bucks a month or whatever it was - they said it extends the mfr warranty another year and then it gives you drop-in-toilet etc insurance with around a 120$ deduc.
I'm with t-mobile and got the phone thru the mail. If I take this back to a local TMO store for warranty claim, there's no difference is there? (i.e. you dont have to follow the mail route just because that's how you got it originally)
Click to expand...
Click to collapse
9/10 times if you buy a phone through the mail you will have to exchange it through the mail they will not allow you to walk into a store and do the exchange. I ran into that with my blackberry 9700.
acsi007 said:
also- would these cache mount or failed -pu errors, essentially beyond repair - are we getting these to be recognized as hardware failure (i.e. no deductabel and counted as a mfr defect) or are these coming up as TMO insisting on counting them as some user fault, requiring the deductable to be paid??
Click to expand...
Click to collapse
nope there is not way around it. once the eMMC fails it's down for the count.

neidlinger said:
I hate to be the bring of bad news, and remember don't kill the messenger, but it sounds as if your phone is truly bricked. There have been several threads on this already. As i know you are aware of. And very few, if any, have recovered.
There is a thread Posted here that boils down to the fact if the VISIONary.apk & root.sh method do not work then you have a bad eMMC.
Since it appears your phone does have a bad eMMC, hope you have insurance on it.
Click to expand...
Click to collapse
Is there any way to tell if the eMMC is bad. the visionary install went fine, just using the terminal to do the sh root.sh command wouldnt work, it would just keep saying failed (function not implemented) which is why I switched to visionary and adb gfree method... which worked like a charm, not a single hickup with it. the problems didnt start coming until after the rom instillation didnt work

hiddentalnt said:
Is there any way to tell if the eMMC is bad. the visionary install went fine, just using the terminal to do the sh root.sh command wouldnt work, it would just keep saying failed (function not implemented) which is why I switched to visionary and adb gfree method... which worked like a charm, not a single hickup with it. the problems didnt start coming until after the rom instillation didnt work
Click to expand...
Click to collapse
i see you didn't read the thread i posted.
The link i posted is to a thread here @ XDA, called "Post your eMMC serial number". It has alot of information regarding this very subject, including how to tell if your eMMC is indeed a faulty one [ by serial number ].
it really doesn't matter when the problem happens. it just matters that it happened.
./gfree is basically forcing the rooting process to happen while the root.sh is asking for it to happen. If the root.sh process doesn't allow you to proceed, then you may have a faulty eMMC. you forced the phone to root and opened up a bee hive in the process.

yeah sorry, I posted and then was just reading that forum as you replied... sorry about that.

hiddentalnt said:
yeah sorry, I posted and then was just reading that forum as you replied... sorry about that.
Click to expand...
Click to collapse
no need to tell me your sorry, . If you want to make me mad tell me Popeye's Chicken is out of business. we all start out somewhere. Just be willing to read prior to doing anything or asking anything. Chances are there is an answer somewhere. Sometimes we like what we read and sometimes we don't either way it's out there.

Hiddentalnt, please post your eMMC serial. We need people who have recovery errors to post what serial they have so we can actually pinpoint the problem being the chip. Thanks. The instructions are posted in the thread neidlinger posted above. Thanks

xdviper said:
Hiddentalnt, please post your eMMC serial. We need people who have recovery errors to post what serial they have so we can actually pinpoint the problem being the chip. Thanks. The instructions are posted in the thread neidlinger posted above. Thanks
Click to expand...
Click to collapse
I just tried to run that command but nothing comes up after it. I dont know if im inputing it in wrong but im currently trying to figure it out... Ill post once I find it. if any advice on why after running the command it just repeats the line, then nothing let me know

hiddentalnt said:
I just tried to run that command but nothing comes up after it. I dont know if im inputing it in wrong but im currently trying to figure it out... Ill post once I find it. if any advice on why after running the command it just repeats the line, then nothing let me know
Click to expand...
Click to collapse
after you got ADB installed and you punch in adb devices does it give you a serial number?

hiddentalnt said:
I just tried to run that command but nothing comes up after it. I dont know if im inputing it in wrong but im currently trying to figure it out... Ill post once I find it. if any advice on why after running the command it just repeats the line, then nothing let me know
Click to expand...
Click to collapse
nevermind... just got it M4G2DE
so from what Im reading...theres no coming back from this, the chip is dead?

hiddentalnt said:
nevermind... just got it M4G2DE
so from what Im reading...theres no coming back from this, the chip is dead?
Click to expand...
Click to collapse
pretty much.
I do know one guy was able to via flashing an older recovery image via the hBoot, but you have to have the .85 engineering screen. Which you do not have.

neidlinger said:
pretty much.
I do know one guy was able to via flashing an older recovery image via the hBoot, but you have to have the .85 engineering screen. Which you do not have.
Click to expand...
Click to collapse
what is the .85 engineering screen, i do have hboot - 0.85.2007 but im assuing thats different.
So its time to call up TMO and have them send me out a new phone? do I need to unroot first so they dont find it?

hiddentalnt said:
what is the .85 engineering screen, i do have hboot - 0.85.2007 but im assuing thats different.
So its time to call up TMO and have them send me out a new phone? do I need to unroot first so they dont find it?
Click to expand...
Click to collapse
Well you need to flash the 2.5.x.x recovery image for the mytouch4g from the hBoot, then reboot then navigate to the recovery and pray that it works. If it loads you might be able to load a new ROM but i only know of one case where that worked.

neidlinger said:
Well you need to flash the 2.5.x.x recovery image for the mytouch4g from the hBoot, then reboot then navigate to the recovery and pray that it works. If it loads you might be able to load a new ROM but i only know of one case where that worked.
Click to expand...
Click to collapse
sorry for asking so many questions. but you really have been a great help. do you have any idea where i can find the 2.5.x.x recovery image, I've been trying to look but I cant find it, just didn't know if you already knew of a forum that had it.

hiddentalnt said:
sorry for asking so many questions. but you really have been a great help. do you have any idea where i can find the 2.5.x.x recovery image, I've been trying to look but I cant find it, just didn't know if you already knew of a forum that had it.
Click to expand...
Click to collapse
I've got it store on my Lunix computer at home. I do not have it on my phone or on my work computer.
sorry. I can post it later on tonight.

neidlinger said:
I've got it store on my Lunix computer at home. I do not have it on my phone or on my work computer.
sorry. I can post it later on tonight.
Click to expand...
Click to collapse
Thanks, I appreciate it. I'm off to class anyways so I have to put a pause on trying to fix it till then.

neidlinger said:
Well you need to flash the 2.5.x.x recovery image for the mytouch4g from the hBoot, then reboot then navigate to the recovery and pray that it works. If it loads you might be able to load a new ROM but i only know of one case where that worked.
Click to expand...
Click to collapse
I would be that ONE case where this option did work. And the difference I have seen between the first time when flashing CWM worked and the second time (when it DIDN'T work) is the COMMAND error. If your CWM says anything about COMMAND error then flashing the old CWM isn't gonna work.
Here is a link to a post I made with a download for the old CWM
http://forum.xda-developers.com/showthread.php?p=14069400#post14069400
have any questions PM me if needed. Hit the Thanks button to if any of us have helped you at all.
Good luck man, I have a 450 dollar batter charger right now, so you'll need it :/

dcwiker05 said:
I would be that ONE case where this option did work. And the difference I have seen between the first time when flashing CWM worked and the second time (when it DIDN'T work) is the COMMAND error. If your CWM says anything about COMMAND error then flashing the old CWM isn't gonna work.
Here is a link to a post I made with a download for the old CWM
http://forum.xda-developers.com/showthread.php?p=14069400#post14069400
have any questions PM me if needed. Hit the Thanks button to if any of us have helped you at all.
Good luck man, I have a 450 dollar batter charger right now, so you'll need it :/
Click to expand...
Click to collapse
I'm not sure I fully understand your directions in the other thread. So when i download the zip, i get inside it and go all the way to recoveries to get out one of the disc image files. which one do I want, there is a 2.5.1.3 and 2.5.1.4 and a 3.0.0.5 but I'm assuming thats not it... but once I get one of those I rename it recovery.img then i use abd to push it... what is the command to push it? and i have to be in hboot then fastboot to push it?

[Q] Bricked my G2 D800, can't access TWRP but can enter download mode (but rooted)

Tried following this guide but I'm still not sure how to enter fastboot mode.

chris9000 said:
Tried following this guide but I'm still not sure how to enter fastboot mode.
Click to expand...
Click to collapse
Just a little hint your phone is not bricked if you can enter download mode but how did it end up like that?

XDAcube said:
Just a little hint your phone is not bricked if you can enter download mode but how did it end up like that?
Click to expand...
Click to collapse
Rooted it, installed recovery, rebooted so I could enter recovery, found it kept bootlooping to logo. I thought wiping would solve everything, but nopes, I'm at square one now.
I'm somewhat new to this and could really use some advice.

Anyone know what's going on exactly? I've been staying up just to research an answer and would love a solution. I may be in serious trouble this week if my phone is inoperable this entire week.

chris9000 said:
Anyone know what's going on exactly? I've been staying up just to research an answer and would love a solution. I may be in serious trouble this week if my phone is inoperable this entire week.
Click to expand...
Click to collapse
Well try this http://www.droidviews.com/how-to-restore-lg-g2-to-stock-firmware/ it should work for your issues. good luck

vs995 stuck on verizon logo after starting step 3

i pressed step 3 and all the command windows closed and my v20 rebooted. However it is stuck on the verizon loading logo. Any one know how to fix?

jccspeed said:
i pressed step 3 and all the command windows closed and my v20 rebooted. However it is stuck on the verizon loading logo. Any one know how to fix?
Click to expand...
Click to collapse
You didn't read the guide.

me2151 said:
You didn't read the guide.
Click to expand...
Click to collapse
I don't get what I did wrong. And when I said the command windows closed I meant step3 ran through and when it finished it closed out all of the existing command prompts including the runmefirst prompt and then the V20 got stuck into the Verizon logo.

me2151 said:
You didn't read the guide.
Click to expand...
Click to collapse
I actually just browsed the guide so I could point him towards the part where you discuss flashing "boot2.img" and I didnt see it. Did you remove it?

jccspeed said:
I don't get what I did wrong. And when I said the command windows closed I meant step3 ran through and when it finished it closed out all of the existing command prompts including the runmefirst prompt and then the V20 got stuck into the Verizon logo.
Click to expand...
Click to collapse
See below.
bond32 said:
I actually just browsed the guide so I could point him towards the part where you discuss flashing "boot2.img" and I didnt see it. Did you remove it?
Click to expand...
Click to collapse
me2151 said:
5) During reboot you will get a Red Triangle with a "!" inside, this is normal (First boot after flashing SuperSu will show the Red triangle twice.Wait for system to boot (this will take awhile). It may appear like the system has frozen but it has not. JUST WAIT!
*****VERIZON USERS******
It has come to my attention that some users have encountered abnormally long first boot time(over 20 minutes before first time setup)
To resolve this issue:
Boot into bootloader by pulling the battery and reinserting it and holding VOL- and phugging in the phone. then typing:
Code:
fastboot flash boot boot2.img
fastboot reboot
**************
Click to expand...
Click to collapse
Wasn't removed

I swear I looked at that like 20 times. I'm getting too freaking old, sorry!

bond32 said:
I swear I looked at that like 20 times. I'm getting too freaking old, sorry!
Click to expand...
Click to collapse

me2151 said:
See below.
Wasn't removed
Click to expand...
Click to collapse
Well ive seen that but where would i type in this command. I also wasn't at the point where i flash supersu because it wouldnt boot to twrp

that command is from fastboot(bootloader)

jccspeed said:
Well ive seen that but where would i type in this command. I also wasn't at the point where i flash supersu because it wouldnt boot to twrp
Click to expand...
Click to collapse
and yes im sorta a noob (only rooted a g3 before) but what is and where would my "active adb directory be

me2151 said:
that command is from fastboot(bootloader)
Click to expand...
Click to collapse
sorry if i sound like an idiot but how do i type that into the bootloader

me2151 said:
See below.
Wasn't removed
Click to expand...
Click to collapse
i did this after trying root the second time. It said could not load boot2 and when i rebooted it it is still not booting up

jccspeed said:
and yes im sorta a noob (only rooted a g3 before) but what is and where would my "active adb directory be
Click to expand...
Click to collapse
Did you get it working? I asked the same thing.. Pm if do so you. Can walk my butt through it..please

d73jester said:
Did you get it working? I asked the same thing.. Pm if do so you. Can walk my butt through it..please
Click to expand...
Click to collapse
well i learned where the active adb directory is (C:\adb) and i moved everything there but my phone bootlooped on the same part. For some reason the people who know how to do this are being irritating and giving very vague answers. If you find out how to fix then pm me cuz im probably going to stop trying until a new method is released by a nicer dev

jccspeed said:
well i learned where the active adb directory is (C:\adb) and i moved everything there but my phone bootlooped on the same part. For some reason the people who know how to do this are being irritating and giving very vague answers. If you find out how to fix then pm me cuz im probably going to stop trying until a new method is released by a nicer dev
Click to expand...
Click to collapse
I got stuck on the 3rd step too man. I left it overnight hoping it would finally start up only to wake up and find it still vibrating. What I ended up doing was flashing the NRD 90M Modded not so stock ROM and was finally able to get my phone to boot up after 5min and it has been working great since. Heres the link. https://forum.xda-developers.com/v20/development/vs995-vzw-nrd90m-modded-notsostock-rom-t3525864

viper_1315 said:
I got stuck on the 3rd step too man. I left it overnight hoping it would finally start up only to wake up and find it still vibrating. What I ended up doing was flashing the NRD 90M Modded not so stock ROM and was finally able to get my phone to boot up after 5min and it has been working great since. Heres the link. https://forum.xda-developers.com/v20/development/vs995-vzw-nrd90m-modded-notsostock-rom-t3525864
Click to expand...
Click to collapse
how did you manage to flash it if it was stuck on the verizon logo?

jccspeed said:
well i learned where the active adb directory is (C:\adb) and i moved everything there but my phone bootlooped on the same part. For some reason the people who know how to do this are being irritating and giving very vague answers. If you find out how to fix then pm me cuz im probably going to stop trying until a new method is released by a nicer dev
Click to expand...
Click to collapse
I wasn't really being vague. I told you exactly what you needed to do. Another method isn't coming out any time soon. And the reason why I may not seem "Nice" is because people don't know how to read a thread through where stuff like this IS ALREADY ANSWERED MULTIPLE TIMES. If you don't even know how to input commands through fastboot(bootloader) you really should NOT have tried this. Thats why I stopped posting replies to you. Im sorry but just read the thread...

me2151 said:
I wasn't really being vague. I told you exactly what you needed to do. Another method isn't coming out any time soon. And the reason why I may not seem "Nice" is because people don't know how to read a thread through where stuff like this IS ALREADY ANSWERED MULTIPLE TIMES. If you don't even know how to input commands through fastboot(bootloader) you really should NOT have tried this. Thats why I stopped posting replies to you. Im sorry but just read the thread...
Click to expand...
Click to collapse
yea i know how to input bootloader commands now sorry about that i was being a little slow. I just wanna know if i could flash boot2 cuz on the op it only says to do that after it goes into twrp and i flash supersu then if it gets stuck in boot. Mine got stuck when it was rebooting before i could put the adb reboot recovery thing. So i just want to know if i can do the boot2 command before flashing supersu or if i can just reboot to recovery and flash a rom? Sorry for being rude I was just irritated in failing to root.

At this point you can just install roms. The boot2.img is mainly for first boot situations after the bootloader flashing.

jccspeed said:
how did you manage to flash it if it was stuck on the verizon logo?
Click to expand...
Click to collapse
What I did is went back to step 3, the step on how to install TWRP, put the rom on an sd card and then flash from there.

Encryption unsuccessful

Running on stock 6.0.1 MMB29M
locked bootloader
after recovery reset, the phone went into " Encryption unsuccessful" screen. Even after press reset or do factory reset in recovery again, the phone still bootloop into this page.
Could someone help?
Thanks.

laofan said:
Running on stock 6.0.1 MMB29M
locked bootloader
after recovery reset, the phone went into " Encryption unsuccessful" screen. Even after press reset or do factory reset in recovery again, the phone still bootloop into this page.
Could someone help?
Thanks.
Click to expand...
Click to collapse
Hello... Try sideloading a full OTA of your choice from here: https://developers.google.com/android/ota#angler
It needs to be newer than the installed version. Not sure it will solve your issue though. Maybe someone else will chime in with a better solution...
If nothing works, RMA your device.
Good luck...

Thanks for the advice.
I tried to manually flash OTA but it falied because of the locked bootloader.
I am not sure if there is anyone could point me to do it via ADB. I tried using ADB but the phone is not recognized by my computer yet.
5.1 said:
Hello... Try sideloading a full OTA of your choice from here: https://developers.google.com/android/ota#angler
It needs to be newer than the installed version. Not sure it will solve your issue though. Maybe someone else will chime in with a better solution...
If nothing works, RMA your device.
Good luck...
Click to expand...
Click to collapse

laofan said:
Thanks for the advice.
I tried to manually flash OTA but it falied because of the locked bootloader.
I am not sure if there is anyone could point me to do it via ADB. I tried using ADB but the phone is not recognized by my computer yet.
Click to expand...
Click to collapse
Hey...
Reboot into Bootloader. Select recovery mode with the volume rocker and press power.
Once you see the Android guy laying down with his belly opened, press power and tap volume up once.
On the menu select: apply update from ADB
From here type in a command prompt:
adb sideload "name of the full OTA zip you downloaded without quote"
Supposing you have prior knowledge with ADB. Let me know if something is not clear here...
Good luck...

I finally get ADB recognized Nexus 6p. But the ota stop flash at 46%. failed to read command: No error.
5.1 said:
Hey...
Reboot into Bootloader. Select recovery mode with the volume rocker and press power.
Once you see the Android guy laying down with his belly opened, press power and tap volume up once.
On the menu select: apply update from ADB
From here type in a command prompt:
adb sideload "name of the full OTA zip you downloaded without quote"
Supposing you have prior knowledge with ADB. Let me know if something is not clear here...
Good luck...
Click to expand...
Click to collapse

laofan said:
I finally get ADB recognized Nexus 6p. But the ota stop flash at 46%. failed to read command: No error.
Click to expand...
Click to collapse
You might have to RMA. I believe "no command" means the emmc has died.

dieselbuddeh said:
You might have to RMA. I believe "no command" means the emmc has died.
Click to expand...
Click to collapse
That is too bad. The warranty was expired in January.... It can't be RMA.... I wished there are some hopes there

laofan said:
That is too bad. The warranty was expired in January.... It can't be RMA.... I wished there are some hopes there
Click to expand...
Click to collapse
Hello...
Try sideloading the 7.1.2 OTA. Nothing to loose... If it fails yet, sorry, I don't know what else to do.
Good luck..

laofan said:
That is too bad. The warranty was expired in January.... It can't be RMA.... I wished there are some hopes there
Click to expand...
Click to collapse
If you bought the phone direct from Google, you will likely get a one time exception.

v12xke said:
If you bought the phone direct from Google, you will likely get a one time exception.
Click to expand...
Click to collapse
Yes, call them anyway if you purchased from Google. I was 5 months out of warranty for my 6p and they replaced it because I was having battery issues.

5.1 said:
Hello...
Try sideloading the 7.1.2 OTA. Nothing to loose... If it fails yet, sorry, I don't know what else to do.
Good luck..
Click to expand...
Click to collapse
I almost tried all the major OTA, none of them could pass 46%... oh well......
v12xke said:
If you bought the phone direct from Google, you will likely get a one time exception.
Click to expand...
Click to collapse
tommyg562000 said:
Yes, call them anyway if you purchased from Google. I was 5 months out of warranty for my 6p and they replaced it because I was having battery issues.
Click to expand...
Click to collapse
It is not from google. And the warranty ended in January... I am fxxked.....

Probably so. There is one guy who found a 6P with a shattered screen for sale and paid a local repair shop to have the motherboard swapped out. Claims it cost him less than USD $100 but he is in South Korea. You're probably better off cutting your losses and finding another phone... after Huawei tells you NO three times.

v12xke said:
Probably so. There is one guy who found a 6P with a shattered screen for sale and paid a local repair shop to have the motherboard swapped out. Claims it cost him less than USD $100 but he is in South Korea. You're probably better off cutting your losses and finding another phone... after Huawei tells you NO three times.
Click to expand...
Click to collapse
posted it on craigslist now.
( I noticed that you are in the Woodlands area. I missed the time when I am in Houston. One of the best memories)

just a follow-up to somebody might see encounter the same thing. I was not able to fix the phone.
With a locked bootloader and "encryption unsuccessful" page, you might try warranty first. If that does not work, you might want to take rescue OTA from google and flash it in recovery via " install update via ADB".
Please be aware that rescue OTA is different from system image and should be flash via ADB in recovery.
Good luck.

laofan said:
just a follow-up to somebody might see encounter the same thing. I was not able to fix the phone.
With a locked bootloader and "encryption unsuccessful" page, you might try warranty first. If that does not work, you might want to take rescue OTA from google and flash it in recovery via " install update via ADB".
Please be aware that rescue OTA is different from system image and should be flash via ADB in recovery.
Good luck.
Click to expand...
Click to collapse
Hello,
What rescue OTA? Something different than the usual OTA you would sideload with ADB?
Cheers...

5.1 said:
Hello,
What rescue OTA? Something different than the usual OTA you would sideload with ADB?
Cheers...
Click to expand...
Click to collapse
Here are Rescue OTA. One would need to flash it with ADB in recovery. https://developers.google.com/android/ota
The following one is firmware/factory image. One would need to flash it with fastboot while in bootloader mode : https://developers.google.com/android/images
Use the correct zip file according to your flashing mode ( recovery or bootloader)

laofan said:
Here are Rescue OTA. One would need to flash it with ADB in recovery. https://developers.google.com/android/ota
The following one is firmware/factory image. One would need to flash it with fastboot while in bootloader mode : https://developers.google.com/android/images
Use the correct zip file according to your flashing mode ( recovery or bootloader)
Click to expand...
Click to collapse
Hello,
I see nothing different than hmm an OTA here. I thought that was a "special" OTA, but no.
Not sure why it's called rescue OTA, lol.
Thanks for the links, but i know exactly what an OTA and a factory image are. :good:
Thanks...

Hello!
I have the same "Encryption unsuccessful" issue. It happened many times recently. First I replaced the battery, because it produced early sudden shutdown at 30-40%, and could run only for a few hours from 100% to 40%.
The new battery is enough for 30-40 hours as I use it, and can operate the phone down to 1-2% before shutting down.
But if I have to restart the phone, the encryption unsuccessful problem still comes up randomly after battery replacement. I can restart several times without problem, then randomly just fails. Mostly after software updates I guess... I have stock firmware, stock rom, etc. the only thing was made that I have installed TWRP, and wiped user data. Hope that helps. Can it be the defect of the emmc ? If so, how shall I diagnose it?
I'm very newbie android user, I changed from Windows Phone ( ) only a few months ago...
The question is what could cause the Encryption unsuccessful error? It's interesting, that if I enter any random numbers as unlock code, the phone tells that it appears to be valid, but unfortunately cannot decrypt data.
So I would like only to disable forced encryption, maybe that helps. Could someone point me to the right direction about what exactly should I do? Is it enough to flash a modded kernel to disable encryption? I don't want to root, or experiment with custom roms and I would stick to the factory firmware as much as I can, but without encryption of corse...
thanks!

fredmoro said:
Hello!
I have the same "Encryption unsuccessful" issue. It happened many times recently. First I replaced the battery, because it produced early sudden shutdown at 30-40%, and could run only for a few hours from 100% to 40%.
The new battery is enough for 30-40 hours as I use it, and can operate the phone down to 1-2% before shutting down.
But if I have to restart the phone, the encryption unsuccessful problem still comes up randomly after battery replacement. I can restart several times without problem, then randomly just fails. Mostly after software updates I guess... I have stock firmware, stock rom, etc. the only thing was made that I have installed TWRP, and wiped user data. Hope that helps. Can it be the defect of the emmc ? If so, how shall I diagnose it?
I'm very newbie android user, I changed from Windows Phone ( ) only a few months ago...
The question is what could cause the Encryption unsuccessful error? It's interesting, that if I enter any random numbers as unlock code, the phone tells that it appears to be valid, but unfortunately cannot decrypt data.
So I would like only to disable forced encryption, maybe that helps. Could someone point me to the right direction about what exactly should I do? Is it enough to flash a modded kernel to disable encryption? I don't want to root, or experiment with custom roms and I would stick to the factory firmware as much as I can, but without encryption of corse...
thanks!
Click to expand...
Click to collapse
Same. The data decryption being unsuccessful happened to me as well on stock oreo 8.1.0. not rooted
Anyone know how to fix it and doesn't happen again?
Thanks