[GUIDE] Recover FULL GT-I8160P if flashed to GT-I8160 (non-P) - Galaxy Ace II Android Development

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
UPDATED 2013-09-06 (NEW AND EASY WAY with links to GB/JB FULL 3-parted Firmwares)
UPDATED 2013-09-05 (I8160PXXMG2_I8160POXXMG2_624MB_MULTI_ROOT)
UPDATED 2013-07-26 (USB Debugging is not needed for working with ADB in Android System Recovery)
UPDATED 2013-07-24 (I8160POXXMF1_MULTI & I8160POXXMF1_MULTI_ROOT)
This GUIDE is for those who own an GT-I8160P and flashed it to an GT-I8160 (non-P) with one of the leaked JB FW MB2/MB4 and/or MC8 or mixed MC8/ME1 or GB RUS LK6 (3-Parted).
This will bring back your FULL GT-I8160P with incl. Baseband, Bootlogo, Model info in Recovery, etc!
Without any Counter increase or unofficial custom Binarys!
Old way (NOT recommended anymore because to difficult for some - but still working)
Whats needed:
- Your ROOTED GT-I8160P has an active and working IMEI currently! This is not a guide to bring back IMEI!
- USB-Debugging is activated! - Not needed for ADB
- You know how to ROOT your Phone! GB or JB having different methods! - Good rooting HOW-TO [http://forum.xda-developers.com/showpost.php?p=39799320]
- Installed ADB and basic knowledge in ADB (I recommend installation to C:\ADB>)
- Installed ODIN 3.07 and basic knowledge in flashing with ODIN 3.07
- Knowledge how to enter Android System Recovery and ODIN Download Mode
- External SD-Card (everyone should have one if you own a 8160P)
- Phone is connected with USB cable to PC
- some patience
Which Files are needed:
- I8160P_DBT.rar (Contains I8160P_DBT.bin) [http://d-h.st/Q4L]
- ANY FULL original GB or JB Firmware for GT-I8160P [http://www.sammobile.com/firmwares/1/?model=GT-I8160P&pcode=0#firmware]
Optional Files
- I recommend to use JB FW I8160PXXME1_I8160PDBTME1_DBT [http://www.hotfile.com/dl/222919379/f5c8dfe/I8160PXXME1_I8160PDBTME1_DBT.zip.html]
- 1st TIP: Made by me MULTI-CSC FW I8160PXXMF1_I8160POXXMF1_MULTI [http://d-h.st/TNo]
- 2nd TIP: Made by me MULTI-CSC Pre-Rooted FW I8160PXXMF1_I8160POXXMF1_MULTI_ROOT [http://d-h.st/MeA]
- 3rd TIP: Made by me MULTI-CSC Pre-Rooted FW I8160PXXMG2_I8160POXXMG2_624MB_MULTI_ROOT [http://d-h.st/TEA]
- FULL_NAND_BACKUP_ADB.rar (ADB with easy to handle FULL BACKUP and FULL RESTORE script) [http://d-h.st/Efj]
Further Information
- If you go back to GB and do rooting with Kernel than your Counter will be increased!
- If everything went well your Data remains untouched! (If you did not Wiping Data and Factory Reset)
- BUT: Wiping Data and Factory Reset is still recommended after you finished HOW-TO!
- Keep the Backup of CSPSA_FS and MODEM_FS + EFS save! This is your Serialnumber, IMEI and MAC adress!
- Use ALL ADB commands from your PCs CMD - Command Prompt (e.g. C:\ADB>) while your Phone is in (stock) Android System Recovery
- If you got ADB message: mount: Device or resource busy - Don't care about it! Your SD-Card is already mounted! Go ahead!
- Its sometimes needed to let the SAMSUNG Android ADB Interface install its driver new. That happens if you came from JB and go to GB and vice versa.
Delete old ADB Interfaces in System Control on PC [if needed "Show hidden devices"] but do NOT delete Drivers!
De- and Replug USB that PC can install new ADB Interface. Only do the driver reinstallation if during ADB commands your Phone is not recognized.
Disclaminar:
I'am not responsible if you brick your phone. Keep in mind that we do some critical commands for partition copy/write here.
If you are NOT familar with ADB or ODIN please don't try this at home!
Special thanks goes to:
avkiev @ xda (his very nice xls file of 8160/8160P partitions makes things easy to understand)
Szaby59 @ xda (for his findings that IMEI could be in partition CSPSA_FS)
matthias76 @ android-hilfe (for his hint to changed MAC adress -> solved)
Also thanks goes out to for thier general help
knipseringo @ xda and android-hilfe
KevinNash @ xda
angrybb @ xda
Optional
- Before you start I recommend to make a FULL (incl internal SDCard) Nand-Backup of 3,68 GB (3.959.422.976 Bytes) to external SD-Card
- This Will take 6-7 mins - could be more if your SD-Card is slow.
A) Enter stock Android System Recovery
B) Mount SD-Card
Code:
adb shell su -c "mount -t vfat -o rw /dev/block/mmcblk1p1 /sdcard"
C) FULL Backup:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0 of=/sdcard/fullbackup.img bs=4096"
Option: FULL Restore - If you want to go back to old state of your Phone
Code:
adb shell su -c "dd if=/sdcard/fullbackup.img of=/dev/block/mmcblk0 bs=4096"
Here we go:
1.) Move File I8160P_DBT.bin from Archive to root of external SD-Card
2.) Enter stock Android System Recovery
3.) Open Command Promt (CMD) to you ADB folder (e.g. C:\ADB> )
Leave the CMD ADB Window open. We need it again.
4.) Mount external SD-Card
Code:
adb shell su -c "mount -t vfat -o rw /dev/block/mmcblk1p1 /sdcard"
5.) Backup CSPSA_FS and MODEM_FS + EFS to external SD-Card
Code:
adb shell su -c "dd if=/dev/block/mmcblk0 of=/sdcard/CSPSA_FS.img bs=4096 skip=384 count=384"
Code:
adb shell su -c "dd if=/dev/block/mmcblk0 of=/sdcard/MODEM_FS_EFS.img bs=4096 skip=1024 count=6656"
6.) Write I8160P_DBT.bin from external SD-Card to your Phone
Code:
adb shell su -c "dd if=/sdcard/I8160P_DBT.bin of=/dev/block/mmcblk0 bs=4096 count=17664"
7.) Go directly into ODIN Downloadmode (Hold the 3 Keys as long as needed directly out of Android System Recovery)
8.) Flash FULL original GT-I8160P Firmware with ODIN 3.07 (PDA)
9.) After ODIN rebooted let your Phone boot completely! activate USB Debugging
10.) Root your Phone! (Keep in mind: JB and GB having different methods!)
11.) Enter stock Android System Recovery
12.) Mount external SD-Card
Code:
adb shell su -c "mount -t vfat -o rw /dev/block/mmcblk1p1 /sdcard"
13.) Write saved CSPSA_FS and MODEM_FS + EFS from external SD-Card to Phone
Code:
adb shell su -c "dd if=/sdcard/CSPSA_FS.img of=/dev/block/mmcblk0 bs=4096 seek=384 count=384"
Code:
adb shell su -c "dd if=/sdcard/MODEM_FS_EFS.img of=/dev/block/mmcblk0 bs=4096 seek=1024 count=6656"
14.) Reboot and be Happy that the FULL GT-I8160P with working IMEI is back in Town!
Without any Counter increase or unofficial custom Binarys!
Optional
- Before you start I recommend to make a FULL (incl internal SDCard) Nand-Backup of 3,68 GB (3.959.422.976 Bytes) to external SD-Card
- This Will take 6-7 mins (on an SDHC 32GB Class 10) - could be more if your SD-Card is slow.
A) Enter stock Android System Recovery
B) Mount SD-Card
Code:
adb shell su -c "mount -t vfat -o rw /dev/block/mmcblk1p1 /sdcard"
C) FULL Backup:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0 of=/sdcard/fullbackup.img bs=4096"
Option: FULL Restore - If you want to go back to old state of your Phone
Code:
adb shell su -c "dd if=/sdcard/fullbackup.img of=/dev/block/mmcblk0 bs=4096"
NEW WAY (recommended)
Whats needed:
- Your [email protected] has an active and working IMEI currently! This is not a guide to bring back IMEI!
- Installed ODIN 3.07 (and Samsung Drivers for flashing) and basic knowledge in flashing with ODIN 3.07
- CWM Recovery (Files are linked) for GB or JB (depends on which you are)
- Knowledge how to enter CWM Recovery and ODIN Download Mode
- Knowledge how to install ZIP files from external SD-Card with CWM Recovery
- External SD-Card (everyone should have one if you own a 8160P)
- some patience
Which files are needed:
- BACK_TO_THE_I8160P.zip (CWM installable zip file) [http://d-h.st/Vcn]
- CWM_Recovery_GB_JB.rar (archive with CWM for GB and JB - unpack it) [http://d-h.st/6Nv]
AND ONE OF THE FOLLOWING FIRMWARES
- FULL 3-parted GT-I8160P GB (2.3.6) Firmware DBT (Open Germany) CODE_GT-I8160P_I8160PXXLK2_CL1211774_REV00_user_SEC_KEY_XLK2_4G [http://d-h.st/fWn]
OR
- FULL 3-parted GT-I8160P JB (4.1.2) Firmware DBT (Open Germany) CODE_GT-I8160P_I8160PXXME1_DBT_1106830_REV00_user_low_ship [http://d-h.st/v6N]
OR
- FULL 3-parted GT-I8160P JB (4.1.2) Firmware OXA (Open Europe) CODE_GT-I8160P_I8160PXXME1_OXA_1106830_REV00_user_low_ship [http://d-h.st/Sux]
Whats NOT needed anymore:
- ROOT is not needed
- ADB is not needed
- no more copy&paste of the ADB commands
Disclaminar:
I'am not responsible if you brick your phone.
Special thanks goes to:
avkiev @ xda (his very nice xls file of 8160/8160P partitions makes things easy to understand)
Szaby59 @ xda (for his findings that IMEI is in partition CSPSA_FS - [HOW-TO] Backup/Restore NV Data (IMEI, Serial number, Baseband...))
Shaaan @ xda (for Temporary CWM Recovery - [JB] CWM Recovery 6)
matthias76 @ android-hilfe (for his hint to changed MAC adress -> solved)
unknown user - he want to stay anonymous (for the links to FULL 3-parted Firmwares)
Also thanks goes out to for thier general help
knipseringo @ xda and android-hilfe
KevinNash @ xda
angrybb @ xda
Here we go:
1.) Move File BACK_TO_THE_I8160P.zip to root of external SD-Card
2.) Install CWM Recovery
- For GB: Flash I8160XXLL2_CWM_5.0.2.6_ANT.tar.md5 from archive with ODIN as PDA (This is the CWM Kernel for GT-I8160)
- For JB: Install CWM_6.0.2.8.zip from Android System Recovery. Move this file before to root of external SD-Card (This is the temporary CWM Recovery for JB)
3.) Go into CWM Recovery
- For GB: Press following keys together (as long as needed): VOL UP + HOME + POWER
- For JB: CWM is available right after you installed it from Android System Recovery (Enter Android System Recovery also with VOL UP + HOME + POWER)
4.) Install from CWM Recovery the file BACK_TO_THE_I8160P.zip and follow the instructions on the display
- This will also save your EFS / MODEMFS / CSPSA partitions to folder BACKI8160P on external SD-Card - Keep those files save.
5.) Flash FULL 3-parted GB or JB Firmware (PIT as PIT / CODE as PDA / CSC as CSC)
- This is also instructed in the script - You do not need it twice of course.
- Set ODIN as mentioned here: [HOW-TO] Go back from JB to GB on GT-I8160P (ACE 2 NFC)
6.) OPTIONAL: Flash any GT-I8160P Firmware of your specific country
That was easy, isn't it?
If you are Happy with this please push Thanks! :highfive: - Or if you just like my "Back to the..." Image LoL
If you cannot post here use former Discussion Thread
http://forum.xda-developers.com/showthread.php?t=2279510
Success Stories
miyagi83 (http://forum.xda-developers.com/showpost.php?p=43297460&postcount=111)
ghostface (http://forum.xda-developers.com/showpost.php?p=43317243&postcount=12)
lasy (http://www.android-hilfe.de/samsung...android-4-1-2-fuers-ace2-199.html#post6047728)
Robin Fischer (http://www.android-hilfe.de/root-cu...-es-zum-i8160-geflasht-wurde.html#post6061538)
infinity4 (http://www.android-hilfe.de/root-cu...-es-zum-i8160-geflasht-wurde.html#post6064240)
Maxwel (http://www.android-hilfe.de/root-cu...s-zum-i8160-geflasht-wurde-2.html#post6064287)
Superarni (http://www.android-hilfe.de/root-cu...s-zum-ace2-geflasht-wurde-2.html?#post6072975)
primewell (http://forum.xda-developers.com/showpost.php?p=43494174&postcount=121)
Shadowcareful (http://forum.xda-developers.com/showpost.php?p=45363432&postcount=22)
Moonly (http://forum.xda-developers.com/showpost.php?p=45367023&postcount=34)

Can this be used to come from JB (the P version) back to GB? It would help a lot of people since many people who had official update through Kies (PHE and XEZ CSC) have only 482 MB of RAM. (I would try it if I wasn't such a *****... but I just got my phone back from service yesterday since it was hardbricked )

This will go over GB RUS FW (this will bring you 550MB) and then (after the other suff) we flash I8160PXXME1_I8160PDBTME1_DBT (you get also 550MB)
If you can use an GB FW of I8160P instead of JB could be possible - Logically it must work - BUT THIS IS NOT TESTED BY ME...
Personally I don't see any reason to go back to GB but I understand your wishes.
I think I'm the best choise to test this (because the RIFF Box is lying around here :good
I will test this with the latest GB 8160P DBT - I8160PXXLK2_I8160PDBTLK2_DBT and let you all know.

AGAIN: Success :victory:
Works also with GB I8160PXXLK2_I8160PDBTLK2_DBT
Be sure that you have Pre-Rooted Version of it or the rooted system_rooted.tar.md5 and csc.tar.md5 available....
I don't know if this will work with the Kernel-Root method - I do not test this.....
So it's also possible to go back to FULL I8160P with GB!
With this way we have an access error to DBT CSC - And Multi CSC will be installed. But this is not a problem!
This leads me to the opinion that this might work with any other original FW of JB or GB of 8160P
Feel free to test this and report please if you used another FW.... Please keep in mind that you need to root it to push CSPSA_FS back....

So in which step should I flash the GB DBT ROM? (step 2 or 9 according to your guide)?
Sent from my GT-I8160P using xda app-developers app

fifo171 said:
So in which step should I flash the GB DBT ROM? (step 2 or 9 according to your guide)?
Click to expand...
Click to collapse
Step 9 (of course)
Please read it again and try to understand what we are doing here...
Main Key is to save the CSPSA_FS from a working IMEI FW.
Then we push the first 70 MB of an 8160P DUMP (to get the 8160P back technically)
This is actually the most "risky" part. But you'll have access to Andriod recovery and Downloadmode anyway. So who cares :angel:
Then we flash the 8160P original FW.
After that we write saved CSPSA_FS back to get IMEI.
The Rest is Rooting, ADB Drivers installing and getting back 550MB (with 3 parted RUS FW)
If you like to have another FW combination (to have 482/550/624MB) feel free to test it.
I posted this HOW-TO for the most recommended way! 550MB with JB in my opinion.
BUT: If you want to stay with your current RAM configuration - and only get back the 8160P - Then you can leave 1 - 3 and start directly with Nr. 4.
It might also work if you save the CSPSA_FS before you do the DUMP and FW flashing (NOT tested). But I decided to write this HOW-TO that everyone has the same initial situation...

Okay, my last question
Lets say I'm on P-version JB and have 482 RAM. I want to have 550. The fact that I have only 482 is caused by the new SBL (normal.bin) from XEZ ME1 JB ROM. (the DBT JB Odin package doesn't contain the normal.bin and because of that it has 550 RAM if you flash it over GB) In order to get 550 I need to flash the GB SBL.(most probably ) Can I just do this?
1. backup CSPSA_FS
2. flash the I8160P_DBT.bin you posted
3. restore my CSPSA_FS
Is there a risk of bricking my phone? (Except typing wrong dd command.)
Sent from my GT-I8160P using xda app-developers app

fifo171 said:
1. backup CSPSA_FS
2. flash the I8160P_DBT.bin you posted
3. restore my CSPSA_FS
Click to expand...
Click to collapse
fifo, fifo, fifo... - If you what to have 550MB and JB why you didn't do it as written in the HOW-TO?
This I8160P_DBT.bin is from an GB Phone! Therefore I think the most secure way is to write this to an GB FW.
And in order to get back 550MB for all the best way was to use the GB RUS FW (3-parted).
I can't say exactly if your way will work. What I can say is that during the whole testings with this 70 MB BUMP (if you flash it completly) I got never got HardBrick...
But what do you what me to say? Your Phone will never be Bricked again? I can NOT promise this! I hope you understand this.
AND: Please do not type the commands! Use Copy&Paste. STRG-C for coping the command from the HOW-TO and right mouse button and insert to paste it to ADB window (I can't belive that I'm writing this here )

One question: After you flash the JB rom do you have valid imei without the 13th step (CSPSA restore) or you have to flash CSPSA to show the correct imei even if with LK6 was ok ?

Thanks for this great guide!
Just one question, whlie I am mounting the SD card, cmd writes that "mount: Device or resource busy", but when I do backup, I´ve got a 3,69GB fullbackup.img there, so what am I doing wrong if something..? Thanks in advance.
P.S.: SU rights are allowed for adb in phone.

Szaby59 said:
One question: After you flash the JB rom do you have valid imei without the 13th step (CSPSA restore) or you have to flash CSPSA to show the correct imei even if with LK6 was ok ?
Click to expand...
Click to collapse
No - After JB flash the IMEI is NOT there. If this would be so then we didn't have this whole trouble :laugh:
Only after CSPSA flash! And CSPSA of GB works on JB!
[EDIT] I konw this is strage because LK6 RUS has also an CSPSA. And the IMEI works after flshing this... Could be that this CSPSA of this LK6 has an emty part in it?! That is one of my next plans to check/compare unflashed CSPSA LK6 with flashed working CSPSA.
But it seams that the step over GB RUS is not needed (some futher tests to go) - Main Key is the to save CSPSA from an working IMEI phone, flash the DUMP of 8160P, flash complete FW and write CSPSA back.
After I did some furthr tests I will adapt the HOW-TO. But up to now this works like I've written it.
ghostface said:
Thanks for this great guide!
Just one question, whlie I am mounting the SD card, cmd writes that "mount: Device or resource busy", but when I do backup, I´ve got a 3,69GB fullbackup.img there, so what am I doing wrong if something..? Thanks in advance.
P.S.: SU rights are allowed for adb in phone.
Click to expand...
Click to collapse
If it say "mount: Device or resource busy" then your SD-Card is already mounted and its OK!
ARH! Its 3,68 GB (3.959.422.976 bytes) - You are right!!!! LOL Will correct HOW-TO! :good:

Thanks again mate, I´ve got a fully working i8160P with IMEI and everything :good:

Hi, pls check "uploaded.net" links... don't work
tnx

ChuckyIT said:
Hi, pls check "uploaded.net" links... don't work
Click to expand...
Click to collapse
Just checked it - works...
If you have local restrictions with uploaded.to please wait until Monday - After I updated the HOW-TO I will move the files to DEV-HOST. This seams to more stress-free for most Users.

fluffi444 said:
Just checked it - works...
If you have local restrictions with uploaded.to please wait until Monday - After I updated the HOW-TO I will move the files to DEV-HOST. This seams to more stress-free for most Users.
Click to expand...
Click to collapse
Worked with google DNS (8.8.8.8 and 8.8.4.4) tomorrow will try all and will let you know!

First Post Updated 2013-07-08

fluffi444 said:
Work in Progess - NO ETA - please don't ask
- GT-I8160P with 624MB RAM (out of I8160XXMF1 FW)
Click to expand...
Click to collapse
I'm not sure how but I managed to get 624MB RAM on my i8160P
I was running XEZ JB ROM with 482MB RAM but wanted to try CM10, so I backed up my ROM in CWM, changed some lines in build.prop (otherwise the CM won't install), went to CWM, full-wiped, formated /system, installed CM10 and GApps. The phone still had 482MB RAM with CM10 but it was fast and smooth. After few days I wanted to go back to stock Samsung ROM, so I went to CWM, restored my backup, booted up the phone and BANG - there was 624MB RAM.
I hope you'll find out why this happened.
BTW I was using this CM10 by dh.harald.

fifo171 said:
I'm not sure how but I managed to get 624MB RAM on my i8160P
I was running XEZ JB ROM with 482MB RAM but wanted to try CM10, so I backed up my ROM in CWM, changed some lines in build.prop (otherwise the CM won't install), went to CWM, full-wiped, formated /system, installed CM10 and GApps. The phone still had 482MB RAM with CM10 but it was fast and smooth. After few days I wanted to go back to stock Samsung ROM, so I went to CWM, restored my backup, booted up the phone and BANG - there was 624MB RAM.
I hope you'll find out why this happened.
BTW I was using this CM10 by dh.harald.
Click to expand...
Click to collapse
Thx for this info! Flashed recently (for testing purposes) the MF1 (from 8160) on my 8160P (as it was an still an 8160).
This gave me also 624MB. Without any repartionering.
Knisperingo had his 8160P at the Samsung Service (as it was HardBricked long time ago). They changed the complete PCB and now he has also 624MB with an 8160P! Never heard that before!
I really don't know what this RAM is all about But lets go back to Topic. There are many other threads which are talking about this never ending story of 482/550/624 RAM...
This for instance: http://forum.xda-developers.com/showthread.php?p=42075864

I'm triing to go back to GB but i have a black screen after the splash screen...
im installing the prerooted version of i8160pxxle6
i'm doing something wrong?? tnx

ChuckyIT said:
I'm triing to go back to GB but i have a black screen after the splash screen...
Click to expand...
Click to collapse
I would try to format system/data and wipe cache...In Recovery Mode... If not already done.
And flash the FW again...
If this did not help you could try to format the partitions with the temporary CWM 6.0.2.8
http://forum.xda-developers.com/showthread.php?t=2141395
Menu MOUNTS AND STORAGE
Format SYSTEM, DATA, CACHE, PRELOAD, EMMC
BUT NOT SDCARD!!!! :angel:
After this your phone will not start anymore properly. But this is normal because of formated partitions
Then flash via ODIN again.....
The next start will take longer than normal....

Related

[Tutorial] Root FRF91/FRF85B/FRF83/FRF72 (T-Mo/AT&T) Without Unlocking (100% Working)

[Tutorial] Root FRF91/FRF85B/FRF83/FRF72 (T-Mo/AT&T) Without Unlocking (100% Working)
Credits:
Booker-T
M9x3mos
th3fallen
juan413
_Sri_
Amon_RA
cyanogen
For your amazing works leading up to this guide
Notes:
- Donate if I've helped save your HTC warranty.
- This will work! If you can't figure something out, don't get discouraged. Ask here for help.
- After this process, you can flash whatever ROM you like in recovery. I just have the steps showing for CyanMod so you know you have a good, clean system to start off with.
[T-Mo & ATT] Prerequisites:
- Locked Nexus One flashed with FRF85B
(Stuck on FRF91? Use THIS to downgrade to EPE76. Then update back up to FRF85B.)
- Lastet SDK (Click)
- Working ADB (Info)
- The attached .zip "ROOT_FRF83.zip" (Attachment at bottom)
- Got Mac/Linux? (Click Thanks madj42)
Process:
1) Extract the files within "ROOT_FRF83.zip" into the "tools" directory of the extracted SDK package
2) Open a command prompt or terminal and change to the "tools" directory of the extracted SDK package
- Example: Type "cd C:\Users\Matt\Desktop\android-sdk-windows\tools" and hit Enter
3) Type "loop" and hit Enter
4) With phone attached through microUSB, enter Recovery with the battery cover OFF and the SDcard REMOVED.
- Tip: Be careful not to let the battery fall out during this process
- Tip: To enter recovery, boot while holding Volume down button. Then select the recovery option.
5) When you see the HTC devices attached in recovery mode, hit Ctrl+C, then "y", then Enter
6) Slide in SDcard (Make sure there is no update.zip on it at this point)
- Tip: It should slide in and click VERY easily if you trim the tab on the battery properly. A sharp razor blaze works well.
- Tip: I recommend this instead of other methods (paper slip) because it will work without error
- Tip: You only need to cut as far as the SDcard slot goes, you do not need to trim the entire tab
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
7) On your phone, press Power + Volume Up AFTER inserting SDcard
8) Choose "apply sdcard:update.zip"
- Tip: It will fail, but that is expected because there is no update.zip
- Tip: This is done to mount the SDcard after achieving adb while the SDcard was out
9) In your terminal type "adb push flash_image /sdcard/flash_image" and hit Enter
10) In your terminal type "adb push ota.zip /sdcard/update.zip" and hit Enter
11) In your terminal, type "adb push update.zip /sdcard/update.zip" and DO NOT yet hit Enter
12)Ready your finger near the Enter key of your keyboard so that you can quickly hit it once you complete the next step
13) Choose "apply sdcard:update.zip"
14) As soon as you see the yellow installation progress bar, hit Enter on your keyboard
- Tip: If completed properly, you should see a message about rooting adb
15) Choose "Reboot into system"
You now have root access(aka Admin rights) in your stock ROM, but with limited capabilities.
If you want to do any of the following, please continue:
- Flash a custom recovery
- Perform Nandroid backup
- Flash a Rooted Stock Froyo ROM with full capabilities
- Flash CyanogenMod
16) Download the following to the root of your SDcard
- recovery-RA-nexus-v1.7.0.1.img: http://rapidshare.com/files/393267368/recovery-RA-nexus-v1.7.0.1.img
- Note: UnMount your SDcard after copying these files, but keep your phone plugged in
17) In your terminal type "adb shell" and hit Enter
18) In your terminal type "su" and hit Enter
- Tip: At this point, it will hang until you choose "Allow" on your phone with the SuperUser app pop-up
- Tip: $ should now be replaced with #
19) In your terminal, type "mount -o rw,remount /dev/block/mtdblock4 /system" and hit Enter
20) In your terminal, type "cat /sdcard/flash_image > /system/bin/flash_image" and hit Enter
21) In your terminal, type "chmod 775 /system/bin/flash_image" and hit Enter
22) In your terminal, type "flash_image recovery /sdcard/recovery-RA-nexus-v1.7.0.1.img" and hit Enter
23) In your terminal, type "rm /system/etc/install-recovery.sh" and hit Enter
24) In your terminal, type "rm /system/recovery-from-boot.p" and hit Enter
You can now boot into your new Recovery by turning off your phone and turning back on while holding Volume Down.
If you want the latest CyanogenMod, please continue.
25) Download the following to the root of your SDcard
- update-CM-5.0.8-N1-signed.zip: http://cyanogen-updater.googlecode.com/files/update-cm-5.0.8-N1-signed.zip
- gapps-passion-EPF30-signed.zip: http://www.mediafire.com/download.php?mjzwozjojkh
26) Nandroid backup
- Tip: In Recovery, choose "Backup/Restore" then "Nand backup"
- Tip: This will give you an exact copy of your system's current state which you can revert back to at any time
27) Wipe your phone
- Tip: In Recovery, Choose "Wipe" then "Wipe data/factory reset"
28) Apply zip "update-CM-5.0.8-N1-signed.zip"
- Tip: In Recovery, Choose "Flash zip from sdcard"
29) Apply zip "gapps-passion-EPF30-signed.zip"
30) Reboot into your newly rooted phone!
thanks! is there any specific reason why it has to be FRF83 or FRF72 if you know? for us AT&T Nexus User stuck on EPE54B, shouldn't we be able to do the same? or the ota.zip is different in that sense? Please give us some insight. thanks!
Sorry, where is The attached .zip "ROOT_FRF83.zip" ?
where is the attached .zip "ROOT_FRF83.zip"
Oops!! Added link to the top!
Constrabus said:
Oops!! Added link to the top!
Click to expand...
Click to collapse
the link wont work
Link updated
Constrabus said:
4) With phone attached through microUSB, enter Recovery with the battery cover OFF and the SDcard REMOVED.
- Tip: Be careful not to let the battery fall out during this process
5) When you see the HTC devices attached in recovery mode, hit Ctrl+C
6) Slide in SDcard (Make sure there is no update.zip on it at this point)
- Tip: It should slide in and click VERY easily if you trimmed the tab on the battery properly
7) On your phone, press Power + Volume Up
8) Choose "Apply update.zip from SDcard"
- Tip: It will fail, but that is expected.
9) In your terminal type "adb push flash_image /sdcard/flash_image" and hit Enter
Click to expand...
Click to collapse
Still getting either adb with no sd, or sd with no adb.
When I follow your exact process, apply "sdcard:update.zip" returns
"-- Install from sdcard...
Finding update package...
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted."
and then "adb push flash_image /sdcard/flash_image" returns
"failed to copy 'ota.zip' to '/sdcard/flash_image'ermission denied".
These are the exact same returns I get when I tried the process without a card inserted, which is what leads me to believe the card is in but not mounted.
Is there a way to tell adb to (re)mount the SD card in recovery?
Or am I doing something wrong...
Can you walk me through just those particular steps? Like Cookbook-detailed instructions.
Make sure that you are inserting the sdcard BEFORE you press Power and Volume Up to reveal the recovery options and AFTER you get adb connected in recovery mode with loop.
Also make sure you can get adb working while in android to make sure the driver is installed properly.
lostinatlanta said:
Still getting either adb with no sd, or sd with no adb.
When I follow your exact process, apply "sdcard:update.zip" returns
"-- Install from sdcard...
Finding update package...
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted."
and then "adb push flash_image /sdcard/flash_image" returns
"failed to copy 'ota.zip' to '/sdcard/flash_image'ermission denied".
These are the exact same returns I get when I tried the process without a card inserted, which is what leads me to believe the card is in but not mounted.
Is there a way to tell adb to (re)mount the SD card in recovery?
Click to expand...
Click to collapse
weird thing is adb devices do not see my phone even without SD card...
guess froyo is a must to get this working?
i am on EPE54B, still...
I now have an unlocked, newly unrooted FRF83. Will this tutorial still work for me?
t mobile usa 3g network, stock recovery image. I think I am unrooted because there was a warning in the tutorial and my adb shell denies super user permissions.
kaiser_tytnii said:
weird thing is adb devices do not see my phone even without SD card...
guess froyo is a must to get this working?
i am on EPE54B, still...
Click to expand...
Click to collapse
This guide is for people stuck on FRF83 because you can't revert to the older build where other guides worked.
adambenjamin said:
I now have an unlocked, newly unrooted FRF83. Will this tutorial still work for me?
t mobile usa 3g network, stock recovery image. I think I am unrooted because there was a warning in the tutorial and my adb shell denies super user permissions.
Click to expand...
Click to collapse
If you are unlocked, this guide would be redundant for you. The purpose of this guide is to root without having to unlock, thus preserving your warranty.
Shell script version of loop.bat:
I assume this will work...
Code:
while true; do adb devices; done
Constrabus said:
If you are unlocked, this guide would be redundant for you. The purpose of this guide is to root without having to unlock, thus preserving your warranty.
Click to expand...
Click to collapse
I still would like to get my root back. Will that part of this tutorial work to get the root back?
EDIT: Got it rooted. wow that was easy.
Based on you providing links for recovery-RA-nexus-v.1.7.0.1.img, update-CM-5.0.8-N1-signed.zip, google addon EPF30; will the steps involving these install Cyanogen on my phone?
I was hoping to do this process without wiping my phone's memory and keeping my stock FRF83.
what25 said:
Based on you providing links for recovery-RA-nexus-v.1.7.0.1.img, update-CM-5.0.8-N1-signed.zip, google addon EPF30; will the steps involving these install Cyanogen on my phone?
I was hoping to do this process without wiping my phone's memory and keeping my stock FRF83.
Click to expand...
Click to collapse
If you don't want the Cyanogen ROM or RA recovery just skip step #22 and stop with step #24. I didn't follow this tutorial as I did Booker-T's method with some tweaks but if you do what I said you should be fine.
madj42 said:
If you don't want the Cyanogen ROM or RA recovery just skip step #22 and stop with step #24. I didn't follow this tutorial as I did Booker-T's method with some tweaks but if you do what I said you should be fine.
Click to expand...
Click to collapse
You dont have to use that rom, you can flash any other rom as long as you have root. Paul obrien offeres a rooted FRF83 rom
I was able to do this without taking out / putting the SD card in (and thus avoided filing down my battery. I didn't run "loop.bat" until I was highlighting the Recovery icon, the ran it, when into Recovery, and adb picked it up.
Worked perfect!
Just, when flashing recovery, the better terminal emulator was giving me an error, i used Rom Manager to flash the recovery, and back to terminal to rm /system/etc/ blah blah ....GREAT Tutorial!

X10 Custom ROM AOSP 2.2.1 : How to for dummies

SINCE FREE X10 IS NOW BETA, THIS HOW TO IS NO LONGER VALID
Hello world !
I noticed there was nothing to explain simply how to install the increible X10 Free Rom in dual-boot with your regular 2.1 rom of Zdzihu.
** No responsability for anything, you are all responsible of what you're doing !! **
** Please follow ALL these steps. Don't try to be Indiana Jones by flashing your device without all the tools needed !!! **
INSTALL
(for 1st install)
Before attempting anything, make sure you have AT LEAST 50% of battery charge. Don't try anything with low battery, you can abort the flashing and brick your device !!!
Please make sure you're also running a 2.1 rom (Generic, nordic, official, custom...)​
- Download FreeX10 v0.0.1 file (NOT 002 yet !!!)
- Download Android SDK
You don't need to save the entire archive (but you can), you just need the Tools folder (because it contains ADB, the Android Debug Bridge we need to install files).
- On x10 :
Download and install Busybox (from Market), make sure it says "Done!".
Connect your x10 in USB, mount SD card, and copy files FreeX10.zip and install on the root of your SD Card.
Enable USB debugging (Parameters > Applications > Development).
- On your computer, go in the Tools folder, open a DOS prompt (for Windows 7 : hold CAPS + right click, you'll see Open a DOS prompt) and
type :
Code:
adb shell
(this will run ADB shell... You will get a "$")
- Type :
Code:
su
(this will make you super-user, you will get a "#")
- Type :
Code:
dd if=/sdcard/install of=/data/install && chmod 777 /data/install && /data/install
(It will display "11", "1+1", or "inflating:..." ...)
- Wait, have a beer, pray for your sins for your phone not to turn into a $600 brick
- One minute after, when it shows
Code:
All done, please reboot!
, reboot ! (But you can gently quit ADB by typing
Code:
exit
twice
)
Note : regarding me, I typed "exit" to quit ADB, I turned off ADB on phone and disconnected USB. You can do, it's even safer
- Wait up to 5 minutes for the phone to boot, it is NORMAL !!!! It looks stuck on Sony Ericsson logo and/or on Free X10 logo, it's NOT stuck !!! You MUST wait !!!!
- It will finally run normal, your phone is alive and 2.2-hearted !!
You are now eligible to install v0.0.2 (as it comes as an update).
Dual Boot usage
This rom comes with a great Dual Boot, which means the 2.2.1 is installed safely apart from your original 2.1 rom. This means you can switch back anytime to stock rom. To say it simply :
- Your Android 2.1 is here, and no changes are made to it (apps, version, etc etc). It is stored as it has to be, in the internal 1Gb phone memory storage (called the "NAND").
- FreeX10 (2.2.1) is running from image files (like .ISO files) stored in your SD Card. This means the two Android are living together peacefully, without affecting (theorically) each other.
FreeX10 mainly creates a bootloader, for you to choose whether to test 2.2.1, or go back to 2.1 for your daily use.
- To run 2.2.1 : do nothing (default boot)
- To run 2.1 : press any key at boot, when it shows "Sony Ericsson".
Notes when upgrading to v0.0.2 :
- As Android is stored into image files (.IMG), upgrading will wipe out all your content (it does a fresh "install"), make backup of what you need !
- to avoid future bugs, altough you're not forced to do, do the routines to make sure Wifi, root, packages install, ... work. This is because USB debug can break, so you won't be able to use ADB to fix these bugs
- Root is strongly recommended to work, because it's cool and because the CPU performance is set to highest : stuck at 998MHz all the time, it will drain your battery like hell ! You can switch it back to original power saving plan (ondemand plan) by using (ie) SetCPU. Root required !
If your Android goes instable, does not work anymore, or you want a fresh install after lots of tests, simply drag and drop the original v0.0.2 .img files on your SD card. This will make you boot into a fully fresh install.
For all bugs, commands, etc.. Please go first to this excellent (and very easy) thread !!
Nice..
How about one on AOSP 2.1
Perceval from Hyrule said:
Hello world !
I noticed there was nothing to explain simply how to install the increible X10 Free Rom in dual-boot with your regular 2.1 rom of Zdzihu.
Click to expand...
Click to collapse
nice dummies HOW TO
and ohhh my god there is dummies
all comands needed
INSTALLATION
1. Download the rom package (FreeX10_alpha-release_0.0.1.tar.bz2)
2. Unpack it to the root (main folder) of your SD Card
3. Connect your phone in USB Debugging mode
4. Open ADB shell, switch to root user (SU)
5. Issue the command
dd if=/sdcard/install of=/data/install && chmod 777 /data/install && ./data/install
6. Reboot when installation is finished
7. Enjoy
---------------------------------------------------------------------------------------------
CHANGE BOOT PRIORITY
Copy chargemon.txt file to
/system/bin
folder ON YOUR ORIGINAL 2.1 ROM, NOT FROYO!!!
---------------------------------------------------------------------------------------------
UPGRADE TO 0.0.2 VERSION
Boot into 2.1, unpack the content of FreeX10_alpha-release_0.0.2-UPDATE.tar.bz2 into
/sdcard/FreeX10
folder and reboot into updated 2.2!
NOTES:
1. SMS vibrate is disabled by default; open Messaging, press MENU button -> settings -> vibrate -> always
2. If you don't have radio (network) after 1st boot, please open ADB shell and issue this command:
killall servicemanager
3. If you don't have root access, please open ADB shell and issue this command:
chmod 4755 /system/bin/su
---------------------------------------------------------------------------------------------
hope it helps too
UPDATE TO v.0.0.2
Note : you can only update from 0.0.1 to 0.0.2. I mean you can't do a fresh install of 0.0.2, you MUST have 0.0.1 installed !
- Download v0.0.2 from main thread.
- Run your device on your regular 2.1 rom (while off, power on, and press any button when it displays Sony Ericsson logo)
- Mount the SD Card, then copy data.img and system.img from the archive into the folder /FreeX10. Replace the two .img files.
- Reboot into 2.2, have fun ^^
OmegaRED^ said:
Nice..
How about one on AOSP 2.1
Click to expand...
Click to collapse
I'll try to do one if I get time, but I need a fully working ROM as my phone is useful for my life (still waiting for 2.1 stable )
Thanks for your posts all, it will help everybody who want to try the 2.2
(as it is safe and running from SD card, very very very cool idea !)
Help followed your guide get adb shell not a internal command what am i doing wrong been trying this for hours now
I found drawing a pentagram in human blood and chanting a few words can do wonders too.
fastphil said:
Help followed your guide get adb shell not a internal command what am i doing wrong been trying this for hours now
Click to expand...
Click to collapse
root privileges do you have it?
unmount sdcard
OmegaRED^ said:
I found drawing a pentagram in human blood and chanting a few words can do wonders too.
Click to expand...
Click to collapse
sarcasm...love it
rendeiro2005 said:
root privileges do you have it?
unmount sdcard
Click to expand...
Click to collapse
yes mate i do have root access titanium etc works fine just cant get adb shell to run
When i installed 2.2, it rebooted and when to the sony ericsson logo for almost an hour, does this mean i have to reinstall 2.1, and if so, i would i accomplish this
fastphil said:
yes mate i do have root access titanium etc works fine just cant get adb shell to run
Click to expand...
Click to collapse
and what about sdcard?
uncheck nount/unmount
rendeiro2005 said:
and what about sdcard?
uncheck nount/unmount
Click to expand...
Click to collapse
done that too
fastphil said:
done that too
Click to expand...
Click to collapse
can you post a screenshot of cmd?
ok will do
I am still having problems also...
after I type the cmd...
dd if=/sdcard/install of=/data/install && chmod 777 /data/install && /data/install
it just says:
1+1 records in
1+1 records out
520 bytes transferred in 0.003 secs...
#
so, where am I going wrong?
fyi, I am trying to install v001, not the update, and the phone is rooted, busybox is installed. Sorry, but I have tried for a while now and I finally have to just ask for help. Thanks guys.
here pic off cmd
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
fastphil said:
Help followed your guide get adb shell not a internal command what am i doing wrong been trying this for hours now
Click to expand...
Click to collapse
Does it work when your run "adb" command only ?
It looks to me your error is because you're not in the folder where adb.exe is
It is in folder tools, if you try to run it from root directory (where is the android app with nice icon) it won't work for sure
Edit: didn't see your screenshot >> you are NOT in the correct folder !! (so Windows is searching for a registered command which does not exist, I think there's a thread somewhere on how to add it as a registered (I mean global) command)
You must download Android SDK (22mb... Lmao regarding 4gb for iOS ), extract the archive and go in the tools folder. Here is adb.exe.
when i try & run adb exe it does not open it just closes right away

[CWM UTIL] GS2PreloadBackup/Restore scripts for Samsung JB (02/03/2013)

The JB XXLSJ leak and the latest XWLS8 official JB releases have introduced a new partition on /dev/block/mmcblk0p12 mounted to /preload.
This was required due to the fact that the /system partition just isn't big enough to hold all the extra apps the JB leak requires.
The problem with this is that with the exception of PhilZ Kernel and Jeboo, CWM backups in bith Siyah and DorimanX omit the backing up this /preload partition. If you regularly try out different ROMs and restore back, this can mean your ROM's getting a little out of step as it would have the /preload files from the ROM you last flashed, with all other files coming from the ROM you performed the backup on.
Currently, if you are on Siyah/Dori, the only way to backup/restore everything via CWM backups is to:
a) reboot into recovery
b) flash PhilZ/Jeboo
c) go to advanced>reboot recovery
d) make your backup in PhilZ/Jeboo/Apolo recovery
and if you want to revert back to Siyah/Dori:
e) flash Siyah/Dori
f) advanced>reboot recovery
If you ever need to restore, and you are using Siyah/Dori then you will need to:
a) reboot into recovery
b) flash PhilZ/Jeboo
c) go to advanced>reboot recovery
d) restore your backup in PhilZ/Jeboo/Apolo recovery
e) flash Siyah/Dori
f) reboot
NOTE: Later versions of PhilZ require you to specifically set the backup/restore of /preload. This is done in PhilZ CWM Recovery:
1. boot into PhilZ recovery
2. Philz settings
3. Special backup and restore
4. Misc nandroid settings
5. Toggle /preload processing (make sure this says /preload will be processed)
To get around this current omission in Siyah and Dori, I have written the following 2 CWM flashable zips:
GS2PreloadBackup
This will backup your current /preload partition.
The backup is made on a per-ROM basis to /sdcard/MyBackups/preload/[ROM-Name]/preload.tar. Therefore, if you backup on several different ROMs, you will get several ROM folders in this preload backup location, one backup per ROM​GS2PreloadRestore
This will restore the /preload backup made by the above script for your current ROM.​
So if you are on Siyah/Dori and want to make a full backup without flashing between PhilZ, you can now do the following:
1. Boot up into recovery
2. Make your CWM backup
3. Run GS2PreloadBackup.zip
Further down the line, if you ever wanted to restore this, then
1. Boot up into recovery
2. Restore your CWM backup
3. Flash GS2PreloadRestore.zip
The restore is sensitive to the ROM you are currently on, so it will only restore the /preload for you current ROM, provided you have run the backup script previously for the ROM of course.
Changing the backup location
By default, backups are made to the internal SD card in /sdcard/MyBackups as described above. You can change the backup location to the external SD card if required. This can be done by editing /sdcard/MyBackups/HawkerOptions/MyWipeOptions.prop. Within this file there is a line that tells the script where the backups are to be stored. Edit the following line as required:
BKP_LOCATION=int (backs up to INTERNAL SD Card, ie. /sdcard/MyBackups)
BKP_LOCATION=ext (backs up to EXTERNAL SD Card, ie. /storage/extSdCard/MyBackups)
Please note, that if you change the location between int/ext in MyWipeOptions.prop, your backups will not get automatically moved to the new location. You would have to manually move the current backup over to the new location if you do not want to potentially have two copies of the backups.
Test Mode
The script inside the zip file that does all the work is called GS2Hawker.sh. This can be called via adb shell/Script Manager etc. in order to perform a test dummy-run. The Test Mode goes through all the motions as per a standard CWM Recovery run, but it does not remove any files/folders in any way, and merely shows the commands it would have done.
eg. extract GS2Hawker.sh from the zip using 7Zip or similar
adb shell
sh GS2Hawker.sh PreloadBackup
sh GS2Hawker.sh PreloadRestore
Summary of Files Created/Used
1. /sdcard/MyBackups/HawkerLogs/GS2PreloadBackup.log.
2. /sdcard/MyBackups/HawkerLogs/GS2PreloadRestore.log.
These shows the activity log of what the script has done. This gets overwritten the next time you run the script.
3. /sdcard/MyBackups/HawkerOptions/MyWipeOptions.prop. Options file for all my scripts. Currently this contains the option for backup location, internal or external SD card. (See Changing the backup location above)
These scripts are of course only a temporary measure as I am in no doubt that both Siyah and Dori will both also include the /preload partition in their CWM Recovery scripts very shortly, but for now, I hope this might help one or two of you out.
Known Issues
Free space checking prior to performing the backup always returns free space on internal sdcard even when
backing up to external sd card.
For some reason, when I do a df (on Siyah, not sure about other kernels)
I get the following:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mmcblk0p11
12063840 231264 11832576 2% /mnt/.secondrom
/dev/block/mmcblk1p1 12063840 231264 11832576 2% /sdcard
/dev/block/mmcblk0p11
12063840 231264 11832576 2% /sdcard
/dev/block/mmcblk1p1 30648992 17592608 13056384 57% /emmc
It appears /dev/block/mmcblk1p1 is mounted to /emmc AND /sdcard?????!!!!
All file operations on /emmc gets performed on the extenral sd card as expected (ie your backups WILL go to external), BUT when the df command is issued to check for available space, it is performed on /sdcard! Therefore, if the script is trying to find the space left on /emmc, and the device returned from the df command is /sdcard, then an error is presumed, an no space check performed.
Please Note
I use these scripts myself between many flashes of different ROMS, and are provided here, as-is, out of my passion for development. Although every effort has been made to ensure everything works correctly on my handset I cannot be held responsible if things get messed up, or if you put something in your user-definable files that you shouldn't have included. As with everything else on here, you flash anything at your own risk. I always recommend performing a full CWM backup before attempting to flash anything onto your device.
Current Versions
GS2PreloadBackup 1.05 (22/05/2013)
GS2PreloadRestore 1.05 (02/03/2013)
Note: If the latest versions quoted above do not appear in the download devhost site, then please be patient!
ApriliaM3 should soon be uploading them.
Downoad Here
Download Here
My HUGE thanks goes out to ApriliaM3 for hosting the scripts.
Please give him the thanks he deserves.
To Do
....​
Work in Progress
....​
Changelog
GS2PreloadBackup v1.05 (22/05/2013)
1. Extra free space checking. (See OP for known issues)
GS2PreloadBackup v1.04 GS2PreloadRestore v1.05 (02/03/2013)
1. Backups can now go to either internal or external SD Card. See Post #1 for details
GS2PreloadRestore v1.04 (22/02/2013)
1. Now restores /preload/symlink instead of whole of /preload for greater flexibility in dual-boot systems
2. Current /preload/symlink contents removed before restore giving a better snapshot for the restore point
GS2PreloadBackup v1.03 (22/02/2013)
1. Now backs up /preload/symlink instead of whole of /preload
GS2PreloadRestore v1.03 (22/02/2013)
1. Current /preload contents removed before restore giving a better snapshot for the restore point
2. Progress now given in Mb during the restore process
v1.02 (13/02/2013)
1. Numerous display updates
2. Log file now goes to /sdcard/MyBackups/HawkerLogs so that they are grouped with logs from my other scripts
v1.01 (31/01/2013)
1. Progress now given during backup operation of the size of backup complete​
Thanks buddy:thumbup::thumbup:. I just wanted to get in first. :thumbup::thumbup:
Edit. I just ran a backup and it worked and so did the restore :thumbup:
In the meantime I'll leave this picture until I can post something constructive.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SIGNATURE
PHONE : SGSII
Sent via: Tapatalk 2
Main ROM: Alliance rom v5.2
KERNEL : Dorimanx 7.39
(DEFAULT PROFILE AND SETTINGS )
MODEM : BVLP7
BATTERY : Stock 1650mAh
EXTERNAL Sdcard : Samsung Class 10 32gb
LAUNCHER : Apex
My Guides list to install NeatRom and other ROMS and kernels on LSJ + tools to have a bug free rom + how to back up and RESTORE FOM FULLY = http://forum.xda-developers.com/showthread.php?p=35923600
1.Rom Nuke script
http://forum.xda-developers.com/showthread.php?p=36268094
2.Kernel Clean script
http://forum.xda-developers.com/showthread.php?p=34879811
3.Fast Dormancy :
http://forum.xda-developers.com/showthread.php?p=36396636
4. How to install full wipe with rom nuke on LSJ
http://forum.xda-developers.com/showthread.php?p=36655790
Nice guide
Sent from my GT-I9100 using xda premium
Thanks Hawker, great work.
Red you got a nice ass!
Edit. ... I have done a backup and ran the zip after it and it worked great.
Thank you!
Sent From My Galaxy S2 Running
AllianceROM Powered By DorimanX Kernel
Some more great work and another great guide there Paul... well done!
I have now created a directory for your work on my Dev-Host mirror site HERE
ApriliaM3 said:
Some more great work and another great guide there Paul... well done!
I have now created a directory for your work on my Dev-Host mirror site HERE
Click to expand...
Click to collapse
Thanks Pete.
I've updated the links in the OP to yours.
I'll let you know if I update the scripts at all.
Cheers mate!
:good:
Thank you, really usefull script.
deleted
Updated to V1.01
See Changelog for details
hawkerpaul said:
Updated to V1.01 (pending upload to ApriliaM3's host.....)
Click to expand...
Click to collapse
All done Paul.
hawkerpaul said:
Updated to V1.01
See Changelog for details
Click to expand...
Click to collapse
I have been trying to backup preload to my external sd card by modifying /sdcard/MyBackups/MyBakDevice.txt ( see screenshot)
But the backup is stil made on the internal and after every attempt the content of MyBakDevice.txt is set back to the default /sdcard
I'm I doing something wrong here
EDIT: Tried 3 times, same result every time.
Backup to external sd card not possible currently, so I'm looking into getting this working properly. For now, ignore any information relating to MyBakDevice.txt. All backup will go to internal sd card only for the time being.
Updated to V1.02
See post #2 for details
Updated GS2PreloadRestore to v1.03
See post#2 for details
AW: [CWM UTIL] GS2PreloadBackup/Restore scripts for Samsung JB (22/02/2013)
This is awesome, thanks for your work!!!!!
May I ask something? (if not, ignore me)
Is it possible to not backup the full /preload partition but only the /preload/symlink part of it? I ask because it would be very helpful with this : http://forum.xda-developers.com/showthread.php?p=38209559
So, a user could backup /preload/symlink/... Then install a 2nd Rom, that will probably format /preload and just restore it easily with your File. This might be a very big step for Dual boot as it makes so many things easier!
Anyways, thank you very much for your efforts!!!
Greetings
Thomas
Sent from my GT-I9100 using xda app-developers app
As far as I'm aware, apart from the generic lost+found folder linux creates under each partition (which 99% of the time will be empty) the only contents of the /preload partition IS the symlink folder.
AW: [CWM UTIL] GS2PreloadBackup/Restore scripts for Samsung JB (22/02/2013)
hawkerpaul said:
As far as I'm aware, apart from the generic lost+found folder linux creates under each partition (which 99% of the time will be empty) the only contents of the /preload partition IS the symlink folder.
Click to expand...
Click to collapse
Thanks!
But in my /preload there is the /symlink part of my Sammy Rom (shorted to about 80mb) and the /system of 2nd Rom (MCM's 10.1)
The created Backup with your zip is about 390mb big so I figured that there has to be more than just the symlink stuff.
This could be solved, of course by a clean install of first Rom (Sammy), backup with your file, install 2nd Rom and then restore /preload.
But it would be easier if only /preload/symlink would be backed up and later restored.
But, important, I don't want to bug you, it's awesome as it is, seriously!!
Greetings
Thomas
Sent from my GT-I9100 using xda app-developers app
Ok mate, I'll have a look into it for you.
Edit:
Updated to GS2PreloadBackup v1.03 and GS2PreloadRestore V1.04
See post #2 for details
AW: [CWM UTIL] GS2PreloadBackup/Restore scripts for Samsung JB (22/02/2013)
hawkerpaul said:
Ok mate, I'll have a look into it for you.
Edit:
Updated to GS2PreloadBackup v1.03 and GS2PreloadRestore V1.04
See post #2 for details
Click to expand...
Click to collapse
Awesome, thank you very much!!!
If it's ok I will add a how-to to my thread and link to yours?
To me, this is an enormous step forward great!!
Sent from my GT-I9100 using xda app-developers app

[FAQ] Frequently Asked Questions For Moto E [UPDATED-05/10/14]

Frequently Asked Questions
Motorola Moto E
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello Guys this is a FAQ for Moto E. Please read this here before posting it in the developmental section or creating a thread anywhere.
I am sure it will help.
Thank You
A big thanks goes to @matmutant for providing FAQ templates and his own FAQ from I have copied some things.Here is the original guide
[SIZE=+1]Q1: How to access Fastboot?[/SIZE]Hold PowerButton and VolDown during boot.​
[SIZE=+1]Q2: How to unlock Bootloader?[/SIZE]Boot to Fastboot and
follow my guide
Motorola guide on Motorola's website
@matmutant Speed Run Guide
[SIZE=+1]Q2: How to relock Bootloader?[/SIZE]Boot to Fastboot and give the command "fastboot oem lock"​
[SIZE=+1]Q3: How do i get adb and fastboot drivers ?[/SIZE]For windows, follow this guide or this one
although, it seems Motorola Device Manager works ok for win7x86-32 (but not for win7x64-64?) i cannot answer this i'm under linux
other USB drivers if first method failed, source
For Linux, get fastboot files here also, adb and fastboot can be installed using repos for ubuntu-based distros packages needed are : android-tools-adb and android-tools-fastboot (android-tools-fsutils may be useful too)
eg:
Code:
sudo apt-get install android-tools-fastboot
[SIZE=+1]Q4: How to flash Stock Firmware?[/SIZE]Please Follow My Guidehere.​
[SIZE=+1]Q5: How to Root my device ?[/SIZE]First you'll need to unlock your bootloader,
then follow this guide
OR this guide(User Friendly)
​
[SIZE=+1]Q6: Where can i find a Custom recovery ?[/SIZE]TWRP 2.7.2.0​
[SIZE=+1]Q7: How to access bootloader?[/SIZE]- Via ADB :
Code:
adb reboot bootloader
- The hard(ware) way :
With the phone powered off, press the VOL DOWN KEY for 2-3 seconds then POWER key then release.
The device will display different BOOT OPTIONS
Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select
[SIZE=+1]Q8: How to access recovery?[/SIZE]
using terminal, if the device is already rooted
Code:
su
reboot recovery
via adb
Code:
adb reboot recovery
via bootloader
boot to bootloader (see Q11) and select recovery (use Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select)
[SIZE=+1]Q9: How to force reboot my frozen device?[/SIZE]
Press and hold the Power button for 10 - 20 seconds, the device will restart and go through the boot-up sequence [source]
(VOL DOWN hold + a quick tap on POWER should force reboot when in bootloader) [source]
[SIZE=+1]Q10: How to charge my device and extend battery life?[/SIZE]Follow Motorola tips:
How do I properly charge my device?
How can I extend my battery life?
[SIZE=+1]Q11: Does rooting/unlocking your phone invalidate its warranty? (In EU)[/SIZE]In short: No. Just the fact that you modified or changed the software of your device, is not a sufficient reason to void your statutory warranty. As long as you have bought the device as a consumer in the European Union.
For Indian customers, The warranty is void if you unlock/root your device. Motorola also reserves the right to maintain the records of unlocked bootloader devices. So you may not even get the warranty by relocking the device
[source]​
[SIZE=+1]Q12: What to do if my battery is fully discharged and not re-charging?[/SIZE][source]​
[SIZE=+1]Q13: Lost IMEI ? : How to backup / restore PDS partition and why?[/SIZE]On Motorola devices the 'pds' partition contains information specific to your machine: IMEI, MAC address, serial number, etc. This partition can be lost by accidental format or over time due to filesystem corruption. If you have made a backup, there is a good chance you can bring your handset back to life.
==> PDS backup will help to restore lost IMEI. It is a situation when the phone reports that the IMEI is unknown. ; This works like a vaccine, apply before having issue with IMEI, after it will be too late !
Instructions:
**Root Required**
Using ADB you can make a copy of the partition and move it to a safe place (Google Drive?):
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/pds of=/sdcard/pds.img​
To restore in the event of corruption or loss:
adb shell
su
dd if=/sdcard/pds.img of=/dev/block/platform/msm_sdcc.1/by-name/pds​(assuming you've pushed pds.img to internal SDcard storage first)
If for some reason this doesn't work, maybe your IMEI isn't destroyed but only not "readable" by system (file system issue? misread cluster reading frame ? no idea), in that case you may read the following story : http://forum.xda-developers.com/showthread.php?p=52648789
​
[SIZE=+1]Q14: How to disable/enable auto On/Off screen with Flip Shell?[/SIZE]
for stock rom : (disabling, since it's enabled by default)
install Xposed framework (and reboot)
install and enable MotoMagnetOff (and reboot)
Follow this FAQ​
[SIZE=+1]Q15: How to remove the 'unlocked warning' message?[/SIZE]Follow @cschmitt method and default Motorola logo will be back .​
[SIZE=+1]Q16: How to reboot into 'safe mode'?[/SIZE]
Press power button, on the pop up, either keep pressing 'shut down' [stock] or 'reboot' [AOSP based]
more infos about this feature​
[SIZE=+1]Q17: What are the Moto E tech specs[/SIZE]
XT1021 (Single Sim)
XT1022 (Dual Sim)
XT1025 (Dual Sim With TV Digital)
[SIZE=+1]Q18: How to get OTA updates even after Rooting and Flashing a custom Recovery[/SIZE]
Use the full unroot option from the Super Su
Flash the stock recovery Use Code : mfastboot flash recovery recovery.img
Now you'll be able to get OTA updates as before
[SIZE=+1]Q19: How to Unlock Advanced Camera Settings?[/SIZE]
Refer to this thread​
some usefull lines of commands for any user wanting to know what's going on:
requirements :
On Windows : install Moto E drivers and
On Linux : set your rules following that guide (3. Set up your system to detect your device.) : add to /etc/udev/rules.d/51-android.rules the following code
Code:
#motoe normal mode
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}==”2e82″, MODE="0666"
#motoe debug mode
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}==”2e76″, MODE="0666"
#motoe fastboot mode
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}==”2e80″, MODE="0666"
For specific access by one group of users, add GROUP="[groupname]"
______________________________
______________________________
______________________________​
Let's start ! :
in terminal, just type the lines,
in ADB, add "adb" before the commands
if you want not to display the output in terminal, specify the path :
Code:
command > /where_you_want_your_output_to_be_stored/name_you_want_for_the_log
to know if KSM is really turned on : KSM means Kernel Samepage Merging, may not exist on Moto E stock or custom roms
Code:
cat /sys/kernel/mm/ksm/run
to know what modules are running :
Code:
lsmod
install an app from terminal :
Code:
pm install /sdcard/app1.apk
from adb :
Code:
adb install /home/user/app1.apk
(if your .apk is located there )
your kernel crashed?
Code:
cat /proc/last_kmsg
ex : from adb, and stored in /home/user/last_kmsg1
Code:
adb cat /proc/last_kmsg > /home/user/last_kmsg1
an app crashed, you want to know why?
Code:
logcat
ex : from adb and stored in /home/user/myfirstlogever
Code:
adb logcat > /home/user/myfirstlogever
don't have an USB cable ?or adb "other the air" :
connect to your home wifi network (both device and pc)
in settings/dev options/ enable adb on TCP/IP
Code:
adb connect xxx.xxx.xxx.xxx:5555
(the IP is the one displayed in the option you choose previously
and then, since it is connected, catch the log :
Code:
adb logcat > /home/user/myfirstlogever
All commands and syntax used for ADB can be found here
reserved---3
reserved----4
last one
Let me reserve a post here
I've updated the thread a bit. Have to leave soon so didn't did much updates.
More Updates Coming Soon
Reserved:victory:
Updated Thread with Model No's
Thanks to @deej_roamer
Like to add an input regarding Q11
For Indian customers, The warranty is void if you unlock/root your device. Maybe OP can add this too.
Hello guys
I switched to moto e from a phone which had a pretty versatile memory system in which i could transfer apps to sd card and use link2sd to partition sd card and use it as internal memory.
in moto e moving the preinstalled apps like maps and music and chrome etc through link2sd causes them to FC.
apart from that i cannot move my whatsapp data to SD card even if i transfer the actual app to sd card partition through link2sd. also, apps do not catch their data from the sd card. everything should be on the internal memory to work and that forces me to not install apps. my whatsapp has important databases which cannot be deleted and they take up 700+MB of internal SD space which cannot be freed to the ext SD since whatsapp doesnt restore from ext card. what to do???
TacTieTee said:
Hello guys
I switched to moto e from a phone which had a pretty versatile memory system in which i could transfer apps to sd card and use link2sd to partition sd card and use it as internal memory.
in moto e moving the preinstalled apps like maps and music and chrome etc through link2sd causes them to FC.
apart from that i cannot move my whatsapp data to SD card even if i transfer the actual app to sd card partition through link2sd. also, apps do not catch their data from the sd card. everything should be on the internal memory to work and that forces me to not install apps. my whatsapp has important databases which cannot be deleted and they take up 700+MB of internal SD space which cannot be freed to the ext SD since whatsapp doesnt restore from ext card. what to do???
Click to expand...
Click to collapse
Thats how KK is designed. App should store their data on internal memory. Sdcard is treated as another partition. Apparently,this is so that on uninstall there's no residual data.
To change that, you need root.
Sent from my XT1022 using Tapatalk
Falcon G said:
[SIZE=+1]Q5: How to Root my device ?[/SIZE]First you'll need to unlock your bootloader,
then follow this guide​
Click to expand...
Click to collapse
There are confirmed rooting methods here and here!​
neo.ank said:
Thats how KK is designed. App should store their data on internal memory. Sdcard is treated as another partition. Apparently,this is so that on uninstall there's no residual data.
To change that, you need root.
Sent from my XT1022 using Tapatalk
Click to expand...
Click to collapse
deej_roamer said:
There are confirmed rooting methods here and here!
Click to expand...
Click to collapse
my device is already rooted guys. trying to keep data in ext but app does not recognise tht data. for example my whatsapp - it only recognises data on internal. and it takes up anywhere between 1 GB to 1.5 GB...even if i mnage to shiftthe app to the ntfs partition through link2sd which i already have, i cant keep the data in ext since itdoesnt recognise
TacTieTee said:
my device is already rooted guys. trying to keep data in ext but app does not recognise tht data. for example my whatsapp - it only recognises data on internal. and it takes up anywhere between 1 GB to 1.5 GB...even if i mnage to shiftthe app to the ntfs partition through link2sd which i already have, i cant keep the data in ext since itdoesnt recognise
Click to expand...
Click to collapse
That needs modification at system level. As I said it is in the design of the OS.
Best bet for now is to wait for Custom ROMs.
Sent from my XT1022 using Tapatalk
TacTieTee said:
my device is already rooted guys. trying to keep data in ext but app does not recognise tht data. for example my whatsapp - it only recognises data on internal. and it takes up anywhere between 1 GB to 1.5 GB...even if i mnage to shiftthe app to the ntfs partition through link2sd which i already have, i cant keep the data in ext since itdoesnt recognise
Click to expand...
Click to collapse
Why was i quoted in this reply?
Sorry I thought u were guiding me to root guides since the poster above yours told me to have my come rooted.
neo.ank said:
Like to add an input regarding Q11
For Indian customers, The warranty is void if you unlock/root your device. Maybe OP can add this too.
Click to expand...
Click to collapse
deej_roamer said:
There are confirmed rooting methods here and here!
Click to expand...
Click to collapse
Added to the OP
Hope it helps
For Q15, you may use this:
http://forum.xda-developers.com/showpost.php?p=52804779&postcount=12

FireTV 2 (sloane) Recovery [v6] - 3.0.0-5

It's finally here! Recovery for the Fire TV 2. This is based off of TWRP and the way versions will work is I will increment the last digit in the version as I make updates. So 3.0.0-1 is my first release based off of 3.0.0. The downloads will be numbered starting at v1, and at the bottom of the post it will explain what is contained within each version.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV, but doing stupid things with it might.
Installing this requires root. If you are not rooted, please see my FireTV 2 Recovery Installer page.
Installation
You can copy the files to /sdcard, a USB storage device, or an sdcard. I will be using /sdcard in the instructions, but you can replace it with /storage/usbotg for USB or /storage/sdcard1 for an sdcard.
Copy the zip file to your destination.
Connect adb
Code:
adb connect IPADDRESS
Open an adb shell
Code:
adb shell
Run the zip file (replace vX with the actual version you downloaded). This will automatically run su, so make sure to accept the prompt if necessary.
Code:
sh /sdcard/firetv2_recovery_vX.zip
Reboot
Upgrade
You may repeat this to upgrade to a newer version, or you can install an updated pre-rooted rom, as I will be uploading new versions of those with every version of recovery.
Notes
This includes bootmenu. For everyone that loved the old FireTV 1 bootmenu with Comic Sans, I'm sorry to disappoint you, but the Comic Sans is gone. When the FireTV boots, it will present you with the bootmenu where you can leave it alone and it will boot normally or you can select recovery and it will boot in to recovery. You do need a USB keyboard to interact with the bootmenu. To force it to boot in to Recovery, you can create a file /cache/bootmenu_recovery.
DHCP for Ethernet is enabled, and if there is enough demand I may add in wifi at some point. The IP address should show up in the top left corner.
USB storage, USB keyboard/mice, and sdcards should all work. Hotplugging works, so you should be able to plug and unplug devices as needed.
You can use a USB keyboard, mouse, or the mouse emulator to interact with it. To use a keyboard, you can use the arrow keys to move the cursor and the enter key to select buttons. Sliders don't require sliding, so you can just hit enter/click on them. To use the mouse emulator, use adb shell and then run the program mouse and follow the instructions.
ROMs
Recovery must be included in all ROMs. If you want to develop a ROM, please contact me about including recovery in it.
Kernels
The bootloader is locked and you cannot flash kernels. If you do attempt to flash a kernel, you will brick it.
Installing zips
You can push zips to /sdcard, put it on a USB storage, put it on an sdcard, or use adb sideload. Do note you need adb version 1.0.32 to use adb sideload.
Stuck in a loop?
If you cannot boot normally and keep going back to the bootmenu, wipe Cache from Wipe -> Advanced Wipe.
If that doesn't work, ensure Cache is not mounted from in the 'Mount' menu and run this from an adb shell:
Code:
mke2fs /dev/block/platform/mtk-msdc.0/by-name/cache
Source Code
You can find the source code here:
https://github.com/androidrbox/sloane-2ndinit
https://github.com/androidrbox/android_bootable_recovery
WARNINGS
It is extremely important you never reboot after a failure. This will most likely lead to a brick. If recovery is hung, you can use adb shell to run
Code:
killall recovery
to restart it
It is also extremely important to never reboot after wiping /system.
If you wind up bricking, you must use the Unbrick Image to unbrick.
Finally, thanks to everyone who has donated to me and those that helped to get me my FireTV 2.
Changelog and Downloads:
April 8, 2016 - v6 (md5sum: 79c1a3efbac86618fa2cdbb4901fbd77)
This should prevent auto flashing amazon updates.
This includes 2ndinit version dee776 and TWRP version 3.0.0-5.
February 14, 2016 - v5 (md5sum: 16c957c86f1f61160e14a55819610707)
This should fix the problems certain keyboard were having in recovery.
This includes 2ndinit version dee776 and TWRP version 3.0.0-4.
February 12, 2016 - v4 (md5sum: 15c6d375607839cac4b186a2b68b8b0d)
This includes 2ndinit version 743aa4 and TWRP version 3.0.0-3.
These are just changes related to the unbricking image. No other functional changes.
February 8, 2016 - v3 (md5sum: b39a4dbe0c19080a97f602f37fda63ec)
This includes an updated script. You can now just run the zip instead of needing the zip and the script.
This includes TWRP 3.0.0-2.
Added a reboot recovery option in addition to reboot system. Now reboot system will reboot straight in to Android. Reboot recovery will reboot to the bootmenu.
Fixed restoring backups.
This includes the same version of 2ndinit.
February 7, 2016 - v2 (md5sum: 762621104d158d7ce4010bea725f7181)
This includes an automated script.
This has the same versions of 2ndinit and recovery as v1.
February 6, 2016 - v1 (md5sum: 7be673dd24489080eacdd0ad00feda51)
This comes with 2ndinit version fe3362 and recovery version 3.0.0-1
Awesome work!
Will try immediately! Thanks for posting this on weekend
Thankyou Rbox, i just saw this & its put a smile on my face. Just one question do you need to reblock the updates after recovery & root have been installed? Thanks
deanr1977 said:
Thankyou Rbox, i just saw this & its put a smile on my face. Just one question do you need to reblock the updates after recovery & root have been installed? Thanks
Click to expand...
Click to collapse
As long as you don't wipe data, updates remain blocked.
rbox said:
As long as you don't wipe data, updates remain blocked.
Click to expand...
Click to collapse
I downloaded both the zips from the Github, im already rooted on the previously rooted software & updates are blocked, im not sure if to wait for AFTV News to do a guide or not, im clued up but not to ADB or Terminal savey so i gonna look at the readme & see if i should try it tonight? I rooted with the video guide before & it was a breeze, i know it sounds easy but want to do it right. Can you give me a little more info on connecting the ADB or Terminal please if you arnt busy?
deanr1977 said:
I downloaded both the zips from the Github, im already rooted on the previously rooted software & updates are blocked, im not sure if to wait for AFTV News to do a guide or not, im clued up but not to ADB or Terminal savey so i gonna look at the readme & see if i should try it tonight? I rooted with the video guide before & it was a breeze, i know it sounds easy but want to do it right. Can you give me a little more info on connecting the ADB or Terminal please if you arnt busy?
Click to expand...
Click to collapse
If you don't want to deal with adb, use the installer.
rbox said:
If you don't want to deal with adb, use the installer.
Click to expand...
Click to collapse
Thanks mate, looking at this now. Will it delete any data on the system? Kodi, Amazon apps or External Sd card? Thanks in advance
deanr1977 said:
Thanks mate, looking at this now. Will it delete any data on the system? Kodi, Amazon apps or External Sd card? Thanks in advance
Click to expand...
Click to collapse
Installing recovery and roms does nothing to data.
rbox said:
It's finally here! Recovery for the Fire TV 2. This is based off of TWRP and the way versions will work is I will increment the last digit in the version as I make updates. So 3.0.0-1 is my first release based off of 3.0.0. The downloads will be numbered starting at v1, and at the bottom of the post it will explain what is contained within each version.
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV, but doing stupid things with it might.
Installing this requires root. If you are not rooted, please see my FireTV 2 Recovery Installer page.
Installation
Copy the contents of the zip to /sdcard on your FireTV.
Remount /system as read-write
Code:
mount -o remount,rw /system
Make the /system/recovery directory
Code:
mkdir /system/recovery
Copy 2ndinitstub
Code:
cp /sdcard/2ndinitstub /system/bin/ext4_resize
Copy 2ndinit
Code:
cp /sdcard/2ndinit /system/recovery/
Copy the recovery ramdisk
Code:
cp /sdcard/ramdisk-recovery.cpio /system/recovery/
Remount /system as read-only
Code:
mount -o remount,ro /system
Upgrade
You may repeat this to upgrade, but it is easier to just install a new pre-rooted rom. Every update for recovery I will make a new rom.
Notes
This includes bootmenu. For everyone that loved the old FireTV 1 bootmenu with Comic Sans, I'm sorry to disappoint you, but the Comic Sans is gone. When the FireTV boots, it will present you with the bootmenu where you can leave it alone and it will boot normally or you can select recovery and it will boot in to recovery. You do need a USB keyboard to interact with the bootmenu. To force it to boot in to Recovery, you can create a file /cache/bootmenu_recovery.
DHCP for Ethernet is enabled, and if there is enough demand I may add in wifi at some point. The IP address should show up in the top left corner.
USB storage, USB keyboard/mice, and sdcards should all work. Hotplugging works, so you should be able to plug and unplug devices as needed.
You can use a USB keyboard, mouse, or the mouse emulator to interact with it. To use a keyboard, you can use the arrow keys to move the cursor and the enter key to select buttons. Sliders don't require sliding, so you can just hit enter/click on them. To use the mouse emulator, use adb shell and then run the program mouse and follow the instructions.
ROMs
Recovery must be included in all ROMs. If you want to develop a ROM, please contact me about including recovery in it.
Kernels
The bootloader is locked and you cannot flash kernels. If you do attempt to flash a kernel, you will brick it.
Installing zips
You can push zips to /sdcard, put it on a USB storage, put it on an sdcard, or use adb sideload. Do note you need adb version 1.0.32 to use adb sideload.
Source Code
You can find the source code here:
https://github.com/androidrbox/sloane-2ndinit
https://github.com/androidrbox/android_bootable_recovery
Finally, thanks to everyone who has donated to me and those that helped to get me my FireTV 2.
Changelog and Downloads:
Februrary 6, 2016 - v1 (md5sum: 7be673dd24489080eacdd0ad00feda51)
This comes with 2ndinit version fe3362 and recovery version 3.0.0-1
Click to expand...
Click to collapse
the commands are entered through adb correct......Also, once recovery is installed can I flash either of your pre-rooted roms or do I have to flash the version I'm currently on....i.e. if I'm on 5.0.4 I can only flash 5.0.4
thanks again for your great work!
dk1keith said:
the commands are entered through adb correct......Also, once recovery is installed can I flash either of your pre-rooted roms or do I have to flash the version I'm currently on....i.e. if I'm on 5.0.4 I can only flash 5.0.4
thanks again for your great work!
Click to expand...
Click to collapse
Yes adb shell. You can flash either version.
rbox said:
Yes adb shell. You can flash either version.
Click to expand...
Click to collapse
Awesome thanks rbox
Not working for me. everything is copied over and after reboot there is no menu. Amazon white logo for 5 seconds, than the colored logo and system is booted in less than 15 seconds.
aboshi said:
Not working for me. everything is copied over and after reboot there is no menu. Amazon white logo for 5 seconds, than the colored logo and system is booted in less than 15 seconds.
Click to expand...
Click to collapse
Same here. No boot menu. Reboot to recovery brings up the stock recovery as well.
dk1keith said:
Awesome thanks rbox
Click to expand...
Click to collapse
first command: mount -o remount,rw /system
in adb shell returns a mountermission denied
aboshi said:
Not working for me. everything is copied over and after reboot there is no menu. Amazon white logo for 5 seconds, than the colored logo and system is booted in less than 15 seconds.
Click to expand...
Click to collapse
retyre said:
Same here. No boot menu. Reboot to recovery brings up the stock recovery as well.
Click to expand...
Click to collapse
Both of you please run:
Code:
ls -lZ /system/bin/ext4_resize /system/recovery
dk1keith said:
first command: mount -o remount,rw /system
in adb shell returns a mountermission denied
Click to expand...
Click to collapse
You need to be root...
rbox said:
Both of you please run:
Code:
ls -lZ /system/bin/ext4_resize /system/recovery
You need to be root...
Click to expand...
Click to collapse
you mean by typing su?
dk1keith said:
you mean by typing su?
Click to expand...
Click to collapse
Yes, by typing su.
Code:
-rwxr-xr-x root shell u:object_r:system_file:s0 ext4_resize
-rw------- root root u:object_r:system_file:s0 2ndinit
-rw------- root root u:object_r:system_file:s0 ramdisk-recovery.cpio
aboshi said:
Code:
-rwxr-xr-x root shell u:object_r:system_file:s0 ext4_resize
-rw------- root root u:object_r:system_file:s0 2ndinit
-rw------- root root u:object_r:system_file:s0 ramdisk-recovery.cpio
Click to expand...
Click to collapse
Hrm... can you run
Code:
ls -l /system/bin/ext4_resize /system/recovery
also?

Categories

Resources