Related
I know there have been similar threads, and I'm sorry that I'm raising another one. But reading to all those old topics didn't help me.
It's a friend's i9020T, bought in the US, so returning it back would be a real problem. He never unlocked bootloader, never applied any custom ROMs or Recovery, always updated it over OTA, and sometime in November, after reboots, phone started to hang on Google logo. Usually, it helped to remove the battery and wait some time, but it doesn't any more. We tried to remove it for a full day, didn't helped.
I tried going into recovery and doing full wipe and cache wipe - didn't help
I tried to unlock the bootloader, can select 'Yes', apply it via Power button, but the phone hangs.
If I want to flash anything with fastboot (boot, system img), it complains about locked bootloader
I tried Odin as well, but can't trick the phone into download mode with both volume up and down, again reports to unlock the bootloader
Is there any way to and how to fix this? I cannot transfer anything to internal memory, have stock recovery?
Thanks a lot to all of those who are willing to help, and I've really want to somehow fix the phone, because I don't have here in Serbia where to repair it. Several mobile providers only imported i9023, so they can't fix i9020T
I'm having the exact same problem with a GT-i9020 so would be interested in any help on this!
May need to format phone. Basically reflash latest update via boot loader. Wipe system to factory. And wipe sd
Sent from my Full Android on Crespo using Tapatalk
RANDYRKELLY said:
May need to format phone. Basically reflash latest update via boot loader. Wipe system to factory. And wipe sd
Sent from my Full Android on Crespo using Tapatalk
Click to expand...
Click to collapse
but I downloaded 2.3.6 stock from here, unpacked in the same folder where adb and fastboot are, and tried to do fastboot flash boot boot.img and so, and didn't work, was bugging me that bootloader isn't unlock
Highl1 said:
but I downloaded 2.3.6 stock from here, unpacked in the same folder where adb and fastboot are, and tried to do fastboot flash boot boot.img and so, and didn't work, was bugging me that bootloader isn't unlock
Click to expand...
Click to collapse
That's the problem dude u don't unpack it. U need to leave as a update zip. Look on xda for the stock 4.0.3 update zip or wait till I provide link. U go thru stock recovery if unrooted, and flash with it. To unlock boot loader u need to be in fastboot and type fastboot oem unlock. But u wait first. Lets get it booted. I'll find link.
Sent from my Full Android on Crespo using Tapatalk
Read here
http://www.androidcentral.com/how-manually-update-your-gsm-nexus-s-ice-cream-sandwich
Sent from my Full Android on Crespo using Tapatalk
RANDYRKELLY said:
That's the problem dude u don't unpack it. U need to leave as a update zip. Look on xda for the stock 4.0.3 update zip or wait till I provide link. U go thru stock recovery if unrooted, and flash with it. To unlock boot loader u need to be in fastboot and type fastboot oem unlock. But u wait first. Lets get it booted. I'll find link.
Sent from my Full Android on Crespo using Tapatalk
Click to expand...
Click to collapse
I'll wait for your link and instructions, it's obvious that I am doing something wrong
Thanks mate!
RANDYRKELLY said:
Read here
http://www.androidcentral.com/how-manually-update-your-gsm-nexus-s-ice-cream-sandwich
Sent from my Full Android on Crespo using Tapatalk
Click to expand...
Click to collapse
But I have stock recovery and can't copy anything to internal memory, since my phone doesn't boot
Highl1 said:
I know there have been similar threads, and I'm sorry that I'm raising another one. But reading to all those old topics didn't help me.
It's a friend's i9020T, bought in the US, so returning it back would be a real problem. He never unlocked bootloader, never applied any custom ROMs or Recovery, always updated it over OTA, and sometime in November, after reboots, phone started to hang on Google logo. Usually, it helped to remove the battery and wait some time, but it doesn't any more. We tried to remove it for a full day, didn't helped.
I tried going into recovery and doing full wipe and cache wipe - didn't help
I tried to unlock the bootloader, can select 'Yes', apply it via Power button, but the phone hangs.
If I want to flash anything with fastboot (boot, system img), it complains about locked bootloader
I tried Odin as well, but can't trick the phone into download mode with both volume up and down, again reports to unlock the bootloader
Is there any way to and how to fix this? I cannot transfer anything to internal memory, have stock recovery?
Thanks a lot to all of those who are willing to help, and I've really want to somehow fix the phone, because I don't have here in Serbia where to repair it. Several mobile providers only imported i9023, so they can't fix i9020T
Click to expand...
Click to collapse
First download this : http://www.4shared.com/zip/2L09-JyW/Root_Nexus_S.html
Just unpack , connect your device and click run.bat - that will root your phone and installed new ClockWordMod Recovery
After that you need : remove install-recovery.sh just in .....
run in windows-> Start->at the search bar write cmd and navigate into your android sdk is installed
For me :
C:/"Programs and Files (x86)"/Android/android-sdk/tools/>adb shell
# rm /system/etc/install-recovery.sh
#exit
or with Root Explorer into system/etc/install-recovery.sh just renam it (ex. : .sh.old)
surdu_petru said:
First download this : http://www.4shared.com/zip/2L09-JyW/Root_Nexus_S.html
Just unpack , connect your device and click run.bat - that will root your phone and installed new ClockWordMod Recovery
After that you need : remove install-recovery.sh just in .....
run in windows-> Start->at the search bar write cmd and navigate into your android sdk is installed
For me :
C:/"Programs and Files (x86)"/Android/android-sdk/tools/>adb shell
# rm /system/etc/install-recovery.sh
#exit
or with Root Explorer into system/etc/install-recovery.sh just renam it (ex. : .sh.old)
Click to expand...
Click to collapse
Same thing mate, I ran it, click two times in console, can't unlock the bootloader, I always get stuck on it
Trying to update the drivers for Nexus S : http://www.4shared.com/rar/_bgEMHqk/Nexus_S_Drivers_x86__x64.html
and after that try to run.bat...Good luck!
I'll try today, but my problem is that adb cannot find the device, fastboot can
I would try downloading the full OTA from this thread, rename it to update.zip (for easy typing), place it in a directory where you can run fastboot, then use the command:
Code:
fastboot update update.zip
I got an error
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Should I create android-info.txt (how?) and place it into the zip (where?)
Thanks.
<edit> I saw this topic http://forum.xda-developers.com/showthread.php?t=1131588 and followed this http://forum.xda-developers.com/showthread.php?t=884416&highlight=STOCK but that as well complains about a locked bootloader </edit>
Is the problem solved？
szk5230 said:
Is the problem solved？
Click to expand...
Click to collapse
Not so far, I'm still having trouble with the phone, and no solution so far helped
Highl1 said:
I got an error
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Should I create android-info.txt (how?) and place it into the zip (where?)
Thanks.
<edit> I saw this topic http://forum.xda-developers.com/showthread.php?t=1131588 and followed this http://forum.xda-developers.com/showthread.php?t=884416&highlight=STOCK but that as well complains about a locked bootloader </edit>
Click to expand...
Click to collapse
Sorry my bad, haven't tried that before either...
If it bugs you the bootloader isn't unlcoked before flashing can't you just use
fastboot oem unlock
then commence with flashing your stock image?
Edit - Nevermind...I see you tried that.
any other suggestion? I'm out of ideas
I had this problem in December. I tried everything you tried without any luck so eventually took it back for warranty repair. Unfortunately I had some water damage from 9 months before so they wouldn't touch it. Luckily I got it replaced on my phone insurance but they said it couldn't repaired.
As far as I know it's a hardware fault. With CWM it looked like I could transfer files into the sd but they would disappear! I was able to use Fastboot and Odin but no joy. I had the same errors when trying to apply update using fastboot and never found answers about the "missing" files.
Sorry to come with bad news and good luck! I'm worried it'll happen to my replacement handset so keen to know if you resolve it.
Please note: I know there are other guides here on XDA but none worked for me, so I'm writing this to help other stuck people.
Disclaimer: I tested this on my XT1032, I don't know if or how it will work on other variants. Following this guide you'll lose all data on your phone, make sure to backup important stuff. I'm not responsible for what you do to your phone following this guide (anyway if you're here probably you have not much to lose...)
Introduction
What happened: a couple of weeks ago I wanted to try GPE rom on my XT1032, so I flashed the appropriate rom for my device (4.4.3 KOT49H.M004) and then applied OTA (4.4.3 KOT49H.M004 to 4.4.4 KTU84P.M003). Today I decided to go back to stock, so I rebooted in bootloader mode and tried to flash stock 4.4.3.
Result: a bunch of fastboot errors, ranging from "wrong size partitions", to "preflash validation failed", to ... well I don't remember all of them, as I said they were a lot..
Then I tried older versions, I tried to reflash 4.4.3 GPE, I tried to follow guides, here on XDA and around the vast internet.. All with no luck. Until I found one and, long story short I did it. I'm back to stock 4.4.4 (flashed stock 4.4.3 and applied OTA)
I'm sharing this what I did to recover from the soft-brick, hoping to help someone. This guide is not a temporary workaround while waiting for full 4.4.4 GPE image, this will fully restore your Moto G.
Let's start
- Make sure you have fastboot drivers installed (if you managed to soft-brick it you probably have them already installed, otherwise you can get them here)
- Download and extract this
- Reboot your phone in fastboot mode (keep Volume Down and Power buttons pressed for about 5 seconds then release the power button) and plug it to the PC
- Open the extracted folder and run "GPE_XT1032_KOT49H.M004_CFC.bat". Wait for it to finish (ignore errors, they're normal), then reboot to bootloader again (choose Normal powerup and keep pressed Volume Down until it boots to bootloader again)
- Download and extract this (mirror)
- Open the extracted folder and run THE FILE "fastboot flash recovery recovery.img.bat" (poorly chosen filenames, I know)
- Wait for it to finish, then choose "Recovery" item in bootloader and let it reboot to recovery.
- Go to "mounts and storage" and select "format cache", confirm, then select "format /data and /data/media", confirm.
- Go back to main menu and select "wipe data/factory", confirm.
- Return to the folder and run the file "adb push a.zip sdcard a.zip.bat", let it finish (it will take a couple of minutes, the window will close itself when done).
- From recovery select "install zip", then "choose zip from sd card" and select "a.zip". Let it finish, then go back to main menu and choose "power options", then "reboot to bootloader"
- Download and extract this (mirror)
- Open the extracted folder and run "flashall.bat". You should see no error (I got an error while it was flashing recovery but this is not important, what you should notice is that all the errors you got before are gone). Let it finish, then give it some time to boot.
Enjoy
You're done. Now you should have a stock 4.4.2 retail EU moto g. At this point you can flash the rom you want (for example, I flashed the original retail de, since my phone is german) without getting errors
---------------------------------------------------------------------------------------------------------
More or less I followed this, but I wrote the exact steps I made, I fixed wrong commands and uploaded a more complete version for last file
i have the same problem... i am waiting for thoe missing files... and i will try to go back to stock
EDIT i can't download the filles from mega
and the first download is broken
bannab said:
i have the same problem... i am waiting for thoe missing files... and i will try to go back to stock
EDIT i can't download the filles from mega
and the first download is broken
Click to expand...
Click to collapse
I fixed first link, I'm going to check the one from mega... If you find some other problems please let me know so I'll update
Edit: mega link is working. I suppose you're from Italy (me too), it's a DNS problem (mega has been blocked by AGCOM). you can follow this guide to change dns to google ones (8.8.8.8 and 8.8.4.4). When you downloaded the file you can set them back to auto. If someone can suggest an alternative good host (and possibly a way to directly upload from mega (I have a veeeeery slow upload bandwidth) I'll appreciate
i have already tried that method but no luck..
bannab said:
i have already tried that method but no luck..
Click to expand...
Click to collapse
Try with tor bundle.. It's a version of firefox modified for privacy and security purposes, you should be able to download from mega with it
Or this
nope
again lo luck for me.. flash of stock gives me always the same errors.. i think i will keep gpe with root... and wait for a camera with slow-mo..
bannab said:
again lo luck for me.. flash of stock gives me always the same errors.. i think i will keep gpe with root... and wait for a camera with slow-mo..
Click to expand...
Click to collapse
Did you follow exactly the guide? Did you get errors while wiping or flashing a.zip from recovery?
flashing stock
maybe beacuse i have booted after flashing gpe... i needed to boot it beacuse adb gives me error (device not found)
so i will keep gpe
bannab said:
flashing stock
maybe beacuse i have booted after flashing gpe... i needed to boot it beacuse adb gives me error (device not found)
so i will keep gpe
Click to expand...
Click to collapse
That is due to drivers.. OK, in case you do it again, check recovery messages to be sure it's doing its things
You saved my phone, thank you ! :victory:
JcruzV said:
You saved my phone, thank you ! :victory:
Click to expand...
Click to collapse
You're welcome.. That little heart attack when you see it's not booting and it doesn't flash anything [emoji1]
It worked! Thank you.
doodoo28s said:
It worked! Thank you.
Click to expand...
Click to collapse
Glad I helped
Thank's my Friend ! You have save my phone ! Thank youuuuuuu !!!!!!! <3
Hello.I tried to root my device with superboot and now my phone is not booting up,i tried to reboot but still the same,my screen stays black.Can this fix my phone? thnks
Nicolae-Daniel said:
Hello.I tried to root my device with superboot and now my phone is not booting up,i tried to reboot but still the same,my screen stays black.Can this fix my phone? thnks
Click to expand...
Click to collapse
This is useful if you can't flash anything. If you can, you can just flash stock or custom ROM
i suceed come back to 4.4.2 stock!!! thank you!!!!
finally a fix
thanks for posting this fix and all the others involved. i'm on EU so now i have to get back to my regular 4.4.4 Google Play Edition. this is good till i can get that back. been trying for 2 weeks to unbrick this thing and now i have it. thanks again and to the member JcruzV who linked this post. and not to forget PhilZ. :good:
bootsie35 said:
thanks for posting this fix and all the others involved. i'm on EU so now i have to get back to my regular 4.4.4 Google Play Edition. this is good till i can get that back. been trying for 2 weeks to unbrick this thing and now i have it. thanks again and to the member JcruzV who linked this post. and not to forget PhilZ. :good:
Click to expand...
Click to collapse
Didn't know this was linked in other threads
I hope this will be sticked or something, to avoid being forgotten in a couple of months. When I was searching how to unbrick I read of people who gave up and bought a replacement, wasting money when fortunately there is a solution
It did work!
I used Linux, so had to change a few things in the command files.
There are also two things:
1.
adb push a.zip /sdcard/a.zip - no apsce before the 2nd a.zip
2.
after the 3rd step recovery complains about "new ROM will overwrite recovery" - I have answered Yes.
I have got also another problem. Meanwhile I tried to recover my phone after the downgrade from 4.4.4 GPE to 4.4.2 Motorola ROM (before this thread), I have lost the IMEI... Currently it's still 0.
Anyone have an idea to recover this?
After flashing sense rom (walkman sense) pico freezes and automatically restarting.. :crying:
Tried flashing super_wipe.zip before flashing rom, and tried other roms too (cm11,carbon,nextgen,jaggy..!! ). The problem still persist..
How to fix this..??
Pee_kee said:
After flashing sense rom (walkman sense) pico freezes and automatically restarting.. :crying:
Tried flashing super_wipe.zip before flashing rom, and tried other roms too (cm11,carbon,nextgen,jaggy..!! ). The problem still persist..
How to fix this..??
Click to expand...
Click to collapse
some questions/ info needed
What recovery you using at the moment
Did you format everything but sdcard
Which firmware are you on / which region
anonymous-user said:
some questions/ info needed
What recovery you using at the moment
Did you format everything but sdcard
Which firmware are you on / which region
Click to expand...
Click to collapse
recovery : Latest TWRP
formatted every thing.. flashed superwipe.zip
am in india using Walkman sense rom 5.10.
problem persist in all rom..
Pee_kee said:
recovery : Latest TWRP
formatted every thing.. flashed superwipe.zip
am in india using Walkman sense rom 5.10.
problem persist in all rom..
Click to expand...
Click to collapse
ok, well have you tried relocking your bootloader and flashing RUU package back to full clean stock? if you`ve already done that properly (not by flashing some custom stock rom through recovery) then I guess its a repair shop job.
anonymous-user said:
ok, well have you tried relocking your bootloader and flashing RUU package back to full clean stock? if you`ve already done that properly (not by flashing some custom stock rom through recovery) then I guess its a repair shop job.
Click to expand...
Click to collapse
I didn't do that /*relocking your bootloader and flashing RUU package*/..
well, let me seek tutorials to do that.
Any tutorial with less risk than this one.? http://forum.xda-developers.com/showthread.php?t=1500165
Pee_kee said:
Any tutorial with less risk than this one.? http://forum.xda-developers.com/showthread.php?t=1500165
Click to expand...
Click to collapse
1st you need to find your firmware version, boot into bootloader and the info is there and then download the appropriate RUU package as these are region specific, I can tell you how to do it without much hassle so long as you have adb setup on your comp already and the unlock token or application used to unlock your bootloader.......
you can find all the RUU packages for pico here : http://www.androidruu.com/?developer=Pico
tell me which 1 it is and I`ll extract the files needed to be able to update it via sdcard
anonymous-user said:
1st you need to find your firmware version, boot into bootloader and the info is there and then download the appropriate RUU package as these are region specific, I can tell you how to do it without much hassle so long as you have adb setup on your comp already and the unlock token or application used to unlock your bootloader.......
you can find all the RUU packages for pico here : http://www.androidruu.com/?developer=Pico
tell me which 1 it is and I`ll extract the files needed to be able to update it via sdcard
Click to expand...
Click to collapse
This is RUU_Pico_hTC_Asia_India_1.31.720.3_Radio_10.35d.80.09H_1.11.82.17_release_230683_signed.exe
Pee_kee said:
This is RUU_Pico_hTC_Asia_India_1.31.720.3_Radio_10.35d.80.09H_1.11.82.17_release_230683_signed.exe
Click to expand...
Click to collapse
ok I have the specific RUU package for your region downloaded and I`ve extracted the rom.zip from the package, now I`m in the process of uploading the file for you. So you have adb working? the unlock token you used to unlock your bootloader or utility that will do the same job?
Ok here`s the full procedure for you
Download the the full firmware stock rom from here: http://www.freefilehosting.net/pj03img press "DOWNLAD THIS FILE" then enter the captcha, the file name is "PJ03IMG" do not modify it in anyway.
Copy the PJ03IMG file to the root of your sdcard (not in any folder)
Boot to Bootloader and connect usb to phone and computer, open CMD on windows or Terminal on Linux and type the following:
Code:
fastboot oem lock
you should now see on the phone that your bootloader has been "re-locked" if you see that you can now press the power button on phone to change to bootloader (mode see attached pic 1 at the bottom), now the phone will look for files on your sdcard (see pic 2 attached at the bottom)
at this point it should find the PJ03IMG file and a loading bar will appear on the right hand side, be patient it takes about 30 secs to load it. When its finished it will ask if you want to flash the update or not, use the volume keys to move the selector to yes and press the power button and the process will begin to totally reflash your phone back to stock once done it will ask you to reboot phone, voila done. the first boot will take some time as its a fresh install so give it afew minutes to get to homescreen, assuming all is well and phone is working as it should we can get a recovery back after unlocking the bootloader.
anonymous-user said:
will ask if you want to flash the update or not, use the volume keys to move the selector to yes and press the power button and the process will begin to totally reflash your phone back to stock
Click to expand...
Click to collapse
how pico do that without stock rom file.?! Where i should should keep rom.zip file.? how can i extract it from RUU_Pico_hTC_Asia_India_1.31.720.3_Radio_10.35d.80 .09H_1.11.82.17_release_230683_signed.exe..??
hey guys, yesterdy I got a notification for android 6.0 upgrade and it was a ~100mb file for preparation so i downloaded it and charged my battery and tapped to install it, it reboots and wants to start installing but then goes to recovery menu and gives an error
the phone is all stock, no root or bl unlock or anything
I attached the error msg below:
it's m8sd not e8sd, mistyped in topic
Might be due to bad zip file! Download the update again and try!
Kianush said:
hey guys, yesterdy I got a notification for android 6.0 upgrade and it was a ~100mb file for preparation so i downloaded it and charged my battery and tapped to install it, it reboots and wants to start installing but then goes to recovery menu and gives an error
the phone is all stock, no root or bl unlock or anything
I attached the error msg below:
it's m8sd not e8sd, mistyped in topic
Click to expand...
Click to collapse
I had a similar error as yours doing exactly the same thing but mine was a e8sw running LP5 Sense6 rooted stock with xposed.
Even when I uninstalled xposed and disabled supersu, I still could not install the upgrade.
Finally managed to get the upgrade by going all the way back to stock and allow the OTA updates all the way up the MM6 update. Took me nearly 2 days to do that.
I have taken clean twrp backups of all the stock updates and will try and post them here soon.
generalugh28 said:
I had a similar error as yours doing exactly the same thing but mine was a e8sw running LP5 Sense6 rooted stock with xposed.
Even when I uninstalled xposed and disabled supersu, I still could not install the upgrade.
Finally managed to get the upgrade by going all the way back to stock and allow the OTA updates all the way up the MM6 update. Took me nearly 2 days to do that.
I have taken clean twrp backups of all the stock updates and will try and post them here soon.
Click to expand...
Click to collapse
thank you for the information, but as I mentioned in op my phone is already all stock, I havent ever moded or rooted or anything, it's stock locked bootloader
Have the exact same issue. My device is compelitely stock. Tried flashing the recovery from the downloaded OTA but still got the sama error. Hopefully someone will be able to resolve the issue.
if you have problems in installing OTA updates, follow these steps
1. check if your CID and MID are matching each other. they should be both for same region. mine are for vietnam. mec_dugl / HTC__057
2.Flash an stock RUU from http://forum.xda-developers.com/one-e8/help/htc-one-e8-mid-cid-ruu-ota-twrp-t2903210
3.Skip all registeration process and directly go to update menu.
4.this is a 3 stage update process: a small update for some applications/another 100 MB update for making device ready for main update!! / at last 1 GB main update . each one should be downloaded and installed separately.
5. after downloading 100MB update, DO NOT restart. coneect your phone to PC and go to download folder on phone internal memory, there should be a zip file containing updates(sadly I forgot file name), copy it on your PC and extract recovery.img from it.
6. boot your phone into bootloader and flash stock recovery you've extracted using fastboot.
7. now you have complete stock ROM. go to setting/update again and follow update process.
8.after updating you may flash twrp and supersu.
9. I don't know why, but there is a good chance that after messing with system files in MM you get stuck in several kinds of bootloops and soft-breaks. Don't worry; all you should do is going to recovery and wiping caches. sometimes you need a factory reset too. also have in mind that a complete boot after changing system files may take up to 15 minutes even without wipes.
@sam5154 well thank you for the info, Im gonna try these steps except, I will try to download again and flash recovery and try it before flashing a RUU and lose everything
but I hope it works anyway, btw mine is also vietnam region.
sam5154 said:
if you have problems in installing OTA updates, follow these steps
1. check if your CID and MID are matching each other. they should be both for same region. mine are for vietnam. mec_dugl / HTC__057
2.Flash an stock RUU from http://forum.xda-developers.com/one-e8/help/htc-one-e8-mid-cid-ruu-ota-twrp-t2903210
3.Skip all registeration process and directly go to update menu.
4.this is a 3 stage update process: a small update for some applications/another 100 MB update for making device ready for main update!! / at last 1 GB main update . each one should be downloaded and installed separately.
5. after downloading 100MB update, DO NOT restart. coneect your phone to PC and go to download folder on phone internal memory, there should be a zip file containing updates(sadly I forgot file name), copy it on your PC and extract recovery.img from it.
6. boot your phone into bootloader and flash stock recovery you've extracted using fastboot.
7. now you have complete stock ROM. go to setting/update again and follow update process.
8.after updating you may flash twrp and supersu.
9. I don't know why, but there is a good chance that after messing with system files in MM you get stuck in several kinds of bootloops and soft-breaks. Don't worry; all you should do is going to recovery and wiping caches. sometimes you need a factory reset too. also have in mind that a complete boot after changing system files may take up to 15 minutes even without wipes.
Click to expand...
Click to collapse
Hi, thanks for this. I will try this once i got home.
But i have one questions, mine is Vietnam MEC_DUGL with stock lollipop 5.0.2. The RUU only available for stock lollipop 5.0.1. Can I use this RUU or should I look for specific RUU for lollipop 5.02?
Thanks!
Kianush said:
@sam5154 well thank you for the info, Im gonna try these steps except, I will try to download again and flash recovery and try it before flashing a RUU and lose everything
but I hope it works anyway, btw mine is also vietnam region.
Click to expand...
Click to collapse
If you gonaa try that, then remeber to unroot and uninstall xposed, and you can use titanium backup for restoring your apps and data of course.
sam5154 said:
If you gonaa try that, then remeber to unroot and uninstall xposed, and you can use titanium backup for restoring your apps and data of course.
Click to expand...
Click to collapse
in op I already told that I dont have root or anything and the phone is all stock and it was like this from the begining, that means no xposed or anything else
Kianush said:
in op I already told that I dont have root or anything and the phone is all stock and it was like this from the begining, that means no xposed or anything else
Click to expand...
Click to collapse
Have you tried the suggestion above? Let me know the result! Thanks man
sam5154 said:
If you gonaa try that, then remeber to unroot and uninstall xposed, and you can use titanium backup for restoring your apps and data of course.
Click to expand...
Click to collapse
and how to check for this mec_dugl / HTC__057?
the first part is ok it shows that in booloader menu, but how to check for HTC__057??
Kianush said:
in op I already told that I dont have root or anything and the phone is all stock and it was like this from the begining, that means no xposed or anything else
Click to expand...
Click to collapse
Kianush said:
and how to check for this mec_dugl / HTC__057?
the first part is ok it shows that in booloader menu, but how to check for HTC__057??
Click to expand...
Click to collapse
Here you go :
If you want more information, use ADB (if you don't how to get it going, use the search on the forum or Google about it).
While you phone is connected to your PC, type adb reboot bootloader and wait for your phone to reboot into bootloader mode. Once there, you can perform fastboot commands like getvar. Type fastboot getvar all and you will see all the information about the phone, including the product variable which lists the model you have.
Source : http://forums.androidcentral.com/htc-one-m7/320871-how-check-htc-one-variant-model.html
bataskhayal said:
Here you go :
If you want more information, use ADB (if you don't how to get it going, use the search on the forum or Google about it).
While you phone is connected to your PC, type adb reboot bootloader and wait for your phone to reboot into bootloader mode. Once there, you can perform fastboot commands like getvar. Type fastboot getvar all and you will see all the information about the phone, including the product variable which lists the model you have.
Source : http://forums.androidcentral.com/htc-one-m7/320871-how-check-htc-one-variant-model.html
Click to expand...
Click to collapse
Thank you for the info
btw I did go through the steps of downloading the 110mb update and flashing its recovery before pressing install and that didnt work and still gives OP error
so I guess I have to use RUU but not gonna do that for a while and also Im not so sure it'll work because the phone is already factory stock!
Kianush said:
Thank you for the info
btw I did go through the steps of downloading the 110mb update and flashing its recovery before pressing install and that didnt work and still gives OP error
so I guess I have to use RUU but not gonna do that for a while and also Im not so sure it'll work because the phone is already factory stock!
Click to expand...
Click to collapse
Yes bos, i also did the recovery trick but still cant make it work. So the only solution we havent try is to flash RUU which i doubt also will make it work since my phone also factory stock. So i guess will stay in 5.0.2 for a while.
Kianush said:
Thank you for the info
btw I did go through the steps of downloading the 110mb update and flashing its recovery before pressing install and that didnt work and still gives OP error
so I guess I have to use RUU but not gonna do that for a while and also Im not so sure it'll work because the phone is already factory stock!
Click to expand...
Click to collapse
Hi, I have managed to finally update my Vietnam HTC One E8 dual SIM (MEC_DUGL) to Android 6.0. The problem that cause the error is the error recovery file, hence I re-install the RUU to get the correct recovery.img file. Below are the steps :
Note : Try with your own risk
1. My device is currently stock 5.0.2 no root and locked. Before starting the update process please make sure to backup all of your important data. Im using the stock HTC backup software, when you restore your device after you finished your update process, it will re-install your currently installed apps , contacts, settings, etc.
2. Download RUU for your device here : http://forum.xda-developers.com/one-e8/help/htc-one-e8-mid-cid-ruu-ota-twrp-t2903210
I downloaded :
[Vietnam][DUAL][M8sd][mec_dugl][CID HTC__059][OPAJ20000] :
[Lollipop 5.0.1][2.35.425.2] : LINK
Seems not match with my current software (5.0.2), but eventually it will do the magic.
3. Flash RUU. NOTE : You will lose all of your data in your internal phone memory. Make sure to backup all of your important files.
Steps:
1) Download RUU.
2) Rename RUU to 0PAJIMG.zip (the first character is a zero, NOT A LETTER O)
3) Put renamed 0PAJIMG.zip on your external_SD
4) Boot into your bootloader and make sure your in hboot and let it update its RUU.
5) No PC, no adb, no fastboot, no terminal is needed, just a root explorer to rename and transfer the renamed RUU file to external_sd
6) After you have updated your RUU, make sure to remove the 0PAJIMG.zip from your external_sd because it will ask to update your RUU everytime your reboot to your bootloader which it is technically supposed to do but its unnecessary after you have done it once (unless you are planning on flashing RUU again).
7) Done!
Source : http://forum.xda-developers.com/one-e8/help/htc-one-e8-mid-cid-ruu-ota-twrp-t2903210
4. Reboot your phone, now your phone is back to factory stock, connect it to wifi, no need to set up any account, just go directly to software update from Settings > About > Software Updates. Just install all the available software updates (5.0.2 > 6.0 part 1 > 6.0 part 2).
5. BOOM! Your HTC One E8 now runs Android 6.0.1 Marshmallow.
6. Restore your phone from the stock HTC Backup Software.
7. Done
After Failing over and over, I finally was able to flash the latest NOUGAT Update provided in the other thread:
http://forum.xda-developers.com/moto-z/how-to/android-7-international-rollout-t3510790
Download the update.zip file "Blur_Version.24.21.46.griffin.retail.en.US.zip" from one of the posts
Main issue for me was i was on the wrong firmware, simple flash the "XT1650-03_GRIFFIN_ROGERS_MPL24.246-45_cid50_subsidy-RGRCA_regulatory-DEFAULT_CFC.xml" firmware by grabbing it from
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
Notice you need the MPL24.246-45 FIRMWARE , the number 45 plays a major role as it will be verified later. I was running the buildnumber MPL24.246-20 instead of 40
once you get that out of the way and are done flashing the MPL24.246-40 firmware, simply adb sideload the Blur_Version.24.21.46.griffin.retail.en.US.zip from your computer, reboot in stock recovery and then hold power and then press volume up and choose the option adb sideload
My sideload failed at 95%, however when i rebooted, it was running nougat
let me know how it goes for you guys
My bootloader is unlocked, and i did not relock it
This is really sad. They said it was going to be this week and a global roll out.
Nothing!
I can't wait until Samsung release the S8E.. Giving this phone to my 8 years old niece to have!
can u make some order here ?
what is your model ?
if u flashed 24.246-45 then u said it needs to be 40
then did u flash the 40 over 45 ?
thanks
hassanman1997 said:
Download the update.zip file "Blur_Version.24.21.46.griffin.retail.en.US.zip" from one of the posts
Main issue for me was i was on the wrong firmware, simple flash the "XT1650-03_GRIFFIN_ROGERS_MPL24.246-45_cid50_subsidy-RGRCA_regulatory-DEFAULT_CFC.xml" firmware by grabbing it from
Notice you need the MPL24.246-45 FIRMWARE , the number 45 plays a major role as it will be verified later. I was running the buildnumber MPL24.246-20 instead of 40
once you get that out of the way and are done flashing the MPL24.246-40 firmware,
Click to expand...
Click to collapse
This is really helpful. I hit the same snag when I tried to upgrade from -17 firmware.
Any chance you could upload the Canadian Rogers firmware (-45) to Mega? It's so painful waiting for 9 hours for it to fail a few minutes from the end.
Yeah I can try, but I won't be home until night, the only pain was waiting 9 hours, and the firmware is -45, I accidently wrote -40 , I don't think there is any firmware with-40
I tried all the above. Still fails for me.
---------- Post added at 05:14 PM ---------- Previous post was at 05:10 PM ----------
I think because the file has been replaced with a v2 so it's failing verification
I'm uploading the Rogers .45 firmware to mega right now. I'll update this post once its done uploading.
Link: https://mega.nz/#!nssGEDiT!hhLkcTM106hmqbH_fiWfAytEV-fgdlYOhUwpcd_sGJY
Downloaded straight from FileFactory and uploaded directly to Mega
Here is: XT1650-03_GRIFFIN_ROGERS_MPL24.246-45
https://drive.google.com/file/d/0Bw3YYHFxKQxVNTBLeWxadUFZOU0/view?usp=sharing
...Now, can someone help me figure out how to flash it? That would be awesome
svetius said:
Here is: XT1650-03_GRIFFIN_ROGERS_MPL24.246-45
https://drive.google.com/file/d/0Bw3YYHFxKQxVNTBLeWxadUFZOU0/view?usp=sharing
...Now, can someone help me figure out how to flash it? That would be awesome
Click to expand...
Click to collapse
Whats the status of your device right now? Are you purely stock? Rooted? Unlocked? TWRP or stock recovery?
Prfndhatrdofman said:
Whats the status of your device right now? Are you purely stock? Rooted? Unlocked? TWRP or stock recovery?
Click to expand...
Click to collapse
I flashed XT1650-03_GRIFFIN_ROGERS_MPL24.246-45 via this method:
http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
And while the flash was successful, strangely booting into the OS I'm still on -20.
So then I tried to sideload nougat, and it went up to 87% and failed, causing a bootloop. The bootloop can be fixed by manually flashing -45 again (which is so weird because it actually loads -20).
I am unrooted, bootloader locked.
svetius said:
I flashed XT1650-03_GRIFFIN_ROGERS_MPL24.246-45 via this method:
http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
And while the flash was successful, strangely booting into the OS I'm still on -20.
So then I tried to sideload nougat, and it went up to 87% and failed, causing a bootloop. The bootloop can be fixed by manually flashing -45 again (which is so weird because it actually loads -20).
I am unrooted, bootloader locked.
Click to expand...
Click to collapse
You got further than me. ADB Sideload wouldnt even look at the Nougat OTA zip. tried multiple ADB versions too
svetius said:
I flashed XT1650-03_GRIFFIN_ROGERS_MPL24.246-45 via this method:
http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
And while the flash was successful, strangely booting into the OS I'm still on -20.
So then I tried to sideload nougat, and it went up to 87% and failed, causing a bootloop. The bootloop can be fixed by manually flashing -45 again (which is so weird because it actually loads -20).
I am unrooted, bootloader locked.
Click to expand...
Click to collapse
Sideload was successful for me, but still completely in a bootloop as well..
for me it worked fine with ADB sideload.
my bootloader is unlocked, i tried locking it back to get official OTA but failed to lock it again.
I tried every method that was mentioned but failed over and over
so here is what I did:
1) removed all the personal files from phone (pictures, videos, texts etc) so i don't lose em
2) flashed the rogers [XT1650-03_GRIFFIN_ROGERS_MPL24.246-45_cid50_subsidy-RGRCA_regulatory-DEFAULT_CFC.xml] firmware by using mfastboot, make sure you grab the mfastbootv2, you can google and download it, use mfastboot and flash the firmware by command lines
3)after flashing, rebooted, set up the device and skipping a few steps to get into homescreen, and then powered off the phone.
4)downloaded Blur_Version.24.21.46.griffin.retail.en.US.zip and placed it in the adb folder, make sure you download the latest adb tools, you can google and find them easily too
5) extract the adb folder and place the Blur_Version.24.21.46.griffin.retail.en.US.zip in side that folder
6) reboot the phone and press volume to navigate to recovery, you should boot into stock recovery as you flashed stock firmware
7) hold power button and press volume up and youll see the menu, select update by ota and connect to the phone
8) open command line in the adb tools and use command to flash ota via adb
9) mine failed at 95% because of system image error, so instead of rebooting it, i used the command again and flashed the ota via adb, it failed again, however when i rebooted i was presented by the new red moto boot animation, there i knew it was updated to android N
*Delete*
hassanman1997 said:
After Failing over and over, I finally was able to flash the latest NOUGAT Update provided in the other thread:
http://forum.xda-developers.com/moto-z/how-to/android-7-international-rollout-t3510790
Download the update.zip file "Blur_Version.24.21.46.griffin.retail.en.US.zip" from one of the posts
Main issue for me was i was on the wrong firmware, simple flash the "XT1650-03_GRIFFIN_ROGERS_MPL24.246-45_cid50_subsidy-RGRCA_regulatory-DEFAULT_CFC.xml" firmware by grabbing it from
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
Notice you need the MPL24.246-45 FIRMWARE , the number 45 plays a major role as it will be verified later. I was running the buildnumber MPL24.246-20 instead of 40
once you get that out of the way and are done flashing the MPL24.246-40 firmware, simply adb sideload the Blur_Version.24.21.46.griffin.retail.en.US.zip from your computer, reboot in stock recovery and then hold power and then press volume up and choose the option adb sideload
My sideload failed at 95%, however when i rebooted, it was running nougat
let me know how it goes for you guys
My bootloader is unlocked, and i did not relock it
Click to expand...
Click to collapse
OK, so i got it working. But there were some difficulties.
I was on 24.246-45 already, but i installed TWRP and a custom kernel. I reflashed the recovery and boot from the BELL 24.246.45 firmware, and proceeded sideloading the update. It errored out, saying system was mounted r/w once (after I installed TWRP, but I never altered it beyond that).
So i flashed the system chunks from the firmware ( "mfastboot flash system system.img_sparsechunk.0" , "mfastboot flash system system.img_sparsechunk.1" etc.), then i retried the sideload, and it worked. The system information still says the build number is MPL24.246-45, but the android version is 7.0, everything seems to be working, including split screen, the new easter egg, quicklaunch ribbon, and new notifications.
gomisensei said:
... The system information still says the build number is MPL24.246-45, but the android version is 7.0, everything seems to be working, including split screen, the new easter egg, quicklaunch ribbon, and new notifications.
Click to expand...
Click to collapse
This should be only a "cosmetic" issue... probably you can fix it by editing build.prop...
enetec said:
This should be only a "cosmetic" issue... probably you can fix it by editing build.prop...
Click to expand...
Click to collapse
meh, i'm not really worried about it, at least not enough to guess what the version SHOULD be...
gomisensei said:
meh, i'm not really worried about it, at least not enough to guess what the version SHOULD be...
Click to expand...
Click to collapse
:laugh:
Does that actually work for other software channels as well?
I'm from india, my software chanel is retin (retail India) can I still flash the one that came for retus?
Sent from my Moto Z using XDA Labs