Marshmallow for Idol 3

[thefabgar]

of course he can´t

Why? Is there any restriction?

 

[DallasCZ]

Why? Is there any restriction?

in stock recovery, you can only adb sideload vendor signed archives.

Odesláno z mého 6045Y pomocí Tapatalk

 

[Siraj Enriq]

I am using 6045k bought from Dubai.... Still i didnt get mm update in india.. Pls help

 

[thefabgar]

of course he can´t

in stock recovery, you can only adb sideload vendor signed archives.

Odesláno z mého 6045Y pomoc�* Tapatalk

I don't know if I'm super stupid, an extreme noob, or something, but I can't do it.
Used mobile q back to Lollipop, unlocked bootloader, installed TWRP, backed up my 6045B System and Boot (will make it available later today) and then I just installed the update.zip Alek provided with the latest OTA for 6045i. After installed succesfully, thats it, boot loop.

What am I doing wrong? Should I mount something after that?

This is driving me crazy, I can't do anything even when I'm following every instruction perfectly.

Is there a chance to upload the latest OTA update.zip signed so I can ADB sideload it with the stock recovery?

Thanks

 

[DallasCZ]

I don't know if I'm super stupid, an extreme noob, or something, but I can't do it.
Used mobile q back to Lollipop, unlocked bootloader, installed TWRP, backed up my 6045B System and Boot (will make it available later today) and then I just installed the update.zip Alek provided with the latest OTA for 6045i. After installed succesfully, thats it, boot loop.

What am I doing wrong? Should I mount something after that?

This is driving me crazy, I can't do anything even when I'm following every instruction perfectly.

Is there a chance to upload the latest OTA update.zip signed so I can ADB sideload it with the stock recovery?

Thanks

nobody beside the nanufacturer can sign the package so far. You have to complain in the desired Alek thread.

Odesláno z mého 6045Y pomocí Tapatalk

 

[François91]

Following up with my adopted SD issues... I decided to try to format the SD card, but now the phone won't allow me to format it as internal... Only portable storage works (but I don't care because I don't have many medias on my phone... I just have enough apps to fill the internal memory !)
Here is the error message when trying to format as internal. A search on the web isn't very helpful, some blame their phone, some blame the SD... (but I checked mine's authenticity and it is OK...)
Anyone having similar issues here ?

 

[newbie_or_not_newbie]

Yes, mine too.
Because of the quality of the micro-sd ?

 

[François91]

Yes, mine too.
Because of the quality of the micro-sd ?

I have this Transcend bought about one year ago. According to the "SD Insight" app, it could be some kind of rebranding of a SanDisk card (it is listed as a "SanDisk SL32G").
It's a class 10. I really can't figure out why it wouldn't fit.

 

[DallasCZ]

Following up with my adopted SD issues... I decided to try to format the SD card, but now the phone won't allow me to format it as internal... Only portable storage works (but I don't care because I don't have many medias on my phone... I just have enough apps to fill the internal memory !)
Here is the error message when trying to format as internal. A search on the web isn't very helpful, some blame their phone, some blame the SD... (but I checked mine's authenticity and it is OK...)
Anyone having similar issues here ?

its totally off topic, please dont post irelevant questions here....

 

[audit13]

It's been a while since I used my Canada 6045i Bell Idol 3 that is running 5.02. I booted it up and there was an OTA update that started to download. I copied today's update.zip to my Windows PC and the file size is 1,391,930 KB.

The previous update.zip file from July, 2016 was 1,381,252 KB.

Any way I can tell what the update is for?

Thanks.

 

[mrcorey]

I would like to know where to find a changelog, too. My Google fu didn't seem to be good enough this time

sent from a phone running a ROM

 

[audit13]

I looked at the metadata file in the update from mid-2016 and it says this: post-build=TCL/6045I/idol3:6.0.1/MMB29M/v7VAB-0:user/release-keys
post-timestamp=1465065463
pre-device=idol3

I looked at the metadata file in the update from 2017/Jan/12 and it says this: post-build=TCL/6045I/idol3:6.0.1/MMB29M/v7VGE-0:user/release-keys
post-timestamp=1479722708
pre-device=idol3

 

[DallasCZ]

I looked at the metadata file in the update from mid-2016 and it says this: post-build=TCL/6045I/idol3:6.0.1/MMB29M/v7VAB-0:user/release-keys
post-timestamp=1465065463
pre-device=idol3

I looked at the metadata file in the update from 2017/Jan/12 and it says this: post-build=TCL/6045I/idol3:6.0.1/MMB29M/v7VGE-0:user/release-keys
post-timestamp=1479722708
pre-device=idol3

It is unix timestamp:
1465065463 = Sat, 04 Jun 2016 18:37:43 GMT
1479722708 = Mon, 21 Nov 2016 10:05:08 GMT
just a build date.

 

[audit13]

Thanks for the clarification. So I assume the build from yesterday is an update to the previous build of June 4/16.

Does V7AB or V7VGE mean anything? I'm not sure.

I haven't installed either build as I am not using my Idol 3 at the moment.

 

[DallasCZ]

But the question is, why ar ethe OTAs so big. As far as i know the first one from summer is the MM build then is the size ok, but after that, only patches arrived for different models and not whole firmware again.

 

[audit13]

My phone is running stock 5.02 and yesterday's update.zip will take me to the latest patched version of MM? I'm not really sure.

 

[DallasCZ]

yes and you will not be able to root the phone when on MM.

 

[audit13]

I realize that installing the MM update will cause me to lose fastboot commands too.

I'm not using my phone at the moment which is why it is still on stock 5.02.

@DallasCZ, thanks for the information.