Database Develop

[Q] Stuck at Samsung Boot Screen

Hi guys,
I just flashed the _AllianceROM_JellyBean XXLSC_ALpha1 via rom customizer from JB RocketRom V1. I am now stuck at samsung boot screen and i can't access my nandroid backups generated using CWM as the TWRP doesn't detact them . I would really appreciate if some1 could tell me how can i solve this problem.
Thanks!

Have you tried doing a factory reset?
Use odin and download mode to go back to any stock rom as a second option

I didn't have the chance to enable usb debugging before this happen. Is there any other solutions for this?

Why do you need adb? Boot into recovery and do a resrt

xxeniumxx said:
Hi guys,
I just flashed the _AllianceROM_JellyBean XXLSC_ALpha1 via rom customizer from JB RocketRom V1. I am now stuck at samsung boot screen and i can't access my nandroid backups generated using CWM as the TWRP doesn't detact them . I would really appreciate if some1 could tell me how can i solve this problem.
Thanks!
Click to expand...
Click to collapse
Stuck at samsung boot screen (the one with samsung logo and NOT galaxy note) is called bootloop
You need a fresh new system, try the following:
1- reboot into recovery (Home + Power + Volume UP)
2- Install a safe kernel - I recommend (Abyss GB Kernel)
3- In recovery >> Advanced >> reboot Recovery
4- when it boots up, do Factory Reset/Data Wipe 3 times
5- Do Cache wipe 3 times
6- Go to Advanced & do Dalvik Cache wipe 3 times
7- Go to Mounts & Storage & do FORMAT SYSTEM
8- Go to Mounts & Storage & do FORMAT PRELOAD
9- Now, Re-Flash Alliance ROM & Reboot - The ROM should come with its own Kernel
Furthermore, it is best if you did your nandroid backups in CWM just before installing a new ROM and while being on Abyss kernel (or whatever safe kernel you're intending to use) to avoid MD5 Checksum failure when restoring
Also, I would recommend you do MD5 Checksum on the Alliance ROM zip file and make sure it matches the one in the thread (you'll find it in the OP, almost always next to the download link - I use MD5Check for windows
P.S. If you can't get into recovery, you got a brick issue, refer to brick threads
Best of luck

[Q] NANDROID restores: TWRP won't boot, CWM corrupts data

Sorry for this being lengthy, I wanted to make sure I gave enough info.
Neither of the two most popular recovery tools are working for me. They both state the backups are successful but the restores have flaws. Is anyone experiencing the problems I am? If so, does anyone know what to do about them?
CWM Recovery Touch (and non-touch): Data restores leave certain things not working. I'm not sure what processes are stopping because it flashes and disappears to fast. I know that it causes the ROM Manager for CWM, Titanium Backup Pro, Google Play, and likely more to crash (disappear) immediately upon opening. Chrome browser *might* bright up the keyboard on the first click but it won't work then it will disappear and not come back (but the keyboard does work in other areas, I use Swype Keyboard). I've tried clearing cache and/or data on all 3, uninstalling them then re-installing via APK and various other things. This occurs regardless of whether a factory reset (data/cache) wipe is performed before the restore. However, if I restore with CWM Recovery *then* do a factory reset, Google Play will work and nothing crashes, nor are their long delays.
TWRP does not boot after a restore. It will pass the initial screen showing the phone model, the phone carrier splash screen, then sit on Samsung with the LED solid bright blue and hang.
My goal is to simply trust my backups. The CWM Recovery problem is workable in a terrible situation since my Titanium backups will get my phone *almost* to where it was (barring widgets, which are pain to re-setup, and a few other things).
Titanium Backup Pro question: Is it normal when you remove a system app with Titanium Backup Pro, then do a restore in CWM for that app to still be gone? Since I use the Swype keyboard I removed the other once, did a restore with CWM, had the problem so I did a factory reset and my stock keyboard was missing still (I think it's a Samsung keyboard)
App Details:
CWM Recovery Touch 6.0.4.7 (for Samsung Galaxy S3 LTE (GT-I9305))
TWRP 2.6.3.0 (for Samsung Galaxy S3 LTE (International i9305))
Phone Details:
Carrier: T-Mobile (Germany)
Model number: GT-I9305
Android Version: 4.3 (stock from Kies, so I do have Knox and it's disabled via SuperSU 1.91 from chainfire)
Baseband version: I9305XXUEMK1
Kernel version: 3.0.31-2051278
Build number: JSS15J.I9305XXUEML5

Titanium Backup Pro question: Is it normal when you remove a system app with Titanium Backup Pro, then do a restore in CWM for that app to still be gone?
No a Nandroid backup wipes the phone .
make a Nandroid then in recovery format system sdcard data cache .
You now have an empty phone and restoring the Nandroid should return exact same state .
All this reads as you are doing something wrong .

JJEgan said:
All this reads as you are doing something wrong .
Click to expand...
Click to collapse
I hope it is as simple as that. I'm booting up in recovery mode (Volume Up + Home + Power) choosing the backup or restore option, then backing up to the External SD card. Then on the restore I'm doing the same except selecting restore from the SD card (I've re-created the CWM problem 5 times, once was with advanced restore of just data the rest were basic restores doing everything). I'm not really sure what I could be doing wrong.
I have the 4.3 stock ROM before I did any custom stuff to the phone (which installed KNOX). I used chainfire's tar.md5 auto root image with Odin 3.09 in download mode when I root the phone, and I've installed CWM Recovery with ROM Manager and with an Odin tar flash in download mode. The install of TWRP was from an Odin 3.09 tar flash in download mode too.
With regard to the TWRP and CWM Recovery, I'm not really sure how easy it is for me to have messed up that part. Do you have this same model phone? Is it possible KNOX is involved in my issues? Maybe I should downgrade one of the recovery tools?

Downgrade your recovery and try again.

jonesjw362 said:
Downgrade your recovery and try again.
Click to expand...
Click to collapse
That's what I was thinking might be the best solution. Since the flaw in the restores with CWM Recovery are workable for me, I figured I may just wait until I have a need to restore to do that though. Once I do, I'll probably do a bunch of tests until I find something that works solid.
I've already restored my backups and widgets etc. a couple of times and don't really want to do it over again only to test. If there's a way to restore all of that without my having to set it up myself then I'll do it. Right now my Titanium restores don't include wallpaper (except lock screen), most of my widgets (maybe all, can't remember), and I think there was one other thing.

Advanced restore in recovery restore data only .

JJEgan said:
Advanced restore in recovery restore data only .
Click to expand...
Click to collapse
I tried that once, that's why I believe the CWM Recovery issue to be specifically with data. I'm going to do it again right now though and if things are messed up again I'm going to try jonesjw362's suggestion.

Downgrading didn't help (6.0.3.6 had a constant barrage of 4-5 apps re-crashing over and over again during the process).
I tried the following with CWM Recovery Touch 6.0.3.6, 6.0.4.5 and 6.0.4.7:
Factory reset wipe, open and test Google Play (more things break but that's the one I chose to test). Reboot into recovery mode and backup to the SD Card (not the external). Immediately advance restored data only (no wipe). Booted up, Google Play crashed, rebooted back into recovery and factory reset (data/cache) and advance restored data again with the same result.
I didn't try a downgraded version of TWRP (probably won't for now). I'm back to 6.0.4.7 and restoring my backups to get my phone back fully. Hopefully CWM Recovery comes out with a new version sometime in the near future that works for me or someone has some insight into what I can do to fix it with the existing (I'm out of ideas).

Issue Samsung stock 4.3 ROM
I ended up switching to CM 10.1.3 (was going to hold off until 11 was stable) but the Samsung stock 4.3 ROM was destroying my battery. After switching, I tested a NANDROID backup and restore with CWM Recovery Touch 6.0.4.7 (same version I was having problems with). The restore worked as it should, no problems.
End Result: As far as I can tell, the cause of the CWM Recovery data partition problem is due to the Samsung 4.3 ROM.
Edit: I was going to mark the post Resolved but I can't seem to find the drop down to do so (at least not in the same place I thought it was).

some problems with my i9305 after installing CM12.1 -> I hope you can help

Hi there,
my plan was to install CM 12.1 with the help of this site:
http://forum.xda-developers.com/galaxy-s3/development-i9305/rom-t3066156
At first, I used Odin to get TWRP on my phone. With TWRP I did a complete backup (EFS, Boot, Cach, System, Data).
Actually, I thought I have done everything like it is instructed on this page.
->
"First time installing CyanogenMod 12.1 to your Galaxy S3 I9305, or coming from another ROM:
- Read known issues ans FAQs
- Flash one of the recovery images (CWM or TWRP)
- Copy GApps and CM12.1 ZIPs to your SDCard
- Boot into Recovery
- Flash CM12.1 zip from SDCard
- Flash GApps zip from SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!"
<-
After installing GApps, I wiped all data on the internal storage, did a factory reset and rebooted.
Unfortunately, I have been stucking at boot. There has been only the CM symbol on the display.
With TWRP I restored my backup. After that, my phone has been booting normally, but it could not find any mobile service.
According to the settings, my phone didn't recognise my sim card anymore.
(After using Odin, I did a reboot and noticed already that my phone hasn't got any mobile service anymore. Can this be?)
Moreover, I discovered that I my phone has got difficulties to copy things from the computer to the SD-card or to the internal storage.
Even copying things from the SD-card to the internal storage, or the other way round, using a file manager app like "Astro" is not working.
I tried to do a factory reset, but then again, the phone stucks at boot. On the display just appears "SAMSUNG".
Can you guys please help me to get back to a working phone?
With best regards,
New.Android.User

which version of TWRP did you flash?

I used twrp-2.8.7.0-i9305.img.tar

although pm'ed you the solution I'll post a big warning again:
DO NOT USE TWRP 2.8.7.0 from twrp.me. This build is faulty and causes a soft brick. To fix that you need to flash stock rom again and stay on TWRP 2.8.5.0 or any other recent recovery of Philz Touch or CWM.

alright! Thank you so much!
So, I will continue like that:
1. With the help of Odin i will install a new bootloader. I recommended twrp-2.8.5.0-i9305.tar
2. Then again with Odin, I will install the stock rom using -> sammobile.com/firmwares/download/45775/I9305XXUFOB2_I9305DTMFOB2_DTM/
3. Then I will go to the TWRP-recovery and install CM12.1 with GApps.
Is this the right order?

first stock, then custom recovery and then you can flash rom and gapps

Phone doesn't boot, just samsung logo

Hello, I have an s3 mini I8190N model, with CM 11.0 kitkat 4.4.4(cm11.0_golden.nova.20150108) installed on it since nearly its release, the phone worked very fine, till today I entered the ROM manager app and pushed the "Boot to Recovery" button, so now it doesn't boot neither to the system nor to the recovery. I remember having CWM on it.
What I get now is only the "Samsung S3 mini..." splash screen, nothing else.
I have these files ready on my computer:
Recovery-CWM-I8190-Official-TOUCH-6.0.2.7.ODIN.zip
cm11.0_golden.nova.20150108.zip
What should I do now ??

You probably soft bricked your phone, I suggest you to check if you still can go into download mode and flash with Odin a wipe file and then a stock rom, once it is working again flash twrp recovery instead of cwm with Odin and try not to use rom manager, I've heard it causes the brick you have.

hng34 said:
You probably soft bricked your phone, I suggest you to check if you still can go into download mode and flash with Odin a wipe file and then a stock rom, once it is working again flash twrp recovery instead of cwm with Odin and try not to use rom manager, I've heard it causes the brick you have.
Click to expand...
Click to collapse
Yes, I can go to download mode, but will my data persist after flashing ?

daemon11 said:
Yes, I can go to download mode, but will my data persist after flashing ?
Click to expand...
Click to collapse
Not if you flash the wipe file, you can try flashing the stock rom without the wipe but It's recommended to do a clean install. Another option is to flash a file called PARAM to see if it solves the bootloop. But the way I fixed a softbrick in my phone was flashing param, wipe and stock rom in that order with Odin.
Are you able to go into recovery?

hng34 said:
Not if you flash the wipe file, you can try flashing the stock rom without the wipe but It's recommended to do a clean install. Another option is to flash a file called PARAM to see if it solves the bootloop. But the way I fixed a softbrick in my phone was flashing param, wipe and stock rom in that order with Odin.
Are you able to go into recovery?
Click to expand...
Click to collapse
I will install TWRP through Odin v3 on the phone, then I'll flash without wiping data, then I'll recover necessary data(especially contacts) and then redo a clean install with wiping all the rubbish files.
I will tell you after I follow these steps on whether it was successful or not.
Thank you very much!

daemon11 said:
I will install TWRP through Odin v3 on the phone, then I'll flash without wiping data, then I'll recover necessary data(especially contacts) and then redo a clean install with wiping all the rubbish files.
I will tell you after I follow these steps on whether it was successful or not.
Thank you very much!
Click to expand...
Click to collapse
No problem, flash the custom recovery after the stock rom though.

hng34 said:
No problem, flash the custom recovery after the stock rom though.
Click to expand...
Click to collapse
Effectively, I installed the missing recovery software (TWRP), and after that I selected from the boot menu in TWRP the "System" entry, then it booted fine and I didn't lose any of my data. Though I have to make a clean flash next time, by cleaning the dalvik cache... etc.
Thank you for your support!

Updating without loosing root

Hi all
I don't have flash for a while then I come to you for some info. I am currently in G781BXXU3CUG1 root + Magisk.
I'd love to do the latest update but no bull****.
As I go from android 11 to 12 is it necessary to do a full wipe or a simple update is possible?
I just need to flash new firmware and reflash twrp & magisk?
Thank you in advance for your answers
Have a good evening

anyone can explain how I can do that? plz

it's not possible to manually update and keep root or TWRP. there's definitely going to be some ''bull****'' involved.
even flashing with home_CSC and keeping your apps will still wipe root and TWRP. restoring TWRP again will require a format of the data partition, wiping your apps anyway. plus you need to set the phone up twice, once after flashing stock and once after flashing vbmeta again.
you can either backup the data partition in TWRP before you start and restore after updating and flashing TWRP. you'd still need to root again. you'd wanna move any TWRP backup you make to somewhere that won't get wiped.
or you can use a root backup app to backup your apps to ext SDcard, do all your updates, TWRP flash and rooting before restoring your apps with the app again.
there are no quick ways thru it.

Thx for your response
So we need to do a backup each time we want to upgrade our firmware.
Whatt's your best solution to do it? I did it with smart switch but I want to know others solutions

for backing up apps I use an app from f-droid called OAndBackupX, but some say Titanium Backup works again (no idea on that). apparently Swift Backup is good but I didn't like it.
you can also use TWRP to backup your data partition too but it's probably best to clear dalvik/art and cache after restoring it on the new rom.
then you put root back (via the best method) and flash a patched boot.img to the boot partition with TWRP.