Hi,
I have a Rooted Samsung Galaxy S3 (GT-i9300) 16GB Intl. Variant, running "KitKat 4.4.4 installed via CM installer"
I was using 'ART' runtime instead of 'Dalvik' and all seemed to work fine until today.
A week ago I installed "Xposed Framework" to try out some different MODS which still was not a problem. Later I did notice that the runtime reverted back to 'Dalvik' which I wasn't aware of. After doing a Google search I came to know that "Xposed Framework" only works with 'Dalvik' hence I was not able to change back 'ART' through 'developer options', although I have uninstalled 'Xposed Framework'. (Phone only restarts after selecting ART, nothing changes)
Furthermore, I learned that I would require a root explorer to navigate to a system file and rename it back to the original, which was complete bogus as after doing so, my phone is stuck on 'bootloop'.
I am now only able to enter 'Download Mode' and a 'CyanogenMod Simple Recovery <3' which doesn't give me the option to flash a New Custom ROM (Like Nightly, or PA, Omni, etc)
I have already tried, the following methods
1. 'CyanogenMod Simple Recovery <3' (wipe data/factory reset, wipe cache partition, wipe media) still stuck in 'bootloop'
2. Kies 3 (Firmware Upgrade & Initialization) phone cannot be detected.
3. ODIN (phone cannot be detected & also Too Risky)
The biggest fear of mine here is, a year back when I was on 4.1.2 Jellybean, I installed an unofficial release of 4.2.2 from SamMobile and was unhappy with the performance and decided to downgrade back to the official software i.e. 4.1.2 (both were ODIN methods). After successfully doing the downgrade, my phone lost network (causing a generic IMEI) compelling me to visit the service center and have it repaired at a rip-off INR7000 (cost of changing the motherboard).
Therefore, reverting back to a previous version of android is not an option.
Please don't provide me with any downgrades, if anything then it should be Equal or an upgrade!
Thanks in advance for any kind of guidance to a thread or any method to work this out.
Apologies for the long thread. But hope it covers all that is required for a solution.
First and foremost, you need to try and flash a custom recovery such as CWM [i930x][CWM Advanced Edition] PhilZ Touch
Or TWRP [RECOVERY] TWRP 2.6.3.0 touch recovery [2013-09-16]
Once done, you should be able reflash CM 11 as you had before.
If you still have questions, please post in [HELP THREAD] Galaxy S3 Ask any question.
Perseus71 said:
First and foremost, you need to try and flash a custom recovery such as CWM [i930x][CWM Advanced Edition] PhilZ Touch
Or TWRP [RECOVERY] TWRP 2.6.3.0 touch recovery [2013-09-16]
Once done, you should be able reflash CM 11 as you had before.
If you still have questions, please post in [HELP THREAD] Galaxy S3 Ask any question.
Click to expand...
Click to collapse
UPDATE
I just tried using ODIN to flash TWRP/CWM but unsuccessful, the furthest I have progressed is to a point where I get an Error (Line 1949). Searched Google, it turns out to be something that has got to do with Region Specific ROMs. So now we rollback to the point where I would require to re-install the latest update Device Specific & REGION Specific i.e. 4.3 Jellybean/TouchWiz, which would mean downgrading...
Please review [APP][2013.11.04] RegionLock Away v1.3 [ROOT]
Perseus71 said:
Please review [APP][2013.11.04] RegionLock Away v1.3 [ROOT]
Click to expand...
Click to collapse
that review did not help.
Is there any way that I can flash a Custom Recovery on to my phone beside Odin. 'Cause if I'm able to boot into recovery then only I will be able to flash another ROM. Thanks for all the help so far!
Related
Hello you brilliant people! I haven't been on here in some time. I recently move to China and brought along my Galaxy S3 i-535. It's been some time since I've worked with flashing custom ROMs and never tried it on the S3 until I came here. I am able to root, unlock the boot loader, and install CWM. However, whenever I try and flash any ROM I get the ever infuriating (Status 7) assert. Meaning that I have the incorrect ROM, correct? But I have double, triple, and quadruple checked and I have the correct ROM. Here are the pertinent details:
=============================================================
-Samsung Galaxy S3 I-535
-Originally a Verizon phone (Screw VZW!)
-Currently on the ChinaMobile network with a Chinese SIM card
-CWM v6.0.2.3
-And I'm currently on Android 4.1.2
-Baseband Ver.: I535VRBMB1
-Kernal Ver.: 3.0.31-861013 (not sure if useful, but maybe)
=============================================================
Here is the my specific question. ##Could I be receiving the Status 7 assert due to the different SIM card/network??##
I've tried removing the assert from the updater-script file, but no luck. I changed almost a year ago, so the old SIM card is long lost and finding a VZW SIM here would be nearly impossible.
I believe my CWM version is new enough.
If this is the case, any suggestions on where to go next? Any developer/website that would work with China Mobile is in Chinese, and my Chinese is VERY poor.
I need to update my phone to receive data, so they say, but I'm not sure how high I have to update. I was trying to avoid 4.3 because of the locked bootloader. But I think I can find a ROM for 4.3 or 4.4 that doesn't force me to take the locked boot loader? Am I correct in my thinking. Yes I have been researching, I just want to make sure I'm right.
Any useful assistance will be rewarded with my endless gratitude and kind thoughts!!!
You want to upgrade your CWM to 6.0.4.5 then flash your roms from there. If you're using Rom Manager, you can upgrade from within the app itself. Alternatively, you can download the CWM 6.0.4.5 recovery IMG file from the official CWM website, download "Flashify" from the Play Store then install the CWM 6.0.4.5. recovery img file using Flashify.
WOot woot!!!!
SlimSnoopOS said:
You want to upgrade your CWM to 6.0.4.5 then flash your roms from there. If you're using Rom Manager, you can upgrade from within the app itself. Alternatively, you can download the CWM 6.0.4.5 recovery IMG file from the official CWM website, download "Flashify" from the Play Store then install the CWM 6.0.4.5. recovery img file using Flashify.
Click to expand...
Click to collapse
That was all it needed! Success! Running the latest Cyanogen!
Much thanks, much thanks!
Hi.. I'm sorry for the long post, but I've been trying to install a nice Google Play Edition ROM on my phone for 2 days now and I'm hitting dead-end after dead-end. I'm just so tired and frustrated!! :crying:
I have rooted my At&T Galaxy S4 (NC1) using Geohot's Towelroot.
I then installed the TWRP app off the Play Store and used it to "Install TWRP".
At this point, when I tried to create a backup by rebooting to recovery, the phone reboots and it gets stuck with the following message (paraphrasing a bit):
"Unable to perform normal boot. Using ODIN.. Downloading.. Do not turn off device"
I then used the "Home+Vol dwn+Power" combo to reboot back into the stock ROM.
At this point I read about Loki and having to bypass the bootloader.
So I downloaded the loki_tool file from https://github.com/djrbliss/loki and followed the instructions there to create the aboot.img. However, when I tried to created the .lok file from a TWRP 2.8.0.1 open recovery image, it said "Failed to find function to patch". (For this step I tried with both ADB and a terminal emulator on my phone).
On Danvdh's forum http://forum.xda-developers.com/showthread.php?t=2557353, he simply says
"I only support the latest TWRP recovery, AT&T users must loki after flashing
-Full wipe
-Flash ROM
-Reboot"
But I'm not even able to boot into TWRP recovery!!
I don't know what the fundamental problem is and trying to wade through the ocean of information out there looking for a solution is just too exhausting when I don't even know the problem!
PLEASE HELP!!
Thanks in advance!:fingers-crossed:
Hi,
Here is the best place to ask for help with your device,
AT&T, Canadian Bell, Rogers, Telus, Virgin Samsung Galaxy S 4>AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshooting
Good luck!
Hi Experts,
I want to upgrade my samsung galaxy note GT-N7000.
After reading on how to install custom rom to N7000. I tried one of the way to install the Custom Rom using Install from Zip using SD card.
Steps i have performed to install custom rom are mentioned below:
1. I have install one app to root my phone.
2. Checked with the help of MD5File checkup to confirm that my phone is rooted or not and found that my phone has been rooted.
3. I have gone to developer option and checked USB Debugging.
4. I have not installed any backup tool for the current recovery.
5. i have copied the N7000 CWM Nightly rom which is for KitKat, but it failed in the verification and errored with Status 7.
6. Then with some other roms its failing in status 6.
8. At last one rom Slimsaber got passed in the verification and removed the current rom but while installing or mounting its rom it failed....(This action is performed using Install using Zip from SD Card)
Result was that my phone got hung on the logo. But some how i managed to installed one korean rom on the phone which was having a older version i.e. 4.0.3 and its update was not available so i got my phone updated with the stock rom of 4.1.2 version from samsung store. So now its back to where i have started
Query:
1. Is that the reason i have not installed a custom recovery tool for the existing rom in case the new rom fails (I have missed 4th point: Is there any best app that backup for current stock rom)
Request:
1. Can you guys please tell me which is the ROM that works for N7000 India version for Kitkat and Lollipop(If available)
2. Please suggest the rom that works with Odin because i have bad exp with installing from SDcard. If possible please provide a link for that tar file.
Really appreciate your support and thanks in advance.
vikashashok said:
Hi Experts,
I want to upgrade my samsung galaxy note GT-N7000.
After reading on how to install custom rom to N7000. I tried one of the way to install the Custom Rom using Install from Zip using SD card.
Steps i have performed to install custom rom are mentioned below:
1. I have install one app to root my phone.
2. Checked with the help of MD5File checkup to confirm that my phone is rooted or not and found that my phone has been rooted.
3. I have gone to developer option and checked USB Debugging.
4. I have not installed any backup tool for the current recovery.
5. i have copied the N7000 CWM Nightly rom which is for KitKat, but it failed in the verification and errored with Status 7.
6. Then with some other roms its failing in status 6.
8. At last one rom Slimsaber got passed in the verification and removed the current rom but while installing or mounting its rom it failed....(This action is performed using Install using Zip from SD Card)
Result was that my phone got hung on the logo. But some how i managed to installed one korean rom on the phone which was having a older version i.e. 4.0.3 and its update was not available so i got my phone updated with the stock rom of 4.1.2 version from samsung store. So now its back to where i have started
Query:
1. Is that the reason i have not installed a custom recovery tool for the existing rom in case the new rom fails (I have missed 4th point: Is there any best app that backup for current stock rom)
Request:
1. Can you guys please tell me which is the ROM that works for N7000 India version for Kitkat and Lollipop(If available)
2. Please suggest the rom that works with Odin because i have bad exp with installing from SDcard. If possible please provide a link for that tar file.
Really appreciate your support and thanks in advance.
Click to expand...
Click to collapse
You should install/flash a custom recovery and make a complete system (nandroid) backup directly in the custom recovery.
There are some other apps, which can create an Online Nandorid backup (just check Play store), but some apps are not compatible with all devices and to restore such a backup, you will need a custom (CWM or TWRP) recovery anyway.
To get best advices about custom recovery, ROMs, etc. for your device, please ask in the Galaxy Note GT-N7000 Q&A, Help & Troubleshooting > [FAQ] [Q&A] [Noob Friendly] HELP THREAD - POST ALL YOUR SUPPORT QUESTIONS HERE thread.
P.S.: To install/flash a custom ROM provided as zip file, you usually need a custom recovery. Stock recovery only flashed signed zip file (e.g. official OTA update files from Samsung).
Thread closed and thank you.
I rooted / S-off and installed a custom ROM from day 1 with this phone (Verizon HTC One M8).
I have been using the phone for awhile and haven't flashed anything. Today, i started looking into upgrading to a new ROM and realized that I needed to update my firmware before hand. I used this to get back to stock with the new firmware - (http://forum.xda-developers.com/ver...ent/ruu-m8vzw-4-4-4-s-off-onlynewest-t2914914). I used the SD card and Hboot loaded the RUU from the 0P6BIMG.zip.
I am currently running this official software with s-off and root. I installed TWRP with flashify. I booted in to TWRP recovery and attempted a backup and it failed. I attempted to flash a new ROM (i verified the MD5) and it also failed. After some reading it seem as if the stock HTC kernel has write protection turned off preventing TWRP from accessing these files.
I think i will be fine if i get another ROM installed....The new ROM will have a kernel with write access. I would even be happy with replacing the kernel on the official ROM (therefore enabling write access).
I don't know, I'm stuck. Please help!!!
-Kesnik
kesnik said:
I rooted / S-off and installed a custom ROM from day 1 with this phone (Verizon HTC One M8).
I have been using the phone for awhile and haven't flashed anything. Today, i started looking into upgrading to a new ROM and realized that I needed to update my firmware before hand. I used this to get back to stock with the new firmware - (http://forum.xda-developers.com/ver...ent/ruu-m8vzw-4-4-4-s-off-onlynewest-t2914914). I used the SD card and Hboot loaded the RUU from the 0P6BIMG.zip.
I am currently running this official software with s-off and root. I installed TWRP with flashify. I booted in to TWRP recovery and attempted a backup and it failed. I attempted to flash a new ROM (i verified the MD5) and it also failed. After some reading it seem as if the stock HTC kernel has write protection turned off preventing TWRP from accessing these files.
I think i will be fine if i get another ROM installed....The new ROM will have a kernel with write access. I would even be happy with replacing the kernel on the official ROM (therefore enabling write access).
I don't know, I'm stuck. Please help!!!
-Kesnik
Click to expand...
Click to collapse
Yes, seems that you might be right.
Maybe flashing a cusom kernel will be enough to gain read/write access in TWRP recovery.
But first:
Are you on the latest TWRP version? (Check in the Verizon One (M8) Original Android Development > [RECOVERY][m8wlv] TWRP 2.8.3.0 touch recovery [2014-12-22] thread.) There was an update yesterday to v2.8.3.0.
The new version has updated support for latest SuperSu app. Check that you are on the latest SuperSU app (viw Play store) too.
If both versions (TWRP and SuperSU) are up-to-date and you still have the access issue, then you should try to flash a custom kernel.
Check this for available kernels: Verizon HTC One (M8) > Kernel.
And here is a discussion thread about ROMs and kernels for your device: Verizon One (M8) Q&A, Help & Troubleshooting > ROM's and kernel suggestions.
In case that you still have questions or need detailed help, please ask in the Verizon One (M8) Q&A, Help & Troubleshooting forum.
Thread closed and thank you.
i had cm10 installed but after a few months of problems i decided to upgrade to cm11. After trying to upgrade to twrp 2.8.3 something happened then my cyangen was tripping balls so i went back to stock s3 4.1.3 by flashing with odin. Then i rooted my s3 again using odin. Then i installed rashr and installed twrp 2.8.3. Then i booted into twrp 2.8.3 and before twrp loaded it had the cyanogen logo on it.Then did factory reset and the davik cahce clear thing. Then i proceeded to installed cm11 20141112 snapshotm12 and gapps kk20140606 but when i rebooted my s3 in still goes into the stock andriod what is going on? i tried to install cyanogen mod from a different sd card and i have no luck
eric95204 said:
i had cm10 installed but after a few months of problems i decided to upgrade to cm11. After trying to upgrade to twrp 2.8.3 something happened then my cyangen was tripping balls so i went back to stock s3 4.1.3 by flashing with odin. Then i rooted my s3 again using odin. Then i installed rashr and installed twrp 2.8.3. Then i booted into twrp 2.8.3 and before twrp loaded it had the cyanogen logo on it.Then did factory reset and the davik cahce clear thing. Then i proceeded to installed cm11 20141112 snapshotm12 and gapps kk20140606 but when i rebooted my s3 in still goes into the stock andriod what is going on? i tried to install cyanogen mod from a different sd card and i have no luck
Click to expand...
Click to collapse
Do you mean this unofficial CM11: [ROM][4.4] CM 11 Unofficial - Beta 7 11-22-13 (Discontinued due to new device)?
Or this one: Cyanogenmod CM11?
Please check this thread: T999 UVDMD5 Firmware / Bootloader.
According to this, you might have to update some files (bootloader, modem, etc.) to be able to install newer CM versions.
AFAIK, only CM10 is officially suported for your device: [ROM][OFFICIAL] CyanogenMod 10 Nightly Builds for SGH-T999.
If you have further questions, please ask in the T-Mobile Galaxy S III Q&A, Help & Troubleshooting.
Thread closed and thank you.