Hello everyone, I've been usuing Xda to troubleshoot all my problems for years now and this is my first time posting because i couldn't find a solution for my problem this time.
I'm trying to flash CyanogenMod 11 on my Galaxy Star Advance SM-G350E, I'm running twrp 3.0-2
Before flashing the rom, i got stuck on wiping system to prepare for the new rom, i was stuck for more than 30 minutes on formatting the system, i resolved this by ticking the (use rm -rf instead of formatting) option on twrp's settings. After ticking that, the wipe completed in seconds so i went on to flash my rom, but when flashing, i get stuck on ( formatting system ).
I tried waiting, but it's been over half an hour and still nothing, i tried troubleshooting the issue for hours and couldn't find anything online, so I'm posting here because i know i can count on my dear members . Any pointer are greatly appreciated.
Related
Hello
Today I was upgrading to the latest starburst rom...this was not the first time I upgraded roms and i did the exact same thing I had done in the past which included wiping data wiping cache wiping dalvik and then flashing....
when i did this and restarted my phone it wouldnt load past the boot screen...after the boot animation the phone stayed black...i repeated steps 1-3 again hoping i just did something wrong...but still nothing
i went back to look at the directions and i say that the developer said to format the system under mounts and storage...in bolded font...i thought maybe thats why it wasnt working so i did just what he said...
now when i load my phone it doesnt load at all and when i open cwm i get a string if e: errors basically saying that it cannot find the drive
if anybody has any advice on how to recover from this I would be extremely greatful
Im having the same problem cant figure out how to fix it.
First off, I have done a search and read dozens of threads, none of which solved my problem...
I have a wifi xoom, which I rooted many months ago without any problems. Recently updated to 3.2 like a month ago or so. I have not made ANY changes within the last month, and the tablet has been working perfectly.
A few days ago, I left the tablet to charge. Once charging was complete, I turned it on and its stuck on the boot animation. I just keeps playing over and over again, I've let it sit for 10+ minutes, with nothing happening...
I tried removing the SD card then rebooting, and its the same result....
Please help! If need be, I can go back and look up all the exact steps I've done to root and get it to where it is today. Like I said though, it has been working perfectly, and I have not made any new changes in at least a month... I don't see why this would happen all of a sudden...
Have you tried to reinstall firmware?
Regards.
GReddySetGO said:
First off, I have done a search and read dozens of threads, none of which solved my problem...
I have a wifi xoom, which I rooted many months ago without any problems. Recently updated to 3.2 like a month ago or so. I have not made ANY changes within the last month, and the tablet has been working perfectly.
A few days ago, I left the tablet to charge. Once charging was complete, I turned it on and its stuck on the boot animation. I just keeps playing over and over again, I've let it sit for 10+ minutes, with nothing happening...
I tried removing the SD card then rebooting, and its the same result....
Please help! If need be, I can go back and look up all the exact steps I've done to root and get it to where it is today. Like I said though, it has been working perfectly, and I have not made any new changes in at least a month... I don't see why this would happen all of a sudden...
Click to expand...
Click to collapse
No need to panic.
When you rooted, did you install CWM Recovery, and if so, do you have a recent nandroid backup? Have you tried rebooting into recovery?
What steps have you followed to get out of your bootloop?
Yes, I have Clockword Mod Recovery 3.2.0.0 R4c 100611-1150
Upon attempting a restore everything appears to work properly until the end when it gets to restoring data, I get an error, regardless of which restore image I use(I tried all the ones I have). It reads as follows:
"Restoring data...
Error removing /data/data/com.noshufou.android.su/cacheError while formatting /data!"
I also attempted a clean wipe/factory reset with similar unsuccessful results. I get an error during formatting data, which reads:
"Formatting /data...
Error removing /data/data/com.noshufou.android.su/cacheFormatting /cache..."
The rest of the formatting appears to run successful for /sd-ext and /sdcard
Have you manually tried to format the system, cache and data? This can be done from the advanced menu.
Sent from my Xoom using Tapatalk
jerrycycle said:
Have you manually tried to format the system, cache and data? This can be done from the advanced menu.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Can you please provide me with more detailed instructions?
From the advanced menu I see:
Reboot Recovery
Wipe Dalvik Cache
Wipe Battery Stats
Report Error
Key Test
Partition SD Card
Fix Permissions
Sorry, we're forgot talking about Cwm. It's under mounts and storage.
Still the same result as before... I went to mounts and storage > format /data
"Formatting /data...
Error removing /data/data/com.noshufou.android.su/cacheError formatting /data!"
Try format system first then data and cache.
My suggestion would be to go back to stock and then re-root. You can find the stock download on the Moto Dev home page.
+1. Restocking link. MOTODEV > Produ / Software http:/.ly/sQtpKQ bit cts > Device. Then use universal root method reroot.
Sent from my Xoom using Tapatalk
Thanks everyone! I was hoping I would be able to fix it without going back to stock, but since I was unable to I just went that route.
Going stock worked, and I am back to where I was before, so thank you for the advice! In case anyone else may have this problem, this is what I did:
Went back to stock using this: http://forum.xda-developers.com/showthread.php?t=1049485
Then rooted using this: http://forum.xda-developers.com/showthread.php?t=1242241
Then got back to 3.2.1 using this: http://forum.xda-developers.com/showthread.php?t=1278214
I previously posted in the local Galaxy S3 i747M section with the same problem, but now the issue is worse than before.
Here's my previous thread:
http://forum.xda-developers.com/galaxy-s3-att/help/boot-loop-plugged-to-ac-twrp-wipe-data-t3070064
A note that I'm no stranger to flashing and the inner workings of Android architecture (ROMs and general hardware), . But for the sake of this issue, please feel free to treat me like a noob if you think it would help elaborate any procedures I should follow or troubleshooting steps I should take, or just throw ideas at me like the software dev that I am and expect me to figure it out on my own.
Some background:
Recently (around beginning of April), my phone began to exhibit strange behaviour - reboots when reading/writing from internal memory (not uSD card), unable to wipe /data partition in TWRP or CWM. I would also get bootloops when I was plugged into direct AC charging (no problems if plugged into a computer for charging, though).
When in TWRP, CWM, and Philz, I would not be able to wipe the /data partition or anything in it. Installing anything to /system also caused a crash (though wiping it didn't cause any issues). Doing a factory reset wipe would also cause the recovery to "crash" - the recovery would freeze up and the phone would reboot. I could not restore a NANdroid, I could not install a new custom ROM. In TWRP, if I opened up a terminal window and manually tried to repair the /data and /system partitions with the e2fsck command, it would still freeze up and crash.
At that point, I downloaded the stock 4.4 firmware image (I think it was NF2?) from Sam Mobile and flashed it via Download Mode + Odin. Booted it up and ran the phone stock for probably a week. Then, I carefully used Odin to flash a freshly downloaded (and MD5 verified) TWRP 2.8.6.0 TAR image and SuperSU. Flashed both via Odin just fine. From there, I mounted the microSD card - I didn't want to touch the internal memory for now - and copied over a fresh downloaded copy of a CM12 based ROM (also MD5 verf'd) to it. From there, still in TWRP, I successfully flashed a 4.4.x TouchWiz-based ROM.
Take note that at this point, doing anything to attempt to wipe /data still leads to crashing the recovery. Nothing I have done has resolved this issue. I left that issue alone, just happy to have a working phone.
That above procedure seemed to work. I could then use the phone for about 2 weeks. Then my phone started crashing again, same as before: only when I was doing something that was reading/writing the internal memory. E.g. music, podcasts, etc.
I followed the same procedure with Odin + stock firmware > reboot > Odin + TWRP + SuperSU > flash custom ROM. Worked fine again for 2 more weeks.
Here I am 1 month later, same problem as the last 2 times. This time, however, after flashing the custom ROM, it does not boot up now. My phone is at home because I cannot use it. Last night, upon trying to boot up S3rx and PAC 5.1, I literally let it sit at the boot animation for 1 hour, each, and neither got past the boot animation. I'm familiar with ROMs sometimes taking say 10 minutes upon very first boot on a clean flash, but I gave up after about 1 hour (in fact, 1.5 hours for PAC 5.1, which was my second attempt last night). It's to the point where I'm certain if I left my phone plugged into the AC, it would still be at the boot animation over 12 hours later.
I know of the NAND memory corruption issue that S3's had previously, and I did flash the stock firmware that came out at the time (I think it was an Lxx based bootloader+firmware). But that was years ago, end of 2012 if memory serves me correct.
Thoughts on what I am facing? What I should try and do next? Where to go from here? If this is a hardware issue that is beyond fixing with flashing things in fastboot/ADB/Odin, then I'll face defeat and look for a new phone. But if I can hang on to this phone for just a little bit longer...
Thanks!
Hi there
Please note the following sticky from the top of the Assist section,
> General discussion > XDA Assist > The Purpose of XDA Assist [Please Read]
As a senior member on XDA, I am quite confident that you know where your device section is (you already asked something there) and where to ask for help.
Thanks for understanding
Good luck
Hello to everyone, posting this here as I don't have access to ask in the forum post for BlissPop - I.E fresh user
I'm having issues with my "recalled" shield tablet (wifi), I had it flashed to BlissPop successfully previously but when I tried reflashing it the other day I was met with a major roadbump: It just won't load the ROM.
The tablet freezes at the screen following the installing and optimization of each application - basically my screen is stuck at a small wall of text saying the following:
"BlissPop is starting...
Powered by Team Bliss
Starting apps.
Please wait for the optimization process to finish."
And before you ask, yes I have waited long enough (left it on through the night just to be sure - this thing won't load).
My procedure is as follows.
Bootloader is CWM and it is rooted beforehand.
1st off going into recovery mode.
#2 Wipe data/cache/dalvik cache - done
#3 Installed BlissPop via sideload, then gapps_pico afterwards (I've tried wiping cache+dalvik before installing gapps to no help.)
#4 Rebooting from CWM, here I've tried both allowing and denying CWM to "fix" root settings.
I've tried the first ROM I installed (when wifi/lte versions were available) and the newer releases - same problem with both.
After this I am met with this screen that won't budge, anyone got a possible solution to this issue?
Hey I just received my replacement tablet and was going through this process too. I did some digging around and found / remembered that having an external SD card socketed can cause this problem. So I powered my device off, removed the card and then rebooted without major issue.
Hope this helps.
I don't have any SD card in my tablet though, thanks anyways.
Did you format system?
If not then do format system/data/cache
Sent from my P4S using Tapatalk
Tried doing a format of system as well as data/cache/dalvik, still getting same result :/
Not sure its still helpful or not...i saw the xda thread regarding to this thread and whoever tried to flash the last zip got stuck at boot. So I'm guessing if you will flash a different one (by this time maybe they upload a new one) maybe you could get rid of it..
Sent from my P4S using Tapatalk
When I switched to BlissPop I had to format /data because TWRP was unable to wipe it. TWRP offers that option unter "advanced wipe". Might be the same with CWM.
any help my phone stuck on this boot loop and i dont know what to do now , any fix ? i dont wanna have broken phone i did everything that u guys said nothing works
So I have this n5110 tablet which has performed without problems since I bought it last year in December. Device is running TWRP recovery and Resurrection Remix 5.7.4 (CM13 based).
The symptom: first time it happened was during an "apps upgrade" session. Google Play Store updated a bunch of apps and all in sudden the tablet froze. Completely. Dead. Clock in status bar stopped working. After an hour I gave it a reset (hold power until it reboots). The result: boot loop. After finishing the boot process, it showed the lock screen for couple of seconds, then reboot ... and so on.
Went into recovery, did a wipe of data & cache & dalvik & system and started all over. After restoring the system, i started installing apps. All in a sudden ... BOOM ... same problem again.
You can imagine - I went through this process about 7 times. Then I realized, no matter what I do, if free storage has decreased to about 7.6 GByte, the big boom happenes and the phone is dead (boot loop).
I began to suspect a nand problem. So after restoring the system (without reinstalling all my apps) I installed “eMMC Brickbug Check” which also does a memory check. The app showed no problem. All good.
So back to recovery, into terminal and there I tried to “zero” the data, cache and dalvik partitions using “dd if=/dev/zero bs=1M of=/dev/block/mmc...” - you get the idea. No error messages here so all 3 partitions did not cause a nand writing problem.
So I'm stuck now. Before I try to replace the motherboard ... does anyone have an idea on how to really “test” the nand to confirm my suspected nand write problem?
Thanks for any help!
Markus.
oldschool63 said:
So I have this n5110 tablet which has performed without problems since I bought it last year in December. Device is running TWRP recovery and Resurrection Remix 5.7.4 (CM13 based).
The symptom: first time it happened was during an "apps upgrade" session. Google Play Store updated a bunch of apps and all in sudden the tablet froze. Completely. Dead. Clock in status bar stopped working. After an hour I gave it a reset (hold power until it reboots). The result: boot loop. After finishing the boot process, it showed the lock screen for couple of seconds, then reboot ... and so on.
Went into recovery, did a wipe of data & cache & dalvik & system and started all over. After restoring the system, i started installing apps. All in a sudden ... BOOM ... same problem again.
You can imagine - I went through this process about 7 times. Then I realized, no matter what I do, if free storage has decreased to about 7.6 GByte, the big boom happenes and the phone is dead (boot loop).
I began to suspect a nand problem. So after restoring the system (without reinstalling all my apps) I installed “eMMC Brickbug Check” which also does a memory check. The app showed no problem. All good.
So back to recovery, into terminal and there I tried to “zero” the data, cache and dalvik partitions using “dd if=/dev/zero bs=1M of=/dev/block/mmc...” - you get the idea. No error messages here so all 3 partitions did not cause a nand writing problem.
So I'm stuck now. Before I try to replace the motherboard ... does anyone have an idea on how to really “test” the nand to confirm my suspected nand write problem?
Thanks for any help!
Markus.
Click to expand...
Click to collapse
Answering my own question here: after quite some hours of trying it turned out that my tablet seems to be just fine. The problem is something totally different and weird. If you are interested in what's going on, please continue reading here: https://forum.xda-developers.com/android/help/help-app-bricks-samsung-tablet-try-to-t3661516