Related
Hi,
I have compiled a note 3 kernel and packaged up a boot.img. I would like to flash via CWM Recovery with a zip file. How do I take the boot.img that was generated and place it within a zip for flashing? Is there some signing that needs to take place? I've noticed a META-INF directory in some kernel binaries that I've downloaded and checked.
Thanks for any help!
solved
xrebecca_kelly1993x said:
Hi,
I have compiled a note 3 kernel and packaged up a boot.img. I would like to flash via CWM Recovery with a zip file. How do I take the boot.img that was generated and place it within a zip for flashing? Is there some signing that needs to take place? I've noticed a META-INF directory in some kernel binaries that I've downloaded and checked.
Thanks for any help!
Click to expand...
Click to collapse
I'm not quite sure yet on how to zip the newly packaged boot.img into a zip for flashing with CWM, but I did figure out how to flash regardless. CWM simply does this too.
adb push boot_repacked.img /sdcard/
adb shell su -c "dd if=/sdcard/boot_repacked.img of=/dev/block/platform/dw_mmc.0/by-name/BOOT"
TWRP 2.8.7.0 custom recovery
thanx to user @Unjustified Dev we have TWRP custom recovery for our phone.
download HERE
So anyone who download the TWRP should send him a dollar for beer or at least thank him!
Of course you do everything on your own!
To test before installation (linux users need sudo before fastboot):
Code:
fastboot -i 0x1bbb boot twrp-2.8.7.0-idol3.img
To install (linux users need sudo before fastboot):
Code:
fastboot -i 0x1bbb flash recovery twrp-2.8.7.0-idol3.img
!BEFORE YOU START, PLEASE READ THIS!
And don´t forget to thank Famewolf for the tutorial, because this could save your phone when something go bad!
Thanks, tried it. It worked.
I also just installed SU directly, bypassing the previous root thread.
1. Download the .zip package from here: https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
2. Put it on the root of my SD card.
3. In TWRP click install and find the .zip.
Wonderful. Just a question: is this recovery for Idol 3 4.7 (6039) or 5.5 (6045) ?
Gynoid said:
Wonderful. Just a question: is this recovery for Idol 3 4.7 (6039) or 5.5 (6045) ?
Click to expand...
Click to collapse
It's for 6045. For 4.7 TWRP, see this post: http://forum.xda-developers.com/showpost.php?p=61976520&postcount=18
Thanks!
is it functional for backing up our system in TWRP?
@DallasCZ could you please provide the original link to TWRP. That was a bit unfair to upload it elsewhere as I tend to track the number of downloads.
Sent from my LGMS395 using Tapatalk
gecko702 said:
is it functional for backing up our system in TWRP?
Click to expand...
Click to collapse
Yes although to my knowledge noone has actually done a restore yet. He's fixing some minor bugs and will be releasing a new version at some point.
famewolf said:
Yes although to my knowledge noone has actually done a restore yet. He's fixing some minor bugs and will be releasing a new version at some point.
Click to expand...
Click to collapse
i am in touch with the dev and allready downloading the new build..will be soon on my google drive
Unjustified Dev said:
@DallasCZ could you please provide the original link to TWRP. That was a bit unfair to upload it elsewhere as I tend to track the number of downloads.
Sent from my LGMS395 using Tapatalk
Click to expand...
Click to collapse
sorry, i corrected the link...
Convert TWRP Backup into flashable rom zip
I found these instructions that explain how to take a TWRP backup and turn it into a flashable zip file. This would allow someone to create a "factory" rom pre-rooted to be flashed.
For TWRP Backup
Transfer the TWRP backup from Phone to PC.
You’ll see a file named system.ext4.win which is the System partition backup of your device. Rename it to system.ext4.tar (Changing its extension from .win to .tar)
Extract the system.ext4.tar using an archive software like Winrar or 7zip.
If your TWRP backup is not in compression mode, you will directly get the system folder, else you will get a file named system.ext4, which should be renamed again to system.ext4.tar and extract it to get the system folder.
Take the boot.emmc.win file and rename it to boot.img.
Now collect a META-INF folder from any custom ROM which is made for your device. Make sure you get the correct Meta-Inf folder, else the Zip won’t work and might worsen the condition of your device.
Select the META-INF, System folders and the boot.img and right click your mouse and select add to Archive.
In the Archive settings, choose the extension of the compressed file as Zip (Make sure of this part)
Now you can use this Zip file to flash it on your Custom recovery.
we dont have the meta-inf folder...there is one in the update i got, but i dont know if this id the right one.
and we dont have custom rom to get meta-inf from.
also the main thing is, that i cannot unpack the system win file when renamed to .tar i dunno why (i got latest 7-zip app).
DallasCZ said:
we dont have the meta-inf folder...there is one in the update i got, but i dont know if this id the right one.
and we dont have custom rom to get meta-inf from.
also the main thing is, that i cannot unpack the system win file when renamed to .tar i dunno why (i got latest 7-zip app).
Click to expand...
Click to collapse
What they primarily want is the "update-binary" which is device specific. I don't remember if the update had one....I did take apart an update-supersu.zip and it uses a script as it's update binary...thought about trying to convert that. Theoretically you could take a meta-inf for another device's rom...and use it's meta-inf making sure to replace the update-binary. It also has an installer script that tells it to mount system and data....extract files from the zip and where to put them. I learned a bit when I was trying to make an update.zip to fix my build.prop.
It untar'd fine for me on my linux pc:
[email protected]:/workarea/android/idol3/TWRP/BACKUPS/408adcbe/1970-01-01--22-28-53_LRX22G_release-keys/work > tar -xvf ../system.ext4.win000
tar: Removing leading `/' from member names
/system/app/
/system/app/AntHalService/
/system/app/AntHalService/AntHalService.apk
/system/app/AntHalService/arm64/
/system/app/AntHalService/arm64/AntHalService.odex
/system/app/BasicDreams/
/system/app/BasicDreams/BasicDreams.apk
/system/app/BasicDreams/arm64/
/system/app/BasicDreams/arm64/BasicDreams.odex
/system/app/Bluetooth/
/system/app/Bluetooth/Bluetooth.apk
/system/app/Bluetooth/arm/
/system/app/Bluetooth/arm/Bluetooth.odex
famewolf said:
What they primarily want is the "update-binary" which is device specific. I don't remember if the update had one....I did take apart an update-supersu.zip and it uses a script as it's update binary...thought about trying to convert that. Theoretically you could take a meta-inf for another device's rom...and use it's meta-inf making sure to replace the update-binary. It also has an installer script that tells it to mount system and data....extract files from the zip and where to put them. I learned a bit when I was trying to make an update.zip to fix my build.prop.
It untar'd fine for me on my linux pc:
[email protected]:/workarea/android/idol3/TWRP/BACKUPS/408adcbe/1970-01-01--22-28-53_LRX22G_release-keys/work > tar -xvf ../system.ext4.win000
tar: Removing leading `/' from member names
/system/app/
/system/app/AntHalService/
/system/app/AntHalService/AntHalService.apk
/system/app/AntHalService/arm64/
/system/app/AntHalService/arm64/AntHalService.odex
/system/app/BasicDreams/
/system/app/BasicDreams/BasicDreams.apk
/system/app/BasicDreams/arm64/
/system/app/BasicDreams/arm64/BasicDreams.odex
/system/app/Bluetooth/
/system/app/Bluetooth/Bluetooth.apk
/system/app/Bluetooth/arm/
/system/app/Bluetooth/arm/Bluetooth.odex
Click to expand...
Click to collapse
i allready build some roms for my older device, so i know what it is about.
For the proper rom zip you have to make the updater script with all the simlinks and metadata ...in the latest update there were no simlinks in the updater script...
without them you can brick your phone.
for example simlinks from 4.4.2 Os from zte V5
Code:
symlink("/data/misc/audio/mbhc.bin", "/system/etc/firmware/wcd9306/wcd9306_mbhc.bin");
symlink("/data/misc/audio/wcd9320_anc.bin", "/system/etc/firmware/wcd9306/wcd9306_anc.bin");
symlink("/persist/WCNSS_qcom_cfg.ini", "/system/etc/firmware/wlan/prima/WCNSS_qcom_cfg.ini");
symlink("/persist/WCNSS_qcom_wlan_nv.bin", "/system/etc/firmware/wlan/prima/WCNSS_qcom_wlan_nv.bin");
symlink("/system/lib/modules/pronto/pronto_wlan.ko", "/system/lib/modules/wlan.ko");
symlink("Roboto-Bold.ttf", "/system/fonts/DroidSans-Bold.ttf");
symlink("Roboto-Regular.ttf", "/system/fonts/DroidSans.ttf");
symlink("libGLESv2.so", "/system/lib/libGLESv3.so");
symlink("mksh", "/system/bin/sh");
this you cannot copy from another device....
Never mind. I installed the second build.
How do I boot into the custom recovery? Is it power up + power button on the Idol 3?
Acreo Aeneas said:
Never mind. I installed the second build.
How do I boot into the custom recovery? Is it power up + power button on the Idol 3?
Click to expand...
Click to collapse
Reboot or power on till you see the alcatel screen pop up....right away hold down up arrow and it should go into recovery.
Thank you so much...been waiting for this....
so now let ROM's start pouring in )))))))
Hmm odd. I had to reflash it. For some reason it didn't take the first time I flashed the second build TWRP to my Idol 3.
What partitions should I backup using TWRP? I'd assume: Boot, System, and Data? Should I include System Image too?
Acreo Aeneas said:
Hmm odd. I had to reflash it. For some reason it didn't take the first time I flash the second build TWRP to my Idol 3.
What partitions should I backup using TWRP? I'd assume: Boot, System, and Data? Should I include System Image too?
Click to expand...
Click to collapse
The default of boot, system and data should be fine for personal use however if you have not yet rooted please read here first! http://forum.xda-developers.com/idol-3/help/want-to-able-to-install-ota-updates-t3163745
So Awesome! best looking twrp Ive seen yet xD. Also, works well too. I havent tested backing up data, but I did a successful restore of the system and boot So far so good!
2015/10/07 The information below will be kept to help folks make backups and for linux/mac users to have some images to restore but if you have bricked your phone the recommended solution now is to install Alcatel's Mobile Q software version 4.9.2 or newer and use it to restore your phone to factory condition. Basically turn off the phone..plug it up to the pc via usb and run the software...it should prompt you from there. The link to download the software is here: http://alcatelonetouch.com/global-en/support/download/pixi_3_7_4g.html
*****Warning***** Recent updates from Alcatel have REMOVED the fastboot commands that allow root and custom recovery for some models of the 6039. Before updating read the details here: http://forum.xda-developers.com/showthread.php?t=3173598 and make sure the new update doesn't do the same!
You should also be aware that if your phone hangs on boot and you are rooted don't do a factory reset or you will lose adb access if you had it enabled which can be used to restore your phone
Table of Contents
Post #1: Intro
Post #2: Backup Instructions http://forum.xda-developers.com/showpost.php?p=62006344&postcount=2
Post #3: System Images http://forum.xda-developers.com/showpost.php?p=62006344&postcount=3
Post #4: Restore Instructions and firmware issues http://forum.xda-developers.com/showpost.php?p=62006344&postcount=4
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Folks, OTA updates for Lollipop check if your system has ever been mounted read/write (which is required to root) and if it has they do not allow the update to install. What that means is before you root you need to first go into fastboot and do a fastboot boot of TWRP (this boots twrp on your phone without installing it) then go into twrp and backup your system directory so you always have something to restore to if you want future OTA updates.
The bad news is that for folks who have already rooted, we need TWRP backups of the system partition for each model of the idol 3 BEFORE someone has rooted. 6045i, 6045k, 6045y...are there more?
If you have NOT yet rooted your phone and are willing to help out please post here with your model number(It shows in settings, about phone as Model Number). I'll add some instructions on how to take a backup then the backup needs to be uploaded online somewhere we can access it. The system partition is normally read only so it contains NONE of your personal information.
This paragraph from the TWRP documentation is taken from: https://twrp.me/site/update/2015/06/22/twrp-2.8.7.0-released.html
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.]
Here's an article that explains it better than I can: https://www.androidpit.com/android-5-0-lollipop-ota-update-fail
20150810 - Turns out all thats required to get updates at least for now is doing a FULL unroot. (That may not be the case with a major jump such as from 5.0.2 to 5.1.1) Failure to do a full unroot can result in boot loops after applying updates that currently DO NOT HAVE A SOLUTION because the default recovery for the 6045i and 6045Y do not have the reboot to bootloader option that IS present in the 6045K and all models of the 6039 Idol 3. Thanks Alcatel! An easier solution is to flash an already upgraded firmware if it is available. Canadian users have also found it useful to flash USA firmware (both have a 6045i) to get updates sooner than being released by the cell providers in canada.
Instructions to backup your system prior to rooting.
-Get/install Alcatel USB driver if Windows. (no need for Mac). FROM HERE: http://54.247.87.13/softwareupgrade/Driver/ALCATEL_ADB_ Driver Qualcomm_ADB.rar , or just connect your idol3 to the computer and from the phone select "cd rom" drive..it will install the drivers automatically
Windows and Mac users should have downloaded the android sdk to get adb and fastboot. [ https://developer.android.com/sdk/ ] Linux (ubuntu based) users should install packages android-tools-adb and android-tools-fastboot Windows users can try a minimal adb and fastboot install using the instructions here: http://forum.xda-developers.com/showthread.php?t=2317790 or here: http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
download twrp from here: https://www.androidfilehost.com/?fid=24052804347778862
-Set USB debugging on in Developer settings (if these are not exposed, go to Settings/About Phone/Build number, and tap 7 times.)
-Plug in USB cable to phone and computer. Tap on USB icon in notifications panel; select MTP (file transfer) mode or PTP also works fine.
-ON your pc open command prompt in the directory where you have placed twrp-2.8.7.0-idol3.img (when using windows in the directory hold shift and press the right button on the mouse, it will pop-up a window where you have to select "open command prompt here" and type "adb reboot-bootloader" to reboot into bootloader
-Then type "fastboot -i 0x1bbb devices" This should show the device
-Type "fastboot -i 0x1bbb boot twrp-2.8.7.0-idol3.img" This will boot twrp on your phone without installing it.
-On your phone do a normal backup but make sure only "system image" (not system) and Boot (to keep the kernel in sync with the system) is checkmarked to be backed up. You can go into TWRP settings and have it write to the external_sd vs using internal "sdcard" before starting the backup if you have one installed
-After backup has completed it will have created a folder named TWRP on your /sdcard or /storage/sdcard1 depending on which you selected (/sdcard by default). Assuming this is your first use of twrp then copy the whole twrp folder over to your pc and zip or rar it then post a message with your model stating you have a backup and we'll work to get it uploaded. If you have previously used twrp and have multiple backups then just go one directory in "/sdcard/TWRP/" and backup only the directory with the date timestamp of your most recent backup.
When uploading to the cloud zip'ing or rar'ing the file will cut it's size by about half. (it's 3gb initially and roughly 900mb afterward) It's still a rather large file so you might look at http://www.filedropper.com/ to upload the file...they claim files allowed up to 5gb and no registration required. https://mega.co.nz is also a good alternative but can be slow. If you have suggestions for a better place to put the files please let me know.
If you are willing to contribute space that will not expire to host the system backups please contact me via pm. Make sure to hit thanks for our generous uploaders.
System Downloads Available [Each download is +- 1GB in size]
(Do not crossflash devices ie flash the 6045i image to a 6045K or 6045Y. We don't know what the results will be!):
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
6045 (5.5 inch model)
From most recent back to "out of the box".
Model: 60450(USA-Cricket) Firmware: 5.0.2-010 03 Link: https://mega.nz/#!xhhy0AKC!hWhDgXCQOGt0cNHcfkkejEEBiP1pjOT5-ZK6mAY5MUU Thanks to squeakychu for the upload!
Model: 6045i(usa) Firmware: 5.0.2.7SRA-UEA2 Link: https://mega.nz/#!dRkgxA5L!z7yVmmgeUWBpAGwJW6ixnGhGBzUky1dfhKksu3yGPKg Thanks to Brian117 for the uploads! (09/28/2015)
Model: 6045i(usa) Firmware: 5.0.2.7SR4-UE40 Link: https://mega.co.nz/#!K9szRIKR!ZdjIiH2Ol0ZCNe2VTSl6cbRyQeZFtafG3Y9CM0ecCkg 20150810 md5sum: 56376824f7c10d8debaec6c3a7100e50
Model: 6045i(usa) Firmware: 5.0.2-7SQR-UER0 Link: https://mega.co.nz/#!FB0DQAhQ!rQ4H39hQR2tDhfniEej-RvsSe5OqWY42_xCsjY08o4k Thanks to buggleston for the upload!
Model: 6045i(usa) Firmware: 5.0.2-7SQ3-UE30 Link: https://mega.co.nz/#!focwnJJL!VQW3Omi3TF4iJzIyNLu73P9gb8i_WKA_fu7ZWUiIsN0 Thanks to Electriccars for the upload!
Model: 6045i(usa) Firmware: 5.0.2.7SMA-UEA1 Link: https://mega.nz/#!pdlWhQLR!D2-mEnxp2SnxH0QBDsSSZ-YrDooJC8BdKronYxziF_A Thanks to lordlittlebrooks for the upload!
Model: 6045i(canada) Firmware: 5.0.2-7SQB-UCB0 Link: https://mega.nz/#!opolxbIY!A9dEfORplfhkmuNwobKsEF2wX6yY3oLq8M9dgWpDNq8 Thanks to KryPTiCk0d3 for the upload!
Model: 6045i(canada) Firmware: 5.0.2-7SQ9-UV93 Link: http://drive.google.com/file/d/0B8Gqss1TYorTaXZrRFdBdDJ2Vnc/view Thanks to green3water5 for the upload!
Model: 6045K(Serbia, Bulgaria, Macedonia and maybe Cz) Firmware: 5.0.2-010 0101001 Link: https://mega.nz/#!L5El0QqA!IrxnA4qyXONyWehaJltc7JsE5TgaAXIdT9RQ73K0Rdw Thanks to bokaco7 and Nikola Jovanovic for the upload!
Model: 6045Y(Europe) Firmware: 5.0.2-010 06 Link: https://mega.nz/#!N9phSbTR!hH0bTJnHcUrwKxdpA-RKyecHNPKls7Cy0fi-Ih3BWkM Thanks to Gynoid for the upload!
Model: 6045Y(Europe) Firmware: 5.0.2-010 05 Link: https://mega.nz/#!pxgwXKIA!TInG7xK9Z-qObX1Cc3BObGp88zx0FCpWI3RDt_wdD0Q and https://mega.nz/#!l5xnSDrL!-y2ye27vODfNAR2qcBAQN7q0gGYA579iRzla07lFkd4 [You will need to flash both as one has the system backup and the other has the boot] Thanks to Gynoid for the upload!
Model: 6045Y(Europe) Firmware: 5.0.2-010 03 Link: http://mega.co.nz/#!CYk2mBCa!XJd1nJI1cUcTcGjwzhApcAyABQ8y54D-bATvgxxHMsE Thanks to zrkkrz for uploading this 2 times!
Model: 6045Y(Europe) Firmware: 5.0.2-010 01 Link: http://data.nettitoimisto.com/f/e308c56574/ Thanks to tommihut for the upload!
Other models not listed? NEEDED!
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
All backups will eventually be mirrored to MEGA. If the file is missing I'm more than likely still trying to get it uploaded. MEGA can be slow however the files should never expire. The folder is here: https://mega.co.nz/#F!DgNhkDKR!GyJsku7nw4F6nLiT4XFRKA
If an individual download link is dead please let me know via post or pm.
Thanks to kirplunk and zrkkrz for uploading backups that ended up having to be replaced due to incorrect instructions to backup system instead of "system image" from within TWRP.
When using these backups.....
There is currently a bug in TWRP that appears to be showing 6045Y for ALL idol3 devices in the recovery.log so make SURE the system image you are flashing is meant for your device to the best of your ability.
Restoring a TWRP backup image:
If you wish to update to a newer firmware or restore an older one you can follow purple.epod's basic instructions here but use the firmware you want to restore: http://forum.xda-developers.com/showpost.php?p=62313284&postcount=1 Also make sure you restore both boot AND system image in the newer firmware's when selecting what to restore.
When restoring the UE40 firmware the first time you go into system update checker you need to delete the existing UE40 update as it kept it around...you should then be able to check updates as normal.
This was brought up in the main rooting thread, but you might also be able to unroot via SuperSU with the Full Unroot option. Haven't tried it yet but if it works, you can just unroot, install whatever OTA there may be, and re-root.
brian117 said:
This was brought up in the main rooting thread, but you might also be able to unroot via SuperSU with the Full Unroot option. Haven't tried it yet but if it works, you can just unroot, install whatever OTA there may be, and re-root.
Click to expand...
Click to collapse
Yeah, I'm the one who brought it up. I thought those about to root should be made aware.
Based on the twrp documentation it sounds like once it's been mounted once as read/write there is a way for them to check and it will kill the ota update. unrooting isn't going to fix that. We also have no good way to intercept the updates so we could alter them to install anyway. I used a squid transparent proxy to find the download url but won't do me any good if my phone can't download the update. If it lets the phone dwonload and then when it runs aborts I may still be able to grab the url and the update could be modified to apply anyway.
tried to upload stock system backup for 6045i
famewolf said:
Reserved 1
Click to expand...
Click to collapse
i have backed up the stock system twrp backup for 6045i zipped in folder then tried your file link to up load, after about 15 minutes it was still uploading seemed to long so i stopped the upload. do you or dallascz have another place to upload or email maybe? i still have not installed the recovery or rooted yet, trying to give back to Idol3ers.
---------- Post added at 01:51 AM ---------- Previous post was at 01:34 AM ----------
famewolf said:
Folks, OTA updates for Lollipop check if your system has ever been mounted read/write (which is required to root) and if it has they do not allow the update to install. What that means is before you root you need to first go into fastboot and do a fastboot boot of TWRP (this boots twrp on your phone without installing it) then go into twrp and backup your system directory so you always have something to restore to if you want future OTA updates.
The bad news is that for folks who have already rooted, we need TWRP backups of the system partition for each model of the idol 3 BEFORE someone has rooted. 6045i, 6045k, 6045y...are there more?
If you have NOT yet rooted your phone and are willing to help out please post here with your model number(It shows in settings, about phone as Model Number). I'll add some instructions on how to take a backup then the backup needs to be uploaded online somewhere we can access it. The system partition is normally read only so it contains NONE of your personal information.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.]
Click to expand...
Click to collapse
i have backed up the stock system twrp backup for 6045i zipped in folder then tried your file link to up load, after about 15 minutes it was still uploading seemed to long so i stopped the upload. do you or dallascz have another place to upload or email maybe? i still have not installed the recovery or rooted yet, trying to give back to Idol3ers.
kirplunk said:
i have backed up the stock system twrp backup for 6045i zipped in folder then tried your file link to up load, after about 15 minutes it was still uploading seemed to long so i stopped the upload. do you or dallascz have another place to upload or email maybe? i still have not installed the recovery or rooted yet, trying to give back to Idol3ers.
---------- Post added at 01:51 AM ---------- Previous post was at 01:34 AM ----------
i have backed up the stock system twrp backup for 6045i zipped in folder then tried your file link to up load, after about 15 minutes it was still uploading seemed to long so i stopped the upload. do you or dallascz have another place to upload or email maybe? i still have not installed the recovery or rooted yet, trying to give back to Idol3ers.
Click to expand...
Click to collapse
kirplunk, how large is the file after you have zipped it? I'll check into some more services. I'm limited by the fact I don't have hi speed and I don't think xda rules allow me to mention any file sharing service that requires registration. If you do a google of "upload large file" and find a service that works for you let me know. If others have a suggestion also let me know. I'm reply back as soon as I find some other sites. Thanks for your assistance!
*update* In other areas of XDA they suggest https://mega.co.nz/ for large file uploads however it would require creating your own account. They give you 50GB. Let me know if this works for you please.
size reply
famewolf said:
kirplunk, how large is the file after you have zipped it? I'll check into some more services. I'm limited by the fact I don't have hi speed and I don't think xda rules allow me to mention any file sharing service that requires registration. If you do a google of "upload large file" and find a service that works for you let me know. If others have a suggestion also let me know. I'm reply back as soon as I find some other sites. Thanks for your assistance!
Click to expand...
Click to collapse
the unzipped folder with files was 2.1gb in size, the zipped folder with files that i tried to upload is 855mb in size. i do not use the cloud at all so i don't have a drop box or any thing of the type. the site you referenced said it was uploading but it seemed 15 minutes was more than enough time for that size of file. my browser kept saying it was uploading and connecting to site.
kirplunk said:
the unzipped folder with files was 2.1gb in size, the zipped folder with files that i tried to upload is 855mb in size. i do not use the cloud at all so i don't have a drop box or any thing of the type. the site you referenced said it was uploading but it seemed 15 minutes was more than enough time for that size of file. my browser kept saying it was uploading and connecting to site.
Click to expand...
Click to collapse
Can you please try https://mega.co.nz/ and see if it works better for you? It will require creating an account but they will give you 50GB and you could use a disposable email address if you prefer. I'm checking other areas of xda to see how they handle large file uploads and this is what I've seen so far.
I have no problem sharing one I've created but there will always be that one person who wants to come along and delete everything in it.
Another is http://www.filedropper.com/ which allows up to 5gb files and keeps them till 30 days of not being downloaded. No registration required.
Also is your backup after the two system updates? Just FYI your upload bandwidth is not going to be as high as your download typically so uploads of large files can take a while.
attempting the second site now, called file dropper.
the file folder i'm uploading is called, 6045i twrp stock system backup.7z
upload is at 10% right now
now at 20%, yes with updates firmware is 5.0.2-7sqr-uero
30% my upload speed should put this file up in 3 minutes but their server is taking it like sucking coffee up through a stir stick, slow
will update when it reaches 100%, but as a junior member i can not post links so you will have to find it at the file dropper.
100% uploaded,
as a junior member this is the best i can do for the link.
www dot filedropper dot com/6045itwrpstocksystembackup
hope this helps
Uploads tend to be much slower than downloads. LTE connections are an exception, but cable and DSL upstream speeds aren't fast.
kirplunk said:
the file folder i'm uploading is called, 6045i twrp stock system backup.7z
upload is at 10% right now
now at 20%, yes with updates firmware is 5.0.2-7sqr-uero
30% my upload speed should put this file up in 3 minutes but their server is taking it like sucking coffee up through a stir stick, slow
will update when it reaches 100%, but as a junior member i can not post links so you will have to find it at the file dropper.
Click to expand...
Click to collapse
Feel free to send me the link in a PM and I'll post it so others can download it in addition to me or I'm sure I can find it based on filename if they have search.
With your permission I'll put it in post #3 with your name and a thank you. I'll have to visit the local library that has rather fast internet to get these files downloaded and moved to one folder for everyone assuming others share theirs as well.
So using stock recovery to Wipe Data/Factory Reset back to new doesn't remove root or r/w status?
mk3 said:
So using stock recovery to Wipe Data/Factory Reset back to new doesn't remove root or r/w status?
Click to expand...
Click to collapse
A factory reset wipes the data and cache partitions. It does nothing to /system since it expects it to be read only.
famewolf said:
A factory reset wipes the data and cache partitions. It does nothing to /system since it expects it to be read only.
Click to expand...
Click to collapse
ahhh.... bummer. Thanks for the clarification.
So I used Hide My Root to hide su binary and the system update doesn't give me the error (like all is fine). Prior to hiding the su binary it throws the error about being rooted.
.
Is the /system partition different than the /system directory that's in the root of the device? If it's the same, we can change the read/write permissions with ES File Explorer if the device is rooted? I'm not sure if it'll offer us the chance, if we want it, to make all the contents of the dir have the same permissions we set for the dir itself. Can the same thing be done from a command line in TWRP?
Why does TWRP show "system" and "system image" as two different options and sizes to backup? I've never seen that before.
maigre said:
Is the /system partition different than the /system directory that's in the root of the device? If it's the same, we can change the read/write permissions with ES File Explorer if the device is rooted? I'm not sure if it'll offer us the chance, if we want it, to make all the contents of the dir have the same permissions we set for the dir itself. Can the same thing be done from a command line in TWRP?
Click to expand...
Click to collapse
The system partition is the same as the /system folder however it's not a file permission that's an issue and you'd never want to set all your files to the same permissions. Here is an article that explains it better than I can: https://www.androidpit.com/android-5-0-lollipop-ota-update-fail
kirplunk said:
the file folder i'm uploading is called, 6045i twrp stock system backup.7z
upload is at 10% right now
now at 20%, yes with updates firmware is 5.0.2-7sqr-uero
30% my upload speed should put this file up in 3 minutes but their server is taking it like sucking coffee up through a stir stick, slow
will update when it reaches 100%, but as a junior member i can not post links so you will have to find it at the file dropper.
100% uploaded,
as a junior member this is the best i can do for the link.
www dot filedropper dot com/6045itwrpstocksystembackup
hope this helps
Click to expand...
Click to collapse
Thanks kirplunk! I've got it downloading and will add my folder as a mirror to try to prevent the file from expiring.
Hello,
Please and thanks in advance for any assistance!
I've successfully rooted my HD8 7th gen fire tablet, thanks to the many helpful posts here. However during some of my failed attempts while using Magisk, TWRP App, etc, I've somehow managed to wipe out my stock Recovery partition/files. I can do normal booting fine and I'm sure that I have root, as confirmed by the # at ADB shell and the Root Checker apps available.
I've tried the following:
-Entered Fastboot mode and tried several commands there: always resulting in a 'the command you input is restricted on locked hw' (So, obviously, my bootloader is locked (but I've overwritten it somehow, so it makes me think that at some point I was able to unlock it and overwrite it?)
-Flashfire, TWRP, Magisk and Flashify apps - successful messages every time I try, but no joy when trying to enter recovery mode (it's possible I'm trying to flash the wrong recovery.img file? - does anyone have it and what is it's size? i searched my tablet for the file and found two: one 17mb and the other 8mb - both "flashed" successfully, but no joy when trying to boot into them)
-adb su commands
-Giving up and doing a full Factory Restore via the GUI - it just tries to reboot to the recovery mode, which doesn't exist, so i can't do anything.
-Giving up and doing a full Factory Restore via Fastboot mode - 'the command you input is restricted on locked hw'
I was so happy I was able to obtain root, but if something gets wonky or I decide to try the much raved about resurrection image, i need to have the recovery boot available if/when everything goes wrong.
Please and thanks again for any advice.
Daveychan said:
Please and thanks again for any advice.
Click to expand...
Click to collapse
It's fairly simple but cumbersome to recreate recovery with root. You need to locate the original install-recovery script for your Rom. You may search in /etc or /system/etc . Most likely though your SuperSu deleted it.
So you download your particular Rom version from amazon, unpack it into a system image via mtk-extractor, mount that system image, and find the files.
You can mount this extracted system.bin either on Linux, or directly on your tablet. Just push it to /sdcard, and do this: https://stackoverflow.com/questions/36448234/how-to-mount-a-loop-device-in-android
Then you run the full install-recovery script which will patch your boot.img into recovery partition.
Alternatively, you can beg someone here to dump their HD8 2017 recovery, and upload the image here. So you can dd it in using root into the appropriate partition.
See, I told you - it's all very simple !
Edit: @dondraper23 - can you help a fellow XDA-er? Just dd your HD8 2017 recovery, and post it here.
Code:
dd if=/dev/block/platform/soc/by-name/recovery of=/sdcard/recovery.img
Then zip it, and post it here.
Thank you very much for the fast reply. Much appreciated!
I’ll give this a try ASAP and post back.
If anyone has the recovery.img for the HD8 Gen7, please do post it.
Thank you again!
Okay, i've spent several hours on this and I need to ask for more help.
I managed to get the system.img file from the Amazon .bin as you described. (I used the MTK Extractor for that. It's 1.57 GB by the way.) Next, I moved the system.img file to my Fire's SD card, then I connected the Fire to my Linux, and mounted the system.img file in Linux so I can see the file directory.
I can now see the install-recovery.sh file, located in the /bin folder of the mounted image, but it's read-only. Even by opening to that path via terminal with SU and trying to chmod 777 the file, it's still locked as read-only.
So, I don't know what to do next. I can't copy the file, and I don't see how to run the file via Fire anyway. (Was I supposed to somehow mount the system.img file via ADB commands and then run it that way? If so, I don't know how to do that.)
Sorry if I've asked something obvious or silly. As before, I appreciate the assistance!
Please and Thanks!
Daveychan said:
Okay, i've spent several hours on this and I need to ask for more help.
I managed to get the system.img file from the Amazon .bin as you described. (I used the MTK Extractor for that. It's 1.57 GB by the way.) Next, I moved the system.img file to my Fire's SD card, then I connected the Fire to my Linux, and mounted the system.img file in Linux so I can see the file directory.
I can now see the install-recovery.sh file, located in the /bin folder of the mounted image, but it's read-only. Even by opening to that path via terminal with SU and trying to chmod 777 the file, it's still locked as read-only.
So, I don't know what to do next. I can't copy the file, and I don't see how to run the file via Fire anyway. (Was I supposed to somehow mount the system.img file via ADB commands and then run it that way? If so, I don't know how to do that.)
Sorry if I've asked something obvious or silly. As before, I appreciate the assistance!
Please and Thanks!
Click to expand...
Click to collapse
Sure, just copy that install-recovery.sh file to your tablet, into /data/local/tmp. There is also another file you will need, it's /system/recovery-from-boot.p . Copy this one to /data/local/tmp as well. Then edit your install recovery script, to point to this /data/local/tmp/recovery-from-boot.p . Then just su, chmod 777 your install recovery script, and run it. It should take your boot, and patch it into recovery using recovery-from-boot.p patch file.
Thank you for the fast reply. But because that sh file its read-only, I can't open it or copy it.
Error when running the script
Hello again,
I managed to get around the read-only problem (opening everything as Superuser in Linux was the trick to making that work, for other noobs who may be following along with my pain here.)
I grabbed those two files as you indicated and followed the instructions. Unfortunately I was met with a ton of error messages. Here they are:
=====================
[email protected]:/data/local/tmp # /data/local/tmp/install-recovery.sh
contents of partition "/dev/block/platform/mtk-msdc.0/by-name/recovery" didn't match EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery:7022592:38eeb844c578f6bbfb6edf8ddf7ba1112200a25c
file "EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery:7022592:38eeb844c578f6bbfb6edf8ddf7ba1112200a25c" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
patch EMMC:/dev/block/platform/mtk-msdc.0/by-name/boot:4720640:9dc6d0ebab0b237a7b2f31ae0fabe026da83cda5: LoadPartitionContents called with bad filename (EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery)
contents of partition "/dev/block/platform/mtk-msdc.0/by-name/recovery" didn't match EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery
contents of partition "/dev/block/platform/mtk-msdc.0/by-name/boot" didn't match EMMC:/dev/block/platform/mtk-msdc.0/by-name/boot:4720640:9dc6d0ebab0b237a7b2f31ae0fabe026da83cda5
source file is bad; trying copy
failed to stat "/cache/saved.file": No such file or directory
failed to read copy file
=====================
I'm attaching the two files i pulled from the system.img file - as converted from the .bin file downloaded from Amazon (as above), in case you are still willing to help out and can take a look. (I edited the install-recovery.sh file to the correct path already, so it's not the original anymore.)
MUCH APPRECIATED!
Thank you!
Daveychan said:
Hello,
Please and thanks in advance for any assistance!
I've successfully rooted my HD8 7th gen fire tablet, thanks to the many helpful posts here. However during some of my failed attempts while using Magisk, TWRP App, etc, I've somehow managed to wipe out my stock Recovery partition/files. I can do normal booting fine and I'm sure that I have root, as confirmed by the # at ADB shell and the Root Checker apps available.
I've tried the following:
-Entered Fastboot mode and tried several commands there: always resulting in a 'the command you input is restricted on locked hw' (So, obviously, my bootloader is locked (but I've overwritten it somehow, so it makes me think that at some point I was able to unlock it and overwrite it?)
-Flashfire, TWRP, Magisk and Flashify apps - successful messages every time I try, but no joy when trying to enter recovery mode (it's possible I'm trying to flash the wrong recovery.img file? - does anyone have it and what is it's size? i searched my tablet for the file and found two: one 17mb and the other 8mb - both "flashed" successfully, but no joy when trying to boot into them)
-adb su commands
-Giving up and doing a full Factory Restore via the GUI - it just tries to reboot to the recovery mode, which doesn't exist, so i can't do anything.
-Giving up and doing a full Factory Restore via Fastboot mode - 'the command you input is restricted on locked hw'
I was so happy I was able to obtain root, but if something gets wonky or I decide to try the much raved about resurrection image, i need to have the recovery boot available if/when everything goes wrong.
Please and thanks again for any advice.
Click to expand...
Click to collapse
You shuld try:
-Extract an ota update in a folder
-Run from the folder with the extracted files
Code:
fastboot flash boot boot.img
the recovery is in boot.img, doing this helped me on a similar situation
Thanks to @bibikalka for pointing me to this thread
On the 7th gen fire hd8 TWRP doesn't work yet
t0x1cSH said:
You shuld try:
-Extract an ota update in a folder
-Run from the folder with the extracted files
Code:
fastboot flash boot boot.img
the recovery is in boot.img, doing this helped me on a similar situation
Thanks to @bibikalka for pointing me to this thread
On the 7th gen fire hd8 TWRP doesn't work yet
Click to expand...
Click to collapse
It's not enough to reflash boot.img ! Recovery is created on boot by patching boot.img, but the OP's fire has messed up recovery creation scripts due to SuperSu. So he needs to either re-run the recovery creation script manually - which seems to produce errors, or simply flash a full recovery image - hence my request to extract it from a fire with working recovery.
Hey, I'll pull the recovery off mine tomorrow
NFSP G35 said:
Hey, I'll pull the recovery off mine tomorrow
Click to expand...
Click to collapse
That would be fantastic! Thank you much!
Here you go
Daveychan said:
That would be fantastic! Thank you much!
Click to expand...
Click to collapse
Just FYI, to flash this image file into recovery (assuming you have the recovery image sitting in /sdcard/recovery.img):
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/mtk-msdc.0/by-name/recovery
bibikalka said:
It's not enough to reflash boot.img ! Recovery is created on boot by patching boot.img, but the OP's fire has messed up recovery creation scripts due to SuperSu. So he needs to either re-run the recovery creation script manually - which seems to produce errors, or simply flash a full recovery image - hence my request to extract it from a fire with working recovery.
Click to expand...
Click to collapse
this is the recovery partition straight from my hd8 2017
but i am very curious about a thing, if you look at booth the boot.img and the recovery partition they contains exactly the same data, in the same structure so why cant he simply flash boot.img?
t0x1cSH said:
this is the recovery partition straight from my hd8 2017
but i am very curious about a thing, if you look at booth the boot.img and the recovery partition they contains exactly the same data, in the same structure so why cant he simply flash boot.img?
Click to expand...
Click to collapse
They do have a lot of similarities, that's why recovery is created by patching boot via a relatively small patch file. But, they are still different! That recovery menu is contained entirely within the recovery image, while the boot image does not do that.
Just to add to this, you don't need to flash the boot.img to use install-recovery.sh.
You can also modify the script to read boot from an img file.
k4y0z said:
Just to add to this, you don't need to flash the boot.img to use install-recovery.sh.
You can also modify the script to read boot from an img file.
Click to expand...
Click to collapse
Do you care to post a script that does that, and writes into a recovery image file? The syntax of that patch command is a bit messy, so I would not mind having a debugged working script
Hello again,
My apologies for the delay, work was busy this week, and I couldn't find the time to check the solution until now.
I'm so VERY HAPPY to report that all worked well, and the recovery.img and the command line you provided worked perfectly. (WOW! Thank you!)
For those who want the details, the message after the command in the terminal was:
==
#dd if=/sdcard/recovery.img of=/dev/block/platform/mtk-msdc.0/by-name/recovery
----
34816+0 records in
34816+0 records out
17825792 bytes transferred in 1.159 secs (15380320 bytes/sec)
==
I then did a full power down, and then a started it up again while holding the top-left Volume key and the Power key, and look at that! I'm sitting at the Amazon system recovery screen again! <insert YAY! here>
I'm not sure if it matters, but I thought I'd mention it. At the bottom of the screen in orange letters, it says:
===
E:Error in /cache/recovery/last_kmsg
(No space left on device)
===
So, after a little bit of searching, I selected "wipe cache partition", rebooted again into recovery, and the error is gone now.
Another normal reboot started the "Optimizing apps..." thingy, but it finished quickly and I can confirm that all my stuff is still there. Just to be sure, I did another reboot to recovery, no error messages this time, and then another regular reboot, with no optimizing.
It appears that everything in my world is good again!
My sincerest gratitude and appreciation to all who helped contribute and support this solution.
THANK YOU VERY MUCH!
Daveychan said:
the much raved about resurrection image .
Click to expand...
Click to collapse
Out of curiosity, what is this? There is an image, other than stock, for the 7th Gen HD8?
Resurrection-remix
xnatex21 said:
Out of curiosity, what is this? There is an image, other than stock, for the 7th Gen HD8?
Click to expand...
Click to collapse
It's a WIP for the HD8 I've read. My friend has this on his HD7 and swears it's twice as fast as the regular.
Here's some info:
https://forum.xda-developers.com/kindle-fire-hd/7-development/rom-resurrection-remix-5-1-x-t3234535
and here:
https://forum.xda-developers.com/le-pro3/development/9-0-resurrection-remix-v7-0-t3894663
Hello guys,
i want to install LOS16, but running into problems at the beginning:
I updated my adb and OP Usb drivers.
I booted and flashed twrp-3.2.3-x_blu_spark_v9.91_op6
Now I tried to sideload OOS 9.0.17 -> Error: Cannot read file
I accessed the internal storage and tried to copy the file -> The Dialog to copy the files starts, but closes after some time, without any error.
Can anyone help?
Im sorry, I had already read about flash-all-partions.bat and forgot.
Now, after booting to bootloader and starting the bat i get many errors, that every .img file is nocht found
*sigh*
Yeah, everything is so obvious. unpacked all zips now its working....
delete pls