I rooted my AT&T Note 3 several months ago using 'towelroot', installed busybox, safestrap, xposed framework and SuperUser. Everything has worked fine until today. I went to swap batteries and after doing so, my phone wouldn't complete boot. It goes past the Samsung splashscreen and when it gets to the AT&T screen it hangs. It hangs after abouth the 3rd time around on the little AT&T globe. I went into recovery and tried to restore and it says that it is complete but 'failed'. I tried the 'factory reset' from within recovery but that didn't seem to do any good either.
I was rooted but have not installed any custom ROMS. The only thing new recently was the "GravityBox" xposed module.
Should I try Odin and which files should I flash? AP, BL, CP, CSC, all of them? Should I repartition?
Gravity Box isn't compatible with Samsung devices. Just Odin all 4 files, repartition shouldn't be necessary.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
Can you get into safe strap recovery?
yokozuna82 said:
Can you get into safe strap recovery?
Click to expand...
Click to collapse
I get into safestrap but when I try factory reset for instance it gives the following:
Factory Reset Complete
Successful
Updating Partition details...
E:error opening '/data/date/com.android/providers.settings/databases'
E:error: I/O error
E:error opening '/data/data/com.wssnps'
E:error: I/O error
Full SELinux support is present.
Wiping data without wiping /data/media ...
Done.
Formatting Cache using make_extfrs function.
Updating partition details...
E:error opening '/data/data/com.android.providers.setting/databases'
E:error: I/O error
E:error opening '/data/data/com.wssnps'
E:error: I/O error
Try downloading an other ROM put it in your microsd card clear cache clear dalvik cache and factory reset then install that new rom under the stock slot...you can get into SS recovery so it can be fixed easily
---------- Post added at 06:45 AM ---------- Previous post was at 06:42 AM ----------
Make sure though that if you had a 4.4.2 rom previously that you don't download a ROM that is older then that keep it the same as previous
Perseids said:
I get into safestrap but when I try factory reset for instance it gives the following:
Factory Reset Complete
Successful
Updating Partition details...
E:error opening '/data/date/com.android/providers.settings/databases'
E:error: I/O error
E:error opening '/data/data/com.wssnps'
E:error: I/O error
Full SELinux support is present.
Wiping data without wiping /data/media ...
Done.
Formatting Cache using make_extfrs function.
Updating partition details...
E:error opening '/data/data/com.android.providers.setting/databases'
E:error: I/O error
E:error opening '/data/data/com.wssnps'
E:error: I/O error
Click to expand...
Click to collapse
Wipe/Factory reset in SafeStrap isn't a true factory reset...you have to flash a ROM after that or you won't have anything to boot to.
yokozuna82 said:
Try downloading an other ROM put it in your microsd card clear cache clear dalvik cache and factory reset then install that new rom under the stock slot...you can get into SS recovery so it can be fixed easily
---------- Post added at 06:45 AM ---------- Previous post was at 06:42 AM ----------
Make sure though that if you had a 4.4.2 rom previously that you don't download a ROM that is older then that keep it the same as previous
Click to expand...
Click to collapse
Yea if you can still get into SS flash a rom or restore a backup if you made one. The Odin install might be easier you don't have to unroot or anything like that just boot to download mode
I ended up doing the Odin thing, all 4 files. I know I lost a lot of stuff, and probably should have waited till I got your all expert advice and instructions. I got paranoid nothaving my phone available and went the desperate route.
Thanks everyone for all your help, I will certainly keep it handy, although I hopper there is no next time!
Related
Since flashing Notecore V9 Extreme I have been getting the following message in recovery,
E:Error in /cache/recovery/last_log
(Read-only file system)
I have done some reading on this and have found various people with the same issue (on different firmwares) with different solutions given... I figured before I do anything rash I check in here first to see if anyone could offer their opinion or has maybe experienced the error before? One suggestion I read was to simply do a wipe cache partition but I'm reluctant to do anything until I get some confirmation from someone in the know.
For reference the process I used for flashing V9 Ex was to first flash Abyss kernel (as far as I can remember!), followed by the jBroid script and then flash v9 over the top. The phone is running fine with no problems, I just can't seem to flash any themes etc via recovery.
My understanding is that its to do with 'safe' kernel disabled processes. Due to custom improvments and brick bug...But I could be wrong.
I got this when switching from speedmod to notecore and vice versa. Format /cache in recovery and the error will be gone.
diverblue said:
Since flashing Notecore V9 Extreme I have been getting the following message in recovery,
E:Error in /cache/recovery/last_log
(Read-only file system)
I have done some reading on this and have found various people with the same issue (on different firmwares) with different solutions given... I figured before I do anything rash I check in here first to see if anyone could offer their opinion or has maybe experienced the error before? One suggestion I read was to simply do a wipe cache partition but I'm reluctant to do anything until I get some confirmation from someone in the know.
For reference the process I used for flashing V9 Ex was to first flash Abyss kernel (as far as I can remember!), followed by the jBroid script and then flash v9 over the top. The phone is running fine with no problems, I just can't seem to flash any themes etc via recovery.
Click to expand...
Click to collapse
This message shows when you use JBRoid cleaner as it cleans out the old kernel modules and files. After that previous log was not found by CWM Recovery. Its nothing to do with your flashing. I get this message always. Ignore it and Keep Flashing
sahilarora2003 said:
This message shows when you use JBRoid cleaner as it cleans out the old kernel modules and files. After that previous log was not found by CWM Recovery. Its nothing to do with your flashing. I get this message always. Ignore it and Keep Flashing
Click to expand...
Click to collapse
Even I have the same problem when I used Jbroid. But now I understand that Jbroid cleans up the previous Kernel footprints resulting in the error.
I have that problem without jBroid too... so it's only related to the cache cleaning process. Wipe cache partition doesn't entirely clean it; format cache does.
So I have been trying to flash another ROM into my bionic which is on .246. I go into safestrap and activate another rom slot, I wipe the system, davlik, cache, then got into install and I choose a rom (I have tried eclipse, and Icarus) it then says install failure, and zip could not be opened. What I am I failing to do correctly? I have tried Safestrap 3.4 and I still get the same error. I have tried placing the zip on internal and external memory.
What is the error it is giving you?
Travisdroidx2 said:
What is the error it is giving you?
Click to expand...
Click to collapse
It just says, it cannot open the zip file, nothing else.
smgrajeda said:
It just says, it cannot open the zip file, nothing else.
Click to expand...
Click to collapse
i'm having the same problem. it says the following:
-- Install /sdcard/Download/Bionic-Eclipse ICS-v1.2.1 (
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/Download/Bionic-Eclipse ICS-v1.2.1 (
(Status 4)
Error flashing zup '/sdcard/Download/Bionic-Eclipse ICS
I receive the same error message for every zip rom I have tried
I see myself possibly having same problem. When i download zip do i put it on int or external sd? When im creating slot do i use int or ext memory. Noob if u cant tell.
Sent from my DROID BIONIC using xda app-developers app
---------- Post added at 10:09 AM ---------- Previous post was at 10:04 AM ----------
Oh yeah.....i have 6.2 gigs free on int mem. And 1.92 free on ext.
Sent from my DROID BIONIC using xda app-developers app
smgrajeda said:
So I have been trying to flash another ROM into my bionic which is on .246. I go into safestrap and activate another rom slot, I wipe the system, davlik, cache, then got into install and I choose a rom (I have tried eclipse, and Icarus) it then says install failure, and zip could not be opened. What I am I failing to do correctly? I have tried Safestrap 3.4 and I still get the same error. I have tried placing the zip on internal and external memory.
Click to expand...
Click to collapse
I know I'm resurrecting an old thread, but I had this problem yesterday and never did find a solution. Here's what worked for me: I removed safestrap 3.5 and went to 3.11. ROM install worked perfectly the first time on 3.11.
GTOMEX09 said:
I know I'm resurrecting an old thread, but I had this problem yesterday and never did find a solution. Here's what worked for me: I removed safestrap 3.5 and went to 3.11. ROM install worked perfectly the first time on 3.11.
Click to expand...
Click to collapse
Can confirm.. just installed cm10.1 via safestrap 3.11 a day or two ago.
I download this roms
-Resurrection Remix V.5.4.4
And also download this.
V.5.7 Remix -Resurrection
Download the gapps and did the normal procedure for installation.
what happens is that after attempting to install the ROM. I get this error.
(Enclose all text that I no longer like spending a capture)
Installing: Storage - sd card1-Resurrecction Remix_Lp_v.5.4.4
finding update package
opening update
installing Update
Detected Fylesystem ext4 for /Dev/block/plataform/msm_sdcc.l/by-name/system
mount: Failed to mount /dev/block/plataform/msm_sdcc.l/by-name/system at / system: Invalid argument
unmouunt of / system failed: no such volume
patching system unconditionally
E: error in /storage/sdcard1/REsurrectionRemix_Lp_v5.4.4-20150511
(Status 0)
instalation aborted
This is me 2 rom mentioned.
after that the micro sd is disabled and must be reintroduced to recognize it the team
Try installing the ROM CM By beto, and is not installed not simply do nothing and pass the phone around two hours in the instalalcion and never proceeded
Now my phone does not pass the logo of motorola
help-'
Did you perform a „factory reset” wipe? Changing ROMs kind of requires you to - a factory reset wipes the old sd-ext, and you still have it.
And are you sure you downloaded the right ROM? I can't access the RR site now, but they don't have ROMs for Thea.
What phone do you have, actually?
FCorvin said:
Did you perform a „factory reset” wipe? Changing ROMs kind of requires you to - a factory reset wipes the old sd-ext, and you still have it.
And are you sure you downloaded the right ROM? I can't access the RR site now, but they don't have ROMs for Thea.
What phone do you have, actually?
Click to expand...
Click to collapse
I have xt1045 4g
I've done all the procedures to install the rom .
but gave those mistakes.
try putting on a rom 5.1 stock xt1045 according to what I found here on xda but I do not install it .
the phone did not stay at the logo and not as most do.
Then you need to flash this ROM: CM Peregrine
Or this one: RR Peregrine
See the ROM's discussion thread here.
You are also on the wrong part of this forum - you'll get better advice here: Moto G
I am having issues with the installation of a Custom ROM on my Galaxy S Advance.
I have done it before, and it went smoothly. But later I reverted back to official one.
Now I am doing it again. But having a few problems with the CWM recovery (v6.0.2.8). I am having an old file which was probably uploaded by Shaaan.
The file name is "update.zip".
I tried downloading the new file from one of his new threads, but that download infected my laptop with a large number of viruses, malwares and adwares that were on the host site. So I am using the old file itself.
So the issue is, I used the "root.zip" file to root my phone and it was done successfully as the Root Checker app also verified the root.
Later, I booted using the CWM Recovery.
Did the Wipe Data/ Fatory Reset.
Did Wipe Cache Data.
Did Wipe Dalvic Cache.
Then I moved to Installation of ROM.
When I select the option, "CHOOSE ZIP FROM SDCARD", there comes an error saying...
"E: Can't Mount /sdcard/"
I browsed the internet and found a solution that said CHANGING THE FILE SYSTEM OF THE SDCARD. So I did that too. Tried with NTFS as well as FAT32, but nothing happened.
I even tried to install by placing the ROM files in Internal Memory since they are not even getting cleaned after Wipe Data operation. But that too resulted in negative.
This is happening every time. By now, I have installed the official firmware 4 times, so as to start the process afresh, but no luck.
The ROM files are also not corrupted, as I have used them earlier.
Here are the images of the issue I am encountering. (Please tell how to upload images, as all that I can see is an option to add URL and not an image, also an error like posting 10 posts)
EXPECTING A SOLUTION TO IT ASAP, as the Official Jellybean version has again started to lag too much.
I have a rooted SM-t817t and have been attempting to flash Lineage 14.1 to it through TWRP 3.1.0-1_ashyx.
I have tried to flash with the gts210ltexx and the gts210wifi and the results are the same, receive the Error 7 message.
After reading up on other threads I attempted to alter the script to either tell it that the ROM is for the gts210ltexx or just remove it entirely and still getting the error.
Also attempted to run it without authentication.
I have read that the t817x tablets can be flashed with the t810 ROMs but have had zero success with doing so at this time.
I am unsure how to proceed from this point.
TheBigby said:
I have a rooted SM-t817t and have been attempting to flash Lineage 14.1 to it through TWRP 3.1.0-1_ashyx.
I have tried to flash with the gts210ltexx and the gts210wifi and the results are the same, receive the Error 7 message.
After reading up on other threads I attempted to alter the script to either tell it that the ROM is for the gts210ltexx or just remove it entirely and still getting the error.
Also attempted to run it without authentication.
I have read that the t817x tablets can be flashed with the t810 ROMs but have had zero success with doing so at this time.
I am unsure how to proceed from this point.
Click to expand...
Click to collapse
Format (not wipe) DATA and if that doesn't work FORMAT the system partition.
If neither works then maybe you should use an updated twrp.
ashyx said:
Format (not wipe) DATA and if that doesn't work FORMAT the system partition.
If neither works then maybe you should use an updated twrp.
Click to expand...
Click to collapse
Thank you for the advice, I will update to the latest TWRP and then format the data and try that. Will report back with results.
After formatting the data and updating to the latest TWRP, 3.2.3-1, I come across the same error 7.
Have updated the script filed to make certain no trace of verification exists for the ROM and still receive the error.
Have now attempted at least five different ROMS all with the same results.
The following is a summarized look at the details it gives.
Installing zip file 'lineage.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
Warning: No file_contexts
detected filesystem ext4 for /dev/block/platform/15540000.dwmmc0/by-name/SYSTEM
Patching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR: 7
Error installing zip file '/lineage.zip'
Updating partition details...
Failed to mount '/hidden' (Invalid argument)
...done
Update: I have now wiped data but have not yet formatted it. I believe I will need to install Magisk for that.
However based on other recommendations I have come to find out about the encryption on the Samsung storage and that it might be causing the issue.
I have tried to circumvent this by formatting the data into ext2 then back to ext4 and restarting recovery, but so far this has not worked. The error 7 message persists regardless.
Will come back with further updates.
TheBigby said:
Update: I have now wiped data but have not yet formatted it. I believe I will need to install Magisk for that.
However based on other recommendations I have come to find out about the encryption on the Samsung storage and that it might be causing the issue.
I have tried to circumvent this by formatting the data into ext2 then back to ext4 and restarting recovery, but so far this has not worked. The error 7 message persists regardless.
Will come back with further updates.
Click to expand...
Click to collapse
You didnt read my previous post correctly.
You don't need Magisk to FORMAT DATA.
The FORMAT DATA button is right there under the wipe options.
However what you did would have formatted DATA anyway.
Now do the same for the system partition after formatting DATA.
Do not reboot just check DATA and SYSTEM can be mounted then try and install the zip again.
ashyx said:
You didnt read my previous post correctly.
You don't need Magisk to FORMAT DATA.
The FORMAT DATA button is right there under the wipe options.
However what you did would have formatted DATA anyway.
Now do the same for the system partition after formatting DATA.
Do not reboot just check DATA and SYSTEM can be mounted then try and install the zip again.
Click to expand...
Click to collapse
Formatted the data and the system. Verified they were both mounted. Then attempted to flash the ROM.
Error 7 message still appearing. As does the unable to mount hidden.
TheBigby said:
Formatted the data and the system. Verified they were both mounted. Then attempted to flash the ROM.
Error 7 message still appearing. As does the unable to mount hidden.
Click to expand...
Click to collapse
What device is the ROM intended for?
ashyx said:
What device is the ROM intended for?
Click to expand...
Click to collapse
Have tried multiple ROMs, all intended for either the t810 or the t815. They include Lineage, Resurrection Remix, Paranoid Android, AOSP, and a couple more besides.
TheBigby said:
Have tried multiple ROMs, all intended for either the t810 or the t815. They include Lineage, Resurrection Remix, Paranoid Android, AOSP, and a couple more besides.
Click to expand...
Click to collapse
It may be that the system partition sizes are different?
Unknown. I have tried reflashing the stock firmware and that still failed in Odin.
I have given up at this point and restored from a backup. Thanks for the help however.
Same issue with Lineage 15.1
TheBigby said:
I have a rooted SM-t817t and have been attempting to flash Lineage 14.1 to it through TWRP 3.1.0-1_ashyx.
I have tried to flash with the gts210ltexx and the gts210wifi and the results are the same, receive the Error 7 message.
After reading up on other threads I attempted to alter the script to either tell it that the ROM is for the gts210ltexx or just remove it entirely and still getting the error.
Also attempted to run it without authentication.
I have read that the t817x tablets can be flashed with the t810 ROMs but have had zero success with doing so at this time.
I am unsure how to proceed from this point.
Click to expand...
Click to collapse
Can you share root procedure for the sm-t817t my roommate has one for sale, I'll only buy it if I can root it though.