This is an AT&T Galaxy S4 SGH-I337. The baseband is OC1 and I have Goldeneye51 rom installed with root. I tried wiping the cache. I also tried to downgrade the kernel but I get an error like "check fail: boot" or something like that. All I want is to backup pics and videos from the internal storage before I do a factory reset.
0siribix said:
This is an AT&T Galaxy S4 SGH-I337. The baseband is OC1 and I have Goldeneye51 rom installed with root. I tried wiping the cache. I also tried to downgrade the kernel but I get an error like "check fail: boot" or something like that. All I want is to backup pics and videos from the internal storage before I do a factory reset.
Click to expand...
Click to collapse
Without it booting via (custom - which you obviously don't have, nor can install at this point) recovery or into the OS, you just don't have any options unfortunately. That is, unless you know someone with an NSA type job that has access to tools to read the nand storage directly. Some Galaxy phone developers have made no wipe stock files to restore the phone, but I don't think they have any for the ATT one, though not 100% sure of that. What did you do to mess it up and which bootloader and update were you on to start before installing the rom?
My wife was calling someone. It suddenly froze and rebooted into this bootloop. after a while it gave a message that 'system process is not responding, wait or ok' or something like that. I wiped the cache and now It will show the home screen for a split second, vibrate, then back to the boot logo. I have proper samsung drivers installed but during the bootloop, Device manager only shows 'Samsung Android' and says no driver installed'. IIRC, before rooting and installing GE51, we were on NB1 or NC1 which at the time was the latest stock OTA.
I guess what I was hoping to hear was that I could use adb sideload to install a special apk that would backup/fix something during boot. Thank you very much for the confirmation. I suppose my next step could be to do the factory reset, then dd an image of /data and use data recovery on that image?
Related
Hi Guys
I am new to playing around with android but not to electronics. I have a Verizon Samsung Galaxy Tab 10.1 16gb (SCH-i905) with current 4g service.
Here is the problem I am having:
It started yesterday, I was browsing the web and the tablet froze and then rebooted. After the reboot programs randomly freeze and crash, if I reboot anything I have downloaded is gone and anything I deleted is back and I can't install or remove apps. I figured I had something corrupted and a factory wipe would fix it. Unfortunately when I perform a factory wipe from the menus or through Android recovery nothing happens. The tablet boots up like nothing was erased. Still has all my accounts, security pin, apps, and so on.
So after that I figured I would flash the tablet, I found the thread here in the development forum with the stock 3.2 image to load through ODIN. I downloaded everything, followed the instructions. ODIN says the flash was successful but when the tablet reboots it still has all my info and is running 4.0.4. I have tried this multiple times. I have tried loading CWM with ODIN but it will not stick.
Any thoughts? If you need more information I will get it, I am just stuck and can't find anything that helps me with this problem!
Thanks for your help!!!
If you want cwm to load after you install it using odin, then you must immediately boot the tablet into recovery without letting it run normally. During the normal boot process, CWM is deleted and the stock recovery is restored. Therefore once Odin finishes installing CWM, hold the volume up button and once you get to the recovery mode you will be running CWM instead of the stock recovery module.
Regards,
Michael
Yes, I did read that in the multiple thread about installing CWM and have gone into recovery directly after ODIN reboots the tablet, however it is still only the stock recovery app.
Any ideas why the factory reset / data wipe won't work?
So after several more hours working on this problem I think I have come across the root cause. I believe that my internal storage has corrupted and is now only mounting in Read-Only mode. From everything I can find online, without having root access previously, this is a no go for fix it yourself.
In case anybody happens on this post down the road, I have been unable to find a resolution and it would appear I must sent the unit back to Samsung for repair.
Mixinitup4Christ said:
So after several more hours working on this problem I think I have come across the root cause. I believe that my internal storage has corrupted and is now only mounting in Read-Only mode. From everything I can find online, without having root access previously, this is a no go for fix it yourself.
In case anybody happens on this post down the road, I have been unable to find a resolution and it would appear I must sent the unit back to Samsung for repair.
Click to expand...
Click to collapse
factory reset through the stock recovery should be able to get you out of it (RO filesystem).
pershoot said:
factory reset through the stock recovery should be able to get you out of it (RO filesystem).
Click to expand...
Click to collapse
I guess that blows my theory out of the water. I can't make heads or tails with this. No matter what I do, Menu Factory Reset, Recovery Wipe/Reset, ODIN Flash Stock EG01 firmware, ODIN flash CWM Recovery as soon as this device reboots I am right back where I started....... GAH!!!
Thanks for letting me know I'm probably wrong.
Mixinitup4Christ said:
I guess that blows my theory out of the water. I can't make heads or tails with this. No matter what I do, Menu Factory Reset, Recovery Wipe/Reset, ODIN Flash Stock EG01 firmware, ODIN flash CWM Recovery as soon as this device reboots I am right back where I started....... GAH!!!
Thanks for letting me know I'm probably wrong.
Click to expand...
Click to collapse
it has to be factory reset through the stock recovery (it will format /data), not through CWM.
rozeins gone
pershoot said:
it has to be factory reset through the stock recovery (it will format /data), not through CWM.
Click to expand...
Click to collapse
Yup, done that multiple times. I'll take video of it if you want, Factory Reset in stock recovery has no effect.
Mixinitup4Christ said:
Yup, done that multiple times. I'll take video of it if you want, Factory Reset in stock recovery has no effect.
Click to expand...
Click to collapse
odin flash CWM (you can use 6.0.2.8 in JB CM10 folder on droidbasement), boot it and try to format the /system partition first then /data.
pershoot said:
odin flash CWM (you can use 6.0.2.8 in JB CM10 folder on droidbasement), boot it and try to format the /system partition first then /data.
Click to expand...
Click to collapse
Will Do, ODIN3 1.85?
pershoot said:
odin flash CWM (you can use 6.0.2.8 in JB CM10 folder on droidbasement), boot it and try to format the /system partition first then /data.
Click to expand...
Click to collapse
HI Pershoot!
I forgot to say thanks for your help!! I appreciate someone smarter than me lending a hand.
That said, I just tried to flash CWM from DB Galaxy Roms/CM10 folder. Upon reboot the tablet still entered stock recovery, I have tried this several times, but this time I took a video. If you feel so inclined to watch it maybe you can catch me doing something wrong....
Again thanks for your help!!
Video of me doing the Stock Recovery Factory Reset
Video of me attempting to flash CWM from droid basement
Mixinitup4Christ said:
HI Pershoot!
I forgot to say thanks for your help!! I appreciate someone smarter than me lending a hand.
That said, I just tried to flash CWM from DB Galaxy Roms/CM10 folder. Upon reboot the tablet still entered stock recovery, I have tried this several times, but this time I took a video. If you feel so inclined to watch it maybe you can catch me doing something wrong....
Again thanks for your help!!
Video of me doing the Stock Recovery Factory Reset
Video of me attempting to flash CWM from droid basement
Click to expand...
Click to collapse
I had to do this on mine. http://techne.alaya.net/?p=8829. I rooted and modified the file described in the steps. Weirdly enough it still booted into stock recovery the first time I installed CWM. I installed CWM one more time and the tablet now boots into CWM.
I recently formatted my internal storage because I felt like I needed a clean wipe. After doing so, flashing anything and rebooting into it will make it hang on the Samsung logo. I flash everything through TWRP v2.5.0.2 and I never had problems until I formatted. Now to get anything to work, I have to "format data" through TWRP and flash after that in order to boot into anything (every single time). And even after booting into it, I can't flash anything (or even simply reboot) without having to see the stuck screen again. Any ideas? My phone is MDK.
You need to update TWRP. Latest is 2.6.3.1. Older twrp doesn't use the proper symlinks for the internal data partition that changed in 4.3.
WhoNeedszzz said:
You need to update TWRP. Latest is 2.6.3.1. Older twrp doesn't use the proper symlinks for the internal data partition that changed in 4.3.
Click to expand...
Click to collapse
Thanks! I think that worked
I just rooted my Galaxy I9505 and flashed a custom ROM available on this link http://forum.xda-developers.com/show....php?t=2789666
I used TWRP recovery method and the ODIN showed the processes as successful.
But when I flashed the ROM it was successful (but in threads it showed message can't read Sdcard in red colour). After flashing I rebooted my phone but now it gives message: unfortunately the process com.android.systemui has stopped
NOTE:My phone was encrypted before I rooted my phone.
Please help..I m unable to use my phone
Asadbodla said:
I just rooted my Galaxy I9505 and flashed a custom ROM available on this link http://forum.xda-developers.com/show....php?t=2789666
I used TWRP recovery method and the ODIN showed the processes as successful.
But when I flashed the ROM it was successful (but in threads it showed message can't read Sdcard in red colour). After flashing I rebooted my phone but now it gives message: unfortunately the process com.android.systemui has stopped
NOTE:My phone was encrypted before I rooted my phone.
Please help..I m unable to use my phone
Click to expand...
Click to collapse
well, the link to the custom rom is down, have you tried to wipe data,cache,dalvik and battery stats,
or try another rom, or restore your nandroid backup,
are you sure that rom is for your device?
hackerse7en said:
well, the link to the custom rom is down, have you tried to wipe data,cache,dalvik and battery stats,
or try another rom, or restore your nandroid backup,
are you sure that rom is for your device?
Click to expand...
Click to collapse
Yes I wiped the data, cache, dalvik but not the batter stats. I tried backup but it also didn't work. The phone continued to restart from the encrypt password screen and didn't continue to home screen.
In the end I unrooted the phone to the stock firmware from sammobile and it went all well (I had to wipe that data from recovery after unrooting)
The only I am facing now is that I can't update via OTA (it shows the message phone is modified). Rest everything is fine.
Asadbodla said:
Yes I wiped the data, cache, dalvik but not the batter stats. I tried backup but it also didn't work. The phone continued to restart from the encrypt password screen and didn't continue to home screen.
In the end I unrooted the phone to the stock firmware from sammobile and it went all well (I had to wipe that data from recovery after unrooting)
The only I am facing now is that I can't update via OTA (it shows the message phone is modified). Rest everything is fine.
Click to expand...
Click to collapse
Also i would like to mention that while flashing the ROM, it couldn't find the MD5 file and also couldn't read the sdcard.
Hi all,
Sigh. So it looks like I bricked my Samsung Tab E Verizon. I rooted it with King root and when I removed it, it is now in a endless boot loop. I've tried all sorts of things to try and recover it.
I used SkipSoft to set it up to be flashed but odin fails everytime. I was using the new ROMS found on this Forum. I've tried putting it into download mode and manually flash it and that didn't work. I can't Re-Root it as it won't stay on long enough to Root and they always fail. Right now I'm at a loss.
Can anyone help?
Thanks.
Do you have custom recovery or default? if you have default you can hold the home button and vol up button then the power button to get into recovery, once your done with that you can wipe cache and reboot, if that STILL does not work then factory reset your phone and re wipe cache, i know losing data sucks but its better then a brick. (this will work 99% of the time because the default recovery automatically re-installs stock rom)
If you have a custom recovery, then i recommend wiping everything including dalvik cache etc, making sure EVERYTHING is squeakly clean (execpt recovery obviously) , and find the driver for your samsung phone and download it on your computer and install, once you are done with that, put your phone into download mode, find your original STOCK rom for your phone, download it and flash it with odin, from there IF successfull you should have a fresh boot of your stock rom, then you can re-root and go on with your day.
Also make sure once you re-gain root access backup your rom so you will always have a plan b if everything goes bad. i cannot recommend this enough, even if you are an expert with flashing, there is always that small percentage things will go wrong and you should always have that backup ready.
Hi!
Thank you very much for the reply. You know, that was one of the things i tried initially when it happened. When I tried it, it wouldn't go into recovery mode. I then went on the odyssey of hell in trying to recover it.
When I read your post I was thinking; "Yeah I tried that", but then I thought I would give it another shot. I went into Factory Reset, it then actually went into the recovery menu. I deleted the cache and set it to data/factory reset and it's still looping. I get an error saying; "E:failed to mount /preload (no such directory)". I then tried to run update from external storage and it's telling me that it's disabled. I tried to update from ADB and it's disabled. I tried to apply from cache and it says; "APPLY_CACHE is depreciated". It's still looping.
Urghhhhhhhhh.......
oh man, my stupidity has done it again.
i did these stupid things below by short:
sm n910g sintel from singapore
last build is 5.0.1 N910GDTU1BOF1
the recently update to 6.0.1 N910GDTU1DPG4
no good
downgrade to 5.1.1 N910GDTU1DPG4
successfull
still no good
want to try dr ketan m6 custom rom
upgrade to 6.0.1 again using smart switch
device stuck in recovery loop
downgrade again with odin but failed
then stuck in firmware upgrade failed screen
can't load stock recovery
can load download mode
try flash cutom twrp & cwm recovery for 6.0.1 since the downgrade failed
can manage to start up recovery of each version
but getting mount /system error
now the device won't boot into tw ui
only can but into twrp/cwm recovery
what should i do now?
please help out
many thanks to you
------------------------------------------------------
since i don't know how to use adb to push file trough twrp
i use micro sd card to flash dr ketan's m6 rom
i factory wipe in cwm
then i install by ext sd following the insturction given in dr ketan's thread
this time i manage to go through samsung galaxy note 4 logo and to samsung logo and the logo is now blinking with the uper right hand light
still not sure if it's under looping cause just 2 minute is wrote this status, still waiting
i notice when in galaxy note 4 logo, i saw there is yellow santance in the top left
saying firmware bit and kernel bit
what does that mean?
-------------------------------------------
currently the device is in apps installing page
i think the installation is a success, is it?
still waiting it to be fully usable
-------------------------------------------
yes!!!
it was a success!!!
currently i'm running dr ketan m6 on my n910g
it's so smooth
but one thing here
before i flash this rom
i did the facrtory reset in the cwm
now that the rom is install, and the esential update that comes with it is installed too
should i go for another factory wipe?
if so, which factory wipe should i choose?
the one in cwm or the one in the m6 system?
-----------------------------------
device is kind of burning now
i wonder is it that i choose to restore all the apps from previous firmware
all 69 apps of them......
-----------------------------------
Uptill now the using experience of Dr ketan m6 is quite good
But still facing a bit laggy while wake up from sleep state
And wired thing is lock screen uses two step
First scroll page to enter password page (eg, draw pattern)
At this point it's gone laggy, for maybe 1~3 time to try to unlock the phone again
Just now I faced this problem again, I think it might be the cache problem
So I try to go in to recovery using power button long press > restart > recovery
But strange thing happen
I can't boot in to recovery
It shows "sbl1 partition doesn't exist"
I haven't try download mode yet
But do I have to Odin again for the custom recovery (cwm) to be use in the future?
You haven't mentioned trying wipes or factory reset. That may be the cause of not booting system when you downgraded.
Unable to mount system in recovery is concerning though. Could possibly be eMMC corruption or hardware failure? But did you make sure the reactivation lock was off? The fact that you were able to flash in Odin successfully suggests it was off to start with but did you enable it afterwards? Read your phone's display while in download mode for reactivation lock status. If unlocked, the focus should be on flashing the right tar- like the one that matches your data.
Did the downgrade with Odin attempt to flash an older tar not compatible with bootloader? (You can't flash full tars like Android 5.0 or KitKat in Odin).
It may be wise to Odin flash the last stock tar that actually booted and matches your data if you haven't wiped it. Or flash the tar you want- as long as it's allowed- and factory reset in stock recovery and Odin the tar again.
But, if you did enable reactivation lock, you should Odin the full tar that matches your point of lock. You would also need to allow it to auto boot and sign in with same Google user and password.
If still having issues or tried all of that already, I haven't mentioned that you should wipe internal memory with TWRP or CWM. If you've had CM on the phone, you should wipe internal memory before stock tar flash. One thing I prefer to do with stock tars is flash them cleanly: backup first, then wipe everything but extSdCard, power down, pull battery. Wait at least 30 seconds, discharge the power circuit by gently pressing and holding power button with battery removed. Install battery and boot to download mode to flash stock tar with latest Odin and Odin defaults.
Sent from my SM-N910P using Tapatalk
samep said:
You haven't mentioned trying wipes or factory reset. That may be the cause of not booting system when you downgraded.
Unable to mount system in recovery is concerning though. Could possibly be eMMC corruption or hardware failure? But did you make sure the reactivation lock was off? The fact that you were able to flash in Odin successfully suggests it was off to start with but did you enable it afterwards? Read your phone's display while in download mode for reactivation lock status. If unlocked, the focus should be on flashing the right tar- like the one that matches your data.
Did the downgrade with Odin attempt to flash an older tar not compatible with bootloader? (You can't flash full tars like Android 5.0 or KitKat in Odin).
It may be wise to Odin flash the last stock tar that actually booted and matches your data if you haven't wiped it. Or flash the tar you want- as long as it's allowed- and factory reset in stock recovery and Odin the tar again.
But, if you did enable reactivation lock, you should Odin the full tar that matches your point of lock. You would also need to allow it to auto boot and sign in with same Google user and password.
If still having issues or tried all of that already, I haven't mentioned that you should wipe internal memory with TWRP or CWM. If you've had CM on the phone, you should wipe internal memory before stock tar flash. One thing I prefer to do with stock tars is flash them cleanly: backup first, then wipe everything but extSdCard, power down, pull battery. Wait at least 30 seconds, discharge the power circuit by gently pressing and holding power button with battery removed. Install battery and boot to download mode to flash stock tar with latest Odin and Odin defaults.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
about the factory wipe, i only did the part that i mentioned, those which i didn't mention, no, this is my carelessness
about reactivation lock, i don't really know what is it, is it debugging mode in the developer menu?
the 1st downgrade from 6.0.1 to 5.1.1 both are stock, and is a success, the 2nd downgrade are under the same situation, but failed, when upgrade to 6.0.1, the 1st i use OTA, 2nd i use smart switch, for downgrading in use odin on both, 1st success, 2nd failed, i'm using stock downloaded from sammobile
NooBDroidPlayer said:
about the factory wipe, i only did the part that i mentioned, those which i didn't mention, no, this is my carelessness
about reactivation lock, i don't really know what is it, is it debugging mode in the developer menu?
the 1st downgrade from 6.0.1 to 5.1.1 both are stock, and is a success, the 2nd downgrade are under the same situation, but failed, when upgrade to 6.0.1, the 1st i use OTA, 2nd i use smart switch, for downgrading in use odin on both, 1st success, 2nd failed, i'm using stock downloaded from sammobile
Click to expand...
Click to collapse
The reactivation lock is enabled by two different methods. Manually at Settings/Security; you also get prompted to set it on the last step of setup wizard after flashing a stock tar.
However, you can verify that reactivation lock is off when in download mode. Read your phone's screen. It should say that it is off.
The Note 4 has an infamous tendency to corrupt or just wear out the eMMC due to excessive wipes, format of data and flashes. I would advise limited use of Odin, Smart Switch and OTA updates to minimum to get you where you want to be. Even the multiple use wipes in recovery should be limited. They're all suspect IMO.
Maybe the extra updates you've attempted were due to things not going as expected or you've experienced the failure or corruption of eMMC. I'd suggest you resolve the reactivation lock (If shown to be locked) try the suggested wipe and flash method at end of my first post on the tar you intend to flash to get the ROM of your choice and limit updates as much as possible.
If you get there cleanly with no failure to boot or reboots unexpected reboots thereafter, maybe it was just something that needed clearing out of internal memory. With that in mind, if you get to the point of flashing a custom ROM, read the OP our thread carefully; consider wiping internal memory in custom recovery before flashing ROM, if suggested.
Maybe just format data once per ROM flash. There's also an option in TWRP settings to wipe rather than format.
Sent from my SM-N910P using Tapatalk
Flash Bootloader PG1 and then MIUI 6.6.3 for N910F/G. It should then work
samep said:
The reactivation lock is enabled by two different methods. Manually at Settings/Security; you also get prompted to set it on the last step of setup wizard after flashing a stock tar.
However, you can verify that reactivation lock is off when in download mode. Read your phone's screen. It should say that it is off.
The Note 4 has an infamous tendency to corrupt or just wear out the eMMC due to excessive wipes, format of data and flashes. I would advise limited use of Odin, Smart Switch and OTA updates to minimum to get you where you want to be. Even the multiple use wipes in recovery should be limited. They're all suspect IMO.
Maybe the extra updates you've attempted were due to things not going as expected or you've experienced the failure or corruption of eMMC. I'd suggest you resolve the reactivation lock (If shown to be locked) try the suggested wipe and flash method at end of my first post on the tar you intend to flash to get the ROM of your choice and limit updates as much as possible.
If you get there cleanly with no failure to boot or reboots unexpected reboots thereafter, maybe it was just something that needed clearing out of internal memory. With that in mind, if you get to the point of flashing a custom ROM, read the OP our thread carefully; consider wiping internal memory in custom recovery before flashing ROM, if suggested.
Maybe just format data once per ROM flash. There's also an option in TWRP settings to wipe rather than format.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
i'll be more caution in the future, thank for the great help !!!
I've noticed in my Sprint forum that some users downgrading from Marshmallow to Lollipop with Odin full tar reportedly had to factory reset after Odin of stock Lollipop tar.
They said phone failed to boot until the factory reset.
There's two particulars that apply to quick downgrade in our forum. If you have an old lollipop TWRP backup of desired ROM and an XDA thread that contains bootloader tars to flash in Odin, you can easily just TWRP backup your current Marshmallow ROM, factory reset and wipe internal memory and restore the TWRP backup of Lollipop and Odin the equivalent bootloader. But without the right bootloader, Wi-Fi won't connect and camera won't focus correctly.
You could easily upgrade and downgrade with TWRP backups and bootloader tars that way minimizing excessive wear on eMMC. Just remember to backup current ROM, factory reset, wipe internal memory, restore backup and flash the equivalent bootloader. Keep your backups current and relevant and always backup to ext sdcard- same for titanium backup backups.
Still I prefer to minimize upgrade and downgrade and wipes to possibly extend the life of the eMMC to maximum. I just minimize wipe and flash so much to avoid component wear. Just a theory though. Also try to minimize heat by avoiding fast charging and ventilating phone when optimizing apps on initial boot of new custom ROM or after flashing Xposed or any wipe of dalvik-cache.
Sent from my SM-N910P using Tapatalk