[Q] Problem With Flashing SCH-I535 - Verizon Samsung Galaxy S III

The very first ROM I tried to flash was a version of CarbonRom. I was unsuccessful, as i got the installation aborted message. I then tried a couple of other lesser know ones, with the same luck. Lastly I tried CM 10.1, and with that, i had success. It was the only one that would work so far. Yesterday, I downloaded DU 4.2.2, and A new nightly version of Carbon (Specifically for my phone) With no luck of installation. Am i doing something wrong with these? Is there a different method of flashing i'm missing?

what is the procedure you take to install?
I usually go this route:
1) Boot into whatever recovery you have
2) Wipe Cache/Davlik
3) Install custom ROM
4) run a factory reset
5) Reboot

snibe said:
what is the procedure you take to install?
I usually go this route:
1) Boot into whatever recovery you have
2) Wipe Cache/Davlik
3) Install custom ROM
4) run a factory reset
5) Reboot
Click to expand...
Click to collapse
I have Philz custom recovery which based on cwm version 6.0.3.7 which when you tap wipe data you will then have the option to clean install for new ROM.

jmxc23 said:
I have Philz custom recovery which based on cwm version 6.0.3.7 which when you tap wipe data you will then have the option to clean install for new ROM.
Click to expand...
Click to collapse
Sorry for not replying earlier, i never got a notification. I'm using the most recent version of CWM. My usual order is :
1. Boot into recovery
2. Factory Reset
3. Clear Cache Partition
4. Wipe Dalvik
5. Format /system
6. Mount /system
7. Flash new ROM

Bcaraway14 said:
Sorry for not replying earlier, i never got a notification. I'm using the most recent version of CWM. My usual order is :
1. Boot into recovery
2. Factory Reset
3. Clear Cache Partition
4. Wipe Dalvik
5. Format /system
6. Mount /system
7. Flash new ROM
Click to expand...
Click to collapse
well we now have 3 custom recoveries to choose from I like the newer one since I can install a new ROM in fewer steps.

i would do a factory reset after you flash your rom too, can't hurt.
of course on updating the same ROM, I only Wipe Cache/Davlik and that's it.

Bad download? Does the md5 match?

after making sure you wiped everything make sure the download itself was proper I am running it flawless right now

Related

How do I specifically install a custom rom on the Nexus 7?

So I've unlocked the bootloader, rooted and flashed CWM.
I've also made a backup with titaniumbackup.
How do I go about installing a ROM? I'm confused because I read in some places that you need to wipe cache (davik? What is this?) then wipe everything else on the current ROM, then install the custom ROM, but do I do this through CMD or natively on the Nexus 7 with ROM manager?
What are the steps to do this properly?
Try this, questions just ask
You need a recovery first like 4ext you put that on then you copy the ROM onto the sd from your PC and enter into recovery then you install the zip file and factory reset in the same place wipe cash and that other cache you mentioned keep forgetting name of it
Lizardwithhat said:
You need a recovery first like 4ext you put that on then you copy the ROM onto the sd from your PC and enter into recovery then you install the zip file and factory reset in the same place wipe cash and that other cache you mentioned keep forgetting name of it
Click to expand...
Click to collapse
I have CWM recovery, wait so I factory reset in recovery before I install the zip, and wipe cache after? Which order?
UnixxinU said:
I have CWM recovery, wait so I factory reset in recovery before I install the zip, and wipe cache after? Which order?
Click to expand...
Click to collapse
in cwm do a factory reset and then clear cache of that install rom (.zip) from sd card

CM9 boot animation loop

I have clockworkmod recovery installed and rooted. It's been a few months since I rooted, and can't remember exactly what I did, but OTA updates stopped working. Hence, I am still on gingerbread.
Trying to flash a custom rom now, CM9. I tried the rom manager method several times, found out that wasn't recommended, and then tried the recovery method.
The same thing happens either way: it boots into CM9, but the boot animation keeps playing.
With the rom manager method, I tried wiping nothing, then tried wiping dalvik only, then tried... whatever the other option was, wipe cache and data?
With CMW recovery I downloaded CM9 zip and the appropriate GAPPS, moved onto the internal SD card, booted into recovery mode Wipe data/factory reset, then Wipe cache partition, then install both.
I'm able to restore from backup each time, but this is annoying.
Thank you
1. Install ICS Radio (UCLF6)
2. Wipe Data/Factory Reset
3. Format /System
4. Install CM9.zip
5. Install Gapps.zip
6. Wipe Cache/Dalvik
7. Reboot
:good:
UZ7 said:
1. Install ICS Radio (UCLF6)
2. Wipe Data/Factory Reset
3. Format /System
4. Install CM9.zip
5. Install Gapps.zip
6. Wipe Cache/Dalvik
7. Reboot
:good:
Click to expand...
Click to collapse
So "UCLF6" appears to be rom that is similar to stock, I'm guessing the idea here is that I'm resetting the phone but retaining root, the idea being that something on my phone is messed up and preventing CM9 from booting but doesn't prevent the current rom from booting?
Two other questions
1. Won't format/system wipe out all my backups in addition to my data?
2. Have you had or seen this problem before? I'm hesitant to commit myself to something, especially with no backups, if it's just a theoretical fix. I do appreciate it either way.
UCLF6 is an ICS modem/radio you need if you're coming from gb.
If you back up though CWM you can restore again later if you want.
Formatting /system will delete the operating system.
Formatting /data will delete your apps/settings/wallpaper etc...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I had a similar boot animation loop when I went from stock GB to stock ICS. What seemed to fix it was updating my CWM from 5.0.2.6 (non-touch) to 5.5.0.4 (touch). (BTW, I couldn't find an advantage of stock ICS over stock GB. I have since put on CM9 which I'm liking).
UZ7 said:
UCLF6 is an ICS modem/radio you need if you're coming from gb.
If you back up though CWM you can restore again later if you want.
Formatting /system will delete the operating system.
Formatting /data will delete your apps/settings/wallpaper etc...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Still got the boot loop.
When I did the "Wipe data/factory reset" I did get an error message during one of the processes"
"Error mounting sdcard/.android_secure!
Skipping format"
I had a boot loop problem when I first tried to flash JB. I went from GB to ICS with a custom rom a few months back, but I couldn't get any of the new JB roms to work. I ended up having to upgrade my CWM to the touch version in order to get JB flash to work. Also, a tip-- the boot animation will take a minute or two even when it is working. Don't assume it is still a problem if you see it more than once.

[Q] Bootloader broken?

Hello guys,
after attempting to install a custom rom in my S5670B I got stuck in CWM every single time I try to reboot the phone. I doesn't matters what I try, it will always boot into recovery.
So, is there anyway to make it boot "correctly"?
Steps to install the custom rom:
1. boot into recovery
2. wipe data/cache
3. wipe dalvik
4. format /system
5. install from zip
6. wipe dalvik
rmartignoni said:
Hello guys,
after attempting to install a custom rom in my S5670B I got stuck in CWM every single time I try to reboot the phone. I doesn't matters what I try, it will always boot into recovery.
So, is there anyway to make it boot "correctly"?
Steps to install the custom rom:
1. boot into recovery
2. wipe data/cache
3. wipe dalvik
4. format /system
5. install from zip
6. wipe dalvik
Click to expand...
Click to collapse
just you need below steps test it reply here again.
1. boot into recovery
2. wipe data/cache
3. wipe dalvik
4. install from zip
5 wipe data/cache
6. wipe dalvik
rmartignoni said:
Hello guys,
after attempting to install a custom rom in my S5670B I got stuck in CWM every single time I try to reboot the phone. I doesn't matters what I try, it will always boot into recovery.
So, is there anyway to make it boot "correctly"?
Steps to install the custom rom:
1. boot into recovery
2. wipe data/cache
3. wipe dalvik
4. format /system
5. install from zip
6. wipe dalvik
Click to expand...
Click to collapse
If you are using CWM6 there is known bug that causes this. Just revert to CWM5.
If not just wipe everything (EXECPT SDCARD) and flash again
If that is no go then flash stock rom via odin, flash CWM5 and then flash custom rom.

[GTab 2 7.0] Can't install custom 4.4.4 ROMs

I can't install custom ROMs on p3113
Steps Taken
Starting with stock firmware/recovery
using chainfire autoroot
reboot
use root checker to confirm root
Use Odin to flash a custom recovery. (I tried Andi's CWM, TWRP, and also Philz touch 6.40)
Custom recovery flashes no issues and I can boot into custom recovery
I do factory wipe, then also dalvik, and cache again for good measure
Go to install a custom ROM via recovery
Go to reboot and the recovery prompts me that I need root and to asks gives me an option to install su
When I do that and reboot it bootloops.
I've tried 3 different recoveries. The ROMs I've attempted to flash are Dhollmen 4..4.4, and Andi's Omnirom 4.4..4.
It appears I can install 5.x ROMs without issue.
Any idea what I can do to fix this problem?
edit: in the process of trying twrp 2.8.0.5
edit2: no luck with 2..8.0.5 which I found on Dhollmen's thread. Going go browse through the forum looking for older recoveries.
Have you tried clearing /system
Yes
Try updating your SU binary before the flash, also try plain jane CWM, Andis CWM acts weird sometimes.
If SU binary won't update delete and install a different one, then update.
Pp.
Wipe cache
Wipe dalvic
Format /data
Format /system
Reboot recovery once
Flash rom.zip (don't flash anything else!)
Reboot into system, don't use "fix root"!
If it boots (Lollipop takes some time) your are good to go to flash gapps etc.
Send from OnePlus One using Tapatalk
Android-Andi said:
Wipe cache
Wipe dalvic
Format /data
Format /system
Reboot recovery once
Flash rom.zip (don't flash anything else!)
Reboot into system, don't use "fix root"!
If it boots (Lollipop takes some time) your are good to go to flash gapps etc.
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
The only thing I wasn't doing was rebooting after wiping. Wiping then rebooting let me install the 4.4.4 ROMs no problem. I never would have figured this out thanks a lot. What causes the need to reboot after wiping?
@HappyRoot good to hear.
Seems like one of the partition wasn't unmount by the updater-script or recovery after wipe and caused that issue.
Send from OnePlus One using Tapatalk
Android-Andi said:
@HappyRoot good to hear.
Seems like one of the partition wasn't unmount by the updater-script or recovery after wipe and caused that issue.
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
It only worked with installing SlimKat/Dhollmen I'm still unable to install Omni 4.4.4. I've done a complete wipe Odin'd twrp 2.8.4.1 and flash the zip via adb sideload. I keep getting an updater binary error.
update: twrp would crash at 37% and give me a binary error. when i odin'd updated cwm from you android file list i was able to get to 100% but then i would get a status 6 error.
Then you are doing something wrong...
Recovery log?
Send from OnePlus One using Tapatalk

[Solved] Help to flash custom ROMs

Hello everybody,
I bought a Oneplus 7 Pro a few days ago and I'm preparing it for my daily usage. It's my fourth Android smartphone, and the third Oneplus. So far, I managed to flash everyone of them, with no major issues.
And then, the Oneplus 7 Pro suddenly appeared
I used this tutorial to unlock the bootloader and flash the custom recovery.
From my understanding, the custom recovery is flashed in the Recovery Ramdisk and available for both A & B slots.
For now, I have A and B slots with stock OSS, unlocked bootloader, custom recovery and Magisk. All of this is working.
There began my problems. I want to flash a custom ROM without Gapps and I fail to do it. All instructions around ROM threads seems different to me, I don't get the thing about A & B slots, when I flash one rom, it boots as usual on the stock ROM, if I flash both slots, It causes bootloops and if I manage to launch the recovery, my internal storage isn't detected and I can't restore any backup.
I already used MSMDownload to restore the phone completely once.
Can somebody explain to my dumb person how to do it proprely ? Thanks in advance ! :fingers-crossed:
TL;DR : I fail to flash a custom ROM and make it work.
Yes I had same issues when rooted, it means you lost root. You can try tool all in one to flash recovery and magesik via fastboot. If that doesn't restore your access, on twrp you will have to type in format, then mount, then add rom to storage(this method wipes everything beware)
djhulk2 said:
Yes I had same issues when rooted, it means you lost root. You can try tool all in one to flash recovery and magesik via fastboot. If that doesn't restore your access, on twrp you will have to type in format, then mount, then add rom to storage(this method wipes everything beware)
Click to expand...
Click to collapse
For now, my phone is working nicely. But that's the process of flashing a new ROM that fails. Recovery and Magisk are already and working.
Factory reset
Flash rom
Flash twrp installer
Reboot recovery
Format data
Reboot system
i boot all roms with these steps
WesTD said:
Factory reset
Flash rom
Flash twrp installer
Reboot recovery
Format data
Reboot system
i boot all roms with these steps
Click to expand...
Click to collapse
Thanks, I will try.
When you flash the ROM, does TWRP tell you that if you want to continue you need to reboot recovery ? If so, do you ? Do you reboot recovery on the same slot, or do you flash both ?
draentor said:
Thanks, I will try.
When you flash the ROM, does TWRP tell you that if you want to continue you need to reboot recovery ? If so, do you ? Do you reboot recovery on the same slot, or do you flash both ?
Click to expand...
Click to collapse
Nope, it doesnt tell you anything. Just reboot recovery from reboot menu. Don't touch the slot options
Thanks for your advices.
I'm trying right now, here's my steps :
- Wipe Data, Cache, Dalvik Cache (the standard Factory Reset)
- Install ROM : TWRP logs show that he's flashing on inactive slot A, then B. After that logs said " To flash additional zips, please reboot recovery to switch to the updated slot ". I'm going back on the menu
- Install TWRP Installer like previously
- Reboot Recovery : TWRP ask me if I want to install the TWRP App, I dismiss. After reboot of the recovery, it asks if I want to keep System Read Only, I swipe to allow modifications
- Wipe Data : Can't do it because TWRP is unable to mount storage. And after further investigations, I'm now on slot A, not B as before.
- Reboot recovery to slot B
- Wipe Data on slot B
- Reboot system
And It still booting on the stock Oxygen OS Rom, not the custom one installed before. I'm lost
The problem is that you are not performing factory reset.
Wipe data is not enough,you gotta go to wipe-format data-enter yes and swipe.
That is why you are getting bootloops and twrp unable to mount storage problem.
A/B is pretty simple.
You got two slots for many partitions like system vendor boot and all,but a single data partition.
Flash a rom from one slot,it always gets flashed to the other slot no matter what.So next time you reboot to recovery or system it's gonna be on the other slot.So here is the problem..one rom cannot decrypt data which was initially encrypted by another rom..so you gotta perform a data format instead of wipe.Thats it.
draentor said:
Thanks for your advices.
I'm trying right now, here's my steps :
- Wipe Data, Cache, Dalvik Cache (the standard Factory Reset)
- Install ROM : TWRP logs show that he's flashing on inactive slot A, then B. After that logs said " To flash additional zips, please reboot recovery to switch to the updated slot ". I'm going back on the menu
- Install TWRP Installer like previously
- Reboot Recovery : TWRP ask me if I want to install the TWRP App, I dismiss. After reboot of the recovery, it asks if I want to keep System Read Only, I swipe to allow modifications
- Wipe Data : Can't do it because TWRP is unable to mount storage. And after further investigations, I'm now on slot A, not B as before.
- Reboot recovery to slot B
- Wipe Data on slot B
- Reboot system
And It still booting on the stock Oxygen OS Rom, not the custom one installed before. I'm lost
Click to expand...
Click to collapse
lol i wrote all steps but you didn't do all of them. Use swipe to wipe for factory reset and you didn't format data
Joker123## said:
The problem is that you are not performing factory reset.
Wipe data is not enough,you gotta go to wipe-format data-enter yes and swipe.
That is why you are getting bootloops and twrp unable to mount storage problem.
A/B is pretty simple.
You got two slots for many partitions like system vendor boot and all,but a single data partition.
Flash a rom from one slot,it always gets flashed to the other slot no matter what.So next time you reboot to recovery or system it's gonna be on the other slot.So here is the problem..one rom cannot decrypt data which was initially encrypted by another rom..so you gotta perform a data format instead of wipe.Thats it.
Click to expand...
Click to collapse
Thanks for the explanation !
WesTD said:
lol i wrote all steps but you didn't do all of them. Use swipe to wipe for factory reset and you didn't format data
Click to expand...
Click to collapse
Well yes, I didn't understood the difference between Wipe and Format Data.
So let's resume :
Unlock Bootloader
Advanced -> Install Recovery Ramdisk : Install TWRP
Install -> Flash TWRP Installer
Install -> Flash Magisk
Reboot -> System : Reboot on stock OxygenOS Rooted
Then
Wipe -> Factory Reset : Wipe Data, Cache and Dalvik Cache, that means you just have to swipe on TWRP.
Install -> Flash ROM : Use the install function and install the ROM
Install -> Flash TWRP Installer : Don't reboot, go back and install as the previous step
Reboot -> Recovery : Reboot TWRP and it automatically load the other slot
Wipe -> Format Data : Click and type yes
Reboot -> System : Just reboot and it should load the installed ROM
is wiping internal storage compulsory?
aaryan45 said:
is wiping internal storage compulsory?
Click to expand...
Click to collapse
How would you do it ? This is an open discussion, I can't find one and only way of doing it
aaryan45 said:
is wiping internal storage compulsory?
Click to expand...
Click to collapse
Not wiping.. formatting..that is compulsory if your current data is encrypted
After multiple tries to verify the process :
Wipe -> Factory Reset + : Wipe Data, System, Cache and Dalvik Cache
Install -> Flash ROM : Use the install function and install the ROM
Install -> Flash TWRP Installer : Don't reboot, go back and install as the previous step
Reboot -> Recovery : Reboot TWRP and it automatically load the other slot
Wipe -> Format Data : Click and type yes
Reboot -> System : Just reboot and it should load the installed ROM
Install -> Magisk
Reboot -> System
Install -> Whathever you want
Reboot -> System
It worked !

Categories

Resources