Related
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!
Hallo,
i have a problem with updating cm 10.1 to 10.2 on my i9000. Like i say, i had allready cm 10.1 and prior to that 10.0 and helly bean. Till now everything was fine and every update was OK. I have allready root rights.
Now i tried to flash cm 10.2 like that;
1.
wipe data/factory reset
wipe cache partition
wipe dalvic cache
- flash cm-10.2-20130824-NIGHTLY-galaxysmtd.zip - 2 times
- flash gapps 10.2.x 20130813
- reboot system now
After reboot, i'm in the welcome modus - i choose German - then start - then i can choose the connection WLAN or skip with data. In this part i get allready an error massage "com.google.android.gsf.login" and "unfurnatly google account manager was shut down". After that i'm back again in the choose-connection area. After chosing WLAN or skip and use data, i always get the above mentioned message.
Restore 10.1 again
2.
like above, but extra mounts and storage - format /system
- Result like 1
3.
Just update from 10.1 to 10.2 with CWM, without wipe data/factory reset - wipe cache partition - wipe dalvic cache.
- Result 4.3 is on my mobile, but there ist still the error massage from above.
4.
like 3, but i deleted the Google account in 10.1. Just uodated to 10.2 without wiping.
- Result -> no error massages, but i can't add google account. I clik on add account - google -> but nothing happen.
I don't know what to do. Do somebody have any idea? Where is my oult?
one-dimon said:
wipe data/factory reset
wipe cache partition
wipe dalvic cache
- flash cm-10.2-20130824-NIGHTLY-galaxysmtd.zip - 2 times
- flash gapps 10.2.x 20130813
- reboot system now
Where is my foult?
Click to expand...
Click to collapse
Your foult is that you didn't read pawitp's opening post carefully. All steps untill gapps were fine, then after gapps you should have remained in CWM recovery and go to advanced restore and restore your /data from last nandroid backup from cm10.1, it works perfectly well.
I would advice you not to install 20130824 build anymore as it has some serious bugs (I run it in my i9000 and it works perfectly fine but some people had total re-formatting ofntheninternal SD card and data lost) but wait now for just short, any moment nightly 20130827 will be uploaded. The bugs are fixed there.
Then you can repeat proceeding once again as above and accomplish with /data restore. Then it should work fine again
Ok, i try it
Last question before i try, i have to restore just /data, wich backup do i have to do, full backup or just /data?
Thanx a lot
one-dimon said:
Last question before i try, i have to restore just /data, wich backup do i have to do, full backup or just /data?
Click to expand...
Click to collapse
OK, now the new nightly build is there, CM10.2 20130827
Do all your steps as above (download zip, go to recovery mode, wipe data/factory reset, wipe cache, wipe dalvik cache under "advanced", install 20130827 zip, stop here) now new:
if your last installed build is 10.2 you have already installed gapps for CM10.2 so you can skip re-installing them again
now go to "advanced restore" and choose your last nandroid backup of the CM10.1, where your google account was still working fine
choose now from your last nandroid file the option: "restore /data"
after restore is finished go back to main menu and reboot the system
Unless if you have formatted your SD card meanwhile, all your data will be back like they were in the CM10.1 (also your google account) and your new CM10.2 will work fine.
For thanking, it is common in this forum to click on "thanks" button left beyond all the posts which you find to be helpful
Hy, i tried what you said. I restored 10.1 before it
*
wipe data / factory reset - wipe cache - advanced .. wipe dalvic cache*- install 10.2
then - flash gapps for 10.2
then - restore just data
reboot system
*
4.3 is on my mobile, google account seems to be OK. But then i recognized, that my Contacts, Keep, Google+ and some other points doesn't synchronize. I've tried flash gapps again, then restore data -> error massage "google account closed"
*
My next step was to do above mentioned again - same error massage
*
So, i do it again. After wipe data / factory reset - wipe cache a.s.o. i had a look in my storage/sdcard0. It was full of old data, so i extra formated /system and formated /storage/sdcard0. After that i flashed 10.2 and gapps again and restored data. I receive the same sh.. error again and google account doesn't work.
*
Now i restored 10.1 again completely
*
Any idea?
one-dimon said:
....Now i restored 10.1 again completely....
Click to expand...
Click to collapse
Did you enable contacts sync in your accounts? Other thing you can do is to export all your contacts (in "people" ) as vfc data and after the upgrade import it from your SD card. I did that as I don't like google sync functions (for having few accounts) so I only enabled sync for the apps.
Other great thing is to use free app "SMS backup&restore" and "Call logs backup&restore" (by the same developer) from play store. The apps work for any android version and backup data is compatible to restore as well
Try to post in the development thread of nightly cm10.2 for i9000 or read through, I think also somebody else reported problems with google account, maybe it is solved why it happened.
BTW: for next flashing don't use nightly 20130827 anymore as the new 20130828 is out and it has many bug fixes
______________________________________
Sent from GT-P5110 powered by CM 10.2
Hy, i'm again. I try it with the newest cm, with the same result. I flashed exactly like the developer said. No error message, but play store, contacts and some other things don't work.
I would like to post in the development Center, but I am a to young forum member.
Maybe you could post for me my problem or the link to this posts?
one-dimon said:
Hy, i'm again. I try it with the newest cm, with the same result. I flashed exactly like the developer said. No error message, but play store, contacts and some other things don't work.
I would like to post in the development Center, but I am a to young forum member.
Maybe you could post for me my problem or the link to this posts?
Click to expand...
Click to collapse
Just one question: did you flash the gapps for 4.3 as well? Developer pawitp is a genious person and he doesn't mention it anymore in his first posts (he thinks that everybody knows it.....)
If you didn't, you can do it later as well, just download them and install zip in recovery mode..... Sorry if it doesn't work. Then would be better to wait untilmstable version is released. CM 10.2 works in my i9000 amazing, but another people report bugs.
Of course, i flashed gapps for 4.3. Some user posted in developement thread, that they solved the problem with the google account with Titanium Backup. They restored data with TB. Do you know what i have to backup / restore: user apps & data & system data?
*
Could you*post a question fpr me in the developement thread if this problem is known to the developers and if they have a resolution? Maybe they are allready working on it and solve the problem in next nightlys?
one-dimon said:
Of course, i flashed gapps for 4.3. Some user posted in developement thread, that they solved the problem with the google account with Titanium Backup. They restored data with TB. Do you know what i have to backup / restore: user apps & data & system data?
Click to expand...
Click to collapse
No, mate, if you meant CWM recovery. I would also use Titanium backup app for that, there can't go so wrong.
Could you*post a question fpr me in the developement thread if this problem is known to the developers and if they have a resolution? Maybe they are allready working on it and solve the problem in next nightlys?
Click to expand...
Click to collapse
you have no idea how little free time I have. But you're already on 5 posts, just five more and you will be able to post the questions in development threads. It is anyway better that you describe what the problem is. I think I saw in CM10.2 thread yesterday that the developer pawitp works on that.
EDIT: BTW, restoring /data from nandroid backup made with CM10.1x under CWM recovery -->advanced restore is possible without problems. But I think we have mentioned that already in last posts...
OK, I can understand you.
What do I have to do first: flash gapps or restore /data?
have you checked that dataprotection for these apps is not enabled?
one-dimon said:
OK, I can understand you.
What do I have to do first: flash gapps or restore /data?
Click to expand...
Click to collapse
I've posted your question and left link to this thread in the CM10.2 development topic. Hope somebody will answer soon.
If your Google account worked well in CM10.1x, I would say you should try this way:
download the newest CM10.2 nightly zip (20130830) directly here: http://get.cm/get/amd
download Google Apps zip for Android 4.3
run CWM recovery mode
try option "install zip" and don't install yet, just check if your zip files are visible for the CWM recovery in the folder where you saved them
return to main menu and wipe data/factory reset
wipe cache
wipe dalvik cache under "advanced"
install zip CM10.2 nightly
install GApps for 4.3
go to "advanced restore" and choose your last nandroid backup file made by CM10.1 build where your Google account worked well
now choose (from that nandroid backup file) the option "restore /data"
after your data are restored, go back to the main menu and reboot the system
Let me know if it worked. Please quote at least little bit of my text (click "reply" beyond my post) so I will get the notification that you've quoted me, otherwise I don't see when you answer
p.s. good point by @Marvi70 just one post before (this one) mine
Marvi70 said:
have you checked that dataprotection for these apps is not enabled?
Click to expand...
Click to collapse
What do you mean? How can I check it?
one-dimon said:
What do you mean? How can I check it?
Click to expand...
Click to collapse
in settings -> apps, in the app property of those apps check if dataprotection is enabled (no access to private data). When yes disable it.
Marvi70 said:
Datatings -> apps, in the app property of those apps check if dataprotection is enabled (no access to private data). When yes disable it.
Click to expand...
Click to collapse
OK, I checked all apps, also system apps. Data protection is disabled everywhere.
tetakpatak said:
I've posted your question and left link to this thread in the CM10.2 development topic. Hope somebody will answer soon.
If your Google account worked well in CM10.1x, I would say you should try this way:
download the newest CM10.2 nightly zip (20130830) directly here: http://get.cm/get/amd
download Google Apps zip for Android 4.3
run CWM recovery mode
try option "install zip" and don't install yet, just check if your zip files are visible for the CWM recovery in the folder where you saved them
return to main menu and wipe data/factory reset
wipe cache
wipe dalvik cache under "advanced"
install zip CM10.2 nightly
install GApps for 4.3
go to "advanced restore" and choose your last nandroid backup file made by CM10.1 build where your Google account worked well
now choose (from that nandroid backup file) the option "restore /data"
after your data are restored, go back to the main menu and reboot the system
Let me know if it worked. Please quote at least little bit of my text (click "reply" beyond my post) so I will get the notification that you've quoted me, otherwise I don't see when you answer
p.s. good point by @Marvi70 just one post before (this one) mine
Click to expand...
Click to collapse
Hy, i'm again. I've just tested to flash another ROM. It was slimbean. Everything works fine, there are no problems with gapps. I thing there is a bug in cm 10.2.
one-dimon said:
Hy, i'm again. I've just tested to flash another ROM. It was slimbean. Everything works fine, there are no problems with gapps. I thing there is a bug in cm 10.2.
Click to expand...
Click to collapse
Good to know, thanks for info! Congratulations also CM10.2 will soon be cool, the devs are now fixing the bugs on daily basis
tetakpatak said:
Good to know, thanks for info! Congratulations also CM10.2 will soon be cool, the devs are now fixing the bugs on daily basis
Click to expand...
Click to collapse
I hope so, i allready use cm a long time and i was a happy user till 10.1. I think if my prob. will be fixed, i'll switch to cm again
one-dimon said:
Of course, i flashed gapps for 4.3. Some user posted in developement thread, that they solved the problem with the google account with Titanium Backup. They restored data with TB. Do you know what i have to backup / restore: user apps & data & system data?
Click to expand...
Click to collapse
BTW, after your post about Titanium Backup I've tried indeed to restore data only from my old backup of Angry Birds app, it went perfectly well
Backup file was done with rooted Froyo 2.2 and restored in CyanogenMod 10.2
Before importing the data saved in different ROM, I used the settings exactly like described on the website of Titanium. I've checked again CM development posts about Titanium backup and they talk indeed about the one shouldn't restore whole apps.... but data only seems not to be a problem!
Big thanks, mate!
Hello
I have the problem that I cannot update my i9000 from CyanogenMod 10.1.3 to 10.2.0. After the update, Cyanogenmod doesn’t start anymore. It gets stuck at the boot animation: The blue CyanogenMod-mascot within the round rotating arrow. I waited 15min for it to start, then I left the phone for 2h and it still didn’t start.
I did the update as follows:
First, I tried to update with the automatic updater from CyanogenMod, but that didn’t work. It aborted and restarted CyanogenMod 10.1.3.
So I tried it manually with ClockworkMod (v6.0.3.6):
- wipe data / factory reset
- wipe cache partition
- advanced -> wipe dalvik cache
This message was shown: E:unknown volume for path [/sd-ext]
Dalvik cache wiped.
- install zip -> choose zip from sdcard -> cm-10.2.0-RC1-galaxysmtd.zip
It aborted and the following message was shown:
This ROM uses an incompatible partition layout
Your /data will be wiped upon installation
Run this update.zip again to confirm install
- Did it again: install zip -> choose zip from sdcard -> cm-10.2.0-RC1-galaxysmtd.zip
Now the zip-file was installed completely.
- reboot system now
The result was that the phone got stuck at the boot animation.
Remarks:
- I didn’t do a backup of apps and data, because I didn’t have important data on the phone.
- I didn’t have root-rights in CM 10.1.3.
I tried it again with the stable version of CM 10.2.0. I didn’t have to install the zip twice anymore, but the phone still gets stuck at the boot animation. Wiping cache and dalvik cache again didn’t make it start.
I can still boot into ClockworkMod and it was also possible to go back to CM 10.1.3. Just CM 10.2 doesn’t start up.
What do I have to do to make CM 10.2 start up?
Thank you very much for your help.
Best regards
Tomy
@Tomy_Delmar
Tomy, CyanogenMod is already custom ROM, there is always root access on it
Try it this way:
download Gapps for CM10.2x (Android 4.3.x) and paste them on your external SD card
put the card in your phone
run it in recovery mode
wipe cache and dalvik cache
flash Gapps for 4.3
wipe again cache and dalvik cache.
reboot
Post if it worked.
Tomy_Delmar said:
Hello
I have the problem that I cannot update my i9000 from CyanogenMod 10.1.3 to 10.2.0. After the update, Cyanogenmod doesn’t start anymore. It gets stuck at the boot animation: The blue CyanogenMod-mascot within the round rotating arrow. I waited 15min for it to start, then I left the phone for 2h and it still didn’t start.
I did the update as follows:
First, I tried to update with the automatic updater from CyanogenMod, but that didn’t work. It aborted and restarted CyanogenMod 10.1.3.
So I tried it manually with ClockworkMod (v6.0.3.6):
- wipe data / factory reset
- wipe cache partition
- advanced -> wipe dalvik cache
This message was shown: E:unknown volume for path [/sd-ext]
Dalvik cache wiped.
- install zip -> choose zip from sdcard -> cm-10.2.0-RC1-galaxysmtd.zip
It aborted and the following message was shown:
This ROM uses an incompatible partition layout
Your /data will be wiped upon installation
Run this update.zip again to confirm install
- Did it again: install zip -> choose zip from sdcard -> cm-10.2.0-RC1-galaxysmtd.zip
Now the zip-file was installed completely.
- reboot system now
The result was that the phone got stuck at the boot animation.
Remarks:
- I didn’t do a backup of apps and data, because I didn’t have important data on the phone.
- I didn’t have root-rights in CM 10.1.3.
I tried it again with the stable version of CM 10.2.0. I didn’t have to install the zip twice anymore, but the phone still gets stuck at the boot animation. Wiping cache and dalvik cache again didn’t make it start.
I can still boot into ClockworkMod and it was also possible to go back to CM 10.1.3. Just CM 10.2 doesn’t start up.
What do I have to do to make CM 10.2 start up?
Thank you very much for your help.
Best regards
Tomy
Click to expand...
Click to collapse
As the partition layout is different in cm10.2, you should flash it at least 2 times and wait for system to be stable for about 15-20 minutes
Tetakpatak and Rohitdahiya, thanks for the reply and advice!
In my previous post, I forgot to mention that I installed CyanogenMod without the Gapps. I’d like to try if an android-phone without the Gapps is still useful. Somehow I don’t like the data-collecting-mania of Google.
I tried again the update from CM 10.1.3 to 10.2:
- I downloaded cm-10.2.0-galaxysmtd.zip again and copied it to the internal SD-card of the phone.
- Restarted the phone into ClockworkMod recovery.
- wipe data / factory reset
- wipe cache partition
- wipe dalvik cache
- install zip -> choose zip from sdcard -> cm-10.2.0-galaxysmtd.zip
- install zip -> choose zip from sdcard -> cm-10.2.0-galaxysmtd.zip
(Did it twice. Don’t know if necessary.)
Didn’t install Gapps.
- wipe cache partition
- wipe dalvik cache
- reboot system now
Unfortunately CM still gets stuck at the boot animation. The arrow has been rotating for over an hour now.
To my knowledge the Gapps are not mandatorily required to install CM. I could install CM 10.1.3 without the Gapps without any problems.
Could a full-wipe solve my problem?
ClockworkMod -> mounts and storage -> format /system …?
I have never done this before.
Or is there something else I can do?
Regards
Tomy
Tomy_Delmar said:
Tetakpatak and Rohitdahiya, thanks for the reply and advice!
In my previous post, I forgot to mention that I installed CyanogenMod without the Gapps. I’d like to try if an android-phone without the Gapps is still useful. Somehow I don’t like the data-collecting-mania of Google.
I tried again the update from CM 10.1.3 to 10.2:
- I downloaded cm-10.2.0-galaxysmtd.zip again and copied it to the internal SD-card of the phone.
- Restarted the phone into ClockworkMod recovery.
- wipe data / factory reset
- wipe cache partition
- wipe dalvik cache
- install zip -> choose zip from sdcard -> cm-10.2.0-galaxysmtd.zip
- install zip -> choose zip from sdcard -> cm-10.2.0-galaxysmtd.zip
(Did it twice. Don’t know if necessary.)
Didn’t install Gapps.
- wipe cache partition
- wipe dalvik cache
- reboot system now
Unfortunately CM still gets stuck at the boot animation. The arrow has been rotating for over an hour now.
To my knowledge the Gapps are not mandatorily required to install CM. I could install CM 10.1.3 without the Gapps without any problems.
Could a full-wipe solve my problem?
ClockworkMod -> mounts and storage -> format /system …?
I have never done this before.
Or is there something else I can do?
Regards
Tomy
Click to expand...
Click to collapse
First of all, don't forget to quote the user whom you want to contact, because he don't get any notification until you quote. I was just checking around the questions and thus I saw this.
Sometimes, there is requirement of g-apps for the core system to be working ( Not sure in case of cm10.2). Try with g-apps (you may choose light package).
In my opinion, it should work. If not, try from the start ( flashing gingerbread with Odin with repartition ticked, then its root and finally cm10.2 from recovery)
Also make sure your handset is i9000 and you are using cm10.2 for the same.
And finally, All the best
CM doesn't neccesarily need Gapps to boot up. In fact most custom roms don't - they are still usable, just that everything Google-related doesn't work.
Its a bit odd seeing as how you've pretty much done what I would have done if I was installing CM to a Galaxy S. I can't think of any reason why it wouldn't work.
As far as I know as well, formatting /system is more of a last-resort method, not something you'd immediately do.
However, I had a similar problem installing a rom onto my tablet - different device, I know, but try this anyway and see if you get anywhere:
1.) Go back into recovery if its still bootlooping
2.) Wipe data, cache, Dalvik (and this is after you've flashed the CM10.2 zip twice like you did)
3.) Reboot device without flashing Gapps - this is to see if it boots up.
Let us know what happens.
Sent from my GT-P7510 using Tapatalk
Tomy_Delmar said:
In my previous post, I forgot to mention that I installed CyanogenMod without the Gapps. I’d like to try if an android-phone without the Gapps is still useful. Somehow I don’t like the data-collecting-mania of Google.
Click to expand...
Click to collapse
Tomy, now it is getting clear- of course, I tought you already had Gapps on your CM10.1.3 installed so in such case they would definitely need to be updated to 4.3
Yes, the ROM shouold work perfectly fine also without Gapps
Your workflow sounds correct, but just to make sure: after first attempt to flash CM10.2 build, there should be a warning that all your data will be wiped, right? After that you must again choose the option "install zip" and install CM10.2. It will work this time.
If it doesn't work, download again the CM10.2 zip as it may be corrupted file. BTW, I didn't like that build for several reasons and returned to RC version.
If nothing helps, flash back your CM10.1.3 and restore your nandroid backup if important files were there. If the downgrade won't work for different partition of the /system, use my unbricking guide and revert to stock, then to CM10.1.3, then to CM10.2.
Keep step by step on the guide if you use it, it has important points to control before flashing. Flashing with re-partition needs always a PIT file, or with other words: without that file re-partition option mustn't be checked. Doing it simply by clicking the re-partition (like @Rohitdahiya adviced you to) without a PIT file checked under "PIT" would brick your i9000.
Soryuu said:
However, I had a similar problem installing a rom onto my tablet - different device, I know, but try this anyway and see if you get anywhere:
1.) Go back into recovery if its still bootlooping
2.) Wipe data, cache, Dalvik (and this is after you've flashed the CM10.2 zip twice like you did)
3.) Reboot device without flashing Gapps - this is to see if it boots up.
Let us know what happens.
Click to expand...
Click to collapse
Unfortunately, Wiping data, cache and Dalvik cache again after I had flashed CM 10.2 didn’t make it start.
tetakpatak said:
Tomy, now it is getting clear- of course, I tought you already had Gapps on your CM10.1.3 installed so in such case they would definitely need to be updated to 4.3
Yes, the ROM shouold work perfectly fine also without Gapps
Your workflow sounds correct, but just to make sure: after first attempt to flash CM10.2 build, there should be a warning that all your data will be wiped, right? After that you must again choose the option "install zip" and install CM10.2. It will work this time.
If it doesn't work, download again the CM10.2 zip as it may be corrupted file. BTW, I didn't like that build for several reasons and returned to RC version.
If nothing helps, flash back your CM10.1.3 and restore your nandroid backup if important files were there. If the downgrade won't work for different partition of the /system, use my unbricking guide and revert to stock, then to CM10.1.3, then to CM10.2.
Keep step by step on the guide if you use it, it has important points to control before flashing. Flashing with re-partition needs always a PIT file, or with other words: without that file re-partition option mustn't be checked. Doing it simply by clicking the re-partition (like @Rohitdahiya adviced you to) without a PIT file checked under "PIT" would brick your i9000.
Click to expand...
Click to collapse
When I tried to flash CM 10.2 the first time – at that time RC1 was the newest version – I was asked to flash it a second time, which I did. To be precise, the following message was shown:
This ROM uses an incompatible partition layout
You /data will be wiped upon installation
Run this update.zip again to confirm install
This message hasn’t been shown again since then. I flashed CM 10.1.3 again and tried to flash 10.2 a second time, but the message wasn’t shown again.
Going back to CM 10.1.3 worked without any problem.
------------------------------------------
Now I have CM 10.2 on my phone and it starts normally
I flashed Stock-Android 2.3.6 with Odin (v1.82). Tetakpatak, thank you for the excellent guide and the video! As written in the guide, I used "s1_odin_20100512.pit" as PIT-file.
(I executed Odin on an old computer with Windows XP 32bit, as the guide says Odin 1.82 works better with Win XP.)
Then I installed CM 10.2 over Stock-Android 2.3.6. I followed the official instructions:
http://wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd?setlang=en
(I executed Heimdall on my new computer with Windows 7. Heimdall 1.4RC2 doesn’t work on Win XP. If one executes Odin and Heimdall on the same PC, I could imagine this could lead to confusion, because Odin needs the Samsung-USB-drivers and Heimdall needs WinUSB. I’m not sure if this really leads to problems. But one should keep that in mind.)
I didn’t flash CM 10.1.3 before 10.2, because I didn’t need to restore a nandroid backup previously made with CM 10.1.3. There were no important data on the phone.
Many thanks to all who gave me advice and helped my solving the problem!
Tomy
HELP MEEE
I put on TWRP 2.6.3.0 on my Nexus 5 (I used towerlroot succesfully) and i tried wiping as you should, i noticed i loaded an old twrp so i quickly powerd off my Nexus5. When i loaded, every app had a "Google play services has stopped" error and some would force close. I reloaded TWRP and tried to flash cyanogenmod and gapps, succelfully they installed. Now cyanogenmod is stuck in the boot animation and i dont know to update TWRP, HELPP PLEASSE!!!!
Pure_Android said:
I put on TWRP 2.6.3.0 on my Nexus 5 (I used towerlroot succesfully) and i tried wiping as you should, i noticed i loaded an old twrp so i quickly powerd off my Nexus5. When i loaded, every app had a "Google play services has stopped" error and some would force close. I reloaded TWRP and tried to flash cyanogenmod and gapps, succelfully they installed. Now cyanogenmod is stuck in the boot animation and i dont know to update TWRP, HELPP PLEASSE!!!!
Click to expand...
Click to collapse
This is the forum for the original Galaxy S, not the Nexus 5, sorry mate
However I think your problem can be fixed by doing a full data/cache wipe so it might be worth a shot
Flash Boot.Img. This might solve the bootloop!
I think, You just need to flash the boot.img (available in the Cynogen Bundle Zip Folder) after installing Cynogen Mod. Me too got stuck on the animation part for a long time. Then I found out this:
CyanogenMod builds for endeavoru currently do NOT support any bootloader version number below: HBOOT 1.28. As the device is S-ON (security-on bootloader), for a working installation you must extract the boot.img from the installer zip and run fastboot flash boot boot.img from fastboot mode.
Source: Cynogen Mod Wiki
Pure_Android said:
I put on TWRP 2.6.3.0 on my Nexus 5 (I used towerlroot succesfully) and i tried wiping as you should, i noticed i loaded an old twrp so i quickly powerd off my Nexus5. When i loaded, every app had a "Google play services has stopped" error and some would force close. I reloaded TWRP and tried to flash cyanogenmod and gapps, succelfully they installed. Now cyanogenmod is stuck in the boot animation and i dont know to update TWRP, HELPP PLEASSE!!!!
Click to expand...
Click to collapse
Which version of CyanogenMod are you using?
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?
Recently got a kindle fire 7" and wanted to root it and flash a rom onto it, but having troubles with that part.
Using this guide https://forum.xda-developers.com/amazon-fire/general/root-t3471289
Rom:
https://forum.xda-developers.com/amazon-fire/orig-development/rom-fire-nexus-rom-lmy49f-t3300714
Usb debugging/install from unknown sources/kingroot done
Process:
Stock firmware (5.3.1) after amazon recovery tool
Kingroot root
Supersu-me
Update su
Tried once with and without rebooting
Rootjunky super tool, installed google play store
Install Flashfire (from play store) ver. .55
Also tried with an apk file ^ (ver. .53)
Set up a wipe for (dalvik, system, 3rd party)
Tried with and without mounting
Crashes after and starts a boot loop going into the amazon logo only
I'm new in regards for rooting, sorry if I'm a bit slow with this.
Thanks in advance for the help!
Check the rom you downloaded is not corrupted, verify hash value. Store it on the tablet not an sd card when flashing.
Reboot the tablet after you install supersu and flashfire. Before you flash the rom, make sure you remove the usb cable.
Don't use auto mount. Make sure you follow the flashfire instructions below. Make sure to move wipe to top of the order !
Fresh installation from FireOS via FlashFire >= 0.55.1
- Click the Red + and choose 'Wipe'
- Ensure System data, 3rd party apps and Dalvik cache are CHECKED
- Click the Red + button and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Fire Nexus ROM Zip
- Accept defaults
- Move "Wipe" to the Top of the order
- Press the big FLASH button.
- Ignore any warnings that appear
Mr McBoatface said:
Check the rom you downloaded is not corrupted, verify hash value. Store it on the tablet not an sd card when flashing.
Reboot the tablet after you install supersu and flashfire. Before you flash the rom, make sure you remove the usb cable.
Don't use auto mount. Make sure you follow the flashfire instructions below. Make sure to move wipe to top of the order !
Fresh installation from FireOS via FlashFire >= 0.55.1
- Click the Red + and choose 'Wipe'
- Ensure System data, 3rd party apps and Dalvik cache are CHECKED
- Click the Red + button and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Fire Nexus ROM Zip
- Accept defaults
- Move "Wipe" to the Top of the order
- Press the big FLASH button.
- Ignore any warnings that appear
Click to expand...
Click to collapse
Still nothing, leads me into another boot loop.
New things:
Rebooted after installing flash fire
Verified the hash
Move the rom onto the internal drive (flashed from there)
No Automount
Any other ideas?
IIRC, I had similar issues when first installing a ROM onto my Fire, but that was many months ago, and my memory is a bit fuzzy... IIRC, it had to do with the location of the ZIP. I believe I had to put the zip on my SD card, and then when I wiped my system, I also wiped my data volume. Speaking of wiping...
Shugumi said:
Process:
Stock firmware (5.3.1) after amazon recovery tool
Kingroot root
Supersu-me
Update su
Tried once with and without rebooting
Rootjunky super tool, installed google play store
Install Flashfire (from play store) ver. .55
Also tried with an apk file ^ (ver. .53)
Set up a wipe for (dalvik, system, 3rd party)
Click to expand...
Click to collapse
Maybe I'm reading this wrong, but are you saying you're installing the zip, and THEN wiping the system? That's going to erase the installation you just flashed. You should be wiping the system, and THEN flashing the zip. The original instructions are here:
ggow said:
Fresh installation from FireOS via FlashFire >= 0.55.1
- Click the Red + and choose 'Wipe'
- Ensure System data, 3rd party apps and Dalvik cache are CHECKED
- Click the Red + button and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Fire Nexus ROM Zip
- Accept defaults
- Move "Wipe" to the Top of the order
- Press the big FLASH button.
- Ignore any warnings that appear
Click to expand...
Click to collapse
IIRC, if you put the ZIP onto the internal storage, it puts it in the Data volume, which is then going to be wiped. FF wipes the data, and then can't find the zip (because it just deleted everything...). Does that make sense?
crazyates said:
IIRC, I had similar issues when first installing a ROM onto my Fire, but that was many months ago, and my memory is a bit fuzzy... IIRC, it had to do with the location of the ZIP. I believe I had to put the zip on my SD card, and then when I wiped my system, I also wiped my data volume. Speaking of wiping...
Maybe I'm reading this wrong, but are you saying you're installing the zip, and THEN wiping the system? That's going to erase the installation you just flashed. You should be wiping the system, and THEN flashing the zip. The original instructions are here:
IIRC, if you put the ZIP onto the internal storage, it puts it in the Data volume, which is then going to be wiped. FF wipes the data, and then can't find the zip (because it just deleted everything...). Does that make sense?
Click to expand...
Click to collapse
Had the zip on storage and wiped before flash, nothing :/
Was kingroot fully removed and SuperSU correctly installed ? Are you using the latest nexus ROM dated Feb 2017 ?
Try again this time use fire flash 0.53 included in super tools. Don't install play store or upgrade SuperSU, use the SuperSU included in super tools. Again make sure you restart the tablet after installing SuperSU and after installing fire flash.
With flashfire 0.53 make sure automount is deselected. Include wipe cache options too.
So wipe System data, 3rd party apps, Dalvik cache and cache , flash the nexus ROM. Again make sure before you hit the flash button the wipe action is moved to the top of the list. Make sure no USB cable connected to the device too
In my experience 0.53 flashes really quick , 0.55.1 "can" show a black screen, you might think its failed but it's working in the background but might take 5 mins to flash.
0.53 sometimes fails to open and crashes but i have only seen that when it was used on a device with a custom ROM already flashed on it. It should be fine for flashing on the fire OS system.
Mr McBoatface said:
Was kingroot fully removed and SuperSU correctly installed ? Are you using the latest nexus ROM dated Feb 2017 ?
Try again this time use fire flash 0.53 included in super tools. Don't install play store or upgrade SuperSU, use the SuperSU included in super tools. Again make sure you restart the tablet after installing SuperSU and after installing fire flash.
With flashfire 0.53 make sure automount is deselected. Include wipe cache options too.
So wipe System data, 3rd party apps, Dalvik cache and cache , flash the nexus ROM. Again make sure before you hit the flash button the wipe action is moved to the top of the list. Make sure no USB cable connected to the device too
In my experience 0.53 flashes really quick , 0.55.1 "can" show a black screen, you might think its failed but it's working in the background but might take 5 mins to flash.
0.53 sometimes fails to open and crashes but i have only seen that when it was used on a device with a custom ROM already flashed on it. It should be fine for flashing on the fire OS system.
Click to expand...
Click to collapse
I might disagree with a few things you said there...
You only have to remove KingRoot if you're using v5.0 or newer. If you can use 4.9.6 to root, which I believe is what the SuperTool uses, then you can download SuperSu from the play store, update SU binary, then uninstall KingRoot with no issues.
As far as FF is concerned, the ROM developer says 0.55.1 is required, so I wouldn't stray from that.
The only other thing I would recommend is using the not-newest version of the ROM. For the last 6 months, the ROM has been based on a 5.3.2 boot.img, and recently switched to a 5.1.4 boot.img. Maybe the newer firmwares don't like the downgrade? I would try the Feb-2-2017 version of the ROM and try again.
Steps:
Restore to stock 5.3.2 (NOT 5.3.2.1)
SuperTool to install KingRoot 4.9.6 & GPlay
Kingroot to root
Install SuerSU (newest) & FF (newest) from Gplay
Use SuperSu to update SU binary
Put Feb-2-2017 zip on SD card
Use FF to wipe System, Data, Cache, Dalvik, 3rd party apps, & then install zip from SD.
Let sit for 5-10 minutes & do it's thing.
Having 2 root managers is not a good idea.
Kingroot uses it's own su binaries which may cause problems and clash with SuperSU. Using the script in supertools is a better option as it replaces the superuser su binary with a SuperSU compatible one.
The version of flashfire shouldn't matter, but he is having issue so best to rule it out. The behavior of 0.53 is different to 0.55.1 . it flashes a lot quicker and is fine to use. I've used it several times in the last fortnight with the latest ROM.
The current ROM is fine, boot image and binary change won't cause the issue experienced here. The older ROMs are broken , in so far as either the camera or screen cast won't work. The latest ROM with the proven and stable binary is a better option, everything works
EDIT , also there are reports of several users losing supersuser seemingly random after upgrading to the latest SuperSU , hence why I suggested sticking with the current one on supertools.
I also suggested wiping cache, just incase an amazon update has downloaded while rooting and attempts to install at the same time at the nexus ROM is being flashed.
I have a Fire running Nexus Fire ROM (2/8/17), and my fiance has a Fire running stock 5.1.2 with root, OTA updates disabled, Nova Launcher, and Gplay Store. I wanted to flash hers from Stock to Fire Nexus, and ran into the same issues I had before.
FF was supposed to Wipe System Data, 3rd party apps, Dalvik, and Cache, then install zip, then inject SuperSU. When it did the wipe, it deleted the ZIP on the Internal Store, so FF sat there for 15 minutes not doing anything, and I didn't have a system to reboot into anymore.
I had to do a sideload recovery of 5.1.2, root, install FF, and do all the same steps as above, but this time install the zip from an SD card. Worked great.
Mr McBoatface said:
Kingroot uses it's own su binaries which may cause problems and clash with SuperSU. Using the script in supertools is a better option as it replaces the superuser su binary with a SuperSU compatible one.
Click to expand...
Click to collapse
I used the SuperTool to root, and this is what I did also. Afterwards, I used the Gplay to update the SuperSU, which updated to the newest binary. I haven't seen any problems as of yet.
Unless internal storage was selected that shouldn't have happened, unfortunate that it did for you. The only time I've seen FF hang was when wipe was in the wrong order or when the USB cable was connected..... Don't know why the USB cable has that effect but I've seen it on 2 devices, other people have not had any problems.
Not seen the issue with SuperSU myself but read plenty of reports about it.
It seems users are affected by several random issues even if following the same instructions.
@Shugumi any update ?
Been swapping out roms and trying each suggestion but its been giving me the same boot loop.
So, I returned the kindle fire, and am waiting to try it on the new coming device :/, but thanks to everybody that replied to this thread. Even though we didn't get to root my kindle, it was great help! Thanks everybody.