Related
So I've had my nexus 5 for the past couple months and was recently prompted to download the latest update, 4.4.3. The thing is, when the update is finished downloading and I'm told to reboot my phone to install it, I get an error message- the green android dude is on its back with a red exclamation point above it. I've reset my phone and attempted to reinstall the update, but no luck. Anyone else have this problem? How do I get around it and download the update?
ksalam said:
So I've had my nexus 5 for the past couple months and was recently prompted to download the latest update, 4.4.3. The thing is, when the update is finished downloading and I'm told to reboot my phone to install it, I get an error message- the green android dude is on its back with a red exclamation point above it. I've reset my phone and attempted to reinstall the update, but no luck. Anyone else have this problem? How do I get around it and download the update?
Click to expand...
Click to collapse
I had the same problem but i was rooted so i thought that rooting messed something up,so i unlocked the bootloader and installed manually.But if you're running full stock then i don't know what causes the problem.
PS:I'm sorry if my english is not perfect,i hope you understand what i'm trying to say.
If you're rooted with a custom recovery, the OTA will not work.
See this OTA help thread...
http://forum.xda-developers.com/showthread.php?t=2523217
Or you can flash 4.4.4 with fastboot and not worry about the OTA....guide for that here....
http://forum.xda-developers.com/showthread.php?t=2513701
Good luck!
Benthemad said:
I had the same problem but i was rooted so i thought that rooting messed something up,so i unlocked the bootloader and installed manually.But if you're running full stock then i don't know what causes the problem.
PS:I'm sorry if my english is not perfect,i hope you understand what i'm trying to say.
Click to expand...
Click to collapse
Guess I should've mentioned I rooted my device right out the box- I had a feeling that had something to do with it, which is why I reset my phone.I'll give your suggestion a shot.
Benthemad said:
I had the same problem but i was rooted so i thought that rooting messed something up,so i unlocked the bootloader and installed manually.But if you're running full stock then i don't know what causes the problem.
PS:I'm sorry if my english is not perfect,i hope you understand what i'm trying to say.
Click to expand...
Click to collapse
KJ said:
If you're rooted with a custom recovery, the OTA will not work.
See this OTA help thread...
http://forum.xda-developers.com/showthread.php?t=2523217
Or you can flash 4.4.4 with fastboot and not worry about the OTA....guide for that here....
http://forum.xda-developers.com/showthread.php?t=2513701
Good luck!
Click to expand...
Click to collapse
thanks!
OP @ksalam
If you tried the search you would have found something by yourself easily. Thats the suggestion to each one of us in the FORUM rules as well.
Please start searching now instead of making new ones and clustering.
Thanks
THREAD CLOSED
I am using TPRW recovery 2.7.1.0 to sideload the latest cyanogenmod cm-11.0-XNPh25R. I use the apply update option and sideload it from the internal storage. The error I am getting is E:footer is wrong E:signature verification failed. Can someone kind enough to help me? Please.. Thanks.
peacewar said:
I am using TPRW recovery 2.7.1.0 to sideload the latest cyanogenmod cm-11.0-XNPh25R. I use the apply update option and sideload it from the internal storage. The error I am getting is E:footer is wrong E:signature verification failed. Can someone kind enough to help me? Please.. Thanks.
Click to expand...
Click to collapse
Am I not supposed to sideload a rom?
peacewar said:
Am I not supposed to sideload a rom?
Click to expand...
Click to collapse
Whatever, the problem is resolved. I just fastboosted the phone to flash the latest version of cyanogenmod. There was no point rooting the phone anyway and It was a bad part of me to try to flash it via recovery mode.
can you tell me how to do this?
peacewar said:
Whatever, the problem is resolved. I just fastboosted the phone to flash the latest version of cyanogenmod. There was no point rooting the phone anyway and It was a bad part of me to try to flash it via recovery mode.
Click to expand...
Click to collapse
can you tell me how to do this?
i have the same problem
xravivx77 said:
can you tell me how to do this?
i have the same problem
Click to expand...
Click to collapse
You need to be specific about what your problem is.
Transmitted via Bacon
signature error
timmaaa said:
You need to be specific about what your problem is.
Transmitted via Bacon
Click to expand...
Click to collapse
now i have XNPh25R and when i try to manual update i got signature error.
xravivx said:
now i have XNPh25R and when i try to manual update i got signature error.
Click to expand...
Click to collapse
Come on, details, details, details.
Transmitted via Bacon
timmaaa said:
Come on, details, details, details.
Transmitted via Bacon
Click to expand...
Click to collapse
i have oneplus one that i bought to months ago from pandawill and since i got it i never get updates for him.
i try to check for update in the phone but it say i dont have any.
i try to manual update but got error : Signature verification failed
i really need your help to update my phone because it got a loot of problems in the screentouch and battery.
xravivx said:
i have oneplus one that i bought to months ago from pandawill and since i got it i never get updates for him.
i try to check for update in the phone but it say i dont have any.
i try to manual update but got error : Signature verification failed
i really need your help to update my phone because it got a loot of problems in the screentouch and battery.
Click to expand...
Click to collapse
The update is failing for a reason. What is your current version? What version is the update you're applying? Do you have any modifications to your current setup at all?
Transmitted via Bacon
timmaaa said:
The update is failing for a reason. What is your current version? What version is the update you're applying? Do you have any modifications to your current setup at all?
Transmitted via Bacon
Click to expand...
Click to collapse
i dont know this is stay like i got it 2 month ago .
im pretty sure that when i order it from pandawill they do root because they got the phone with oppo and change it to cm11 before the shipping.
cyanogenMod - 11.0-xnph25r
android - 4.4.2
build num - kvt49l
xravivx said:
i dont know this is stay like i got it 2 month ago .
im pretty sure that when i order it from pandawill they do root because they got the phone with oppo and change it to cm11 before the shipping.
cyanogenMod - 11.0-xnph25r
android - 4.4.2
build num - kvt49l
Click to expand...
Click to collapse
I think the best idea for you is to start from scratch. Unlock the bootloader (if it isn't already unlocked), install TWRP recovery, then install Calkulin's stock rooted 38R ROM. From there you should have no problems receiving further updates.
Transmitted via Bacon
timmaaa said:
I think the best idea for you is to start from scratch. Unlock the bootloader (if it isn't already unlocked), install TWRP recovery, then install Calkulin's stock rooted 38R ROM. From there you should have no problems receiving further updates.
Transmitted via Bacon
Click to expand...
Click to collapse
when you say that it sound easy
do you have GUIDE for me?
xravivx said:
when you say that it sound easy
do you have GUIDE for me?
Click to expand...
Click to collapse
Yep, I have a guide thread, the link is in my signature.
Transmitted via Bacon
timmaaa said:
Yep, I have a guide thread, the link is in my signature.
Transmitted via Bacon
Click to expand...
Click to collapse
can you tell me which step i need to do?
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
xravivx77 said:
can you tell me which step i need to do?
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Click to expand...
Click to collapse
Steps 1, 2, 3, and 5, in that order.
Transmitted via Bacon
normal people and incorrect e-footer
Hi guys. I'm trying to flash the rom on a galaxy S4 to get rid of bloatware and free up memory. It's been a bit of a learning curve. I softbricked the machine and rescued it with odin but of course that is a stock rom and not what I want. EVERY CUSTOM ROM I HAVE TRIED ABORTS INSTALL DUE TO FAILED SIGNATURE VERIFICATION. incorrect e-footer or whatever. Does anybody KNOW how this is caused? Why are files not being copied bit for bit?
I want to say first that I have done a fairly thorough search of your archives to no avail. That is because most related threads are *****ing about the threads or the personalities involved along with mixtures of real and perceived breaches of this sites code of conduct and etiquette in general. I am not interested in any of that. Neither do I want to hear from the guy who danced widdershins round a cauldron waving his phone in the air telling me it fixed it for him. Please, can somebody that knows reply? Once I know the why I hope to fix it with a binary file editor. If somebody knows the why and the "how to fix" even better.
many thanks
Warwick
warwick512 said:
Hi guys. I'm trying to flash the rom on a galaxy S4 to get rid of bloatware and free up memory. It's been a bit of a learning curve. I softbricked the machine and rescued it with odin but of course that is a stock rom and not what I want. EVERY CUSTOM ROM I HAVE TRIED ABORTS INSTALL DUE TO FAILED SIGNATURE VERIFICATION. incorrect e-footer or whatever. Does anybody KNOW how this is caused? Why are files not being copied bit for bit?
I want to say first that I have done a fairly thorough search of your archives to no avail. That is because most related threads are *****ing about the threads or the personalities involved along with mixtures of real and perceived breaches of this sites code of conduct and etiquette in general. I am not interested in any of that. Neither do I want to hear from the guy who danced widdershins round a cauldron waving his phone in the air telling me it fixed it for him. Please, can somebody that knows reply? Once I know the why I hope to fix it with a binary file editor. If somebody knows the why and the "how to fix" even better.
many thanks
Warwick
Click to expand...
Click to collapse
You're in the wrong section, this is the OnePlus One section. You need to find the S4 section and ask there.
Heisenberg said:
You're in the wrong section, this is the OnePlus One section. You need to find the S4 section and ask there.
Click to expand...
Click to collapse
This is hopeless. My comments about moderation have met more moderation. Apparently this is the type of site that likes to flood its own archives with spam. goog on ya Anyways there seems to be little or no evidence that the verification problem is device specific. quite the opposite in fact. Maybe somebody that KNOWS will respond. i'll give it a week and see
cheers
warwick512 said:
This is hopeless. My comments about moderation have met more moderation. Apparently this is the type of site that likes to flood its own archives with spam. goog on ya Anyways there seems to be little or no evidence that the verification problem is device specific. quite the opposite in fact. Maybe somebody that KNOWS will respond. i'll give it a week and see
cheers
Click to expand...
Click to collapse
We have device sections for a reason. Each device has its own quirks, requirements, and problems. It's important for you to post in the right place because then you'll be able to get assistance from people who are familiar with your device and those quirks, requirements, and problems that come with it. There's Q&A section for your phone, that's where you need to be addressing the problem you're having. I'm not moderating you, I'm trying to help you get the help you need. Posting in the wrong device section isn't going to achieve that. If you drive a Ford you wouldn't post in a VW forum for help, the same logic applies here.
I want to flash my Cricket Moto G (xt1045) 4.4.4 to the retail 4.4.4 version for a few reasons. Mainly to get access to tethering and the chance that I will be able to update to Lollipop since my hope of cricket releasing the update is fading.
I've been searching around and cannot find a definite answer to this. Lots of people say it should work but I have yet to find anyone who successfully did so. Some say to flash all files but the bootloader and it should be good while others say being the official Motorola firmware everything will flash without a problem.
Has anyone took the plunge and tried it? I would, but I really don't want to be stuck with my Lumia 520 backup phone if I screw something up. Thanks!
macgi77 said:
I want to flash my Cricket Moto G (xt1045) 4.4.4 to the retail 4.4.4 version for a few reasons. Mainly to get access to tethering and the chance that I will be able to update to Lollipop since my hope of cricket releasing the update is fading.
I've been searching around and cannot find a definite answer to this. Lots of people say it should work but I have yet to find anyone who successfully did so. Some say to flash all files but the bootloader and it should be good while others say being the official Motorola firmware everything will flash without a problem.
Has anyone took the plunge and tried it? I would, but I really don't want to be stuck with my Lumia 520 backup phone if I screw something up. Thanks!
Click to expand...
Click to collapse
Anyone? I found a link with instructions but I can't post it until I have 10 posts. If anyone wants to try it, search for "viraj's flash stock rom lock bootloader moto g"
macgi77 said:
Anyone? I found a link with instructions but I can't post it until I have 10 posts. If anyone wants to try it, search for "viraj's flash stock rom lock bootloader moto g"
Click to expand...
Click to collapse
http://dev-viraj.blogspot.in/2015/01/flash-stock-rom-firmware-lock.html
Is that the page? His instructions and ROM download seem to be for a XT1068, not a XT1045. Did you find the ROM files for a 1045 somewhere? I'd like to get access to wifi tethering, too...
Yes, that is the page. I'm assuming the software install would be the same for all models in the Moto G group. The ROM files are located in a thread on here titled "Moto G 4G/LTE Stock Firmware (XT1039/40/42/45)"
Would post a link, but I'm still not allowed.
macgi77 said:
Yes, that is the page. I'm assuming the software install would be the same for all models in the Moto G group. The ROM files are located in a thread on here titled "Moto G 4G/LTE Stock Firmware (XT1039/40/42/45)"
Would post a link, but I'm still not allowed.
Click to expand...
Click to collapse
Link for those looking for it.
Thanks for the link. Maybe I will give this a try, I'm buying an android stereo for my car and need wifi tethering to run the GPS.
If you wind up trying it before I do, let us know! This would theoretically only update the ROM, we'd still be stuck with a locked bootloader, right? If we could find a 4.4.2 ROM, then the Sunshine S-off unlock would work, and we'd be set.
RonnieTheBear said:
Link for those looking for it.
Thanks for the link. Maybe I will give this a try, I'm buying an android stereo for my car and need wifi tethering to run the GPS.
If you wind up trying it before I do, let us know! This would theoretically only update the ROM, we'd still be stuck with a locked bootloader, right? If we could find a 4.4.2 ROM, then the Sunshine S-off unlock would work, and we'd be set.
Click to expand...
Click to collapse
No problem. I will report back if I try, you do the same if you beat me to it! Yes, the bootloader would still be locked, but the software should install since it is an official Motorola signed software. I think I recall reading somewhere that flashing to 4.4.2 would not allow unlocking through sunshine though.
macgi77 said:
No problem. I will report back if I try, you do the same if you beat me to it! Yes, the bootloader would still be locked, but the software should install since it is an official Motorola signed software. I think I recall reading somewhere that flashing to 4.4.2 would not allow unlocking through sunshine though.
Click to expand...
Click to collapse
macgi , I gave this a try last night and the results were extremely not good. Wasn't able to flash the retail firmware, got a bunch of "prevalidation flash failed" on some items, but not others, and then it wouldn't boot. Tried to reflash the cricket firmware to revert back, and got the same prevalidation error for the boot image and the partition gpt.bat file, and now I can't get past the fastboot screen.
RonnieTheBear said:
macgi , I gave this a try last night and the results were extremely not good. Wasn't able to flash the retail firmware, got a bunch of "prevalidation flash failed" on some items, but not others, and then it wouldn't boot. Tried to reflash the cricket firmware to revert back, and got the same prevalidation error for the boot image and the partition gpt.bat file, and now I can't get past the fastboot screen.
Click to expand...
Click to collapse
That sucks. That was the only thing keeping me from trying, the process of fixing it if something screwed up. Hopefully someone has an idea how to fix it since I'm not quite and expert in recoveries.
Thanks for reporting back though!
macgi77 said:
That sucks. That was the only thing keeping me from trying, the process of fixing it if something screwed up. Hopefully someone has an idea how to fix it since I'm not quite and expert in recoveries.
Thanks for reporting back though!
Click to expand...
Click to collapse
Yeah, no problem - it's possible I messed something up in the flashing operation, but I thought you'd want to know.
RonnieTheBear said:
Yeah, no problem - it's possible I messed something up in the flashing operation, but I thought you'd want to know.
Click to expand...
Click to collapse
I'm assuming you tried using the link above? Or did you try flashing each individual file and skipping the bootloader file which was talked about in the firmware thread? (I believe it was around pages 20-30 if I recall)
Found it
@JoeSyr, maybe I'm missing something here specific to Moto G LTE, but flashing a firmware image does not require an unlocked Bootloader. I would do it manually, skip most of the steps, and only flash the system.img initially.
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
The only way you can get into serious trouble would by flashing the motoboot.img (Bootloader) and phone no longer loads fastboot mode. But even then, is there not a hardbrick mbm-ci recovery option for Moto G 4G
Click to expand...
Click to collapse
macgi77 said:
I'm assuming you tried using the link above? Or did you try flashing each individual file and skipping the bootloader file which was talked about in the firmware thread? (I believe it was around pages 20-30 if I recall)
Found it
Click to expand...
Click to collapse
I tried running the ROM Install.bat file the guy put together in the first page you/I linked to, which did attempt to flash the bootloader. It sounds like this person you're quoting is saying the flash should be operational even just flashing those three chunks of the system image file? I think those files wrote okay, but it still didn't boot. Problem might be with this other partition file i mentioned.
RonnieTheBear said:
I tried running the ROM Install.bat file the guy put together in the first page you/I linked to, which did attempt to flash the bootloader. It sounds like this person you're quoting is saying the flash should be operational even just flashing those three chunks of the system image file? I think those files wrote okay, but it still didn't boot. Problem might be with this other partition file i mentioned.
Click to expand...
Click to collapse
That's what it sounds like. Any luck restoring the phone yet?
no, haven't really gotten a chance to mess with it, yet. I popped my sim card into an old samsung galaxy Blaze I had laying around as a backup, and I've been getting by with that for the time being. I think I've still got to figure out what the next thing I should try is. Might try asking around in some more of the subforums, here.
RonnieTheBear said:
no, haven't really gotten a chance to mess with it, yet. I popped my sim card into an old samsung galaxy Blaze I had laying around as a backup, and I've been getting by with that for the time being. I think I've still got to figure out what the next thing I should try is. Might try asking around in some more of the subforums, here.
Click to expand...
Click to collapse
Good luck, let us know how you make out.
RonnieTheBear said:
no, haven't really gotten a chance to mess with it, yet. I popped my sim card into an old samsung galaxy Blaze I had laying around as a backup, and I've been getting by with that for the time being. I think I've still got to figure out what the next thing I should try is. Might try asking around in some more of the subforums, here.
Click to expand...
Click to collapse
Any update?
macgi77 said:
Any update?
Click to expand...
Click to collapse
I tried flashing with some more tools, different firmwares, and different combinations of commands, no luck.
I found a guy in the stock firmware thread that had the exact same problem as me, and has the same cid as my phone, cid 10, which no one else seems to have. They think it might be why the preflash validation failed.
Other users suggested that if a cricket lollipop firmware image is developed at some point in the future, that would be able to flash without error. I reached out to the user to see if he ever resolved it, but didn't get a response.
Anyway, the sense that I got is that my problems were because my cid didn't match. Is yours cid 10 as well? you can check from adb. If it's not, you might be fine attempting it.
It's been a while since I checked, but I believe it is cid 10 as well. Now just hoping cricket releases Lollipop soon.....
The lollipop release for the retail (non carrier) version just came out OTA yesterday, apparently, so hopefully Cricket is not too far behind...Though it will probably take a while to go from an OTA update to a downloadable firmware image.
I contacted Motorola tech support today, they said they would replace the phone for $75 + taxes (flashing firmware via adb fastboot voids the warranty, of course), and told me it wouldn't have the Cricket firmware on it, so worst case, i would be gaining tethering ability, best case, they might send me a variant (xt1039?) that is capable of being rooted and installing a custom ROM in addition to tether. I'll probably take this option if I'm not able to get it working once the lollipop xt1045 firmware file shows up.
That's not a bad deal. Hopefully you can get it working when lollipop comes out though. Thanks for the update!
Hey guys,
i wanted to update my OPO with the last incremental update, but when i press update on the phone it restarts into TWRP and does nothing.
If i try to flash it from TWRP it gives me this error... (its the last TWRP).
What can i do?
Thanks guys
byte37 said:
Hey guys,
i wanted to update my OPO with the last incremental update, but when i press update on the phone it restarts into TWRP and does nothing.
If i try to flash it from TWRP it gives me this error... (its the last TWRP).
What can i do?
Thanks guys
Click to expand...
Click to collapse
First, you posted in the wrong section! This section is for development projects.
Also, have you installed a different version of CM12s? The zip is not flashing because it sees a modification to the firmware you're running, or it's a bad download .
Qrze said:
First, you posted in the wrong section! This section is for development projects.
Also, have you installed a different version of CM12s? The zip is not flashing because it sees a modification to the firmware you're running, or it's a bad download .
Click to expand...
Click to collapse
Damn, sorry about that, btw nope, a month ago i rooted the phone and installed TWRP and so wiped all, i also saw that it sees i have 4.4.2 but cant understand why...
PS. i cant change the section right?
byte37 said:
Damn, sorry about that, btw nope, a month ago i rooted the phone and installed TWRP and so wiped all, i also saw that it sees i have 4.4.2 but cant understand why...
PS. i cant change the section right?
Click to expand...
Click to collapse
Help is on the way, don't worry about the thread moving .
Can you screenshot your Settings->About Phone
Qrze said:
Help is on the way, don't worry about the thread moving .
Can you screenshot your Settings->About Phone
Click to expand...
Click to collapse
Thanks mate btw here it is
byte37 said:
Thanks mate btw here it is
Click to expand...
Click to collapse
Here try this, flash cyangen's recovery and try updating again. I don't know if that will do anything but it's worth a try!
It was told a zillion times. Either cyanogen recovery or download the full rom update instead of the delta OTA (full can be flashed via TWRP).
Look around the oneplus forums, I had the same problem. I managed to find the file and flash it with twrp without having to do the whole rom. The battery got better along with touch screen fixes
Sent from my A0001 using XDA Free mobile app
Done, thanks guys!
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