Hello, I use Rootbox 4.2 with Dorimanx 9.43 (october). After a reboot i had a crazy issue i never had before : first the rom didn't boot, i was stuck on kernel logo. Since wiping caches didn't help, first thing to do is to backup, so i did and it ended (successfully) but in only 30sec..!
So i plugged USB and checked the backup folder and saw there was barely any data there..! So i thought it's wiped.. I tried reinstalling the rom (which means stock kernel instead dorimanx) without wiping, still no boot but trying backup again, it's doing the backup fully!!
However since space was missing, it failed.. So i had to reinstall Dorimanx, mount USB, make space, reinstall rom, reboot recovery and do back up again (currently on process). I'm wondering if there's an issue with the internal memory, if so i shoud delete all and send back.I would NEVER send back an Android for warranty if my data wasn't wiped before, your life's inside of it!
--STILL EDITING/ADDING INFO//PRESS F5 AND SOMETHING NEW MAY APPEAR---
LOOKING AT THE BACKUP FOLDER, I SEE BOOT.IMG IS 0MB! What does it means..?!
goja said:
Hello, I use Rootbox 4.2 with Dorimanx 9.43 (october). After a reboot i had a crazy issue i never had before : first the rom didn't boot, i was stuck on kernel logo. Since wiping caches didn't help, first thing to do is to backup, so i did and it ended (successfully) but in only 30sec..!
So i plugged USB and checked the backup folder and saw there was barely any data there..! So i thought it's wiped.. I tried reinstalling the rom (which means stock kernel instead dorimanx) without wiping, still no boot but trying backup again, it's doing the backup fully!!
However since space was missing, it failed.. So i had to reinstall Dorimanx, mount USB, make space, reinstall rom, reboot recovery and do back up again (currently on process). I'm wondering if there's an issue with the internal memory, if so i shoud delete all and send back.I would NEVER send back an Android for warranty if my data wasn't wiped before, your life's inside of it!
--STILL EDITING/ADDING INFO//PRESS F5 AND SOMETHING NEW MAY APPEAR---
LOOKING AT THE BACKUP FOLDER, I SEE BOOT.IMG IS 0MB! What does it means..?!
Click to expand...
Click to collapse
Wipe EVERYTHING from your phone, delete all folders and stuff, then install an Oficial Rom and after that put your Rom again. Can be a Rom, kernel or flash error...
Related
Hi,
First time it happened. tried everything but still cant fix it.
after a month or two on MIUI, I wanted to move to AOKP JB.
As I always do when switching ROMs, I backed up everything (efs, pictures, apps with titanium, etc) and format the internal sd card within the os to get rid of all the junk.
Then went into CWM (siyah) and wiped data and cache.
And now for my mistake, I foramt the /system instead of / cache.
So now, when Im trying to install the ROM as a zip file threw CWM I got an error 7.
When trying to do it on ODIN, it stuck on 'factory fs', 'cache', or 'boot'.
After some time, I got the "Firmware upgrade encountered an issue" message.
Then got rid of it after somehow succeeding installing a different cwm (the stock one) but nothing worked there either, exept installing the Siyah kernel zip from there.
What can I do now to get my phone back alive?
THANKS :crying:
pedel said:
Hi,
First time it happened. tried everything but still cant fix it.
after a month or two on MIUI, I wanted to move to AOKP JB.
As I always do when switching ROMs, I backed up everything (efs, pictures, apps with titanium, etc) and format the internal sd card within the os to get rid of all the junk.
Then went into CWM (siyah) and wiped data and cache.
And now for my mistake, I foramt the /system instead of / cache.
So now, when Im trying to install the ROM as a zip file threw CWM I got an error 7.
When trying to do it on ODIN, it stuck on 'factory fs', 'cache', or 'boot'.
After some time, I got the "Firmware upgrade encountered an issue" message.
Then got rid of it after somehow succeeding installing a different cwm (the stock one) but nothing worked there either, exept installing the Siyah kernel zip from there.
What can I do now to get my phone back alive?
THANKS :crying:
Click to expand...
Click to collapse
I jumped from S1 to S3, but I'm sure it's applicable. You need to flash via odin stock rom that originally came with your phone. Then root then flash custom rom. Odd tho in past I've done the 5 formats, boot, cache, data, system, sdcard then while still in recovery flash rom. Good luck
Sent from my GT-I9300 using xda premium
jj92942000 said:
I jumped from S1 to S3, but I'm sure it's applicable. You need to flash via odin stock rom that originally came with your phone. Then root then flash custom rom. Odd tho in past I've done the 5 formats, boot, cache, data, system, sdcard then while still in recovery flash rom. Good luck
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
thanks
The problem is, I really cant remember what was the original ROM version. I bought it end of june 2011.
I cant even remember if it was a UK ROM, or an open europe one, or anything else.
****
Hi guys.
I got a problem.
Got tired of lags, so i decided to wipe (data + dalvik) and reinstall Omega 27.1.
Now i can't boot up the phone - it just starts up CWM (6.0.1.2) when i reboot. Have tried to pull battery and when i insert it recovery just comes up.
What have i missed?
I have tried to install again, with and without wipes but still the same.
Can't restore nandroid either. Getting error on restoring /data, and just comes back to CWM again.
I'm kinda stuck.. ideas?
EDIT:
Just did a nandroid restore, error on restoring /data as always, but i rebooted and got into Android. I had to type in my google account information again, and all apps crashes all the time.
So I rebooted to recovery, and installed 27.1 (did a full wipe again), and now i can't get past recovery again.
Wtf?
mrBira said:
Hi guys.
I got a problem.
Got tired of lags, so i decided to wipe (data + dalvik) and reinstall Omega 27.1.
Now i can't boot up the phone - it just starts up CWM (6.0.1.2) when i reboot. Have tried to pull battery and when i insert it recovery just comes up.
What have i missed?
I have tried to install again, with and without wipes but still the same.p
Can't restore nandroid either. Getting error on restoring /data, and just comes back to CWM again.
I'm kinda stuck.. ideas?
EDIT:
Just did a nandroid restore, error on restoring /data as always, but i rebooted and got into Android. I had to type in my google account information again, and all apps crashes all the time.
So I rebooted to recovery, and installed 27.1 (did a full wipe again), and now i can't get past recovery again.
Wtf?
Click to expand...
Click to collapse
If you can get into download mode, flash a stock rom samsung www.sammobile.com with ODIN, then get root permissions and cwm with ]cf-root 6.4
devid801 said:
If you can get into download mode, flash a stock rom samsung www.sammobile.com with ODIN, then get root permissions and cwm with ]cf-root 6.4
Click to expand...
Click to collapse
Yes, it seems to be the only thing to do..
But does anyone know what is causing this?
Can't be the boot.img, because restoring the boot (wipes+restores) doesn't work. And installing a new rom also adds a new boot.img.
I was using my phone and all had been working fine for ages. It was in my pocket for a while and when i took it out to use it I saw that it was on the boot animation of CM11. My phone was already on when I last used it so I had assumed it had crashed. I took the battery out and turned the phone on again but it got stuck on the CM boot animation. The last time I turned on my phone before that was when I flashed a supersu zip file to make my root work as I was having some problems. After flashing the supersu zip and told my CWM recovery to restart the system, it prompted me to "fix root" or something like that, and I clicked yes and it booted normally. That was the last time it booted normally before being stuck as it is now. First thing I did after it got stuck was go into recovery and reflash my current rom ( a CM11 snapshot) I then got faced with a status 7 error and so couldnt flash the rom. So then I flashed multiple other CM11 roms, none of which worked, so I flashed a CM10.2 stable rom which worked. I then got faced with the fix root before reboot thing and so I clicked yes. Still had the stuck booting thingy. I tried many things, flashing kernals roms gapps etc and nothing made a difference. I wiped cache, dalvik cache and no difference. I even wiped the system and tried to flash roms but only the 10.2 one would work, still got a status 7 with the CM11 ones. When I wiped my data however and flashed CM 10.2, it booted. I still couldn't flash the CM11 roms though even after a factory reset. So I have the reason to believe something in the data is wrong, not cache system or anything like that. What could it be? I don't want to have to lose all my data in order to be able to use my phone again, even then, something is still wrong as my phone won't flash CM11 roms anymore. So my questions are;
What things could have caused this?
Can this be a problem from flashing the supersu zip (a root issue)
Is it possible to somehow view or copy the internal data on a computer (since I cant get into the operating system), and this would allow me to get all my pictures contacts music etc anything so I can use my phone by wiping data?
Thanks, sorry this is quite long and probably hard to understand whats going on, but help is appriciated thanks
Don't fix root if you wish to use SuperSU instead builded-in cm superuser. Also try to flash via Odin latest recovery. TWRP should be fine. You can mount partitions from recovery level to download data to your computer. Of course if it still exists. If not, if they are corrupted you need to flash stock ROM and repeat whole cm11 adventure again. If Odin successfully flash the stock then it's a chance your partition layout and user data are untouched.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
Hey all,
I've got a N7105 (Galaxy Note II LTE) running CM12.1 and TWRP which I was planning to change shortly as it's old and the USB port has issues (charges but doesn't pass data; luckily it has a microsd slot). As it happens, the other day I left it discharge fully and turning it back on left it stuck at Samsung logo (not boot animation, the splash screen before it) forever.
I am: not a noob, I've rooted and flashed plenty of devices before.
I tried: removing battery for a while, charging fully, removing microsd and sim, clearing Cache and Dalvik. Nothing works.
I can: get into ODIN mode (but it's useless as USB data is not working); get into TWRP recovery; explore the Data partition in TWRP
I cannot: mount the System partition in TWRP, not even manually. It just does not let me select it, and gives an error whenever it needs to access it (e.g. if I try to backup it is says Error: unable to mount System)
I want: if possible to solve the issue without formatting Data. I had a TB backup but kinda old, so I got a Nandroid of Data and Boot out from TWRP and I suppose I could then recover stuff extracting from Nandroid through TB, but I've never done it and would rather be able to get a fresh TB backup and move on from there.
A few questions I have: any idea on why I am not able to mount System in TWRP? Could it help to reflash Boot or System, and if so how do I go to do that considering what I have is the whole CM rom package? (I remember being able to fastboot flash single partitions on Nexus devices but that's because the stock rom comes packaged in separate images).
Any input would be greatly appreciated!
Lazer Bear said:
Hey all,
I've got a N7105 (Galaxy Note II LTE) running CM12.1 and TWRP which I was planning to change shortly as it's old and the USB port has issues (charges but doesn't pass data; luckily it has a microsd slot). As it happens, the other day I left it discharge fully and turning it back on left it stuck at Samsung logo (not boot animation, the splash screen before it) forever.
I am: not a noob, I've rooted and flashed plenty of devices before.
I tried: removing battery for a while, charging fully, removing microsd and sim, clearing Cache and Dalvik. Nothing works.
I can: get into ODIN mode (but it's useless as USB data is not working); get into TWRP recovery; explore the Data partition in TWRP
I cannot: mount the System partition in TWRP, not even manually. It just does not let me select it, and gives an error whenever it needs to access it (e.g. if I try to backup it is says Error: unable to mount System)
I want: if possible to solve the issue without formatting Data. I had a TB backup but kinda old, so I got a Nandroid of Data and Boot out from TWRP and I suppose I could then recover stuff extracting from Nandroid through TB, but I've never done it and would rather be able to get a fresh TB backup and move on from there.
A few questions I have: any idea on why I am not able to mount System in TWRP? Could it help to reflash Boot or System, and if so how do I go to do that considering what I have is the whole CM rom package? (I remember being able to fastboot flash single partitions on Nexus devices but that's because the stock rom comes packaged in separate images).
Any input would be greatly appreciated!
Click to expand...
Click to collapse
The note 2 has this issue that makes it unable to be recognized by PC, so this isn't your phone problem, the only way to solve it is replacing the usb socket in your phone, anyway i can recommend dirty flashing your rom first, just flash the rom in recovery and wipe cache and Dalvik cache only then reboot.
If that didn't work, I'm afraid you might have to...... clear data ?
MigoMujahid said:
The note 2 has this issue that makes it unable to be recognized by PC, so this isn't your phone problem, the only way to solve it is replacing the usb socket in your phone, anyway i can recommend dirty flashing your rom first, just flash the rom in recovery and wipe cache and Dalvik cache only then reboot.
If that didn't work, I'm afraid you might have to...... clear data
Click to expand...
Click to collapse
Thanks for the input, I was thinking something along those lines but I wasn't totally sure, I always avoided dirty flashing as I heard of people having issues. Happily, it worked! Weirdest think I saw in a while, it gave me a bunch of errors with System partition (unable to mount, unmount, find), then it gave a "proceeding to patch system partition unconditionally", then it completed. The whole thing took less than 20secs so I do not think it even actually flashed the ROM. Now I am just getting some Play Services error, likely need to reinstall gapps, but phone boots just fine!
I seem to have shot myself in the foot recently. I've been on CM 13 for nearly a year now and I wanted to try out LineageOS for the hell of it since I am planning to get a new phone and I wanted to put LineageOS on that as well. So I downloaded an unofficial build of LineageOS for the G850W and followed some basic instructions: backup with TWRP, wipe with TWRP, and flash both the ROM and OpenGApps with TWRP. All three of these went well and I was able to install LineageOS. Now the problem: I tried restoring my backup (a CM 13 based backup) thinking I could restore some things from that backup and when I went to restart the CM boot screen popped up and I immediately knew I must have messed up. Checking my backup it contained boot, cache, system, EFS, modem, and a couple other folders/partitions that I can't remember off the top of my head. I then simply tried to redo everything again: backup, wipe, flash. While I am able to backup, wipe, and flash, and I am able to proceed past my device's boot screen, the Lineage OS boot screen seems to either be stuck or it is taking a long time. I've waited for 30 minutes with no change and I am sure that shouldn't be the case at all. Stock ROM was the same way, sitting on the Samsung logo with the sparkles forever. I managed to reinstall CM 13 but it's a very buggy install as sometimes it restarts randomly and goes through the "preparing applications" thing upon restart. Furthermore data doesn't seem to work and IMEI info is not found and sometimes in the stock recovery mode it shows that the EFS partition could not be found. Same thing happens when I poke around in ADB, I do not see any EFS partition when I type in the mount command. Clearly I've really messed things up. So would there be some way to fix things considering I do have a backup of things before I messed things up? How would I use my backup to fix everything? Would there be other tools I should be trying? Any help would be appreciated.
Flash original firmware
echo124 said:
Flash original firmware
Click to expand...
Click to collapse
I did: "Stock ROM was the same way, sitting on the Samsung logo with the sparkles forever".
Erase everything on your phone (aftet backup) and flash stock again.
echo124 said:
Erase everything on your phone (aftet backup) and flash stock again.
Click to expand...
Click to collapse
I've done that as well already, still the same issue.
:fingers-crossed:Flash stock, flash same version twrp used to backup, flash same version of cm 13 used on backup, try restore.