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

Root Roms For The Fierce 2

Mrnatetaylor4479 said:
If u made a custom recovery for this phone can u plz post it or email it to me
Click to expand...
it wouldn't ****ing matter if there was a custom recovery, it won't work without an unlocked bootloader,which we have given up trying to unlock.
 
floridaboy89 said:
If this is true
Click to expand...

For the vast majority of devices, you cannot install or run a custom recovery with a locked bootloader (there are a few exceptions, of course).

Also, let's all make sure we're careful to not post anything that leads to asterisks ("*") being auto-substituted for naughty words :).

Thanks!
 
floridaboy89 said:
This should've never been said
Click to expand...
lol. I said i was gonna finish it, and im finishing it now, there is no one devoted to this, and no one will be, it's a miracle there was even a way to root this thing, let's just leave it at that, no point in commenting any further. Good Night.
 
There doesn't seem to be any hope... So far ive read through this whole fourm and everything seems so hopeless... Like what was said above.... We are lucky this phone was even able to be rooted... On top of all this.... This is the first time anything has been posted here in over a month... Think it's safe to say there's nothing we can do to get some sort of ROM on this phone... R.I.P to all our dreams..
 
No not true. I did not give up. I am successful in that i found a way to patch the stock recovery. The patch will allow you to sideload any zip file signed with my keys. Meaning at this time i have a backup of. Stock firmware that can be flashef with my stock recovery. Modified for my keys. It pass signature verification. So i have a way to fix fierce 2. Meaning when test go bad. I can fix. Meaning i will have custom rom soon. Less than 1 week. Allready tested on working fierce 2
 
Well I have a new phone now and since the Alcatel is basically trash to me, I'm more than willing to sacrifice it. I don't really know what I'm doing with all of this stuff but I did get it to root. Anyways if there's anyone that wants to help me Id be glad to try to mess around with the phone and figure out a fix. Since posting a few months ago symptoms got worse, the phone began to restart on its own and the error messages got worse. However I did discover that when the WiFi is off the error messages stop.
 
Its funny because i literally just got done reading your fourm post about it then I see this. You are putting in great work. Proud of you.
Bigcountry907 said:
No not true. I did not give up. I am successful in that i found a way to patch the stock recovery. The patch will allow you to sideload any zip file signed with my keys. Meaning at this time i have a backup of. Stock firmware that can be flashef with my stock recovery. Modified for my keys. It pass signature verification. So i have a way to fix fierce 2. Meaning when test go bad. I can fix. Meaning i will have custom rom soon. Less than 1 week. Allready tested on working fierce 2
Click to expand...
 
So you're saying you'll test it??
lyssal0ve3 said:
Well I have a new phone now and since the Alcatel is basically trash to me, I'm more than willing to sacrifice it. I don't really know what I'm doing with all of this stuff but I did get it to root. Anyways if there's anyone that wants to help me Id be glad to try to mess around with the phone and figure out a fix. Since posting a few months ago symptoms got worse, the phone began to restart on its own and the error messages got worse. However I did discover that when the WiFi is off the error messages stop.
Click to expand...
 
Bigcountry907 said:
No not true. I did not give up. I am successful in that i found a way to patch the stock recovery. The patch will allow you to sideload any zip file signed with my keys. Meaning at this time i have a backup of. Stock firmware that can be flashef with my stock recovery. Modified for my keys. It pass signature verification. So i have a way to fix fierce 2. Meaning when test go bad. I can fix. Meaning i will have custom rom soon. Less than 1 week. Allready tested on working fierce 2
Click to expand...
Before we go testing any of this, do you have proof?
 
Not everyone is willing to flash just anything someone uploads, and that's not a bad thing. It's a cautious question and if bigcountry is legit (not that I doubt anyone here) then things will speak for themselves and he should have no problem providing some assurance of his work.
 
Ikonex said:
Well I'm pretty sure the proof will be when the files are given.... Duh.... what kind of question is that.
Click to expand...
We just need to see what kind of evidence he has, we need to see a video of some sort, and then check the files he uploads, what if he trashes your phone? (Not saying he is)
 
Bigcountry907 said:
No not true. I did not give up. I am successful in that i found a way to patch the stock recovery. The patch will allow you to sideload any zip file signed with my keys. Meaning at this time i have a backup of. Stock firmware that can be flashef with my stock recovery. Modified for my keys. It pass signature verification. So i have a way to fix fierce 2. Meaning when test go bad. I can fix. Meaning i will have custom rom soon. Less than 1 week. Allready tested on working fierce 2
Click to expand...
You sure in less than a week you will have a custom ROM? Expect LOT'S of bugs, I'd say in a Month or two it should be ready for public testing, if your sure you can get it to work in less than a week.
 
Ok here is the thing. Even if you flash a recovery.img that wont boot into recovery it will not boot-loop the phone. It actually took me a few tries to get everything right.
And you just flash back the original. So there is no risk for anyone to try this.

The benefits are obvious. Many people with a rooted fierce 2 start deleting apps and then the phone starts crashing and acting up. And other than this there is no way to fix it.

It is pretty simple how this works. The recovery image has a file called "keys" in the /res folder.
You have to unpack the recovery image ram disk to see this file.

I create my own releasekey.x509.pem and releasekey.pk8 then create the "keys" file with the new .pem and .pk8.

Unpack the ramdisk and replace the /res/keys file with the new keys file and repack the recovery.img.

Now when you sideload a file to the phone in the recovery it passes signature verification and runs the updater script.

And I did not say a custom ROM built from source.
Since the bootloader is locked you cant just build a rom and flash it. The phone will boot loop. But we can take backups of a phone that is simply rooted and in good shape and make a flashable stock rom. At least this way we can test things and see what we can do before the phone is toast.

Basically as long as you can boot into the recovery you can sideload the backup and be back to good.

I have no reason to put up files that would hurt anything. That would be pretty stupid.
 
So here is the recovery.img for the 7040T. It might work with the 7040N but i havent tested that. If someone puts up a recovery.img from the 7040N I will patch it.

Just download and install the flashify app on your phone.

Make a Backup of your recovery with flashify.

Then flash my uploaded recovery to your phone with flashify.

If you have any problems you just flash the backup recovery with flashify.

Simple as that.

To sideload any zip file with the new recovery you have to sign the zip file with the releasekey.x509.pem and releasekey.pk8 that are attached. Make sure you sign with the -w option.

Like this

java -Xmx2048m -jar ~/path/to/signapk.jar -w releasekey.x509.pem releasekey.pk8 /path/to/zip filename.zip

I use Ubuntu so that command is for Linux. I don’t know the equivalent for windows.
But the -w means sign whole file. The file has to be signed as -w or it will not flash.

There is a Meta-Inf folder included in the zip. It is from a factory OTA so the format of the updater-script is good and the update-binary is good. Edit the updater-script to do what you want it to and include the META-INF in your zip file for flashing.

Make sure you EDIT IT FIRST {Updater-Script}

Im working on making a flashable factory backup.

I just have to write the Updater-Script. Mainly i have to make sure i get all the symlinks and file permissions correct. Maybe one of you can help out with that.

Here is all the information for the 7040T recovery.img

********************************************************************************
Unpack & decompress recovery.img to ramdisk
board : R2C28080AW00
kernel : kernel
ramdisk : ramdisk
page size : 2048
kernel size : 5933680
ramdisk size : 1309094
dtb size : 1275904
base : 0x00000000
kernel offset : 0x00008000
ramdisk offset : 0x02000000
tags offset : 0x01e00000
dtb img : dt.img
cmd line : console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 androidboot.bootloader=L2C28080AW00 109f10eed3f021e3
ramdisk is gzip format.
Unpack completed.
 

Attachments

Last edited:
You can create your own releasekeys using AOSP source or use my keys.

Just in case you want to go through this process yourself to verify the correctness of my work.
This is the command to dump public keys. {make the res/keys file}

java -cp .:./bcprov-jdk15on-153.jar com.android.dumpkey.DumpPublicKey releasekey.x509.pem > /path/filename

Unpack your recovery.img. NOTE: Not with unmkbootimg this recovery is not built in a standard way. It includes a dt.img

Replace the /res/keys file with the one you made with the dump.

Repack the recovery.img NOTE: most of the boot.img tools out there dont work because the format of this recovery. They will repack the recovery but not with the correct offsets and the dt.img

I have included in this zip the files you need to dump the /res/keys. Again use Linux
 

Attachments

You must log in or register to reply here.
Back
Top Bottom