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
Related
As rooting has become so easy these days I am considering to try custom roms (as many hv done lately). I hv read alot since the root with unlocking the bootloader method came out. I am still on stock FRF91 and I'd like to keep my apps and data intact. CM6-RC3 has just released and I m so tempted to try!
Here is the proposed routine:
"Originally Posted by cicrockets"
0. Download the CM6-RC3 ROM with the gapps and put them on SD Card.
1. Plug in the power cable and root using the 1-click root.
2. Back up apps and data with Titanium Backup / MyBackupPro (which is better?)
3. Search for ROM Manager on Market and Install
4. Click the "Flash ClockworkMod Recovery" and wait until the progress bar is finished.
5. Reboot and do a Nandroid backup.
6. Open ROM Manager and "Install ROM from SD Card".
7. Add Zip:
i) update-cm-6.0.0-N1-RC3-signed.zip
ii) gapps-hdpi-20100814-signed.zip
8. When it prompts, choose to backup before flashing and give the backup a name like "Stock N1 Rooted". Also choose to clear data and dalvik-cache.
9. Wait. It'll reboot and go into the clockwork recovery and automatically queue and flash the two zips. Keep waiting until it reboots again.
At this point the phone should hv booted into CM6. Should I do the restore from the backup apps immediately? Or should I wait for 10-15min market sync?
My major concern will be the data. Is there any problem with the above routine? Please bear with me
Technically that is the way to do it. But some people say that they get issues when restoring titanium backups for certain apps and data. So keep that in mind.
Yeah I read about that too. They said it can be fixed by doing an advanced restore, right? Will u recommend MyBackUpPro instead?
Thanks!
I rooted my hero using the 1 click root from the market. I then used rom manager to make a back up image, then flashed cyanogenmod 7.0.2 on it. There was no Market, my home button didnt work, and a few other quirks so I decided to go back to my original os. I clicked on the manage and restore in rom manager. It went thru the process and said restore complete. when it boots up it has overlayed images, and says "the application Settings(process.com.android.settings)has stopped unexpectedly.FC. As i go thru the set up, many of they options are greyed out and not accessable, then when i get to "finish setup" it FC's and says" the application Setup(process.com.htc.android.htcsetupwizard)has stopped unexpectedly. Then i get a black screen. Just wondering if I can get a good Back up image from someone to put on my sd card, then do a restore? I am pretty noob at all this, so any help would be greatly appreciated!!!!!
Mmhmm...first, 1 click bad, second, rom manager...worse in the wrong hands...
Why don't you download the gapps and put it on the root of your sdcard and then flash it after the 7.0.2 and then you'll be ok I'm sure if you take a little time to figure out you may be the only person that can fix your issue. By that, what I mean is in the install steps I'd bet it mentions to install gapps and if it doesn't let me know and I'll get the op to add that step.
As for all your messed up permissions try running fix permissions in rom manager if you can get there.
~maybe I set it too high...
i tried that first but coulnt get it to work, so i downloaded the rom directly from rom manager. The only thing i can do on the phone now is thru clockworkMod recovery
You can do fix permission in cwm also, I think under advanced. Just whatever you do, do NOT format recovery or misc if those options are in your recovery.
If you're in recovery though you're in the right place to flash. It's just
Wipe data /factory reset
Advanced -> wipe dalvik cache
Back
Install zip from sdcard and choose the7.0.2 zip and then thesame thing with gapps.
Reboot system
Edit, you could also just try to restore again from cwm. I'm assuming it holds the backup.
~maybe I set it too high...
ok, im off to bed...i will try this in the morning and post my status, thanks for your help so far
Did you ever wipe between installations and flashes? I always play it safe and wipe boot, cache, data, system and dalvik cache when I am flashing different ROMs and when restoring. Try going back into recovery and wipe what I posted and then restore your backup.
Sent from my HERO200 using XDA Premium App
I couldnt wait, I had to try it....YOU ARE ABSOLUTELY AWESOME!!!!!!!!!!!! Thank you so very much. I already had Rocksteady and Gapps downloaded on my comp, so i put those on the sd, followed your steps and BAMM! Works great! I can not thank you enough!
I have Samsung i897 Captivate (i9000) with SlimICS 4.1.1 Cyanogenmod installed.
Yesterday morning I've found, that my phone is repeatedly show me boot screen (video on boot with many blinking pieces/elements colors shown to me), but did not load an Android at all. I've tried to reboot the phone (with battery eject), but nothing changes: phone shows start-up animations repeatedly.
Last my action evening before was setting alarm (usual task that I've done for one year probably). Dont know what reason to reboot was, maybe no free space available, but dont sure. Before this problem with load I have no problems with phone at all.
I have Clockworkmod installed, but there's no options to boot an Android in safe mode or some similar options. I could get access to the internal phone memory, but not for system partitions. I've tried to wipe dalvik/cache, fix permissions, but no changes at boot.
So could you gents help me to get access to the filesystem: I have memo's & uncynchronised contacts & SMS, which I would like to save before do anything. I know how to reinstall the system (I have backup for it, but not for contacts & memo's).
Thanks.
kalabazoo said:
I have Samsung i897 Captivate (i9000) with SlimICS 4.1.1 Cyanogenmod installed.
Yesterday morning I've found, that my phone is repeatedly show me boot screen (video on boot with many blinking pieces/elements colors shown to me), but did not load an Android at all. I've tried to reboot the phone (with battery eject), but nothing changes: phone shows start-up animations repeatedly.
Last my action evening before was setting alarm (usual task that I've done for one year probably). Dont know what reason to reboot was, maybe no free space available, but dont sure. Before this problem with load I have no problems with phone at all.
I have Clockworkmod installed, but there's no options to boot an Android in safe mode or some similar options. I could get access to the internal phone memory, but not for system partitions. I've tried to wipe dalvik/cache, fix permissions, but no changes at boot.
So could you gents help me to get access to the filesystem: I have memo's & uncynchronised contacts & SMS, which I would like to save before do anything. I know how to reinstall the system (I have backup for it, but not for contacts & memo's).
Thanks.
Click to expand...
Click to collapse
The I9000 and the I897 are 2 different phones. I9000 is the international version of the Captivate, therefor, if you flashed the I9000 bootloaders on a I897 Captivate, you'll have distorted colors/screen.
What exactly was done to the phone before this happened?
Pardon, I have AT&T i897 Captivate phone. I did not flashed, nor updated phone, nothing similar, that could affect phone booting process. Just set an alarm (default, from Clocks), then go sleep. In morning found that my phone stuck in boot process - it show boot-up animation but don't load OS.
kalabazoo said:
Pardon, I have AT&T i897 Captivate phone. I did not flashed, nor updated phone, nothing similar, that could affect phone booting process. Just set an alarm (default, from Clocks), then go sleep. In morning found that my phone stuck in boot process - it show boot-up animation but don't load OS.
Click to expand...
Click to collapse
Have you tried re-flashing the ROM (Without factory reset)? Wipe cache and dalvik.
BWolf56 said:
Have you tried re-flashing the ROM (Without factory reset)?
Click to expand...
Click to collapse
No, I'm no so clean understand reflashing process, so worry to lost my data (I know that my contacts lie here - /data/data/com.android.providers.contacts , but can't found where memo's saved). I could choose "Restore /system" from
"Backup & Resore -> Advanced" in CWM, you mean this?
BWolf56 said:
Wipe cache and dalvik.
Click to expand...
Click to collapse
Yes, did it, but no changes at boot at all (wait there >10 minutes).
kalabazoo said:
No, I'm no so clean understand reflashing process, so worry to lost my data (I know that my contacts lie here - /data/data/com.android.providers.contacts , but can't found where memo's saved). I could choose "Restore /system" from
"Backup & Resore -> Advanced" in CWM, you mean this?
Yes, did it, but no changes at boot at all (wait there >10 minutes).
Click to expand...
Click to collapse
Reflashing your ROM won't touch your data as long as you don't wipe/factory reset. It's what we call a dirty flash, you just wipe cache/dalvik and flash your ROM again with the Gapps.
Thank you for the way to resolve the problem. Spend some time to understand the process of reflashing. Now I collected all files (bootloader, ROM, essentials, gapps and so on of my actual setup) and ready to reflash it with Heimdall.
But still have a question: is there any possibilities to get access to filesystem (for maybe just copy all files from system partitions into Big Brother) before take action in my case?
Will I get access to my contacts & memo's after reflashing? As I understand, if I reflash phone, /data & /datadata partitions (as part of freshy ROM reinstall) will be touched too, then I lost as minumum link to the Wizard Memo (and I'm not sure that installing it from Google Play will restore access to my memo's).
As you could realise, I have no actual backup of my data, so asking maybe dumb questions (
Could I simple use Clockwork's mod option "Restore /system" & "Restore /data" (as I have it in almost fresh backup - 2 months ago)? Will it be analogue to reflashing? Or it revert /system and /data to the stage when it was make, with contacts, programs and so on with 2 months ago state, not current?
kalabazoo said:
Thank you for the way to resolve the problem. Spend some time to understand the process of reflashing. Now I collected all files (bootloader, ROM, essentials, gapps and so on of my actual setup) and ready to reflash it with Heimdall.
But still have a question: is there any possibilities to get access to filesystem (for maybe just copy all files from system partitions into Big Brother) before take action in my case?
Will I get access to my contacts & memo's after reflashing? As I understand, if I reflash phone, /data & /datadata partitions (as part of freshy ROM reinstall) will be touched too, then I lost as minumum link to the Wizard Memo (and I'm not sure that installing it from Google Play will restore access to my memo's).
As you could realise, I have no actual backup of my data, so asking maybe dumb questions (
Could I simple use Clockwork's mod option "Restore /system" & "Restore /data" (as I have it in almost fresh backup - 2 months ago)? Will it be analogue to reflashing? Or it revert /system and /data to the stage when it was make, with contacts, programs and so on with 2 months ago state, not current?
Click to expand...
Click to collapse
I guess i wasn't so clear. What I mean by reflashing is to simply get in recovery mode and reflashing RemICS and their Gapps. Not to start fresh with stock.
Sent from my SGH-I747 using xda app-developers app
You explained well, errors on my side Resolved this issue with copying all data from filesystem, then reflashing with fresh slimrom . For those who fall into same situation: you could get access to filesystem of your phone trough ADB tool, and just copy sensible data to another partition/SD/device. See QtADB program also, very friendly for that.
I have been getting error messages ("unfortunately, android.process.acore has stopped") and have concluded that I need to ROM my phone.
See post here http://androidforums.com/huawei-ide...ss-acore-has-stopped-working.html#post5803220
and here http://forum.xda-developers.com/showthread.php?t=2227732&goto=newpost
The problem is that I can't even run Titanium Backup now (it immediately crashes) and the Titanium directory is empty (meaning it had not been running nightly backups as I thought it was).
What should I do now. It occurred to me that I could ROM without "factory reset" and "wipe cache" just to try running Titanium Backup. If that works then I could ROM with "factory reset" and "wipe cache".
Does that make sense? Do you have a better suggestion?
Galaxy S GT-I9000
Android 4.1.2
Cyanogen Mod 10.0.0
I managed to copy all the files off my phone (internal SD card and External SD card). It looks like I won't be able to do a Titanium Backup. Will these files be helpful in restoring data.
unfortunately android keyboard aosp has stopped
No this is really frustrating. I did Factory Reset and Wipe Cache.
I went into Recovery and Rom'ed CyanogenMod (cm-10.0.0-galaxysmtd.zip) and GApps (http://goo.im/gapps/gapps-jb-20130301-signed.zip).
Now when I try to use my phone I get
"unfortunately android keyboard aosp has stopped".
I'm really stuck! :-O
webmanoffesto said:
unfortunately android keyboard aosp has stopped
No this is really frustrating. I did Factory Reset and Wipe Cache.
I went into Recovery and Rom'ed CyanogenMod (cm-10.0.0-galaxysmtd.zip) and GApps (http://goo.im/gapps/gapps-jb-20130301-signed.zip).
Now when I try to use my phone I get
"unfortunately android keyboard aosp has stopped".
I'm really stuck! :-O
Click to expand...
Click to collapse
I'm sorry I have read just now that you did reset all because we could try something, but given your current situation I advise you to be born again smartphone.
then:
Factory Reset, Wipe Cache and Wipe dalwik
with odin install GINGERBREAD (THE LAST STOCK FOR YOUR COUNTRY)
root with cf-root
now from the recovery install the ROM of your choice
This is the only way to definitely eliminate all the problems of your device
quack75 said:
with odin install GINGERBREAD (THE LAST STOCK FOR YOUR COUNTRY)
Click to expand...
Click to collapse
Can you give me some more specific guidance on how to do that for a GT-I9000. I opened up Odin and did some Google searching but I still don't understand what to do next.
Do you mean this?
Instructions - ODIN (long)
- Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Unzip the attached CF-Root-xxx-vX.X.zip
- (USB) Disconnect your phone from your computer
- Start ODIN
- Click the PDA button, and select CF-Root-xxx-vX.X.tar
>->->-[* Question: does that refer to CF-Root-SGS2_XX_OXA_KPA-v5.2-CWM5.zip which is at http://download.chainfire.eu/133/ *]
- Put your phone in download mode
- (USB) Connect the phone to your computer
- Make sure repartition is NOT checked
- Click the START button
- Wait for the phone to reboot
- Done (if it took you more than 30 seconds, you need practise!)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1103399
How do I "Put [my] phone in download mode"?
Does this just mean that I can copy files from my PC to a directory on my phone?
I can get into Recovery.
I finally found the "Recovery / Advanced / Wipe Dalvik Cache" fixed the ASOP Keyboard problem.
So I rooted my phone and flashedTWRP. What's my next step to flashing TEKXodus?
I'm confused about steps on the guide on XDA.
Do I just go into recovery and install the whole .zip file? Or do I install individuals mods?
Thank you.
Make sure you download the correct version depending on if you have 910T or 910T3.
Follow the steps in this thread for rooting and installing TWRP:
910T:
http://forum.xda-developers.com/not...sy-steps-stock-odin-n910tuvu1anih-cf-t2903733
910T3:
http://forum.xda-developers.com/not...y-steps-n910t3-dofc-dog1-how-to-root-t3177225
MAKE A BACKUP OF YOUR CURRENT STOCK ROM WITH ROOT!!! Can not stress this enough. If you need to go back to stock, and you download an Odin file from a shady site, you have no idea what you're putting on your phone. It's sooo much easier to just backup your stock. Make sure ALL options are checked under backup. Save this file on your PC or external SD card just to be safe. I always keep a backup copy on my PC.
Put the ROM zip file on your phone, either internal or external SD card. Some recommend internal SD only, but I have had 0 issues flashing from an external SD card. I guess if you use a cheap card you may have issues, but if you have a name brand class 10 you should be fine.
Do a full wipe.... When you are in TWRP, choose wipe, then factory reset. Then goto advanced and check system and data and wipe again.
In TWRP choose install then navigate to the folder that has the ROM zip file... and install.
Do another factory reset wipe (do not wipe system this time, just goto the wipe screen, and default swipe is factory reset.
Boot your phone, and LEAVE IT ALONE. First boot will take a LONG time. 10 to 15 minutes sometimes. Once you get to the setup screen... LET IT SIT for another 5 or 1 0 minutes.
Complete your setup process as you normally would do. There will be a popup saying it needs to reboot to complete some actions. Go ahead and reboot.
Once everything is installed and working as it should you can continue on.
Keep in mind there are some mods that come pre-attached to the TEKXodus rom. To flash these, boot into recovery, goto Mount -> check SYSTEM. Goto Install, select "Up a folder" to get to the root folder, then goto System then Mods. There you can play around with different mods. The Note 5 screen off memo.apk will just need to be installed like you would a normal downloaded APK and is not flashed. You only flash the .zip files.
BEFORE YOU START MESSING WITH DPI settings (if that's your thing) make sure you do a backup first. Some DPI settings will cause force close on touchwiz, and you'll be stuck unless you use another launcher. Basically before you install Xposed, any Xposed module, or play around with the build.prop file make a backup first. Can NOT stress this enough. I'm constantly tweaking things, and will make a backup every 3 days just out of habit. Delete your previous backup after creating a new one as the files are quite large (5GB+ depending on what you have installed). ALWAYS keep your stock backup that you originally made.
I do not recommend using the TEKXodus Rom's Tweaks for changing DPI settings. This basically just edits the build.prop and makes a global DPI change. There are SEVERAL samsung apps that need to be changed back to 640 DPI (the stock setting) or they will force close. It is MUCH better to install the Xposed framework, and then install the "App Settings" module and change the DPI on a per app basis. Personally I changed "System UI" only (not android system) to 420DPI. This will give you a smaller notification bar but not mess with alot of the other apps. You can then change the DPI settings using App Settings on a per apk basis. Some I like at 420, some at 480, some even in the 300s. After changing a setting you will have to reboot to see the change. You used to be able to just kill the app and then re-open but that doesn't seem to work anymore.
If you DO decide to change the global DPI setting, MAKE SURE you install xposed and App Settings first, then read this thread to change all the nescessary apps back to 640 stock DPI or you will have issues.
http://forum.xda-developers.com/not...anging-note-4-dpi-settings-to-change-t2923408
If you need anything clarified let me know, typed this up in a bit of a rush at work.
Don't forget to hit that Thanks button if I helped
So I followed the instructions above, however, after the flash I just hit reboot instead of doing another factory reset wipe and the phone never booted after the reboot. So I went back into TWRP and restored.
What did I do wrong? Was it just the fact that I didn't do the factory reset after installing the new ROM?
More than likely yes that's what caused the error.
Do this just to be safe.
Boot into TWRP.
Do a FULL wipe (advanced wipe) and wipe System, Data, Cache, Dalvik, etc)
Re-Install TEKXodus
Do a "Factory Reset Wipe" BEFORE booting. Literally as soon as it gets done flashing, goto TWRP wipe, and just do the default factory reset (do not wipe system this time)
Then you can reboot.
The error I end up with was the kernal is not seandroid error. I'm guessing I picked the wrong ROM install?