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

Root Root for Fierce 2?

i don't know if this will be any help but ill explain how it worked for me first i ran antutu waited until it was at 10% then i pressed the home button opened kingroot it rebooted the phone and once it was back on i opened antutu waited until 10% then pressed home button and picked kingroot and it jumped to 100%
 
bakageta said:
I don't mean to sound rude, but I think you're getting a bit ahead of yourself. I dumped the bootloader to take a peek, and it appears to not only be locked, but also to have disabled fastboot entirely. Even if you build a recovery, flashing a recovery.img is an almost certain way to end up with a paperweight. We'll need a 2nd init recovery that hijacks the normal boot process, like Safestrap. These require several modifications on /system, and mistakes can easily cripple a device. Without a way to restore the factory rom, it's a fairly dangerous combination, especially for inexperienced devs. Under no circumstance should random users be testing in-progress builds, it'll just end up with bricks all around.

While we're on the topic of bootloaders, at a quick glance ours doesn't seem to be the same codebase as anything with a recent exploit. I'll do some further digging as I can and see if I can match it to an existing open-source project, to help narrow down potential unlock exploits.
Click to expand...
I have flashed a recovery of the alcatel fierce and it didn't work but my phone still booted just couldn't go into recovery so I reflashed the stock recovery and everything is back to normal so I don't think flashing a recovery will brick the phone.
 
I just wanted to say thank you for everyones help on rooting my phone. You have know idea how happy I am now. I thought you could never root this phone but you can unbelievable I've given up trying and I started reading this post and when you guys figured out how to use kingroot with antutu it did the job I thought I was dreaming thank you so much. Now I don't know what to do next?
 
KrazyKobra said:
Link For Downloads?
Click to expand...
Dude I just wanted to thankyou and tell you your a pimp the only thing I did different was when antutu was running I had to wait till it got to 63percent to hurry and open kingroot and start it but it did the trick thanks again.
 
I agree it will help to have a list of working modules, I was testing some modules and have had to factory reset my android a few times. Haven't tried any more tired of having to factory reset I've only got 3 modules, I read the forum and seen that flat style colored bars works and I tried wanam kit it worked and lucky patcher too.
 
bakageta said:
While we're on the topic of bootloaders, at a quick glance ours doesn't seem to be the same codebase as anything with a recent exploit. I'll do some further digging as I can and see if I can match it to an existing open-source project, to help narrow down potential unlock exploits.
Click to expand...

So, I had a bit more time to look at it, and t-mobile's device is using a fork of lk, though it's not the same fork as the L70 was using. From a quick glance, it seems to be based on the dragonboard source or a related project. There are some fastboot-related strings that I'm not seeing in other projects, but it was just a quick glance.

callal241 said:
I have flashed a recovery of the alcatel fierce and it didn't work but my phone still booted just couldn't go into recovery so I reflashed the stock recovery and everything is back to normal so I don't think flashing a recovery will brick the phone.
Click to expand...

If you flash a recovery to a locked bootloader device, it will fail to boot. I certainly haven't had any luck getting to fastboot, which would be a typical way to fix it. Now, if the bootloader is unlocked, a bunk recovery.img will just leave you without a recovery, no real harm as you can boot normally and flash from there.

So, just to clarify then, what recovery did you try to flash, and how did you flash it? Which carrier do you have? If you've got MetroPCS, can you dump your aboot / abootbk partitions and upload them? I'd like to compare against the T-Mobile version. Throw in your boot.img as well, if you don't mind. If your bootloader turns out to be unlocked, I'll get a bit more brave playing with mine and throw a traditional recovery.img together. Quick shell commands to dump them:

Code: 
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/abootbk of=/sdcard/abootbk.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img
 
jdzero89 said:
i don't know if this will be any help but ill explain how it worked for me first i ran antutu waited until it was at 10% then i pressed the home button opened kingroot it rebooted the phone and once it was back on i opened antutu waited until 10% then pressed home button and picked kingroot and it jumped to 100%
Click to expand...
Thankyou so much it worked first time I'll list the steps.
1 - Install Kingroot and Antutu benchmark.
2 - start antutu and begin benchmark test.
3 - When antutu gets to 10% press your home button. (I put kingroot on homepage)
4 - Start Kingroot and wait for device to reboot.
5 - As soon as you can open Antutu and begin test again.
6 - When at 10% again press home button.
7 - Open Kingroot and wait for reboot once more.
8 - Open kingroot again and you should get root.


Hope this helps newbs or people who like step by steps. This is exactly what I did after doing it other ways for over a day.
 
jdzero89 said:
I agree it will help to have a list of working modules, I was testing some modules and have had to factory reset my android a few times. Haven't tried any more tired of having to factory reset I've only got 3 modules, I read the forum and seen that flat style colored bars works and I tried wanam kit it worked and lucky patcher too.
Click to expand...
You sure wanam kit work I'm not trying to reset again
 

Attachments

  • Screenshot_2015-05-18-23-10-39.png
    Screenshot_2015-05-18-23-10-39.png
    74.1 KB · Views: 153
bakageta said:
I don't mean to sound rude, but I think you're getting a bit ahead of yourself. I dumped the bootloader to take a peek, and it appears to not only be locked, but also to have disabled fastboot entirely. Even if you build a recovery, flashing a recovery.img is an almost certain way to end up with a paperweight. We'll need a 2nd init recovery that hijacks the normal boot process, like Safestrap. These require several modifications on /system, and mistakes can easily cripple a device. Without a way to restore the factory rom, it's a fairly dangerous combination, especially for inexperienced devs. Under no circumstance should random users be testing in-progress builds, it'll just end up with bricks all around.

While we're on the topic of bootloaders, at a quick glance ours doesn't seem to be the same codebase as anything with a recent exploit. I'll do some further digging as I can and see if I can match it to an existing open-source project, to help narrow down potential unlock exploits.
Click to expand...
Lol, 'inexperienced'. Im sure both metro and T-Mobile locked the bootloader for this thing, its why I asked if anybody has tried, I was going to but when I restored my fonts I Hard Bricked, the phone won't do shit, stays at the Alcatel Fierce 2 Screen, and Hell No I'm not buying another Alcatel phone Again, its just a pain in the ass and a waste of time, but I think I can still help out, my sister has one of these, I'll probably talk her into getting a new one, cuz this is crap (for now) What's the Next Move?
 
So far, I can confirm 4 modules as working. I can try and update this post once more modules are found that work.

  1. Wanam Kit
  2. Greenify
  3. Flat Styled Colored Bars
  4. Lucky Patcher
 
GTizzle said:
Lol, 'inexperienced'. Im sure both metro and T-Mobile locked the bootloader for this thing, its why I asked if anybody has tried, I was going to but when I restored my fonts I Hard Bricked, the phone won't do shit, stays at the Alcatel Fierce 2 Screen, and Hell No I'm not buying another Alcatel phone Again, its just a pain in the ass and a waste of time, but I think I can still help out, my sister has one of these, I'll probably talk her into getting a new one, cuz this is crap (for now) What's the Next Move?
Click to expand...

Inexperienced doesn't mean you can't help out, I just think your expectations might be a little high. Assuming the bootloader is locked (a pretty safe assumption), there are two paths to take. The first leads to the ideal solution of an unlocked bootloader: reverse engineer the bootloader, find a potential exploit, and develop an exploit. This is a major task, as you can tell by how few bootloader exploits have been released compared to root exploits. You'll need to have a working knowledge of arm assembly, and since there's not exactly a vulnerability database to sift for ideas, you'll need to be able to actually spot vulnerabilities. It's well outside of my comfort zone, and if you've never done any reverse engineering, learning to create an exploit from nothing is likely to take longer than the phone's life.

The second path is likely to yield something useful quicker, but it's still fairly complicated. You need to use the 2nd Init method to hijack the init script, stop the normal boot process, and launch the recovery's separate init scripts. It needs to only do this when you press a button at a specific time, or create a file somewhere that says next reboot should be recovery, so that you can boot normally otherwise. A recovery needs to be built and adjusted to deal with not having access to the boot partition. Normally devices with a locked bootloader are still able to restore the factory software with fastboot, odin, or other various flashing tools, which means you are only out a little time when you make a mistake. We don't have a signed stock rom to restore to, which means a simple bootloop becomes a brick, since factory reset assumes you couldn't have messed with /system and won't do anything to it.
 
floridaboy89 said:
Could someone confirm this
Click to expand...

That's not for our phones, it's for the Evolve 2, which has vastly different hardware. The original XDA thread changed the title to have the correct name, but that crappy caching blog still shows the original title. The model number and use of MTK Droid Tools gives it away though.
 
bakageta said:
That's not for our phones, it's for the Evolve 2, which has vastly different hardware. The original XDA thread changed the title to have the correct name, but that crappy caching blog still shows the original title. The model number and use of MTK Droid Tools gives it away though.
Click to expand...
Thanks
 
Ok I'm very new to rooting and modifying your phone so I have a few questions. 1. Do I need to root my phone to tether ? I'm with metro PCs and when I tether it takes away from my WiFi hotspot that I pay for, and I thought tethering was supposed to go off your 4g internet access ? 2. Does my phone need to be rooted to mirror ? I bought and mhdl adapter and it wouldn't work. Also while I was messing around with my phone trying to root I was able to get developer options. Will that help with modifying anything on my phone ? As in deleting apps that were on phone when bought ? Any help would be greatly appreciated ! Thanks
 
holokost said:
Ok I'm very new to rooting and modifying your phone so I have a few questions. 1. Do I need to root my phone to tether ? I'm with metro PCs and when I tether it takes away from my WiFi hotspot that I pay for, and I thought tethering was supposed to go off your 4g internet access ? 2. Does my phone need to be rooted to mirror ? I bought and mhdl adapter and it wouldn't work. Also while I was messing around with my phone trying to root I was able to get developer options. Will that help with modifying anything on my phone ? As in deleting apps that were on phone when bought ? Any help would be greatly appreciated ! Thanks
Click to expand...
Tbh don't root you're phone you will probably brick it
 
You must log in or register to reply here.
Back
Top Bottom