not able to install lineage-14.1-20170719-nightly-i9100-signed.zip - LineageOS Questions & Answers

samsung i9100
lineage-14.1-20170719-nightly-i9100-signed.zip
replicant 6.0
linux computer
android-tools-adb 4.2.2
heimdall-flash 1.4.0
After testing replicant 6.0, I wanted to test lineage-14.1-20170719-nightly-i9100-signed.zip. There is no stable image for samsung i9100?
I flashed twrp-3.1.1-0-i9100.img on the phone. Volume up + home + poweron makes the phone boot the 3.1.1 boot screen.
Then what?
adb push does not work. It does not get the lineage-14.1-20170719-nightly-i9100-signed.zip file moved to the phone. Error message is failed to copy is a directory.
I then moved the lineage-14.1-20170719-nightly-i9100-signed.zip to a micro sdcard. Placing the sdcard in the phone, if I select install on the phone's 3.1.1 boot screen, I cannot find the micro sdcard. Thank you.

I had the same problem with i9100 and twrp-3.1.1.
Twrp-3.1.0 worked for me.

thmmht said:
samsung i9100, lineage-14.1-20170719-nightly-i9100-signed.zip, replicant 6.0, linux computer, android-tools-adb 4.2.2
heimdall-flash 1.4.0. After testing replicant 6.0, I wanted to test lineage-14.1-20170719-nightly-i9100-signed.zip. There is no stable image for samsung i9100? I flashed twrp-3.1.1-0-i9100.img on the phone. Volume up + home + poweron makes the phone boot the 3.1.1 boot screen. Then what?
adb push does not work. It does not get the lineage-14.1-20170719-nightly-i9100-signed.zip file moved to the phone. Error message is failed to copy is a directory.
I then moved the lineage-14.1-20170719-nightly-i9100-signed.zip to a micro sdcard. Placing the sdcard in the phone, if I select install on the phone's 3.1.1 boot screen, I cannot find the micro sdcard. Thank you.
Click to expand...
Click to collapse
mariusz.b said:
I had the same problem with i9100 and twrp-3.1.1.
Twrp-3.1.0 worked for me.
Click to expand...
Click to collapse
This question should be posted on the following Official LineageOS thread:
[ROM][I9100][OFFICIAL][7.1.2] LineageOS 14.1 by rINanDO
Your more likely to receive an answer on that thread from other members who has the same device and Firmware.
I wish you the best of luck!
______________
PLEASE NOTE: I welcome any member to help with further valuable information/clarification for any of my posts.
×MY DEVELOPMENTS×
[APP][TOOL][4.2+]The SELinux Toggler
[ZIP][TOOL][AIO]BusyBox Stericson Binary Installer v1.26.2 {BB/TB Auto-Symlink}
×IN DEVELOPMENT×
[APP][TOOL][4.2+][OFFICIAL]The SELinux Switch
Will Supersede "The SELinux Toggler"
×IDEAS FOR DEVELOPMENT×
[APP][UNOFFICIAL][4.2+]XDA Forum {Classic}
[APP][UNOFFICIAL][4.2+]XDA Reader {Classic}

mariusz.b said:
I had the same problem with i9100 and twrp-3.1.1.
Twrp-3.1.0 worked for me.
Click to expand...
Click to collapse
Thanks.
I tested twrp-3.1.0-0-i9100.img.
It did not work. Flashing shows no error messages. But when I restart the phone, it does not open the recovery
mode screen.

thmmht said:
Thanks.
I tested twrp-3.1.0-0-i9100.img.
It did not work. Flashing shows no error messages. But when I restart the phone, it does not open the recovery
mode screen.
Click to expand...
Click to collapse
The TWRP ".img" file is for flashing (updating) within an already installed TWRP Recovery.
The ".img.tar" file is for flashing via ODIN.
______________
PLEASE NOTE: I welcome any member to help with further valuable information/clarification for any of my posts.

Related

[RECOVERY]Samsung Galaxy W i8150 RZRecovery

I'm very happy to announce, that a developer raidzero from rootzwiki forum, has made us a fully working recovery for Samsung Galaxy w i8150!
You can download it from here:
DOWNLOAD
TEMPORARY LINK .... USE THIS IF FIRST ONE DOESN'T WORK
THANKS TO andynroid FOR PROVIDING LINKS!
Flashing recovery is very simple, all you need is root access on your phone, and adb on computer. You just copy downloaded recovery on internal sdcard. Then disconect phone from copmuter. Make sure that USB debugging is on. Now connect it again but don't connect phone memory (computer shouldn't see sdcard and internal memory in Windows explorer), open command prompt and got directory where adb is installed, now enter this:
Code:
adb shell
$su
#dd if=/sdcard/RZR-2.1.4-ancora-rec.img of=/dev/block/mmcblk0p13
This is all. Now turn off phone and turnd it on like this: hold Volume Up + Home + Power button, when Samsung sign appears relese power button but still hold other two, until recovery is loaded. Bamm you are in, and ready to flash something, or backup ! Expolre the recovery, it has a lot of options, you can even choose what color of menus you want .
I would like to thanks raidzero again for all his effort he made! And also big thanks to arco68,for much need informations he provided!
We can now expect, that when developing his recovery and adding new goodies, this recovery will follow others!
great news!! Thanks for your effort!
Has anyone had a chance to test the Recovery?
Will this work on the Samsung Exhibit II?
thanks mate.downloading now. just in case it needs to be recovered. after this we would see custom roms developed by our developers here..
klingel_One said:
great news!! Thanks for your effort!
Has anyone had a chance to test the Recovery?
Click to expand...
Click to collapse
I've tested it and it works
radgoos said:
Will this work on the Samsung Exhibit II?
Click to expand...
Click to collapse
I wouldn't bet that this will work on Exibith II cause every phone has different partitions.
after giving me the command you said to me reacts to: permission denied.. Whi?
lipanz said:
thanks mate.downloading now. just in case it needs to be recovered. after this we would see custom roms developed by our developers here..
Click to expand...
Click to collapse
Definitely...BTW can anyone adv us the rooting method Odin or....
can you show me a screen when you give the command adb?
when I try to restart the device in recovery restarts continuously and never give me the recovery menu
qzem said:
I'm very happy to announce, that a developer raidzero from rootzwiki forum, has made us a fully working recovery for Samsung Galaxy w i8150!
You can download it from here:
www.rzdroid.com/ftp/recovery/gingerbread/2.1.4/RZR-2.1.4-ancora-rec.img
Flashing recovery is very simple, all you need is root access on your phone, and adb on computer. You just copy downloaded recovery on internal sdcard. Then disconect phone from copmuter. Make sure that USB debugging is on. Now connect it again but don't connect phone memory (computer shouldn't see sdcard and internal memory in Windows explorer), open command prompt and got directory where adb is installed, now enter this:
Code:
adb shell
$su
#dd if=/sdcard/RZR-2.1.4-ancora-rec.img of=/dev/block/mmcblk0p13
This is all. Now turn off phone and turnd it on like this: hold Volume Up + Home + Power button, when Samsung sign appears relese power button but still hold other two, until recovery is loaded. Bamm you are in, and ready to flash something, or backup ! Expolre the recovery, it has a lot of options, you can even choose what color of menus you want .
I would like to thanks raidzero again for all his effort he made! And also big thanks to arco68,for much need informations he provided!
We can now expect, that when developing his recovery and adding new goodies, this recovery will follow others!
Click to expand...
Click to collapse
Thanks again, will try this ASAP, just a few questions:
Is /dev/block/mmcblk0p13 the Recovery partition??
Is it been overwritten by the dd if.......of??
Should the original stock recovery?? be backed-up/saved first??
Is there an MD5 or anything to check file integrity:
This could be used on the Device: Android File Verifier
Can the procedure be done using Terminal Emulator on the phone?
Do I need to have stock ROM for it to work?
snake873 said:
after giving me the command you said to me reacts to: permission denied.. Whi?
Click to expand...
Click to collapse
There are two possible reasons for this either you didn't run su command first, or you don't have rooted phone.
irishpancake said:
Thanks again, will try this ASAP, just a few questions:
Is /dev/block/mmcblk0p13 the Recovery partition??
Is it been overwritten by the dd if.......of??
Should the original stock recovery?? be backed-up/saved first??
Is there an MD5 or anything to check file integrity:
This could be used on the Device: Android File Verifier
Can the procedure be done using Terminal Emulator on the phone?
Click to expand...
Click to collapse
1. Yes /dev/block/mmcblk0p13 is recovery partition
2. It is gonna be overwritten with costum one.
3. You can back it up that you reverse dd command. Or I can upload original recovery.
4. There isn't MD5 cause noone made it , you only need MD5 file if you would like to flash this via Odin.
nakTT said:
Do I need to have stock ROM for it to work?
Click to expand...
Click to collapse
Do you know any custom rom for our phone ? But no it is not rom related.
snake873 said:
can you show me a screen when you give the command adb?
when I try to restart the device in recovery restarts continuously and never give me the recovery menu
Click to expand...
Click to collapse
What screen? From computer or phone? Your phone need to be turned on and booted in android when running dd command.
qzem said:
There are two possible reasons for this either you didn't run su command first, or you don't have rooted phone.
1. Yes /dev/block/mmcblk0p13 is recovery partition
2. It is gonna be overwritten with costum one.
3. You can back it up that you reverse dd command. Or I can upload original recovery.
4. There isn't MD5 cause noone made it , you only need MD5 file if you would like to flash this via Odin.
Do you know any custom rom for our phone ? But no it is not rom related.
What screen? From computer or phone? Your phone need to be turned on and booted in android when running dd command.
Click to expand...
Click to collapse
From computer
---------- Post added at 12:09 PM ---------- Previous post was at 11:41 AM ----------
ahahaha ok ok I did thank you very much for your patience
qzem......top marks for your persistence
qzem said:
There are two possible reasons for this either you didn't run su command first, or you don't have rooted phone.
1. Yes /dev/block/mmcblk0p13 is recovery partition
2. It is gonna be overwritten with costum one.
3. You can back it up that you reverse dd command. Or I can upload original recovery.
4. There isn't MD5 cause noone made it , you only need MD5 file if you would like to flash this via Odin.
Click to expand...
Click to collapse
Thanks, gotta learn ODIN first,
btw, thanks for the ODIN d/l........installed it, but still unsure how to proceed???
I have latest Kies installed on my laptop, any reason why you do not use it?? It appears to allow back-ups and restores, also new firmware d/l.
As I am new to Samsung, and also ODIN, but does using ODIN have advantages over Kies, and is it safer to upgrade new f/w with ODIN or Kies, do you lose root, or anything else??
BTW, on the MD5 thing, for the RZR-2.1.4-ancora-rec.img
I used MD5 Checksum Tool from http://www.novirusthanks.org/product/md5-checksum-tool/
to generate the MD5.
File: RZR-2.1.4-ancora-rec.img
Size: 5230592 bytes
Publisher: Unknown
Checksum (MD5): 3b9cc641aa898910b5bad911bd38f675
*File generated by MD5 Checksum Tool*
http://www.novirusthanks.org
Click to expand...
Click to collapse
I just think it is good security practice to check file integrity before applying on your device, as many things can happen, like data corruption, while transferring file from download on Laptop to SD card, and best to check file on device SD or Internal Storage with AFV against MD5 generated at source.........
which I did not check at source, but I am just illustrating for example!!
[BTW, lots of MD5's on rzdroid.com recovery ftp site, here, but not sure of our .img file
The above MD5 is what I got from the d/l file
Thanks again, I saw your stuff with raidzero on rootzwiki.........
top marks for your persistence, and a good result for all i8150 owners.
irishpancake said:
Thanks, gotta learn ODIN first,
btw, thanks for the ODIN d/l........installed it, but still unsure how to proceed???
I have latest Kies installed on my laptop, any reason why you do not use it?? It appears to allow back-ups and restores, also new firmware d/l.
As I am new to Samsung, and also ODIN, but does using ODIN have advantages over Kies, and is it safer to upgrade new f/w with ODIN or Kies, do you lose root, or anything else??
BTW, on the MD5 thing, for the RZR-2.1.4-ancora-rec.img
I used MD5 Checksum Tool from http://www.novirusthanks.org/product/md5-checksum-tool/
to generate the MD5.
I just think it is good security practice to check file integrity before applying on your device, as many things can happen, like data corruption, while transferring file from download on Laptop to SD card, and best to check file on device SD or Internal Storage with AFV against MD5 generated at source.........
which I did not check at source, but I am just illustrating for example!!
[BTW, lots of MD5's on rzdroid.com recovery ftp site, here, but not sure of our .img file
The above MD5 is what I got from the d/l file
Thanks again, I saw your stuff with raidzero on rootzwiki.........
top marks for your persistence, and a good result for all i8150 owners.
Click to expand...
Click to collapse
Well I really don't know that is better to use Kies or Odin. If you want official and (what is supposed to be tested) firmware, tha you better use Kies (but well even with kies your phone could get bricked, I've learned that from one user here ). If you want to flash latest firmware, which sometimes is not availible on all the countries, and you can't get it from Kies fast enaught, than I suggest odin is the choice. I prefere Odin, cause I don't like official stuff .
To use Odin is very simple. You need to turn on phone with Volume Down + Home + Power. When you are prompt (on hte phone),wether to conutioue od cancle, you connect phone and computer with USB cable, and choose contuinu, now you are in download mode. Then all you have to do, to choos proper .ops file (button OPS) in odin, an proper firmware (usually you choos that under One Package button, if you have one package in tar.md5), then you wait for chekcking md5. When is checked you just click Start, and wait for stuff to happen.
Don't forget that there is a possabiltiy that something might go wrong with flashing, but it is not that big one. I suggest, that you first made full nandorid backup with recovery, if something goes wrong, you can boot you phone in recovery and restore it totaly. And one more suggestin when flashing, do it with latop(if possible), so that you have battery and power cable plugged in laptop, if electricyty goes out, that you still have battery to run laptop.
And thanks for the support you guys are showing to me, since I'm not a developer. I try really hard, to get people that are willing to help us developing better roms for our phone !
qzem said:
There are two possible reasons for this either you
Do you know any custom rom for our phone ? But no it is not rom related.
Click to expand...
Click to collapse
Spot on. I just need to know if it is ROM related (that I need a ROM file on my PC).
Thanks for the reply.
Hey there, just a noob question:
Where are adb drivers installed? I'm working under Windows 7.
I tried to google this and ended up here /developer.android.com/sdk/index.html
and downloaded the first two files, but I'm unsure what to do now. Thanks in advance!
Hey qzem,
Am I right, that the adb driver should be installed, when i first installed Kies?
Is your Guide How-To Install the recovery also working on my mac? I think so, or am I wrong?
Perhaps you already figured by now, I'm new to Android!
There is one more thing i can't seem to figure out:
In foreseeable future, there are hopefully some nice custom roms for the Galaxy W. Do I have to install recovery everytime i flash a new Rom? Or is it like a bios, that has nothing to do with the actual Android System?
Thanks for your help in advance
fender90 said:
Hey there, just a noob question:
Where are adb drivers installed? I'm working under Windows 7.
I tried to google this and ended up here /developer.android.com/sdk/index.html
and downloaded the first two files, but I'm unsure what to do now. Thanks in advance!
Click to expand...
Click to collapse
For adb, you need to download Android SDK from here. Download zip file and extract it somwhere. Than go in folder where you have extract it and run SDK Manager, from there you will install adb rivers and everything else. When you are done (it could take a while, to download and install everything), open Command promnt and follow the instrucions I've wrote in first post.
klingel_One said:
Hey qzem,
Am I right, that the adb driver should be installed, when i first installed Kies?
Is your Guide How-To Install the recovery also working on my mac? I think so, or am I wrong?
Perhaps you already figured by now, I'm new to Android!
There is one more thing i can't seem to figure out:
In foreseeable future, there are hopefully some nice custom roms for the Galaxy W. Do I have to install recovery everytime i flash a new Rom? Or is it like a bios, that has nothing to do with the actual Android System?
Thanks for your help in advance
Click to expand...
Click to collapse
The same goes for mac users, there is also Android SDK for mac. You can install Kies before this, but you need both because kies includes drivers for this phone exactly. As far as recoverey goes, if it is not included in ROM, which you flash, I think you'll need to install it again. I hope that developers will include recovery in their roms.
Thanks so far qzem,
It seems like theres someone in your Cyanogenom-Forum-Post qzem, who is trying and willing to help making a custom rom. But he seeks for som guidance!
Perhaps someone with experience like, arco can take him under his wings!
Hi there,
i would like to thank you. Everything works like a charm.
Did the flash, tried the recovery.. and uaaaahhhh....
...i forgot to backup the original recovery!
can someone please, please upload it to somewhere??
thx.
Zetup-EXe

Motorola Defy Mini XT320 all-in-one script

Motorola Defy Mini XT320/XT321 all-in-one script/utility
I've ported mattlgroff's DROIDRAZR all-in-one Script to the Motorola Defy Mini XT320/XT321. This will make life easier and it will do it for you.
Make sure you have fastboot mode if not please refer to this guide for fastboot but there is a fastboot checker in option 6 but it won't install fastboot for you.
Link: http://forum.xda-developers.com/showpost.php?p=36199694&postcount=3
Options available:
1. Root your Motorola Defy Mini XT320/XT321
2. Install 2nd-init/TWRP Recovery
3. Overclock installation
4. Unroot Device
5. Wipe Data/Factory Reset
6. Fastboot checker.
7. Exit Utility
Instructions:
NEW PACKAGE & instructions
1. Download the EXE file at http://www.mediafire.com/?c81fnrtrki65e9i
2. Double click on the exe.
3. Choose an option by entering a number from 1 to 7
OLD PACKAGE & instructions
1. Download package at [REMOVED OLD LINK]
Please Download the fixed package at http://www.mediafire.com/?krxtemrthsz5ier
EXE Version: http://www.mediafire.com/?0kwmx4whjj1ua8c
2. Extract the zip file making sure all the files are in the same place.
3. Click on the batch file named 'DefyMiniUtility.bat'
4. Choose an option by entering a number from 1 to 7.
Credits to:
- Bernd.Defy for overclock module and Guitwo2 for init.d script
- Guitwo2 and jkkk88 for TWRP and aweosomeabhjeet for 2nd-init
- DoOMLoRD for unroot script
- Mattlgroff for the original DROID RAZR all-in-one script
If anyone knows if I missed a member for the credits, please PM me. Thanks
Make sure press thanks if it works
Guys please don't repost it as your own work, otherwise I'll report it and you will get banned from XDA.
NOTE: If you have previously used the old EXE to install TWRP then please remove the old folders by using these instructions using cmd before using updated exe to install TWRP;
1.
Code:
adb shell
2.
Code:
su
3.
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock11 /system
4.
Code:
rm -R /system/bootmenu
Then use the updated exe to install TWRP.
NOTE: If you don't like TWRP, you can download Guitwo2's Permanent CWM at http://forum.xda-developers.com/attachment.php?attachmentid=1875373&d=1365682716
Temporary CWM Recovery: http://forum.xda-developers.com/attachment.php?attachmentid=1875299&d=1365680458
2nd-init does NOT work in CWM Recovery
Thanks to @Guitwo2 for CWM Recovery.
Instructions on how to install Permanent CWM Recovery:
1. Make sure stericson-busybox is installed
2. Put XT320_bootmenuV2.zip in the root of your sdcard
3. Reboot into fastboot mode by typing this command in cmd:
Code:
adb reboot bootloader
4. Then type this command in cmd:
Code:
fastboot boot recovery.img
5. Then use volume keys to navigate and power button to select option. Select install zip from sdcard, then select XT320_bootmenuV2.zip and select yes to install the zip file
6. Then reboot device by selecting reboot device now.
CWM 6 has a bug where it asks you to 'disable recovery flash' when you select reboot system now make sure you select NO or you will soft brick your device.
Changelog:
-v2 No need to mount /sdcard in CWM Recovery. Fixed TWRP installation issues.
-v2.0.1 Released an .exe version of script, to simplify installation
-v2.0.1.1 Fixed bootmenu.zip
This can install a custom recovery?
This can install a custom recovery?
Thank you
The root process worked for me. Now i can install link2sd and set up a swap partition.
I cant install TWRP and i think the reason is that the bat was having some problem to send that bootmenu.tar file to my sd card. I tried to send that file myself before starting the entire process and it didnt worked.
I took a picture of the error i'm getting . Thank you again, i was really mad about that low internal space xD
same problem... someone can fix it? please
fca.sjc said:
The root process worked for me. Now i can install link2sd and set up a swap partition.
I cant install TWRP and i think the reason is that the bat was having some problem to send that bootmenu.tar file to my sd card. I tried to send that file myself before starting the entire process and it didnt worked.
I took a picture of the error i'm getting . Thank you again, i was really mad about that low internal space xD
Click to expand...
Click to collapse
sfoot13 said:
same problem... someone can fix it? please
Click to expand...
Click to collapse
Ok, I've made a fixed script here. The error was that the sdcard is a directory so it will refuse to push files into it.
Here's the updated script below. Just put the .bat file in the same place as the other files.
Thanks
rootdefyxt320 said:
Ok, I've made a fixed script here. The error was that the sdcard is a directory so it will refuse to push files into it.
Here's the updated script below. Just put the .bat file in the same place as the other files.
Click to expand...
Click to collapse
Ty for the quickly answer.
Btw, my gsm network wasnt working after the root process. If the same thing happens to someone else, just do a master reset and it will work again.
pull command is working now
That sdcard copy part is working now. The TWRP process is still not working for me. I tried to do myself the commands using the adb interface and when i use the command to intall the tar, i got the message 'tar: no space left on device" . I hope you can help me with that and i'm sorry about all this questions xD .
fca.sjc said:
That sdcard copy part is working now. The TWRP process is still not working for me. I tried to do myself the commands using the adb interface and when i use the command to intall the tar, i got the message 'tar: no space left on device" . I hope you can help me with that and i'm sorry about all this questions xD .
Click to expand...
Click to collapse
You must have more than 5MB free in your /system partition. Please move your apps to the /flex partition or delete the useless apps in /system.
rootdefyxt320 said:
You must have more than 5MB free in your /system partition. Please move your apps to the /flex partition or delete the useless apps in /system.
Click to expand...
Click to collapse
Thank u so much to everyone who make it possible xD
(can i do now a overclock to 720 without problems?)
sfoot13 said:
Thank u so much to everyone who make it possible xD
(can i do now a overclock to 720 without problems?)
Click to expand...
Click to collapse
Yes but it sometimes gets unstable so you should overclock to 700MHz which is the highest I got without reboots. pll2_l_val=73 gives you 700MHz.
rootdefyxt320 said:
Yes but it sometimes gets unstable so you should overclock to 700MHz which is the highest I got without reboots. pll2_l_val=73 gives you 700MHz.
Click to expand...
Click to collapse
Thank u so much and TWRP doesn't work xD i have 8.5 mb free on system but it can't create the folders on bootmenu
sfoot13 said:
Thank u so much and TWRP doesn't work xD i have 8.5 mb free on system but it can't create the folders on bootmenu
Click to expand...
Click to collapse
I've released an .exe version of my script. This should work now .
Link: http://www.mediafire.com/?0kwmx4whjj1ua8c
Thank u bro and sorry but i can't overclock it to 700 =/
i installed TWRP but it doesn't work and when i turn on my mobile it freezes on home screen :/ is a mess.... it's possible install it via recovery (temportal CWM)?
OFF TOPIC.
Congrats on your well deserved mention on the portal.
sfoot13 said:
i installed TWRP but it doesn't work and when i turn on my mobile it freezes on home screen :/ is a mess.... it's possible install it via recovery (temportal CWM)?
Click to expand...
Click to collapse
It worked for others but in your situation the only thing I can advise is to do a data wipe and relfash SBF file. Just go to Guitwo2's there to install permanent CWM.
Link: http://forum.xda-developers.com/showthread.php?t=2229233
rootdefyxt320 said:
It worked for others but in your situation the only thing I can advise is to do a data wipe and relfash SBF file. Just go to Guitwo2's there to install permanent CWM.
Link: http://forum.xda-developers.com/showthread.php?t=2229233
Click to expand...
Click to collapse
:good: Working! Thank u so much, now i have CWM working on my defy mini, i'm really thankful, thanks again
Hi, it's me again... i have a new trouble
i installed the xt320_bootmenu.zip (from this thread http://forum.xda-developers.com/showthread.php?t=2229233) the first time that i rebooted works fine, but the on the second reboot it doesn't work, then i went to data to check if test.log was there and here's the problem... no test.log...
init.d was working fine until that i did it, i guess that my phone have troubles making work init.d
some solution for this annoying guy? thanks in advance!
sfoot13 said:
Hi, it's me again... i have a new trouble
i installed the xt320_bootmenu.zip (from this thread http://forum.xda-developers.com/showthread.php?t=2229233) the first time that i rebooted works fine, but the on the second reboot it doesn't work, then i went to data to check if test.log was there and here's the problem... no test.log...
init.d was working fine until that i did it, i guess that my phone have troubles making work init.d
some solution for this annoying guy? thanks in advance!
Click to expand...
Click to collapse
Looks like 97bootmenu deleted itself, please reinstall the CWM zip again and it should work.

[RECOVERY] [golden] TWRP 2.8.1.0 for S3 Mini (I8190)

Hello.
I built Omnirom from the sources and with this comes TWRP - version 2.8.1.0
The build is from 07. November 2014.
I removed support for true type fonts because it gave some build errors. (FYI: git revert 76ee903)
There is no support for f2fs.
How to install:
1) Boot up your phone, connect it to the PC and stay in the home screen
2) Copy recovery.img to the sdcard
3) Open the shell: adb shell
4) Get root: su
5) Compare the checksum of the file: md5sum /path/to/file
6) Flash it: dd if=/path/to/the/recovery/file of=/dev/block/mmcblk0p21
7) Reboot into recovery if you want
Thanks to: TWRP team, golden-guy
TWRP changelog: http://teamw.in/project/twrp2
P.S.: I cannot tell you if it works for the GT-i8190N/L version - test it and report back if you like.
P.S.S.: I will not provide a flashable zip file but if somebody wants to do this I am fine with that.
P.S.S.S.: Apply the mentioned steps at your own risk
Can you make a flashable one?
I will not provide a flashable zip file but if somebody wants to do this I am fine with that.
Can confirm that this works for the i8190N, but I'm getting a load of "Unable to mount" errors in the log when im trying to mount anything BUT the mtp is working for the external sd card. /system/ is formatted as f2fs and possibly others so I'm thinking thats the problem. Does this have f2fs support?
Thx for reporting back and good to hear that it works for the i8190N as well.
Unfortunately there is no support for f2fs - and this might be causing the problems you experience. I do not get errors when mounting ext4.
For TWRP with f2fs support you might to have a look here:
http://forum.xda-developers.com/showthread.php?t=2748327
thomson.aa said:
Thx for reporting back and good to hear that it works for the i8190N as well.
Unfortunately there is no support for f2fs - and this might be causing the problems you experience. I do not get errors when mounting ext4.
For TWRP with f2fs support you might to have a look here:
http://forum.xda-developers.com/showthread.php?t=2748327
Click to expand...
Click to collapse
Thanks for the link , I'll give it a whirl, yeah everything else seemed fine on you build so thanks for building it. Good luck.
MounirHero said:
Can you make a flashable one?
Click to expand...
Click to collapse
you can make it too.
just open any flashable recovery zip with winrar delete the img file and replace it with this and finish.
Flashable zip
Here's a flashable zip for those who are looking for it. I haven't flashed this yet myself (at work), it should work without any problems but ymmv. I'll test it later myself and report back. You should have another recovery ready to flash that you know to be working in case this doesn't work for you.
can you update your TWRP to v2.8.5.0?
http://teamw.in/project/twrp2
evildog1 said:
can you update your TWRP to v2.8.5.0?
http://teamw.in/project/twrp2
Click to expand...
Click to collapse
Please
party_boy-25 said:
Please
Click to expand...
Click to collapse
I do not own a S3 Mini anymore. Sry, but I will not provide an update.

Erased my Fire HD 8.9 - Can it be saved?

I was running Candy5 ROM ver. 2.5 and saw the thread for the 4.0 ROM. I downloaded it and Gapps and put it on the Fire HD. Rebooted into Recovery and into TWRP. That's when I did one of the most stupid things that I've ever done. I wanted a clean install from scratch. Unfortunately, I erased everything! When I realized what happened I rebooted and the screen goes through the two fire HD logos stopping at the last one. Is there ANYTHING I can do to get an operating Fire HD back up and running, Please!
rebelduke said:
I was running Candy5 ROM ver. 2.5 and saw the thread for the 4.0 ROM. I downloaded it and Gapps and put it on the Fire HD. Rebooted into Recovery and into TWRP. That's when I did one of the most stupid things that I've ever done. I wanted a clean install from scratch. Unfortunately, I erased everything! When I realized what happened I rebooted and the screen goes through the two fire HD logos stopping at the last one. Is there ANYTHING I can do to get an operating Fire HD back up and running, Please!
Click to expand...
Click to collapse
Try to reboot into TWRP (press + hold volume up as soon as you see the first logo, keep holding till you see the TWRP curtain). If you are successful, copy a ROM zip into the kindle's internal storage (gapps are optional, but I recommend you flash them along with your chosen ROM), flash it, reboot, and cross your fingers.
Thank you. I'm making some progress. Your instructions got me into TWRP (ver. 2.8.6). Next step is to get the PC to allow copying of the ROM file. TWRP does recognize that there is no operating system installed. Thanks again!
rebelduke said:
Thank you. I'm making some progress. Your instructions got me into TWRP (ver. 2.8.6). Next step is to get the PC to allow copying of the ROM file. TWRP does recognize that there is no operating system installed. Thanks again!
Click to expand...
Click to collapse
If you can't directly copy it, try adb sideload path/to/ROM.zip (enable sideloading in the advanced menu in TWRP first, or you'll get an error). Make sure you have adb drivers installed and working if your PC's running Windows. Good luck!
monster1612 said:
If you can't directly copy it, try adb sideload path/to/ROM.zip (enable sideloading in the advanced menu in TWRP first, or you'll get an error). Make sure you have adb drivers installed and working if your PC's running Windows. Good luck!
Click to expand...
Click to collapse
Adb sideload worked with the Candy5 4.0 ROM. The Gapps zip failed due to the file size being too great. I can tackle that after the ROM is installed. Another stupid question - any idea where the sideloaded ROM zip file would be internally? I explored using the TWRP file manager and all I have is the directory structure - no actual files. I probably looked in 50+ folders and they were all empty. I think there must be hundreds of directories and subdirectories. I found one folder named sideload thinking I had it but no luck. Worst case I can open every folder and hopefully find the ROM zip file.
rebelduke said:
Adb sideload worked with the Candy5 4.0 ROM. The Gapps zip failed due to the file size being too great. I can tackle that after the ROM is installed. Another stupid question - any idea where the sideloaded ROM zip file would be internally? I explored using the TWRP file manager and all I have is the directory structure - no actual files. I probably looked in 50+ folders and they were all empty. I think there must be hundreds of directories and subdirectories. I found one folder named sideload thinking I had it but no luck. Worst case I can open every folder and hopefully find the ROM zip file.
Click to expand...
Click to collapse
From the TWRP FAQ for the sideloading feature:
TWRP versions 2.8.2.0 and higher will stream the zip from your PC without storing it on your device. If you wish to store the zip on your device for later, you should not use sideload and instead use adb push or some other method to copy the zip to the device.
Click to expand...
Click to collapse
Older TWRP versions used to store the zip file in /sdcard/sideload, but I think versions 2.8.2.0 and higher use it as a temporary buffer and delete the zip after flashing. If you're able to get Android up and running, then you should be able to connect it to your PC, copy the ROM and gapps zips over to the kindle without using adb, and flash the gapps.
monster1612 said:
From the TWRP FAQ for the sideloading feature:
Older TWRP versions used to store the zip file in /sdcard/sideload, but I think versions 2.8.2.0 and higher use it as a temporary buffer and delete the zip after flashing. If you're able to get Android up and running, then you should be able to connect it to your PC, copy the ROM and gapps zips over to the kindle without using adb, and flash the gapps.
Click to expand...
Click to collapse
Thanks very much for all of your advice and suggestions! I'm back up and running. The gapps package was causing an error 70 message. Once I found a smaller file it worked. It certainly was an excellent learning experience. Thank you again.

A request to official/unofficial TWRP developers

Hi All!
As plenty of people know by now that the latest modified twrp that we have does not work with encrypted storage when flashing official nougat oos. And there must be many people like me who due to reasons dont have time to copy n move everything back or don't want to decrypt their storage. So me and all of op3 community would appreciate if anyone can take some time out of their schedule and build an updated twrp version so that we can flash official nougat without screwing with storage or encryption. Because nougat is the future now and we'll start receiving nougat update from now onwards. And its a shame tha such an active dev device like op3 does not even have an updated twrp version. Thanks!
+1
A reason for this issue is probably OnePlus not releasing any Kernel Source code yet.
https://github.com/OnePlusOSS/android_kernel_oneplus_msm8996/issues/27
eng.stk was releasing a couple twrp mods but doing so is a pita with users on your back who constantly want 247 support.
AcmE85 said:
A reason for this issue is probably OnePlus not releasing any Kernel Source code yet.
https://github.com/OnePlusOSS/android_kernel_oneplus_msm8996/issues/27
eng.stk was releasing a couple twrp mods but doing so is a pita with users on your back who constantly want 247 support.
Click to expand...
Click to collapse
Totally agree to that. I was also assuming that an updated kernel sources are required to build a compatible twrp recovery for nougat. Waiting eagerly for the same. And considering the feedback of people on official OOS, i don't feel it's really a must have update as of now.
I also agree to the point about users. People need to stop taking developers for granted, and give them their space to release updates, and they should understand the dev is doing this in his/her free time not as a full time job. I hope we'll see an updated TWRP soon. Until then, MM is serving me well. No hurry
He is only asking, stop crying dude
To many ladies with balls here
fanbogo said:
He is only asking, stop crying dude
To many ladies with balls here
Click to expand...
Click to collapse
Sorry for the confusion what is it intended for me?
TWRP password, please help.
As first i wasn't able to flash any twrp files at all as after flashing it shows some black screen so not even from the official TWRP site the files were helpful, then after ages of serching I found some thread in XDA where a guy posted the link to this twrp https://forum.xda-developers.com/on...nity-build-t3461648/post68691560#post68691560, then I was able to successfully install it and boot into TWRP recovery.
So here I am now stuck with the ****** password to decrypt data and I simply want to root my OP 3 but due to this situation I am unable to so any solutions on this will be much helpful and any way to remove the dumb password for the TWRP.
Thanks.
Dude even if twrp shows encrypted you can still flash supersu. Just mount the /system partition in Mount options and flash supersu via otg.
Dude that is a mess n upon that I don't have otg, and really isn't there any way for this to encryption to get decrypt ?
samyj22 said:
Dude that is a mess n upon that I don't have otg, and really isn't there any way for this to encryption to get decrypt ?
Click to expand...
Click to collapse
You can flash SuperSU without TWRP being able to decrypt your DATA partition:
- Boot into TWRP
- cancel the password prompt
- push the supersu.zip to your phone via adb push supersu.zip / (notice the blank between zip and /!).
- go to INSTALL, navigate to the root directory and flash it
- reboot
Worked without issues on my device.
samyj22 said:
Dude that is a mess n upon that I don't have otg, and really isn't there any way for this to encryption to get decrypt ?
Click to expand...
Click to collapse
Connect your phone to your pc, boot TWRP via fastboot from the PC and flash SuperSu via adb under advanced in TWRP.
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
AcmE85 said:
You can flash SuperSU without TWRP being able to decrypt your DATA partition:
- Boot into TWRP
- cancel the password prompt
- push the supersu.zip to your phone via adb push supersu.zip / (notice the blank between zip and /!).
- go to INSTALL, navigate to the root directory and flash it
- reboot
Worked without issues on my device.
Click to expand...
Click to collapse
Didn't knew that at all part from ya we can push files via side load, but just to confirm my internal storage shows as 0mb as it is encrypted n even if I push the files to internal storage so just wanted to make sure will it show up in two file manager?
Next thing so if I have any ROM files to flash can they be pushed as well with the command adb push file.zip /right?
N yah I have to enter sideload mode for this right.
samyj22 said:
Didn't knew that at all part from ya we can push files via side load, but just to confirm my internal storage shows as 0mb as it is encrypted n even if I push the files to internal storage so just wanted to make sure will it show up in two file manager?
Next thing so if I have any ROM files to flash can they be pushed as well with the command adb push file.zip /right?
N yah I have to enter sideload mode for this right.
Click to expand...
Click to collapse
I just booted into twrp, canceled the password prompt and pushed the file while being in the main menu.
The file will be stored in your devices root folder, not "internal storage" or "sdcard".
So when you go to "install", you have to go all the way up your folder structure. This is were you will find the supersu.zip.
AcmE85 said:
You can flash SuperSU without TWRP being able to decrypt your DATA partition:
- Boot into TWRP
- cancel the password prompt
- push the supersu.zip to your phone via adb push supersu.zip / (notice the blank between zip and /!).
- go to INSTALL, navigate to the root directory and flash it
- reboot
Worked without issues on my device.
Click to expand...
Click to collapse
Can we perform an adb sideload rather than adb push to directly flash SuperSU zip? Or does sideload only works for rom zips?
AcmE85 said:
I just booted into twrp, canceled the password prompt and pushed the file while being in the main menu.
The file will be stored in your devices root folder, not "internal storage" or "sdcard".
So when you go to "install", you have to go all the way up your folder structure. This is were you will find the supersu.zip.
Click to expand...
Click to collapse
Just a little confusion, as the internal storage is the same as root directory or the one level back to the SD card is the root directory?
abhibnl said:
Can we perform an adb sideload rather than adb push to directly flash SuperSU zip? Or does sideload only works for rom zips?
Click to expand...
Click to collapse
Yes you can directly sideload.
Bro just need confirmation on the commands for the push and sideload as well correctly, that will be really helpful...... ?
samyj22 said:
Bro just need confirmation on the commands for the push and sideload as well correctly, that will be really helpful......
Click to expand...
Click to collapse
Mount system in recovery,
adb sideload sample.zip
adb push <source-path> <target-path>
If file is in the adb folder already, then
adb push sample.zip /system or whatever path you want to send it to.
Edit: While pushing, make sure you mount system as RW first. But i guess when you mount system in TWRP, it's automatically in RW mode. But please do check with someone who has done it or an expert. I have limited knowledge, so sharing as far as i know
abhibnl said:
Mount system in recovery,
Click to expand...
Click to collapse
Hello thank you, but in twrp i can't mount /system
in mount i can select system but i have
Decrypt data
Select Storage
Disable/enable MTP.
acetone802000 said:
Hello thank you, but in twrp i can't mount /system
in mount i can select system but i have
Decrypt data
Select Storage
Disable/enable MTP.
Click to expand...
Click to collapse
Do you have all those 3 options in the mount menu? I don't think that should be there. I'm sorry, your statement is a bit unclear actually.

Categories

Resources