Develop Bugs

[Q] HELP - Wiped the OS off of my Galaxy S3 I747

Alright, well I've come to a problem and I'm not quite sure how to fix it.
The title pretty much says it all, I've completely wiped the operating system off of my phone. There is nothing left, absolutely no data or anything. I was much too hasty and irresponsible, and I fear for the worst. I had previously attempted installing multiple ROMs multiple times using CWM to no avail so I re-rooted and switched over to Team Win. I know before installing a ROM you have to wipe your phone, well... I hit advanced wipe and within that I hit "system", went ahead and wiped. There's nothing left on my phone my phone and there are no ROMs on my SD card. I had backed up my phone before wiping but when I wiped that was also deleted. Before restarting it always warns me "No OS installed on your phone, are you sure you want to reboot?" Of course it's bricked and stays at the "Samsung Galaxy SIII" screen. I attempted putting a stock ROM back on my phone through ODIN, but a'las it didn't work (always stops at "SetupConnection"). I have nothing and there is no way for me to get a new ROM on the phone, I obviously cannot connect to my computer unless through download mode because the phone is bricked. So, what do I do? Is there any hope left for me or am I just completely screwed? The phone is less than a month old.

another option is to purchase a micro sd card and place a ROM and gapps (if required) on it, install the card and boot into recovery.
so when you connect your device to your pc, you're getting a yellow com connection in odin? what link did you follow for a stock ROM?
as long as you can still access recovery and download mode, there is hope, buddy.

xBeerdroiDx said:
another option is to purchase a micro sd card and place a ROM and gapps (if required) on it, install the card and boot into recovery.
so when you connect your device to your pc, you're getting a yellow com connection in odin? what link did you follow for a stock ROM?
as long as you can still access recovery and download mode, there is hope, buddy.
Click to expand...
Click to collapse
Yeah, when I connect to the PC I get a yellow com connection in ODIN. I followed what is, perhaps, a sketchy looking link for the stock ROM... It's not letting me post a link because I'm a new member to the board, though I've looked over this place plenty of times in the past. Should I look for something a bit more official and retry? I don't think it's going to work. Will a ROM work, without an OS? I know that may sound silly but everything I've tried so far has failed.

here's a link to the stock firmware with root already injected: http://forum.xda-developers.com/showthread.php?t=1739426
flash the tar in odin like you have been. make sure the auto reboot box is unticked. if you get a PASS after flashing, unplug the device, pull the battery, replace it and press the recovery button combo. once in recovery, wipe data and wipe cache. reboot.
lemme know if that worked, otherwise throw a ROM on a micro sd card as stated and go that route
btw, a ROM is the OS.

And also, my phone has to be rooted for a ROM to be installed, right? Well there's no guarantee my phone is still rooted since I've wiped literally everything on the phone. I like the idea of a placing it all on an SD card but that could be wasted money and I don't have very much money to spend, especially if a ROM isn't going to replace all of the needed system files which have been deleted.

NovoAevum said:
And also, my phone has to be rooted for a ROM to be installed, right? Well there's no guarantee my phone is still rooted since I've wiped literally everything on the phone. I like the idea of a placing it all on an SD card but that could be wasted money and I don't have very much money to spend, especially if a ROM isn't going to replace all of the needed system files which have been deleted.
Click to expand...
Click to collapse
follow my directions above to flash rooted stock firmware

xBeerdroiDx said:
follow my directions above to flash rooted stock firmware
Click to expand...
Click to collapse
Alright, thanks a lot. My internet is super slow so it'll probably be a while before the file is completely downloaded. Let's hope this works. I'll get back to you when it's all said and done.

xBeerdroiDx said:
follow my directions above to flash rooted stock firmware
Click to expand...
Click to collapse
You have no idea how grateful I am, thank you so very, very much. It worked, I cannot express my gratitude. I truly appreciate it.

NovoAevum said:
You have no idea how grateful I am, thank you so very, very much. It worked, I cannot express my gratitude. I truly appreciate it.
Click to expand...
Click to collapse
booyah.
:good: thats why we're called a community. cheers!

NovoAevum said:
You have no idea how grateful I am, thank you so very, very much. It worked, I cannot express my gratitude. I truly appreciate it.
Click to expand...
Click to collapse
One small thing you can do is to hit the "Thanks" button on xBeerdroiDx's posts.
:good:

im having the same promblem
post-mortem said:
One small thing you can do is to hit the "Thanks" button on xBeerdroiDx's posts.
:good:
Click to expand...
Click to collapse
how did u get your phone to connect to odin

dorvilkervins said:
how did u get your phone to connect to odin
Click to expand...
Click to collapse
Have you installed the Samsung drivers?
---------- Post added at 06:03 PM ---------- Previous post was at 05:27 PM ----------
Can you explain what happened with your phone? How did you "lose everything?" Is it able to boot up into Android? Can you get into recovery (TWRP)? Did you accidentally wipe something you shouldn't have?

I accidentally wiped my OS on my Galaxy S3 AT&T - Please Help!!!
Hello all,
I am a rookie user of smartphones and I have a Samsung Galaxy S3 AT&T. I accidentally wiped my OS leaving me with no OS. The good news is that I can still use Team Win and boot into recovery. How can I download and install a new OS? I live in a rural area with no place to go to get this fixed; so I would really appreciate any and all help on this matter. Thanks for reading
Tyler
---------- Post added at 01:10 AM ---------- Previous post was at 12:24 AM ----------
Hello all,
I am a rookie user of smartphones and I have a Samsung Galaxy S3 AT&T. I accidentally wiped my OS leaving me with no OS. The good news is that I can still use Team Win Development. Using Team Win, how can I download and install a new OS? I live in a rural area with no place to go to get this fixed; so I would really appreciate any and all help on this matter. Thanks for reading
Tyler

Check this:
http://forum.xda-developers.com/showthread.php?t=2363882

Hey Bro, xBeerdroiDx, Indeed this is a great community, but, it is the fellas' and ladies, like you,that have the knowledge and experience ,that do not have to assist anyone ,but do anyway. I am just another member here, but as a brother, you get a pat on the back from the gallery. Your willingness to help is very much appreciated.

me too
so twrp and dl mode are cool...but odin fails and zip in recovery kicks a status 7 error...what to do?
sgh-i747 .....i think my build.prop or bootloader is jacked?

hewhoisnotasothers said:
so twrp and dl mode are cool...but odin fails and zip in recovery kicks a status 7 error...what to do?
sgh-i747 .....i think my build.prop or bootloader is jacked?
Click to expand...
Click to collapse
Did you try \the latest CWM or TWRP? Maybe the ROM needs a more recent bootloader?

gottam
audit13 said:
Did you try \the latest CWM or TWRP? Maybe the ROM needs a more recent bootloader?
Click to expand...
Click to collapse
the bootloader may have been corrupted by a 4.x downgraded flash....i'm not sure how to proceed...

hewhoisnotasothers said:
the bootloader may have been corrupted by a 4.x downgraded flash....i'm not sure how to proceed...
Click to expand...
Click to collapse
Were you on stock 4.3 ROM?

audit13 said:
Were you on stock 4.3 ROM?
Click to expand...
Click to collapse
yes...I have tryed everything i can think of....i can flash recoverys just fine, but i havent found a rom that will boot past the splash screen...most just fail in odin...i don't want to jtag if i dont have to...in theory there should be hope since i can get into DL and twrp....

Read a zillion threads, nothing sticks

So I've rooted my phones for the last 5 years, nexus 1, droid, rezound, gs4, n5 and then the m8. finally i screwed up, and i was getting bootloops. in my slightly panicked state i managed to wipe the OS completely off of the device.
i can get into fastboot and from there also TWRP recovery. i've read a million threads, adb sideload, One_M8 all in one kit, etc....
I can't figure out how to now simply flash a stock ROM onto my device. can anyone spell it out in a way this idiot can get it? i;ve downloaded a gazillion things. i'm stuck. i had to go pay full retail for a phone because as a realtor i simply can't be without one even for a day. it's my lifeline. i'd like to fix this one so i can return the new one and save $700.
thanks.

When you say you wiped the OS, did you also clear the partitions? Are you booting into recovery by flashing TWRP and then booting into recovery... or are you booting into recovery via "fastboot boot"? If you have partitions still, you can use a USB OTG adapter and memory stick (or just sdcard) to store the firmware.zip file and flash it from TWRP.
IF, on the other hand, you wiped your partition table, you are in a bigger mess. It's possible a RUU can help, but I'm not familiar with them so can't comment beyond suggesting that you look into that more...

In the development section there is a system dump by (Mike1986). If your computer still recognizes your phone, download system dump to computer, copy it to your phone's internal storage, get into twrp and flash.
Sent from my HTC One_M8 using XDA Premium 4 mobile app

Tdeljr said:
In the development section there is a system dump by (Mike1986). If your computer still recognizes your phone, download system dump to computer, copy it to your phone's internal storage, get into twrp and flash.
Click to expand...
Click to collapse
How would you go about copying to the phone's internal storage?

After downloading Rom right click on it select cut, go into your phone's storage on computer (as long as computer recognizes phone) find empty space right click and select paste.
Sent from my HTC One_M8 using XDA Premium 4 mobile app

Tdeljr said:
After downloading Rom right click on it select cut, go into your phone's storage on computer (as long as computer recognizes phone) find empty space right click and select paste.
Click to expand...
Click to collapse
Please re-read the original post. The phone doesn't boot into android.

garyd9 said:
Please re-read the original post. The phone doesn't boot into android.
Click to expand...
Click to collapse
Well considering your not the original poster, and I've read the original post several times and can't seem to find where it says it doesn't boot into android. I'm just trying to offer whatever help I can.
Sent from my HTC One_M8 using XDA Premium 4 mobile app

There is a DEV RUU out. You can use that. Or if you want ATT, or GPE, find the zips, and use fastboot commands to flash. If the computer can see the phone and you can issue commands, then there is nothing to worry about. Been there done that dozens of times with the M7. After playing with this M8, seems to be the same. Let us know where you are stuck, i.e. don't know the commands, or don't know where to find the zips.
---------- Post added at 09:05 PM ---------- Previous post was at 09:01 PM ----------
Tdeljr said:
Well considering your not the original poster, and I've read the original post several times and can't seem to find where it says it doesn't boot into android. I'm just trying to offer whatever help I can.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
He wiped the OS, which is Android, thus he can't just plug it in and transfer files back and forth anymore.

hack14u said:
There is a DEV RUU out. You can use that. Or if you want ATT, or GPE, find the zips, and use fastboot commands to flash. If the computer can see the phone and you can issue commands, then there is nothing to worry about. Been there done that dozens of times with the M7. After playing with this M8, seems to be the same. Let us know where you are stuck, i.e. don't know the commands, or don't know where to find the zips.
---------- Post added at 09:05 PM ---------- Previous post was at 09:01 PM ----------
He wiped the OS, which is Android, thus he can't just plug it in and transfer files back and forth anymore.
Click to expand...
Click to collapse
That's my bad, didn't put 2 & 2 together. Thanks for explaining.
Sent from my HTC One_M8 using XDA Premium 4 mobile app

Surely if you've only deleted the OS just flash a nandroid from the stock backup thread via TWRP?

pixelsquish said:
So I've rooted my phones for the last 5 years, nexus 1, droid, rezound, gs4, n5 and then the m8. finally i screwed up, and i was getting bootloops. in my slightly panicked state i managed to wipe the OS completely off of the device.
i can get into fastboot and from there also TWRP recovery. i've read a million threads, adb sideload, One_M8 all in one kit, etc....
I can't figure out how to now simply flash a stock ROM onto my device. can anyone spell it out in a way this idiot can get it? i;ve downloaded a gazillion things. i'm stuck. i had to go pay full retail for a phone because as a realtor i simply can't be without one even for a day. it's my lifeline. i'd like to fix this one so i can return the new one and save $700.
thanks.
Click to expand...
Click to collapse
Have you got an external sd card? whack it on there using a card reader and flash from external sd
---------- Post added at 11:04 AM ---------- Previous post was at 11:01 AM ----------
If that won't work on TWRP use philz

not sure if i wiped the partitions. don't think so.
i can't transfer files to the device, the pc recognizes it to give fastboot commands via a command prompt, but not as a removable device.
i'll get an sd card on my way home today and try flashing a rom using recovery.

hack14u said:
There is a DEV RUU out. You can use that. Or if you want ATT, or GPE, find the zips, and use fastboot commands to flash. If the computer can see the phone and you can issue commands, then there is nothing to worry about. Been there done that dozens of times with the M7. After playing with this M8, seems to be the same. Let us know where you are stuck, i.e. don't know the commands, or don't know where to find the zips.
---------- Post added at 09:05 PM ---------- Previous post was at 09:01 PM ----------
He wiped the OS, which is Android, thus he can't just plug it in and transfer files back and forth anymore.
Click to expand...
Click to collapse
i think i got the right zip. nm not the right one.

If you want, set up a TeamViewer session and I will fix it for you.
My thread is here: http://forum.xda-developers.com/showpost.php?p=43588969

Matt said:
If you want, set up a TeamViewer session and I will fix it for you.
My thread is here: http://forum.xda-developers.com/showpost.php?p=43588969
Click to expand...
Click to collapse
oh pretty cool. i have the sd card now and going to try. otherwise i may take you up on your offer.
anyone have a link to the right ROM zip file to flash for AT&T version phone?
EDiT: NM Found the thread in the Development section. Flashed it. Currently it's booting up, Android is upgrading optimizing all apps.

pixelsquish said:
oh pretty cool. i have the sd card now and going to try. otherwise i may take you up on your offer.
anyone have a link to the right ROM zip file to flash for AT&T version phone?
EDiT: NM Found the thread in the Development section. Flashed it. Currently it's booting up, Android is upgrading optimizing all apps.
Click to expand...
Click to collapse
very strange. after flashing and rebooting, i didn't have a clean install of Android, all my customizations and apps from before were installed. and i got the same random reboots. so all that info was still on the phone. went back into recovery and wiped everything, then re-flashed. now have a fresh clean install of stock 4.4.2
Thanks everyone! i kinda thought the sd card thing would be the easiest but the comments in this thread confirmed it and it worked.

pixelsquish said:
very strange. after flashing and rebooting, i didn't have a clean install of Android, all my customizations and apps from before were installed. and i got the same random reboots. so all that info was still on the phone. went back into recovery and wiped everything, then re-flashed. now have a fresh clean install of stock 4.4.2
Thanks everyone! i kinda thought the sd card thing would be the easiest but the comments in this thread confirmed it and it worked.
Click to expand...
Click to collapse
That's the beauty of the sd card slot mate, i have saved my m8 countless times. i would always make a backup of your phone prior to tinkering but this really helps save ur ass if you forget to backup.
Glad everything is ok and that this simple solution worked :highfive::good:

[Q] GT-I9195 Black Edition - What to do in which order?

Hi,
please give keywords and guiding advice, I will try to find the corresponding threads by myself
I have a brand new GT-I9195 Black Edition. I want to do as less damage as possible, so what do I have to do to get CM11 with Xposed framework running?
I just switched it on, started KIES 2 and connected. No SIM-card is inserted, no microSD-card, no WiFi connection. The phone is offline.
KIES says that the firmware is the most recent and gives this:
Code:
I9195XXUBML4 / I9195YBTBNA2 / I9195XXUBML4 / I9195XXUBML4 (DBT)
I assume this is not the newest firmware, and according to this thread (German) "I9195XXUCNE6 I9195OXACNE6 DBT 4.4.2 23.05.2014 is newer.
I have or see no possibility to upgrade via KIES.
Would the new firmware give me another, better modem/baseband firmware? If so, I would flash with Odin 3.09.
I think I need root permissions for Xposed and XPrivacy, at least this is what I did with my Sony Xperia mango. Is that correct?
What steps do I have to take to get root access without interacting with KNOX? Does it make sense to avoid the KNOX counter increase?
What part of the warranty will be void if KNOX is triggered?
What recovery should I use? There is already a recovery available, accessible by pressing Volume Up and home button at the same time when switching on.
I wanted to start with CM11 and no special kernel, just what CM11 brings, to keep it easy. So flashing serranoltexx M9 or later should be sufficient?
How do I get Xposed and XPrivacy to work? I want it working before putting in the SIM card and connecting to the internet. Do I have to worry about dalvik and ART?
GApps 20140105 from http://wiki.cyanogenmod.org/w/Google_Apps are the right ones?
Did I forget something?
Thank you
Raubsau

You answered most of it yourself, just go for it and you will learn even more doing it.
If I were you I would probably flash TWRP 2.7.1, latest stable CM11, and a gapps from CM or wherever. Install xposed and whatever modules. Done.
Xposed is sort of contained/maintained within itself but it and its modules install just the same. Its easy to set up. I don't know Xprivacy at alll.
You can flash and try any compatible kernels from here anytime. Remember Nandroid and Titanium backups are your best mates.
Forget about Kies, you won't need it. CM11 firmware should provide a more than adequate modem and everything you need to go.

MarkAndroid.UK said:
You answered most of it yourself, just go for it and you will learn even more doing it.
If I were you I would probably flash TWRP 2.7.1, latest stable CM11, and a gapps from CM or wherever. Install xposed and whatever modules. Done.
Xposed is sort of contained/maintained within itself but it and its modules install just the same. Its easy to set up. I don't know Xprivacy at alll.
You can flash and try any compatible kernels from here anytime. Remember Nandroid and Titanium backups are your best mates.
Forget about Kies, you won't need it. CM11 firmware should provide a more than adequate modem and everything you need to go.
Click to expand...
Click to collapse
I don't want to brick the device, that's why I'm asking.
Each thread seems to recommend CWM - why do you suggest TWRP?
I want to install Xposed an the XPrivacy module even before starting CM for the first time - I'm not afraid of injecting the .apk via ADB, if there is a way to connect without enabling dev mode or similar. Any idea about how to do that?
(XPrivacy is restriction management on a very fine grain level - if you want to restrict the phone app from actually making a phone call, or any (even system!) app from reading your conatcs or only certain contacts, this is your best friend. Similar but way mightier to the good old PDroid :good
I thought the modem was something independent from the ROM? More like a driver for an auxiliary processor?

Raubsau said:
I don't want to brick the device, that's why I'm asking.
Each thread seems to recommend CWM - why do you suggest TWRP?
I want to install Xposed an the XPrivacy module even before starting CM for the first time - I'm not afraid of injecting the .apk via ADB, if there is a way to connect without enabling dev mode or similar. Any idea about how to do that?
(XPrivacy is restriction management on a very fine grain level - if you want to restrict the phone app from actually making a phone call, or any (even system!) app from reading your conatcs or only certain contacts, this is your best friend. Similar but way mightier to the good old PDroid :good
I thought the modem was something independent from the ROM? More like a driver for an auxiliary processor?
Click to expand...
Click to collapse
Why is it so important to you to install XPrivacy before first boot?

Raubsau said:
I don't want to brick the device, that's why I'm asking.
Each thread seems to recommend CWM - why do you suggest TWRP?
I want to install Xposed an the XPrivacy module even before starting CM for the first time - I'm not afraid of injecting the .apk via ADB, if there is a way to connect without enabling dev mode or similar. Any idea about how to do that?
(XPrivacy is restriction management on a very fine grain level - if you want to restrict the phone app from actually making a phone call, or any (even system!) app from reading your conatcs or only certain contacts, this is your best friend. Similar but way mightier to the good old PDroid :good
I thought the modem was something independent from the ROM? More like a driver for an auxiliary processor?
Click to expand...
Click to collapse
No one wants to brick their device, do they? I've never bricked mine and I've made lots of mistakes. It is highly unlikely unless you try to flash something not meant for your device or something similarly bad.
I certainly haven't found CWM being recommended over TWRP - devs here tend not to recommend, just point things out; ALL choices are yours. There is always a risk but if you want to be safe then why are you here!
I first flashed TWRP because it was touch screen and had more options to back up partitions separately, such as EFS strangely enough; EFS partition contains the modem stuff. So you could archive your EFS and flash it back if any ROM overwrites it. ROM's are built from components and not everything has to be there - one of the brilliant things about Android is how it interfaces with all the different aspects of a mobile device - it appears to be one program running everything but it is extremely modular.
With external apk's I just copy them to external SD and install them on the phone.

Raubsau said:
Do I have to worry about dalvik and ART?
Click to expand...
Click to collapse
Forgot this bit!
No. You can elect to use ART in the system setting of some ROM's (certainly SLIM) and I know some people who do. However, ART is still under development and by no means are all apps ready for it yet. Xposed Framework itself will not work under ART and won't be for quite a while yet.

MarkAndroid.UK said:
There is always a risk but if you want to be safe then why are you here!
I first flashed TWRP because it was touch screen and had more options to back up partitions separately, such as EFS strangely enough; EFS partition contains the modem stuff. So you could archive your EFS and flash it back if any ROM overwrites it.
With external apk's I just copy them to external SD and install them on the phone.
Click to expand...
Click to collapse
I just want to minimize the risk, this phone was more expensive than the last one which had to take one or two for the team.
I will root with Odin as suggested here: http://forum.xda-developers.com/showpost.php?p=43622999&postcount=1
How do I delete the Knox stuff, then? Just flash CM11? I understood Knox is independent from ROM?
dalvik/ART: Good, I will not try to activate/use ART, then.

Raubsau said:
I just want to minimize the risk, this phone was more expensive than the last one which had to take one or two for the team.
I will root with Odin as suggested here: http://forum.xda-developers.com/showpost.php?p=43622999&postcount=1
How do I delete the Knox stuff, then? Just flash CM11? I understood Knox is independent from ROM?
dalvik/ART: Good, I will not try to activate/use ART, then.
Click to expand...
Click to collapse
Yes, those root instructions are good. The Knox issue shouldn't be a problem and you can deal with it post ROM flash by removing those files mentioned in your link. The flag will be tripped (it appears it is tripped if the bootloader is modified rather than just root but it is that sort of level) but that doesn't void the warranty in the EU anyway.
---------- Post added at 06:51 PM ---------- Previous post was at 06:43 PM ----------
Quick addition : No 7 in those instructions MUST be done otherwise I don't think you get root. It is tricky, just be prepared - it resets quickly. If you miss it I think you go back to no 3 again to get to download mode.

MarkAndroid.UK said:
Yes, those root instructions are good. The Knox issue shouldn't be a problem and you can deal with it post ROM flash by removing those files mentioned in your link. The flag will be tripped (it appears it is tripped if the bootloader is modified rather than just root but it is that sort of level) but that doesn't void the warranty in the EU anyway.
---------- Post added at 06:51 PM ---------- Previous post was at 06:43 PM ----------
Quick addition : No 7 in those instructions MUST be done otherwise I don't think you get root. It is tricky, just be prepared - it resets quickly. If you miss it I think you go back to no 3 again to get to download mode.
Click to expand...
Click to collapse
Alright, that went smooth. Now which GApps do I need? http://wiki.cyanogenmod.org/w/Google_Apps
If so, why not "small"?

Raubsau said:
Alright, that went smooth. Now which GApps do I need? http://wiki.cyanogenmod.org/w/Google_Apps
If so, why not "small"?
Click to expand...
Click to collapse
'Small' would be fine

MarkAndroid.UK said:
'Small' would be fine
Click to expand...
Click to collapse
I flashed CM11 M9, booted, installed Xposed Framework, installed XPrivacy and will now proceed to install the small GApps.
Thanks for your help

Raubsau said:
I flashed CM11 M9, booted, installed Xposed Framework, installed XPrivacy and will now proceed to install the small GApps.
Thanks for your help
Click to expand...
Click to collapse
That's great, have fun and you're welcome

Hello RaubSau
Have you successfully installed CM onto your Galaxy S4 mini black edition?
I intend to buy the 'black edition' too but I am worried whether the internals changed as it's a later model and hence CM wouldn't run on it...
black edition:
cdn2.gsmarena.com/vv/pics/samsung/samsung-galaxy-s4-mini-I9190-black-edition.jpg
"ordinary" black version:
cdn2.gsmarena.com/vv/pics/samsung/samsung-galaxy-s4-mini-I9190-1.jpg
Thanks a lot

soikku said:
Hello RaubSau
Have you successfully installed CM onto your Galaxy S4 mini black edition?
Thanks a lot
Click to expand...
Click to collapse
If the model number of the device you wish to buy is I9190 or I9195 then you can follow standard procedure.
Black edition is just cosmetic variation. Nothing special about that. Model number is always I9190/2/5.
So use normal procedure from threads in this forum. Good luck.

My phone looks like this:
cdn2.gsmarena.com/vv/pics/samsung/samsung-galaxy-s4-mini-I9190-black-edition.jpg
Info in the Settings menu says "GT-I9195".
As I was using XPrivacy fromt the start, some of these problems may have occured because of wrong restrictions:
- orientation of indicator in Google Maps shows wrong direction
- no compass app is working
I use my phone for calling, reading and writing mails, and remote control my media box. In the few cases I needed it for navigation, it worked fine (regardless of the wrong indicator).
Hope that helps.

Thank you for the replies, Raubsau and sasank360
Thank you for pointing out that the 'black edition' indeed is identical to the previous one internally.
I ordered the phone now and am looking forward to happy flashing (CM11 for the time being as freecyngn doesn't work for CM12 (yet)).

Working zip of Chinese stock rom for 6045I

First of all I am not a established developer still learning android system...... if anything creates problems after flashing this rom or after installing, dont blame me..
Proudly present the rom for Idol 3 6045I ported from it Chinese sibling TCL I806.
Fully working on my 6045I. Its stock 5.0.2 from TCL I806.
Many chinese apps have been removed but still few remains which can be removed by getting root.
Features:
1. Less Lags.
2. Fast.
3. Camera is working far better than the recent updates provided for 6045I.
How to install:
Caution : Before doing this, please make backup of your system & efs as mentioned by Famewolf in his thread of making backups.
1. Just download the zip from the link provided below and keep it in the root of sdcard.
2. Also download the gapps provided in the links. First link is which I installed on my device and second one is the latest. Keep it also in the root of the sdcard.
3. Now just boot into recovery mode i.e. TWRP , do not wipe anything, script will do it itself and just go to install and choose the stock chinese rom for 6045I.zip and flash.
4. Let the process to complete. It will ask to restart the system and just restart the system.
5. After first start choose language and other options, again boot into recovery mode and flash the gapps provided.
6. Here the stock chinese rom will run smoothly on your 6045I.
7. If TWRP gives error "error in executing binary" then you have to manually edit the updater-script but it depends on what your TWRP says about the error. So just ask me I will tell you what changes to make in updater-script.
After couple of manual restarts or with time rom will start to run smoothly.
Links :
Rom : removed due to some problems occurred after flashing.
gapps : https://www.androidfilehost.com/?fid=95784891001614559 or https://basketbuild.com/gapps (choose android 5.0).
For any kind of help regarding to this rom pm me or just ask in this thread.
I will try my best
Caution : Does not works on 6045Y & 6045K.
Backup efs also in case u loose ur IMEI or having error of unknown baseband/ no network
If you like my work, dont forget to hit thanks......
Sorry for all the trouble caused.
Well I am also in the same boat as well.....

yash_rathore25 said:
First of all I am not a established developer still learning android system...... if anything creates problems after flashing this rom or after installing, dont blame me..
Proudly present the rom for Idol 3 6045I ported from it Chinese sibling TCL I806.
Fully working on my 6045I. Its stock 5.0.2 from TCL I806.
Many chinese apps have been removed but still few remains which can be removed by getting root.
Features:
1. Less Lags.
2. Fast.
3. Camera is working far better than the recent updates provided for 6045I.
How to install:
Caution : Before doing this, please make backup of your system as mentioned by Famewolf in his thread of making backups.
1. Just download the zip from the link provided below and keep it in the root of sdcard.
2. Also download the gapps provided in the links. First link is which I installed on my device and second one is the latest. Keep it also in the root of the sdcard.
3. Now just boot into recovery mode i.e. TWRP , do not wipe anything, script will do it itself and just go to install and choose the stock chinese rom for 6045I.zip and flash.
4. Let the process to complete. It will ask to restart the system and just restart the system.
5. After first start choose language and other options, again boot into recovery mode and flash the gapps provided.
6. Here the stock chinese rom will run smoothly on your 6045I.
7. If TWRP gives error "error in executing binary" then you have to manually edit the updater-script but it depends on what your TWRP says about the error. So just ask me I will tell you what changes to make in updater-script.
After couple of manual restarts or with time rom will start to run smoothly.
Links :
Rom : https://mega.nz/#!88t2jJjT!dFpCY6987LAyAO2CcuKr0wmi5EPB3kRu9v8YTrNBgHs
gapps : https://www.androidfilehost.com/?fid=95784891001614559 or https://basketbuild.com/gapps (choose android 5.0).
For any kind of help regarding to this rom pm me or just ask in this thread.
I will try my best
May also work on 6045Y and 6045K : just need some willing hands.
If you like my work, dont forget to hit thanks......
Click to expand...
Click to collapse
Woohoo. Gonna download this!!!

For screenshots of rom visit this page : http://forum.xda-developers.com/idol-3/development/idol-3-source-code-available-t3180369/page14
Now going to sleep, as have to go office in morning......

Quick question. Can this rom read/write ExFat? I'd rather have my sd card formatted to that so that i can store larger movie files.

Are there any real noticeable differences besides less lag and fast? Those two mean almost the same thing. Does this ROM offer anything major that the US stock ROM doesn't? Awesome work though making a new ROM for the community to try. We appreciate your work. :good:

brian117 said:
Are there any real noticeable differences besides less lag and fast? Those two mean almost the same thing. Does this ROM offer anything major that the US stock ROM doesn't? Awesome work though making a new ROM for the community to try. We appreciate your work. :good:
Click to expand...
Click to collapse
One enhancement I read about was that it did have newer camera software. Many of the packages included are newer version levels than the ones included on our phones because the i806 came out after our models.
---------- Post added at 08:58 PM ---------- Previous post was at 08:45 PM ----------
yash_rathore25 said:
For screenshots of rom visit this page : http://forum.xda-developers.com/idol-3/development/idol-3-source-code-available-t3180369/page14
Now going to sleep, as have to go office in morning......
Click to expand...
Click to collapse
You should consider removing the system update checker from your custom rom. The icon appears in your screenshots so I'm assuming it's still included. Since the build.prop says it's a 6045i but it has the i806 codebase patches will never apply since the checksum's won't match.....so depending on what "version" it thinks it's on vs the update version the update checker will either never show an update or always show an update.

OK. I think I have this working. The ROM seems to be functional for me. Downloading all my apps now and getting it set up how I like. Will try to run it through the day tomorrow and see what I like and don't like... not expecting much difference over stock, but we'll see.

Anyone have a suggestion for a lollipop compatible "minimal gapps?" I'm really only interested in google play and gmail..no need for google+ etc.

famewolf said:
Anyone have a suggestion for a lollipop compatible "minimal gapps?" I'm really only interested in google play and gmail..no need for google+ etc.
Click to expand...
Click to collapse
I might still have a PA micro gapps file somewhere. Just need to see if it's 5.0 or 5.1.
Edit: Here you go. Just pick up the zero gapps. It works perfectly.
http://forum.xda-developers.com/showthread.php?t=2792842
Another option is the Slimgapps official thread here. They do have a "zero gapps" package, and both 5.x I think.
Sent from my 6045Y using XDA Free mobile app

yash_rathore25 said:
May also work on 6045Y and 6045K : just need some willing hands.
Click to expand...
Click to collapse
You mean testers?
Sent from my 6045Y using XDA Free mobile app

Anghirrim said:
You mean testers?
Sent from my 6045Y using XDA Free mobile app
Click to expand...
Click to collapse
Yupp bro.
Just edit build.prop with notepad++ and change it to 6045Y instead of 6045I and flash the rom.
Then check the log of TWRP specially before the error in executing updater binary.
It will say something about the check_cu.
If you will open updater script with notepad++ you will see first line of command saying "check_cu("6045I-2AALUS7");"
Just change this line ("6045I-2AALUS7") with the line shown in the TWRP similar to this ( something like 6045Y-XXXXXXX)
Then again flash the rom, gapps and hope it will work.
If it works, dont forget to hit thanks button :laugh:

Ok... I'll see, my phone is less than one week old and I swore myself that this one would be kept untouched for a year. I wanted to keep it clean for warranty purpose but one week later... I'm already rooted.
I'm kind of flashaholic so won't resist very long... Don't worry.
What will it update exactly? Is there a risk it will mess up the European radio part? Just to make sure I'll still get a good signal or loose imei.
I do have my twrp backup for boot and system image, will that be enough to get back to a previous working state?
Thanks,
Sent from my 6045Y using XDA Free mobile app

Anghirrim said:
Ok... I'll see, my phone is less than one week old and I swore myself that this one would be kept untouched for a year. I wanted to keep it clean for warranty purpose but one week later... I'm already rooted.
I'm kind of flashaholic so won't resist very long... Don't worry.
What will it update exactly? Is there a risk it will mess up the European radio part? Just to make sure I'll still get a good signal or loose imei.
I do have my twrp backup for boot and system image, will that be enough to get back to a previous working state?
Thanks,
Sent from my 6045Y using XDA Free mobile app
Click to expand...
Click to collapse
I rooted my phone the next day it came to me,
Eventually i am also not going to get warranty as I imported this device from US to India.
N I personally dont care about warranty as none of the android device gets bricked completely, there is always a way.
Like I got stucked in bootloops in try of porting cm12.1 from other device.Even my backups failed to boot. Then I followed the mobile updater app provided by Alcatel and it simply restored my device to factory rom which will get updates also.
N warranty will not work if the device got physically damaged.
Yes backup will work.
After flashing this rom I would suggest you to make TWRP backup of this rom also alongwith Stock one.
I am getting a lot of range in network selection as it contains all the radios available for this device.
Screenshots of network range:

Anghirrim said:
Ok... I'll see, my phone is less than one week old and I swore myself that this one would be kept untouched for a year. I wanted to keep it clean for warranty purpose but one week later... I'm already rooted.
I'm kind of flashaholic so won't resist very long... Don't worry.
What will it update exactly? Is there a risk it will mess up the European radio part? Just to make sure I'll still get a good signal or loose imei.
I do have my twrp backup for boot and system image, will that be enough to get back to a previous working state?
Thanks,
Sent from my 6045Y using XDA Free mobile app
Click to expand...
Click to collapse
It's much safer to mod now since with Version 4.9.2 of the Mobile Q software from alcatel (you have to tell it you have a "pixi" for that version to appear as it's so new) allows you to put the phone in "download mode" and fully restore the device to factory condition. (tested by multiple idol 3 users of both the 6039 and 6045) This goes a long way towards making the device unbrickable.

famewolf said:
It's much safer to mod now since with Version 4.9.2 of the Mobile Q software from alcatel (you have to tell it you have a "pixi" for that version to appear as it's so new) allows you to put the phone in "download mode" and fully restore the device to factory condition. (tested by multiple idol 3 users of both the 6039 and 6045) This goes a long way towards making the device unbrickable.
Click to expand...
Click to collapse
I agree with you bro......:good::good:

Thanks both for your answers. Yes the Alcatel restore software makes things way easier to fix. I already installed it yesterday to make sure my phone drivers are installed for any "phone state". I also have the android sdk installed.
By the way, I am thinking to bring my small contribution to this forum by creating an " ultimate list of mods/softwares/issues" for this phone.
There have been so many news and achivements in the past few weeks, it's a bit difficult to read everything in the correct order.
So last question, how about the radio, imei, etc... Any risk on this?
And then, I think I'll give it a try.
Sent from my 6045Y using XDA Free mobile app

Anghirrim said:
Thanks both for your answers. Yes the Alcatel restore software makes things way easier to fix. I already installed it yesterday to make sure my phone drivers are installed for any "phone state". I also have the android sdk installed.
By the way, I am thinking to bring my small contribution to this forum by creating an " ultimate list of mods/softwares/issues" for this phone.
There have been so many news and achivements in the past few weeks, it's a bit difficult to read everything in the correct order.
So last question, how about the radio, imei, etc... Any risk on this?
And then, I think I'll give it a try.
Sent from my 6045Y using XDA Free mobile app
Click to expand...
Click to collapse
In my opinion no risk of losing imei no. and radio modems

yash_rathore25 said:
In my opinion no risk of losing imei no. and radio modems
Click to expand...
Click to collapse
I'm attaching a platform.xml file already modded to allow full read/write access to the external sd (just drop the .zip off the filename as that was just to get xda to allow me to upload it...it's a text file)....you might find it useful to replace this in yours.(/etc/permissions)..other options include pre-rooting...adding in init.d support....etc.

Ran this ROM overnight and through most of my day so far (about 3 hours off the charger). First impression is that it's about the same as stock, not that I was expecting any different. You get the TCL splash screen at boot but the overall UI is pretty much the same. Since I now have root I went ahead and used app quarantine to freeze the bloatware apps I didn't want. Kinda wishing I had installed minimal gapps, but I figure I'll be reflashing again soon since the floodgates are probably about to open with new ROMS anyway.
Conclusion: If you're curious, flash it, it doesn't hurt anything. It may be a hair smoother, and I haven't really tested the camera extensively enough before or after to be able to tell a difference.
Edit: Literally as soon as I submitted this message (from my PC) I went to turn wi-fi off and the phone decided to reboot. Really odd.

@nickalltogether:
Which version of the phone do you have?
Sent from my 6045Y using XDA Free mobile app

Updated Magisk Manager - NOW BRICKED?!

Hello all!
This morning I updated Magisk Manager.
Once updated (or perhaps only downloaded update) the app prompted a reboot.
I rebooted and ended up in TWRP.
But I did not know what to do in TWRP so I rebooted system...
However, now the phone cannot boot and after one try it reboots into TWRP again.
PLEASE HELP ME!
I need my phone for work! Like now-now! :silly: :crying:

dustylambo said:
Hello all!
This morning I updated Magisk Manager.
Once updated (or perhaps only downloaded update) the app prompted a reboot.
I rebooted and ended up in TWRP.
But I did not know what to do in TWRP so I rebooted system...
However, now the phone cannot boot and after one try it reboots into TWRP again.
PLEASE HELP ME!
I need my phone for work! Like now-now! :silly: :crying:
Click to expand...
Click to collapse
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504

timbernot said:
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
Click to expand...
Click to collapse
Well, that rabbit went into quite the hole... hehe
However, at the other end was a person who restored an old backup to revert this problem... And I -MAYBE- have an old backup on my external hdd, but won't that wipe all data that has been written to my phone since that "MAYBE" backup?
The other suggestion was wiping my MISC-partition using commands through ADB - something I have no clue how to setup and/or execute.
Still, thank you so much for your effort!
Reading all of this made me remember that one time I spaced out and tried to install an official firmware update upon release and prompt, which lead to the same issue. I could then just reinstall an older raw firmware version, which left all my files and data intact. Hopefully this will work here too.
BUT... It still feels very risky. If anyone out there has any sure-fire solution to this update Magisk Manager through the built-in updater no-boot issue, then please feel free to let me know - I would be forever in your debt

The best surefire solution is just don't. And BTW always backup before you flash anything in twrp.
Sent from my ASUS_Z00A using Tapatalk
---------- Post added at 08:49 AM ---------- Previous post was at 08:47 AM ----------
timbernot said:
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
Click to expand...
Click to collapse
I love what you did there! Lol
Sent from my ASUS_Z00A using Tapatalk

kenbo111 said:
The best surefire solution is just don't. And BTW always backup before you flash anything in twrp
Click to expand...
Click to collapse
I didn't flash anything in twrp. If you're gonna reply at least read the post. Also, none of what you wrote is a solution, unless you're in possession of a time machine. I'll keep it in mind for the next time though (of which there won't be one). Thanks, captain hindsight.

dustylambo said:
I didn't flash anything in twrp. If you're gonna reply at least read the post. Also, none of what you wrote is a solution, unless you're in possession of a time machine. I'll keep it in mind for the next time though (of which there won't be one). Thanks, captain hindsight.
Click to expand...
Click to collapse
That's what the update does. Reboots to twrp and installs the download. Maybe you should know what you're doing before you snap at us.
Sent from my ASUS_Z00A using Tapatalk

dustylambo said:
However, at the other end was a person who restored an old backup to revert this problem... And I -MAYBE- have an old backup on my external hdd, but won't that wipe all data that has been written to my phone since that "MAYBE" backup?
Click to expand...
Click to collapse
No, just restore the boot partition (16MB).
I learnt the hard way about backup, when years ago I didn't make one for my Galaxy S2 and lost everything (pictures, etc). Now after installing TWRP I always do a backup...
You should be able to reflash your boot partition with a fastboot command like "fastboot flash boot boot.img" (people with more knowledge than me can help you)
EDIT: the problem is that our Zenfone2 needs a signature for the boot partition, this is why we have a special Magisk installer that just add the signature to the image. The automatic update installer of Magisk has no clue about this, me and a few others here made the same mistake as you when Magisk popup "I have an update!" and we clicked "Install"...
All your data and app are still there, do not worry, no need to wipe anything, just reflash a signed boot.

kenbo111 said:
That's what the update does. Reboots to twrp and installs the download. Maybe you should know what you're doing before you snap at us.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Look... I am sorry if I "snapped" as you put it... But let's make one thing clear - I snapped at YOU; there is no "us" in this case, as you tried to skew it. Don't lump yourself together with these other helpful people, because so far you have nothing in common to me. If I were looking for someone to go "Hey, I got a solution - you know that thing you did? - Don't do it again!" I'd just go stand on the street corner with a sign asking for someone to slap my face.
As for your principal of don't do things if your not sure of how they work, I am totally behind that. But it has NOTHING to offer here as we are past that point. A broad comparison would be like "a solution to world hunger = eat food" ("but we don't have any food!" "you should have thought of that before you started starving now shouldn't you...?!").
In your defense, I guess you really believe you are trying to help. But compare your comment to the other ones posted and it is quickly clear that you are not. However, YOU ARE RIGHT, I should've known better and shouldn't do it again. And obviously I am enerved at this situation, but equally obvious (now) is that what you wrote is NOT "the best sure-fire solution" as what was posted afterward seems at least 100% (would have been more if possible) more applicable to my issue.
Anyway, I'll do the right thing here in the end, after having said so many things, and admit, once again, that I was wrong, you were right, I snapped for no good reason and you were just trying to help.
And I sincerely apologize for my rude behaviour. Hopefully now you can at least understand my reaction.
Also, fair is fair - Maybe TWRP flashes the update before it even enters into it. It would be the first I've EVER heard of something like that. But I am out of my element a bit here, so I will withdraw that comment and once again apologize for snapping at you because of it.

Magister54 said:
No, just restore the boot partition (16MB).
I learnt the hard way about backup, when years ago I didn't make one for my Galaxy S2 and lost everything (pictures, etc). Now after installing TWRP I always do a backup...
You should be able to reflash your boot partition with a fastboot command like "fastboot flash boot boot.img" (people with more knowledge than me can help you)
EDIT: the problem is that our Zenfone2 needs a signature for the boot partition, this is why we have a special Magisk installer that just add the signature to the image. The automatic update installer of Magisk has no clue about this, me and a few others here made the same mistake as you when Magisk popup "I have an update!" and we clicked "Install"...
All your data and app are still there, do not worry, no need to wipe anything, just reflash a signed boot.
Click to expand...
Click to collapse
NOW THIS IS HELPING!
THANK YOU SO MUCH!
Basically, you are saying that I would, in theory, just have to use fastboot and flash boot.img (extracted from any firmware?) again, which I am very familiar with how to do, and presto - boot partition restored and working (once again, in theory)?
Sounds amazing!:good:

dustylambo said:
NOW THIS IS HELPING!
THANK YOU SO MUCH!
Basically, you are saying that I would, in theory, just have to use fastboot and flash boot.img (extracted from any firmware?) again, which I am very familiar with how to do, and presto - boot partition restored and working (once again, in theory)?
Sounds amazing!:good:
Click to expand...
Click to collapse
Yes, if you have a Z00A for instance with MM version 223, take the Z00A.zip file from https://forum.xda-developers.com/zenfone2/general/bl-unlock-ze551ml-toolkit-t3546293 and use the file stock\z00a\223\boot.img

This is stock unsigned boot.img file for M .223
http://www.mediafire.com/file/rw73099svgbv0kv/boot.img

timbernot said:
boot.img file for M .223
http://www.mediafire.com/file/rw73099svgbv0kv/boot.img
Click to expand...
Click to collapse
Is there any way to check from TWRP or using fastboot, or otherwise find out what version of the rom I have (had)?
I am definitely still on LolliPo... I think I am one or two official updates from the switch to MarshMallow... But how can I be sure?

WW_ZE551ML_2.20.40.139_sal358-amtech.vn
Last year sometime I ran into a similar problem, where I had to flash raw firmware in order to unbrick the phone... This is the firmware that I downloaded and flashed then.
However, within this .raw-file there is no boot.img ...? There are a couple of .img-files, but none named boot.
On a side-note: When I bricked it last year and had to flash this raw firmware, which I did with Asus Flash Tool, if I am not mistaken... However, whichever way I did it, I managed to flash and then boot as usual. The phone then updated all apps, and I was just blessed with this wonderful sight of "my phone" with all the apps, files and data still intact.
And this problem, which resulted in the same boot issue, came from trying to apply an official OTA update, just after rooting and unlocking the bootloader (forgot myself for just a moment there), which to me seems like a way more serious screw-up than what I just managed to do today...?

@dustylambo
You still boot to TWRP ?
Simple questions
check date of back ups , course you won't be able to restore but title will have builds.
What twrp build ?
Then....
Select reboot in twrp then power off in twrp .
Wait 15 seconds...
Power plus vol+ , you can now boot to bootloader.
What IFWI version ?
0094.0177 or .0173 is LP
0094.0183 is M
Flash relevant raw , without ticking wipe data in AFT.
Check my unbrick thread in my signature for AFT and links to raws
Enjoy

timbernot said:
@dustylambo
You still boot to TWRP ?
Simple questions
check date of back ups , course you won't be able to restore but title will have builds.
What twrp build ?
Then....
Select reboot in twrp then power off in twrp .
Wait 15 seconds...
Power plus vol+ , you can now boot to bootloader.
What IFWI version ?
0094.0177 or .0173 is LP
0094.0183 is M
Flash relevant raw , without ticking wipe data in AFT.
Check my unbrick thread in my signature for AFT and links to raws
Enjoy
Click to expand...
Click to collapse
Yes, I still boot into TWRP.
I can't find my old backup for some reason, but after flashing the previously mentioned raw firmware I never up- or downgraded the ROM, so it MUST be that version. It's the only one I've ever downloaded and flashed.
IFWI version is 0094.0183
But so you are saying I could basically just flash [correct version FW].raw via AFT, without wiping data, and all should be good?
I am on your unbrick thread aws.
I will def bookmark it.
But I already have AFT and the same FW... so I could just go-go-go, right? Or is the IFWI version being M an issue?
Also, I downloaded the official Asus FW from their ZF2 website. In that .zip is in fact a "boot.img" - can I flash this via fastboot you think?
Thanks again for all your help!
You are unbelievable!

@dustylambo
0094.0183 is M
So flash a M raw.
You must've upgraded bootloader since flashing the last raw .139 which is LP to get to M bootloader .0183
In bootloader .0183
You flash raw for M, these have just been added by realyoti
drop him a thanks .
Flash without ticking wipe data in AFT

Damnit! I don't like where this is going... But it's late and I'm dumb
I never upgraded to M because I read that there were several apps that would lose support, MUSIC in particular, but there were others as well.
Will an M raw-file flash and still boot with all my old apps?

@dustylambo
It's simple really , what is the twrp build number ?
You never said
0094.0177
Is locked 5 LP bootloader.
.0173 is 5 unlocked bootloader
.0183 is M
What twrp build is yours ?
Ps , I don't think it matters which version raw you flash , only that it may fail and might have to wipe data to succeed which is better than what you have and are struggling with right now
gnite , enjoy
---------- Post added at 11:45 PM ---------- Previous post was at 11:30 PM ----------
Pls , remember the reason you installed twrp initially ?
For backing up

Sounds like you didn't only update Magisk Manager, you update Magisk itself. A non-signed Magisk update will always result in bootloop.

adobrakic said:
Sounds like you didn't only update Magisk Manager, you update Magisk itself. A non-signed Magisk update will always result in bootloop.
Click to expand...
Click to collapse
To be corrected: Not the Magisk, but the repacked boot.img. ?
Sent from my Redmi 3 using XDA Labs