Root Roms For The Fierce 2

[Bigcountry907]

Maybe the busybox cp will work for symlinks.

cp

cp [OPTIONS] SOURCE DEST

Copy SOURCE to DEST, or multiple SOURCE(s) to DIRECTORY

Options:

-a Same as -dpR
-R,-r Recurse
-d,-P Preserve symlinks (default if -R)
-L Follow all symlinks
-H Follow symlinks on command line
-p Preserve file attributes if possible
-f Overwrite
-i Prompt before overwrite
-l,-s Create (sym)links
Would it be necessary to use -L or is -a good enough?

 

[jason39828]

sorry Bigcountry, passed out. 28 hours no sleep working two jobs can catch up with you....lol. Anyway I havent created a backup of the phone so need to know exactly how to do it so it will be right for what you need

 

[Csgfierce2]

Maybe the busybox cp will work for symlinks.

cp

cp [OPTIONS] SOURCE DEST

Copy SOURCE to DEST, or multiple SOURCE(s) to DIRECTORY

Options:

-a Same as -dpR
-R,-r Recurse
-d,-P Preserve symlinks (default if -R)
-L Follow all symlinks
-H Follow symlinks on command line
-p Preserve file attributes if possible
-f Overwrite
-i Prompt before overwrite
-l,-s Create (sym)links
Would it be necessary to use -L or is -a good enough?

i bricked my fierce 2 7040n i deleted the framework-res.apk file i have the original phone recovery you can help me? the mobile upgrade not working with this phone ...
i didnt do a backup how can put this file again

 

[Bigcountry907]

@jason39828
I will put together the commands to backup the partitions. We will create image files using adb.
Today i am taking a break. Too tired to think to much. But tommorow i will put something together.

@Csgfierce2
Unfortunately at this time i have no way to fix your phone.
If you would have flashed my recovery before you bootlooped you phone I would have a chance at fixing it. Defiantly soon. I just got to get the rom right.

I would recommend anyone who has a rooted phone to flash my recovery. Then if you get boot loop it will be fixable. For any phones stuck in boot loop until we find a way to flash the patched recovery I cant fix them.

I would flash the recovery right after I rooted this phone. It works and there is no reason not to. Theres nothing to loose and at aleast you have a safety net.

I will post a new recovery for the 7040T tommorow.
The recovery for the 7040N posted a couple of post back is good to go.

Do yourself a favor and flash the recovery before you mess with your system or custpack files.

 

[Csgfierce2]

@jason39828
I will put together the commands to backup the partitions. We will create image files using adb.
Today i am taking a break. Too tired to think to much. But tommorow i will put something together.

@Csgfierce2
Unfortunately at this time i have no way to fix your phone.
If you would have flashed my recovery before you bootlooped you phone I would have a chance at fixing it. Defiantly soon. I just got to get the rom right.

I would recommend anyone who has a rooted phone to flash my recovery. Then if you get boot loop it will be fixable. For any phones stuck in boot loop until we find a way to flash the patched recovery I cant fix them.

I would flash the recovery right after I rooted this phone. It works and there is no reason not to. Theres nothing to loose and at aleast you have a safety net.

I will post a new recovery for the 7040T tommorow.
The recovery for the 7040N posted a couple of post back is good to go.

Do yourself a favor and flash the recovery before you mess with your system or custpack files.

haha omg and there is no way to do it with sdcard update?

 

[Bigcountry907]

haha omg and there is no way to do it with sdcard update?

No...only by sideload. Even the factory ota will not be found on the sdcard.

And the sideload or update thdough adb with ths recovery will only flash a factory signed by the factory update. Ie. The ota updates.

My patched recovery is a recovery with the key changed to take files signed by my keys.

For boot loop soneone needs to figur out how to use thd qualcom qdl 9008 toolz.

Turn off your phone. Hold volume down and plug into computer wile holding down volume.

You will find a new device

 

[Bigcountry907]

You can backup the phone to the sd card. Use onandroid script. But ya there is no cwm or twrp. The bootloader is locked but it dont mind the changed key in the recovery

Try cwm or twrp recovery and i guarentee u boot loop.

My recovery is stock just with patched key for flashing updatd zips

 

[Bigcountry907]

Oh one more thing. Using adb i will be getting the raw image files.

I can mount them in linux without screwing up the symlinks and permissions.

I hope anyway the symlinks should get copied. Considering evrn the 0 byte or empty memory of the partition gets copied

 

[Csgfierce2]

No...only by sideload. Even the factory ota will not be found on the sdcard.

And the sideload or update thdough adb with ths recovery will only flash a factory signed by the factory update. Ie. The ota updates.

My patched recovery is a recovery with the key changed to take files signed by my keys.

For boot loop soneone needs to figur out how to use thd qualcom qdl 9008 toolz.

Turn off your phone. Hold volume down and plug into computer wile holding down volume.

You will find a new device

thanks i got the adb driver and cmd and i can access to system files but i cant push the framework-res.apk launch an error say the file is read only

the phone dont have fast boot

about the rom you uploaded dont have the boot.img to launch in adb update

 

[Csgfierce2]

so please can anyone upload the original rom of alcatel fierce 2 7040N?

 

[Djuane]

Please make a lollipop rom

 

[Bigcountry907]

I have the boot image.
There is no need to flash it.

so please can anyone upload the original rom of alcatel fierce 2 7040N?

There is no original rom. Alcatel never released one.
If they had i never would have needed to do all this work.

You really messed up your phone.
You cant just delete things without knowing what they do. Especially when the boot-loader is locked.

The problem is you can no longer access adb as root. Since you boot-looped your phone.

If you would have flashed my recovery before you broke your phone i could have fixed it easy. Now its a little late.

There is no way to flash the recovery for you.
Until I figure out how to do this with the qualcom tools your phone is broke. For good.

adb update is to update android sdk. Not your phone silly.

I would reccommend you go back through this thread and read it.
There is alot going on here. Its a good way to learn.

 

[Bigcountry907]

@jason39828
I put together the commands to back up the entire phone partition by partition.
It will be real helpful for me to have these files. Then i should be able to fix this rom.

I uploaded a text file. If you put it in the c:\android\sdk\platform-tools folder and rename it from ,txt to .bat Im pretty sure you can double click on it or run it automatically.

COMMAND SEQUENCE
It will copy the files to the sd card 1 at a time.
Copy it to the c:\android\sdk\platform-tools folder
Then delete it from the sd card
and go to the next file.
This way sd card space isnt an issue.
FINISHED BACKUP

After you are all done getting the files. Just zip the platform-tools folder and upload it on google drive. Then post the link or PM me. I appreciate your help. Very Very much

 

[Bigcountry907]

I need backups from the 7040T as well. So if one of you have it please do the same as above post. In case the .bat file dont work. Run the following commands in adb one line at a time.
Just copy and paste the commands.

If anyone needs help doing this let me know.
Each set of three lines completes a backup of one partition. There are 30 total.

adb shell su -c "dd if=/dev/block/mmcblk0p1 of=/storage/sdcard0/modem.mbn"
adb pull /storage/sdcard0/modem.mbn
adb shell su -c "rm -f /storage/sdcard0/modem.mbn"

adb shell su -c "dd if=/dev/block/mmcblk0p2 of=/storage/sdcard0/sbl1.img"
adb pull /storage/sdcard0/sbl1.img
adb shell su -c "rm -f /storage/sdcard0/sbl1.img"

adb shell su -c "dd if=/dev/block/mmcblk0p3 of=/storage/sdcard0/sdi.img"
adb pull /storage/sdcard0/sdi.img
adb shell su -c "rm -f /storage/sdcard0/sdi.img"

adb shell su -c "dd if=/dev/block/mmcblk0p4 of=/storage/sdcard0/DDR.img"
adb pull /storage/sdcard0/DDR.img
adb shell su -c "rm -f /storage/sdcard0/DDR.img"

adb shell su -c "dd if=/dev/block/mmcblk0p5 of=/storage/sdcard0/emmc_appsboot.mbn"
adb pull /storage/sdcard0/emmc_appsboot.mbn
adb shell su -c "rm -f /storage/sdcard0/emmc_appsboot.mbn"

adb shell su -c "dd if=/dev/block/mmcblk0p6 of=/storage/sdcard0/rpm.img"
adb pull /storage/sdcard0/rpm.img
adb shell su -c "rm -f /storage/sdcard0/rpm.img"

adb shell su -c "dd if=/dev/block/mmcblk0p7 of=/storage/sdcard0/boot.img"
adb pull /storage/sdcard0/boot.img
adb shell su -c "rm -f /storage/sdcard0/boot.img"

adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/storage/sdcard0/tz.img"
adb pull /storage/sdcard0/tz.img
adb shell su -c "rm -f /storage/sdcard0/tz.img"

adb shell su -c "dd if=/dev/block/mmcblk0p9 of=/storage/sdcard0/pad.img"
adb pull /storage/sdcard0/pad.img
adb shell su -c "rm -f /storage/sdcard0/pad.img"

adb shell su -c "dd if=/dev/block/mmcblk0p10 of=/storage/sdcard0/modemst1.mbn"
adb pull /storage/sdcard0/modemst1.mbn
adb shell su -c "rm -f /storage/sdcard0/modemst1.mbn"

adb shell su -c "dd if=/dev/block/mmcblk0p11 of=/storage/sdcard0/modemst2.mbn"
adb pull /storage/sdcard0/modemst2.mbn
adb shell su -c "rm -f /storage/sdcard0/modemst2.mbn"

adb shell su -c "dd if=/dev/block/mmcblk0p12 of=/storage/sdcard0/study.img"
adb pull /storage/sdcard0/study.img
adb shell su -c "rm -f /storage/sdcard0/study.img"

adb shell su -c "dd if=/dev/block/mmcblk0p13 of=/storage/sdcard0/fsc.img"
adb pull /storage/sdcard0/fsc.img
adb shell su -c "rm -f /storage/sdcard0/fsc.img"

adb shell su -c "dd if=/dev/block/mmcblk0p14 of=/storage/sdcard0/ssd.img"
adb pull /storage/sdcard0/ssd.img
adb shell su -c "rm -f /storage/sdcard0/ssd.img"

adb shell su -c "dd if=/dev/block/mmcblk0p15 of=/storage/sdcard0/tunning.img"
adb pull /storage/sdcard0/tunning.img
adb shell su -c "rm -f /storage/sdcard0/tunning.img"

adb shell su -c "dd if=/dev/block/mmcblk0p16 of=/storage/sdcard0/traceability.img"
adb pull /storage/sdcard0/traceability.img
adb shell su -c "rm -f /storage/sdcard0/traceability.img"

adb shell su -c "dd if=/dev/block/mmcblk0p17 of=/storage/sdcard0/mobile_info.img"
adb pull /storage/sdcard0/mobile_info.img
adb shell su -c "rm -f /storage/sdcard0/mobile_info.img"

adb shell su -c "dd if=/dev/block/mmcblk0p18 of=/storage/sdcard0/splash.img"
adb pull /storage/sdcard0/splash.img
adb shell su -c "rm -f /storage/sdcard0/splash.img"

adb shell su -c "dd if=/dev/block/mmcblk0p19 of=/storage/sdcard0/custpack.img"
adb pull /storage/sdcard0/custpack.img
adb shell su -c "rm -f /storage/sdcard0/custpack.img"

adb shell su -c "dd if=/dev/block/mmcblk0p20 of=/storage/sdcard0/emmc_appsbootbk.mbn"
adb pull /storage/sdcard0/emmc_appsbootbk.mbn
adb shell su -c "rm -f /storage/sdcard0/emmc_appsbootbk.mbn"

adb shell su -c "dd if=/dev/block/mmcblk0p21 of=/storage/sdcard0/rpmbk.img"
adb pull /storage/sdcard0/rpmbk.img
adb shell su -c "rm -f /storage/sdcard0/rpmbk.img"

adb shell su -c "dd if=/dev/block/mmcblk0p22 of=/storage/sdcard0/tzbk.img"
adb pull /storage/sdcard0/tzbk.img
adb shell su -c "rm -f /storage/sdcard0/tzbk.img"

adb shell su -c "dd if=/dev/block/mmcblk0p23 of=/storage/sdcard0/fota.img"
adb pull /storage/sdcard0/fota.img
adb shell su -c "rm -f /storage/sdcard0/fota.img"

adb shell su -c "dd if=/dev/block/mmcblk0p24 of=/storage/sdcard0/redbend.img"
adb pull /storage/sdcard0/redbend.img
adb shell su -c "rm -f /storage/sdcard0/redbend.img"

adb shell su -c "dd if=/dev/block/mmcblk0p25 of=/storage/sdcard0/misc.img"
adb pull /storage/sdcard0/misc.img
adb shell su -c "rm -f /storage/sdcard0/misc.img"

adb shell su -c "dd if=/dev/block/mmcblk0p26 of=/storage/sdcard0/cache.img"
adb pull /storage/sdcard0/cache.img
adb shell su -c "rm -f /storage/sdcard0/cache.img"

adb shell su -c "dd if=/dev/block/mmcblk0p27 of=/storage/sdcard0/persist.img"
adb pull /storage/sdcard0/persist.img
adb shell su -c "rm -f /storage/sdcard0/persist.img"

adb shell su -c "dd if=/dev/block/mmcblk0p28 of=/storage/sdcard0/system.img"
adb pull /storage/sdcard0/system.img
adb shell su -c "rm -f /storage/sdcard0/system.img"

adb shell su -c "dd if=/dev/block/mmcblk0p29 of=/storage/sdcard0/recovery.img"
adb pull /storage/sdcard0/recovery.img
adb shell su -c "rm -f /storage/sdcard0/recovery.img"

adb shell su -c "dd if=/dev/block/mmcblk0p30 of=/storage/sdcard0/data.img"
adb pull /storage/sdcard0/data.img
adb shell su -c "rm -f /storage/sdcard0/data.img"

 

[Bigcountry907]

@ Scary Alien
Im just wondering if it would be a good idea to split off the Recovery Images and the Test file to a separate thread.
We can still leave them here but when they get all mixed in maybe hard to find?

This thread is moving so fast lately I dont know if the links will get lost in action.

Thanks
Rich.

 

[Bigcountry907]

Im really new to rooting. I have rooted my 7040N and already have SuperSU instead of Kingroot. Now i don't know what to do. What if something goes wrong, and i am pretty new to roms flashing etc.

My best advice to you is.

AT a minimum download the recovery.img for the 7040N.

Flash it to your phone with Flashify. It is very easy to use. You install Flashify from here.

https://play.google.com/store/apps/details?id=com.cgollner.flashify

Then in flashify you pick flash recovery.
Select the file for the 7040N.
Flash.

Phone will reboot to recovery.
Just select reboot now.
Thats all.

Then you have a safety net.

If you want to make a backup of your phone PM me and i will walk you through it.

 

[scary alien]

@ Scary Alien
Im just wondering if it would be a good idea to split off the Recovery Images and the Test file to a separate thread.
We can still leave them here but when they get all mixed in maybe hard to find?

This thread is moving so fast lately I dont know if the links will get lost in action.

Thanks
Rich.

Ah, Rich, I'd be happy to...but, like you said, the fur is certainly flying in this thread and I'm a bit behind on being able to read/absorb all you've got going on.

If you could let me know which posts or the proper starting point to carve-out for you, I'd be happy to do that.

Lemme know .

(and keep up the awesome work here! we all very much appreciate your efforts and contributions here )

 

[Bigcountry907]

#141 and #142 would be good.

Then under those two post i can try to make a simpler tutorial.
No rush. Im just trying to think ahead here for the long term.

Thank You

 

[scary alien]

#141 and #142 would be good.

Then under those two post i can try to make a simpler tutorial.
No rush. Im just trying to think ahead here for the long term.

Thank You

No worries! All done:

http://androidforums.com/threads/new-recovery-image-for-the-7040t.993682/​

with new name:

http://androidforums.com/threads/new-recovery-for-alcatel-one-touch-fierce-2.993682/​

Let me know if and what you'd like the title to say.

Cheers!

 

[Bigcountry907]

Ok everybody just to avoid confusion or trouble finding the files a new thread was created here.
http://androidforums.com/threads/new-recovery-for-alcatel-one-touch-fierce-2.993682/

That is where the recovery images are located and the test files for testing the recovery.

 

[MSD2g]

My best advice to you is.

AT a minimum download the recovery.img for the 7040N.

Flash it to your phone with Flashify. It is very easy to use. You install Flashify from here.

https://play.google.com/store/apps/details?id=com.cgollner.flashify

Then in flashify you pick flash recovery.
Select the file for the 7040N.
Flash.

Phone will reboot to recovery.
Just select reboot now.
Thats all.

Then you have a safety net.

If you want to make a backup of your phone PM me and i will walk you through it.

Okay thanks! Sorry I was following up from from2 pages back. My email couldn't update and I saw that there were more discussions happening right now.

 

[whatsupdoc]

I installed recovery7040T.img through Flashify then booted into recovery mode. I tried to sideload message.zip, but got * cannot read 'message.zip' *
Is this mean that recovery7040T.img was not installed? I am attaching the adb screenshot and phone screenshot.

Ok thats good. reboot your phone its still fine. Flashify automatically boots you into recovery after it flashes it.

To sideload open up adb.

attach phone to computer
reboot the phone to recovery.
in recovery select apply update from ADB.

on the computer in ADB shell
type
adb devices
you should see sideload
if you do
type

adb sideload message.zip

 

[Bigcountry907]

@whatsupdoc

you have to cd to the directory where adb.exe is. And also you have to copy the message.zip file there.

By default it should be

c:\android\sdk]platform-tools

The message.zip must be in that directory and the command prompt must be cd to that directory.

Then do adb sideload message.zip

 

[whatsupdoc]

Thanks, that did it and your recovery worked.

@whatsupdoc

you have to cd to the directory where adb.exe is. And also you have to copy the message.zip file there.

By default it should be

c:\android\sdk]platform-tools

The message.zip must be in that directory and the command prompt must be cd to that directory.

Then do adb sideload message.zip

 

[Bigcountry907]

@whatsupdoc
What phone do you have?

7040N or 7040T

I could really use some files from your phone to finish the rom.