Database Users

[Guide] Restore Idol 3 back to factory ROM

Hi all! I know that Mobile Upgrade Q is long gone and I have a program that will reset your Idol 3 back to factory settings with the factory ROM. I have used this program in the past, but unfortunately I no longer have the device.
What you will have to do is download the program available here: https://drive.google.com/open?id=1Sd99aiZIL8JSpXwAiwGitulNFbJxi2Z4
After downloading there will be a folder named "SUGAR QCT_SP v11.1.2" open this folder and use the setup installer to install the program. After installing (assuming you have the necessary usb drivers installed that can also be found within the folder but I assume many of us have it already installed) open the program "SUGAR QCT_SP_Gotu2" which if memory serves me correctly, will be placed on the desktop.
Note that you will have to have your device connected to the computer prior to launching the application.
A window will pop up asking you for a username and password. The username and password can be found in the downloaded folder in a file named "sugarpw". The user name is "SU_IN.Panasonic" without quotations and the password is "KoD8naL2".
If any window pops up regarding updates to the program, do not update it as it can cause complications when trying to restore. After this point I cannot remember much of the program because as you need your device to be connected in order to access it, I cannot see it personally. From what I remember there is a drop-down box in which you will need to select your model of Alcatel device. Then there will be two buttons from what I remember. "Get root status" (or something along the lines of this maybe "check root" I am not sure) you need to press the Upgrade or Restore button. I am not sure past this point but I assume someone can comment on this procedure exactly but this should be enough to get you through the process.
~Jason

hello, first time i write here after long time reading about idol3 recovery, i was almost out of ideas, my 6039k dual sim (italy) got bricked hard as couldn't do any backup, no usb debug no adb no custom recovery, plus alcatel do not share stock rom so this software and chewyboy0 saved my phone. thank you very much. Stefano

thank u a lot you saved my phone i was not able to restore my 6045k dual sim and i was having twrp recovery but there is no roms for dual sim 6045k exept cyanogenmod 12 which was making a lot of problems glitches very annoying . by the way it after your instruction no much left behind the most important thing is after connecting your phone usb put the phone in download mode manually by pressing volume up and down with usb connected after turning your phone off till download screen popup then press volume up continuously till screen turn off , the program can not go to download mode automatically so do it manually then press upgrade in program then screen will popup asking u are u sure u want to install this rom with firmware num etc... agree and wait till it done .thank a lot chewyboy0 god give u the right path and keep u happy in life and last thanks again

Just wanted to share my experience. I actually had to upgrade the software in order to get my 6045O from cricket to restore it back to the original cricket MM. In fact, before I upgraded the software it just said 6045 and afterwards it showed multiple versions of the 6045 including the 6045O. Anyways, I just booted into download mode and pressed upgrade and waited 30 minutes. After setting my phone up I went ahead and used Alcatel Flasher to install TWRP and root my phone again.
I was beginning to give up hope. Before updating the software I kept getting model mismatch error. Had already used Eluga, which dumped by Lte for HSPA+ and I tried flashing every radio possible, which only made it worse to where the sim wasn't detected.

If you can help, on the Alcatel website it was necessary for the idol 3 Mobile_Upgrade_Q_5.1.8_Setup.exe and in fact contact me with Alcatel support and the only thing they told me was that I had to send it, but it had a cost, and My last option was to do the trial and error, so I saved it with the Mobile_Upgrade_Q_5.1.7_Setup.exe and it worked.
Note:
My idol 3 is 6045I
Android 5.0.2
I also use Google translator, I do not know English

It worked for me!
Before opening the program "SUGAR QCT_SP_Gotu2" I had to put my mobile in "Download Mode"...
Step by step:
1: Download the program available in the link posted in the threat;
2: Extract the downloaded zip file and open the "SUGAR QCT_SP v11.1.2" folder, then setup installer to install the program;
1: Turn off your device completely and connect it to your computer with a USB cable;
2: Put your mobile in "Download Mode". For Alcatel Idol 3 6039J, push and hold the Power and Both the Volume Buttons, a Red Screen should appear in your mobile, then release all buttons and quickly hold the Volume Up Button until the screen turns Black;
3: Open the program "SUGAR QCT_SP_Gotu2" which will be placed on the desktop (when asked, allow windows administrator privileges);
4: Enter with username (SU_IN.Panasonic) and pw (KoD8naL2), click on "OK" button;
5: Click "No" to quit updating;
6: Select your device model in "Product Models" list (6039 for Idol3 4,7");
7: Click in "Upgrade" button and wait until the end (it takes a while for downloading the firmware and writing it into your device);
8: Your device should restart automatically running the stock ROM.
9: Have fun

Hi
I tried the app but it says it's wrong password...
Don't you know any other solution ?
Thanks a lot

newbie_or_not_newbie said:
Hi
I tried the app but it says it's wrong password...
Don't you know any other solution ?
Thanks a lot
Click to expand...
Click to collapse
Same for me:
Error code = 401 Wrong server location, user name or password

Same situation here - error 401, anyone got an update ?

Hi
I could restore with Mobile Upgrade Q 5.1.8
Available on alcatel-mobile.com
Idol 3 was restored to Marshmallow, so I don't know if root is possible after restoring.

johnnybelite said:
Just wanted to share my experience. I actually had to upgrade the software in order to get my 6045O from cricket to restore it back to the original cricket MM. In fact, before I upgraded the software it just said 6045 and afterwards it showed multiple versions of the 6045 including the 6045O. Anyways, I just booted into download mode and pressed upgrade and waited 30 minutes. After setting my phone up I went ahead and used Alcatel Flasher to install TWRP and root my phone again.
I was beginning to give up hope. Before updating the software I kept getting model mismatch error. Had already used Eluga, which dumped by Lte for HSPA+ and I tried flashing every radio possible, which only made it worse to where the sim wasn't detected.
Click to expand...
Click to collapse
newbie_or_not_newbie said:
Hi
I could restore with Mobile Upgrade Q 5.1.8
Available on alcatel-mobile.com
Idol 3 was restored to Marshmallow, so I don't know if root is possible after restoring.
Click to expand...
Click to collapse
Hello,
Restoring via Mobile Upgrade Q isn't option for me ...i've tried multiple times.
Thank you !

dan1t000 said:
Hello,
Restoring via Mobile Upgrade Q isn't option for me ...i've tried multiple times.
Thank you !
Click to expand...
Click to collapse
Just 3 weeks ago, I was able to restore (in Canada) my Idol 3 to stock MM using Mobile Upgrade from download mode (I think it was version 5.1.7 as 5.1.8 would not do anything).
Here is a download link:
5.1.7:
https://mega.nz/#!KmogkYAa!e5y6ZSM98...jANMglrhB4rtHo
5.1.8:
https://mega.nz/#!OuhEGaaQ!g6mH6RE7v...qh1fmCtHzhHptI

Thanks a lot mate!

tess1 said:
Just 3 weeks ago, I was able to restore (in Canada) my Idol 3 to stock MM using Mobile Upgrade from download mode (I think it was version 5.1.7 as 5.1.8 would not do anything).
Here is a download link:
5.1.7:
https://mega.nz/#!KmogkYAa!e5y6ZSM98...jANMglrhB4rtHo
5.1.8:
https://mega.nz/#!OuhEGaaQ!g6mH6RE7v...qh1fmCtHzhHptI
Click to expand...
Click to collapse
mega says enter decryption key ???
but thanks to you mentioning the version i managed to google and download it

Hi all, I wrote a 2022 update on how to put the non-responsive phone into a fastboot state. You can find it here:
[TOOL] Sahara & Firehose Test (Alcatel Flasher oncoming ...)
Let me introduce some new tool for you. This is my first practice in learning and understanding "How to work with Sahara & Firehose?" and as an owner of Alcatel Idol 3 4.7" firsts test of this app were made on my Idol 3 6039Y. What is this...
forum.xda-developers.com

Shield TV won't accept Google login credentials

I received a new (to me) 2017 Shield via RMA from nVidia. I plug it in and go to set it up but when I get to entering your google account info, it consistently fails. The option to use androidtv dot com/setup and enter the provided PIN fails with "Something went wrong" (yes I'm on the same wifi, also fails when wired). The option to type in your account credentials also consistently fails saying my user name and password don't match. Now before you say "learn 2 type", immediately after not logging in, I get a security notification saying a new device has logged in to my account. This same result happens with any gmail account I try. I have factory reset the Shield (as instructed by nVidia support) to no avail. I have contacted Google support but they say it's nVidia's problem. I'm not sure what to do next. Any suggestions would be greatly appreciated.

Jesterium said:
I received a new (to me) 2017 Shield via RMA from nVidia. I plug it in and go to set it up but when I get to entering your google account info, it consistently fails. The option to use androidtv dot com/setup and enter the provided PIN fails with "Something went wrong" (yes I'm on the same wifi, also fails when wired). The option to type in your account credentials also consistently fails saying my user name and password don't match. Now before you say "learn 2 type", immediately after not logging in, I get a security notification saying a new device has logged in to my account. This same result happens with any gmail account I try. I have factory reset the Shield (as instructed by nVidia support) to no avail. I have contacted Google support but they say it's nVidia's problem. I'm not sure what to do next. Any suggestions would be greatly appreciated.
Click to expand...
Click to collapse
I have the same problem. Did you manage to get this fixed by chance?

Yes. I fixed it by flashing a recovery image. 8.0.1 just caused a boot loop but flashing 8.0 worked.
https://developer.nvidia.com/gameworksdownload

Jesterium said:
Yes. I fixed it by flashing a recovery image. 8.0.1 just caused a boot loop but flashing 8.0 worked.
https://developer.nvidia.com/gameworksdownload
Click to expand...
Click to collapse
Thanks for getting back to me. I assume that to flash a recovery image, I'll need to unlock the bootloader? I was trying to avoid flashing, but it doesn't look like another solution will work...

Aripex said:
Thanks for getting back to me. I assume that to flash a recovery image, I'll need to unlock the bootloader? I was trying to avoid flashing, but it doesn't look like another solution will work...
Click to expand...
Click to collapse
I tried quite literally everything I could think of - multiple google accounts, different networks including hot-spotting my cell service, multiple factory resets. It seems my problem may have been a very outdated OS as after I was able to flash, the setup process was in a newer android style. It didn't occur to me that what I was seeing previously was "old" and may explain why it wouldn't connect to google.
Keep in mind, you can lock the bootloader again when you're finished.

Jesterium said:
I tried quite literally everything I could think of - multiple google accounts, different networks including hot-spotting my cell service, multiple factory resets. It seems my problem may have been a very outdated OS as after I was able to flash, the setup process was in a newer android style. It didn't occur to me that what I was seeing previously was "old" and may explain why it wouldn't connect to google.
Keep in mind, you can lock the bootloader again when you're finished.
Click to expand...
Click to collapse
Cool - thanks for the advice. Like you, I tried everything too. I tried 2FA on/off, turned on the "Less secure apps" option in my Google Account > Security. I also tried to factory reset without any success, as well as using a different Wi-Fi network and opened a new dummy Google Account just to make sure my original account wasn't the problem! None of it worked and had me tearing my hair out.
I have a 2015 Shield TV that was sealed and unused until the last week. I have never seen an issue before where even an older Android device cannot be signed into Google. At least it is a lesson learned for the future....!
Anyway, I've successfully flashed a newer version of Android now and it works. Hallelujah!

Right guys I have just got a replacement NVidia pro 500gb from them for a bricked unit and I am having the same problem. As I am a novice I have no clue about flashing an updated image to it. Is there anyone who is will to spell it out for me in easy to follow instructions??

Device not starting/black screen after stock-ROM flash via Odin

Hello, everyone,
I tried to install LineageOS on my S10 Plus yesterday. That worked so far, but I found that it didn't have a decent camera app and the Samsung Watch wasn't that easy to connect either. So I thought I'd just go back to the Stock ROM again. I then downloaded the latest stock firmware according to this guide and installed it with Odin. The installation also runs through, after the installation the mobile phone starts and after the start screen there is an Android man with the signature "Erasing". After a few seconds, the device turns off and stays black. Even if I put it on the charger or try to restart it, nothing happens. I keep getting into download mode and recovery, but that's about it. Multiple reinstallations and resets via the recovery didn't help - the phone just won't start.
I used the CSC_... and not the HOME_CSC_... at the firmware is the right one for my phone.
Is there any way I can salvage the device? I'm afraid that something in the memory is defective now, which has nothing to do with the flashing itself. Do you have any ideas?
Many thanks!

tefracky said:
Hello, everyone,
I tried to install LineageOS on my S10 Plus yesterday. That worked so far, but I found that it didn't have a decent camera app and the Samsung Watch wasn't that easy to connect either. So I thought I'd just go back to the Stock ROM again. I then downloaded the latest stock firmware according to this guide and installed it with Odin. The installation also runs through, after the installation the mobile phone starts and after the start screen there is an Android man with the signature "Erasing". After a few seconds, the device turns off and stays black. Even if I put it on the charger or try to restart it, nothing happens. I keep getting into download mode and recovery, but that's about it. Multiple reinstallations and resets via the recovery didn't help - the phone just won't start.
I used the CSC_... and not the HOME_CSC_... at the firmware is the right one for my phone.
Is there any way I can salvage the device? I'm afraid that something in the memory is defective now, which has nothing to do with the flashing itself. Do you have any ideas?
Many thanks!
Click to expand...
Click to collapse
same thing happened to me today. but I flashed my s10e the bootloader and modem file of android 9 from twrp, the phone did not boot up and I loaded the stock rom again, then when I open it, it's the same as yours, I really need urgent help.
Releases · corsicanu/9820-bootloaders_and_modems
Contribute to corsicanu/9820-bootloaders_and_modems development by creating an account on GitHub.
github.com
EDİT: Anyway, I solved the problem, I flashed the bootloader and modem file that is suitable for my current version from the same site with twrp and the phone turned on. maybe you can solve it by flashing the bootloader and modem file suitable for the current version. try if you want

Thanks a lot, this worked!

tefracky said:
Thanks a lot, this worked!
Click to expand...
Click to collapse
I'm glad it worked.
I was very afraid that the phone died, what did you do for 5 days in this state?
Now I have a question in my mind: When Samsung releases an update in the future, will the bootloader and modem files be updated when we update it with odin? won't it be updated? After that, do we will always update manually as twrp? do you have any idea?

Well, I simply didn't use a mobile phone in these days. It was a very "interesting" experience, but not a huge problem. I sometimes opened WhatsApp as Windows App (interestingly, which works without phone).
I don't know, what happens at a Samsung Update, but until Android 13, I will not update (so probatly never). In our German forum (www.android-hilfe.de), a pre rooted and debloated "Stock"-Firmware is provided, but I can't install it, since my Bootloader is too new (V15 instead V14 for the ROM). When it is possible, I will install this firmware. If you are interested, here is the link: https://www.android-hilfe.de/forum/...3-2022-stock-rom-v2-0-pre-rooted.1000713.html

tefracky said:
Well, I simply didn't use a mobile phone in these days. It was a very "interesting" experience, but not a huge problem. I sometimes opened WhatsApp as Windows App (interestingly, which works without phone).
I don't know, what happens at a Samsung Update, but until Android 13, I will not update (so probatly never). In our German forum (www.android-hilfe.de), a pre rooted and debloated "Stock"-Firmware is provided, but I can't install it, since my Bootloader is too new (V15 instead V14 for the ROM). When it is possible, I will install this firmware. If you are interested, here is the link: https://www.android-hilfe.de/forum/...3-2022-stock-rom-v2-0-pre-rooted.1000713.html
Click to expand...
Click to collapse
thanks, if i'm going to use stock rom i prefer to root it myself

some basic questions on sm-t235 re: root/custom rom/custom recovery

Hi,
the other day a friend gave me her old Samsung tab 4 7.0 (SM-T235). It's in its default state, running Android 5.1.1 stock ROM with all the most recent (5 year old) updates. "KNOX" appears to be ok, afaik.
This is my first Samsung device, up to the date I had experience with HTC Desire, Sony Xperia (2x) and OnePlus devices. I unlocked / rooted and installed custom ROMs on all of them.
Done quite a bit of googling and playing around with my "new" Samsung to see where it's different compared to my other devices. But there still are some blank spots, and there doesn't seem to be too much information out there regarding that specific tab 4 device. Before I start messing around I'd love to have some input from experienced Samsung users in regards to custom recoveries and ROMs, and possibly rooting. If there are comprehensive guides etc. out there that I simply didn't find don't hesitate to give me some hints:
First of all it appears to me that this device is going under the codename "degas". Correct? (meanwhile confirmed)
I hooked up the device to my PC, made sure that adb found it alright, then called "adb reboot recovery". That worked nicely, got me into Samsung recovery
Next I again tried to connect through ADB to the device still being in recovery, but that didn't work. To be expected?
Still in recovery I chose the "boot to bootloader" option, but that got me back into system instead.
So from system I again connected to adb then called "adb reboot bootloader". Device booted alright, but again it just rebooted into system.
>> Is there really no way to get into bootloader?
Trying to find out what has to be done in order to flash a custom ROM (rooted or not): from what I get, and unlike my other devices, I do not have to unlock the device / bootloader to begin with. It looks as if it was sufficient to boot into what they call "download mode", then hook up the device to my PC where ODIN is waiting already. Following this thread (and others) it then is sufficient to just flash TWRP from ODIN, boot to recovery and then do what is usually done here (like flash custom ROM, flash Gapps and possibly Magisk etc.). Is there something else / important I should know / observe?
Speaking about TWRP and Custom ROMs: TWRP.me lists that device on their site. So has anyone here flashed latest TWRP (3.6.2_x)? Or should I rather start with an older version like the one listed here, then possibly upgrade from there?
In regards to Custom ROMs I basically just found this LOS 16 thread (which is the same linked in the previous "TWRP" bullet). I assume that's it, or does anyone know about a newer android version (which I didn't find so far)? There seems to be lots of activity around "matisse" and "millet", but apparently those aren't the right devices, right?
Back to recovery: I see that in stock recovery there is an option to "wipe data/factory reset": should I do that before flashing TWRP from ODIN, or is it sufficient to wipe everything once I booted into TWRP?
I'm aware that I'll lose "Knox" as soon as I flash a different ROM / Recovery. As I don't want to use the tab 4 in some critical "BYOD" area I don't care (neither do I care about warranty, that's long gone anyways). But just to be sure: is it true that I'll lose "Knox" access?
In case I would decide to "go back" to stock ROM one day, how would I proceed then? Would ODIN still work so that I can flash latest stock ROM? Would Knox then be restored, or is that a thing of the past once I leave the stock ROM path?
Again: if you think I've done a bad job searching for answers don't hesitate to let me know but please be so kind then to hint the phrases I should look for ("SM-T235" really doesn't bring up that much valuable info)
Thanks and cheers
Update 2022-08-03: meanwhile I realized that the device is connected to my PC through generic drivers. Would it help to install specific Samsung drivers although both ADB and ODIN are acknowledging the device? Or can I just neglect that?

Since no answers came in I dared to just try. Meanwhile I'm running the device on LOS 16 with TWRP 3.5.2_9. Then flashed MindTheGapps (arm/Android 9 flavour)The switch wasn't as easy as I expected for some reason not obvious to me (somehow I couldn't get into TWRP after flashing it through ODIN. Then after the ~25th attempt it suddenly worked). Meanwhile I installed the official Samsung drivers, and maybe that helped, in combination with other adjustments I lost trace of...
I'll answer some of the above questions, for anyone who's interested:
#3: while in recovery (TWRP 3.5.2, as it is now) I still cannot access the device through adb. But I have access from windows' file explorer, so at least I can exchange files while being in recovery. Strange thing, this is the only one of my devices that behaves this way. The other day I'll try again from a Linux machine. maybe that works...
#4/5/6: boot to bootloader still doesn't work no matter what I try - devices always boots back into system
#7: Once I managed to get into TWRP the rest was a breeze
#8: I tried TWRP 3.6.0_9-0 which worked but on every boot into recovery it shows first a red notice that recovery was not enforcing SEAndroid. The notice then turns into blue and a second later TWRP logo shows up. This dowsn't happen with TWRP 3.5.2_9, so I stay there for the time being. Then I felt lucky and installed TWRP 3.6.2_9 image from running TWRP recovery, then rebooted. That again showed the red "not enforcing" message - and got stuck there. Solution was to get back into "Download mode" then re-flash TWRP 3.5.2 through ODIN.
Conclusion TWRP 3.6.2 is not fit to be used on that device (no, I didn't try 3.6.1...)
#9: since there aren't any more security updates released by google for A9 ROMs it would really be great to be able to upgrade to an A10 or even A11 ROM... anyone ever tried to use a "matisse" or "millet" ROM?
#10: I decided to use that - wiping everything that was on the device then doing a factory reset as well before flashing LOS 16. Then after first boot into LOS 16 a strange thing happened: when I made a basic setting (in regards to location services" the device told me that in a previous version I had decided to NOT allow google to use those services: after all that wiping and factory resetting: how could the device know that? By that time I had not yet logged myself into Google. Very mysterious!
#11/12: I guess I know the answer: I'm out of "Knox" now once and forever. And apparently ODIN is still working and recognizing the device.
Cheers!

SM-P550 can not recover

So I go to schools and help them with IT issues, I noticed they had some tablets sitting there and I asked what was wrong with them and said they were locked and no one knows the code.
SM-P550 - there is account that was signed in with, I have gone to Google admin and noticed there are other 10 of the same type against that account, but has not checked in over a 1000 days as they cant use them.
I can't turn them off, only restat, I can't get to recovery menu, only thing I can go and do is press the power, volume down and home button to get to the screen and it says downloading, and seems to be suck there as nothing ever happens.
I have downloaded all the tools, Odin, Officaial firmware, Samsung USB drivers but nothing comes up on my computer.
Does anyone have any thoughs on fixing this, seems like a waste having these devices just sitting there,
I have tried all the passwords I can get of, nothing.
Thanks

Load a Linux distro and try
Bash:
heimdall detect
If heimdall can detect it, you can use heimdall to flash TWRP and then you can download stock or my ROM (my ROM has no S-pen support).

xdesdx said:
So I go to schools and help them with IT issues, I noticed they had some tablets sitting there and I asked what was wrong with them and said they were locked and no one knows the code.
SM-P550 - there is account that was signed in with, I have gone to Google admin and noticed there are other 10 of the same type against that account, but has not checked in over a 1000 days as they cant use them.
I can't turn them off, only restat, I can't get to recovery menu, only thing I can go and do is press the power, volume down and home button to get to the screen and it says downloading, and seems to be suck there as nothing ever happens.
I have downloaded all the tools, Odin, Officaial firmware, Samsung USB drivers but nothing comes up on my computer.
Does anyone have any thoughs on fixing this, seems like a waste having these devices just sitting there,
I have tried all the passwords I can get of, nothing.
Thanks
Click to expand...
Click to collapse
If they are locked by a Google Account, there is a possibility that, depending on what version of Android is installed, that the FRP lock can be bypassed. Typically, anything later than Android 6, you'd have to send them to Samsung tech support to have the lock removed.

retiredtab said:
Load a Linux distro and try
Bash:
heimdall detect
If heimdall can detect it, you can use heimdall to flash TWRP and then you can download stock or my ROM (my ROM has no S-pen support).
Click to expand...
Click to collapse
Hi can you provide me the link that you used. I have tried using it and doesnt work for me. Went to Heimdall website and followed some videos

Update, the USB cable I was trying was crap so I change to a better quailty Odin can see my device, I have installed the fireware for that device but the old account stays there, so it has not been removed.

xdesdx said:
Update, the USB cable I was trying was crap so I change to a better quailty Odin can see my device, I have installed the fireware for that device but the old account stays there, so it has not been removed.
Click to expand...
Click to collapse
What version of Android did you install? I see that the last version for that device was 7.1, which won't work. But if you can find and flash a early 6 version, I may be able to help. Try Sammobile.
edit: Read this link.

Sorted, so I put the original firmware back on and the account was still there, then I put the combination firmware on, which worked and I removed and reset the tablet. Than I put the original firrware back on. Boom done plus odin needed a high quality cable.
Thanks all