Hey,
I've been messing around with flashify app to see if it will install a custom TWRP or CWM as a recovery image but made sure i backed up my recovery using ES File Explorer (as root) /dev/block/platform/msm_sdcc.1/by-name/ recovery and by all intents and purposes it would work if there was a custom recovery out there that would support the Amazon Fire Phone.
When i install a random phones custom recovery and boot up into recovery it will show the amazon screen then with power and up button pressed it will go to a plain black screen.
I would the recover my original recovery file to area mentioned above after this not working and i would have my normal recovery again.
Just wondering if anyone can utilize this info as i know that the Kindle HDX managed to have a custom recovery installed on with with a locked bootloader.
I am currently looking at building a custom CWM recovery for device but if anyone else has better understanding of how to do this it might save a lot of time lol
TheDynamo said:
Hey,
I've been messing around with flashify app to see if it will install a custom TWRP or CWM as a recovery image but made sure i backed up my recovery using ES File Explorer (as root) /dev/block/platform/msm_sdcc.1/by-name/ recovery and by all intents and purposes it would work if there was a custom recovery out there that would support the Amazon Fire Phone.
When i install a random phones custom recovery and boot up into recovery it will show the amazon screen then with power and up button pressed it will go to a plain black screen.
I would the recover my original recovery file to area mentioned above after this not working and i would have my normal recovery again.
Just wondering if anyone can utilize this info as i know that the Kindle HDX managed to have a custom recovery installed on with with a locked bootloader.
I am currently looking at building a custom CWM recovery for device but if anyone else has better understanding of how to do this it might save a lot of time lol
Click to expand...
Click to collapse
I'm doing experiments, I flashed the TWRP version of the Galaxy Note 3 HLTE as they share processor but has not worked, I keep trying.
Best regards,
Just spent hours trying to make a custom CWM recovery image in Ubuntu 14.04 following the guide below but didn't have much luck. May try again at the weekend. If anyone else wants to have a go i have attached recovery and boot images
http://forum.xda-developers.com/android/development/guide-how-to-build-cwm-based-recovery-t2973804
On my KDFIRE Soho is the bootloader Locked and Stock recovery. But you can Flash Roms with the Stock Recovery. There is something with the signature. But only custom Roms based on FireOS Are Working. The FireOS Statusbar is my Personal Nightmare
Well I ported a custom CWM recovery but unfortunately it still does not work when installing with Flashify get the same black screen - Attached.
This made me laugh today
Amazon.co.uk
Your Account Amazon.co.uk
Message From Customer Service
Hello,
I understand that you are not happy, as bootloader is locker for Amazon Fire Phone and would like to have a Key to unlock Bootloader.
I realise that you have been greatly inconvenienced by this situation, it is never our intention to cause inconvenience to our valued customers like you. Please accept my apologies.
Unfortunately, at this time we do not have option to provide Key to unlock Bootloader.
Customer feedback like yours is very important in helping us continue to improve the Fire phone experience. I've forwarded your message to our Fire Phone Team for consideration as we make further improvements.
Thanks for taking the time to provide your feedback.
We look forward to seeing you again soon.
Warmest regards,
Sravanthi
Your feedback is helping us build Earth's Most Customer-Centric Company.
Amazon.co.uk
here's something you should consider.. make a single byte modification to the original bootloader and see if it boots.. if it does.. then we're clear.. if not we're ****ed.. if we're ****ed, then we need to deal with the procedure authenticating (and probably hashing) the recovery.. the bootloader.. or hashcode's hijack it is...
AbdouRetro said:
here's something you should consider.. make a single byte modification to the original bootloader and see if it boots.. if it does.. then we're clear.. if not we're ****ed.. if we're ****ed, then we need to deal with the procedure authenticating (and probably hashing) the recovery.. the bootloader.. or hashcode's hijack it is...
Click to expand...
Click to collapse
So did anyone tried this? It's very easy to do.
Pull your recovery image
Code:
adb shell
su
cat /dev/block/platform/msm_sdcc.1/by-name/recovery > /sdcard/recovery.img
exit
adb pull /sdcard/recovery.img .
then open it up in a hex editor (hdx - windows/ vi - linux) and change a useless byte (probably at the end of the file) or unpack/repack the image using unmkbbotimg/mkbootimg. Then push it back
Code:
adb push recovery.img /sdcard/recovery-new.img
adb shell
su
cat /sdcard/recovery-new.img /dev/block/platform/msm_sdcc.1/by-name/recovery
exit
Then try rebooting to your recovery
Code:
adb reboot recovery
If it works, We might be able to replace stock recovery with a custom built CWM recovery or something since we have the kernel source available. As it seems in update-script, recovery has access to everything weather bootloader is unlocked or not. If you can't modify recovery image yourself, post it here. I'll modify it for you.
madushan1000 said:
So did anyone tried this? It's very easy to do.
Pull your recovery image
Code:
adb shell
su
cat /dev/block/platform/msm_sdcc.1/by-name/recovery > /sdcard/recovery.img
exit
adb pull /sdcard/recovery.img .
then open it up in a hex editor (hdx - windows/ vi - linux) and change a useless byte (probably at the end of the file) or unpack/repack the image using unmkbbotimg/mkbootimg. Then push it back
Code:
adb push recovery.img /sdcard/recovery-new.img
adb shell
su
cat /sdcard/recovery-new.img /dev/block/platform/msm_sdcc.1/by-name/recovery
exit
Then try rebooting to your recovery
Code:
adb reboot recovery
If it works, We might be able to replace stock recovery with a custom built CWM recovery or something since we have the kernel source available. As it seems in update-script, recovery has access to everything weather bootloader is unlocked or not. If you can't modify recovery image yourself, post it here. I'll modify it for you.
Click to expand...
Click to collapse
so this works i just tested it, I used the method you posted about changed the last bit with the hex editor, changed the last octet from 00 to 01, used flashify to flash the recovery
Heres the link to the recovery I modded if you want to test/verify:
https://drive.google.com/file/d/0Bw62MrywuCbwNUZ3Sm05b3FBMGM/view?usp=sharing
thoughtlesskyle said:
so this works i just tested it, I used the method you posted about changed the last bit with the hex editor, changed the last octet from 00 to 01, used flashify to flash the recovery
Heres the link to the recovery I modded if you want to test/verify:
https://drive.google.com/open?id=0Bw62MrywuCbwNUZ3Sm05b3FBMGM
Click to expand...
Click to collapse
You changed a bit at the end of the image right? Then that doesn't make any difference. Sorry I was misleading the last time. I didn't know any better myself then. Recovery partition doesn't contain the recovery image in its entirety. There is extra space. What bootloader does is, it reads the image Heder from the first few bytes of the partition, header contains the length of the recovery image. Then the bootloader verify that length of the recovery partition against some encrypted hash. So to check if this really works (My bet is it doesn't) we have to change a bit inside the length of the recovery image. The easiest thing to do is, unpack and repack the recovery image. I'll give it a try later and post the results.
madushan1000 said:
You changed a bit at the end of the image right? Then that doesn't make any difference. Sorry I was misleading the last time. I didn't know any better myself then. Recovery partition doesn't contain the recovery image in its entirety. There is extra space. What bootloader does is, it reads the image Heder from the first few bytes of the partition, header contains the length of the recovery image. Then the bootloader verify that length of the recovery partition against some encrypted hash. So to check if this really works (My bet is it doesn't) we have to change a bit inside the length of the recovery image. The easiest thing to do is, unpack and repack the recovery image. I'll give it a try later and post the results.
Click to expand...
Click to collapse
Yeah i changed the one at the end, hopefully your testing does work, the way you explained it did make sense
Sent from my A0001 using Tapatalk
This is a no-go, I unpacked and repacked the stock recovery with bootimg-tools (so that it would have no signature information) and flashed it on to recovery partition. The device hangs on Amazon logo when I reboot to recovery. We need to find a way to unlock the bootloader
Related
Now that I'm satisfied with the results from the original testing thread, I'd like to announce the general public release of my modified version of the FIREFIREFIRE 1.2 bootloader. The main feature? You can dualboot two different ROMs! All of the downloads I'm providing are listed in the second post.
Standard disclaimer: I am not responsible for anything that happens to your Kindle Fire as a result of using this software. I designed this in my spare time, voluntarily, and choose to release it for others to hopefully enjoy. Although it has been safe throughout testing there is always a risk involved in modifying your device, including unpredictable and uncontrollable circumstances that I cannot prepare for. You have been given a fair warning.
Installation
You can install FFF Extended like you would any other bootloader:
Download the latest zipped binary from GitHub (links below).
Extract the u-boot.bin file from the zip. This is the bootloader.
If you already have a custom bootloader you can install from fastboot by rebooting into fastboot and executing fastboot flash bootloader u-boot.bin from a PC shell. You can also run this on your PC first and then reboot with your device plugged in; it should run when your device starts up fastboot.
If you do NOT have a custom bootloader, you can follow pokey9000's instructions for the original FFF:
Code:
Howto flash by hand
- Get into fastboot mode somehow. Having and older FFF from the TWRP
installer is a good start. Currently KFU or fbmode is the easiest
- flash with "fastboot -i 0x1949 flash bootloader u-boot.bin"
(take out "-i 0x1949" if FFF is already installed)
- disable fastboot: "fastboot -i 0x1949 oem idme bootmode 4000"
- reboot: "fastboot -i 0x1949 reboot"
Done! The bootloader is installed.
Prepping for dualboot
Once the bootloader is installed, you can use it right away to boot into recovery or your normal ROM. In order to use your device to dualboot, though, you're going to need to do a little bit of up-front configuration.
NOTE: Backup the data on your sdcard partition. It will be formatted during the setup procedure.
Get into fastboot somehow and execute fastboot oem dualformat
Reboot your device into recovery mode.
Use your recovery to format/wipe your sdcard partition. This varies between CWM and TWRP, but it will be in the "wipe" or "advanced" menus.
Download altrom-format-all.zip and flash it from recovery to properly format your secondary partition set.
Your device should be ready to flash an alternate ROM now.
To return to a stock partition layout, connect your device to a PC, reboot into fastboot, and execute fastboot oem format from a PC shell. You will probably want to format your sdcard partition afterwards.
Installing alternate ROMs
If you want to install an alternate ROM, the ROM must be properly packaged to use the secondary partition set instead of the default ones. Normal ROMs will install ONLY to your regular partition slots.
I am currently providing one ROM, which is a CM7 KANG build and a GAPPs package for it. You do not need to do anything special to install the ROM, just flash it from recovery as you normally would (see downloads below).
If you want to install a new alternate ROM, you can flash the altrom-factory-reset.zip to perform a "factory reset" of your alternate partitions (it will wipe data2 and cache2).
You cannot currently make a nandroid backup of an alternate ROM install (unless you want to manually use 'dd' or something). This would require recovery changes which I may or may not try to implement at some point, or someone else is welcome to do it if they feel so compelled.
Each ROM will have its own boot, data, system, and cache partitions and they will share your sdcard (media) partition. They run completely separately, and modifications to the kernel, apps, system, etc of one will not in any way affect the other.
Using the boot menu
FIREFIREFIRE Extended listens for 5 seconds and starts up fastboot like FFF1.2 does, but when you press the power button it starts a new 2.5 second countdown and effectively changes the selected boot state. This provides more flexibility because it allows you to "cycle" between boot options instead of just being a one-shot thing. Note that there is a slight delay before the power button will accept input, but you can tell when it's ready when the LED fades from bright green to darker green. You can see a demo of the boot menu on YouTube here: http://www.youtube.com/watch?v=xV2Jtu3fDSM
Packaging alternate ROMs
If you're a ROM author and would like to package your ROM for alternate booting, please see the "how-to" page on my GitHub. Note that some ROMs seem to play more nicely than others, so you may experience some bugs when running your ROM from the alternate partition set. I'd be happy to try to help you out if I can, but I can't guarantee that I'll know the solution to your specific issues.
Downloads and Source
Downloads are provided in the second post. The source for FFF Extended is available on my GitHub and is licensed under the GNU GPLv2. I've also set up a few wiki pages on my GitHub with some additional information about the bootloader.
Credits
Thanks and appreciation to:
pokey9000 for all of his development, tutorials, etc for FIREFIREFIRE and omap4boot.
All of the people that helped me test this.
Everyone who's worked on the CM7 repos that my altrom version is built on, both for the KF specifically (whistlestop, IngCr3at1on) and the CM project as a whole.
Downloads
These are various downloads provided by me. If you get a ROM from somewhere other than this post, I didn't package it. So if you have bugs, talk to the ROM author first
Bootloader
Latest version: GitHub, Mediafire (md5 of the u-boot.bin: 89df8d45262a92061c461e8ff134286a)
All versions: GitHub
Setup/Maintenance Files
altrom-format-all.zip (reformats all secondary partitions, flash from recovery)
altrom-factory-reset.zip (factory reset for your secondary partitions, flash from recovery)
My altboot ROMs
CyanogenMod7 KANG
Gingerbread GAPPS for altboot partitions
Bugs in this ROM: Unpredictably hangs on boot very occasionally (once every 5 or 6 boots, maybe?). Rebooting fixes it.
Kernels
IntersectRaven's 2.6.35.14 CM7 kernel, repackaged for altboot partitions (Thanks IR!): http://www.mediafire.com/?6b5545b55tx5jwd
Wooo hoooo, can't wait!!!!
Sent from my classic stock
Nice nice nice! Could you make a guide to change the updater-script for random ROM ?
Trojan38 said:
Nice nice nice! Could you make a guide to change the updater-script for random ROM ?
Click to expand...
Click to collapse
Check out the wiki page on GitHub. If you think it could use expansion feel free to let me know
Thanks and appreciation to:
pokey9000 for all of his development, tutorials, etc for FIREFIREFIRE and omap4boot.
All of the people that helped me test this.
Everyone who's worked on the CM7 repos that my altrom version is built on, both for the KF specifically (whistlestop, IngCr3at1on) and the CM project as a whole.
I think this is not so easy, you'll need to compile a source code of random rom.
Oh okay, I thought it was more simple, something like renaming partition names in the updater-script . Will take a look at it, thanks .
animefun135 said:
Thanks and appreciation to:
pokey9000 for all of his development, tutorials, etc for FIREFIREFIRE and omap4boot.
All of the people that helped me test this.
Everyone who's worked on the CM7 repos that my altrom version is built on, both for the KF specifically (whistlestop, IngCr3at1on) and the CM project as a whole.
I think this is not so easy, you'll need to compile a source code of random rom.
Click to expand...
Click to collapse
What?
eldarerathis said:
What?
Click to expand...
Click to collapse
Nevermind
I've installed your bootloader and running altcm7 rom, but if I want flash cm7 or cm9 kernels - how to determine to whom it is intended?
animefun135 said:
Nevermind
I've installed your bootloader and running altcm7 rom, but if I want flash cm7 or cm9 kernels - how to determine to whom it is intended?
Click to expand...
Click to collapse
If you mean "how do I know where it will install?" then it's all based on how it's packaged. Unless the ROM/kernel author packages the zip for the alternate partitions and specifically says that's what it's for, it will install for your regular ones. So everything is for your primary ROM unless otherwise noted by the author.
Dualboot Support for CM9
When will there be dualboot support for CM9??
thedeveloper1 said:
When will there be dualboot support for CM9??
Click to expand...
Click to collapse
When it's done.
Fixed
stephenm00 said:
What about a stock kindle image for the 2nd rom?
Click to expand...
Click to collapse
This would be quite a feat.
Sent from my Amazon Kindle Fire using XDA
I am kinda new to all of this so this is maybe a noob question!
I have Flashed FFF extended, but before Formatting my SD Card, I am just having some simple question: Would running 2 ROMs on my Kindle Fire be really heavy, we have a 8Gb of storage in your Kindle Fire and how much would it take out of the 8Gb? Is it acceptable for a "user" such as myself, I mean I will still have space to storage my personal data
Thanks!
pmdisawesome said:
I am kinda new to all of this so this is maybe a noob question!
I have Flashed FFF extended, but before Formatting my SD Card, I am just having some simple question: Would running 2 ROMs on my Kindle Fire be really heavy, we have a 8Gb of storage in your Kindle Fire and how much would it take out of the 8Gb? Is it acceptable for a "user" such as myself, I mean I will still have space to storage my personal data
Thanks!
Click to expand...
Click to collapse
Of the 8 GB, about 6 is usable by you normally, and 1 GB of that is reserved for apps leaving ~5 GB of general storage space (the "sdcard" partition). You'll end up with about 1 GB of data space (e.g. apps and the like) per ROM and 3.6 GB of general storage space using FFFE.
eldarerathis said:
Check out the wiki page on GitHub. If you think it could use expansion feel free to let me know
Click to expand...
Click to collapse
Thanks for taking the time to type this up, it helps alot. And thanks for your work on this project
Wow! Thanks for making this for us! It's amazing!
stephenm00 said:
What about a stock kindle image for the 2nd rom?
Click to expand...
Click to collapse
I have stock rooted 6.3 insecure, originally from here modded to install to the alternate partition.
If you want it, let me know and I can find a place to put it.
three-p-o said:
I have stock rooted 6.3 insecure, originally from here modded to install to the alternate partition.
If you want it, let me know and I can find a place to put it.
Click to expand...
Click to collapse
I know I want it........Please.
Hello there,
Today I will teach you how to make a full backup of your Spreadtrum phone !
This tutorial may also work on several other phones.
CWM can make a nearly full backup of your Spreadtrum, but it's not enough unfortunately.
Android is compartmented in 4 main partitions. You have theses partition:
* boot - It contains the Linux kernel
* System - It contains Android
* Recovery - It contains the recovery system, CWM if you installed it.
* DATA - It contain your personal datas, and should not be published online if you share your backup online.
But Android is one thing, your phone also have a lot of bios, firmwares, and bootloaders. Theses are not saved by traditional backup utilities such as CWM.
Theses partitions includes:
* UBoot - Very important, this thing is the low level bootloader. It starts Linux !
* Modem Firmware - used to dial with your GSM provider
* DSP Firmware - Make video playback smoother using DSP resources.
* NV - It's some kind of encryption key with some low levels parameters. Very important !
* Lots of misc stuffs - Like the boot logo, the kernel panics logs (record the boot-up errors to help the debugging process), etc ...
* Lots of important misc stuffs - For example what start-up the device even before handing the phone to Uboot.
This thread will cover a new way to backup your device, working "only" on rooted Spreadtrum devices.
With this you can recreate your original firmware file, and then rescue your phone even on the worst case you can find. (And help those with the same phone as you but have made a big flashing mistake)
So first, you will need to root your device. It may be simple or difficult, it all depends of the device you have. The instructions on how to root your device are here: http://forum.xda-developers.com/showthread.php?t=2165554
When you are rooted, you will have to install the Spreadtrum drivers if it's not already the case and log into your device with ADB.
You can download the drivers here:
http://www.mediafire.com/download.php?c5nf3rlhxmxhu4x
http://www.mediafire.com/download.php?2tyg0k2xp3ejgyg
You can download ADB and learn how it work here: http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
Then you will have to tell adb what phone to use. By that I mean adding the PCI ID to a text file to tell adb that this peripheral is compatible.
The Spreadtrum PCI ID is 0x1782
add this line to "Your user directory/.android/adb_usb.ini"
Code:
0x1782
So when you are ready to go, you have to download this file: http://www.mediafire.com/download.php?y6wmegkc22gkr97
Then with adb, push it on your device with this command:
Code:
adb push backuptools.tar /data/local/tmp
Now we will extract the tools with this command:
Code:
adb shell su -c "tar -xvpf /data/local/tmp/backuptools.tar"
And now, let's start the backup process:
Code:
adb shell su -c "./mkbackup.sh"
and here we go, just wait a while and every partitions on your phone will be saved in the backup directory on the sd card !
You will never have to backup this way again as those partitions are read only, if you don't do crazy things they will never change. But if you want to make another backup I suggest you go with CWM (read this page if you don't have it: http://forum.xda-developers.com/showthread.php?t=2165554).
Please do another backup with CWM even if everything as gone right with this method. Just to double check !
PS: if CWM does not work for you, you just have to send me your boot.img file from your backup and I will make one compatible with your phone.
To restore your backups you will also need to have CWM, you also can use ResearchDownload if you manage to entirely brick your phone or if any attempts to make a CWM recovery fails. I will have to do a tutorial about that too.
Thanks a lot :good:
this is my boot.img after a full backup :www .mediafire.com/?gmnm65rn65b28c3
i need a CWM image for my GT-I9300 clone.
all the best.
monster-exodia said:
Thanks a lot :good:
this is my boot.img after a full backup :www .mediafire.com/?gmnm65rn65b28c3
i need a CWM image for my GT-I9300 clone.
all the best.
Click to expand...
Click to collapse
Hi,
Can I have the exact name of your device ? (it must be in the battery compartment)
Did you tried all the CWM already in the rooting tutorial ? (I added one this morning)
If none of them work, I made this recovery with the boot.img you provided: http://www.mediafire.com/download.php?aj2nman38j5cfip
Please don't forget to tell me what CWM work for you so I can add the name of your phone on the tutorial.
@ElectronikHear
phone model (in battery) : N9300
phone model : (system info) GT-I9300
Build number : MT6515M_C909_HT_V14
cpu hardware : SP6820A
..........
I never tried ... firslty how to to flash CMW recovery ?
thanks in advance.
deleted
monster-exodia said:
how to to flash CMW recovery ?
Click to expand...
Click to collapse
Well it's explained in the rooting tutorial.
If your phone have Fastboot you can flash using it. If you don't you can use the Spreadtrum flash utility called ResearchDownload.
Everything is here:
http://forum.xda-developers.com/showthread.php?t=2165554
As your phone is already rooted it will be a lot more simple to flash using "dd" or some android flashing utilities. Actually it doesn't work that way on theses phones, sorry ... So just do as the rooting tutorial explains.
Hi, I'm succesfully rooted my phone with the "rooted system partition image" method, but none of the CWM images work, so I would be grateful if you can send me the recovery image.
Device Info:
Phone model (in battery) : S6500-TV
Phone model : (system info) S560
Android Version: 4.0.3
Baseband Version: DM_BASE_12A_W12.32|sc8810_modem|08-9-2012 16:47:10
Kernel Version: 2.6.35.7 [email protected] #3
Software Version: T162_JYY_G2_P2_1_W1220P12_DNY_V0.8.1_20121015
Hardware Version: 1.1.0
boot.img : www .dropbox.com/s/ka43sd45em9lu9k/mtd9.boot.img
Thanks in advance.
monster-exodia said:
I never tried ... firslty how to to flash CMW recovery ?
thanks in advance.
Click to expand...
Click to collapse
Don't even try!
Backup first.
janzlev said:
Hi, I'm succesfully rooted my phone with the "rooted system partition image" method, but none of the CWM images work, so I would be grateful if you can send me the recovery image.
Device Info:
Phone model (in battery) : S6500-TV
Phone model : (system info) S560
Android Version: 4.0.3
Baseband Version: DM_BASE_12A_W12.32|sc8810_modem|08-9-2012 16:47:10
Kernel Version: 2.6.35.7 [email protected] #3
Software Version: T162_JYY_G2_P2_1_W1220P12_DNY_V0.8.1_20121015
Hardware Version: 1.1.0
boot.img : www .dropbox.com/s/ka43sd45em9lu9k/mtd9.boot.img
Thanks in advance.
Click to expand...
Click to collapse
Hi there,
Here is your new recovery: http://www.mediafire.com/download.php?iahnncpjhm44etn
Please tell me if it works so I can add it to the rooting tutorial ^^
Thank you very much !
Not working, after flashing the recovery, the phone enters into a boot loop.
Anyway thank you.
janzlev said:
Not working, after flashing the recovery, the phone enters into a boot loop.
Anyway thank you.
Click to expand...
Click to collapse
A boot loop ?
You mean the recovery is looping ? and if you try to boot as normal everything working ok ?
I don't know what has gone wrong ... Where did you find your boot.img ? Did you extract it from the rom as the tutorial said or extracted from a .pac file ?
Have you flashed it with fastboot or with ResearchDownload ?
ElectronikHeart said:
A boot loop ?
You mean the recovery is looping ? and if you try to boot as normal everything working ok ?
I don't know what has gone wrong ... Where did you find your boot.img ? Did you extract it from the rom as the tutorial said or extracted from a .pac file ?
Have you flashed it with fastboot or with ResearchDownload ?
Click to expand...
Click to collapse
Recovery does not start, normal boot enters into a boot loop, the boot.img is extracted from the rom as in the tutorial.
Flashed with ResearchDownload.
janzlev said:
Recovery does not start, normal boot enters into a boot loop, the boot.img is extracted from the rom as in the tutorial.
Flashed with ResearchDownload.
Click to expand...
Click to collapse
That's weird, really weird. Because the recovery partition is not involved in the normal boot procedure. So flashing a new recovery should not harm in any way the normal boot procedure.
I really don't know what have brought your phone in such state I'm afraid.
Maybe you should try to flash the recovery again. and see if everything is the same.
As the recovery is not involved in the normal boot process, it surely will not change anything, but as you have tried the over ones (CWM I mean), and that have not screwed your booting process, you may try to flash one of the non working ones again (but known for sure to not harm the boot process) to see if it work again.
Have you used the same FDL set as when you flashed the system partition and the over CWM ?
It's a good thing you have the full backup on your hand. Because you may surely be able to recover from that. I just have to make a tutorial about flashing the backup with ResearchDownload and explaining what file goes where from the backup.
ElectronikHeart said:
That's weird, really weird. Because the recovery partition is not involved in the normal boot procedure. So flashing a new recovery should not harm in any way the normal boot procedure.
I really don't know what have brought your phone in such state I'm afraid.
Maybe you should try to flash the recovery again. and see if everything is the same.
As the recovery is not involved in the normal boot process, it surely will not change anything, but as you have tried the over ones (CWM I mean), and that have not screwed your booting process, you may try to flash one of the non working ones again (but known for sure to not harm the boot process) to see if it work again.
Have you used the same FDL set as when you flashed the system partition and the over CWM ?
It's a good thing you have the full backup on your hand. Because you may surely be able to recover from that. I just have to make a tutorial about flashing the backup with ResearchDownload and explaining what file goes where from the backup.
Click to expand...
Click to collapse
Thanks would be really helpful, and yes I used the same FDL.
janzlev said:
Thanks would be really helpful, and yes I used the same FDL.
Click to expand...
Click to collapse
I made another CWM recovery for your phone, please try it: http://www.mediafire.com/download.php?lg7m6v49efzpnjk
Apparently was an error of ResearchDownload (It seems was flashing recovery.img into boot.), so I tried with another copy of ResearchDownload and FDL files and now works like a charm.
Thank you very much!
janzlev said:
Apparently was an error of ResearchDownload (It seems was flashing recovery.img into boot.), so I tried with another copy of ResearchDownload and FDL files and now works like a charm.
Thank you very much!
Click to expand...
Click to collapse
Can you tell me what version of ResearchDownload have this bug. It's a pretty scary one. I have to be sure I don't have it on my computer ...
By the way what CWM image is working ? The first or the second one ? (the two should work but I want to be sure before adding it to the main tutorial)
Thank you very much ! That's one more phone to the list of easily rootable Spreadtrums thanks to you !
Edit: And what FDLs you use precisely so I can rename the folder to reflect the use of this set for this phone (Is this the ones on the .pac firmware you've uploaded on the over topic ?)
RESEARCHDOWNLOAD R2.9.6010, with the R2.9.7002 everything's fine. Respect to the CWM images, after the error I tried with the second one, so maybe the first one also works, the FDLs that I used was extracted from the .pac dropbox.com/s/69yl8hn9361qpy5/FDLs-S6500-TV.tar
That's it, if I can help more, let me know.
janzlev said:
RESEARCHDOWNLOAD R2.9.6010, with the R2.9.7002 everything's fine. Respect to the CWM images, after the error I tried with the second one, so maybe the first one also works, the FDLs that I used was extracted from the .pac dropbox.com/s/69yl8hn9361qpy5/FDLs-S6500-TV.tar
That's it, if I can help more, let me know.
Click to expand...
Click to collapse
I think I have every informations I need ^^
I have added the recovery for S6500-TV to the main tutorial and will add in a short while the fdls to the FDL pack file.
Thanks again !
Backup
attached is my boot.img
to follow: entire backup
Greetings,
I'm trying to build a clockworkmod recovery for my smartphone Fujitsu Arrows X F-02E. I've got the stock recovery dumped from the phone (attachments) and the recovery.fstab. I used them to build recovery on this site builder.clockworkmod.com. Recovery compiled successfully. Then I flashed it to my phone. And when I try to boot into recovery nothing happens, the phone just boots normally into the system (the stock recovery, in its turn, booted normally). Can anyone help with making a CWM recovery?
UPDATE: I can't attach these files here so I've uploaded them to my Cubby: cubby.com/pl/Android/_1f03da99a7034dd6b5ed7cb27bcc0bb0
UPDATE2: There are source code files of firmware of F-02E here - http://spf.fmworld.net/oss/oss/f-02e/ But I'm not advanced in programming enough to use it.
Cat In Boots said:
Greetings,
I'm trying to build a clockworkmod recovery for my smartphone Fujitsu Arrows X F-02E. I've got the stock recovery dumped from the phone (attachments) and the recovery.fstab. I used them to build recovery on this site builder.clockworkmod.com. Recovery compiled successfully. Then I flashed it to my phone. And when I try to boot into recovery nothing happens, the phone just boots normally into the system (the stock recovery, in its turn, booted normally). Can anyone help with making a CWM recovery?
UPDATE: I can't attach these files here so I've uploaded them to my Cubby: cubby.com/pl/Android/_1f03da99a7034dd6b5ed7cb27bcc0bb0
Click to expand...
Click to collapse
did you use
# cat /proc/mtd
or http://forum.xda-developers.com/showthread.php?t=2334554
to get the recovery.img
hechis said:
did you use
# cat /proc/mtd
or http://forum.xda-developers.com/showthread.php?t=2334554
to get the recovery.img
Click to expand...
Click to collapse
I've used different ways. Using adb I've downloaded, for a backup, all files from phone in /dev/block/ section. I've got 45 files,from mmcblk0 to mmcblk45, and only two of them had 10240kb size, one of them was a recovery. Then I've made backup with recovery-tools and got one more .img file. Checking the md5 sums showed that mmcblk32 is equal to recovery.img. So here it is. As alternative way I could get this recovery by copying /dev/block/platform/sdhci-tegra.3/by-name/SOS . It's the same recovery and equal to mmcblck32. So there is no doubt that it's the correct file we need.
UPDATE2: There are source code files of firmware of F-02E here - http://spf.fmworld.net/oss/oss/f-02e/ But I'm not advanced in programming enough to use it.
Found this info - blogs.yahoo.co.jp/y_19980320/33484520.html (use google translate). It seems that bootloader is locked and it's divided into 2 parts. First one, BL1 (not re-writable) is checking the authenticity of the BL2 (re-writable, but without correct signature it has no sense) after that, BL2 checks the kernel and boot the phone. Can we do something with that? (hello Motorola Defy)
And in the second post - blogs.yahoo.co.jp/y_19980320/33513111.html there are some usefull info too, but I culdn't understand a bit of this, even with google translate. Does anyone knows what is said in that post?
I think I've got both of this files. BI1 and BI2 here - cubby.com/pl/Android/_1f03da99a7034dd6b5ed7cb27bcc0bb0 But I may be wrong. As mentioned in the article in the first link the first part of bootloader can not be re-written. But I've tried and both parts flashed successfully. So either I've found not the bootloader files either info in the article is wrong. How can I find out are these correct bootloader files or not?
It seems that I found wrong files. Correct files seems to be - mmcblk0boot0.img and mmcblk0boot1.img. Here - cubby.com/pl/Android/_1f03da99a7034dd6b5ed7cb27bcc0bb0
You can try this
From China:
http://bbs.xda.cn/thread-11674785-1-1.html
From xda
http://forum.xda-developers.com/showthread.php?t=2334554
Works with F03D
I have a Fujitsu F03 D , this recovery can works with it ?
Thanks , bye :fingers-crossed:
F02-E Data Recovery
Hello everybody, I don't know if I am on the right topic, but I think people here can answer because it's about the Fujitsu F02-E.
I have this phone since more than 4 years and I was plenty satisfied with this item but since yesterday, the phone don't want to work anymore...
At first, it was starting until the screen "ARROWS" and then restart again and again.
Today, the phone is trying to start by two times himself when I put the battery in it...(Orange led; green led; orange led, green led, and at last orange led twinkle two times..then, all is switch off)
When I try to charging, it try to restart like I was explaining and then all is switch off, even the orange led that tells you it is charging...
But when charging it try to restart every 5 minutes..
Now, the screen switch on very rarely and not even for one second.
The very important question is:
Do You know a trick or an application that can recovery all data, because there are A LOT of important things Inside. I have found a few data recover but they are not compatible with the F02-E.
I would be very, very grateful if You can help me, please.
ps: Sorry for my English, I'm French
Have a good day.
Thank You.
Disclaimer:
Code:
Your warranty is now void.
Flashing this recovery assumes you have a sufficient technical understanding
of your device. Before continuing, you should be aware of the risks involved
and have an idea of what to do if something goes wrong. I am not responsible
for any bricked or otherwise malfunctioning devices.
A while back, bekriebel posted a working CWM image for Glass. Since then, there have been significant firmware changes for Glass that rendered the old recovery image unusable. A lot of people have been asking for an update, so I decided to compile an updated version.
This image is based on the latest stable CM11 sources, and uses the XE18.1 (XRV70D) kernel source found at http://github.com/justindriggers/android_kernel_Google_glass_1 and the device tree at http://github.com/justindriggers/android_device_Google_glass_1
Installation Instructions:
Download the recovery image here (md5sum: 1c0299145ec08efc5a7ec0f87ab7ef24)
Boot into fastboot mode:
Code:
adb reboot bootloader
Flash the image:
Code:
fastboot flash recovery recovery-clockworkmod-20140613-UNOFFICIAL-glass_1.img
Reboot your device:
Code:
fastboot reboot
Finally, you can boot into recovery:
Code:
adb reboot recovery
Usage:
Change the selection with the camera button. Select the current item with the power button.
Let me know if you have any issues, and enjoy.
What are the changes made? Does it add anything new that Glass couldn't do before, does it re-add non-glass input (OTG USB - Bluetooth input)?
Basically, what are the advantages of using this?
ResleyZ said:
What are the changes made? Does it add anything new that Glass couldn't do before, does it re-add non-glass input (OTG USB - Bluetooth input)?
Basically, what are the advantages of using this?
Click to expand...
Click to collapse
This is just the recovery, completely separate from everything inside the Glass operating system. I've personally used it to install Superuser and Xposed onto my device, but it opens the door to many other opportunities. If Google ever decides to make Glass open-source, then we may see some custom roms, which would be flashed using this recovery.
A publicly available recovery image is the first step toward further customization. If you have no need for it at the moment (you aren't a developer), then I wouldn't recommend flashing it.
I know this is old but it does work and even on XE24. I just did a full backup. Took awhile to find where it was stored but found it and pulled it to the computer with adb pull command. Found at:
/mnt/shell/emulated/clockworkmod/backup/ where there were a total of 10 files from the backup.
Just wish I would have had this before losing my working XE23 which at least could still send texts, make calls and a few other things.
ADB seems to have quit working. I had AOSP 5.1.1 on it but things got too slow and decided to put XE24 back on so got that done with fastboot but have not been able to get ADB to work at all. Any ideas?
I flashed to rooted bootloader after adb quit working but no change. Tried flashing the clockworkmod recovery again but still no adb.
Hey guys, I am new to the forum and this is my first time posting, yesterday I made a stupid mistake of flashing my Xiaomi 6 MIUI to Lineage OS, I didn't do it correctly and it resulted a bootloop, I managed to flash back the stock rom via fastboot, it did boot up into MIUI, but I cannot connect to network as nothing is shown there and it just stucks in updating...
I also have TWRP but somehow Xiaomi recovery had taken over and I have no idea how to enter TWRP, (tried volume up + PWR, both volume + PWR, volume down + PWR which just gives me fastboot, Volume up plus + home...) is there anyway for me to get to TWRP and maybe I can try to flash Lineage?
Or how can I flash back to the stock rom via fastboot/TWRP, thank you for your help~!
Flash twrp from fastboot, make a fastboot format userdata and from twrp wipe all and then flash firmware, rom of your choice, gapps if you want and the others. Then reboot.
ccelik97 said:
Flash twrp from fastboot, make a fastboot format userdata and from twrp wipe all and then flash firmware, rom of your choice, gapps if you want and the others. Then reboot.
Click to expand...
Click to collapse
hey there, thank you so much for your reply!!!
Stupidly I made a terrible mistake of relocking from the miflash tool and nope it doesn't work... Now will TWRP flash if my phone is locked???
And could you please tell me the instructions as I am a complete noob, thank you once again!
CaptainBilly said:
hey there, thank you so much for your reply!!!
Stupidly I made a terrible mistake of relocking from the miflash tool and nope it doesn't work... Now will TWRP flash if my phone is locked???
And could you please tell me the instructions as I am a complete noob, thank you once again!
Click to expand...
Click to collapse
No you can't do anything with a locked bootloader. But since you have permission to unlock your bootloader with xiaomi's tool then unlock it again. (To be honest I've first unlocked at octover and haven't locked it again so I don't know if you'd have to wait for another 3 days. But after getting it unlocked it'd be okay, you'll be able to use fastboot so no worries)
ccelik97 said:
No you can't do anything with a locked bootloader. But since you have permission to unlock your bootloader with xiaomi's tool then unlock it again. (To be honest I've first unlocked at octover and haven't locked it again so I don't know if you'd have to wait for another 3 days. But after getting it unlocked it'd be okay, you'll be able to use fastboot so no worries)
Click to expand...
Click to collapse
Okay then! Thank you! I just unlocked it! But now I have no idea how to reflash TWRP, could u please help?
I have the minimal ADB and fastboot installed, but currently when I type fastboot flash recovery recovery.img, both powershell/cmd says cannot load recovery.img...
CaptainBilly said:
Okay then! Thank you! I just unlocked it! But now I have no idea how to reflash TWRP, could u please help?
I have the minimal ADB and fastboot installed, but currently when I type fastboot flash recovery recovery.img, both powershell/cmd says cannot load recovery.img...
Click to expand...
Click to collapse
Do you have a file called recovery.img at the same directory with the fastboot binary file? If no either rename it or write the recovery img 's actual name in terminal after fastboot flash recovery.
ccelik97 said:
Do you have a file called recovery.img at the same directory with the fastboot binary file? If no either rename it or write the recovery img 's actual name in terminal after fastboot flash recovery.
Click to expand...
Click to collapse
I am not sure what fastboot binary file is...sorry, but I think what you meant is having TWRP file at the same location as the Minimal ADB and Fastboot program? If so yes I do, I did save the TWRP as the same location AND I did renamed it recovery.img, should I use MIUI Recovery Tool to install TWRP for me?
Thanks once again! Really appreciated.
CaptainBilly said:
I am not sure what fastboot binary file is...sorry, but I think what you meant is having TWRP file at the same location as the Minimal ADB and Fastboot program? If so yes I do, I did save the TWRP as the same location AND I did renamed it recovery.img, should I use MIUI Recovery Tool to install TWRP for me?
Thanks once again! Really appreciated.
Click to expand...
Click to collapse
Check the file name correctly. Windows doesn't show every extension name so maybe the file you see as "recovery.img" is actually "recovery.img.img". Enable to show all extensions from explorer settings (search for it in Google because I forget it too even though I'm doing it on all windows pcs I use
And for what that so called "fastboot binary file" is just that "fastboot" file in adb and fastboot folder. It's a binary type file and that's why I'm referring to it as a binary file (it has executable codes in it). And the difference from a text file is while a text file has a structure like "file start"+"the actual text in it"+"file end", a binary file has executable codes in it so you execute it (like typing "fastboot flash recovery twrp.img ; it means you're running fastboot to execute it's flash function to recovery partition of your device, and the file you want to use as the input is twrp.img in this example. It's good to learn.)
ccelik97 said:
Check the file name correctly. Windows doesn't show every extension name so maybe the file you see as "recovery.img" is actually "recovery.img.img". Enable to show all extensions from explorer settings (search for it in Google because I forget it too even though I'm doing it on all windows pcs I use
And for what that so called "fastboot binary file" is just that "fastboot" file in adb and fastboot folder. It's a binary type file and that's why I'm referring to it as a binary file (it has executable codes in it). And the difference from a text file is while a text file has a structure like "file start"+"the actual text in it"+"file end", a binary file has executable codes in it so you execute it (like typing "fastboot flash recovery twrp.img ; it means you're running fastboot to execute it's flash function to recovery partition of your device, and the file you want to use as the input is twrp.img in this example. It's good to learn.)
Click to expand...
Click to collapse
Thank you SO MUCH!!! your the best!!! Now I installed TWRP!!!
what should we do next? wipe portion? what does that mean? thanks!
CaptainBilly said:
Thank you SO MUCH!!! your the best!!! Now I installed TWRP!!!
what should we do next? wipe portion? what does that mean? thanks!
Click to expand...
Click to collapse
Not portion, but partition. Partitions are simply the different parts on a storage. For example when you open a file explorer on your device you see your sdcard folder which is in data partition. System files are in system partition, kernel is in boot partition etc.
And yes simply in twrp under wipe select advanced wipe and select all of them, wipe. After that from the same screen select format data, type yes to confirm and reboot to recovery again.
Then while in twrp copy files you want to flash to your device (or use an usb flash drive with otg, which I prefer but for this don't forget to tick usb otg in mount section in twrp)
Personally I flash firnware, rom, gapps and reboot, configure my account settings and auto download apps etc. Then when finished go back to recovery and flash magisk (flash magisk after booting into the system at least for once or most likely you won't pass safetynet checks) for root and the other things (e.g. font).
ccelik97 said:
Not portion, but partition. Partitions are simply the different parts on a storage. For example when you open a file explorer on your device you see your sdcard folder which is in data partition. System files are in system partition, kernel is in boot partition etc.
And yes simply in twrp under wipe select advanced wipe and select all of them, wipe. After that from the same screen select format data, type yes to confirm and reboot to recovery again.
Then while in twrp copy files you want to flash to your device (or use an usb flash drive with otg, which I prefer but for this don't forget to tick usb otg in mount section in twrp)
Personally I flash firnware, rom, gapps and reboot, configure my account settings and auto download apps etc. Then when finished go back to recovery and flash magisk (flash magisk after booting into the system at least for once or most likely you won't pass safetynet checks) for root and the other things (e.g. font).
Click to expand...
Click to collapse
oopsies sorry, I am very new to this and thanks for your really helpful explanation, I will wipe all now that includes dalvik,cache, system and data and internal storage, but what firmware should I flash and how do I know which one do I need? I am going for Linegae os btw.
Thanks once again, if without ur help my phone will essentially be dead :good:
ccelik97 said:
Not portion, but partition. Partitions are simply the different parts on a storage. For example when you open a file explorer on your device you see your sdcard folder which is in data partition. System files are in system partition, kernel is in boot partition etc.
And yes simply in twrp under wipe select advanced wipe and select all of them, wipe. After that from the same screen select format data, type yes to confirm and reboot to recovery again.
Then while in twrp copy files you want to flash to your device (or use an usb flash drive with otg, which I prefer but for this don't forget to tick usb otg in mount section in twrp)
Personally I flash firnware, rom, gapps and reboot, configure my account settings and auto download apps etc. Then when finished go back to recovery and flash magisk (flash magisk after booting into the system at least for once or most likely you won't pass safetynet checks) for root and the other things (e.g. font).
Click to expand...
Click to collapse
I will wipe all now! Thankyou! but one question how do I know which firmware I need to flash and what do you mean by going back and flash magisk?
I am planning to flash lineage os if possible! Thanks once again for your help! if its without you I would probably never have it functional again
CaptainBilly said:
I will wipe all now! Thankyou! but one question how do I know which firmware I need to flash and what do you mean by going back and flash magisk?
I am planning to flash lineage os if possible! Thanks once again for your help! if its without you I would probably never have it functional again
Click to expand...
Click to collapse
You're welcome but I'm pretty sure you'd figure it out yourself if you've wanted.
Which lineageos? And I suggest you to wait for the official los (next week I think) and try omnirom official for example. Officials are better for newcomers but try to not to spam the threads with the questions without doing some research first. You know I could just ignore your topic in the beginning and maybe nobody would answer it and you'd be on your own with all those comments on other threads without a proper preliminary knowledge.
ccelik97 said:
You're welcome but I'm pretty sure you'd figure it out yourself if you've wanted.
Which lineageos? And I suggest you to wait for the official los (next week I think) and try omnirom official for example. Officials are better for newcomers but try to not to spam the threads with the questions without doing some research first. You know I could just ignore your topic in the beginning and maybe nobody would answer it and you'd be on your own with all those comments on other threads without a proper preliminary knowledge.
Click to expand...
Click to collapse
Thank you!
I had successfully flashed Lineage OS 15.1, will be tweaking a bit and decide if I wanna go for another custom rom or flash back to MIUI
CaptainBilly said:
oopsies sorry, I am very new to this and thanks for your really helpful explanation, I will wipe all now that includes dalvik,cache, system and data and internal storage, but what firmware should I flash and how do I know which one do I need? I am going for Linegae os btw.
Thanks once again, if without ur help my phone will essentially be dead :good:
Click to expand...
Click to collapse
you can flash lineageos or MIUI by TWRP,just simply flow the wipe,then flash miui or lineageos ,but if you flash miui,you might go back to mi official recovery instead of TWRP(poor English).
laijirong said:
you can flash lineageos or MIUI by TWRP,just simply flow the wipe,then flash miui or lineageos ,but if you flash miui,you might go back to mi official recovery instead of TWRP(poor English).
Click to expand...
Click to collapse
How do you even get the phone to be recognised to initiate the flash if its stuck in constant boot loop??
Normally your laptop or pc needs to recognise the phone before it can start the flash right?
Shanrom said:
How do you even get the phone to be recognised to initiate the flash if its stuck in constant boot loop??
Normally your laptop or pc needs to recognise the phone before it can start the flash right?
Click to expand...
Click to collapse
vol + and power ,if not you might have it repaired.
Poor English.