I flashed a rom and then this problem started happening since. My phone tries to go to the samsung boot animation screen but never goes through it, it vibrates and then reboot, i tried installing stock rom, etc, i can now go to recovery and download mode.
You might need a jtag
But if i can go through recovery and download mode, maybe there is something i could do to fix this issue?
errusdan said:
But if i can go through recovery and download mode, maybe there is something i could do to fix this issue?
Click to expand...
Click to collapse
I Can install firmware through download mode.!""
Me too, i tried installing stock firmware and all that. Even i am able to use the aroma filemanager from recovery, to see all my files, and when i delete system, preload, data, cache, etc i can see that in fact the device deletes them correctly.
Sorry I miss understand, you can go in download and recovery, my bad.
Have you tried factory reset, Flash original firmware, factory reset, let it boot
What was your original firmware which file(s) did you use?
When the thing you said happened i went on the store and Luckly they replaced my phone. Your phone probably ruined thats what happens when you play with it:cyclops:
Yeah i know that there are risks when you install another roms and such. I've read that it can corrupt your internal sd card, maybe that is what happened to me? because i tried installing different firmwares, kernels, recoveries, wipe data, wipe cache, wipe dalvik cache, wipe system, wipe preload, etc, even i tried installing boot animations, and it stucks at the boot animation screen samsung galaxy, it tries to load but then it vibrates and restart like a loop.
I am now with the russian 4.4.2 rom, and yes i know that i cannot downgrade because of the bootloader version. But i tried installing modified roms with zip (like cm 11) in recovery, and it installs correctly without errors, the problem is with the bootloop.
Related
I tried to root my wifi Note 10.1(wifi) using TWRP and the SuperSU flashable zip, but when wiping cache and Dalvik the tablet shut down. Now when I try to boot the device it only plays part of the boot sound and gets stuck on the "Samsung" logo. I've tried searching for ODIN flashable stock firmware, but with Hotfile being down(sammobile's file host) and the rest requiring a paid subscription to their site, I'm screwed.
I've tried using Kies' emergency recovery option, but it won't recognize the device as needing recovered. When I try to search for updates through Kies it tells me the model name is invalid(P600, SMP600, SM-P6000ZKYXAR, Galaxy Note 10.1 2014).
I can still boot into download mode and TWRP.(I REALLY should have made a backup first.)
All I need is the stock US(XAR) firmware, preferably ODIN flashable. I'm not sure if I trust TWRP to flash it just yet considering it crashed wiping dalvik, but if it's my only option I'm willing to try it.
I have seen somewhere that TWRP is a bit temperamental on our devices with wiping cache, and you sometimes have to do it twice, have you tried it the 2nd time ?? Use the advanced menu, wipe cache and reboot.
Edit
http://forum.xda-developers.com/showthread.php?p=47379905&highlight=cache#post47379905
i did this
::
jpearn said:
I have seen somewhere that TWRP is a bit temperamental on our devices with wiping cache, and you sometimes have to do it twice, have you tried it the 2nd time ?? Use the advanced menu, wipe cache and reboot.
Edit
http://forum.xda-developers.com/showthread.php?p=47379905&highlight=cache#post47379905
Click to expand...
Click to collapse
It took a long time to finish, but it successfully wiped the cache the second time and booted successfully! Thanks for the link by the way.
Hi all, hoping this is a stupidly simple fix. I wanted to update to latest stable CM7 and so downloaded and flashed it from CWRecovery,
I also ran the factory reset, and cleared the cache.
When I boot, it shows the blue loading screen, then comes to the "Welcome to ADR6300" and reverts to the CyanogenMod7 loading screen..
Then, it keeps bouncing back and forth between these two screens until I pull the battery...
You didn't mention the order of what you did. Assuming you have no valuable data, I would just start over.
Reboot into recovery
Wipe system
Factory reset
Flash ROM
Flash GAPPs (if desired)
Reboot into ROM
Also, ensure you're on the latest CWM, first.
[Solved]
PonsAsinorem said:
You didn't mention the order of what you did. Assuming you have no valuable data, I would just start over.
Reboot into recovery
Wipe system
Factory reset
Flash ROM
Flash GAPPs (if desired)
Reboot into ROM
Also, ensure you're on the latest CWM, first.
Click to expand...
Click to collapse
Worked perfectly! Thank you!!
Apparently the problem was having the wrong version of GAPPs. I was reinstalling but Wiping system was the step I had skipped!
I've looked around a bit and can't quite find someone that has had my specific situation.
I have a AT&T S3 SGH-I747 that is rooted running stock 4.1.1 with CWM 6.0.4.7. I have updated the modem and bootloader (Baseband - I747UCUEMJB and Build # JRO03L.I747UCDLK3).
I have tried to flash custom and stock ROMS with CWM but get stuck on the glowing Samsung logo. I have tried to follow the instructions listed here but I cannot flash the stock ROM with ODEN.
I am not sure as to what to attempt next. I first want to be able to update to 4.3/4.4.2 and then try custom builds.
I have all my apps and data backed up with MyBackup and a Nandroid backup as well.
Thank you.
Are you wiping the cache, davilk, and data before of after flashing the ROM?
I wipe/format before the flash. I factory reset, clear cache, clear davilk, format data, and format system then flash the ROM. I've tried several combinations of clearing/formatting. The flash always goes well and then I reboot. The boot goes and then just sits at the Samsung logo (It does make the AT&T sound during this time)
Hubbins said:
I wipe/format before the flash. I factory reset, clear cache, clear davilk, format data, and format system then flash the ROM. I've tried several combinations of clearing/formatting. The flash always goes well and then I reboot. The boot goes and then just sits at the Samsung logo (It does make the AT&T sound during this time)
Click to expand...
Click to collapse
Try to factory reset once the flash is done if it doesn't boot after 5-10min.
Thanks. I'll give it a shot and we'll see how it goes.
Unfortunately that tip did not appear to help. I still got stuck on the glowing Samsung logo.
I was final able to flash 4.3 using the method here using odin.
Hi,
I was frustrated with the delay in T-Mobile's release of KitKat for the GSIII, so I decided to root my phone last night in order to try flashing CM11 on it. Rooted my phone with Towelroot, installed ROM Manager and CWM, and created backups on Kies and through CWM. Then I proceeded to do data wipe/factory reset, cache wipe, and /system format. Tried to flash CM11, but got a status 7 error.
I freaked out, so I decided to restore everything from the backup I'd created. Restoration seemed like a success, but now I get the error "Unfortunately, the process com.google.process.gapps has stopped" in an endless loop, and it prevents me and any apps from doing anything. I tried clearing dalvik cache in recovery, but the problem still persists. Read on a few threads that I should flash to stock firmware via Odin, but I'm currently on a macbook, so I can't install it.
tl;dr - Prepped to flash CM11, reached status 7 error, got freaked out, and did restore via CWM, only to get infinite loop of gapp crashes. No access to Odin or PC. Not hard bricked or soft bricked, but essentially useless phone. Help? );
if you can still get to recovery, download latest gapps and flash that
Did you factory reset before or after you restored your back up?
Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:
Try to factory reset again
vvnn said:
Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:
Click to expand...
Click to collapse
If I'm not mistaken, there is some device ID that will change each time you flash a new rom. It may be something to do with this ID not matching the one in the restored data. Purely a guess but seems logical to me.
Anyway, factory resetting will most likely solve this for you, but I wanted to add that except in certain circumstances, you shouldn't ever manually format /system. (and one format on any partition is sufficient. There shouldn't be any need to format multiple times). If you format /system, you are wiping the O/S off of your device. Then what happens if you have problems flashing a rom, or firmware? I've seen it happen many times and I often end up spending a couple of days working with them just to get the thing to boot up again!
When you flash a rom, the first thing it does is format /system. So there is just no need to do this manually. At least if the rom fails to flash (such as failing the assert checks), youll still have something to boot into. Hope this helps in the future!
I have had the exact same issue. I have a Samsung note 2 N7105. I rooted made a backup in CWM and flashed ditto n3/s5 rom made another backup in CWM. No issues. Got a bit cocky seen as it was my first time doing anything like that. My next adventure was to try a custom kernel (agni). This didn't go so well, so I tried to do a restorw to my working backup of ditto n3/s5 rom through CMW. restore went smoothly and the phone booted. once I opened the lock screen I got the gapps error as described. I had to do a factory reset to get the phone working and then re-flashed ditto n3/s3. I've since flashed other roms and when ever I try to do a restore, I get the issue described. Note I am using the latest CWM. I putting off flashing and trying any other ROMs because of this issue. I do love dn3/s5 but id love to try others. Anyone can help it would be appreciate.
I'm having some issues flashing any ROM. TWRP will not wipe data, or internal SD
For some reason, when I go to wipe data and factory reset, TWRP will say it was successful, but nothing ever gets wiped. It will only wipe system if I choose to. I've gotten a ROM to flash but when it boots up, all of the old apps and user data are still there and it makes everything crash. I've gotten into settings to do a reset, it reboots into recovery, runs the script, and still nothing wipes.
What I have tried:
Old TWRP, newest TWRP
CWM (seems to wipe but it won't get past the note 2 screen after flashing anything)
Wiping with CWM, flashing TWRP, then flashing a ROM (still loops after the note 2 screen)
Is there a terminal command I can use in TWRP to manually wipe things?
Thanks for any help I can get, I've flashed so many phones I can't remember but I've never had this issue
Maybe flash back to a stock ROM, factory wipe using stock recovery, then flash TWRP?
audit13 said:
Maybe flash back to a stock ROM, factory wipe using stock recovery, then flash TWRP?
Click to expand...
Click to collapse
Well when it bootloops t the Note 2 screen, I have to flash a ROM with Odin to get it working again. I've flashed a stock ROM with Odin, flashed TWRP with Odin, tried the wipes and it never wipes anything... I'm lost...
Isn't there a format function in TWRP that is seperate from the factory reset or advanced wipes? I was also trying to find a terminal command to type in the terminal in TWRP... I'm a little stumped...
I'm sorry, I read that too fast... That may actually work, wipe it in the stock recovery, and just don't let it boot into the system before flashing other stuff... I'm gonna try that out... Thanks man, I'll post back about it...
Since you are flashing the phone with Odin, is it a stock 4.1.1 ROM you're flashing? Which custom ROM are you flashing to the phone?
audit13 said:
Since you are flashing the phone with Odin, is it a stock 4.1.1 ROM you're flashing? Which custom ROM are you flashing to the phone?
Click to expand...
Click to collapse
The stock ROM I used is I317-ODIN-UCUCNJ1-Stock without the booloader packaged in, I'm still on the old bootloader. It's 4.4.2
The ROMS I've tried to flash was
Cyanide (Error 7, says incompatible data, please wipe the phone)
Resurrection Remix (Error 7, says incompatible data, please wipe the phone)
Latest CM10 Nightly
I got CM10 and Resurrection Remix to flash a couple times, but the phone boots and all the old apps and data, including the AT&T ones are still there, and the system keeps crashing. Then I change the recovery to CWM because it seems to wipe, change back to TWRP, flash the ROM and gapps again, but it bootloops at the Note 2 screen.
Should I try the 4.1.1 ROM and CWM? Whenever I'm going from a stock TW to non-TW I like to format everything, data, cache, system, and internal SD, but of course TWRP won't wipe the data or the internal SD.
It's probably because the bootloader and modem are too old for the roms. Recent roms will need updated bootloaders.
Ok, I had some more time to mess around with this today and figured it out. I feel kind of dumb but oh well, I got it.
TWRP was already loaded on, so I went to messing with it again. The 'Swipe to factory reset' was not wiping the data, and there was the 'Format Data' button right there in front of me. I did the factory reset, format data, rebooted recovery, wiped dalvik, cache, and system, then flashed the ROM and everything booted up just fine.
Thanks for all of the help!