Database Develop

Tab bricked, CWM Recovery - Read-only file system issue

Hello all,
I have an issue with latest CWM 5.5.0.4 recovery. It says the following error:
E:Error in /cache/recovery/last_log
(Read-only file system)
and other similar errors:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
and I'm unable to reflash GalaxianSoup ROM nor restore the original backed up 3.2 factory rom.
What actually happened ?
Once bought, I managed to root, flash CWM 5.5.0.4 recovery and install the latest GalaxianSoup ROM. Everything based on the guides in development forum and successful (all latest versions). All cool! System was working fine.
Yesterday, I was using tablet, installed few apps, nothing special and later left tablet turned on and charging. When I came back, it was turned off. Okay, tried to turned on, but the system never booted and always looped (seeing only Google logo and moving gears). I rebooted into recovery and noticed the error (see above).
Now, I'm basically unable to do anything. I tried to wipe data, cache and Dalvik cache several times, and reflash GalaxianSoup again (Galaxian + Gapps) or also restore the 3.2 system backup that I've made (always fails).
I've read on some other forums that it might have something to do with damaged SD card partition or something.
I'm out of ideas. Can anyone help me pleeeeease?
EDIT: I've got european Samsung Galaxy Tab 8.9 16GB WIFI version.
EDIT: I must correct myself. After rolling back to factory rom, I was experiencing the same issues, seems there some hardware issue. I sent the tablet back for repair, seems now it had nothing to do with GalaxianSoup. No need to worry, keep up the good work.

whiplash84 said:
Hello all,
I have an issue with latest CWM 5.5.0.4 recovery. It says the following error:
E:Error in /cache/recovery/last_log
(Read-only file system)
and other similar errors:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
and I'm unable to reflash GalaxianSoup ROM nor restore the original backed up 3.2 factory rom.
What actually happened ?
Once bought, I managed to root, flash CWM 5.5.0.4 recovery and install the latest GalaxianSoup ROM. Everything based on the guides in development forum and successful (all latest versions). All cool! System was working fine.
Yesterday, I was using tablet, installed few apps, nothing special and later left tablet turned on and charging. When I came back, it was turned off. Okay, tried to turned on, but the system never booted and always looped (seeing only Google logo and moving gears). I rebooted into recovery and noticed the error (see above).
Now, I'm basically unable to do anything. I tried to wipe data, cache and Dalvik cache several times, and reflash GalaxianSoup again (Galaxian + Gapps) or also restore the 3.2 system backup that I've made (always fails).
I've read on some other forums that it might have something to do with damaged SD card partition or something.
I'm out of ideas. Can anyone help me pleeeeease?
EDIT: I've got european Samsung Galaxy Tab 8.9 16GB WIFI version.
Click to expand...
Click to collapse
Flash your recovery again through odin..
Then reflash your galaxian soup..
If not success, use odin and flash stock rom..
Dont forget backup your file from sdcard just in case if you need reset factory..

suwandiapr said:
Flash your recovery again through odin..
Then reflash your galaxian soup..
If not success, use odin and flash stock rom..
Dont forget backup your file from sdcard just in case if you need reset factory..
Click to expand...
Click to collapse
Flashing of CWM didn't help to fix the issue, installing of GalaxianSoup didnt work at all (corrupted ZIP file error...)
Thanks God, reflashing of stock ROM via Odin did work, tablet is up and running. GalaxianSoup is definitely not stable enough yet, I'll stick to the stock rom fora while. Thank you!

whiplash84 said:
Flashing of CWM didn't help to fix the issue, installing of GalaxianSoup didnt work at all (corrupted ZIP file error...)
Thanks God, reflashing of stock ROM via Odin did work, tablet is up and running. GalaxianSoup is definitely not stable enough yet, I'll stick to the stock rom fora while. Thank you!
Click to expand...
Click to collapse
Galaxian Soup is more then stable enough. Bad flashes happen and you just said you had it up and running.

bdfull3r said:
Galaxian Soup is more then stable enough. Bad flashes happen and you just said you had it up and running.
Click to expand...
Click to collapse
To be honest, it is kind of stable, but not enough, hence the beta label. Some further optimizing will be done once the team has ICS source. In my experience, it was stable, but sometimes it would turn off when in fell into Deep Sleep state. Now, the AOKP milestone 5 is giving me issues with the screen rotation. I've experienced both sides, AOSP and AOKP in their latest versions. Obviously there is more room for improvement, but I'm afraid the team is kinda stuck without source. They've done miracles without source though.

[Q] Caught in Bootscreen loop - i9305 LTE have access to CWM! [SOLVED]

My i9305 LTE is caught in a boot loop (just loops the start-up screen of any ROM I install). I have access to CWM recovery v6.0.4.5 and also download recovery.
The only thing I can think that might have caused this was when I installed Archidroid I (foolishly?) selected the only partition that wasn't ext4, to be set as ext4. It's not booted past any of the bootscreens on any ROM since I did this.
I've tried wiping all data and cache and also doing a data/factory reset and every "clear data" option available and I'm still caught in a boot screen loop on any ROM I try.
I've formatted each of the folders on the device by mounting and formatting (I don't need to keep any data on the phone) and then to get a new ROM on the phone I've inserted an SD Card, mounted it in CWM recovery and installed it from the .zip that way, all ROMs I've tried just lock up at their boot screen, it just loops over and over.
I've searched this forum and on Google but cannot find a solution or anyone with a similar issue, most that have had a similar looping problem say they performed an Odin factory reset, which brings me to my next question.
I don't know the region of my phone as I cannot access the dialler or any of my settings to find out the region, and forgot (as I rooted so long ago). I do have on the back of the phone the codes:
FCC ID: A3LGI9305
SSN: -I9305GSMH
as well as my IMEI #
How do I know my phone region, and which firmware/rom would I use to perform a full factory reset to at least get it booting again?
Any tips/ideas please, that would be much appreciated.

likeasir said:
My i9305 LTE is caught in a boot loop (just loops the start-up screen of any ROM I install). I have access to CWM recovery v6.0.4.5 and also download recovery.
The only thing I can think that might have caused this was when I installed Archidroid I (foolishly?) selected the only partition that wasn't ext4, to be set as ext4. It's not booted past any of the bootscreens on any ROM since I did this.
I've tried wiping all data and cache and also doing a data/factory reset and every "clear data" option available and I'm still caught in a boot screen loop on any ROM I try.
I've formatted each of the folders on the device by mounting and formatting (I don't need to keep any data on the phone) and then to get a new ROM on the phone I've inserted an SD Card, mounted it in CWM recovery and installed it from the .zip that way, all ROMs I've tried just lock up at their boot screen, it just loops over and over.
I've searched this forum and on Google but cannot find a solution or anyone with a similar issue, most that have had a similar looping problem say they performed an Odin factory reset, which brings me to my next question.
I don't know the region of my phone as I cannot access the dialler or any of my settings to find out the region, and forgot (as I rooted so long ago). I do have on the back of the phone the codes:
FCC ID: A3LGI9305
SSN: -I9305GSMH
as well as my IMEI #
How do I know my phone region, and which firmware/rom would I use to perform a full factory reset to at least get it booting again?
Any tips/ideas please, that would be much appreciated.
Click to expand...
Click to collapse
what country do you live? the region is the country you live in, just search for your official firmware on sammobile or samsung update site. and download the firmware for your country, flash it with odin.
also update your recovery to the latest available in your case cwm 6.0.4.7

PHP:
MaHo_66 said:
what country do you live? the region is the country you live in, just search for your official firmware on sammobile or samsung update site. and download the firmware for your country, flash it with odin.
also update your recovery to the latest available in your case cwm 6.0.4.7
Click to expand...
Click to collapse
I live in Australia but am slightly worried as I bought my phone from Koga online so it's an internationally shipped phone I think originally intended for the uk as it had a uk adaptor for the plug does this matter?

likeasir said:
PHP:
I live in Australia but am slightly worried as I bought my phone from Koga online so it's an internationally shipped phone I think originally intended for the uk as it had a uk adaptor for the plug does this matter?
Click to expand...
Click to collapse
Hmm... Good question. I understand your issue here but im afraid i cant answer this.. While it was working what firmware was running on it? What baseband? If you have any kind of info of the working firmware, analyze it with firmwares on those sites and try to find the one you need.
Sent from my GT-I9305 using XDA Premium 4 mobile app

likeasir said:
My i9305 LTE is caught in a boot loop (just loops the start-up screen of any ROM I install). I have access to CWM recovery v6.0.4.5 and also download recovery.
The only thing I can think that might have caused this was when I installed Archidroid I (foolishly?) selected the only partition that wasn't ext4, to be set as ext4. It's not booted past any of the bootscreens on any ROM since I did this.
I've tried wiping all data and cache and also doing a data/factory reset and every "clear data" option available and I'm still caught in a boot screen loop on any ROM I try.
I've formatted each of the folders on the device by mounting and formatting (I don't need to keep any data on the phone) and then to get a new ROM on the phone I've inserted an SD Card, mounted it in CWM recovery and installed it from the .zip that way, all ROMs I've tried just lock up at their boot screen, it just loops over and over.
I've searched this forum and on Google but cannot find a solution or anyone with a similar issue, most that have had a similar looping problem say they performed an Odin factory reset, which brings me to my next question.
I don't know the region of my phone as I cannot access the dialler or any of my settings to find out the region, and forgot (as I rooted so long ago). I do have on the back of the phone the codes:
FCC ID: A3LGI9305
SSN: -I9305GSMH
as well as my IMEI #
How do I know my phone region, and which firmware/rom would I use to perform a full factory reset to at least get it booting again?
Any tips/ideas please, that would be much appreciated.
Click to expand...
Click to collapse
Well I was in the same pickle
whicever 4.3 rom i flashed through odin i got stuck in boot logo or even if i recovered device from odin through emergency frimware and intillation
Also tried customs 4.3 roms stuck a boot logo
Here what u should try and what i did
1 flash philz recovery + 4.1.2 rom
if it works back up efs
2 Using Philz recovery wipe data factory reset + wipe cache + dalvik cache
3 in mount and storage section format everything ( THINK THIS IS THE MOST IMPORTANT STEP )
4 Used odin to flash a 4.3 stock package it worked ( note u may get knox from this u may try a modifed stock package if u dont have knox and dont want to get it )

AMoizK said:
Well I was in the same pickle
whicever 4.3 rom i flashed through odin i got stuck in boot logo or even if i recovered device from odin through emergency frimware and intillation
Also tried customs 4.3 roms stuck a boot logo
Here what u should try and what i did
1 flash philz recovery + 4.1.2 rom
if it works back up efs
2 Using Philz recovery wipe data factory reset + wipe cache + dalvik cache
3 in mount and storage section format everything ( THINK THIS IS THE MOST IMPORTANT STEP )
4 Used odin to flash a 4.3 stock package it worked ( note u may get knox from this u may try a modifed stock package if u dont have knox and dont want to get it )
Click to expand...
Click to collapse
Thanks for your suggestion, I'll give that a shot tonight. I'm able to get into CWM as explained, mount and format everything so I'm not sure that this step will make a difference, but I'll do it again anyway.
So I'll see how it goes tonight. Actually been quite refreshing without a phone these past couple of days

likeasir said:
Thanks for your suggestion, I'll give that a shot tonight. I'm able to get into CWM as explained, mount and format everything so I'm not sure that this step will make a difference, but I'll do it again anyway.
So I'll see how it goes tonight. Actually been quite refreshing without a phone these past couple of days
Click to expand...
Click to collapse
I managed to fix it, but it had me totally stumped for a while.
I flashed philz recovery and then formatted all of the directories as I'd done previously on CWM.
I tried Slim Rom which didn't work.
I ended up tying CyanogenMod stable which actually worked, it got past the boot loop phase! - I was glad to see a setup screen after 2 days!
I then had another issue with my Cell Reception not working, no data or reception would be shown.
This seemed to happen since I tried a KitKat ROM, as I remember before the bootloop it did this on a couple of ROMs I tried to manually enter the APN over and over and it wouldn't let me save it, very annoying.
I checked the baseband in the about phone section and it was being displayed as "unknown", luckily I remembered my baseband # from when I rooted the phone about 8 months ago (XXBLL3), then I found on this forum a list of 9305i baseband downloads as .zips so I was able to load up CWM and flash it, reboot and it worked!
I will be keeping with CM Stable (10.1.3) for a while now.
I hope this helps someone else that might run into a similar issue.

likeasir said:
I managed to fix it, but it had me totally stumped for a while.
I flashed philz recovery and then formatted all of the directories as I'd done previously on CWM.
I tried Slim Rom which didn't work.
I ended up tying CyanogenMod stable which actually worked, it got past the boot loop phase! - I was glad to see a setup screen after 2 days!
I then had another issue with my Cell Reception not working, no data or reception would be shown.
This seemed to happen since I tried a KitKat ROM, as I remember before the bootloop it did this on a couple of ROMs I tried to manually enter the APN over and over and it wouldn't let me save it, very annoying.
I checked the baseband in the about phone section and it was being displayed as "unknown", luckily I remembered my baseband # from when I rooted the phone about 8 months ago (XXBLL3), then I found on this forum a list of 9305i baseband downloads as .zips so I was able to load up CWM and flash it, reboot and it worked!
I will be keeping with CM Stable (10.1.3) for a while now.
I hope this helps someone else that might run into a similar issue.
Click to expand...
Click to collapse
Cheers on getting ur phone fixed but after wiping all directories a stock rom flash would have cleared all the problems

lol i just did this to my phone, time to find a stock firmware.

Bricked or Hardware defect?

Hello,
first post, trust I did not miss aynthing.
Bought a cheap used SM-T810N as "damaged" believing it is a software problem and I can fix it.
Flashed everything I found (Lollipo, Marshmallow, CM, TWRP recovery, etc.)
Tablet stucks at Samsung Logo and shows some strange color effects (lines, artefacts) but screen works fine in Recovery, TWRP, etc.
Anyone any idea how to identify the real problem?
Thanks a lot, you all are doing a great job here.
DaWool

wool242 said:
Hello,
first post, trust I did not miss aynthing.
Bought a cheap used SM-T810N as "damaged" believing it is a software problem and I can fix it.
Flashed everything I found (Lollipo, Marshmallow, CM, TWRP recovery, etc.)
Tablet stucks at Samsung Logo and shows some strange color effects (lines, artefacts) but screen works fine in Recovery, TWRP, etc.
Anyone any idea how to identify the real problem?
Thanks a lot, you all are doing a great job here.
DaWool
Click to expand...
Click to collapse
Have you tried a full wipe before using Odin to flash a ROM? Including the data partition? Or tried booting to "download" instead of TWRP to use Odin?
edit: And you do need to use Odin to get things working before trying to flash anything via TWRP.

Seems like a mismatched bootloader and kernel issue to me.
Flashing stock firmware with ODIN should fix it if it is.

lewmur said:
Have you tried a full wipe before using Odin to flash a ROM? Including the data partition? Or tried booting to "download" instead of TWRP to use Odin?
edit: And you do need to use Odin to get things working before trying to flash anything via TWRP.
Click to expand...
Click to collapse
Tried both, Odin and flashing from recovery... Even different Odin versions

No imei or baseband after failed root attempt--Please help!!

After a failed root attempt on my SM-N920L I have lost network capabilities; there is no baseband and imei.
The phone was working perfectly until the root attempt-- which was made by flashing a file named "Noble-Kernel-N920L_Alpha1.tar" which caused a "Kernel is not Seandroid Enforcing" error and temporarily bricked the phone.
After some googling I was able to fix the bricked phone, but the network problem started to occur at this point.
I've since been able to successfully root the phone using the method on this site and everything else with the phone is working perfectly. (From my experience with this particular model, SM-N920L, flashing "CF-Auto-Root-nobleltelgt-nobleltelgt-smn920l.tar.md5" is the only method that successfully rooted the phone.)
I have tried everything I could google to fix the problem:
-using a different sim card (and this sim card works fine on other phones)
- using the keypad method to punch in *#197328640# or other variants
-factory resetting
-downloading and installing stock rom using odin and also
-resetting by installing ap along with bl, cp, csc, even pti
-using twrp to wipe out (hopefully reset) everything
Obviously the imei is on the back of the phone, so there must be some way to salvage it somehow and enter it into the phone again but I am out of ideas. Any suggestions would be appreciated!
One side note:
Using twrp, I did try attempting to install two custom roms (AryaMod and Hyperdrive) to see if that would solve the problem. Everything installs fine, but once I get into the rebooting stage the screen turns off and does not turn on again-- nothing happens even though I wait for over 30 minutes. I just end up having to install the stock rom again. So I can't tell if installing a custom rom would solve the issue (someone on another forum was mentioning this worked for them). Any input on why the custom roms install fine, but then does not open during reboot, would also be appreciated!

update: I have successfully installed a custom rom-- installing seems to have worked after flashing this kernel: NEMESIS_KERNEL_N5_V2.0.zip instead of using the stock kernel.
But sort of as expected, installing the custom rom did not solve the issue.
"dr.ketan" mentioned in one of his threads about entering a bunch of codes using root explorer and Terminal emulator, but these methods also did not work.

sskkambad said:
update: I have successfully installed a custom rom-- installing seems to have worked after flashing this kernel: NEMESIS_KERNEL_N5_V2.0.zip instead of using the stock kernel.
But sort of as expected, installing the custom rom did not solve the issue.
"dr.ketan" mentioned in one of his threads about entering a bunch of codes using root explorer and Terminal emulator, but these methods also did not work.
Click to expand...
Click to collapse
Did your problem solved? I have the same problem with an endless rebooting. Sigh~

Problems with OctOS/TWRP... or maybe I'm the problem ;)

Update for the readers wh don't want to read the rest of the thread:
I solved 2 issues ("com.android.phone has stopped" was gone after wiping system, and the updating now works smoothly after i realized that the latest firmware is 4.0.3 and not 4.0.2)
The remaining problem is:
But i still get the welcome screen (like i wiped the data) everytime i reboot from twrp
It is not a ROM issue, because during the process i switched from OctOS to lineage and i still get the problem... what can that be???
quick info: TWRP is the most recent (3.0.3-1), firmware is the newest (4.0.3), Lineage is the nightly from Feb 14.
Original post:
Hello there fellow Oneplus users,
I've got some trouble with my 3T. I changed the OS to OctN some weeks ago. Everything was fine, i din't update the first 2 weeklys and when i wanted to update a few days ago (to OCT-N-WEEKLY-20170210-2251-oneplus3.zip) i tried but there was error 7... i don't remember exactly what i did then but when i booted i got the message "com.android.phone has stopped" and i couldn't get the message away (it appeared directly again after clicking ok) in the background the phone wanted to make a fresh setup. i tried a few things out, and the only thing that worked was wiping the cache, dalvik and data and then installing the rom, that was installed before (OCT-N-WEEKLY-20170121-0348-oneplus3.zip)
the next day i thought i could try it again (i hoped it was just coincidence), but make a backup via twrp before. but then same error... So i wanted to restore the backup. It went without errors in twrp, but the booting afterwards took about 15 minutes! After the boot: again the error message and in the background the "set up new phone" screen... even though i did a restore... so again wipe cache/dalvik/data via twrp and re install the old version of the OctOS
Next day after research: maybe i needed to update the firmware (4.0.2). downloaded it but i thought i would wait a little, because i don't have that much time to deal with those problem right now.
So today i decided to give it a try, rebooted to twrp, but then i thougt: "nah, i'll do it another day". So i really did NOTHING in TWRP -> reboot to system -> same old Error (com.android.phone has stopped) and data lost (new phone setup)
Ok: reboot to twrp, flashed the new firmware (no error) tried to flash the new OctOS -> error 7...
I also have the latest LineageOS rom (lineage-14.1-20170214-nightly-oneplus3-signed.zip) on the phone to try out: wiped Cache/Dalvik/Data install Lineage: same error 7...
same with the old OctOS: everything's fine...
Longstory short: what ever i do in twrp doesn't work expect a wiping and reinstalling the same OctOS that worked the last 3 or 4 weeks...
What am i missing? Or is there really something wrong with my phone?

Try to flash the new TWRP, firmware.

and flash the rom with full wipe

svandasek said:
Try to flash the new TWRP, firmware.
Click to expand...
Click to collapse
TWRP is the newest, and (as already mentioned in the text) firmware was renewed during the process without any success.
What do you mean by full wipe? More than Cache, Dalvik and Data?
But still, i have the feeling, that this error is something not very common... I think i might return to complete stock, if the problems continue.

So,
i solved 2 issues ("com.android.phone has stopped" was gone after wiping system, and the updating now works smoothly after i realized that the latest firmware is 4.0.3 and not 4.0.2)
But is Still get the Welcome Screen (like i wiped the data) everytime i reboot from twrp
It is not a ROM issue, because during the provess i switched from OctOS to lineage and i still get the problem... what can that be???

Nobody got any idea?

felixburk said:
Nobody got any idea?
Click to expand...
Click to collapse
It's a TWRP and f2fs problem. You either need to change your data partition to EXT4 and/or update your TWRP to 3.0.4-1
https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391

GrandMasterB said:
It's a TWRP and f2fs problem. You either need to change your data partition to EXT4 and/or update your TWRP to 3.0.4-1
https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391
Click to expand...
Click to collapse
Thanks I'll try that out.
Might it help, if i don't set a password for the phone? Or is it not encryption related?

felixburk said:
Thanks I'll try that out.
Might it help, if i don't set a password for the phone? Or is it not encryption related?
Click to expand...
Click to collapse
It's filesystem driver related and nothing to do with the encryption.