Related
(Avis aux intéressés, j'ai parti une discussion en français sur Frandroid.)
Hello everyone,
Here's my ArpegGioMod ROM, for the Galaxy Gio GT-S5660M. Current (and final) version is 0.9
(ArpegGioMod has had over 1500 downloads! Thanks!)
Features:
Rooted
Deodexed apps and framework. (Optional)
Working FM radio (remember, your headphones are the antenna!)
No power on sound.
Restored support for the normal Android bootanimation.zip format. Right now it's just running the "base" animation (with the green Android text). I'm open to suggestions/logos/proposals!
CRT screen off animation re-enabled, you do need to turn back animations on in the settings to see it.
ADW Launcher (I just used the "standalone" version and placed it in /system/app/, not the cleanest way, but it works, and leaves you the choice between that and Touchwiz Launcher)
Removed all Bell software, as well as some Samsung apps.
New in 0.6
Added options to the power button menu: Reboot (Normal), Reboot Recovery Mode and Reboot to Download Mode.
Car mode.
New in 0.7
Phone will not relock itself to Bell after doing a factory reset without a SIM card in the phone.
Changed the default browser homepage to Google instead of Bell's.
New in 0.8
Phone will not relock itself to Bell after doing a factory reset without a SIM card in the phone. (Turns out I mixed up some files and uploaded a version with Bell apps left in the CSC folder, along with the unmodified customer.xml. Not an issue, until someone did a factory reset.)
Unsecure kernel. So now, adb remount and push work. adb shell is permanently root.
New in 0.9
CWM installation instead of Odin
Using Phiexz's customized stock ROM kernel, with support for both ext4 and RFS partitions. The kernel also includes different wifi drivers, and they work for me!
Updated superuser apps (3.0.7) and binaries (3.0.3.2). The upgrade of su from 3.0.3 to 3.0.3.2 seems to have fixed whatever caused the crashes.
Reodexed, this seems to provide better performance.
Removed the annoying "Full charge" notification.
Enabled native SIP functionality. (Untested.)
Removed the "Android Tips" widget.
Added the "Roboto" FlipFont apk, found on XDA.
No-frills CPU Control 1.20
Google Application updates:
Android Market 3.4.4
Gmail 2.3.5.2
Google Maps 6.3.0
Google Search 1.3.3.247963
Street View 1.7.1.0
Voice Search 2.1.4
YouTube 2.3.4
To do:
Implement BLN by patching /system/framework/services.jar
Things I will not do. (Or at least, not without significant assistance from those requesting it.)
Additional languages.
Files required to install 0.9:
Galaxy Gio ext4 converter
Backup RFS User Data (Optional)
Restore User Data to ext4 (Optional)
ROM Zip file: ArpegGioMod 0.9 MD5 hash: 010DA7C4542537443D2DD2E9BDBAFC43
Re-odex script (Optional)
Short Version 0.9 Installation instructions:
If you're upgrading from a stock ROM or ArpegGioMod 0.8: Backup User Data Script
(You'll probably want to delete the two tar.gz files remaining on your SD card afterwards.)
As required: format from RFS to ext4.
If you're upgrading from a stock ROM or ArpegGioMod 0.8: Restore User Data Script
Flash ROM zip
Re-odex as required
Detailed Version 0.9 Installation instructions:
(Or, the "this is my first time trying this out and frankly I'm a little overwhelmed with information" version.)
I'm going to start this one with a brand new, freshly out of the box Gio. I will however assume that you already have a working Odin and Android SDK install. Plenty of tutorials out there for both. (See links below for the correct Odin version.)
Copy the zip files to your MicroSD card.
Reboot your phone in Download Mode. (Hold Volume Down + Home + Power. There will be a pink warning screen. Press Volume Up.)
Flash ClockWorkMod Recovery with Odin.
Reboot the phone into Recovery Mode. (adb reboot recovery, or Home + Power)
"install zip from sdcard"
"choose zip from sdcard"
Install the ext4 converter zip.
Install the ROM zip.
Install the Re-odex script zip.
Reboot
Optional: adb shell, then dd if=/dev/block/bml5 of=/sdcard/bml5 bs=4096 to get your unlock code as per Tweakradje's unlock tutorial.
Enjoy!
Version 0.8 Installation instructions:
Un7zip and flash with Odin.
I strongly suggest you do a factory reflash and reset if you're flashing from something other than stock or ArpegGioMod.
Version 0.8: http://www.mediafire.com/?nxp0ce21909c676 7-Zip file MD5 hash: 6CEE73812AF9D30189A5F808CE0A7DEA
(Thanks Koodiifin!)
Tools and additional information:
CWM 5.0.2.7-based recovery, compiled for the 5660 by Phiexz, modified for the 5660M by Peteragent5: http://forum.xda-developers.com/showthread.php?t=1493932
"Supersafe" bml5 unlock method by Tweakradje, originally meant for the GT-I5500, should also work with little or no modifications for the 5660M: http://forum.xda-developers.com/showthread.php?t=828534
My other thread from which all of this started: Samsung Galaxy Gio GT-S5660 and GT-S5660M Partition Mapping This thread contains links to a rooted, but otherwise completely stock ROM backup I made prior to starting my work on ArpegGioMod.
Older Clockworkmod-based recovery, meant for the Europe/Asia 5660, but working fine on the 5660M: http://particle.blurringexistence.net/samsung-gt-s5660/clockworkmod-recovery
Tutorial on flashing with Odin, with link for the appropriate version for our phone.
Goodbye,
Darkshado
Just installed ArpegGio on my Virgin Mobile 5660M and it seems to be working great. 3G wifi and FM are working, plus I am glad to be rid of a bunch of carrier garbage apps. Thanks Darkshado I can't wait to see a2sd in there. Could I install it the manual way on this FW?
OT:
Thanks too Darkshado for all your tips for 5660M owners. I got mine 3 days ago, rooted and unlocked on day 2, flashed your FW on day 3. Reminds me of my days making custom OS for my blackberry
hardran3 said:
Just installed ArpegGio on my Virgin Mobile 5660M and it seems to be working great. 3G wifi and FM are working, plus I am glad to be rid of a bunch of carrier garbage apps. Thanks Darkshado I can't wait to see a2sd in there. Could I install it the manual way on this FW?
Click to expand...
Click to collapse
If you mean by modifying your boot.img ramdisk, yes. That's what I've been unable to do. I suspect an outdated/incompatible mkbootimg binary, and can't download the source make a new one as of writing this since kernel.org is still down.
If you're feeling adventurous, you could also try flashing an Euro 5660 boot.img. But I can't guarantee there won't be other issues.
OT:
Thanks too Darkshado for all your tips for 5660M owners. I got mine 3 days ago, rooted and unlocked on day 2, flashed your FW on day 3. Reminds me of my days making custom OS for my blackberry
Click to expand...
Click to collapse
You're welcome.
Hi, This is going to be my first flash for my S5660M. I've a small question for it. What mode should I choose in ODIN? Do I need to care about the ops file?
Sorry for my newbie question. Thank you.
You have to rebuild kernel with ext support. To create system.rfs or other *.rfs you have to type in console
Code:
mkfs.ext4 -O ^huge_file system.rfs
or it won`t boot. Of course you need modify initscripts. You can change from rfs to ext4 and it should work.
My problem is that due to the troubles at kernel.org I haven't been able to download the AOSP source yet.
I already suspected it wouldn't work with the stock kernel boot.img before trying.
For the conversion, I used a modified Galaxy Tab ext4 conversion update with the mkfs binaries included. That worked like a charm, CWM mounted the partitions, no questions asked.
I'll have to wait until an official AOSP repo comes back online to take this further.
Goodbye,
Darkshado
Sent from my Nexus S using XDA App
It will work with stock kernel, but you need change build config.
Hi
Just installed your rom this sunday... It work nice and no problem!
Was wondering, is the factory reset from the cwm is better than the one within the phone app? And or is the same?
And keep up the good work it is really appreciated
Thx Dark!
Sent from my GT-S5660M using XDA App
Darkshado said:
Hello everyone,
New in 0.6
[*]Added options to the power button menu: Reboot (Normal), Reboot Recovery Mode and Reboot to Download Mode.
[*]Car mode.
[/LIST]
Goodbye,
Darkshado
Click to expand...
Click to collapse
Nice job, very nice.
Is it duable to create that option in a aditional zipfile.
That you can flash it in recoverymode with a other rom????
You would make me very happy with that.
You have to modify framework-res.apk framework.jar and android.policy.jar for this to work, and it requires editing Smali code.
I did it by loosely following guides meant for the I9000 found here.
You could always push those files from my ROM to give it a try like that, but I wouldn't count on the framework from the 5660M to be fully compatible with the 5660 (which I understand you have from some of your other posts).
Question: has anyone else managed to re-Sim-lock their phone?
It's happened to me inadvertently, twice. Not knowing why on Earth the phone did this, I decided to get to the bottom of things.
The unlock code from bml5 still works, but I find this annoying to say the least.
I found some strings in the CSC files (customer.xml to be exact) that seemed to tell the phone what network to lock itself to.
I managed to make the phone relock itself by going into recovery, wiping user data, and rebooting the phone without a SIM card in. Checking lock status with *#7465625# shows Network Lock [ON]
I turned off the phone, put a foreign SIM back in, unlocked the phone again, and re-wiped user data, leaving the non-Bell SIM in for the first boot. No relock.
I relocked the phone as above. Rebooted into recovery and pushed modified customer.xml files, without the network lock strings, to my /system/csc/ and /system/csc/BMC/system/csc/ directories. No relock!
Those modified CSC files are going to be included in ArpegGioMod from now on.
Goodbye,
Darkshado
Darkshado said:
You have to modify framework-res.apk framework.jar and android.policy.jar for this to work, and it requires editing Smali code.
I did it by loosely following guides meant for the I9000 found here.
You could always push those files from my ROM to give it a try like that, but I wouldn't count on the framework from the 5660M to be fully compatible with the 5660 (which I understand you have from some of your other posts).
Click to expand...
Click to collapse
Hi, thx for the reply
Yes i have the 5660 ( no M ).
But i don't have a linux machine........
And i need that to compile those files.
I supose a linux-live dristri doesn't ad up for the job
Amadeus01 said:
Hi, thx for the reply
Yes i have the 5660 ( no M ).
But i don't have a linux machine........
And i need that to compile those files.
I supose a linux-live dristri doesn't ad up for the job
Click to expand...
Click to collapse
I think a live distro would work fine... Me I installed Vmware player (free) to run a virtual ubuntu machine and it work fine for editing some of the the tar file... so a live distro would even be better i'm sure!
Sent from my GT-S5660M using XDA App
I unlocked with safe bml5 trick and wiped a couple of time but i did not put back a non bell sim since then... So i dont really know...
Did you use some script or some like that in you Rom? Because I got like almost 400-500 more point on antutu benchmark.... Nice
Sent from my GT-S5660M using XDA App
theboo23, Amadeus01: Practically all of my ROM work has been done under Windows so far!
You need:
Java JDK
Android SDK
apktool
Cygwin
A hex editor (I've used Frhed so far)
Notepad++ (Free, open source, tons of features: syntax highlighting and Unix line ending support to name a few)
(Optional) A program that can open FAT format image files such as MagicISO, to extract files from RFS partition images.
(Optional) xUltimate, to simplify deodexing a great deal.
(Optional) 7-Zip
I have installed Ubuntu (on an external USB drive with Wubi and Grub4DOS) to attempt boot.img and kernel modifications, and to build from AOSP/CyanogenMod source.
However, kernel.org, which hosts AOSP repositories, is still down almost three weeks after having been hacked. So those parts of my project have been stalled in the meantime as I hadn't downloaded the source beforehand.
theboo23: There have been multiple reports of deodexing increasing performance, that might explain the points increase on the benchmark. To be frank, I don't bother with them unless I have something really specific to test.
Goodbye,
Darkshado
Darkshado said:
Those modified CSC files are going to be included in ArpegGioMod from now on.
Click to expand...
Click to collapse
By "from now on" I suppose you mean ver 0.7 included which is also on the changelog for it. However, it's exaclty after I flashed 0.7 (from 0.6 and stock before that) that my phone re-locked again and I had to use the unlock code (which I retreived while ago using bml5 method and still keep). I wiped before flashing 0.6 on top of stock, but did now wipe before flashing 0.7 on top of 0.6.
By the way, I knew already that at one point I will need my unlock code again. Having unlocked 6 or 7 5660Ms in the last week I have noticed that, once unlocked for a network (say, Fido) and you put a different SIM (Chatr), it gets locked again! Not only that, if you put the Fido SIM back, it is still locked. You have to enter the unlock code again, and luckily it's always the same. So, I resorted to writing down the code on the back of the phone under the back plate for further reference
And a couple of questions: your ROM has only one file/partition in it - system.rfs - and apparently this is the only thing that it replaces, everything else remains stock. One other custom ROM available on this site contains two files in the .tar - system.rfs and boot.img.
Q1: will it be safe to flash that other ROM on a 5660M having in mind it only replaces those two files/partitions? I know you already answered this before, just being extra cautious
Q2: if I want to return to ArpegGioMod after that, how do I proceed? Where do I get the boot.img from? Posible answer here: I have made a full backup via CWM of the stock ROM. It contains boot.img. Can I insert it in your .tar and flash and expect to get the same as flashing ArpegGioMod directly on stock?
Q3: if I get the system.img (renamed to system.frs) and boot.img from the SWM backup, put them in a .tar and flash, will that give me stock phone?
stfn74 said:
By "from now on" I suppose you mean ver 0.7 included which is also on the changelog for it. However, it's exaclty after I flashed 0.7 (from 0.6 and stock before that) that my phone re-locked again and I had to use the unlock code (which I retreived while ago using bml5 method and still keep). I wiped before flashing 0.6 on top of stock, but did now wipe before flashing 0.7 on top of 0.6.
Click to expand...
Click to collapse
I tried a couple more wipes and SIM swaps (T-Mobile USA, Koodo and Telna) with no relock occurring, so I hate to say, but I'm a bit stumped if there's something else than the CSC files causing this.
By the way, I knew already that at one point I will need my unlock code again. Having unlocked 6 or 7 5660Ms in the last week I have noticed that, once unlocked for a network (say, Fido) and you put a different SIM (Chatr), it gets locked again! Not only that, if you put the Fido SIM back, it is still locked. You have to enter the unlock code again, and luckily it's always the same. So, I resorted to writing down the code on the back of the phone under the back plate for further reference
Click to expand...
Click to collapse
I take it you work at a Rogers/Fido kiosk or store right? You're probably going to get more data on this than I ever will. I too wrote my code in the battery door just in case after it relocked a second time.
Q1: will it be safe to flash that other ROM on a 5660M having in mind it only replaces those two files/partitions? I know you already answered this before, just being extra cautious
Click to expand...
Click to collapse
Should be safe, if the boot.img is meant for the Euro 5660, you could encounter some bugs. I haven't tested those boot partitions and kernels.
Q2: if I want to return to ArpegGioMod after that, how do I proceed? Where do I get the boot.img from? Posible answer here: I have made a full backup via CWM of the stock ROM. It contains boot.img. Can I insert it in your .tar and flash and expect to get the same as flashing ArpegGioMod directly on stock?
Click to expand...
Click to collapse
You could just restore that nandroid backup.
Otherwise, tarring the boot.img with Cygwin and flashing with Odin should work. Then flash ArpegGioMod. Or make a single tar file with both partitions in Cygwin.
Here's a "universal" command: tar -H ustar -c amss arm11boot mibib oemsbl qcsbl boot.img recovery.img csc.rfs system.rfs data.rfs efs.rfs > GT-S5660M_MUGKG3.tar
I put it in a text file with the .sh extension, in cygwin/bin/ making it a command that can be invoked directly. (It's actually part of a set of batch files I've made to automate the copy and preparation of ArpegGioMod updates.)
Q3: if I get the system.img (renamed to system.frs) and boot.img from the SWM backup, put them in a .tar and flash, will that give me stock phone?
Click to expand...
Click to collapse
No reason it shouldn't.
Darkshado said:
I take it you work at a Rogers/Fido kiosk or store right?
Click to expand...
Click to collapse
No, I'm just an user, my job has nothing to do with mobile business. It's just Futureshop had a great deal on 5660Ms last week and half of my family and friends got one I was the first to root and unlock mine so... had to do it with everybody else's. I'm playing with custom ROM flashing now and want to make sure I got everything right, because I suspect I will be doing it number of times.
So I'm using the opportunity to say "Thank you!" for your work!
i used this rom with m 5660m and i still got wifi problems. wont turn correctly. im seeing you mention about ops file and boot img modding.dont kno how to do that
chairsz said:
i used this rom with m 5660m and i still got wifi problems. wont turn correctly. im seeing you mention about ops file and boot img modding.dont kno how to do that
Click to expand...
Click to collapse
Did you flashed a 5660 rom? You'll need to flash the stock 5660m rom first. The link is here;
http://forum.xda-developers.com/showthread.php?t=1233719
Hey guys
I am completely new in this topic. I just got an Samsung Galaxy Tab S (SMT700 Wifi) as a present a few days ago. Its my first android device I had so far.... so everyone will call me "noob" and I am okay with it DD
When I realised that there are different android os development projects like CM and Paranoid, I become interested in trying them out. so...
1.) Is it possible to brick the android device completely or is there something like an recovery/dfu mode in iOS devices?
2.) Can I go back to the stock OS contributed bey samsung itself (Touchwiz Kitkat)? If yes are this files online?
3.) Does I need special hardware to perform a custom rom flash? (micros card/special OS on pc (linux,....)
4.) Does the CM blck mod in the official forums contains alle required drivers and blobs already to perform gpu tasks and so on? (are there currently downsides swell?)
Thx :fingers-crossed:
androidnoob222 said:
Hey guys
I am completely new in this topic. I just got an Samsung Galaxy Tab S (SMT700 Wifi) as a present a few days ago. Its my first android device I had so far.... so everyone will call me "noob" and I am okay with it DD
When I realised that there are different android os development projects like CM and Paranoid, I become interested in trying them out. so...
1.) Is it possible to brick the android device completely or is there something like an recovery/dfu mode in iOS devices?
2.) Can I go back to the stock OS contributed bey samsung itself (Touchwiz Kitkat)? If yes are this files online?
3.) Does I need special hardware to perform a custom rom flash? (micros card/special OS on pc (linux,....)
4.) Does the CM blck mod in the official forums contains alle required drivers and blobs already to perform gpu tasks and so on? (are there currently downsides swell?)
Thx :fingers-crossed:
Click to expand...
Click to collapse
1. There is bootloops but hardbricks are rare. You can enter recovery and download mode(flash stock rom on broke os) in a bootloop. Just hold power, home or vol up for recovery and home +power +vol down for download mode.
2. Yes you can go back to any version of stock os unlike apple you have to be on the latest. The files are online for your device at sammobile. (google it) and also samsung updates.
3. All you need to perform a custom rom flash is a custom recovery called twrp and your device. Theres an app on google play for installation of it. (search on youtube on how to do so). But thats just flashing zip based roms(which most custom roms are). For stock rom installation, you will need a pc and a application called odin 309 to flash a stock md5 file rom in which you will need to be in download mode (like installing new update from itunes).
You will need to backup your whole rom with twrp before flashing a custom rom. You may need a micro sd if your short on space. You will also need to be rooted to install custom roms. Please go to the cfautoroot thread of your device to root your device in which you will viod warrenty.
4. Cm rom as of now still has bugs but is still useable for games and such. There should be a list of bugs on the thread and might have some missing features such as ir blaster and finger print scanner. Battery life may vary. So there are downsides.
5. I can go into more depth of custom stuff and flashing if you wish. Right now my fingers hurts xD. Hope this helps!
1) it is very, very unlikely even if you try intentionally to do so
2) yes, no problem. google for Samsung Firwares, it's all online
3) windows PC, Odin Software, and an USB cable, that's all. You can do it with Linux if you prefer. Some Roms are installed via zip file from the device itself, then you need to flash a new Recovery partition first, that is able to do so
4) ?
Thx you very much for the help !
After reading a lot about this topic it seems to be not as difficult as I thought it would be.
But I don't get one thing. Why does I need to make a proper backup only for the flashing propos? If I flash my internal memory, all data will be replaced. And if it goes wrong I will be able to do a complet software reset with odin and the original samsung image found in the Internet?! So why I have to make a backup (there is no data in my current tap I will need in the future)?
And does the cf chain root flash the OS or the firmware ?
As my understanding tell me that the firmware is something comparable to a bios , which should never be flashed to maintain stability.
So as my logic goes further if my device is rooted, after a proper reset it will not be rooted anymore? (Android stock reset function in settings)
Or does armbased devices not have a normal firmware/bios as I mentioned ? And something in the bootprocess itself is manipulated to anable root access?
Hopefully you get what i mean :angel:
androidnoob222 said:
Thx you very much for the help !
After reading a lot about this topic it seems to be not as difficult as I thought it would be.
But I don't get one thing. Why does I need to make a proper backup only for the flashing propos? If I flash my internal memory, all data will be replaced. And if it goes wrong I will be able to do a complet software reset with odin and the original samsung image found in the Internet?! So why I have to make a backup (there is no data in my current tap I will need in the future)?
And does the cf chain root flash the OS or the firmware ?
As my understanding tell me that the firmware is something comparable to a bios , which should never be flashed to maintain stability.
So as my logic goes further if my device is rooted, after a proper reset it will not be rooted anymore? (Android stock reset function in settings)
Or does armbased devices not have a normal firmware/bios as I mentioned ? And something in the bootprocess itself is manipulated to anable root access?
Hopefully you get what i mean :angel:
Click to expand...
Click to collapse
1. Sometimes odin and kies will fail for you. Twrp backups is to be really safe if you get bootlooped and odin fails for you. Its much easyer to restore a twrp backup and easy to make one. Its just if odin or kies fails which twrpnwould be your only hope. Just in case
2. Cfautoroot only flashes supersu and root. It keeps your apps and everything. So when you flash cfautoroot, it will say andriod is upgrading becuase its installing root and restoring back your apps.
3. After a full proper reset, it will not have root and revert back to stock. Thats where you flash cfautoroot to gain root again!
Hope this helps!
So as of now I managed to root my device and also created a twrc backup, which is now transfered to my sd card
Are there major differences between a rom flash with twrc recovery or odin?
androidnoob222 said:
So as of now I managed to root my device and also created a twrc backup, which is now transfered to my sd card
Are there major differences between a rom flash with twrc recovery or odin?
Click to expand...
Click to collapse
Most custom roms are to be flashed with twrp. Meanwhile stock roms/md5 is to be flashed with odin(firmware from website).
Again Thx you very much!! You are awesome!
I managed to install cyanogenmod its insanely fast compared to the touchwiz version
But there is one more thing I have to ask.
I installed TWR in the latest version but the klimwifi (2.8.XX) version (klimtwifixx was not avaible). Is this the right version?
Where exactly does TWR be installed. Afther the wipe and the format it stays, so I have no clue how it can be available even if the internel memory was formated?
I started TWR by the terminal (reboot recovery), becouse I have no clue how to start it instead by button pressing?
And there are no playstore how can i get it on cm11?
androidnoob222 said:
Again Thx you very much!! You are awesome!
I managed to install cyanogenmod its insanely fast compared to the touchwiz version
But there is one more thing I have to ask.
I installed TWR in the latest version but the klimwifi (2.8.XX) version (klimtwifixx was not avaible). Is this the right version?
Where exactly does TWR be installed. Afther the wipe and the format it stays, so I have no clue how it can be available even if the internel memory was formated?
I started TWR by the terminal (reboot recovery), becouse I have no clue how to start it instead by button pressing?
And there are no playstore how can i get it on cm11?
Click to expand...
Click to collapse
2.8 is the latest version of twrp. I dont think your device is klimwifixx. It should be klimwifi. What the wipe and and factory reset in twrp does is that it clears all your apps and wipe cache. It does not wipe any folders and it justs wipes your apps. So internal should not be affected unless you formatted it... You just need to swipe the factory reset on it when installing roms. For google play store you have to flash a file name gapps. There should be a link to it on the thread. To get into recovery, turn off your device, then hold power, home, vol up buttons at the same time to enter recovery. To exit recover just touch the reboot rectangle and hit reboot system. Hope this helps!
Okay now its clear TWRP replace the "downloade mode", which is the standard recoverymode
You said I do not need to format the disk, but why?
In linux distributions (debian for example) you will have similliar structure for example /var /bin /sbin /usr /proc,.....
If there is the stock touchwiz android it will have this structure listed above as well. So it will courrupt the os by overwriting this folders by a custom rom....
. Maybe you wont do it in the TWRP menue, because it will do it automatically by choose you custom rom install script in the zip?
How is the portioning in those devices? Maybe there are /dev/sda1 (android) and /dev/sda2 (with the recovery setup inside)....? I just want to understand those things
androidnoob222 said:
Okay now its clear TWRP replace the "downloade mode", which is the standard recoverymode
You said I do not need to format the disk, but why?
In linux distributions (debian for example) you will have similliar structure for example /var /bin /sbin /usr /proc,.....
If there is the stock touchwiz android it will have this structure listed above as well. So it will courrupt the os by overwriting this folders by a custom rom....
. Maybe you wont do it in the TWRP menue, because it will do it automatically by choose you custom rom install script in the zip?
How is the portioning in those devices? Maybe there are /dev/sda1 (android) and /dev/sda2 (with the recovery setup inside)....? I just want to understand those things
Click to expand...
Click to collapse
No no! Twrp replaces stock recovery. Download mode cannot be replaced. You enter it by holding power, vol down, home button when the device is off. Download mode is when you flash things. Recovery mode is when you clear cache or other stuffs. I have no idea with the linux stuff you explained but custom zip roms just adds some modifications and other stuff to the device. You would need to clear cache and factory reset so you wont have problems installing it. You can easyly go back to stock rooted by restoreing a backup you made in twrp. It has to do something with img and replacing those if thats what your talking about idk. No need to format as the rom add things to it. Just need to factory reset and cleae caches.
But now if I want to enter download mode for testing, it will boot into the twrp recovery. So as for me it looks like that it is already replaced..
androidnoob222 said:
But now if I want to enter download mode for testing, it will boot into the twrp recovery. So as for me it looks like that it is already replaced..
Click to expand...
Click to collapse
It shouldnt be as twrp only replaces recovery. Img did you try doing home, power, vol down?
Hi
I have a quick question I have the Galaxy tab S 10.5 wifi and was wondering can I install TWRP without the tablet being rooted?
Also there are some builds where it states that its rooted, debloated and de-knocked. Does this mean that they can be flashed without rooting the tablet and tripping knox.
Thanks for your replies, still trying to get my head around this.
So I have no access to a PC which means I can't create a flashable .zip for my phone, so would it be possible to manually flash images in TWRP and have it work? I know you can flash the .img files, but I'd rather ask here and know it will work, even if it is a tedious task to do, instead of try it and do it wrong or manage to hard brick it
**Edit**
I'm guessing an option could be Flashfire? I want to switch to CopperheadOS but I'm not sure how to do it without a PC
Managed to answer my own question after trial and answer
Since I didn't receive any responses, I took matters into my own hands and messed around with TWRP. I was successfully able to return to stock using images from Google. The only part you can't do is flash cache, bootloader, or radio. Radio doesn't change as far as I'm aware, so that is okay. I'm not sure what cache does, but I do know that flashing the bootloader is important. All I did was flash the matching update/OTA zip with the bootloader I had and it work. After booting, signing in, and restoring to a backup, I was able to update to the current version available for my device (Oreo, Nexus 5X). Now I know that I can flash stock images, you just need to flash .img files and make sure you have the right bootloader to go with them. I'm guessing there is no way to flash the bootloader with TWRP, and I won't try to because it isn't advised by anybody that uses TWRP, but I'll find more info. Maybe I can do this with Chainfire?
Any questions users have, I will try to answer to the best of my ability, and I'm sure others will see this because I get a few views every now and then
I know there is currently no TWRP for the X2 / X2 Pro devices.
But I wonder why / if it is so difficult to generate one?!
What do the TWRP developer need to create one?
A dump of the recovery partition? Should be possible with root - or not?
(BTW, which of the devices _is_ the recovery partition?)
What else is needed?
Bodenseematze said:
I know there is currently no TWRP for the X2 / X2 Pro devices.
But I wonder why / if it is so difficult to generate one?!
What do the TWRP developer need to create one?
A dump of the recovery partition? Should be possible with root - or not?
(BTW, which of the devices _is_ the recovery partition?)
What else is needed?
Click to expand...
Click to collapse
I would start here: https://forum.xda-developers.com/showthread.php?p=32965365#post32965365
Or if you speak Spain go to:
https://www.htcmania.com/showthread.php?t=1312725
Maybe member @nuv can help you as well.
AndroidenKalle said:
I would start here: https://forum.xda-developers.com/showthread.php?p=32965365#post32965365
Or if you speak Spain go to:
https://www.htcmania.com/showthread.php?t=1312725
Maybe member @nuv can help you as well.
Click to expand...
Click to collapse
Hi @Bodenseematze,
uh, well; unfortunately I got no X2 and do not know anything about the partition structure.
I didn't compile TWRP myself (e.g. for my X Pro ), so I can't give you hints about that either :crying:
The first link from @AndroidenKalle looks promising, I would start reading there.
If BQ doesn't change the way their phones handle the firmware, the bootloader locking and so on, maybe I can help in the later steps after building TWRP (?)...
edit: if you don't need TWRP but only Magisk, maybe take a look here: https://forum.xda-developers.com/aquaris-x-pro/how-to/root-magisk-bq-aquaris-x2-pro-custom-t3841795
Thanks for your answers.
I'm not sure if compiling TWRP from sources is the right direction for me :silly:
And the guide is really old - I'm not sure if it's still valid (especially because the X2 Pro is such a "a/b"-Device.
I thought about trying this:
[GUIDE]Porting TWRP without source
But I'm not sure about which partition I should use - or if the correct (recovery) partition is included in an official update.
I only see the boot.img - but as opposed to the above source porting guide our device has also two (_a/_b) of them...
And I'm also not sure which existing twrp binary I should use as base (arm64 and 1080x2160 screen resolution and maybe _a/_b support?)...
@AndroidenKalle: unfortunately I'm not able to speak Spanish...
And yes, of course I already have rooted my device with Magisk - but I really want to have TWRP possibilities (easily create flashable backup image, restore image without losing my data, easy flashing, easy access to all partitions, ....)
Apparently, there is a TWRP from aquaris-dev, downloadable from their Slack:
https://join.slack.com/t/aquaris-de...QyMWIwZTk4ZjllYjMxZWJhYzM0YzNhZWZkYTEwMzQ5ZDQ
Yes, that one seems to work at my X2 Pro device (tried with fastboot).
Soon after start it asks for a password when trying to mount the partitions.
In principal that's to decrypt the encrypted stock partitions - but that functionality is currently not available - so to install lineageos this TWRP is fine - for everything else (e.g. to make a backup of your stock image) not...
T-Mobile V30 H932 20s Stock Collection
Based on OEM 20s KDZ. Extracted and Repacked.
DISCLAIMER
Proceed at your own risk. I am not responsible for any damage to your device.
Flashing LAF WILL REMOVE TWRP from your laf partition and restore stock DL Mode
Bins in these packages are unmodified and you may need to flash no-verity-opt-encrypt and rctd remover after to keep force-encryption away.
REQUIRED
TWRP on LAF or Recovery
Latest Magisk Zip (if performing clean flash)
no-verity-opt-encrypt
rctd remover
FILE BREAKDOWN
None of these Zips flash the Recovery partition.
Besides StockLAF, these Zips DO NOT flash the LAF partition.
If you want to restore DL Mode and Stock LAF, you must flash the StockLAF package separately.
Bootloader: 20s Stock Bootloader ONLY
FullStock: Full 20s Stock Firmware Only (bootloader, modem, boot, system) - Instructions in Section A
Debloated w/Magisk: Boot+Debloated System + Magisk Root (force enc & dm-verity removed) - Instructions in Section B
StockLAF: Individual LAF image for returning to stock DL mode
WARNING
This firmware contains DTS libs and there are related changes within the Bootloader/Modem zips.
Anybody running a custom rom like LOS or RR will have sound problems if you flash these. (until a compatible build is released)
Unless you are already running 20r, anybody running the Debloated zip will have video/sound problems if you DO NOT flash these (FullStock contains both)
Thanks to @ChazzMatt for sharing this helpful info.
Global Instructions
Always make a backup first
If device has been encrypted, see encryption notes at the bottom before continuing.
A - FullStock
If coming from Nougat, Clean Flash is Recommended
Wipe Dalvik, System, Data, Cache... then flash
If coming from previous Oreo versions, Dirty Flash works fine. OS and Apps are updated.
Copy All Zips to SDCard
Flash h93220s_FullStock.zip
Flash Magisk
Flash no-verity-opt-encrypt
Flash rctd remover
Reboot to system and install Magisk Manager (if not installed)
B - Debloated with Magisk
You MUST flash FullStock, or Bootloader and Modem before flashing this to make sure all of your device firmware is up to date.
Be aware
This ROM does NOT flash LAF, recovery, bootloader or modem firmware directly.
Boot image has been patched to remove force encryption and dm-verity
This ROM has had several pre-loaded and system apps removed. If someone wants to send me a list of any additional apps that can be safely removed, i can update the rom to include them.
system/app/CloudPrint
system/app/Drive
system/app/Duo
system/app/EditorsDocs
system/app/EditorsSheets
system/app/Gmail2
system/app/GooglePay
system/app/LGAccount
system/app/LGAirDrive
system/app/LGAmazonAssistant
system/app/LGAmazonAttribution
system/app/Maps
system/app/Music2
system/app/Photos
system/app/YouTube
system/priv-app/CloudHub
system/priv-app/CollageWallpapers
system/priv-app/facebook-installer
system/priv-app/LG360VideoWallpaper
system/priv-app/LG360Wallpaper
system/priv-app/LGEasyHome
system/priv-app/LGEmail
system/priv-app/LGExchange
system/priv-app/LGQHelpService
system/priv-app/LGVVM
system/priv-app/NameID
system/priv-app/TMO_MyAccount
system/priv-app/xtra_t_app
system/vendor/app/facebook-appmanager
system/vendor/overlay/com.lge.easyhome
system/vendor/overlay/com.lge.email
system/vendor/overlay/com.lge.exchange
system/vendor/overlay/com.lge.lgworld
system/vendor/overlay/com.lge.qhelp
system/vendor/overlay/com.lge.qhelp.application
system/vendor/overlay/com.lge.qmemoplus
For best results a clean flash is recommended for this package if you are not already running 20p Debloated
Format data, and remove any apps installed to external sd. Then wipe system, dalvik, cache, data, internal storage
This will ensure no lingering apps are left behind.
If coming from Nougat, Clean Flash is Highly Recommended
Wipe Dalvik, System, Data, Cache... then flash
If coming from previous Oreo Versions
Wipe Dalvik, Cache, and System, and optionally data and internal storage
If you do not perform a clean flash, you may need to manually remove the apps left behind after flashing
Flash h93220s_Debloated.zip
Reboot
DOWNLOADS
Stable v1.0
Project files are hosted on SourceForge
Bootloader - md5:17db9bf058d53ecdd80f79a27b7fe469
Modem - md5:905cb40dc6e9eeb5fa52dd0d8d4f09cb
FullStock ROM - md5:ff32af2c1f3140c3c8c27ddac59e4950
FullStock w/Magisk - md5:9567710ab9f8e1ee4e4e4e36cfd1d2f5
Debloated w/Magisk - md5:fc0b6d9cd357ade5db472f36a10ecc8e
StockLAF - md5:799362769b0712a10818c0f26258efc2
*************************************************************************************************************
Encryption Notes
In Android, a stock device will have it's data encrypted. Often when working in TWRP on an encrypted device, you will be greeted by prompt asking for a passcode in order to decrypt the device. Unless that port of TWRP has been written for your specific device and supports decryption, you will not be able to decrypt the data on your phone. If you cannot decrypt the data, then TWRP cannot mount system and/or other partitions it needs to mount in order to safely flash anything. In order to solve this problem, sadly, you have to format the data partition on your phone (losing all personal data accumulated on the internal storage, so back it all up manually) The steps for this process are Format Data in TWRP, Reboot to recovery (to mount partitions), then flash your rom and root. There are a few tools out there to disable force encryption on your device. See the Required section above for links for this device.
Debloated has been testing via Dirty Flash from 20r.
FullStock, Bootloader and Modem have not yet been tested, but boot and system have been verified and remaining SHA1 hash checks all match with 20r which is working.
If anyone has any issues with one or more of these packages, please let me know. Thank you!
-weakNPCdotCom
XDA:DevDB Information
[STOCK] h93220s, ROM for the LG V30
Contributors
weakNPCdotCom
Source Code: https://sourceforge.net/projects/t-mobile-v30-firmware/files/h932/20s/
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Based On: 20s KDZ
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2019-04-02
Created 2019-04-02
Last Updated 2019-04-05
All packages have been released except for debloated. I am going to cook that this afternoon and should have it uploaded by tonight. Ill post an update when it's available.
Debloated Package has been Uploaded
weakNPCdotCom said:
All packages have been released except for debloated. I am going to cook that this afternoon and should have it uploaded by tonight. Ill post an update when it's available.
Click to expand...
Click to collapse
is it possible that the full stock is bad? i flashed it, now im 9008. could be corrupted dl on my end. jjust figured you might want to check
BROKEN1981 said:
is it possible that the full stock is bad? i flashed it, now im 9008. could be corrupted dl on my end. jjust figured you might want to check
Click to expand...
Click to collapse
Sorry man. what do you mean 9008? Any way you can get me your TWRP logs?
I did have to re-upload the fullstock zips after I discovered an issue with the boot image.
Also, id recommend checking the md5 hash after you download to make sure it matches what's in the OP
weakNPCdotCom said:
Sorry man. what do you mean 9008? Any way you can get me your TWRP logs?
I did have to re-upload the fullstock zips after I discovered an issue with the boot image.
Click to expand...
Click to collapse
i flashed the full stock zip, when i did reboot to system, my screen stays black. i plugged it into the computer, the computer made the sound that a device was plugged in.
in device manager its listed as 9008. so its a brick now. i got my RMA with lg. just need to send it out.
also want to make an edit, im not upset, and thank you for what you do for the community. we all take the risk.
BROKEN1981 said:
i flashed the full stock zip, when i did reboot to system, my screen stays black. i plugged it into the computer, the computer made the sound that a device was plugged in.
in device manager its listed as 9008. so its a brick now. i got my RMA with lg. just need to send it out.
also want to make an edit, im not upset, and thank you for what you do for the community. we all take the risk.
Click to expand...
Click to collapse
Yeah but still, I hate that happened to you. Are you not able to boot to DL/LAF?
it looks like the phone being read as 9008 is what happens with a dead boot.
I tried to upload the boot fix as fast as I could. Can you tell me when you downloaded it? I'm going to take the fullstock links down until I can make sure they have the correct boot image
weakNPCdotCom said:
Yeah but still, I hate that happened to you. Are you not able to boot to DL/LAF?
it looks like the phone being read as 9008 is what happens with a dead boot.
I tried to upload the boot fix as fast as I could. Can you tell me when you downloaded it? I'm going to take the fullstock links down until I can make sure they have the correct boot image
Click to expand...
Click to collapse
I tried the button combo, i tried to get to twrp via dl mode on my pc as well.
i called T-mobile around 5pm i think. its now 8:05pm.
only reason im posting now is due to trying to figure out how to lon on XDA with my G-account. i figured out how to take that 2 factor auth off.
BROKEN1981 said:
I tried the button combo, i tried to get to twrp via dl mode on my pc as well.
i called T-mobile around 5pm i think. its now 8:05pm.
only reason im posting now is due to trying to figure out how to lon on XDA with my G-account. i figured out how to take that 2 factor auth off.
Click to expand...
Click to collapse
I was just trying to figure out if you might have downloaded the first upload or the second. but i think I uploaded the new version before 5.
I found a video online for unbricking a v30 phone in 9008 mode. not sure if it works for the H932 but might be worth looking at
Im going to rebuild all the primary zips just to be safe.
I was running debloated 20r and I dirty flashed the debloated 20s and it is working 100%
If you guys aren't already on 20r and don't want to wait on the new zips you can flash one of the 20r packages and then flash the 20s debloated.
weakNPCdotCom said:
I was just trying to figure out if you might have downloaded the first upload or the second. but i think I uploaded the new version before 5.
I found a video online for unbricking a v30 phone in 9008 mode. not sure if it works for the H932 but might be worth looking at
Click to expand...
Click to collapse
i found this, but it may as well be in Greek.
https://innaz2.blogspot.com/2016/06/revised-how-to-unbrick-qualcomm-android.html
BROKEN1981 said:
i found this, but it may as well be in Greek.
https://innaz2.blogspot.com/2016/06/revised-how-to-unbrick-qualcomm-android.html
Click to expand...
Click to collapse
Yeah that looks like a heavy walkthrough. Im really sorry you ended up being the Guinea pig with this one. thank you very much for reporting the issue
I rebuilt all packages and they are now available again.
I have not tested them, but I have verified the boot and system images are good, and all remaining files have SHA1 checksums that match with 20r, which has been verified working.
All zips perform SHA1 checks prior to flashing to ensure each partition image is valid.
These should all be safe to flash going forward.
weakNPCdotCom said:
Yeah that looks like a heavy walkthrough. Im really sorry you ended up being the Guinea pig with this one. thank you very much for reporting the issue
Click to expand...
Click to collapse
ahhh NP man. I just hope i was the first and only person to flash it. its all good man, we all take risk and if it was not for you, i would not have had DTS on 20R
Flashed debloated, work as charm, thanks dev
anyway you can modified it to be flashed on a US998?
BROKEN1981 said:
ahhh NP man. I just hope i was the first and only person to flash it. its all good man, we all take risk and if it was not for you, i would not have had DTS on 20R
Click to expand...
Click to collapse
I was in the same boat when 20r was released. Had my phone unable to boot for a week. Luckily the devs put together a fix for us. But it looks like everything is sorted out here now. I'll be flashing it later tonight. Thanks @weakNPCdotCom
Flashed the 20s bootloader no problem, but got a assert failure on flashing the 20s modem- looked like it was an SHA confirmation issue.
KanBorges said:
anyway you can modified it to be flashed on a US998?
Click to expand...
Click to collapse
No. You cannot flash U.S T-Mobile H932 firmware on US998 or any other V30/V30+/V30S.
You can use US998 on T-Mobile, as-is. We have a lot of US998 T-Mobile users. For instance, @runningnak3d is currently using a US998 on T-Mobile. He's the one who rooted the T-Mobile H932 in the first place.
@weakNPCdotCom - full stock with magisk getting asset error on abl.img
Md5 hash matches what's in OP