Hi there, can anyone tell me how to copy the stock room from a note2 (4.1.1) to another note
I have two note2 one running Resurrection Remix and one with stock, I have ClockWorkMod Recovery installed on both but when I try to make a backup/recovery on the stock note2 im getting error message unable to backup to SD card.
Also on the resurrection remix note2 I cannot install gapps , I downloaded from here
https://rootmygalaxy.net/download-gapps-resurrection-remix-rom-google-apps/
Thanks for any help.
Here's a picture of the error message, I've also tried to make a recovery file with TWRP with the same result.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am not sure what happen on this.
If I were you, my way is just backup those chatting apps (Whatsapp, viber, Line,etc) since I can manually back them up under their settings and restore them easily.
For the rest of apps, I will take note which apps I need. Then find and redownload them back.
As for documents, pictures, music, videos, I will manually copy them out and restore back.
There's another way, use Titanium Backup, but your note got to be root.
---------- Post added at 10:45 AM ---------- Previous post was at 10:43 AM ----------
And one more, gapps. I use the link below to choose and download. I am using Resurrection Remix for tolte currently too.
https://opengapps.org/
Thanks for your reply, I will try this on the stock note2, so do I just back up to a external SD card and then transfer to my other note2 running reassertion?
however I am now getting the exact same error message (there was an error in trying to flash your recovery, unable to backup) on my custom ROM reassertion as well !
Both have root, I'm really just wanting to have play store and Viber on my custom ROM.
Thanks
huh? For playstore, download the gapps from the link I sent just now.
I install using twrp without issue.
Way1:
For viber, there is a backup in the viber setting. but for text only. For the media , you need to manually move them.
Way 2:
Since you have root, use titanium backup to backup viber and restore it over to new phone. That's all.
Well I seem to have found a problem that obviously doesn't help, I can't install the Gapps package as per 1st photo.
I then tried your suggestion of using titanium backup and again I get a error message as per 2nd photo.
I then checked to see what was going on with Root checker and it shows my device running custom ROM reasurrection remix is not root, how could this be?
It was root before installing remix, really weird.
Not sure what my next step is to get everything working.
Titatium backup works for root device only. You said it was root before RR rom, but when you go this RR, do you find a way to root it? If not, go for root first will be good for you to proceed.
Hey I did manage to get Gapps installed, had to re flash the ROM and was then working.
Ok so I have to root the phone again,, I didn't know that by flashing a custom ROM that I would lose this feature.
Hopefully this isn't to hard to do with this ROM installed.
tenkan said:
Hey I did manage to get Gapps installed, had to re flash the ROM and was then working.
Ok so I have to root the phone again,, I didn't know that by flashing a custom ROM that I would lose this feature.
Hopefully this isn't to hard to do with this ROM installed.
Click to expand...
Click to collapse
There is a sequence here.
1. a)Confirm your phone model, (N7105, N7100, etc...) Make sure the customs rom is for the exact model of your phone. Download the zip file and put in your phone or sd card.
b) Gapps- Go and download from the link I posted on previous link with below choices. Put the file in your phone or sd card.
Platform: ARM
Android: Choose the exact OS of the RR rom.
Variant: Nano
2. Backup your media and stuff to PC or sd card if you need them.
3. Flash TWRP via odin tool.
4. Boot into twrp recovery mode, install the RR rom first. After finish install RR rom, Don't choose clear cache/dalvik or reboot. Just press Back button to return to TWRP main screen.
5. Then, Install Gapps file that you downloaded. After done, clear cache/dalvik and reboot. Then should be done.
But I am not sure the RR rom you use got preinstall Magisk root or not. So I can't comment anything on the root.
Ok thanks for this information, I have followed your instructions and all is good except root, I'm looking into the Magisk Manager
Also I noticed that only 2 custom ROM work on my note 2 (N7100) I've tried 4 others and they all get stuck on reboot (boot loop) they install without errors tho.
Can you recommend one in particular?
tenkan said:
Also I noticed that only 2 custom ROM work on my note 2 (N7100) I've tried 4 others and they all get stuck on reboot (boot loop) they install without errors tho.
Can you recommend one in particular?
Click to expand...
Click to collapse
I am using RR made by kozmo21, it's for n7105 and magisk root is included.
https://forum.xda-developers.com/ga...rom-resurrectionremix-v5-8-2-t3567769/page139
Here's the download link for the latest update he has done except magisk, you need to update by magisk manager:
https://androidfilehost.com/?fid=1322778262904012906
Ok so I have tried a number of different ROMs and unfortunately I cannot get root access, magisk cannot be installed with any of the ROMs I've tried because I get error message "unable to install as magisk needs Android 5.0 or higher", it's weird because the custom ROMs I've managed to install are based on 7.0.
Also I thought you must have root access to be able to flash custom ROMs ? Root checker and superSU both say no Root ! The whole thing is strange.
But I'll keep trying any suggestions that you can offer, as I brought two Samsung note 2 to experiment with ; )
tenkan said:
Ok so I have tried a number of different ROMs and unfortunately I cannot get root access, magisk cannot be installed with any of the ROMs I've tried because I get error message "unable to install as magisk needs Android 5.0 or higher", it's weird because the custom ROMs I've managed to install are based on 7.0.
Also I thought you must have root access to be able to flash custom ROMs ? Root checker and superSU both say no Root ! The whole thing is strange.
But I'll keep trying any suggestions that you can offer, as I brought two Samsung note 2 to experiment with ; )
Click to expand...
Click to collapse
You may try the one I shared to you on previous message.
That one is RR from for n7105 with magisk root inside. I use it to flash without any problem.
If still got problem, try to flash the latest stock from (4.4.2), then install twrp. Reboot to twrp to wipe data, then install the RR rom. This work for me.
---------- Post added at 08:26 AM ---------- Previous post was at 08:25 AM ----------
Based on your screenshot, you are using hyper from, I'm not sure on that one as I never try that. The link I shared is the one I am familiar with .
Hi there, ok so unfortunately I can't try the one you suggested as the is for the n705 which cannot be flashed to the n7100
However with a lot of experimenting I have decided to go with Viper Rom with Root.
I have a tried quite a few ROMs without root and having to gain access to this as a separate item is not always as easy as one would think!
Magisk seems only to be available with the right kernel on certain ROMs but not all ?
Ok, Now I get it. It is N7100 you are using. I keep on confusing on which you are using previously.
You can try this(RR rom For N7100), flash via TWRP:
https://forum.xda-developers.com/ga...t/resurection-remix-n-5-8-5-20180825-t3837356
The RR rom above doesn't come with root. so try this way to go for Magisk root:
1) Go to this site: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
2) Download Latest Stable or Latest Beta. It will be downloaded as zip.
3) Place it under your sd card.
4)After the RR rom has been installed, reboot to twrp.
5) Install the magisk zip. Once installed, reboot to see whether magisk manager is installed or not.
Related
I soft-bricked my galaxy and there's no way to fix it, help! Okay, this is a what happened, I installed a custom ROM which worked out perfectly well until one day all applications started force closing for apparently no reason so I reboot and got stuck in a boot loop. I can only access download mode, recovery is out of the question. I tried to flash back to stock with Odin and it "passed" but the screen was just blank. So, I removed the USB cable hoping it will work and it got stuck in another boot loop. I tried everything that I could have think of but nothing works. It seems that I'm not the only one and is common for Galaxy W devices. Please help!
Also, in the worst case how do I send it back to Samsung? I mean, I know how to but will they fix it?
Location ?
Sent from my GT-I8150 using xda premium
dont worry , you can just flash it again. A new stock ROM would do. Its no problem.
We have a guide here on this forum. Check it out ^_^
andynroid said:
Location ?
Sent from my GT-I8150 using xda premium
Click to expand...
Click to collapse
Umm....Malaysia?
jrandroid said:
dont worry , you can just flash it again. A new stock ROM would do. Its no problem.
We have a guide here on this forum. Check it out ^_^
Click to expand...
Click to collapse
I have tried that and it does not work.
Me too I got the same problem. But flashed a stock rom and everything 's working well except data network. Sending it to Samsung centre to fix. To brick it join the Galaxy W Malaysian users group on FB I'm sure you'll find the solution to brick
Sent from my GT-I8150 using XDA
darthbii said:
Me too I got the same problem. But flashed a stock rom and everything 's working well except data network. Sending it to Samsung centre to fix. To brick it join the Galaxy W Malaysian users group on FB I'm sure you'll find the solution to brick
Sent from my GT-I8150 using XDA
Click to expand...
Click to collapse
Can you please explain what did you do exactly?
Hi
Sorry, but if you cannot go to recovery problem..
The problem is in your hardware
I already put this problem to this thread
Read carefully
To many member have re-post this problem
So your are not alone
For the others please aware this situation,
This is not problem that you can solve by flashing
Read the thread with "star" first before you posting and get confuse
Regards
Stock Gaming Rom Stable i8150XXLM8
i may have the same problem i use cynanogen mod 9 build 3 then flash to this stock gaming rom..problem start
1. 3g/wcdma not detected/no 3g icon appear/cannot download anuthing
2. reboot using clockwokr mod....but cannot reboot..its say root acces posibly lost..but SU does exist in apps
andydidacus said:
i may have the same problem i use cynanogen mod 9 build 3 then flash to this stock gaming rom..problem start
1. 3g/wcdma not detected/no 3g icon appear/cannot download anuthing
2. reboot using clockwokr mod....but cannot reboot..its say root acces posibly lost..but SU does exist in apps
Click to expand...
Click to collapse
did you full wipe before flashing stock rom?
what stock gaming rom, it is full recovery?
you may can try:
- flashing again cwm using odin,
- if succesfull, boot to cwm, format data and cache, except system
- try reboot normally.
- if failed, format everything, except your sdcard,
- flashing stock rom using odin, (better use stock rom provided for your country), use original stock rom, not modified rom ! with size more than 350mb, its contain recovery, baseand and everything you need. of course your cwm will be replaced after. you can flash again cwm after your phone boot normally.
good luck.
andydidacus said:
i may have the same problem i use cynanogen mod 9 build 3 then flash to this stock gaming rom..problem start
1. 3g/wcdma not detected/no 3g icon appear/cannot download anuthing
2. reboot using clockwokr mod....but cannot reboot..its say root acces posibly lost..but SU does exist in apps
Click to expand...
Click to collapse
In reverting back to GB 2.3.6 from CM9, you should do format /system to be able to flash successfully. Try it.
Yes i jave succesfully revert to gb rom..n finally traded it woth sgn
Sent from my GT-N7000 using xda premium
Thanks
coliv_aja said:
did you full wipe before flashing stock rom?
what stock gaming rom, it is full recovery?
you may can try:
- flashing again cwm using odin,
- if succesfull, boot to cwm, format data and cache, except system
- try reboot normally.
- if failed, format everything, except your sdcard,
- flashing stock rom using odin, (better use stock rom provided for your country), use original stock rom, not modified rom ! with size more than 350mb, its contain recovery, baseand and everything you need. of course your cwm will be replaced after. you can flash again cwm after your phone boot normally.
good luck.
Click to expand...
Click to collapse
Thanks really worked! ^
Hi! yesterday I tried to get cyanogenmod to my Samsung galaxy W. Firstly I used this tutorial to root my phone View attachment 1899558
Then I installed clockworkmod recovery with this tutorial
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I did the ''IV. Accessing ClockworkMod Recovery'' , I tried to backup my phone, but there wasn't enough space to do it, so I pressed ''reboot'' and this happens, it goes through the samsung and galaxy w logo, but after that the screen just turns black, this happens every time when I try to turn it on. I can access the clockworkmod recovery.
I have tried to ''wipe the cache partition'', ''wipe data/factory reset'' and wipe ''dalvik cache'' but it doesn't seem to work.
What should I do, I don't want cyangenmod after this haha I just want to know if there is a way to get the phone working.
Any answers would be appreciated
Eerooo said:
Hi! yesterday I tried to get cyanogenmod to my Samsung galaxy W. Firstly I used this tutorial to root my phone View attachment 1899558
Then I installed clockworkmod recovery with this tutorial View attachment 1899561
When I did the ''IV. Accessing ClockworkMod Recovery'' , I tried to backup my phone, but there wasn't enough space to do it, so I pressed ''reboot'' and this happens, it goes through the samsung and galaxy w logo, but after that the screen just turns black, this happens every time when I try to turn it on. I can access the clockworkmod recovery.
I have tried to ''wipe the cache partition'', ''wipe data/factory reset'' and wipe ''dalvik cache'' but it doesn't seem to work.
What should I do, I don't want cyangenmod after this haha I just want to know if there is a way to get the phone working.
Any answers would be appreciated
Click to expand...
Click to collapse
Some wrong sequence there :
Forgets the steps as per attachment.
In assumption the CM9 ROM.zip is in your SD Card...
Boot to CWM
Locate the CM9 ROM using and remember the location i.e. External SD etc
Now under Advance...Format all folders clean (not the folder containing the CM9 ROM)
Wipe / Format / Cache etc = the usual
Wipe Dalvik
Fix Permission
Flash the CM9 then GAPPS
Reboot...:good:
No need to back-up once you have used CM9...you will never go back to GB
If you insist on back-up just move all your treasures in your PC 1st, best to format the SD Card then move the ROM.zip to it
andynroid said:
Some wrong sequence there :
Forgets the steps as per attachment.
In assumption the CM9 ROM.zip is in your SD Card...
Boot to CWM
Locate the CM9 ROM using and remember the location i.e. External SD etc
Now under Advance...Format all folders clean (not the folder containing the CM9 ROM)
Wipe / Format / Cache etc = the usual
Wipe Dalvik
Fix Permission
Flash the CM9 then GAPPS
Reboot...:good:
No need to back-up once you have used CM9...you will never go back to GB
If you insist on back-up just move all your treasures in your PC 1st, best to format the SD Card then move the ROM.zip to it
Click to expand...
Click to collapse
Thank you so much!There is still a problem my phone recognizesmy sd card it and also tells me how much storage i have left. But when i want to use an application like the camera it says there is no sd card. What should I do?
E: Already got the problem fixed
Got another SD card to swap ?
Please Help me T.T
I just wanna go back to original Stock Rom and yesterday I Flash the firmware Malaysia with Odin.. the Odin haven't pass then my phone automatically restart and after few minutes the odin said PASS and the message there wrote ''distroy instant'' and ''Killed timer''... after that my galaxy w cannot boot.. it just stucked at the start screen wallpaper there.....
please help me... sorry for my broken english...
---------- Post added at 02:01 PM ---------- Previous post was at 01:21 PM ----------
odin wrote Close serial portal and wait until rebooting but it havent PASS and my wonder cannot start and it stucked at samsung logo....
j0rd4nkzf said:
Umm....Malaysia?
I have tried that and it does not work.
Click to expand...
Click to collapse
last time my phone cannot start too because i flash wrong file, then i send service centre at lowyat saying my phone suddenly can't be turned on (don't say ur already root or whatever can void the warranty)
Ore Sanjou!
j0rd4nkzf said:
I soft-bricked my galaxy and there's no way to fix it, help! Okay, this is a what happened, I installed a custom ROM which worked out perfectly well until one day all applications started force closing for apparently no reason so I reboot and got stuck in a boot loop. I can only access download mode, recovery is out of the question. I tried to flash back to stock with Odin and it "passed" but the screen was just blank. So, I removed the USB cable hoping it will work and it got stuck in another boot loop. I tried everything that I could have think of but nothing works. It seems that I'm not the only one and is common for Galaxy W devices. Please help!
Click to expand...
Click to collapse
u must service it in SamsungServiceCenter
Hi guys, i just updated my Ace 2 from 2.3.6 GB to 4.1.2 JB through Samsung Kies. After the update process, i used the "root.zip" (err, just saw it while searching from the forum) in order for it to be rooted. I also downloaded gooManager, Root Browser, ROM manager, Greenify, Titanium. Also removed unnecessary apps using Root Browser ( saw list of bloated apps on Ace 2 also in this forum). It is my first time rooting my droid and I want to obtain knowledge in order to maximize my droid's capabilities.
So here's my questions (so far):
1. Why is it my Recovery Mode is looking like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
instead of looking like this:
since because i wanted to flash it but when I see some tutorials, their recovery mode has a ROM Manager logo which made me hesitated on flashing.
2. What can you recommend on me , a newbie , about flashing tips in order to flash my Ace 2 into 4.4 kitkat?
Source : http://forum.xda-developers.com/showthread.php?t=2524905
3. Can someone tell me how to flash proper because im confused on flashing through recov mode and using Odin
4. Lastly, if i factory reset my 4.1.2 JB through recov. mode, will it revert my droid into 2.3.6 GB ? will it remove the root?
since i also saw some tutorials flashing by factory reset in recov. mode then installing from SD Card also in recov. mode
Please help me clear my mind on flashing Thank you !
So here's my questions (so far):
1. Why is it my Recovery Mode is looking like this:
instead of looking like this:
since because i wanted to flash it but when I see some tutorials, their recovery mode has a ROM Manager logo which made me hesitated on flashing.
1- because thats CWM, never use rom manager. Search forum for cwm 6 by shaaan
EDIT: temp cwm 6 http://forum.xda-developers.com/showthread.php?t=2141395
2. What can you recommend on me , a newbie , about flashing tips in order to flash my Ace 2 into 4.4 kitkat?
Source : http://forum.xda-developers.com/showthread.php?t=2524905
2- thats a theme, no kitkat yet
3. Can someone tell me how to flash proper because im confused on flashing through recov mode and using Odin
3- follow instructions in first post of EVERY rom thread, you should be safe
4. Lastly, if i factory reset my 4.1.2 JB through recov. mode, will it revert my droid into 2.3.6 GB ? will it remove the root?
since i also saw some tutorials flashing by factory reset in recov. mode then installing from SD Card also in recov. mode
4-
-no
-no
-dont follow those tuts, follow our ace 2 ones, to revert to 2.3 search forum for the thread, its late here ill try to link the thread for you
Sent from my GT-I8160 using Tapatalk
Try to download it again and as it says, it is for Android 4.3.
nairb310 said:
1. Why is it my Recovery Mode is looking like this instead of looking like this:
4. Lastly, if i factory reset my 4.1.2 JB through recov. mode, will it revert my droid into 2.3.6 GB ? will it remove the root?
since i also saw some tutorials flashing by factory reset in recov. mode then installing from SD Card also in recov. mode
Please help me clear my mind on flashing Thank you !
Click to expand...
Click to collapse
1: In the Ace 2, recovery comes from the kernel. You can temporarily load "cwm6.zip" to upgrade until the next reboot "Android system recovery 3E" into CWM 6.0.2, and once you install another kernel with a modified recovery (CM10.2 contains CWM 6.0.3 for example) it will always load in place of the stock one.
4: Factory reset means deleting everything under /data (the system memory in which apps are installed by default), /cache and .android_secure (apps moved to SD or USB storage), the OS and all system applications will persist. You will technically stay rooted, but SuperSU will only remain if it was installed as a system app.
To switch between 2.x and 4.x you must flash and repartition with a complete 3-part firmware (with PIT, CODE/PDA and CSC files), like LK4 or MB4. After that you can install an OS of the same generation using Odin/Heimdall (for tar files) or CWM (for zips).
Most stock-derivate firmwares recommend a base version but it's usually optional; AOSP roms (Cyanogen, AOKP and the like) don't care at all.
Ryccardo said:
1: In the Ace 2, recovery comes from the kernel. You can temporarily load "cwm6.zip" to upgrade until the next reboot "Android system recovery 3E" into CWM 6.0.2, and once you install another kernel with a modified recovery (CM10.2 contains CWM 6.0.3 for example) it will always load in place of the stock one.
4: Factory reset means deleting everything under /data (the system memory in which apps are installed by default), /cache and .android_secure (apps moved to SD or USB storage), the OS and all system applications will persist. You will technically stay rooted, but SuperSU will only remain if it was installed as a system app.
To switch between 2.x and 4.x you must flash and repartition with a complete 3-part firmware (with PIT, CODE/PDA and CSC files), like LK4 or MB4. After that you can install an OS of the same generation using Odin/Heimdall (for tar files) or CWM (for zips).
Most stock-derivate firmwares recommend a base version but it's usually optional; AOSP roms (Cyanogen, AOKP and the like) don't care at all.
Click to expand...
Click to collapse
Thank you for your reply but i cant understand some of the term you are saying XD So basically on 1. recovery kernel can be upgraded ? and my kernel i think is old ? so that is why my recov mode is not looking like ROM manager logo?
so also i can flash using ROM manager or Recovery mode with my current system ?
Flash temp cwm 6 zip in stock recovery(will be called update.zip, i added link). Dont use rom manager
Sent from my iPhone
nairb310 said:
Thank you for your reply but i cant understand some of the term you are saying XD So basically on 1. recovery kernel can be upgraded ? and my kernel i think is old ? so that is why my recov mode is not looking like ROM manager logo?
so also i can flash using ROM manager or Recovery mode with my current system ?
Click to expand...
Click to collapse
The same kernel that runs "the full Android experience" also contains the recovery that boots with up+home+power. Some kernels have the "Android system recovery 3E" (which can be temporarily upgraded to CWM with cwm6.zip), others have CWM directly.
Basically, if you have a Cyanogen ROM installed, it will have CWM preinstalled. For everything else keep the temporary CWM in you external storage.
(All this ignores Gingerbread kernels, but let's keep matters simple as you're probably using JB)
I'm on a rooted Nexus 7 2013 wifi only with twrp recovery installed. I'm currently running stock android 4.3 and wish to update to 4.4.2. I had originally held off updating but now want to do so. Here's what happened.
1. I first went to Settings /about phone /System update and tried to update. That failed repeatedly even though I have unmodified stock rom. (now even download fails though earlier it has downloaded successfully and the file is somewhere on the tablet).
2. So I next went to
http://forum.xda-developers.com/showthread.php?t=2380113
And downloaded the ota update zip file (JSS15R to kot49h). Then went to my Twrp 2.6.3.0 recovery screen and tried flashing the zip file from there. It failed. I didn't wipe anything first because I didn't want to lose my data.
So I'm stuck. Can I update without losing my data?
Thanks
Jeff
are you using supersu 1.69 or older for root?
if yes you must disable ota survival in supersu settings and re-root after update.
and normaly you can ota update without wipe your data, but i dont want to assure that.
dusu84 said:
are you using supersu 1.69 or older for root?
if yes you must disable ota survival in supersu settings and re-root after update.
and normaly you can ota update without wipe your data, but i dont want to assure that.
Click to expand...
Click to collapse
Thanks for offering to help.
I'm running supersu 1.91. I went into its settings and found it had "survival mode" selected, so I unselected it. Then booted into twrp screen and tried to flash the downloaded ota zip file again. No luck. Here's the fail screen image.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Apparently some twrp versions have trouble flashing. I would like to update twrp but don't know how. No update button and can't find anything on the twrp website about updating.
because of the unexpected content in app_process... have you maybe running xposed framework?
then flash xposed_disabler zip first.
dusu84 said:
because of the unexpected content in app_process... have you maybe running xposed framework?
then flash xposed_disabler zip first.
Click to expand...
Click to collapse
Aha! You're a genius! I think we're getting somewhere now. Yes, I have Xposed, GravityBox, and XPrivacy installed and running.
Should I uninstall them?
Where do I find xposed_disabler zip?
I'll start searching for xposed_disabler but would appreciate any pointers.
Also, this may have nothing to do with this, but when I searched for key loggers I got this message (I ignored} :
you should see the xposed disabler recovery zip in your recovery on sdcard. this zip should be copied to your sd card when you install xposed framework. when the zip isnt there you can also download this in the original xposed thread. (im not allowed to share links because im new at xda).
because the message by search for key loggers... i dont know. sorry.
Anderson2 said:
And downloaded the ota update zip file (JSS15R to kot49h). Then went to my Twrp 2.6.3.0 recovery screen and tried flashing the zip file from there. It failed. I didn't wipe anything first because I didn't want to lose my data.
So I'm stuck. Can I update without losing my data?
Thanks
Jeff
Click to expand...
Click to collapse
Jeff, your best bet really is to just flash back to stock, then just flash recovery and root in one step using the Nexus 7 Toolbox. This whole process will take you about 15 minutes and you will have a solid foundation.
The first reaction of many people to a suggestion like that is "what about my data?" My answer is to think carefully about what data would actually be affected by wiping your device. If you have things set up normally on Android there is very little that won't be put back on your device after going through the initial setup again. All your apps will reinstall from Google Play, contacts and email will sync, settings will sync... Even your WiFi settings. Wallpapers will sync, and pictures and videos will sync if you have one or more of the various accounts set up that do that. The only things missing will be things that you downloaded from the web and any sideloaded apps. That probably isn't more than a handful of apps and/or PDF documents... And only if they are stored on internal memory vs. Virtual SD card. If you have any stragglers, you can use Titanium Backup for ROOT, but I don't even find that necessary.
Just make sure you have your Google account sync set to on, and whatever other apps you use sync for like SkyDrive, DropBox, and any other things that get their names from two capitalized words mashed together.
Mike
Sent from my Nexus 7 using Tapatalk
Ah, but I am one of those who avoid syncing and trusting Google with my data.
Anderson2 said:
Where do I find xposed_disabler zip?
Click to expand...
Click to collapse
hey, have you find the xposed disabler recovery zip and whether have you flashed it?
is the ota update now working?
greets
EDIT: the xposed disabler recovery zip must be directly on your sd card... not in a specifically folder.
dusu84 said:
hey, have you find the xposed disabler recovery zip and whether have you flashed it?
is the ota update now working?
greets
EDIT: the xposed disabler recovery zip must be directly on your sd card... not in a specifically folder.
Click to expand...
Click to collapse
Not, I didn't find the xposed disabler recovery zip. At least not from a site I can trust. I searched my Nexus 7 contents and didn't find a xposed disabler recovery zip.
What I did do was uninstall Xposed, rebooted, and now Settings /about phone /system update did download the 4.4.2 system update - but didn't keep the file (at least not in the cache folder) because "verification failed". So I'm back where I was.
I also have Avast Mobile Security installed and it has a stealth anti-theft component that protects itself from tampering. I wonder if it might be blocking things. I might temporarily uninstall Avast to see.
One more thought: the Nexus 7 apparently has a way of booting into "safe mode". I don't know how to get into it, but perhaps the Android update might succeed when in safe mode.
This is really a pain! I can't believe I'm the only one facing this problem.
Anderson2 said:
Not, I didn't find the xposed disabler recovery zip. At least not from a site I can trust. I searched my Nexus 7 contents and didn't find a xposed disabler recovery zip.
What I did do was uninstall Xposed, rebooted, and now Settings /about phone /system update did download the 4.4.2 system update - but didn't keep the file (at least not in the cache folder) because "verification failed". So I'm back where I was.
I also have Avast Mobile Security installed and it has a stealth anti-theft component that protects itself from tampering. I wonder if it might be blocking things. I might temporarily uninstall Avast to see.
One more thought: the Nexus 7 apparently has a way of booting into "safe mode". I don't know how to get into it, but perhaps the Android update might succeed when in safe mode.
This is really a pain! I can't believe I'm the only one facing this problem.
Click to expand...
Click to collapse
ok strange...
btw. what the xposed disabler recovery zip does is copying /system/bin/app_process.orig back to /system/bin/app_process ... and in system/bin/app_process you have the unexpected contents according to your image what you have posted.
the xposed disabler recovery zip can you download from here: http://forum.xda-developers.com/attachment.php?attachmentid=2314045&d=1381353218
but the problem with the app_process should done with uninstall xposed i think. after you uninstalled xposed, have you try to flash the ota zip again?
you come into safe mode by holding "shut down" after you press on/off button.
dusu84 said:
ok strange...
btw. what the xposed disabler recovery zip does is copying /system/bin/app_process.orig back to /system/bin/app_process ... and in system/bin/app_process you have the unexpected contents according to your image what you have posted.
the xposed disabler recovery zip can you download from here: http://forum.xda-developers.com/attachment.php?attachmentid=2314045&d=1381353218
but the problem with the app_process should done with uninstall xposed i think. after you uninstalled xposed, have you try to flash the ota zip again?
you come into safe mode by holding "shut down" after you press on/off button.
Click to expand...
Click to collapse
Thanks for hanging with me.
It gets stranger still. Safe mode method doesn't work for me. When the power off popup comes on, if I short press or long press, it doesn't bring up the safe mode option.
I uninstalled Xposed and rebooted. Then I went back to my Twrp recovery screen and tried to reflash the ota zip again. It failed again but with an interesting error message about debuggerd contents.
And in case I'm missing something here is my tablet information.
Anderson2 said:
Thanks for hanging with me.
It gets stranger still. Safe mode method doesn't work for me. When the power off popup comes on, if I short press or long press, it doesn't bring up the safe mode option.
I uninstalled Xposed and rebooted. Then I went back to my Twrp recovery screen and tried to reflash the ota zip again. It failed again but with an interesting error message about debuggerd contents.
Click to expand...
Click to collapse
im sure we will make it
i hope this can solved the debuggerd problem: http://forum.xda-developers.com/attachment.php?attachmentid=2307599&d=1381111112
download it and flash it with twrp. perhaps a reeboot into recovery. then try to flash the ota update zip again.
dusu84 said:
im sure we will make it
i hope this can solved the debuggerd problem: http://forum.xda-developers.com/attachment.php?attachmentid=2307599&d=1381111112
download it and flash it with twrp. perhaps a reeboot into recovery. then try to flash the ota update zip again.
Click to expand...
Click to collapse
Here's what I did that finally worked. (sort of cheated)
1. Made a nandroid backup of the current state.
2. I had previously restored to an earlier nandroid and then tried to update again various ways. No success.
3. Finally, I restored a nandroid I made when I first rooted right after I bought the tablet. From this state the tablet updated itself automatically to 4.4.2!
My next task is to check my data to see if it went back to that early days. If so, maybe I can restore just data from the recent nandroid. Otherwise, I'll just work around it.
So far data and apps appear OK. How lucky can I be? Shows the advantage of making an early nandroid when tablet is still new.
(big sigh of relief)
Anderson2 said:
Here's what I did that finally worked. (sort of cheated)
1. Made a nandroid backup of the current state.
2. I had previously restored to an earlier nandroid and then tried to update again various ways. No success.
3. Finally, I restored a nandroid I made when I first rooted right after I bought the tablet. From this state the tablet updated itself automatically to 4.4.2!
My next task is to check my data to see if it went back to that early days. If so, maybe I can restore just data from the recent nandroid. Otherwise, I'll just work around it.
Click to expand...
Click to collapse
Anderson2 said:
So far data and apps appear OK. How lucky can I be? Shows the advantage of making an early nandroid when tablet is still new.
(big sigh of relief)
Click to expand...
Click to collapse
perfect its solved :good:
still have a nice day with your kitkat nexus!
Thank you.
One problem remains. I tried to do a new nandroid and discovered that when I went to the recovery screen instead of twrp, all it showed was open Android with red exclamation and something about "no command".
I think it deleted my Twrp, (or my Twrp was not compatible with kitkat). I don't recall how to reinstate twrp. Will try to find out. Rom Toolbox tells me there is no available recovery for my device, which must be wrong.
EDIT reinstalled twrp using goo manager. So I'm good!
I didn't read through this whole thread so excuse my response if you already found your answer.. I think if you have twrp flashed then the ota is going to fail every time. Reflash the stock recovery and run the ota update.
Sent from my Nexus 7 using Tapatalk
If I were in your shoes, I would just flash the factory KitKat ROM. You can download it here: https://developers.google.com/android/nexus/images
If you edit flash-all.bat (windows) or flash-all.sh (Linux) you can flash it without wiping your data. I would not bother though, I would let it while my data and restore it through synching or through Titanium Backup
Sent from my Nexus 7 using XDA Premium HD app
I was running rooted stock version of kit kat. Yesterday afternoon I had Google Music running while doing housework when suddenly the music stopped. I checked the phone and the screen was black and would not turn on. Pulled the battery and then it stuck at the AT&T logo for 30+ minutes. I booted into CWM to perform a factory reset and potentially reinstall the ROM from the external sd card. The factory reset produced the following error.
Code:
--Wiping Data ...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache
Formatting /sdcard/.android_secure...
Error mounting /sdcard/.android_secure!
Skipping format...
Data wipe complete
Fiddled around more with CWM to reset and try to fix. Now, upon reboot, it hands at the Samsung Galaxy Note II screen.
Any help on fixing this so it can at least limp along until my Nexus 6 gets here would be greatly appreciated.
Use Phil touch recovery, and use wipe\clean to install new ROM. Should fix your problem. Also if you are going to a Nexus 6 you should try CM11 when u flash a new ROM.
If you want to use CWM then just format the system and flash a new ROM.
Sent from my GT-N7105 using XDA Free mobile app
I'm unfamilair with Phil Touch recovery.
Can I flash it using JOding on OSX?
ShrekOpher said:
Use Phil touch recovery, and use wipe\clean to install new ROM. Should fix your problem. Also if you are going to a Nexus 6 you should try CM11 when u flash a new ROM.
If you want to use CWM then just format the system and flash a new ROM.
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
John.T.Erskine said:
I'm unfamilair with Phil Touch recovery.
Can I flash it using JOding on OSX?
Click to expand...
Click to collapse
You can check here
http://forum.xda-developers.com/showthread.php?t=2201860
Sent from my SHIELD Tablet using XDA Free mobile app
Odin doesn't recognize the device. It could be the browser version running on an old macbook pro, but I believe it is the fact that the phone's internal sd card is corrupted somehow.
John.T.Erskine said:
Odin doesn't recognize the device. It could be the browser version running on an old macbook pro, but I believe it is the fact that the phone's internal sd card is corrupted somehow.
Click to expand...
Click to collapse
Have you tried formating the data and system from cwm?
Go into recovery and go to "advanced" and select format system and/or format data.
Sent from my GT-N7105 using XDA Free mobile app
Tried that and received the same error as the OP. Can not mount SD card.
ShrekOpher said:
Have you tried formating the data and system from cwm?
Go into recovery and go to "advanced" and select format system and/or format data.
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
Same issue
I'm having the same issue as OP. The phone won't get back to recovery. Won't even go into download mode.......Please help!
Edit: I was so used to working on my wife's phone (Note 1) that I was using the wrong button combination for download mode. I still can't get back to recovery, but I'll be ok once I get home.
Try to flash stock rom in Odin. That should fix any errors but if you're still getting errors there's other stuff to try
absinthesummer said:
Try to flash stock rom in Odin. That should fix any errors but if you're still getting errors there's other stuff to try
Click to expand...
Click to collapse
Not the OP but I just tried this with KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user_low_ship.tar and it did not help.
Here's what I have done thus far:
1. Reflash the stock ROM from sammobile via ODIN
2. Ends in a FAIL on sboot.img
3. Phone says unsupported version (I believe this is due to the Knox locking. I can't downgrade)
4. Reflash recovery-clockwork-touch-6.0.4.3-t0lteatt.img using Heimdall
5. Wipe data, cache, and Dalvik cache (noting the errors regarding the /data partition still occur)
5. Sideload cm-11-20141008-SNAPSHOT-M11-t0lte.zip
6. Sideload gapps-kk-20140606-signed.zip
7. Reboot the phone
8. Stuck in a boot loop on the cyanogenmod logo
Thoughts on where to go from here? Tearing my hair out.
ProjektTHOR said:
Not the OP but I just tried this with KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user_low_ship.tar and it did not help.
Here's what I have done thus far:
1. Reflash the stock ROM from sammobile via ODIN
2. Ends in a FAIL on sboot.img
3. Phone says unsupported version (I believe this is due to the Knox locking. I can't downgrade)
4. Reflash recovery-clockwork-touch-6.0.4.3-t0lteatt.img using Heimdall
5. Wipe data, cache, and Dalvik cache (noting the errors regarding the /data partition still occur)
5. Sideload cm-11-20141008-SNAPSHOT-M11-t0lte.zip
6. Sideload gapps-kk-20140606-signed.zip
7. Reboot the phone
8. Stuck in a boot loop on the cyanogenmod logo
Thoughts on where to go from here? Tearing my hair out.
Click to expand...
Click to collapse
Yes that's definitely KNOX bootloader kicking back your flash attempts in odin. MA4 is pretty old firmware. You need MK6 or NE5. Here's where you can get the latest 4.3-4.4.2 firmwares: http://forum.xda-developers.com/galaxy-note-2-att/development/rom-att-i317-ucucne5-mj4-stock-odex-t2802189
This should correct the data issue, if not, you may need to grab a pit file, but usually flashing the latest stock fixes it without requiring all that.
Flash that, re-root, flash new recovery (note: use a newer recovery, cwm sometimes has issues with our device, but twrp has been updated to work with 4.3+ same with philz, if you prefer that UI. Once 4.4.4 comes out, it doesn't play well with cwm, philz, OR older versions of twrp- I had a fight with a note 3 and recoveries yesterday, finally got it going with the latest twrp).
Boot up the device, flash/update your supersu. If you want to install a different rom now, go ahead. Once you have a new recovery installed, format (manually) /system /data /internal storage /cache /dalvik. The internal storage is important b/c it's usually what causes the /data corruption. Always wipe internal storage when switching between roms (or even between an update, I do). I don't usually wipe everything 3 times like some people do, but it is important to wipe the essentials. In twrp, internal storage is an option when wiping. In cwm & philz, you have to go under mounts & storage & it's second up from the bottom (format /data including /data/media> sdcard). Then back out to the main recovery menu and flash your rom, if you have any issues reboot recovery (not system) and re-flash it.
One more thing, make sure you have enough system storage for the gapps. I've run into issues where the rom flashed fine but gapps was too big for the system and didn't flash correctly. Try a slim gapps
Hope this helps, if you have any other questions I'm happy to try to help. We'll get it fixed for ya
Not able to flash other ROMS besides Stock now.......
In my previous post, I was able to get to download mode and flashed back to stock. I thought I was flashing At&t Stock 4.3, but was really flashing At&t 4.1.2 Stock.
I guess it would help to state what happened and the order of things. I'm at work so I don't have the exact versions for each file used, but I'll try my best. I was running DN3 v3.1.1. Something was happening where there was very little space left on my internal storage and I felt like it was time to try a different Rom since I had been on this for a few months as a daily.
1. I flashed BlissStalk with no issues, just didn't care much for the Rom (no hate, just not my cup of tea!)
2. Next I flashed CyanideMod and didn't care for that either. No issues, just wasn't my cup of tea.
3. I then attempted to flash the DS NE5 Rom, using CWM, and it would come on and show the Samsung Galaxy Note II screen and then go black. I had to do a battery pull to get anywhere and then it would come back on and get back to the Galaxy Note II screen and freeze there, or cut off completely again. This is what brought me here to this thread.
I was able to go back to stock 4.1.2, then stock 4.3, and even now on stock 4.4.2. But now I can't flash any Rom at all without getting stuck. I tried to flash DN3's latest and keep getting stuck at the second Samung Screen. I have tried to reboot and tried to reflash as the help says. I am reading through various topics and FAQ pages, but I figured this may be more than any particular Rom issue (I've tried flashing other Roms and I'm getting stuck on those too-either stuck at logos or turning off completely). I have to keep flashing back to stock.
I am researching this, even while at work, but does anyone have any idea what could be wrong?
PS Even though I don't state it above, I followed all flashing directions to a T!
dirtyalphaman said:
In my previous post, I was able to get to download mode and flashed back to stock. I thought I was flashing At&t Stock 4.3, but was really flashing At&t 4.1.2 Stock.
I guess it would help to state what happened and the order of things. I'm at work so I don't have the exact versions for each file used, but I'll try my best. I was running DN3 v3.1.1. Something was happening where there was very little space left on my internal storage and I felt like it was time to try a different Rom since I had been on this for a few months as a daily.
1. I flashed BlissStalk with no issues, just didn't care much for the Rom (no hate, just not my cup of tea!)
2. Next I flashed CyanideMod and didn't care for that either. No issues, just wasn't my cup of tea.
3. I then attempted to flash the DS NE5 Rom, using CWM, and it would come on and show the Samsung Galaxy Note II screen and then go black. I had to do a battery pull to get anywhere and then it would come back on and get back to the Galaxy Note II screen and freeze there, or cut off completely again. This is what brought me here to this thread.
I was able to go back to stock 4.1.2, then stock 4.3, and even now on stock 4.4.2. But now I can't flash any Rom at all without getting stuck. I tried to flash DN3's latest and keep getting stuck at the second Samung Screen. I have tried to reboot and tried to reflash as the help says. I am reading through various topics and FAQ pages, but I figured this may be more than any particular Rom issue (I've tried flashing other Roms and I'm getting stuck on those too-either stuck at logos or turning off completely). I have to keep flashing back to stock.
I am researching this, even while at work, but does anyone have any idea what could be wrong?
PS Even though I don't state it above, I followed all flashing directions to a T!
Click to expand...
Click to collapse
Ok so you've got the ne5 bootloader, so any time you flash stock you'll have to flash that version or above. Stock rom works, but custom ones don't, correct?
What's weird is that the latest dn3 is a modified stock rom so that shouldn't be an issue.
When you flashed stock, you re-rooted and did you update super su? I'm sure you already know but you should update super su's binaries & let it disable Knox, which will set your seLinux from enforcing to permissive. That could potentially be a reason why you can't flash new roms, Knox & selinux interfering with the kernel flash part of the rom(s) you're trying. If you haven't done this you may want to try and then try flashing a custom rom again. If you still encounter issues I'll try to help.
---------- Post added at 12:32 PM ---------- Previous post was at 12:21 PM ----------
John.T.Erskine said:
I'm unfamilair with Phil Touch recovery.
Can I flash it using JOding on OSX?
Click to expand...
Click to collapse
Also, cwm is pretty old and prone to bugs on our devices. However philz is based on cwm and very similar in terms of user interface. It's not as different as twrp is. It has the same style and setup just a few additional tools that cwm doesn't have. It's also more compatible with our devices. If I had to choose one I wouldn't choose cwm, I'd go with philz or twrp for the sake of compatibility.
Thanks. I'll try this when I get home. Yea, once I flashed stock I kept getting Security Notices. I saw this was due to Knox and disabled it but that was a few flash attempts ago. I will follow you steps and let you know how it goes. Once again, thanks.
absinthesummer said:
Yes that's definitely KNOX bootloader kicking back your flash attempts in odin. MA4 is pretty old firmware. You need MK6 or NE5. Here's where you can get the latest 4.3-4.4.2 firmwares: http://forum.xda-developers.com/galaxy-note-2-att/development/rom-att-i317-ucucne5-mj4-stock-odex-t2802189
This should correct the data issue, if not, you may need to grab a pit file, but usually flashing the latest stock fixes it without requiring all that.
Click to expand...
Click to collapse
You are a saint. I'm not sure why I was struggling to find stock 4.4-series firmwares that could be flashed. I was so focused on getting them from sammobile or samware-firmware that I didn't even think to look here. I am going to try this process today and let you know if it works out!
absinthesummer said:
When you flashed stock, you re-rooted and did you update super su? I'm sure you already know but you should update super su's binaries & let it disable Knox, which will set your seLinux from enforcing to permissive. That could potentially be a reason why you can't flash new roms, Knox & selinux interfering with the kernel flash part of the rom(s) you're trying. If you haven't done this you may want to try and then try flashing a custom rom again. If you still encounter issues I'll try to help.
Click to expand...
Click to collapse
I really think this is my issue. I tried updating Super SU by flashing 1.75, but I think that's old. It doesn't show up and when I download it from the PLAY store, it says there is no SU Binary. It's too late to fiddle with this now, but I will mess around with it tomorrow. I think I lost my root and it's not trying to let me get it back. But I don't give up that easy. I was looking through the sticky thread to get the most up to date SU flash, but because it's late and I had a lot going on, this project will have to wait until tomorrow. Thanks for your help and I will let you know what happens tomorrow.
dirtyalphaman said:
I really think this is my issue. I tried updating Super SU by flashing 1.75, but I think that's old. It doesn't show up and when I download it from the PLAY store, it says there is no SU Binary. It's too late to fiddle with this now, but I will mess around with it tomorrow. I think I lost my root and it's not trying to let me get it back. But I don't give up that easy. I was looking through the sticky thread to get the most up to date SU flash, but because it's late and I had a lot going on, this project will have to wait until tomorrow. Thanks for your help and I will let you know what happens tomorrow.
Click to expand...
Click to collapse
Sounds like you've figured it out. 1.75 is very old. Latest (stable) is 2.16. There are also beta versions out. I can link you to the latest flashable in the morning.
You may want to re-root via cf auto root if you can't get it to flash, but if you've got access to recovery a flash to the latest supersu should take... it's just not with 1.75 because those binaries are so outdated, it likely can't overpower enforcing selinux. That has been resolved in newer versions. I'm almost positive you'll be fine with a newer supersu/root.
Edit:
here's the link to 2.16 zip download: http://download.chainfire.eu/589/SuperSU/UPDATE-SuperSU-v2.16.zip
And here's a link to chainfire's thread so you can bookmark it & always have access to the latest:
http://forum.xda-developers.com/showthread.php?t=1538053
absinthesummer said:
Sounds like you've figured it out. 1.75 is very old. Latest (stable) is 2.16. There are also beta versions out. I can link you to the latest flashable in the morning.
You may want to re-root via cf auto root if you can't get it to flash, but if you've got access to recovery a flash to the latest supersu should take... it's just not with 1.75 because those binaries are so outdated, it likely can't overpower enforcing selinux. That has been resolved in newer versions. I'm almost positive you'll be fine with a newer supersu/root.
Edit:
here's the link to 2.16 zip download: http://download.chainfire.eu/589/SuperSU/UPDATE-SuperSU-v2.16.zip
And here's a link to chainfire's thread so you can bookmark it & always have access to the latest:
http://forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
Hey, this worked for my root. I installed and updated the SU Binary. It got stuck trying to disable Knox, but I rebooted and went right back to it--Knox was disabled in a few seconds! Thanks again. I will wait until I get home to try to flash again because I would hate to end up stuck at work without my phone working and also because..........my name.......my name is Ken. And I.......I'm a flashaholic...........
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dirtyalphaman said:
Hey, this worked for my root. I installed and updated the SU Binary. It got stuck trying to disable Knox, but I rebooted and went right back to it--Knox was disabled in a few seconds! Thanks again. I will wait until I get home to try to flash again because I would hate to end up stuck at work without my phone working and also because..........my name.......my name is Ken. And I.......I'm a flashaholic...........
Click to expand...
Click to collapse
Awesome! Good luck (and I think we're all flash-aholics)
Thank you for all of your help!!! Flashed the latest DN5 rom and it's working great. I found an issue that might have been preventing me from flashing earlier besides the botched root. My external sd card is having a few issues. A week or so ago it changed to read only and wouldn't let me move any files to or from it. Tonight it wouldn't let me flash the rom, but it worked when moved the rom to the internal storage. So I'm good to go! Can't thank you enough!
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
Sprint S3. 4.4.2.
So I screwed up installing a rom this morning, and ended up having to factory reset my phone. Normally, this wouldn't be a problem, but my authenticator for my accounts (namely my Google account) was on the phone. Again, normally, this wouldn't be an issue since I made a backup using the Philz backup/restore in the recovery. However, trying to restore the backup causes the phone to constantly act up with the error "the process com.google.process.gapps has stopped working", along with any apps I (managed) to try and start. This doesn't stop unless I factory reset the phone.
I've done full resets, wipe clean for a new rom, tried restoring just basic /data folders and such. Nothing has worked so far. any ideas? Am I just screwed until Google recovers my account? Many thanks ahead of time.
PS. This started because I wanted to install a custom rom due to busybox not wanting to install correctly. Something about not being able to verify if everything it needed to install was on the phone. I was rooted and all that jazz, still didn't work. I don't even care about that right now. I just wanna get the phone working properly with the backup if possible.
Deathscreton said:
Sprint S3. 4.4.2.
So I screwed up installing a rom this morning, and ended up having to factory reset my phone. Normally, this wouldn't be a problem, but my authenticator for my accounts (namely my Google account) was on the phone. Again, normally, this wouldn't be an issue since I made a backup using the Philz backup/restore in the recovery. However, trying to restore the backup causes the phone to constantly act up with the error "the process com.google.process.gapps has stopped working", along with any apps I (managed) to try and start. This doesn't stop unless I factory reset the phone.
I've done full resets, wipe clean for a new rom, tried restoring just basic /data folders and such. Nothing has worked so far. any ideas? Am I just screwed until Google recovers my account? Many thanks ahead of time.
PS. This started because I wanted to install a custom rom due to busybox not wanting to install correctly. Something about not being able to verify if everything it needed to install was on the phone. I was rooted and all that jazz, still didn't work. I don't even care about that right now. I just wanna get the phone working properly with the backup if possible.
Click to expand...
Click to collapse
Do a custom restore of /data only after you restore the full ROM. I'm guessing you tried to install a Lollipop ROM? As for busybox you need to wait for it to load everything and then press Smart Install.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My ROMs: Wicked X & Wicked S5 Xperience
help needed
this may not be the right place to post this question but i need help and all the other threads on this topic are seriously outdated. im trying to find a root method for a boost samsung galaxy s3 running 4.4.2. baseband version is L710VPUCNJ3. tried a method on a root guide on another thread that uses odin and philz recovery but i cant get it to work. the thread is pretty old, but theres some recent activity. any help or fingers pointed in the right direction are greatly appreciated. thank you.
-Gill
bilgerryan said:
Do a custom restore of /data only after you restore the full ROM. I'm guessing you tried to install a Lollipop ROM? As for busybox you need to wait for it to load everything and then press Smart Install.
My ROMs: Wicked X & Wicked S5 Xperience
Click to expand...
Click to collapse
That's the thing, the rom didn't complete the install. At least I don't think it did. Maybe it installed certain parts of itself that don't match up with the stock rom, so doing a full reset works, but doing a restore doesn't? I don't know. All I know is that the rom didn't work.
Deathscreton said:
That's the thing, the rom didn't complete the install. At least I don't think it did. Maybe it installed certain parts of itself that don't match up with the stock rom, so doing a full reset works, but doing a restore doesn't? I don't know. All I know is that the rom didn't work.
Click to expand...
Click to collapse
Go into Recovery. Restore Nandroid. Then go to Custom Restore. Uncheck everything but Data. Click on your Nandroid. Then click on the first data partition. Reboot. Profit.
Lollipop ROMs encrypt data whether they boot or not.
My ROMs: Wicked X & Wicked S5 Xperience
bilgerryan said:
Go into Recovery. Restore Nandroid. Then go to Custom Restore. Uncheck everything but Data. Click on your Nandroid. Then click on the first data partition. Reboot. Profit.
Lollipop ROMs encrypt data whether they boot or not.
My ROMs: Wicked X & Wicked S5 Xperience
Click to expand...
Click to collapse
I'll give that a shot. thanks for the advice. I'll post if it worked.
Deathscreton said:
I'll give that a shot. thanks for the advice. I'll post if it worked.
Click to expand...
Click to collapse
If not you'll need to wipe your internal SD. That's where the encryption takes place.
My ROMs: Wicked X & Wicked S5 Xperience
bilgerryan said:
Go into Recovery. Restore Nandroid. Then go to Custom Restore. Uncheck everything but Data. Click on your Nandroid. Then click on the first data partition. Reboot. Profit.
Lollipop ROMs encrypt data whether they boot or not.
My ROMs: Wicked X & Wicked S5 Xperience
Click to expand...
Click to collapse
That didn't work. Process still kept crashing. I did manage to get into my account so I could change the phone number. this way, I should be able to remove the authenticator, or at least transfer it over to my phone again. Thanks for the help.
PS. It wasn't lollipop. Forgot to mention it. It was CyanogenMod 10 I was trying to install. Failed before it even started really. As well, how would this setup have worked if restoring and using the custom restore would have restored the same information? Just curious.
Deathscreton said:
That didn't work. Process still kept crashing. I did manage to get into my account so I could change the phone number. this way, I should be able to remove the authenticator, or at least transfer it over to my phone again. Thanks for the help.
PS. It wasn't lollipop. Forgot to mention it. It was CyanogenMod 10 I was trying to install. Failed before it even started really. As well, how would this setup have worked if restoring and using the custom restore would have restored the same information? Just curious.
Click to expand...
Click to collapse
I'm not sure why it works, it was suggested to me by someone else, but did some reason it does. If you're not using Lollipop then it's irrelevant.
My ROMs: Wicked X & Wicked S5 Xperience
Evvery time I have flashed ANY aosp ROM, I've needed to format my internal sd card when flashing a new ROM. No matter what version it was. It wont hurt to try that.