Database Develop

[Q] Phone won't boot after Ultimate JB ROM Upgrade

Can anyone please help?
I just installed the Ultimate JB ROM XXLSA 4.1.2 v5 upgrade on top of v4.
All went perfectly well and I was able to enter all my setup and account details after the initial boot of the phone.
When I tried to re-install apps from Google Play, however, (Titanium Backup Pro, Quickboot) the phone hangs at the Samsung Splash screen and won't go any further. I re-tried the procedure 3 times but each time the result is the same.
Can anyone tell me what the problem could be? I followed all the instructions about wiping etc. correctly.
Trevor

v4 and v5 use completely different bases (LS7 and LSA).
I would save everything to my ext SD card.
Then goto Settings > Backup & Restore > Factory Reset (don't click on format external sd card).
Your phone will restart and do some crazy things. Then restart again.
When you get to the welcome page, or bootloop... take the battery out (its safe).
Then hold Vol Up, Home and Power (let go of Power after ~5-15sec) and goto recovery.
In recovery, wipe cache.
Then format data.
Then format system.
Then format cache.
Then wipe Dalvik cache.
Then install the v5 zip.
It shouldn't restart automatically, but it might, don't worry let it.
Now you should have a fully, fresh, clean install of v5.
Connect to your wifi, go through the start up.
Goto SuperSU and update binary.
Goto Play Store and install TiBu.
Open TiBu and grant it root access.
Close TiBu.
Connect phone to PC, then copy your TitaniumBackup folder into your sdcard directory.
Open TiBU and now, it will see your previous saves.
Restore your apps + data.
Presto! No bootlooping and no App FC !

Thanks for going to all the trouble to write all that out.
I followed the instructions to the letter but no, same result I'm afraid: it worked fine but as soon as I installed Titanium and granted root access, it asked me to choose to restore the original phone ID which I did. The phone rebooted but then wouldn't go past the "Samsung Galaxy Note Gt-N7000" screen.
I have no choice but to restore from my Nandroid backup. This is really p****ng me off but at least I can restore v4 easily.
Thanks again
Trevor
Kangal said:
v4 and v5 use completely different bases (LS7 and LSA).
I would save everything to my ext SD card.
Then goto Settings > Backup & Restore > Factory Reset (don't click on format external sd card).
Your phone will restart and do some crazy things. Then restart again.
When you get to the welcome page, or bootloop... take the battery out (its safe).
Then hold Vol Up, Home and Power (let go of Power after ~5-15sec) and goto recovery.
In recovery, wipe cache.
Then format data.
Then format system.
Then format cache.
Then wipe Dalvik cache.
Then install the v5 zip.
It shouldn't restart automatically, but it might, don't worry let it.
Now you should have a fully, fresh, clean install of v5.
Connect to your wifi, go through the start up.
Goto SuperSU and update binary.
Goto Play Store and install TiBu.
Open TiBu and grant it root access.
Close TiBu.
Connect phone to PC, then copy your TitaniumBackup folder into your sdcard directory.
Open TiBU and now, it will see your previous saves.
Restore your apps + data.
Presto! No bootlooping and no App FC !
Click to expand...
Click to collapse

Mystery solved - well partly. Turns out Titanium Backup Pro was causing it on my phone for some reason. This was naturally the first app I wanted to install so I could restore apps one by one from the Nandroid backup. I tried Quickboot too which also caused the same problem so because TB and then QB did the same thing I assumed every app was going to cause trouble. Shouldn't jump to conclusions, I know.
I have JB Ultimate XXSLA v5 installed and am restoring my apps one at a time from Google Play and making new Nandroid backups as I go along.
And now I just tried installing TB free version - the phone boots normally! Then I installed the TB Pro version and again the phone boots normally. When TB was the first app I installed after the ROM upgrade it hung up the phone every time on 6 attempts. I'll try re-installing Quickboot now and see what happens. Conclusion: I must have been doing something in the wrong sequence but can's see what.
Many thanks for your help.
Trevor
sacentre said:
Thanks for going to all the trouble to write all that out.
I followed the instructions to the letter but no, same result I'm afraid: it worked fine but as soon as I installed Titanium and granted root access, it asked me to choose to restore the original phone ID which I did. The phone rebooted but then wouldn't go past the "Samsung Galaxy Note Gt-N7000" screen.
I have no choice but to restore from my Nandroid backup. This is really p****ng me off but at least I can restore v4 easily.
Thanks again
Trevor
Click to expand...
Click to collapse

[Q] CWM recovery loop, stock ROM

Tried ROM Manager backup of factory ROM.
Now, I power on and get CWM recovery. Choosing reboot always returns me
to CWM recov. I read every thread in this forum that refers to
loop, brick, etc. I have various backups, but I don't know what they
are worth, best way to use them. How to get out of the boot loop?
Best outcome would be to recover my last stable state. Factory reset
would be ok. Hardbrick would be a drag.
* Bought factory unlocked G-ST6500D (no vendor) in Spain.
* Have current non-root backups of contacts, sms, media, calendar, etc. on
laptop.
* Installed CWM v5.0.2.8 with Odin (three yellow boxes appeared in odin,
FWIW), and rooted. Froze bloatware listed by some people as safe, but
did not delete any factory installed software.
* Wanted to have a stock ROM backup before I did anything else. It's
not clear to me whether it is best/possible to download one or create
an image from my device. Started reading/trying backup apps, but I
don't really know what each one does.
* Did a full backup, apps + data, to extSD, and copy to laptop with Titanium
backup (free). This wrote >1000 files.
* Did most complete (as best I could tell) backup to extSD and laptop
with Online Nandroid app. This wrote boot.img, cache.ext4.tar,
data.ext4.tar, nandroid.md5, recovery.img, system.ext4.tar. Can these
be used to restore ?
* Tried to backup the ROM with ROM Manager app, but could not find an
option to backup to ext SD, only int SD. There was only 200MB free, so
I knew this would fail. I choose this anyway, hoping it would realize
there is not enough space and offer to change the path. The phone
rebooted into CWM and began a backup. After a few minutes, it printed
an error message and told me where a log was written, and rebooted
into CWM recovery. I tried rebooting, holding buttons, removing
battery, etc. Always returns to CWM recovery. Tried the 'backup and
restore' menu hoping it would give info on the backup. Instead, it
immediately started another backup, this time showing 1GB intSD
free. This backup reported success, then reboot into CWM recov.
* Since then, from CWM, I did 'wipe cache partition' and 'wipe davlik
cache'. Did not yet try factory reset.
* Show log ends with
"skipping exectuion of extendedcommand, file not found"
I read that sometimes it is possible to exit a boot loop without
flashing anything. If that is not possible, I guess I should do
factory reset. If that does not work, then I guess I should try
restoring something somehow: Use CWM recovery to recover nandroid
backup from extSD? Or install something via Odin ? For any solutions,
I am more comfortable doing things from linux than MSWin, but I think
that is not possible. Do I have to race to solve this before the
battery runs out?
Thank you for reading.

just install cwm 6.0.3.3 b2 from TheWhisps goo.im account and then should everything work fine.

midzan21 said:
just install cwm 6.0.3.3 b2 from TheWhisps goo.im account and then should everything work fine.
Click to expand...
Click to collapse
Thanks. I just figured that out after a several hours of reading. Finally saw stories on the thread
introducing CWM 6.0.3.3 of people who never flashed a ROM and still had boot loops.
I was on the wrong track because I assumed it was the filled up int. SD causing the
problem. I still have to fix that, but my phone is running. It would be nice if ROM Manager or CWM calculated the space
needed and refused to start if insufficient. But, I understand that there are few good devs and much to do.

How-To: Samsung Allshare Cast dongle with custom N7100 ROM

Hey guys,
I was having serious issues getting my Allshare Cast dongle to work with my rooted Note 2 (N7100). It either broke off the connection because of the flash counter or (even worse), when I ran TriangleAway beforehand, always rebootet my phone.
I've dug through countless threads addressing this issue and offering all kinds of different until I was finally able to make it work - still being rooted and using a custom rom. So I thought I'd just share my solution with anybody here who may find it useful.
*Edit*
Seems like Allshare Cast still tends to be a bit picky. The first connection is stable, but a second one reboots my phone after a few minutes. Quite annoying, but at least it works.
As usual, I will not be held responsible for any damage that might occur, so don't blame me if your phone blows up itself, or your house. :angel:
This works *for me*, other phones might yield other results.
These are step-by-step instructions if you're coming either from a f%*'ed up ROM that needs major repairs anyway (like me), or from a different android version. If you're running a 4.1.2 ROM you can try to jump directly to step 2. c). Still, I'd suggest you backup everything, see below 2. a)
Here we go:
1. Things you'll need:
a) Wanamlite 3.9 (http://wanamlite.com/2013/07/19/wanamlite-mg1-v3-9-android-4-1-2-clean-stable/) by Wanam (who saved me from ruining my phone btw: tried Wanamlite 4.2 with new bootloader, and without his warning, I would've used the MK4 bootloader instead of MJ5 and would've been stuck with Android 4.3/Know forever...)
b) Adam Kernel v2.7, Odin and/or CWM version (http://wanamlite.com/2013/07/19/adam-kernel-v2-7/) by Wanam
c) Stock recovery, kernel, etc. (http://forum.xda-developers.com/showpost.php?p=31986738&postcount=7), provided by dr. ketan. I'm using this one: http://d-h.st/gwn (Stock Recovery/Kernel/Modem from XXDMB6 19th March13)
d) Mobile Odin (http://forum.xda-developers.com/showthread.php?t=1347899) by Chainfire
along with the FlashKernel file (MobileODIN_FlashKernel_N7100-v5.0.apk) further down on the same page. if v5.0 doesn't work, try v4.0 instead.
e) TriangleAway (http://forum.xda-developers.com/showthread.php?t=1494114) by Chainfire
f) I'm assuming you're already rooted and therefore have a working CWM/TWRM running.
2. What to do (step-by-step):
a) I'm being a bit paranoid by now, but for various good reasons. These instructions may be a bit overcautious, but at least your data will be safe from being accidentally erased. Trust me, you do not want that ever to happen... :crying:
Also, I always carry a ROM with me so I can repair my phone on the go. So of course, you can also do the flashing via PC Odin, but I prefer the CWM method I've described further down.
- backup everything. And I mean EVERYTHING! I did a full backup, i.e. Titanium Backup, TWRP backup, and I copied the whole contents of my internal and external SD cards to my PC. I'd even suggest you use another extSd during this process (which will save you from the hassle of copying the whole thing btw). This whole backup thing took me about 2-3 hours, but I would've gone mad if I'd lost either internal or external SD data.
- copy Wanamlite 3.9 onto the external SD your're going to use.
- power off your phone (take out the battery to be sure)
- take out your external sd to protect all your precious data. Just in case you accidentally do something wrong and end up formatting the extSd (in TWRM, this option hovers dangerously between "Factory Reset" and "Format Data")
- boot into recovery and do a full wipe (Wipe Cache / Wipe Dalvik Cache / Factory Reset / Format Data)
- power off your phone (take out the battery to be sure), re-insert the external SD
- boot into recovery and flash Wanamlite 3.9 (follow the instructions on his site). Be sure to chose Adam Kernel and checke "Allshare Cast" during the installation process. The Adam Kernel works best with TriangleAway, because (unlike the stock kernel provided with his ROM) you can reset the flash counter without rebooting.
Now you have an absolutely clean 4.1.2 rooted custom ROM running on your phone.
b) Restore your data.
- run Titanium Backup, and restore everything that's important (all user apps w/ data, call logs, messages, email etc.). I'd suggest you just leave out system apps if you're coming from another ROM. You can try to restore everything of course, worst thing to happen is that you'll habe to re-wipe and then re-flash the ROM. In my case, it was no problem, because I had made my backup from this very ROM version.
- Next, copy at least the "Android" folder (containing /data and /obb) from your backup back to your internal SD card. By default, TB doesn't backup large files and folders, so all the bigger apps (like e.g. games) are still missing. If asked to overwrite, simply say "yes". If you want to make sure everything's back to how it was before, copy your whole internal SD backup back to your phone.
c) You've spent an awful lot of time by now, and still, Allshare Cast won't work. So let's go for it:
- install Mobile Odin and the appropriate Flashkernel.apk
- install TriangleAway
- unpack and then copy the contents of "Stock Recovery/Kernel/Modem from XXDMB6 19th March13" to your internal or external SD card (doesn't matter which one).
- run TriangleAway. It should read "Counter: 1 /Binary: Custom".
- tap "Reset flash counter". TriangleAway confirms that the counter was reset to 0 and closes.
- restart the app. Now you should see "Counter:0 / Binary: Official".
- run Mobile Odin, chose the stock kernel (tap "Kernel" -> "[path where you stored the kernel.tar from the archive]")
- tap "Flash Firmware". Your phone will reboot.
Congratulations! If you did everything correctly, you should now be running Wanamlite 3.9 (JB 4.1.2) ROM with rooted stock kernel. Allshare Cast works like it should. FIFA14 or DIII4A are really fun on a 40" screen.
If you don't want to use the stock kernel all the time, flash Adam Kernel v2.7 through Mobile Odin or CWM. Allshare Cast functionality will be broken, but you have all the nice benefits of the custom kernel like STweaks or BoefflaSound. To make Allshare Cast work again, simply repeat the last five steps from above: "c) - run TriangleAway... etc."
That's it. I hope this is helpful! Suggestions are welcome. If something's missing, or if I posted anything dangerous, please feel free to scream, and I'll correct it ASAP.
Cheers,
- Alex

Thanks for the nice review. I have these and wholeheartedly recommend them as well.

does anyone know how to update Allshare Dongle via N7100?
I've had many ROMs and on every single one I have message that update was downloaded and to restart the dongle, but after I restart the dongle it connects again with the same message, so it is infinite loop. I can connect, but sometimes it laggs, so I assume that newer firmware would fix that issue.
I've even contacted Samsung's support service and they couldn't help me. They told me to wait for update, but even on the newest stock it is still the same.
If anyone knows the solution please share.

thanks
thanks for the review its really helpful

MM - NanDroid Backups Disappearing!

Hi,
May I please humbly request some help with my issue?
I have an N910T, Rooted, w/MM 6.0.1 Samsung OEM ROM.
I started with TWRP 3.0.2.0 and it was working fine, except that for some reason, my NanDroid Backups would just disappear. I mean even the TWRP folder was gone!
When I would then boot into Recovery, it would say something about a "Systemless Recovery" and then ask me if I wanted it to Write to the System. I would say "Yes" (it's the only way you can even save the options you choose).
All would be well for a bit and then it would happen again.
So I tried replacing TWRP with PhilZ Touch Recovery 6.59.0 and it was working fine, until it just happened again. Except when I booted into PhilZ Recovery, it didn't ask me about the Systemless Recovery.
I have tried both my Internal & External Storages and it makes no difference.
Obviously this is not good! Does anyone have any idea what's going on and how to make it stop deleting my NanDroid Backups please?
Thank You!!!
TTYL

Hi,
I figured out what this was. For some reason with MM, when you run "Corpse Finder" in SD Maid, it sees the folder with the NanDroid Backups (Recovery app irrelevant) as not being tied to an installed app (i.e., data from an app, but the app is no longer present) and therefore something that's just taking up space.
I just used a "Global Exclusion" in the apps' "Explorer" mode. But the app has since been updated to handle this and not delete them.
TTYL

Installed TWRP 3.1.0 on my XT1096 and get "not enough space" errors

I installed TWRP 3.1.0 on my XT1096 and everything went fine. I got the mismatched partition size error in fastboot but it still worked. I booted into TWRP directly from fastboot after flashing TWRP. It asks me it I wanted to modify my system so TWRP wouldn't keep getting written over on boot so I had TWRP modify my system so it doesn't happen. I thought okay cool my recovery flash went through fine and went to boot back into the system. Before I booted back into the system TWRP made me aware I had no root access and asked If I wanted to install the SuperSU script, which I did. The script finished with no issue and my phone rebooted. I went into my app drawer and finished setting up SuperSU by downloading the GUI from the Play Store and then I downloaded TitanBackup so I could backup my apps in between switching ROMs. The first hint of my issue was with TitanBackup when I tried to make a backup of my user apps. Titan errored out after backing up the first app and left me with an insufficient space error. I thought that was weird and figured maybe the app just was not compatible with my device for some odd reason. Next I booted back into TWRP to try and do a nandroid backup. When I did the backup I got the same error, saying I did not have enough space available. I booted back up into the system and unrooted my device through the "permanent unroot" option in SuperSU thinking maybe it did something weird to the filesystem by some chance, booted back into TWRP and still got the same not enough space error trying to do a backup. Can anyone help me out with this issue. I am completely new to the device, I just got it yesterday so there is barely anything on it. Any help would be greatly appreciated. Thanks

It sounds to me like you're out of space... If you go to Settings > Storage how much do you have and what is taking it all up?

xKroniK13x said:
It sounds to me like you're out of space... If you go to Settings > Storage how much do you have and what is taking it all up?
Click to expand...
Click to collapse
I got this phone off eBay so this may be something sketchy but. It says I have 10.33gb total in storage available (purchased 16 gb model) to use with user data. Apps is taking up 3.70gb of that and I have 3.96gb of space free. Is that not enough?