Related
Hi,
I am having really bad issues with my Alcatel One Touch Idol S OT-6034R and need to reflash it back to stock. On Sammy phones their is an option as everyone probably knows of emergency firmware recovery. Not so with Alcatel. i tried their "One touch upgrade" software but it says it is already the latest version, which yeah I know it is but I want to reflash it. I tried calling Alcatel and they said it must be sent off. Really? For something I could fix myself if only they just provided the stuff to do it. If anyone has any ideas where I could get the stock zip file that I can flash with stock recovery or other files I could grab to force the flash then please help with anything you may have.
Many thanks, I know never to buy Alcatel again but until I can afford another phone I am stuck with this one.
I have the same issue, I swapped the settings.apk and settingprovidor.apk from the wrong custpack and not its stuck in a boot loop.
I have the original files but can't add them back to the phone
anybody?
tomolewis said:
I have the same issue, I swapped the settings.apk and settingprovidor.apk from the wrong custpack and not its stuck in a boot loop.
I have the original files but can't add them back to the phone
anybody?
Click to expand...
Click to collapse
Can you not ADB PUSH them back to the phone with it in recovery mode? might fix your issue possibly.
chronic8000 said:
Can you not ADB PUSH them back to the phone with it in recovery mode? might fix your issue possibly.
Click to expand...
Click to collapse
look this
http://www.forum-generationmobiles.net/f447-one-touch-idol-s
Any news on this?
Hello, I'm in the same position with 6034R - need to reflash but the application says I'm already on the latest version. Did anybody found a solution on this?
chronic8000 said:
Hi,
I am having really bad issues with my Alcatel One Touch Idol S OT-6034R and need to reflash it back to stock. On Sammy phones their is an option as everyone probably knows of emergency firmware recovery. Not so with Alcatel. i tried their "One touch upgrade" software but it says it is already the latest version, which yeah I know it is but I want to reflash it. I tried calling Alcatel and they said it must be sent off. Really? For something I could fix myself if only they just provided the stuff to do it. If anyone has any ideas where I could get the stock zip file that I can flash with stock recovery or other files I could grab to force the flash then please help with anything you may have.
Many thanks, I know never to buy Alcatel again but until I can afford another phone I am stuck with this one.
Click to expand...
Click to collapse
reflash
pmarkov said:
Hello, I'm in the same position with 6034R - need to reflash but the application says I'm already on the latest version. Did anybody found a solution on this?
Click to expand...
Click to collapse
This worked for me:
system.img - mega.co.nz/#!HBIF3KzY!R6roKuvEeVYCcPFphY0fPi7FoMll0WqRaCZQLoroP_w
custpack.img - mediafire.com/download/hccfk2bqq81m3oi/custpack_modifier.img
recovery.img - mediafire.com/download/vdl78u0fhov6xhl/idolscwm6.0.3.7.img
boot.img - shared.com/vkk89d3d6b?s=l
reflash:
adb reboot bootloader
fastboot -i 0x1bbb erase boot.img
fastboot -i 0x1bbb erase recovery.img
fastboot -i 0x1bbb erase system.img
fastboot -i 0x1bbb erase custpack.img
fastboot -i 0x1bbb flash boot boot.img
fastboot -i 0x1bbb flash recovery recovery.img
fastboot -i 0x1bbb flash system system.img
fastboot -i 0x1bbb flash custpack custpack.img
fastboot -i 0x1bbb reboot
Links and commands from: forum-generationmobiles.net/t74868-tuto-transformer-ultym4-en-idol-s
and big thanks for dams161 :good:
gabcs said:
This worked for me:
system.img - mega.co.nz/#!HBIF3KzY!R6roKuvEeVYCcPFphY0fPi7FoMll0WqRaCZQLoroP_w
custpack.img - mediafire.com/download/hccfk2bqq81m3oi/custpack_modifier.img
recovery.img - mediafire.com/download/vdl78u0fhov6xhl/idolscwm6.0.3.7.img
boot.img - shared.com/vkk89d3d6b?s=l
reflash:
adb reboot bootloader
fastboot -i 0x1bbb erase boot.img
fastboot -i 0x1bbb erase recovery.img
fastboot -i 0x1bbb erase system.img
fastboot -i 0x1bbb erase custpack.img
fastboot -i 0x1bbb flash boot boot.img
fastboot -i 0x1bbb flash recovery recovery.img
fastboot -i 0x1bbb flash system system.img
fastboot -i 0x1bbb flash custpack custpack.img
fastboot -i 0x1bbb reboot
Links and commands from: forum-generationmobiles.net/t74868-tuto-transformer-ultym4-en-idol-s
and big thanks for dams161 :good:
Click to expand...
Click to collapse
Hi, everyone!
I have the same problem. Everything worked fine untill I changed some values in build.prop. Since then the phone freezes on operator logo when I try to boot.
I can boot to CWM and restore previously made backup, but no results, can't boot to system.
When I try with ADB; "fastboot -i 0x1bbb erase boot.img" it tells me that partition table is missing..... Is it possible to restore partition table informations? Any further thoughts?
Root Alcatel
Hello everyone, Esque quelqun could tell me when will esqu'on rooter The alcatel one touch idol 2 mini S android 4.3 please
zlamar said:
Hi, everyone!
I have the same problem. Everything worked fine untill I changed some values in build.prop. Since then the phone freezes on operator logo when I try to boot.
I can boot to CWM and restore previously made backup, but no results, can't boot to system.
When I try with ADB; "fastboot -i 0x1bbb erase boot.img" it tells me that partition table is missing..... Is it possible to restore partition table informations? Any further thoughts?
Click to expand...
Click to collapse
Leave the erase command, just boot into cwm, format the system, custpack, reboot to bootloader and flash the files Will working too
The custpack file seems to be wrong. I've managed to flash the files but this version of custpack leads to bootloop. I found another version custpack on the french forum and with it booted successfully but... NO WIFI, NO GSM. And the "Baseband version" is Unknown.
gabcs said:
Leave the erase command, just boot into cwm, format the system, custpack, reboot to bootloader and flash the files Will working too
Click to expand...
Click to collapse
pmarkov said:
The custpack file seems to be wrong. I've managed to flash the files but this version of custpack leads to bootloop. I found another version custpack on the french forum and with it booted successfully but... NO WIFI, NO GSM. And the "Baseband version" is Unknown.
Click to expand...
Click to collapse
Try this: shared.com/7dwx96a1yy?s=l
This is from the french forum - I already tried exactly this image with no success.
gabcs said:
Try this: shared.com/7dwx96a1yy?s=l
Click to expand...
Click to collapse
pmarkov said:
This is from the french forum - I already tried exactly this image with no success.
Click to expand...
Click to collapse
your phone is 6034 or 6035? i tried on 2 phones (6034r) and the custpack is work. one of these roms maybe help...this is my last idea
mediafire.com/folder/628vrfsah9mbs/recovery#44uztz6cagnl7
gabcs said:
one of these roms maybe help...this is my last idea
mediafire.com/folder/628vrfsah9mbs/recovery#44uztz6cagnl7
Click to expand...
Click to collapse
Can you please explain us more about this last resource?
In folder BS472 there are 3 files... isn't "custpack.img" to small? And should we rename "boot-bs472.img" and "recovery_bs472.img" to "boot.img" and "recovery.img" before flashing?
And about two ROMs; first is just 70 Mb in size and the other is 233 Mb? Are they both working as standalone ROMs or something else? Should we flash it with CWM?
Maybe flashing ROM will resolve all problems?
What about other folders and files within?
Sorry for lot of questions, but this phone is a frustrating experience for me...
zlamar said:
Can you please explain us more about this last resource?
In folder BS472 there are 3 files... isn't "custpack.img" to small? And should we rename "boot-bs472.img" and "recovery_bs472.img" to "boot.img" and "recovery.img" before flashing?
And about two ROMs; first is just 70 Mb in size and the other is 233 Mb? Are they both working as standalone ROMs or something else? Should we flash it with CWM?
Maybe flashing ROM will resolve all problems?
What about other folders and files within?
Sorry for lot of questions, but this phone is a frustrating experience for me...
Click to expand...
Click to collapse
Sorry, but my english is bad. But yeah, i know, i spent 3 days (0-24) to fix this phone. For me the reflash custpack, boot and system img worked from my first post. From mediafire folder need just the 2 roms. the first 70mb is only the system. The orange rom i think the full rom. Yes, every two are cwm flashable. Try to flash the img-s in bootloader mode after flash the 70mb rom with cwm. If dont work make a factory reset with cwm and flash the 233mb orange rom. This phone's software like a nightmare. No source code, everything is different like in other phones and nobody knows the different between the 6034 and 6035. I better like my OT-991 with MTK soc...
@gabcs
Unfortunatelly, after no success in searching for solution (couldn't find the ROM), two weeks ago, I gave up and sent my phone to service center and I hope that they will resolve the problem. Big and frustrating issue was that I couldn't get to bootloader any more, so the phone couldn't recieve adb commands, only thing that worked was CWM...
Service center will resolve that for 20 euros, and I will resolve my nerves
Anyway, thank you for your time and your help.
@zlamar,
what happened with your phone? Did you managed to have it repaired/restored? My phone is still bricked and It seems the problem is to find the appropriate custpack image as the french versions don't work for other countries.
Still nothing.... Service center where I gave it for repair isn't authorised and they didn't resolve the issue.
Does anybody have a full CWM backup image, and is willing to share it and upload it somewhere?
It has nothing to do with authorization, they just don't have alcatel service access.
There is special alcatel service flasher, that works online, and is intended for Qualcomm platform.
I played with it, and re-flashed my 6016x (MSM8210 - Qualcomm Snapdragon 200).
If you were somewhere closer, I would repair it for 20€ very fast and effiecent
@pmarkov ... I have original files but they are useless, because no any flasher to use them.
b.r.
ALex
Hi Alex,
Thanks for the clarification. Obviously this magic flashing tool is only internaly available for authorized service providers. Today I contacted the official local partner of Alcatel and they were positive they can handle the reflashing for approx. 20 EUR. Let's hope they really will fix it.
BR
I unrooted and relocked the bootloader to install Lollipop. Succeeded and installed the soak test version.
Here's where I screwed up. I tried downgrading to 4.4.4 using the factory firmware and now I'm unable to mount any partition or install any boot image. Every time I try installing an img via fastboot I get a "Prefetch validation failed". When I start the phone I get "Invalid boot image header".
What works:
Recovery (TWRP) - Can't install anything because cache, data, system cannot be mounted.
Followed these steps:
http://forum.xda-developers.com/moto-e/general/video-tutorial-downgrade-moto-e-android-t3032738
I was able to install TWRP. But these are not mounting - cache, system, data.
I was able to flash gpt.bin.
Can someone please give links to 5.0.2 firmware? Why am I not able to flash the 4.4.4 firmware?
how did you install lollipop ..through stock recov or twrp.
Did it from recovery via adb sideload.
I'm able to flash all the images except: motoboot.img and gpt.bin.
I have a running android system but the SIM card is not getting detected at all.
Shredder333 said:
Did it from recovery via adb sideload.
I'm able to flash all the images except: motoboot.img and gpt.bin.
I have a running android system but the SIM card is not getting detected at all.
Click to expand...
Click to collapse
I think you should clean install Soak lollipop update from ADB sideload again... Maybe it will help...
Or try Custom Roms! like cm12 or PAC... But remember, Do flash a rom of lollipop... and forget kitkat for now!1!!!
Regards
Andy
Shredder333 said:
Did it from recovery via adb sideload.
I'm able to flash all the images except: motoboot.img and gpt.bin.
I have a running android system but the SIM card is not getting detected at all.
Click to expand...
Click to collapse
motoboot.img and gpt.bin are not supposed to b flashed..................as for ur SIM, maybe u flashed the wrong firmware..............
I tried installing the lollipop firmware through ADB but it aborts after verification. I've tried other ROMs, everything works fine except that the SIM doesn't detect at all.
System, modem, recovery, boot all get flashed fine. Except motoboot and gpt.bin which fail to flash saying "preflash validation failure". Is the SIM not detecting because these 2 images fail to get flashed?
moto r hard brick
heloo guys i have MOTO E i updates it to LOLIPOP.. wch ws soak version realized..!!
after a time downgraded it 4.4.2 wia fastboot going in moto e bootloader menu..!!
it ws successful..!! afterwards i updated it to 4.4.4 from OTA .. and while updateing phn went into recovery, and turn off!!
n it dint start again ..!! and now it does not turn onn.. the led blinks when i connect it to charger..!!
i also tried the BLANKFLASH way.. but the files given are for MOTO G..!!! my cell was DEAD ..!!
so i went to the SERVICE CENTER and told them that my cell is in WARENNTY and it does not turn on since i updatedet to 4.4.4
they ACCEPTED and they are going to change my MOTHERBOARD in FREE of cost..!!!
SO THOSE WHO HAVE BRICKED THEIR MOTO PLZ RUN TO SREVICE CENTER ASAP.!!!!
HARD LUCK...!!!!
Shredder333 said:
I tried installing the lollipop firmware through ADB but it aborts after verification. I've tried other ROMs, everything works fine except that the SIM doesn't detect at all.
System, modem, recovery, boot all get flashed fine. Except motoboot and gpt.bin which fail to flash saying "preflash validation failure". Is the SIM not detecting because these 2 images fail to get flashed?
Click to expand...
Click to collapse
sim card not working...seems like a efs partition problem.do u have a back up of your efs partition.
Hi there,
i am newbie at xda-developers and posting this thread to get you android engineere help to unbrick my cdma android phone.
last yesterday, i've tried to to install custom rom in my phone by using adb sdk.
my hardware is QRD
brand model is MTS MTAG353 Coolpad 5210
Android version 2.3.5
Iast week i planed to change its rom and download a cwm7.1 Custom rom compatible with android 2.3.5.
i'd took backup of my original rom before flashing files of cwm custom rom. and start flashing files of cwm.
i'd first flash recovery by adb command "flastboot flash recovery recovery.img" and then flash "fastboot flash boot boot.img"
And after that use command "fastboot reboot" (mistake i did).
then my phone reboot, mts logo image appear and then black screen. My phone connected with pc but no usb port show that my android device is connected.
now i am confuse what to do. As adb don't show my device connected with pc. I've backup of my last used boot and recovery file. But i don't know, how to re-flash them.
so guys, if there is any solution reply me as-soon-as possible.
Hello,
First of all I want to tell, that I have read all topics about flashing new firmware to Stratos
And also I have unocked bootloader.
My sad story have begun at the moment my Stratos with factory EN 2.3.2.8 firmwary started to hangs.
I could wait for click reaction for a long time, animation was shown with huge delays.
Ones I managed to factory reset Stratos from menu.
But in shirt time it again became in non-working mode.
After reboot the watch I could see only Amazfit logo
But nothing changed with hangs.
So I decided to unlock bootloader and reflash the Stratos with firmware 2.3.2.7
Well, afer flashing the situation didn't change.
I saw only Amazfit logo.
Also I couldn't make adb shell
adb shows device, but adb shell command gives me:
Code:
- exec '/system/bin/sh' failed: Permission denied (13) -
using port=5555
I only managed to unbrick it with The English AmazFit firmware 1.3.0n (nor CN version, nor other firmware worked for my Stratos)
but it appears the Pace firmware.
Once I managed to flash boot from EN 1.3.0n and system from EN 2.3.0.8
It boots, but onlt one power button worked. Touchpad and other buttons - didn't.
After that I flashed misc.img (was found here) and nothing.
So I decided that it's boot issue in my case.
Please help with advice how can I manage to return my Startos back to life.
This may help:
https://forum.xda-developers.com/smartwatch/amazfit/tools-unbrick-huami-amazfit-stratos-t3777380
Pazzl said:
Hello,
First of all I want to tell, that I have read all topics about flashing new firmware to Stratos
And also I have unocked bootloader.
My sad story have begun at the moment my Stratos with factory EN 2.3.2.8 firmwary started to hangs.
I could wait for click reaction for a long time, animation was shown with huge delays.
Ones I managed to factory reset Stratos from menu.
But in shirt time it again became in non-working mode.
After reboot the watch I could see only Amazfit logo
But nothing changed with hangs.
So I decided to unlock bootloader and reflash the Stratos with firmware 2.3.2.7
Well, afer flashing the situation didn't change.
I saw only Amazfit logo.
Also I couldn't make adb shell
adb shows device, but adb shell command gives me:
Code:
- exec '/system/bin/sh' failed: Permission denied (13) -
using port=5555
I only managed to unbrick it with The English AmazFit firmware 1.3.0n (nor CN version, nor other firmware worked for my Stratos)
but it appears the Pace firmware.
Once I managed to flash boot from EN 1.3.0n and system from EN 2.3.0.8
It boots, but onlt one power button worked. Touchpad and other buttons - didn't.
After that I flashed misc.img (was found here) and nothing.
So I decided that it's boot issue in my case.
Please help with advice how can I manage to return my Startos back to life.
Click to expand...
Click to collapse
You flashed a Stock ROM from Amazfit Pace in your Amazfit 2 Stratos, I'm sorry to tell that you probably ruined your watch, as you probably lost your serial number (SN) and locked your bootloader too, and for being now in a stock ROM without root access, I'm afraid you have nothing to do to recover your watch.
You may check your bootloader and SN firstly, and read this restoration thread: https://forum.xda-developers.com/smartwatch/amazfit/guide-restore-null-sn-locked-t3775998
Saratoga79 said:
You flashed a Stock ROM from Amazfit Pace in your Amazfit 2 Stratos, I'm sorry to tell that you probably ruined your watch, as you probably lost your serial number (SN) and locked your bootloader too, and for being now in a stock ROM without root access, I'm afraid you have nothing to do to recover your watch.
You may check your bootloader and SN firstly, and read this restoration thread: https://forum.xda-developers.com/smartwatch/amazfit/guide-restore-null-sn-locked-t3775998
Click to expand...
Click to collapse
Hello,
well, fastboot getvar all shows me correct SN and unlocked bootloader.
And yes, I flashed misc.img with correct values (SN factory, BT and WiFi macs are ok)
And it didn't help.
I can get root access to the device via boot-US-adb-root.img from fastboot mode
I can also access to system partition and mount it from recovery mode.
I several times wipe cache and data.
Also yesterday I managed to flash STRATOSfied 2.0.22.0 and after reboot into recovery it started to update, but hangs almost at the end.
When I mounted system partition I saw that it was only one dir there with app. So update process didn't finish the task.
I don't think that I ruined my watch
lfom said:
This may help:
https://forum.xda-developers.com/smartwatch/amazfit/tools-unbrick-huami-amazfit-stratos-t3777380
Click to expand...
Click to collapse
Hello,
well, it didn't. either full install, either unbrick
Pazzl said:
Hello,
well, fastboot getvar all shows me correct SN and unlocked bootloader.
And yes, I flashed misc.img with correct values (SN factory, BT and WiFi macs are ok)
And it didn't help.
I can get root access to the device via boot-US-adb-root.img from fastboot mode
I can also access to system partition and mount it from recovery mode.
I several times wipe cache and data.
Also yesterday I managed to flash STRATOSfied 2.0.22.0 and after reboot into recovery it started to update, but hangs almost at the end.
When I mounted system partition I saw that it was only one dir there with app. So update process didn't finish the task.
I don't think that I ruined my watch
Click to expand...
Click to collapse
Lucky you
Maybe your system partition is corrupted somehow. You could try maybe flashing the US Stock firmware as your bootloader is unlocked and see if that helps.
Saratoga79 said:
Lucky you
Maybe your system partition is corrupted somehow. You could try maybe flashing the US Stock firmware as your bootloader is unlocked and see if that helps.
Click to expand...
Click to collapse
So you think the issue in the system partition?
Not boot partition?
Could you please tell me how can I unpack img files to check what exactly is in images?
Cause I do think that smth wrong with boot once.
I couldn't mount boot partition under recovery cause it mmc format I think, not ext4
Pazzl said:
So you think the issue in the system partition?
Not boot partition?
Could you please tell me how can I unpack img files to check what exactly is in images?
Cause I do think that smth wrong with boot once.
I couldn't mount boot partition under recovery cause it mmc format I think, not ext4
Click to expand...
Click to collapse
Both boot and recovery use the same format, then need to be unpacked. System.img normally used to flash via dd is a common ext4 partition.
Either way, the correct way t fix it is what Saratoga said: flash a stock ROM (both boot.img and system.img) to boot correctly, and stock recovery if you want OTA. I send a private message, but you didn't reply. Good luck.
lfom said:
Both boot and recovery use the same format, then need to be unpacked. System.img normally used to flash via dd is a common ext4 partition.
Either way, the correct way t fix it is what Saratoga said: flash a stock ROM (both boot.img and system.img) to boot correctly, and stock recovery if you want OTA. I send a private message, but you didn't reply. Good luck.
Click to expand...
Click to collapse
Hello,
I will try again to flash stock boot and system.
The boot partition could be flashed via fastboot flash command or only dd is acceptable?
Pazzl said:
Hello,
I will try again to flash stock boot and system.
The boot partition could be flashed via fastboot flash command or only dd is acceptable?
Click to expand...
Click to collapse
Hello, any update on this? I have the exact same situation you have. Stratos became sluggish, but when factory reset it works back fine, after few days/months its sluggish again until it stucks in amazfit logo only, everything is stock on this point as well as boot loader is locked, I managed to unlock my bootloader via fastboot. Tried most of the unbrick thread here but haven't managed to make it work. Tried stratosfied and it went to recovery where it is updating firmware but stuck at the end. Exactly same situation with you. Hoping I could get information in here, thanks
Edit: Was able to fix it following this -> https://forum.xda-developers.com/smartwatch/amazfit/tutorial-unbrick-huami-amazfit-t3547300
Somehow custom rom, newer stock firmware doesnt work but old 1.3.0n in the thread works yaay!
Hello! This is my first thread on the forum;
I'm writing because I think I soft bricked my Xiaomi Mi Pad 4 LTE, let me explain from the very beginning.
It's a brand new device, bought today, and with a custom italian ROM which was sold with.
I just wanted to root it, and the bootloader was already unlocked because it was a custom ROM, so I tried to install TWRP (mocha version for Mi Pad) with Fastboot and then I wanted to install Magisk.
The issue is that, when I tried to flash TWRP to recovery with fastboot flash recovery twrp.img, it all went "OK" but then TWRP was not actually flashed and couldn't boot it with key combinations, it just looked like it wasn't there. I also tried to boot it without flashing, with fastboot boot twrp.img but it gave me
"Failed to load/authenticate boot image: 00000050" error
Looking on the web, I found someone who told to try fastboot flash boot twrp.img and so, without even thinking, I did it.
That's the main issue. I rebooted, and found that TWRP started, but now I couldn't boot my device anymore, because the default boot.img file was replaced by twrp.img. So, practically, TWRP replaced my device's default system (I think?).
Then, I tried to find a stock firmware for Mi Pad 4 (Clover) on the web, and I found it, so I flashed the stock firmware boot.img, fastboot flash boot boot.img, but when I rebooted, the device was stuck in the loading screen with three dots loading over a "Powered by Android" logo. I waited 20 minutes, nothing, it looks stuck, so this stock boot.img doesn't seem to work.
I can actually flash TWRP and that stock boot image both whenever I want and switch between them; the first works, the latter doesn't.
So, in poor words: I flashed twrp.img as boot.img and now I can't boot normally, but TWRP starts when turning on my device.
But I just want to get my default boot.img or system, or any other way to reaccess to my device. That's fine even if I have to hard reset or wipe everything, it's fine even if I am going to lose data, but please, just help me.
Can someone help me? I'm just a newbie in this world, please help me unbricking my device.
Thanks in advance.
Try installing twrp again and boot to it
Download custom rom.of your choice ( im using hovac and it been great for a year now )
Move it to your mipad via comouter
Format everything in twrp and install the rom and gapps
--- I just remembered havin same issue u having and if im not mistaking : u should reboot to recovery right after installing twrp ( you dont reboot to system )
Im not really sure about it cause it happened long time ago
@DanielVipx
Sorry, seems you tried that already. Did you try the mi flash tool?
This might help:
https://osdn.net/projects/xiaomifirmwareupdater/storage/Stable/V10/clover/