Related
CM9 NIGHTLY (UNOFFICIAL SEMI-KANG) FOR CDMA TORO
Hey! This is my first post here on XDA, though I've been a long time user of these very forums, since the OG Droid root.
This is also my first ROM, though the credit should really go to the Cyanogenmod team. This is a pull from the ICS branch of CM's git repository,
built on Ubuntu x64. The proprietary .so files were pulled from Team-Kang's repo, because theirs was the only files I could actually get running.
I'm running this as my main install, and so far there's been no problems at all.
THIS IS NOT STABLE.
This is the equivalent of a nightly from CM, though much less polished. It can be considered a pre-alpha nightly build.
I am not liable for anything this ROM may do to your phone.
I'm doing this because I always enjoyed Cyanogen's ROMs straight without any mods or tweaks. I knew exactly what was running on my
phone. This is a straight pull from git. I haven't included any extra pulls from git or gerrit, nor anything else. It's pure Cyan.
I will do nightly releases of this ROM. CM's source is constantly changing, and I'll try and keep up with that, at least until the
build servers are doing automated nightly compiles.
Download:
thewcubed.com/update-cm-9.0.0-RC0-GN-CDMA-KANG-signed.zip
To install:
Download the ROM to your phone.
Download a GApps zip to your phone. (I use kejar31's zip)
Make sure you have the latest version of CWM's recovery.
Boot to recovery.
Backup your current system and data partitions.
Wipe data, cache, and the dalvik-vm cache. (I always do it twice to be on the safe side.)
Flash the ROM.
Flash GApps zip.
Reboot.
(tentative) Hooray!
If the download is too slow, I'll try and upload this to a couple mirrors. I don't know if my server's going to be able to handle a request flood on a 10Mb/s upload line.
Glad your making a Rom, but...
1) its in the wrong forum and
2) you dont have a link because of your "probation" status of < 10 posts
Good luck with your work though!
Also there's (unofficial) builds by a CM developer in the development section already:
http://forum.xda-developers.com/showthread.php?t=1397122
@kenyu73
I know that this isn't in the Dev section, but I can't switch it yet due to the 10 post limit. It should still be valid in the General section though.
The URL is still valid, simply copying and pasting it begins a download of the zip.
@got_milk
There may be unofficial builds, but those are for GSM devices. I apologize for not clarifying in the title that this is for CDMA/LTE versions of the Galaxy Nexus.
toroidal_loop said:
CM9 NIGHTLY (UNOFFICIAL SEMI-KANG)
Hey! This is my first post here on XDA, though I've been a long time user of these very forums, since the OG Droid root.
This is also my first ROM, though the credit should really go to the Cyanogenmod team. This is a pull from the ICS branch of CM's git repository,
built on Ubuntu x64. The proprietary .so files were pulled from Team-Kang's repo, because theirs was the only files I could actually get running.
I'm running this as my main install, and so far there's been no problems at all.
THIS IS NOT STABLE.
This is the equivalent of a nightly from CM, though much less polished. It can be considered a pre-alpha nightly build.
I am not liable for anything this ROM may do to your phone.
I'm doing this because I always enjoyed Cyanogen's ROMs straight without any mods or tweaks. I knew exactly what was running on my
phone. This is a straight pull from git. I haven't included any extra pulls from git or gerrit, nor anything else. It's pure Cyan.
I will do nightly releases of this ROM. CM's source is constantly changing, and I'll try and keep up with that, at least until the
build servers are doing automated nightly compiles.
Download:
thewcubed.com/update-cm-9.0.0-RC0-GN-CDMA-KANG-signed.zip
To install:
Download the ROM to your phone.
Download a GApps zip to your phone. (I use kejar31's zip)
Make sure you have the latest version of CWM's recovery.
Boot to recovery.
Backup your current system and data partitions.
Wipe data, cache, and the dalvik-vm cache. (I always do it twice to be on the safe side.)
Flash the ROM.
Flash GApps zip.
Reboot.
(tentative) Hooray!
If the download is too slow, I'll try and upload this to a couple mirrors. I don't know if my server's going to be able to handle a request flood on a 10Mb/s upload line.
Click to expand...
Click to collapse
I love seeing new developers come here everyday
One small issue though, this is posted in the wrong section. This should be posted in the GSM Galaxy Nexus Android Development or CDMA Galaxy Nexus Android Development (depending whether its GSM or CDMA)
toroidal_loop said:
@kenyu73
I know that this isn't in the Dev section, but I can't switch it yet due to the 10 post limit. It should still be valid in the General section though.
The URL is still valid, simply copying and pasting it begins a download of the zip.
@got_milk
There may be unofficial builds, but those are for GSM devices. I apologize for not clarifying in the title that this is for CDMA/LTE versions of the Galaxy Nexus.
Click to expand...
Click to collapse
Did you ever ask the guys from cm team before you post the kang build?I dont think this allowed.
Sent from my Galaxy Nexus using Tapatalk
Getting your post count up and then posting in Development would have been the thing to do. This will get lost in General, and I can't see it being moved to Development or everyone and his mate would be using that loophole.
@afilopou The CyanogenMod source is released under the Apache 2.0 license. This ROM isn't built for commercial gain, I'm crediting the CM team as the writers of the code, nor am I attempting to alter the code and then copyright it. The concept of "open-source" is that one can do something like this, building and redistributing.
@Kalavere I'm not trying to get this moved to the Dev. If there's enough interest in it, I'll repost the thread to Dev when I'm able. The problem I had was that there wasn't a vanilla build of CM that I could find anywhere for the CDMA/LTE toro.
toroidal_loop said:
@afilopou The CyanogenMod source is released under the Apache 2.0 license. This ROM isn't built for commercial gain, I'm crediting the CM team as the writers of the code, nor am I attempting to alter the code and then copyright it. The concept of "open-source" is that one can do something like this, building and redistributing.
Click to expand...
Click to collapse
Perfect .Just mention it because i dont want to see another locked thread
[Q&A] [DEV][OTA] CyanogenMod 11.0 Galaxy 551/Callisto (GT-I5510) Port [androidarmv6]
Q&A for [DEV][OTA] CyanogenMod 11.0 Galaxy 551/Callisto (GT-I5510) Port [androidarmv6]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [DEV][OTA] CyanogenMod 11.0 Galaxy 551/Callisto (GT-I5510) Port [androidarmv6]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Ansh2000 said:
result is same as before.
Click to expand...
Click to collapse
TWRP 2.6.0.0 and ClockworkMod v6.0.5.3 upload pls.
can't install it
Hi ! I need help with this installation procedure, cause i put the code on the terminal emulator, and then, my cwm is deleted.. I want to try this cm rom ! Please help !
Problem with recovery
I didn't have problems before with installing any rom or recovery, I think I've passed through all of possible combinations, but this time, it's terribly buggy :/
I started from stock rom 2.3.6 XEO (as always) then installed CWM Custom Recovery "CWM-5.0.2.8_GAZZY.tar" (need some cwm to update, right?) but stock rom didn't find "flash_image" just like few other roms (arkas for ex.)
Finally Burnmode's KitKatSpecialEdition didn't alert about anything missing and it just jumped to the next line. (success I think, right?) The problem is that when I reboot into recovery it flashes a blank, black screen and reboots leaving my phone recovery-less ! What do I do wrong? Since then I tried many roms and most of them don't work anymore (no luck with cm10.2 for example, KitKat special edition works, so it's the only thing I can now run without bugs, but it's BurnMode's rom, it always works well)
I downloaded recovery.img "2014-12-04 22:43:18" which is the newest (at least now!) is there a problem with the recovery, my phone or maybe I am doing something wrong? My options are now very limited since many things crash my phone (can't flash a stock rom anymore, might be hard to do it again)
Hi
Thanks for your great work. I updated my cooper (s5830) to the latest release but my device won't boot. So I return back to the previous version.
For totoro??
Hi Sir, Im on Galaxy Y s5360 , no possibility for our totoro device?
Help!
help me when i'm trying to download cwm on github is error that i'm missing the Overall/Read permission. How can i fix it? Help
recovery
I couldnt download u recovery, u wot m8 with it i havrnt got perms, upload it normal or get REKT
Can we expect working cm12 on our devices? Or this is the end of the unofficial support?
The page is closed now. Is anybody known how long will be unable to download ROMs on this page? Are there any other links in which we can get RC14 for Callisto? Thanks for help!
Updates? LinkS?
Hi, are there any updates for Callisto?
Whats the last stable build for daily use?
LInks?
anasahmad17 said:
Hi, are there any updates for Callisto?
Whats the last stable build for daily use?
LInks?
Click to expand...
Click to collapse
No more development since Feb '15 (http://forum.xda-developers.com/showpost.php?p=58590015&postcount=261), last version seems to be
Code:
[...] 112913587 Feb 11 18:56 cm-11.0.0-GT-I5510-callisto.zip
and the server hosting the images has gone (http://download.androidarmv6.org/_builds/callisto/).
You may try to find a copy of the zip, check the md5sum (mine is 37c0f0fadb2f0d7444a175e42b78a84a )
Please share your findings.
BTW, 11.0-20150211 (that's how it identifies itself) is quite responsive once you've changed the CPU governor and IO scheduler settings ("Performance" menu in Settings, I'm using SmartassV2 and Deadline. Only tick "Set on boot" after a while of testing, I have seen some particular settings freeze the phone!)
steve8x8 said:
No more development since Feb '15 (http://forum.xda-developers.com/showpost.php?p=58590015&postcount=261), last version seems to be
Code:
[...] 112913587 Feb 11 18:56 cm-11.0.0-GT-I5510-callisto.zip
and the server hosting the images has gone (http://download.androidarmv6.org/_builds/callisto/).
You may try to find a copy of the zip, check the md5sum (mine is 37c0f0fadb2f0d7444a175e42b78a84a )
Please share your findings.
BTW, 11.0-20150211 (that's how it identifies itself) is quite responsive once you've changed the CPU governor and IO scheduler settings ("Performance" menu in Settings, I'm using SmartassV2 and Deadline. Only tick "Set on boot" after a while of testing, I have seen some particular settings freeze the phone!)
Click to expand...
Click to collapse
I tried finding the rom and the only one i could find on the inter-webs is here but the website is paid one so i cant download and i cant check the checksum
http://chomikuj.pl/kaktus47/Telefon....0.0-GT-I5510-callisto,4616249982.zip(archive)
OK; here you go. That's what I found on my disk. No checksums, so you got to trust me, or unpack and inspect everything. (Perhaps someone else can confirm?)
https://drive.google.com/folderview...hrbmxzZFUwdTd0N1RSdTN4OHI1VzhsVlk&usp=sharing
Prerequisites:
You must have flashed CWM6 using Odin before.
Also you need a second partition on your sdcard, formatted as ext4.
Preparation:
Put the files you need on the sdcard (normal vfat partition), shut down the phone.
Charge the phone's battery.
Now the really tricky stuff (if you mastered Odin, that's just a piece of cake though):
Start the phone into recovery.
Flash the ROM image, and wipe data.
Boot into Android, install and setup s2e to use the sd-ext partition.
Reboot into recovery.
Flash the gapps package, and possibly one of the keyboard zips (see http://forum.xda-developers.com/showpost.php?p=56625731&postcount=162 for those). You may have to switch off package checks in between.
Reboot into Android, and change your governor and io scheduler settings.
Done.
Edit: I've got requests to share the filespace - which should be accessible by link. I'm re-adding the URL now. Apologies to everyone who tried in vain
@steve8x8 Hi, I know it's been a long time but i hope you see this, but could you please be more specific with the steps? what files to use, what keys to press? Sorry it's been a while since i used this phone or any android phone, what odin version should i use?
Have you searched the 'net (and the archive.org) for the original 551 blog? It has/had a quite good explanation of almost everything related to this particular phone. Odin version doesn't matter much, I had used 4.34 (that was current when the instructions were written) and 4.43 IIRC, no difference. Make sure to get good instructions for the CWM flash, as this is the stage where most bricks happen.
To make things easier, I'm uploading the stuff related to the Odin step from my HD ("Odin" subfolder on GDrive), more than two years old. Use them on your own risk, and check the URLs provided.
Note that I didn't go directly for CM11, but installed CM10.2 first. I would have to read the instructions to tell whether this was actually necessary...
On the way, I upgraded the recovery (from the jenkins server that doesn't exist any longer, http://jenkins.androidarmv6.org/view/Developers/job/cm-recovery/24/ of Oct 2014) to 6.0.5.3. (IIRC I did this using the terminal emulator, not Odin, but that should be possible too. I'll upload the recovery.img)
You perhaps max have to create your own Odin-flashable recovery similar to the following (again, I assume no liability at all!):
- take a .tar.md5 as starting point, and unpack it (it's just a tar with a checksum appended)
- replace the recovery.img
- create a new tar file x.tar (name it as you like)
- (cat x.tar; md5sum x.tar) >x.tar.md5
- Odin flash that
I admit it becomes more and more difficult to keep the necessary tools, files, and instructions available and in shape for devices as old as this one (I'm still confused by the "KERNEL3" series.)
---------- Post added at 09:22 AM ---------- Previous post was at 09:00 AM ----------
Quick addendum: there's a new, stagefright-fixed cm11 available for callisto, see http://forum.xda-developers.com/showthread.php?t=2453085&page=27 - which is currently being debugged but looks promising (see page 29 of that thread)
---------- Post added at 10:09 AM ---------- Previous post was at 09:22 AM ----------
It seems that there's a lot of stuff still around if you search for the "galaxy-551" tag.
Bebek's GD might also be interesting (with Odin, CWM5, and more, but stopping at Gingerbread): https://docs.google.com/folderview?...SURkMEE&tid=0B-QaRW7SLPQPTHpaQXR5b1ZVMHc#list
1
bro help
thx for sharing
steve8x8 said:
OK; here you go. That's what I found on my disk. No checksums, so you got to trust me, or unpack and inspect everything. (Perhaps someone else can confirm?)
https://drive.google.com/folderview...hrbmxzZFUwdTd0N1RSdTN4OHI1VzhsVlk&usp=sharing
Click to expand...
Click to collapse
Please don't remove those files from gdrive!:good:
Danke sehr
I didn't plan to, and indeed they are still there. Is there anyone using a Callisto running CM11?
Last night I had a dream: There was a recent ROM upgrade for the Callisto (not sure whether Nougat or Oreo), and I had started to dig out all the old instructions and notes to make it happen.
Only in the morning, after having a big mug of coffee, I realized it was only a dream :'(
armv6 ghosts haunting...
Hi, I did factory reset, wipe cache and dalvik, then instal PA and gapps but my phone always boot into recovery. Can somebody help me.
My phone: Samsung Galaxy S3 i9300
Current OS: Cyanogenmod 11 (11-20150607-NIGHTLY-I9300)
Recovery: TWRP v2.8.6.1
PA version: pa_i9300-5.1-20150612.zip
gapps: I tried all android 5.1 gapps from this two links here and here.
Flash boeffla kernel 4.0 alpha 3, the ROM will boot up normally, it's just a workaround tho, dunno why the ROM won't boot up without flashing a kernel.
AbdelGad said:
Flash boeffla kernel 4.0 alpha 3, the ROM will boot up normally, it's just a workaround tho, dunno why the ROM won't boot up without flashing a kernel.
Click to expand...
Click to collapse
Same issue still happened
I wish everyone would realize that posting in this forum is useless. If you have a device specific problem, you need to take it up with your maintainer.
Pirateghost said:
I wish everyone would realize that posting in this forum is useless. If you have a device specific problem, you need to take it up with your maintainer.
Click to expand...
Click to collapse
Sorry. Newbie here. I thought posting here will help me, as per forum description (If you need help troubleshooting a problem, please be as specific as possible by describing your software configuration, including the ROM, kernel, and any modifications you've done.)
Yeah but the maintainer and users of that device do not use this forum like they do their own device forum.
Device specific issues should always go to the device maintainer's thread, since the team doesn't support anything other than nexus in the main line of development.
Pirateghost said:
Yeah but the maintainer and users of that device do not use this forum like they do their own device forum.
Device specific issues should always go to the device maintainer's thread, since the team doesn't support anything other than nexus in the main line of development.
Click to expand...
Click to collapse
Ok got it. I will find the forum and ask there. Thank you.
[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2]Samsung Galaxy Note 2
[/SIZE]
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.
[/SIZE][SIZE=+1]Q1: Which versions are available from Samsung Galaxy Note 2
[/SIZE][SIZE=+1][/SIZE]Without LTE: N7100
With LTE: N7105
[SIZE=+1]
[/SIZE][SIZE=+1]Q1: Is there a list for all ROMs, Kernels, Apps and Guides?
[/SIZE]For N7100: [INDEX] Note 2 - ROMs, Kernels, MODs, GUIDES
For N7105: [INDEX] Note 2 4G LTE/t0lte/N7105[SIZE=+1]Q3: What does "flashing" my phone mean?
[/SIZE][SIZE=+1][/SIZE]You are overriding the currect firmware with another ROM and Kernel. There are some AOSP or CyanogenMod based ROMs available, which are upgraded to Android Marshmallow, but you can also install a Samsung Stock based ROM, which is based on Android 4.3 or Android 4.4. You can flash your Note 2 with TWRP or ClockWorkMod. [SIZE=+1]Q4: Download Mode... What is this?[/SIZE]
In Download Mode you can flash ROMs or Recovery to your phone. If you want to flash the Stock-ROM back, you are forced to use Odin to flash the firmware. For flashing via Odin, you need to boot into Download Mode. To get into the download-mode, you must shut down your Note 2 and start it, while pressing Power, Volume Down and the home button.[SIZE=+1]
[/SIZE][SIZE=+1]Q5: How can I flash the Stock-ROM?[/SIZE]
[SIZE=+1][/SIZE]For flashing the Stock-ROM, you can visit this guide by @dr.ketan[SIZE=+1]Q6: How do I root my device?[/SIZE]
Another great guide by @dr.ketan:
[Root]How to Root Note2 [N7100] & keep flash counter 0[SIZE=+1]
[/SIZE][SIZE=+1]Q7: Can I install an OTA if I'm rooted/unencrypted?
[/SIZE][SIZE=+1][/SIZE]If you installed a Custom Recovery or rooted your phone, you are not able to install updates via OTA. You are forced to flash the upgrade via Odin then.[SIZE=+1]Q8: I'm trying to search for something specific but I'm having trouble. How do I use XDA Search?[/SIZE]
XDA Forum Moderator The_Merovingian has done a nice guide, how to use the search-feature: HERE[SIZE=+1]Q9: How can I install Android Marshmallow on Galaxy Note 2?[/SIZE]
You can have a look at this Thread by me. You will learn, how to install Android Marshmallow coming from Stock:
[GUIDE] How to install Android Marshmallow on Galaxy Note 2[SIZE=+1]Q10: How can I get out of a Bootloop?[/SIZE]
Doing a FactoryReset should solve this issue. You can do this by booting into Recovery.[SIZE=+1]Q11: Will Knox triggered, if I flash a Custom ROM or Custom Recovery?[/SIZE]
Yes, Knox counter will go to 0x1 and you will lost your warranty.[SIZE=+1]Q12: How can I enable MTP on CyanogenMod ROMs?
[/SIZE]You need to pull down the status-bar and enable MTP there. If there is not button, you need to go to the developer settings and enable it there.Some other helpful words:
ADB - "Android Debug Bridge" a system that can be accessed using a computer where you can manage the device from. You need the Android SDK to use it.
AOSP - "Android open source project" a project by Google Inc. to give android to developers and manufactures for free.
APK - "Android Package" an Android application
Bloatware - Software or 'apps' that you don't need, but come preinstalled to a device's /system partition, meaning that you cannot remove them unless the device has been rooted. Usually, these are apps are sponsored by a company and included by a carrier for profit
CDMA/GSM - A type of network communication between phones and carriers. GSM phones normally are included with SIM Cards that authorize them onto the network. CDMA have this authorization built in and do not need a sim card.
Custom recovery - A modified version of stock recoveries that allow you to do more things in the recovery mode.
Cyanogenmod (CM) - A free open-source project based on the AOSP. It is a modded version of the Android firmware
Dalvik-Cache - Holds all of the pre-compiled .dex files created from installed apps. These files are static and do not change unless the app is updated.
Deodexed - Where ODEX files are moved into the actual applications modded) version of the Android firmware.
Developer - A man or woman who has created (developed) software.
Firmware - a piece of software to make hardware function correctly. This can refer to Radio Firmware, but is normally used as another name for ROM.
Governor - A system embedded into the kernel to automatically change the current working CPU frequency depending on the workload. It would only go up to what it is overclocked (or underclocked) to, this is called the maximum frequency. It would not drop below the minimum frequency.
KANG - The process of creating a code based of someone else's code.
Kernel - An important part of all operating systems that handles the CPU and other vital components. A modded kernel may be used for overclocking.
Logcat - A logging system built into the ADB
Mod - A modification to a part of the phones software. It is also POSSIBLE to mod the phones hardware but is not recommended.
OTA - "Over the air" a term used to indicate software that was sent to phones directly through the internet to their phones.
Open-source - (not to be confussed with free) A peice of software that is free to edit, use, distribute and share with no charge.
Overclock - To exceed the default maximum CPU speed. This could make a phone more powerful but may cause damage. Although no damaged has been reported so far it could still drain battery life.
Radio Firmware - A type of software that allows correct communication with the radio and the operating system. A newer firmware would normally improve battery life and call quality. The radio firmware only applies to the CDMA/GSM radio.
Radio - (not to be confused with Radio Firmware) A piece of hardware that allows communication. There are 3 main radios in your phone. Bluetooth, WiFi and GSM/CDMA.
ROM -
1. A modified version of the Android operating system operating system.
2. Read Only Memory, a place where information is stored and can not be destroyed, modified or written to.
Stock - An unchanged version of something. Example: I just flashed stock sense.
Underclock - To change your phones maximum frequency to LOWER than the default to attempt to extend the phones lifespan and battery.
WIP - "Work In Progress"
Zipalligned - An archive alignment tool that provides important optimization to Android application (.apk) files. The purpose is to ensure that all uncompressed data starts with a particular alignment relative to the start of the file. Specifically, it causes all uncompressed data within the .apk, such as images or raw files, to be aligned on 4-byte boundaries. This allows all portions to be accessed directly with mmap() even if they contain binary data with alignment restrictions. The benefit is a reduction in the amount of RAM consumed when running the application.
INTL - International
Odex - Files that are collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application.
Recovery Mode - A special environment that you can boot into for troubleshooting and upgrading purposes
Thanks to @benjamingwynn for the glossary of terms
Forum Rules | New Users Guide | XDA Tour | Report PostsThis FAQ is part of a Recognized Contributor Group Initiative. Please look for a similar FAQ thread when visiting another device forum.
A special thanks to everyone who contributed to the production of this FAQ
This thread is an ongoing process. This will be a WIP for a period of time
http://forum.xda-developers.com/wiki/Bootloader
This is not a Q&A Thread
This is not a Q&A Thread This is not intended to be a Q&A help thread. Please only post suggestions for content that should be added to the OP. Post the relevant links to accompany your request.
If you need help or have a general question, consider using these links:
Question's please here: http://forum.xda-developers.com/shield-tablet/help
Or here: [NOOB FRIENDLY] Ask the question! [N7100 and other variants]
Trafalgar Square said:
This is not a Q&A Thread This is not intended to be a Q&A help thread. Please only post suggestions for content that should be added to the OP. Post the relevant links to accompany your request.
If you need help or have a general question, consider using these links:
Question's please here:http://forum.xda-developers.com/shield-tablet/help
Or here:[NOOB FRIENDLY] Ask the question! [N7100 and other variants]
Click to expand...
Click to collapse
I need your help pls help me
Sid76 said:
I need your help pls help me
Click to expand...
Click to collapse
Pls help me when I disconnect my phone from charger it stuck in boot image like icon of galaxy note 2 after that when I connect again it starts normally and I do disconnect this happen again pls help me our bootloop and I tried many ROMs but not able to fix help me
Hello PLZ someone help me. I searched for more than two weeks to solve my problem and did not find any results
I'm sorry in advance that I could not write English well.
I have a Samsung Galaxy Note 2 (N7100) phone with Android 9 custom ROM, which I charged quickly when it finished charging, but it doesn't turn on now.
The mobile stops on the Samsung logo or lineage logo or mobile Battery animation when I charge it and I can only go into recovery mode and download mode
After this incident, I wanted to factory reset it with the custom recovery twrp that I installed on my mobile phone or wipe all the memory, but I got the error "Unable to mount storage".
Even when I wanted to install the official ROM with micro sd memory, twrp displays zero for mobile memory, sd memory and otg.
I also wanted to flash it with Odin with four official files and a pit file, which was unsuccessful and show erorr at the end the message "re-partition operation failed" was announced.
I tried to flash files again with the Miracle tool without a box. Some partitions were burned, but due to the inability to burn some partitions, I received a wrong reply error (0).
Also, after flashing the recovery file with the official recovery and new version of twrp, Miracle displayed a successful message, but in practice, there was no change in my custom recovery.
So I'm looking for a way to repair emmc with just a usb cable and no box or any other way to repair my mobile
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
* I am not your help desk.
Prerequisites
1. Unlocked bootloader
2. Patience (even i was unable to unlock for 4-6 hours and also fastboot was hanging while flashing twrp for testing, changing USB port worked. My first build was stuck in splash screen for infinite time, it happens keep patience)
Bugs
1. Maybe under your bed !
2. If you have found a bug/issue, please consider posting it to my GitHub Issues.
Instructions
1. Boot into fastboot mode by adb reboot bootloader or key combo, doesn't matter.
2. Download the twrp image following the link in the download section and transfer it to the adb folder (or add adb to PATH for universal access).
3. Open the cmd/terminal and change directory into the adb folder (or where you downloaded twrp image).
4. Now confirm/check that device is connected by typing:-
Code:
fastboot devices
If you got your device seriel number there then you are ready to continue otherwise try connecting device again and make sure USB debugging is on and you have granted permission to the PC to debug, linux users may need to change connection type to transfer files from charging only.
5. After that we will flash this TWRP recovery to the recovery partition by below command:-
Code:
fastboot flash recovery <twrp-name.img>
BooM ! TWRP flashed successfully.
6. Now unplug your device and then select recovery mode by pressing vol down/up and boot into twrp mode.
Note: Right after flashing twrp & booting into it, format data and flash Disable_Dm-Verity_ForceEncrypt for persistence twrp. Otherwise as soon as you boot to system, it's gonna replaced by stock recovery. Another option is to flash PBRP zip, if Disable_Dm-Verity_ForceEncrypt didn't work, PBRP by default have decryption patch.
Downloads
Android File Host: https://www.androidfilehost.com/?w=files&flid=298214
Official TWRP Page: https://build.twrp.me/twrp-3.3.1-0-RMX1901.img
Screenshots
Check screenshots section
XDA:DevDB Information
TWRP For Realme X, Kernel for the Realme X
Contributors
chankruze
Source Code: https://github.com/N00bTree/android_device_realme_RMX1901
Kernel Special Features:
Version Information
Status: Stable
Created 2019-09-20
Last Updated 2019-09-22
Thank you ?
Orange fox now TWRP its good to see some officials coming...now just waiting for pixel experience or Some aosp builds...
Can used on RMX1903?
Hi OP,
What's the difference between your one and this one?
https://forum.xda-developers.com/re...very-unofficial-twrp-realme-x-stable-t3959556
And please do not label unofficial TWRP as official, "going to be supported officially soon". I have changed title for you.
jerryhou85 said:
Hi OP,
What's the difference between your one and this one?
https://forum.xda-developers.com/re...very-unofficial-twrp-realme-x-stable-t3959556
And please do not label unofficial TWRP as official, "going to be supported officially soon". I have changed title for you.
Click to expand...
Click to collapse
Oh, you are the moderator who asked for answer. I missed it untill oswald's PM. Very busy in real life and also for this device kernel. Also to be noted suffering from severe back pain.
Let me ask you one question: What is the difference between TWRP images, let's say you compiled and i compiled both from omni android-9.0. The thing is this post you are seeing could be here 33 days ago but i waited for the device so that i don't brick others device. There will be some changes later, when kernel is ready. for now it's working.
With due respect and humble submission, i want a small declaration from you, if you are going to update the new build links, add a FAQ section i won't have to write official or unofficial in future. You are going to update it right ? At the moment the gerrit patch got merged, i expect you to change title from unofficial to official.
I can't say same thing to each and every mod ... (i am stupid i could have added you as cc/bcc for the PM i answered).
A few last words, "Respect Should Be Earned, Not Given".
Regards,
chandan
chankruze said:
Oh, you are the moderator who asked for answer. I missed it untill oswald's PM. Very busy in real life and also for this device kernel. Also to be noted suffering from severe back pain.
Let me ask you one question: What is the difference between TWRP images, let's say you compiled and i compiled both from omni android-9.0. The thing is this post you are seeing could be here 33 days ago but i waited for the device so that i don't brick others device. There will be some changes later, when kernel is ready. for now it's working.
With due respect and humble submission, i want a small declaration from you, if you are going to update the new build links, add a FAQ section i won't have to write official or unofficial in future. You are going to update it right ? At the moment the gerrit patch got merged, i expect you to change title from unofficial to official.
I can't say same thing to each and every mod ... (i am stupid i could have added you as cc/bcc for the PM i answered).
A few last words, "Respect Should Be Earned, Not Given".
Regards,
chandan
Click to expand...
Click to collapse
Bhai dhyan diani karma kari chala.
Keep up the good work?
Thanks for TWRP. Any Idea when would custom ROMs start rolling in? I recently read that XDA sent out devices to devs for development.
chankruze said:
Oh, you are the moderator who asked for answer. I missed it untill oswald's PM. Very busy in real life and also for this device kernel. Also to be noted suffering from severe back pain.
Let me ask you one question: What is the difference between TWRP images, let's say you compiled and i compiled both from omni android-9.0. The thing is this post you are seeing could be here 33 days ago but i waited for the device so that i don't brick others device. There will be some changes later, when kernel is ready. for now it's working.
With due respect and humble submission, i want a small declaration from you, if you are going to update the new build links, add a FAQ section i won't have to write official or unofficial in future. You are going to update it right ? At the moment the gerrit patch got merged, i expect you to change title from unofficial to official.
I can't say same thing to each and every mod ... (i am stupid i could have added you as cc/bcc for the PM i answered).
A few last words, "Respect Should Be Earned, Not Given".
Regards,
chandan
Click to expand...
Click to collapse
Hi, fully understand your point. When this one is merged, you could change the title from unofficial to official by yourself. :highfive:
Thanks for your hard work and development.
Hi this should also work in OPPO K3 I suppose. Everything is same except camera. Anyone tried?
HI Chandan,
Good work on the TWRP for X, Is there a possibilty for XT as well for the TWRP
Regards,
Diaz M