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 accidentally formatted my internal SD card with TWRP instead of factory reseting. I can get into recovery, but loading any ROM hangs at the loading screen. For awhile, TWRP was asking for a password, and then somehow I hit the magic combination of things to make that stop happening. I adb pushed an updated TWRP and reinstalling various ROMs.
All this started from trying to install Hyperdrive RLS8. I was running RLS7 fine, went for a clean install, spaced out and formatted the phone, flashed the ROM, and had a whole slew of stability problems. Things would randomly crash instantly, booted only 50% of the time, when it did, installing things would break it, tried various things to fix it, fixing permissions and wiping cache's and such, and results were unpredictable. Kept re-formatting and reflashing with different options until I finally realized that I was formatting it and that's probably what the whole problem was.
Currently I can't boot into a ROM, it hangs on the boot animation. I tried another clean install with RLS7, and the same thing happens. I'm assuming that I need to get back to stock somehow, but I'm not sure how. Odin has always confused me. I used the all in one tool to root awhile back, and I only used odin to send a kernel tar file. If I download a stock build, it's a zip file... so how can I odin it? Is that what I need to do? I'm imagining at this point that the file structure is messed up and I need to rebuild it somehow. I don't have my nandroid backup on this computer, so I haven't tried that yet.
You can either odin stock. It's about a 1.8gb file.
Or you can get a known working ROM on your sd card, factory reset wipe, wipe preload, wipe system, install known working rom+gapps+whatever, wipe cache and wipe dalvik. Reboot. If it sticks at the samsung logo pull the battery and then try to reboot again. Sometimes first boot can take a while. I'd give it 10 minutes before throwing in the towel lol
I bricked my phone by updating Hyperdrive (which I will never (curse words... lots of them) use again. Can someone tell me where to find this stock file? I've been searching long enough to get frustrated and delete several less diplomatic posts, settling with this one.
hey guys, I am a little confused. I just came to the S4 from a galaxy nexus, and I previously used CWM as my recovery option when doing clean install of new ROMS.
When I rooted my S4, I installed TWRP (via goomananger, version 2.5.0.2) because of people saying its much better (on the galaxy nexus forums). However, I keep reading issues of people being stuck in bootloops for TWRP when wiping data.
My question is -- what is this issue? Are you not supposed to clean flash with TWRP?? Or do you only do "factory reset" option in TWRP and not wipe the data?
As I am a little confused on this issue, is it more safe to just install most recent CWM and use that as recovery instead?
Thanks alot
No worries
uberpippi said:
I accidentally formatted my internal SD card with TWRP instead of factory reseting. I can get into recovery, but loading any ROM hangs at the loading screen. For awhile, TWRP was asking for a password, and then somehow I hit the magic combination of things to make that stop happening. I adb pushed an updated TWRP and reinstalling various ROMs.
All this started from trying to install Hyperdrive RLS8. I was running RLS7 fine, went for a clean install, spaced out and formatted the phone, flashed the ROM, and had a whole slew of stability problems. Things would randomly crash instantly, booted only 50% of the time, when it did, installing things would break it, tried various things to fix it, fixing permissions and wiping cache's and such, and results were unpredictable. Kept re-formatting and reflashing with different options until I finally realized that I was formatting it and that's probably what the whole problem was.
Currently I can't boot into a ROM, it hangs on the boot animation. I tried another clean install with RLS7, and the same thing happens. I'm assuming that I need to get back to stock somehow, but I'm not sure how. Odin has always confused me. I used the all in one tool to root awhile back, and I only used odin to send a kernel tar file. If I download a stock build, it's a zip file... so how can I odin it? Is that what I need to do? I'm imagining at this point that the file structure is messed up and I need to rebuild it somehow. I don't have my nandroid backup on this computer, so I haven't tried that yet.
Click to expand...
Click to collapse
Try using odin to flash to stock. Then re-root and install custom recovery and whichever rom. I had a similar problem posted here with no help from the big brains. Had to trial and error with caution on my own. Kinda disappointing since the answer is quite simple once you connect all the dots. Flashing in odin will fix yer internal storage problem because it redefines everything.
cidorov said:
Try using odin to flash to stock. Then re-root and install custom recovery and whichever rom. I had a similar problem posted here with no help from the big brains. Had to trial and error with caution on my own. Kinda disappointing since the answer is quite simple once you connect all the dots. Flashing in odin will fix yer internal storage problem because it redefines everything.
Click to expand...
Click to collapse
uberpippi said:
I accidentally formatted my internal SD card with TWRP instead of factory reseting. I can get into recovery, but loading any ROM hangs at the loading screen. For awhile, TWRP was asking for a password, and then somehow I hit the magic combination of things to make that stop happening. I adb pushed an updated TWRP and reinstalling various ROMs.
All this started from trying to install Hyperdrive RLS8. I was running RLS7 fine, went for a clean install, spaced out and formatted the phone, flashed the ROM, and had a whole slew of stability problems. Things would randomly crash instantly, booted only 50% of the time, when it did, installing things would break it, tried various things to fix it, fixing permissions and wiping cache's and such, and results were unpredictable. Kept re-formatting and reflashing with different options until I finally realized that I was formatting it and that's probably what the whole problem was.
Currently I can't boot into a ROM, it hangs on the boot animation. I tried another clean install with RLS7, and the same thing happens. I'm assuming that I need to get back to stock somehow, but I'm not sure how. Odin has always confused me. I used the all in one tool to root awhile back, and I only used odin to send a kernel tar file. If I download a stock build, it's a zip file... so how can I odin it? Is that what I need to do? I'm imagining at this point that the file structure is messed up and I need to rebuild it somehow. I don't have my nandroid backup on this computer, so I haven't tried that yet.
Click to expand...
Click to collapse
Yes this would probably be your best bet. I wouldn't say the answer "is quite simple when you connect the dots" though, because with that logic there would be no PC problems, you would just connect the dots and format the harddrive and Windows will redefine everything else for you!
But back to seriousness, you have to download a stock factory image and its actually a tar.md5 file and not a .zip because you cant flash zips through odin. The stock factory images can be found in the development section, and they are usually quite large files (2gb+ when extracted!) and you will have to download odin and make sure you have the latest usb drivers from samsung. Then its pretty straight forward, The threads in the development section have guides for how to use odin. The stock image contains all the partitions within in it and will effectively repartition your device when you flash it so no need to use a pit file.
Surge1223 said:
Yes this would probably be your best bet. I wouldn't say the answer "is quite simple when you connect the dots" though, because with that logic there would be no PC problems, you would just connect the dots and format the harddrive and Windows will redefine everything else for you!
But back to seriousness, you have to download a stock factory image and its actually a tar.md5 file and not a .zip because you cant flash zips through odin. The stock factory images can be found in the development section, and they are usually quite large files (2gb+ when extracted!) and you will have to download odin and make sure you have the latest usb drivers from samsung. Then its pretty straight forward, The threads in the development section have guides for how to use odin. The stock image contains all the partitions within in it and will effectively repartition your device when you flash it so no need to use a pit file.
Click to expand...
Click to collapse
Just to follow up, that's what I ended up doing. I used the "No-wipe" factory image, odin'd it, re-rooted (I don't know if I had to do that step, but I did), and then loaded my ROM of choice and it works perfectly now. Thanks!
Hi,
I have a big problem. I was trying to install the newest Renovate ROM, and I think I did everything correctly. I pasted the ROM into my phone's storage, booted into recovery, and installed it choosing the "update only" option (I had Renovate 2.1 before).
Everything seemed fine, except rebooting the phone takes me to recovery, and every reboot option I could find always reboot me to recovery. I can also get to the bootloader, but eventually I ended up back at recovery...
What should I do? I have a Nandroid backup of the phone before I flashed Renovate 5.0, should I full wipe the phone and restore that backup?
Any help would be appreciated.
You should read before you mess with your phone.
Sent from my HTC One using Tapatalk 4
xexxonx said:
Hi,
I have a big problem. I was trying to install the newest Renovate ROM, and I think I did everything correctly. I pasted the ROM into my phone's storage, booted into recovery, and installed it choosing the "update only" option (I had Renovate 2.1 before).
Everything seemed fine, except rebooting the phone takes me to recovery, and every reboot option I could find always reboot me to recovery. I can also get to the bootloader, but eventually I ended up back at recovery...
What should I do? I have a Nandroid backup of the phone before I flashed Renovate 5.0, should I full wipe the phone and restore that backup?
Any help would be appreciated.
Click to expand...
Click to collapse
Restore your nandroid as long as all was working well before your issue.
First off I am on mdk and rooted and up until today have been running hd 10.2. I had been having some weird things happen with twrp 2502 so I went into goo and tried to update to the newest version of twrp. it downloaded and went through with everything and I rebooted into recovery. once I got into recovery it was showing I was still on 2502, but it was asking for a password which I had never seen before. I backed out and tried to boot into my rom again and it got stuck on the samsung custom screen. pulled the battery a few times and still kept getting stuck. went back into recovery and tried to restore a known good backup that I had restored before, but it keeps failing. I had rls12 on my phone so I tried installing it dirty since I cant wipe anything due to the whole password thing in twrp which said it was succesful but still gets stuck on the samsung custom screen. it sits there for about 10 seconds and loops. I tried about 10 more times to get my backup restored and it finally finished and booted into the rom. I left it this way for an hour or so and did some stuff with my phone, tried to update twrp again which did the same thing again and still shows 2502. after the reboot I am back to the same problem of not being able to do anything in twrp except restore or dirty flash, I cant get the usb to mount in twrp so I cant try putting another rom on the phone unless I go and buy a micro sd adapter.
I am in the process of downloading a stock mdk rom to try and flash in odin, but is there anything I can try before I go through with this, or is it pretty much my only option.
after some more research I think I figured out what caused all this. I wiped the data partition with the old version of twrp which screwed it up pretty bad. Apparently the older versions of twrp were known to have this problem. I kept trying to restore, but trying to restore kept failing on the data partition. After about 25 attempts of trying to restore just the data partition I was able to get it to work finally, and then I restored the the others and got it to boot back into the rom. like an idiot I rebooted the phone back into recovery after it finished and had the same problem again. another couple hours wasted trying to restore the data partition and it worked again and this time i was able to get twrp to update and then went back to recovery and formated the data partition again and it seems to have fixed the problem. Now to figure out why hd rls 12 wont install.
So I created a full backup of my device using TWRP and now just tried to restore it and it's just completely messed up my device. I got an error saying extracttarfork() process ended with error=255. My device was a custom timurs rom which I dont remember how to go through the whole process again. From the videos I have seen apparently I need to reflash it. How do I do that? What files do I need? Can someone please help
So, although the message logs shows that it formatted and wiped the system, I just thought i would give it a restart and see if I get a bootloop. But it seems to have not done anything of such like deleting or wiping because the system is still the same. However, I did notice my bootanimation logo has gone back to the version before the backup. So I don't know what exactly has happened.
Is it possible on TWRP to do a clean fresh install and then flash the Timurs Kernel rom back on? My tablet is in fix mode and I don't really have access to the volume buttons to force TWRP easily. So I'm thinking I would like to do a clean android refresh and flash the kernel again.
It's definately messed something up because now when I try to transfer a file into the System partition using TWRP i get error saying Full SELinux support is present. This never happened before. Any ideas please on how I can just start fresh on this?