Dear all,
I finally got TWRP flashed onto my Le Max..
With TWRP, I backupped my phone and copied it to my PC.
I downloaded several roms to my Le Max, wich all went ok...
In the TWRP recovery menu, I choose Wipe All ( Dalvik, system, Cache, Data, Internal )...
But now, you guess, there is no OS on the phone...
When I enter TWRP recovey menu, advanced, sideload, I tried to copy a rom to the phone via " ADB SIDELOAD MAX.ZIP" but I get the message on the pc
loading : max.zip
* cannot read max.zip
Who can help? At the moment I dont have a USB stick....
if max.zip is your backup then do restore.
Max.zip is my rename of 23S Chinese...
My backup is " 2017-05-24--12-39-24_FIXNAOP5801607292S_release-keys"
It is more, how to get the files on my phone without a OTG USB stick...
Which commands and so...
ADB SIDELOAD xxxx.img works better, then xxxx.zip.
But I cant find any rom in .img format...
Bobenjanneke said:
Dear all,
I finally got TWRP flashed onto my Le Max..
With TWRP, I backupped my phone and copied it to my PC.
I downloaded several roms to my Le Max, wich all went ok...
In the TWRP recovery menu, I choose Wipe All ( Dalvik, system, Cache, Data, Internal )...
But now, you guess, there is no OS on the phone...
When I enter TWRP recovey menu, advanced, sideload, I tried to copy a rom to the phone via " ADB SIDELOAD MAX.ZIP" but I get the message on the pc
loading : max.zip
* cannot read max.zip
Who can help? At the moment I dont have a USB stick....
Click to expand...
Click to collapse
If you flash system off course you get No OS, because you deleted system partition.
And do not wipe Internal, phone has no sd card. When you flash internal you delete everything on the media partition which includes backup, music, photos, and the ROMs yo downloaded. When you flash a rom you only need to wipe cache, dalvik media and data. (System when u move from stock to custom, if you flash system and then try to flash another stock rom you will get error 7)
Now, I don't know what "max.zip" is. Try with other rom file or download cuoco92 fastboot version, then put your phone on fastboot mode, execute cuoco installation on PC and it will automatically flash the rom.
Edit: Install this driver https://drive.google.com/open?id=0By3XfnDvUFlAYXBZbFNhYTdCcjQ and then try to connect your phone to pc when in TWRP. It lets connect in MTP mode and it works for me
Enviado desde mi LEX829 mediante Tapatalk
max.zip = 23s Chinese ROM
While booted into TWRP. Connect your phone via the charging cable to your computer and copy rom + GApps to the internal storage of your phone.
Now install in TWRP.
Everybody allready thank you!
I don't know HOW to copy the files to my phone...
It is in recovery TWRP mode not recognized in Explorer, and the ADB command's I have found on Google, like ADB SIDELOAD and ADB PUSH don't work...
Does someone know if the USB cable witch came with the package, is OTG ready?
Bobenjanneke said:
Everybody allready thank you!
I don't know HOW to copy the files to my phone...
It is in recovery TWRP mode not recognized in Explorer, and the ADB command's I have found on Google, like ADB SIDELOAD and ADB PUSH don't work...
Does someone know if the USB cable witch came with the package, is OTG ready?
Click to expand...
Click to collapse
Copy the ROM to the ADB & Fastboot file path, then connect your Le Max 2 with your pc.
Now go in TWRP to Advanced and click on "ADB Sideload", type in ADB "adb sideload nameofthefile.zip", this will flash your ROM.
(It will not work with EUI but with every other ROM)
Or you push it with ADB push: "adb push /filepath/nameofthefile.zip/sdcard" after this click on Install, and install ist. ? Hope this helps your, and sorry for my bad english.
jufece said:
If you flash system off course you get No OS, because you deleted system partition.
And do not wipe Internal, phone has no sd card. When you flash internal you delete everything on the media partition which includes backup, music, photos, and the ROMs yo downloaded. When you flash a rom you only need to wipe cache, dalvik media and data. (System when u move from stock to custom, if you flash system and then try to flash another stock rom you will get error 7)
Now, I don't know what "max.zip" is. Try with other rom file or download cuoco92 fastboot version, then put your phone on fastboot mode, execute cuoco installation on PC and it will automatically flash the rom.
Edit: Install this driver https://drive.google.com/open?id=0By3XfnDvUFlAYXBZbFNhYTdCcjQ and then try to connect your phone to pc when in TWRP. It lets connect in MTP mode and it works for me
Enviado desde mi LEX829 mediante Tapatalk
Click to expand...
Click to collapse
What's the way to work when I want all of my 64gb ? ( If possible )
I read some about X829 has encrypted partition?
So when ( when all is fixed ) i am in the phone filemanager, I see total free space = 64gb -/- ROM = 60GB
Bobenjanneke said:
What's the way to work when I want all of my 64gb ? ( If possible )
I read some about X829 has encrypted partition?
So when ( when all is fixed ) i am in the phone filemanager, I see total free space = 64gb -/- ROM = 60GB
Click to expand...
Click to collapse
It's imposible to get 64 gb free...
And as far as I know the encryption problem is an issue fixed from 19S and above
Enviado desde mi LEX829 mediante Tapatalk
jufece said:
....
Try with other rom file or download cuoco92 fastboot version, then put your phone on fastboot mode, execute cuoco installation on PC and it will automatically flash the rom.
Click to expand...
Click to collapse
THE PHONE IS
****************************** ALIVE ******************************
THANK YOU very much!!!
( BTW, thank you all folks !!!! )
VC-34 said:
Copy the ROM to the ADB & Fastboot file path, then connect your Le Max 2 with your pc.
Now go in TWRP to Advanced and click on "ADB Sideload", type in ADB "adb sideload nameofthefile.zip", this will flash your ROM.
(It will not work with EUI but with every other ROM)
Or you push it with ADB push: "adb push /filepath/nameofthefile.zip/sdcard" after this click on Install, and install ist. ? Hope this helps your, and sorry for my bad english.
Click to expand...
Click to collapse
just wanted to say that I sideloaded Aurel EUI Rom.
but not recommended as it took me 2 tries.
What is best ROM for the Le Max 2?
I had vendor rom, which I turned on in the Chinese.
Now I have the Cuoco rom with some apps...
And "the best" rom is for everybody different, but I am curious at the thougths of other people about it...
I continiou that in another forum
( https://forum.xda-developers.com/le-max-2/development/best-stock-custom-rom-le-max-2-x829-t3612563 )
cy-rock said:
just wanted to say that I sideloaded Aurel EUI Rom.
but not recommended as it took me 2 tries.
Click to expand...
Click to collapse
It's because aurel EUI-ROM uses Aroma Installer.
jufece said:
It's imposible to get 64 gb free...
And as far as I know the encryption problem is an issue fixed from 19S and above
Enviado desde mi LEX829 mediante Tapatalk
Click to expand...
Click to collapse
What if I format my internal storage, and then repair the internal storage with cuoco92 fastboot version?
Whill that work?
Thank you already guys!
Bobenjanneke said:
What if I format my internal storage, and then repair the internal storage with cuoco92 fastboot version?
Whill that work?
Thank you already guys!
Click to expand...
Click to collapse
It doesn't matter because when u flash a rom with fastboot method it wipes everything.
Enviado desde mi LEX829 mediante Tapatalk
Related
alright i have this problem and i am quite panicking now.
i will set everything straight , i hope someone reading the forums can help me asap !
- have a sgs2 unbranded (hk)
- has ICS 4.0.3 stock rom, rooted.
- i don't remember if usb debug mode was enabled
- i messed up in some way with the file /system/build.prop but there is a backup in /system/ called build.prop.bak
- phone doesn't boot anymore as it's stuck at the logo
- recovery and download modes work however
#need a way to delete the build.prop and replace the bloody file with the one backupped. I would like to avoid having to format the phone as i do not remember when was my last kies backup...
what i tried:
-adb shell: it doesn't work. for some stupid reasons the drivers won't be recognized (i have download android sdk and usb drivers), but when i plug the phone in recovery windows just says Device Unknown and even if i update drivers manually it would say that current ones are functioning so no need to update.
if i connect the phone to usb while it's stuck at boot logo, it would recognize the device through samsung drivers (except MTP of course, that would give error).
in both cases adb shell doesn't list any connected device: even if i kill-server and start-server it still doesn't list anything.
-tried using droid explorer in both frozenboot mode and recovery mode, doesn't see anything.
-tried using that other program called SuperOneClick or something like that, that has a "check drivers" button in advanced: if the phone is in recovery pressing the button doesn't do anyhing; if the phone is in frozenboot it asks to download and install some drivers but when i press yes a message appears with " no more data is available " !
i tried this procedure on both win7x64 and winXPx86: same results. reading around , someone says that adb shell will never work if usb debug is de-actived, like i said i cannot remember if that's the case.
-zip package: i created a package to try and overwrite the file with a custom working one i got. i put the package in the root of the micro sd , put the sd in the phone and booted in recovery.
but when i am in recovery the bloody CWM 5.0.2.7 says error to mount /sdcard, or E: could not mount /sdcard , same if i try to mount/unmount /sdcard. if i go to mount external usb card or whatever it says that a file or a lib (cant remember the exact message) was not found.
i have no more ideas of how to solve this, please be patient :<
edit: is there a way to soft format the system folder so that i don't have to properly wipe all my user data and it only affects the system without other contents?
If adb doesn't work hen you are in trouble, better download some non wipe rom and flash it over the existing rom so that your user data will still be there.
Sent from my GT-I9100 using xda premium
bala_gamer said:
If adb doesn't work hen you are in trouble, better download some non wipe rom and flash it over the existing rom so that your user data will still be there.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
can you expand on this?
give any suggestion/example?
isn't there a soft temp rom for emergencies like this that you can just start, make modifies to fix and reboot (similar to the process to boot ubuntu on windows, fix issues and then restart normal windows? )
i would so like to make adb work.. but how.!!!
probebly will not work but try backing up of your ROM from CWM working or not..then just back up current one...
you can restore apps & data lateron from nandroid backup with some application like titanium backup donated version.
i made a backup . but since the external sd card isn't found by the recovery, now the backup is sitting on the internal memory.
the problem is that, if i flash something with odin now, won't odin wipe everything in the internal memory killing my backup as well?
-marco- said:
i made a backup . but since the external sd card isn't found by the recovery, now the backup is sitting on the internal memory.
the problem is that, if i flash something with odin now, won't odin wipe everything in the internal memory killing my backup as well?
Click to expand...
Click to collapse
nope....it will be there dont worry,
just check one more option, go to storage and mount, there is one option mount usb storage, after connecting your phone to PC just mout that and check, are you able to access the SDcard from the computor ot not, if yes, just copy paste your backup to the computor.
then flash a firmware from ODIN
Did the very same thing myself yesterday.. Most ICS-roms from Samsung is non-wipe, so you can just flash it over again with Odin.. Then you just need to root and make customizations (if any) again
zaheedahmed said:
nope....it will be there dont worry,
just check one more option, go to storage and mount, there is one option mount usb storage, after connecting your phone to PC just mout that and check, are you able to access the SDcard from the computor ot not, if yes, just copy paste your backup to the computor.
then flash a firmware from ODIN
Click to expand...
Click to collapse
nope. i just tried this , and when i "mount /sdcard" it says " Error mounting /sdcard! "
when i try mount USB storage , it says " E: unable to open ums lunfile (no such file or directory) "
mljjlm said:
Did the very same thing myself yesterday.. Most ICS-roms from Samsung is non-wipe, so you can just flash it over again with Odin.. Then you just need to root and make customizations (if any) again
Click to expand...
Click to collapse
could you be more specific on the process ? can you suggest me one to flash with odin ? i need to enter the OS , transfer my backup on my hard disk and then restore the whole thing.
currently my kernel is CF-Root-SGS2_XX_XEO_LPQ-PROPER-v5.4-CWM5.tar
and my firmware is GT-I9100_BRI_I9100ZSLPE_I9100OZSLPE_I9100ZSLPE.tar
-marco- said:
nope. i just tried this , and when i "mount /sdcard" it says " Error mounting /sdcard! "
when i try mount USB storage , it says " E: unable to open ums lunfile (no such file or directory) "
could you be more specific on the process ? can you suggest me one to flash with odin ? i need to enter the OS , transfer my backup on my hard disk and then restore the whole thing.
currently my kernel is CF-Root-SGS2_XX_XEO_LPQ-PROPER-v5.4-CWM5.tar
and my firmware is GT-I9100_BRI_I9100ZSLPE_I9100OZSLPE_I9100ZSLPE.tar
Click to expand...
Click to collapse
you try to reflash once more CF-Root (.TAR)only from odin
then check "E: cant mout...error" is rectified or not.... also check booting or not,
still no hope...you flash the same firmware again and Cf-root, your SD card data will be there for sure as far as our expereicne till now..
first part of your comment: i tried reflashing the kernel; no changes. same errors
second part: shall i try using the same firmware from my previous post then?? not other roms? after that i will put the root and check if internal memory is still there. if it is i will copy it on my hd and restore.
if it is not there anymore..............
so the end of the story.
thanks to anyone who helped.
the resolution was much easier than everything else.
opened odin, pda loaded my same firmware which was the HK stock update to ICS and reflashed.
what it did was apparently and overhaul of the system folder, that's it.
any data was still there, as well as the backup that i did and all my apps etc etc etc.
however especially at first it looked a bit unstable, with processes failing randomly. now it seems it has stabilized a bit, but still when i try to run a Kies backup, the phone kies process dies and the backup gets stopped.
i still don't know how to fix this, but i'll be looking into it.
so, the morale out of this was at least for me: if there is some **** up within the system folder just reflash the same rom installed. i feel so stupid now for having made such a fuss when the solution was so easy and straightforward
NICE that you finaly came across and able to boot , now you make the Titanium back of your all apps and data transfer to PC....forget the system data.
and move to a nice stable ROM
"Unfortunately, wssyncmlnps has stopped"
anybody knows about this?
Hello all. hdx 7 was running the original version of safestrap and gapps on the very first firmware. accidently wiped internal and now can only boot to safestrap no abd so bricked or not and by the way i already read like damm near all the threrads i could find so dont accuse me of being a lazy no good non reasearching az mf thanx
jamesh1979 said:
Hello all. hdx 7 was running the original version of safestrap and gapps on the very first firmware. accidently wiped internal and now can only boot to safestrap no abd so bricked or not and by the way i already read like damm near all the threrads i could find so dont accuse me of being a lazy no good non reasearching az mf thanx
Click to expand...
Click to collapse
Ok, if I understand you correctly, you wiped internal storage of your sdcard, so no backups to restore for safestrap.
But when wiping happened, you were on activated extra rom slot? So now safestrap cant boot there, because with internal storage you deleted image files for rom slots...
If you can boot into safestrap, can you switch to stock rom? And boot into it? If yes, and Fireos start normally, then nothing is lost, reinstall safestrap, you should have adb access, and do whatever you want to do next...
Did you disabled OTA updates on stock rom? If not, turn off wifi as fast as you can, when you boot into Fireos, so it cant update to nonrootable FW.
thats whats wierd i was on rom slot one but it wiped even my stock img as far as i can tell because it wont let me switch to it , and yes disabled ota with toolkit like a year ago and all was fine?
jamesh1979 said:
thats whats wierd i was on rom slot one but it wiped even my stock img as far as i can tell because it wont let me switch to it , and yes disabled ota with toolkit like a year ago and all was fine?
Click to expand...
Click to collapse
Well, I installed safestrap on my working kindle, so I can check what else was deleted in the wiping, unfortunately there was a little config file where safestrap stored which slot was last active. This file no longer exist, so safestrap dont know from what to switch where.
The only thing we can try (AFAIK) requires working adb connection and it must be working from safestrap, so you can use adb sideload feature - so enter safestrap and connect kindle to your pc or laptop. Then start cmd window or terminal if you using linux, and try:
adb devices
it should return:
list of devices attached
xxxxxxxxx recovery
if you can achieve this, we can try with sideloading, if not I am sorry, dont know what else to do - actually there is one thing you can try - with working adb access you can recreate directory structure needed for safestrap config file and push it there (I will attach it later), then restart and see if it boot to stock rom
edit:
I was able connect through adb from windows to running safestrap, so it is possible (at least kindle is recognized in "adb devices")
ok guys i got the pc to see the kindle in recovery via adb!!! so what now push a rom to internal storage and flash it and then reinstall safestrap to get stock slot available or what????
jamesh1979 said:
ok guys i got the pc to see the kindle in recovery via adb!!! so what now push a rom to internal storage and flash it and then reinstall safestrap to get stock slot available or what????
Click to expand...
Click to collapse
Great!
Now download this 13.3.1.0 (Kindle HDX 7") update - pure amazon FireOS so OTA updates enabled - do not connect to wifi/register your kindle if you want root and use of custom recovery after flashing this
A. Now, since I am not expert for adb installing pushing repairing etc., read this thread [HOWTO] Unbrick your device, especially this post (shows similar symptoms as your current problem)
B. If that for whatever reason wont work, you can try sideload update-kindle-13.3.1.0_user_310079820.bin (rename .bin to .zip before sideloading) through safestrap recovery, but because Safestrap is "only" TWRP based, I cant guarantee that this will work either (it should, but this is one way ticket, your working safestrap recovery will be destroyed in the process of update):
0. connect kindle to pc/laptop
1. enter Safestrap, tap Advanced -> ADB Sideload -> Swipe slider to start Sideload
2. on pc/laptop open cmd/terminal, type adb devices, you should see:
List of devices attached
XXXXXXXXXXXXXXXX sideload
3. type adb sideload update-kindle-13.3.1.0_user_310079820.zip
4. You will see a progress bar in the command prompt indicating that the Zip file is being copied to the device. Once the file is transferred, the Zip is automatically installed on your device.
C. You can consider also recreating deleted folder containing slot config file for Safestrap (active_slot file attached below (file is in archive, you need extract it)) through adb shell:
0. connect kindle to pc/laptop
1. enter Safestrap
2. on pc/laptop open cmd/terminal, type adb devices, you should see:
List of devices attached
XXXXXXXXXXXXXXXX recovery
3. type adb shell
4. type mkdir -p data/media/safestrap/rom-slot1
5. type exit
6. type adb push active_slot data/media/safestrap
7. reboot/reboot into recovery and see if you can switch/boot to stock rom (which is still there, otherwise safestrap will not be accessible)
C variant is a really long-shot, but relatively harmless (or maybe not who knows, I am not expert)
OK fingers crossed, I hope something will work, but things can go wrong, unfortunatelly from my side all above is just a theory, adb commands should works, I tested them all (except sideload), works on my side...
Thanx a lot guys I got I t back in action thanx for all the help
jamesh1979 said:
Thanx a lot guys I got I t back in action thanx for all the help
Click to expand...
Click to collapse
Care to share which method you use to recover your kindle?
anyone here? lol
XPOSED FOR XPERIA M4 AQUA- STOCK 5.0
Hello guys, i updated the guide, for install xposed on stock 5.0 rooted firmware.
Much thanks to @husam666 and anyone who made twrp,xposed and all other...
PLEASE NOTE: AFTER THIS STOCK CAMERA WILL NOT WORK. USE GOOGLE CAMERA
Requirements:
Unlocked bootloader & root (CLICK HERE TO SEE HOW TO DO IT...)
Xposed apk file:http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440
Xposed zip file: http://forum.xda-developers.com/attachment.php?attachmentid=3543411&d=1447616600
The guide will not show how to unlock bootloader and root phone, only xposed install procedure.
Step 1:
Install xposed apk file in the phone, then run adb tools on pc.
Step 2:
Reboot phone into recovery TWRP. (press vol- button at power, when phone vibrate, press it for much time). Screen will be black, not worry, its all ok.
Step 3:
type (in adb) these 2 commands:
Code:
adb devices
(If your device is here, you can continue.)
and
Code:
adb shell
Step 3:
A prompt like ~ # will appear, type these commands :
Code:
mount -w /dev/block/platform/7824900.sdhci/by-name/system /system
mount -w /dev/block/platform/7824900.sdhci/by-name/userdata /data
mount -w /dev/block/platform/7824900.sdhci/by-name/cache /cache
Step 4:
Now type:
Code:
twrp sideload
Step 5:
Type
Code:
adb sideload <path_to_zip>
(without <> and with the real directory of the zip.)
Step 6:
When done, type that:
Code:
adb reboot
ALTERNATIVE BEST METHOD: Install new TWRP touch recovery with working display, put zip into sd internal and flash. At the end of flash wipe dalvik cache /cache.
The phone will reboot and you have xposed installed!.
Attention: XDA, Me and all other members not take responsability for damaged phones or other problems.
I can't wait to know how to install Xposed! THANKS AGAIN!
Guide updated!
Could you explain better the point 5: <path_to_zip> ?
It could be useful, so we are sure not to miss anything.
EnricoLH said:
Could you explain better the point 5: <path_to_zip> ?
It could be useful, so we are sure not to miss anything.
Click to expand...
Click to collapse
The path to the zip file of xposed, can be something like c:\downloads\xposed-v74-sdk21-arm64.zip
Also I would like to note that you should do this after you flashed the zip so that you don't get low storage space error
celtique said:
For those with "Low Space" after sideloading xposed, do as follow:
Code:
adb shell
twrp wipe cache
twrp wipe dalvik
reboot
It will take long to boot.
It stuck after 10 min, simple press the tiny button next to SD Card and the power on again.
Enviado desde mi E2306 mediante Tapatalk
Click to expand...
Click to collapse
error: protocol fault (no status)
Argh...always this message when I try to sideload
Edit : If sideload crashes for you, after mounting, instead of sideload, type
twrp install /data/media/0/<yourxposedfile.zip>
and wait for it.
After the "Done processing script file", plug out your cable and press power and vol+ until it vibrates 3 times.
Press power to boot
Pay attention to copy the xposed zip file in internal memory and not in your external SD Card
Guys later i will update guide for fixing problem of memory.
Infinite thanks to @husam666.
alby_var said:
Guys later i will update guide for fixing problem of memory.
Infinite thanks to @husam666.
Click to expand...
Click to collapse
If you can add the part I wrote for those who have sideloading problem, it can be useful
husam666 said:
The path to the zip file of xposed, can be something like c:\downloads\xposed-v74-sdk21-arm64.zip
Also I would like to note that you should do this after you flashed the zip so that you don't get low storage space error
Click to expand...
Click to collapse
After do that, stuck at boot...
After install xpoxed, memory error, after fix memory error (wipes from recovery,hard reset,flashtool wipe) you will lose de camera. No way to hold the camera working after 13 flashins. Firm 112.
Somebody can confirm that after install xposed,fix the memory error,have working the camera?
Flamenawer said:
After install xpoxed, memory error, after fix memory error (wipes from recovery,hard reset,flashtool wipe) you will lose de camera. No way to hold the camera working after 13 flashins. Firm 112.
Somebody can confirm that after install xposed,fix the memory error,have working the camera?
Click to expand...
Click to collapse
I lost my camera, too. Too lazy to figure out what caused it, so I'm reflashing /system
husam666 said:
I lost my camera, too. Too lazy to figure out what caused it, so I'm reflashing /system
Click to expand...
Click to collapse
Same for my camera not working
Which way I can uninstall xposed without losing everything ?
Thanks
Envoyé de mon E2333 en utilisant Tapatalk
flexouille1 said:
Same for my camera not working
Which way I can uninstall xposed without losing everything ?
Thanks
Envoyé de mon E2333 en utilisant Tapatalk
Click to expand...
Click to collapse
There's a zip file that uninstalls it, not sure if you'll get your camera back
I didn't test the camera. I lost apps in SD card.
I flashed an Uninstaller and it gone back to normal
Flamenawer said:
After install xpoxed, memory error, after fix memory error (wipes from recovery,hard reset,flashtool wipe) you will lose de camera. No way to hold the camera working after 13 flashins. Firm 112.
Somebody can confirm that after install xposed,fix the memory error,have working the camera?
Click to expand...
Click to collapse
Try to sideload and older version of xposed64.
Enviado desde mi E2306 mediante Tapatalk
This moded camera from z3 work, http://forum.xda-developers.com/cro...ps/mod-xperia-camera-unlocked-t3071161/page49
Only problems, will show 20mpx,but will work at 13mpx in auto mode. And camera not work too. Is a starting.... until a xposed version that work. You need have the xposed 20 superior auto module.
I will look for a old version of xposed.
I flashed the original firmware (26.1.B.2.129) and I have my camera back.
[Noob question] Could somebody explain what benefits of Xposed installing bring to the phone?
lordgamma said:
[Noob question] Could somebody explain what benefits of Xposed installing bring to the phone?
Click to expand...
Click to collapse
It brings you modifications of the framework without touching any apks
Someone succeded to install it without bugs (no photo, no sd)?
Hi
I own a 100% stock Samsung Galaxy S2 (GT-i9100).
The device is not rooted or modified and is currently running standard Samsung firmware.
Baseband I9100XXMS2
Kernel 3.0.31-1211311
Build numberJZ054K.I9100XWLSW
Android 4.1.2
Whilst I am not a power user I am tired of running out of system memory and having to move apps to the SD card. I am also tired of not being able to load certain apps due to the old Android version. I do want to connect to my car via Bluetooth (audio and internet etc).
It's time for a new operating system ... hence my visit to this web site. I have tried reading the guides but most use a lot of jargon and talk of multiple ROM options. I am a little lost and need some plain English instruction to follow since this is my first step into the ROM flashing world.
Which version should I install? Where do I download it from? What tools do I need for my PC? How do I do the flash?
Anyone out there who can help a complete novice?
Thanks in advance
Jacbjacb said:
Hi
I own a 100% stock Samsung Galaxy S2 (GT-i9100).
The device is not rooted or modified and is currently running standard Samsung firmware.
Baseband I9100XXMS2
Kernel 3.0.31-1211311
Build numberJZ054K.I9100XWLSW
Android 4.1.2
Whilst I am not a power user I am tired of running out of system memory and having to move apps to the SD card. I am also tired of not being able to load certain apps due to the old Android version. I do want to connect to my car via Bluetooth (audio and internet etc).
It's time for a new operating system ... hence my visit to this web site. I have tried reading the guides but most use a lot of jargon and talk of multiple ROM options. I am a little lost and need some plain English instruction to follow since this is my first step into the ROM flashing world.
Which version should I install? Where do I download it from? What tools do I need for my PC? How do I do the flash?
Anyone out there who can help a complete novice?
Thanks in advance
Click to expand...
Click to collapse
Mate, take it easy, i see you are a good English speaker, it should be very easy for you to understand the guides, for me it was hard and i bricked my phone multiple times, I'm not saying that I'm a geek or an android expert or something like that, but i know enough about my phone and i know what it's capable of and what it isn't, you should start easy step by step, and try following a video guide from YouTube like searching in google "i9100 root and custom recovery" and start reading some articles about it, believe me no one would just give you instructions on a silver plate, even if someone did, you will remain a noob who knows nothing about flashing and you won't be able to change your new rom or go back to stock rom..you should dig for it, there are guides that provide you with instructions and information about what you do..all you have to do is do a couple of google searches..
Anyway, all i can do to you is give you a link to this guide
Hope you understand the message
Regards Migo
Well I spent the entire afternoon and evening yesterday reading all I could about the flashing of the this Samsung Galaxy S2 GT-i9100. I then started to collect the files I think I will need:
Heimdall Suite: Inc' zadig.exe 2.0.0147, heimdall-frontend.exe 1.4.0, heimdall.exe
Lineage 14.1 Rom: cm-14.1-20161225-UNOFFICIAL-i9100.zip
Minimal_adb_fastboot_v1.4.2_setup.exe: Inc' adb.exe. cmd-here.exe, fastboot.exe etc
Odin3 v1.85.exe
open_gapps-arm-7.1-nano-20170225.zip
PIT Files: I9100_2GB-STOCK.pit (in case of problems) and I91001GB_6GB.pit
SAMSUNG USB Driver for Mobile Phones 1.5.27.0.exe
TWRP: twrp-3.0.2-1-i9100.img, recovery-the.gangster-IsoRec-TWRP-3.0.2-1-i9100.zip,
On the phone I activated USB Debugging
I installed the USB drivers and the PC can see the phone
I ran Odin and the phone is seen
I tried to install TWRP using the instructions found here: https://twrp.me/devices/samsunggalaxys2i9100.html .... It didn't work!
I copied recovery-the.gangster-IsoRec-TWRP-3.0.2-1-i9100.zip to the SD card, entered recovery mode and tried to apply the update from external storage. All seem to go well but then I got E:Error in tmp/sideload/package.zip (Status 7) ..... at the Top of the page it said Android System recovery (3e) ... I take it that is the system recovery currently installed on the phone. I found twrp-3.0.2-0-i9100.zip and tried that .... but got the same System 7 error!
So I have got nowhere really!
I know I have to repartition the drive using the PIT file
I know I have to load a custom recovery file using the TWRP
I then have to load the new ROM
But I don't know the order in which to do the operations .... TWRP first or PIT?
I don't seem to be alone in my fog ... see https://forum.xda-developers.com/ga...twrp-galaxy-s2-i9100-tried-t3539940?nocache=1
I have now realized that the various guides relate to the version of ROM they wish to install .... I am planning to use a Lineage 14.1 Rom. It seems that I can load it using TWRP or Odin.
I think the first step is to load TWRP ....... But I cant seem to be able to do that ..... Can Anyone help me install TWRP if that if the first priority?
Well I spent the entire afternoon and evening yesterday reading all I could about the flashing of the this Samsung Galaxy S2 GT-i9100. I then started to collect the files I think I will need:
Heimdall Suite: Inc' zadig.exe 2.0.0147, heimdall-frontend.exe 1.4.0, heimdall.exe
Lineage 14.1 Rom: cm-14.1-20161225-UNOFFICIAL-i9100.zip
Minimal_adb_fastboot_v1.4.2_setup.exe: Inc' adb.exe. cmd-here.exe, fastboot.exe etc
Odin3 v1.85.exe
open_gapps-arm-7.1-nano-20170225.zip
PIT Files: I9100_2GB-STOCK.pit (in case of problems) and I91001GB_6GB.pit
SAMSUNG USB Driver for Mobile Phones 1.5.27.0.exe
TWRP: twrp-3.0.2-1-i9100.img, recovery-the.gangster-IsoRec-TWRP-3.0.2-1-i9100.zip,
On the phone I activated USB Debugging
I installed the USB drivers and the PC can see the phone
I ran Odin and the phone is seen
I tried to install TWRP using the instructions found here: https://twrp.me/devices/samsunggalaxys2i9100.html .... It didn't work!
I copied recovery-the.gangster-IsoRec-TWRP-3.0.2-1-i9100.zip to the SD card, entered recovery mode and tried to apply the update from external storage. All seem to go well but then I got E:Error in tmp/sideload/package.zip (Status 7) ..... at the Top of the page it said Android System recovery (3e) ... I take it that is the system recovery currently installed on the phone. I found twrp-3.0.2-0-i9100.zip and tried that .... but got the same System 7 error!
So I have got nowhere really!
I know I have to repartition the drive using the PIT file
I know I have to load a custom recovery file - TWRP
I then have to load the new ROM
But I don't know the order in which to do the operations .... TWRP first or PIT?
I don't seem to be alone in my fog ... see https://forum.xda-developers.com/ga...twrp-galaxy-s2-i9100-tried-t3539940?nocache=1
I have now realized that the various guide relate to the version of ROM you wish to install .... I am planning to use a Lineage 14.1 Rom. It seems that I can load it using TWRP or Odin.
I think the first step is to load TWRP ....... But I cant seem to be able to do that ..... Can Anyone help?
Jacbjacb said:
I have now realized that the various guide relate to the version of ROM you wish to install .... I am planning to use a Lineage 14.1 Rom. It seems that I can load it using TWRP or Odin.
I think the first step is to load TWRP ....... But I cant seem to be able to do that ..... Can Anyone help?
Click to expand...
Click to collapse
The TWRP you are trying to install requires a kernel that supports isorec, so you must have that kernel first.
To have isorec support:
Note: -the rom and the isorec recovery and nogut rom and gapps -in short: all files- should be put in external sdcard because the internal sdcard will be wiped in the procedure.
1-you should install latest kernel-Lanchon-TRIM-IsoRec, you can easily flash it using a
Kitkat compatible recovery, flash the recovery using Odin along with a pit that has 1GB system or more,
1.5GB PIT Files by the.gangster or 1GB PIT Files by ELgmal 1GB is enough
2-after that, reboot to recovery:
• wipe data
• wipe cache
• navigate to "mount" and format system and format internal sdcard using (default)
• go back and navigate to "advanced" and wipe Dalvik cache.
• then go back and choose "install zip from sdcard1 (external sdcard)"
• and navigate to your kernel-Lanchon-TRIM-IsoRec and flash it.
• install arnab isorec recovery twrp zip by the gangster
• reboot your recovery, you will find the TWRP installed, now wipe system and data and cache and dalvik and install your nogut rom and the correct gapps.
that's it
Alternative Method
DON'T use odin to flash pit, just use it to flash the kitkat compatible recovery.
• flash Kitkat Compatible recovery with odin.
• in recovery flash kernel-Lanchon-TRIM-IsoRec and then flash twrp 3 isorec.
• and reboot recovery, then in TWRP 3 flash lanchon repit tool.
Lanchon repit tool is a simple flashable zip that can be edited to split the partition in desired way, read more about it in the official thread
This method was recommended by @TriboDoP
All credits goes to our great Developers.
MigoMujahid said:
The TWRP you are trying to install requires a kernel that supports isorec, so you must have that kernel first.
To have isorec support:
Note: -the rom and the isorec recovery and nogut rom and gapps -in short: all files- should be put in external sdcard because the internal sdcard will be wiped in the procedure-
1-you should install latest CM11, you can easily flash it using a
Kitkat compatible recovery, flash the recovery using Odin along with a pit that has 1GB system or more,
1.5GB PIT Files by the.gangster or 1GB PIT Files by ELgmal 1GB is enough
2-after that, reboot to recovery:
• wipe data
• wipe cache
• navigate to "mount" and format system and internal sdcard
• go back and navigate to "advanced" and wipe Dalvik cache.
• then go back and choose "install zip from sdcard1 (external sdcard)"
• and navigate to your cm11 rom and install the rom
• install arnab isorec recovery twrp zip by the gangster
• reboot your recovery, you will find the TWRP installed, now wipe system and data and cache and dalvik and install your nogut rom and the correct gapps.
that's it
Alternative Method
• flash Kitkat Compatible recovery with odin.
• in recovery flash cm11 with twrp 3 isorec.
• and reboot recovery, then in TWRP 3 flash lanchon repit tool.
Lanchon repit tool is a simple flashable zip that can be edited to split the partition in desired way, read more about it in the official thread
This method was recommended by @TriboDoP
All credits goes to our great Developers.
Click to expand...
Click to collapse
WOW IT WORKED! THANK YOU THANK YOU THANK YOU!
I used the following files:
SAMSUNG_USB_Driver_for_Mobile_Phones v1.5.51.0.exe
Lineage-11-20170115-UNOFFICIAL-i9100.zip … (CM11)
CWM-KitKatCompatible-i9100.tar
Odin3 v3.07
PIT Files: I91001GB_6GB.pit
Lineage 14.1 Rom: cm-14.1-20161225-UNOFFICIAL-i9100.zip
TWRP: twrp-3.0.2-1-i9100.img, recovery-the.gangster-IsoRec-TWRP-3.0.2-1-i9100.zip
open_gapps-arm-7.1-nano-20170225.zip
All went well following the upgrade of SAMSUNG USB Driver for Mobile Phones 1.5.27.0.exe to SAMSUNG_USB_Driver_for_Mobile_Phones v1.5.51.0.exe. Odin 3 v3.07 had communication problems in download mode with the earlier drivers.
I followed your instructions to the letter (printed and ticked as I progressed) and only had one issue when it came to formatting the internal sdcard ….. I didn’t know what format so I selected “default” which worked.
I used a PIT file I had rather than your files simply because I didn’t know which one of your files to choose … too many options! I didn't fully appreciate the difference between them?
What can I say but Thank You …. This must be the simplest and BEST GUIDE out there for somebody going from a stock 4.1.2 to 7.1.1
One last question ..... how do I read my SD card (external) now that I have flashed my phone with 7.1.1?
Windows can see the SD card but wont let me read the contents. I have read https://www.reddit.com/r/Android/comments/3nnkaa/cant_access_android_device_internal_storage_from/ and put the phone into MTP for the USB.
Jacbjacb said:
One last question ..... how do I read my SD card (external) now that I have flashed my phone with 7.1.1?
Windows can see the SD card but wont let me read the contents. I have read https://www.reddit.com/r/Android/comments/3nnkaa/cant_access_android_device_internal_storage_from/ and put the phone into MTP for the USB.
Click to expand...
Click to collapse
It should work, I'm using AICP 12.1 (7.1.1) build 7 Feb, and it's working when i set it to MTP, but sometimes i have to change the cable, try changing the cable or use another USB port.
I installed AICP because official LineageOS 14.1 is buggy these days.
Thanks for the tip i forgot when formatting internal sdcard using default, i edited the guide and added it to my signature so every one can easily find it.
There are good talks about other nogut roms like crDroid and xenonHD, i would try them, but it would take time and i only have one s2 and it's my daily driver, so i couldn't, but many people recommended them.
I'm happy that i was able to help you, and thank you for telling me that my guide was easy, i was afraid that it might be complicated or something
Regards Migo
---------- Post added at 10:28 PM ---------- Previous post was at 10:22 PM ----------
Jacbjacb said:
One last question ..... how do I read my SD card (external) now that I have flashed my phone with 7.1.1?
Windows can see the SD card but wont let me read the contents. I have read https://www.reddit.com/r/Android/comments/3nnkaa/cant_access_android_device_internal_storage_from/ and put the phone into MTP for the USB.
Click to expand...
Click to collapse
Oh, you meant the external sdcard, have you mount it after the first boot, you must have got some notification about it.
If you didn't, navigate to storage in settings and choose the external sdcard and you will be asked to mount it as a "portable storage" or an "internal storage", choose "portable storage".
Jacbjacb said:
One last question ..... how do I read my SD card (external) now that I have flashed my phone with 7.1.1?
Windows can see the SD card but wont let me read the contents. I have read https://www.reddit.com/r/Android/comments/3nnkaa/cant_access_android_device_internal_storage_from/ and put the phone into MTP for the USB.
Click to expand...
Click to collapse
You can use recovery to transfer between computer and phone.(in case the rom fails to do that)
Greetings!
I'd like to present a TWRP recovery for the single-sim Xperia X. This release works on Xperia X F5121 and F5122
DISCLAIMER:
I'm not responsible for any damage done to your device. You have been warned.
REQUIREMENTS
Unlocked bootloader
Working ADB and Fastboot (You can get the latest version through Android Studio or by visiting this site)
FEATURES
MTP support
ADB Sideload
Backups and restores almost every partition
Full SELinux support
Working encryption. You can access /data within recovery
NEEDS TESTING
USB-OTG
DOWNLOADS
INSTALLATION
Unlock the bootloader
Download the file
Put the following code in CMD/Terminal:
Code:
fastboot flash recovery twrp-3.1.1-suzu-*.img
//Replace * with the version you want to flash
Unplug the cable
Press Volume Down + Power to activate the recovery. When installed properly, the device should vibrate funnily, purple LED should appear and after a couple of seconds you should see the TWRP screen.
Enjoy!
BUILD
You need to sync the OmniROM and vendor blobs from DonkeyCoyote. You can find my sources on GitHub.
android_device_sony_loire_common
https://github.com/omnirom/android_bootable_recovery/commits/android-7.1
Thanks:
@grayleshy - for initial TWRP
@AndroPlus for some of his flags
OmniROM team for sources
If you find my work useful, consider buying me a cup of coffee
[TWRP] TWRP 3.1.0 for Xperia X
Old OP below:
Team Win Recovery Project 3.1.0
REQUIREMENT:
- Unlocked bootloader
FEATURES:
- MTP support
- USB OTG storage support
- Covers most partitions for nandroid backups
- ADB root
- Full SELinux support
- Support for partition decryption
Download: Dropbox
Installation via the bootloader (Platform-tools (adb & fastboot))
Code:
fastboot flash recovery recovery.img
Running TWRP: turn the phone off, wait 5 seconds, then pinch at the same time the power key and the volume down key until the device vibrates, release the keys. Recovery starts within 5-10 seconds.
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
Special thanks kistigun for testing recovery on the device.
Changelog: twrp.me
TWRP was going on OmniRom 7.1 sources and XperiaDeveloper.
SOURCEs: Suzu; loire; Common.
Nice work! Finally no more decryption problems on the X!
Working well, thanks!
One question ; is it possible to reboot the recovery via twrp reboot menu (or use an app like flashfire /flashify)? When I've tried the phone boots normally instead.
baddesthad said:
One question ; is it possible to reboot the recovery via twrp reboot menu (or use an app like flashfire /flashify)?
Click to expand...
Click to collapse
Unfortunately the reboot Recovery does not work from the specifics of the section, but in the future maybe will be fixed. If I don't find how to fix that button will be removed.
samavar89 said:
Unfortunately the reboot Recovery does not work from the specifics of the section, but in the future maybe will be fixed.
Click to expand...
Click to collapse
Good to know, thanks for clarifying
Is there a difference to the 3.1.0 TWRP recovery from the Poison thread?
Oel said:
Is there a difference to the 3.1.0 TWRP recovery from the Poison thread?
Click to expand...
Click to collapse
Yes, this TWRP version has decryption problem fixed. So you can acces internal memory(and make a full backup) without the need of doing a full whipe & format /DATA
kistigun said:
Yes, this TWRP version has decryption problem fixed. So you can acces internal memory(and make a full backup) without the need of doing a full whipe & format /DATA
Click to expand...
Click to collapse
Ah...
Ok, Thanks!
kistigun said:
Yes, this TWRP version has decryption problem fixed. So you can acces internal memory(and make a full backup) without the need of doing a full whipe & format /DATA
Click to expand...
Click to collapse
No,
don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup...
someone knows a recovery that finally works?
robby.pgn said:
No, don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup...
Click to expand...
Click to collapse
This problem is strange, please provide a log recovery.
I flashed this on my xperia x dual on nougat 7.0
I can go to recovery but when i try to turn on the phone normally it says "The phone is corrupt and cant be trusted bluh bluh..."
it says press power button to continue but when i press it screen turns off and nothings happens
what should i do?!
Kianush said:
I flashed this on my xperia x dual on nougat 7.0
I can go to recovery but when i try to turn on the phone normally it says "The phone is corrupt and cant be trusted bluh bluh..."
it says press power button to continue but when i press it screen turns off and nothings happens
what should i do?!
Click to expand...
Click to collapse
In Your kernel there is support for DM-Verity and Sony RIC?
it's stock kernel man, I unlocked bootloader and flashed stock nougat for xperia X dual sim
I just wanna root it, if there is any other way pls help me out
-----
btw after this problem i used flashtool to flash system and kernel from stock rom to be able to use my phone again
robby.pgn said:
No,
don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup...
someone knows a recovery that finally works?
Click to expand...
Click to collapse
Kianush said:
it's stock kernel man, I unlocked bootloader and flashed stock nougat for xperia X dual sim
I just wanna root it, if there is any other way pls help me out
-----
btw after this problem i used flashtool to flash system and kernel from stock rom to be able to use my phone again
Click to expand...
Click to collapse
use this tool/guide to make a rooted kernel(and edit DM-Verity and Sony RIC): https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
grayleshy said:
Team Win Recovery Project 3.1.0
Click to expand...
Click to collapse
I've installed and tried this TWRP in my Xperia X with MM. Very nice that it can access the data partition! I did not try to install any zip yet.
Some problems I've seen:
dmesg.log: no output
recovery.log: https://pastebin.com/EwbtuC9q
What is interesting in the output:
Code:
I:cmd: /sbin/exfat-fuse -o big_writes,max_read=131072,max_write=131072 /dev/block/mmcblk1p1 /external_sd
CANNOT LINK EXECUTABLE "sh": cannot locate symbol "__fwrite_chk" referenced by "/sbin/busybox"...
I:exfat-fuse failed to mount with result '', trying vfat
I:Unable to mount '/external_sd'
I:Actual block device: '/dev/block/mmcblk1p1', current file system: 'vfat'
Looks like something is not right with the busybox in the image. Maybe it is that what is causing the external sdcard (in my case in exfat filesystem) not being mounted?
Thanks
robby.pgn said:
don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup.
Click to expand...
Click to collapse
This problem is almost resolved, just need to test, but I don't have time to compile recovery. In the test version recovery without decryption, problem solved.
juliompinheiro said:
I've installed and tried this TWRP in my Xperia X with MM. Very nice that it can access the data partition! I did not try to install any zip yet.
Some problems I've seen:
dmesg.log: no output
recovery.log: https://pastebin.com/EwbtuC9q
What is interesting in the output:
Code:
I:cmd: /sbin/exfat-fuse -o big_writes,max_read=131072,max_write=131072 /dev/block/mmcblk1p1 /external_sd
CANNOT LINK EXECUTABLE "sh": cannot locate symbol "__fwrite_chk" referenced by "/sbin/busybox"...
I:exfat-fuse failed to mount with result '', trying vfat
I:Unable to mount '/external_sd'
I:Actual block device: '/dev/block/mmcblk1p1', current file system: 'vfat'
Looks like something is not right with the busybox in the image. Maybe it is that what is causing the external sdcard (in my case in exfat filesystem) not being mounted?
Click to expand...
Click to collapse
This issue failed to reproduce, and yet there is no solution. You the problem is not in Busybox, and something else.
grayleshy said:
Running TWRP: turn the phone off, wait 5 seconds, then pinch at the same time the power key and the volume down key until the device vibrates, release the keys. Recovery starts within 5-10 seconds.
Click to expand...
Click to collapse
For whatever reason I'm not able to boot into TWRP like I should be. I've used the poison version of TWRP before so I know what to do, and yet the phone will just boot normally despite holding volume down and power when off.
I know that TWRP is installed though as I am able to boot to it if I first boot to the bootloader using a USB cable but that is very cumbersome to do though.
grayleshy said:
This issue failed to reproduce, and yet there is no solution. You the problem is not in Busybox, and something else.
Click to expand...
Click to collapse
Clearly for the image available at your dropbox there are some libraries dependency errors, not only for the 'busybox', but also for other binaries that are in /sbin.
I do not know why this issue is only happening on my device since you said you can't reproduce this error. If there is anything I can do to help solve this strange behavior, count on me. I am an advanced linux user, but not too familiar with android specifics.
On latest 333 ROM for UK so that fingerprint scanner works on my Xperia X F5121.
I also modified by kernel/boot so that TWRP doesn't brick (actually boot loop) the device like it did the first time. After using these awesome instructions flashing TWRP recovery from here didn't kill the device any longer: https://forum.xda-developers.com/crossdevice-dev/sony/root-root-stock-firmware-modern-sony-t3558904
I was able to take an early nandroid backup before a bunch of Titanium restores, etc. Now I get stuck at "Backing up data" step and it literally doesn't move to the next file. Attaching an image of where I get stuck. FYI, I do use password encryption on the backup and I did disable MD5 creation... still just stuck.
Next tests are to:
see if the stall is on the same exact file number
try no encryption
do a check disk (fsck) type of repair just in case I have corruption --- on my brand new device
Any suggestions greatly appreciated!
UPDATED:
I only back up Boot, System & Data (the default)
On second attempt it stopped at file 18869 of 22065 --- so it does jump and not consistently stop at a certain file.