• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Alcatel One Touch Fierce [RECOVERY]

possibly a 2nd init, but no idea if that would even work on the chipset in this device. if it was your run of the mill qualcomm yea, but its some mediatek garbage :( it doesn't even have a proper recovery partition.
 
hi,I need to help get OT Fierce to fastboot/adb mode(need to do full wipe to get options unlock it again)
Can anyone help me please?
edit 8.1.:I am in adb succesfully,but have problems with adb wipe all-does nothing....
 
Hey Shabby can you please describe the difference between a normal custom recovery and a 2nd init recovery.
 
normal recovery you can get into no matter how bad you mess up your system rom, 2nd init requires your phone to be booted and to then "reboot" your device with a modded ramdisk into a temp recovery. downside of 2nd init is that it will not save you form bootloops.
 
chances are its like the one touch evloved where the partition is actually hidden. ive never dealt with these kinds of devices.[/QUOTE

Is this video for the sim unlock or the bootloader? I dont know to much about unlocking either one so.. You know what your doing youve helped allot with different types of phones so here's the link Instant Fast Unlock 7024W 7024N Alcatel Fierce T-Mobile Metro PCS Brightspot by USB cable on Vimeo

Also this site News - Sigma - MTK, Qualcomm, Broadcom, TI OMAP based flashing, unlocking, repair IMEI solution was posted on another site, could this potentially unlock our bootloader?

Any info would be appreciated.
 
Damn. Alright well thanks for the info. I'll keep digging arund to see if I can find anything that will help us unlock the bootloader, this phone has potential, the only thing us we can't unlock it.
 
!!These files are for DEV's only!!
!!They are not what you need to fix a brick!!
!!They will probably make a brick if used incorrectly!!
!!Dont blame me if you fail to heed my warnings!!

Images of every partition(I think, except for /dev/misc-sd)
https://mega.co.nz/#!vsQzjDAS!LYNpnuNjDX2rSSK5i0xBpoVWhkXEsAAS4woT0bRZ-_s

Not sure if this preloader is correct as I can't figure out how to mount and unpack it or mmcblk0.
https://www.dropbox.com/s/i0rlx0r8qhn5856/preloader.img

Backup made with Nandroid Online
https://mega.co.nz/#!K5xDAJqQ!0sIjIUgW92xZb00fxQJt6cdcOJ2sll2x0NQl2vxJr9Y

/system/etc/security/otacerts.zip
https://www.dropbox.com/s/6sa0v5tn1408rky/otacerts.zip

Log from stock recovery
https://www.dropbox.com/s/zfq3j6ajkx9ssxd/last_log

Partition maps as seen by
cat /proc/dumchar_info,
Part_Name Size StartAddr Type MapTo
preloader 0x0000000001000000 0x0000000000000000 2 /dev/misc-sd
mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000100000 2 /dev/block/mmcblk0
pro_info 0x0000000000300000 0x0000000000500000 2 /dev/block/mmcblk0
nvram 0x0000000000500000 0x0000000000800000 2 /dev/block/mmcblk0
protect_f 0x0000000000a00000 0x0000000000d00000 2 /dev/block/mmcblk0p2
protect_s 0x0000000000a00000 0x0000000001700000 2 /dev/block/mmcblk0p3
seccfg 0x0000000000020000 0x0000000002100000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000002120000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x0000000002180000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000002780000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x0000000002d80000 2 /dev/block/mmcblk0p4
misc 0x0000000000080000 0x0000000003380000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000003400000 2 /dev/block/mmcblk0
ebr2 0x0000000000080000 0x0000000003700000 2 /dev/block/mmcblk0
custpack 0x0000000026500000 0x0000000003780000 2 /dev/block/mmcblk0p5
mobile_info 0x0000000000800000 0x0000000029c80000 2 /dev/block/mmcblk0p6
expdb 0x0000000000a00000 0x000000002a480000 2 /dev/block/mmcblk0
android 0x0000000028a00000 0x000000002ae80000 2 /dev/block/mmcblk0p7
cache 0x0000000007e00000 0x0000000053880000 2 /dev/block/mmcblk0p8
usrdata 0x0000000088c80000 0x000000005b680000 2 /dev/block/mmcblk0p9
otp 0x0000000004000000 0x00000000feff0200 2 /dev/block/mmcblk0
bmtpool 0x0000000001500000 0x00000000feff00a8 2 /dev/block/mmcblk0
Part_Name:Partition name you should open;
Size:size of partition
StartAddr:Start Address of partition;
Type:Type of partition(MTD=1,EMMC=2)
MapTo:actual device you operate

cat /proc/emmc,
partno: start_sect nr_sects partition_name
emmc_p1: 00000400 00000002 "ebr1"
emmc_p2: 00006800 00005000 "protect_f"
emmc_p3: 0000b800 00005000 "protect_s"
emmc_p4: 00016c00 00003000 "sec_ro"
emmc_p5: 0001bc00 00132800 "custpack"
emmc_p6: 0014e400 00004000 "mobile_info"
emmc_p7: 00157400 00145000 "android"
emmc_p8: 0029c400 0003f000 "cache"
emmc_p9: 002db400 00446400 "usrdata"

fdisk -l mmcblk0.img,
Warning: ignoring extra data in partition table 5
Warning: ignoring extra data in partition table 5
Warning: ignoring extra data in partition table 6

Disk mmcblk0.img: 3828 MB, 3828350976 bytes
1 heads, 63 sectors/track, 118686 cylinders, total 7477248 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
mmcblk0.img1 1024 4294968318 2147483647+ 5 Extended
mmcblk0.img2 26624 47103 10240 83 Linux
mmcblk0.img3 47104 67583 10240 83 Linux
mmcblk0.img4 93184 105471 6144 83 Linux
mmcblk0.img5 113664 1369087 627712 83 Linux
mmcblk0.img6 2737152 2995199 129024 83 Linux

and MTK Droid Tools
 

Attachments

  • Screenshot from 2014-04-03 14:30:18.jpg
    Screenshot from 2014-04-03 14:30:18.jpg
    34.2 KB · Views: 207
  • Screenshot from 2014-04-05 08:48:27.jpg
    Screenshot from 2014-04-05 08:48:27.jpg
    37 KB · Views: 217
  • Screenshot from 2014-04-05 10:29:52.jpg
    Screenshot from 2014-04-05 10:29:52.jpg
    12.3 KB · Views: 160
  • Screenshot from 2014-04-05 11:41:07.jpg
    Screenshot from 2014-04-05 11:41:07.jpg
    18.6 KB · Views: 174
Hi, you seem like you guys know what you're talking about so I was wondering if you might be able to help. I have a one touch fierce, never tried any crazy mods or rooting or whatever, just stock. Yesterday it told me there was a mandatory update so I tried to install it. Seemed like it was going ok for a few minutes then it rebooted and when it came back on it said that it had failed. After that when I tried to get to settings it said unfortunately settings has stopped. Power off and on, same thing. So my next thought was factory reset, but that has just made the situation worse because now it starts at the welcome setup screen, hit next, select English, hit next, unfortunately settings has stopped, and then back to first screen. Can't get to the home screen. Can pull down the top bar thing, can hold the home key and use Google, if I get a text I can get to it from the top bar and respond, etc. But use is very difficult and limited like this, lol! Do you know what I need to do to fix this or undo whatever the update screwed up? I'll take it to t mobile tomorrow, but based on my past experience with the jerks at the one I go to, they'll probably just try to sell me another phone, all they seem interested in is commission. Any help or advice would be greatly appreciated, thank you very very much.
 
Hi, you seem like you guys know what you're talking about so I was wondering if you might be able to help. I have a one touch fierce, never tried any crazy mods or rooting or whatever, just stock. Yesterday it told me there was a mandatory update so I tried to install it. Seemed like it was going ok for a few minutes then it rebooted and when it came back on it said that it had failed. After that when I tried to get to settings it said unfortunately settings has stopped. Power off and on, same thing. So my next thought was factory reset, but that has just made the situation worse because now it starts at the welcome setup screen, hit next, select English, hit next, unfortunately settings has stopped, and then back to first screen. Can't get to the home screen. Can pull down the top bar thing, can hold the home key and use Google, if I get a text I can get to it from the top bar and respond, etc. But use is very difficult and limited like this, lol! Do you know what I need to do to fix this or undo whatever the update screwed up? I'll take it to t mobile tomorrow, but based on my past experience with the jerks at the one I go to, they'll probably just try to sell me another phone, all they seem interested in is commission. Any help or advice would be greatly appreciated, thank you very very much.
Usually people who had update failed didn't even get that far, they get soft bricked. You can try safe mode, but wait till someone else has a better opinion. I'm not an expert at this phone.
 
The fierce is a big improvement over my last phone, an HTC Wildfire, but it does seem to have some issues here and there. I should have exchanged it when it was new since the front camera has never worked, but it was too much hassle and I didn't have time at the time. For the price though it has been a good phone, just really unhappy that I can't use it much right now because normally I'm pretty much using it constantly. Hopefully someone can help figure it out. Thanks again.
 
Hmm.... You say you can't go to settings right? Try opening settings (it will fail) the open the recent apps and settings should appear, long press it and go to apps and HOPEFULLY it let's you. If you can try to delete data/ cache
 
Hey, I didn't know you could do that if you long pressed it! Unfortunately it didn't work, just said settings stopped again. But I'm grateful for the help, anything is worth trying, thank you!
 
So I was wondering, since it shows options to install update from sd card, or there's another option (adb or something?), is there a way to download the update and save it to the sd card and then try to reinstall it maybe and see what happens? I haven't been able to find anything to download though...
 
Haven't made it to t mobile yet to see if they can help, been figuring out how to do some things without the apps, settings, or home screen, but still could use help if anyone knows anything useful, thanks.
 
Back
Top Bottom