So ive got safestrap and trying to flash an ics rom from aopk i think and ive backed up then went to safe mode then data reset/wipe cache/dalvik and format system. Then i go to flash the rom and when i turn on my phone it just sits black after safestrap splash screen. How do i get a rom to work?
Ilikecheese said:
So ive got safestrap and trying to flash an ics rom from aopk i think and ive backed up then went to safe mode then data reset/wipe cache/dalvik and format system. Then i go to flash the rom and when i turn on my phone it just sits black after safestrap splash screen. How do i get a rom to work?
Click to expand...
Click to collapse
Do you have a verizon razr right?
Yeah
Related
Hello all, could use some help here.
I'm trying to restore my Note to the factory ROM and I'm running into an issue.
Fyi, I had the latest Paranoid JB Rom from Oct 13.
I followed the proceedures outlined in the forums (used ODIN to restore the default "attstockrom") and after that restore the phone would loop rebooting into ATT rethink possible animation screen.
I found and downloaded the latest 4.04 rom for the phone (I717UCLF6) and rebooted. Now it just hangs at the "ATT Rethink possible" graphic (no animation, no loop).
Odin does see the device fine so I can reflash again with no problems if I need to. I'm thinking of trying the I717UCLA1 version from Jan to see if that works but I'm hoping I can get some better advice before I do something that might cause more permanent problems.
Any advice on how to get back to stock ICS (or even JB) and get the phone working again?
Thanks!
Try doing a factory data/cache wipe from Recovery.
I flashed the stock rom via ODIN. There is no factory data/cache wipe since there's no custom recovery.
Are you suggesting flashing CWM/TWRP on the phone now then doing that?
Houston we have liftoff. Thanks for the tip Fappa, that got me into the phone (reinstalled cwm, factory reset). However I'd still like to remove CWM and go back to completely stock....
I'm not overly worried about it as I'm selling the phone but I'd like the new owner to have a completely clean phone in case they need to send it in at some point for repair. But in any case it's up and running with CWM and factory ICS rom.
santiagodraco said:
I flashed the stock rom via ODIN. There is no factory data/cache wipe since there's no custom recovery.
Are you suggesting flashing CWM/TWRP on the phone now then doing that?
Click to expand...
Click to collapse
I'm sure fappa meant to use the stock android recovery and wipe. when I go back to stock it always hangs at AT&T boot logo and have to wipe/reset from stock recovery to get it to boot.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Yes do what they say or you will continue to boot loop.
Sent using cheezoline.
So basically my S2 died on me randomly, but i was able to boot into recovery so i tried to restore my backup. It then said 'MD5 mismatch', I then tried to install a rom but it said installation aborted, I then booted my phone into download mode, loaded a stock rom through odin, it said successful but it won't go past the boot screen, it just hangs. I tried flashing another stock rom but the same problem occurred.
Any form of help is appreciated
OK now you flashed back to stock rom, boot into stock recovery then do a factory reset/wipe data. Be sure your not dangered by the emmc bug on 4.0.4.
Sent from my Galaxy SII
*boy*racer* said:
OK now you flashed back to stock rom, boot into stock recovery then do a factory reset/wipe data. Be sure your not dangered by the emmc bug on 4.0.4.
Sent from my Galaxy SII
Click to expand...
Click to collapse
What do i do next after wipe data?
restart ur phone lol
i've already tried wipe data, install rom or wipe data, install rom via odin but it still won't go past the boot screen
Hey guys,
I was just wondering what the general consensus is on which recovery is the most preferred.
I was using TWRP 2.6, but that gave me problems (being stuck on samsung logo everytime my phone rebooted). Reverted back to 2.5.0.2 and it seems to work fine so far. I did try CWM in the past but for some reason my boot loader would get locked and I would have to ODIN back to stock.
So what's your preferred recovery and why?
Thanks.
Exodus885 said:
Hey guys,
I was just wondering what the general consensus is on which recovery is the most preferred.
I was using TWRP 2.6, but that gave me problems (being stuck on samsung logo everytime my phone rebooted). Reverted back to 2.5.0.2 and it seems to work fine so far. I did try CWM in the past but for some reason my boot loader would get locked and I would have to ODIN back to stock.
So what's your preferred recovery and why?
Thanks.
Click to expand...
Click to collapse
I like TWRP. It works well with the new phone and Roms that are coming out plus it is so easy to use. Never liked CWM very much. You did right by reverting to an older version of TWRP I had to do that once.
TWRP... i don't even consider anything else.
Do you guys know why my phone gets stuck on the samsung logo everytime i restart my phone?
Doesn't matter what ROM i use it always happens....
Did you do a factory reset, system wipe, preload wipe, cache wipe, and dalvik wipe? Or try fix permissions from recovery?
If not, go do all of those.
If that doesn't work, something is missing from the system partition that is keeping it from booting. Which means you deleted it. :good:
Dubbsy said:
Did you do a factory reset, system wipe, preload wipe, cache wipe, and dalvik wipe? Or try fix permissions from recovery?
If not, go do all of those.
If that doesn't work, something is missing from the system partition that is keeping it from booting. Which means you deleted it. :good:
Click to expand...
Click to collapse
I did ALL of those, still have the problem.
So.... I just ODIN-ed back to stock and going to root and basically re-do everything -_-
Been using twrp since rooting note II. I wanted to try out 4.4 PA but they said to only use cwm. It was late so I decided to be lazy and since I used to use rom manager all the time I installed it to flash cwm recovery then booted into recovery to install touch version. It wasn't showing the touch version so selected to restart to check to see where I saved it to it would not boot past the first "note II" splash screen. Battery pull then back into recovery and went ahead and flashed PA 4.4 and now it will get past the splash screen then shows boot animation but then starts all over.
Is this a rom manager issue?
can I flash twrp from within cwm recovery?
will I have to basically reroot it?
Any suggestions on how to get back to twrp and to a usable phone?
thanks
If you download a .zip of twrp and flash it you will have twrp for your recovery.
As long as you flash a rooted rom, you will be rooted.
Not sure what happened with the boot loop, did you by chance wipe the system without flashing another before booting?
Sent from my SCH-I605 using Tapatalk
cadavjo said:
If you download a .zip of twrp and flash it you will have twrp for your recovery.
As long as you flash a rooted rom, you will be rooted.
Not sure what happened with the boot loop, did you by chance wipe the system without flashing another before booting?
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Nope did my standard wipe cache, wipe dalvik, and factory reset then flashed rom then gapps. Going to go back to twrp and wait for 4.4 to be more stable before I try it out again and maybe then I can use twrp to flash it.
thanks for the help
cadavjo said:
If you download a .zip of twrp and flash it you will have twrp for your recovery.
As long as you flash a rooted rom, you will be rooted.
Not sure what happened with the boot loop, did you by chance wipe the system without flashing another before booting?
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
that didn't work. flashed newest twrp then rebooted into it and tried to flash tweaked and sticks at the splash screen again
jdpeck said:
that didn't work. flashed newest twrp then rebooted into it and tried to flash tweaked and sticks at the splash screen again
Click to expand...
Click to collapse
Have you wiped data at all? You need to wipe data / factory reset when switching roms, and it sounds like you havent.
fallingup said:
Have you wiped data at all? You need to wipe data / factory reset when switching roms, and it sounds like you havent.
Click to expand...
Click to collapse
As stated above, on both cwm and twrp I wiped caches and did factory reset and still having the issues. Once back on twrp I even formatted internal memory thinking maybe rom manager messed something up on it and still can't get passed the splash screen.
jdpeck said:
As stated above, on both cwm and twrp I wiped caches and did factory reset and still having the issues. Once back on twrp I even formatted internal memory thinking maybe rom manager messed something up on it and still can't get passed the splash screen.
Click to expand...
Click to collapse
Copy a ROM to your SD card (external not internal)
Install cwm and format data (actually full format, where /data/media gets wiped) and system
Install rom
Reboot
TWRP has some issues randomly with corrupting /data, that's why I no longer use it.
fallingup said:
Copy a ROM to your SD card (external not internal)
Install cwm and format data (actually full format, where /data/media gets wiped) and system
Install rom
Reboot
TWRP has some issues randomly with corrupting /data, that's why I no longer use it.
Click to expand...
Click to collapse
Finally got it. Thought using odin to flash back to root 66 and start fresh would work but after that it was still going to the splash screen then black and a battery pull had to be done. TWRP back ups would fail when trying to restore, so I reverted back to an older version of twrp and it finally let a back up be installed and it booted up just fine!!
thanks for all the suggestions
Im having a similar problem to yours, I am using twrp and flashed PA 3.99 the phone works great, but if my battery dies or i restart the phone or shut it down it automatically wont get passed the samsung logo, or sometimes the PA logo, the only work arounds ive seen to it is to wipe the cache and dalvik to boot, but when that fails i have to install the whole rom over again. any ideas?
So I was flashing the new Hyperdrive Rom for the Verizon S4 and I made a mistake. After I wiped data/factory reset the device, cleared the dalvik and cleared the cache I accidentally swiped "Reboot" prior to installing a new Rom. Seeing what I did, I pulled the battery and rebooted into recovery. After rebooting into recovery, I re-wiped the data/factory reset, re-wiped the dalvik and re-wiped the cache.
I then installed the new rom RS11 Rom through the Aroma installer and when I click "Reboot", nothing happens. Phone just goes black and the only thing I can do with it is pull the battery and reboot into recovery. I've re-wiped everything multiple times and performed multiple fresh flashes, but this happens every time.
What did I do? Is this thing bricked? I have a nandroid backup made, but unfortunately it is on a separate SD at home and I'm currently at work.
Any help/advice would be tremendously appreciated.
Thanks!
rjbecker26 said:
So I was flashing the new Hyperdrive Rom for the Verizon S4 and I made a mistake. After I wiped data/factory reset the device, cleared the dalvik and cleared the cache I accidentally swiped "Reboot" prior to installing a new Rom. Seeing what I did, I pulled the battery and rebooted into recovery. After rebooting into recovery, I re-wiped the data/factory reset, re-wiped the dalvik and re-wiped the cache.
I then installed the new rom RS11 Rom through the Aroma installer and when I click "Reboot", nothing happens. Phone just goes black and the only thing I can do with it is pull the battery and reboot into recovery. I've re-wiped everything multiple times and performed multiple fresh flashes, but this happens every time.
What did I do? Is this thing bricked? I have a nandroid backup made, but unfortunately it is on a separate SD at home and I'm currently at work.
Any help/advice would be tremendously appreciated.
Thanks!
Click to expand...
Click to collapse
What recovery are you on? Have you tried rebooting through the recovery rather than Aroma?
joshm.1219 said:
What recovery are you on? Have you tried rebooting through the recovery rather than Aroma?
Click to expand...
Click to collapse
I'm on OUDhs CWM Touch Req0very v1.0.3.5.
I'm worried to reboot through the recovery, because it's telling me "ROM may flash stock recovery on boot. Fix?"
^^Will I lose root if I say ok to that?
You can Odin back to stock and start over as worst case scenario.
powered by hashcode safestrap hyperdrive 10.2
decaturbob said:
You can Odin back to stock and start over as worst case scenario.
powered by hashcode safestrap hyperdrive 10.2
Click to expand...
Click to collapse
I've read things in the past about going back to stock and losing the ability to re-root. Is there a way to avoid that?
rjbecker26 said:
I've read things in the past about going back to stock and losing the ability to re-root. Is there a way to avoid that?
Click to expand...
Click to collapse
You are mdk base and using Loki exploit to load custom recovery right?
powered by hashcode safestrap hyperdrive 10.2
rjbecker26 said:
I'm on OUDhs CWM Touch Req0very v1.0.3.5.
I'm worried to reboot through the recovery, because it's telling me "ROM may flash stock recovery on boot. Fix?"
^^Will I lose root if I say ok to that?
Click to expand...
Click to collapse
I don't think you will, I usually say Yes when it asks that and never had a problem. Can't make a guarantee.
joshm.1219 said:
I don't think you will, I usually say Yes when it asks that and never had a problem. Can't make a guarantee.
Click to expand...
Click to collapse
Said yes to it. Same thing happened. Just a black screen and only a battery pull got me back to recovery.
decaturbob said:
You are mdk base and using Loki exploit to load custom recovery right?
powered by hashcode safestrap hyperdrive 10.2
Click to expand...
Click to collapse
Yup, mdk base and using Loki. Are there instructions for how to go back to stock and re-root?
rjbecker26 said:
Said yes to it. Same thing happened. Just a black screen and only a battery pull got me back to recovery.
Yup, mdk base and using Loki. Are there instructions for how to go back to stock and re-root?
Click to expand...
Click to collapse
I am sure there are...not first time some one had to go back to first base. You will need mdk tar file for Odin. Probably a couple out there. I don't have any links.
powered by hashcode safestrap hyperdrive 10.2
SOLVED
Installed my nandroid backup when I got home, the re-wiped and re-flashed hyperdrive rs11. All is good!
Thanks for the help.
Similar problem, can't get the solution! Please help!
I can no longer get my verizon Samsung galaxy s4 into recovery mode with power+home+up button.
I always get to a screen that says
"Downloading.... Do not turn off target!!"
Could not do normal boot.
ODIN MODE
PRODUCT NAME: SCH-I545
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
KNOX KERNEL LOCK: 0 X 0
KNOX WARRANTY VOID: 0 X 0
CSB-CONFIG-LSB: 0 X 30
WRITE PROTECTION: ENABLE
eMMC BURST MODE: ENABLED
This also happens when I tried to do a factory reset and also when I tried to to the OTA update. (They both failed and I got stuck on the same screen)
I can boot the phone by pulling the battery and pressing power+down+home.
Then it says:
Warning!!
A custom OS can cause critical problems in a phone and installed applications.
If you want to download a custom OS, press the volume up key.
Otherwise, press the volume down key to cancel.
I press the volume down key and then I can use my phone, but I can never get into recovery mode or use any different roms.
How can I fix this problem?
Thanks in advance for your knowledge and help!
Verizon Galaxy S4
Android 4.3
Model SCH- I545
Baseband version I545VRUEMJ7
Build number JSS15J.I545VRUEMJ7
Hardware version I545.06