I'm facing a bug eversince i updated to JB so instead of doing something about it i decided to flash a custom rom but since then i got bored with flashing and stuff and now want to return to my stock rom as i have a nandroid back of it so i want to do a factory reset to see if it removes the bug but i don't know if that will remove the root or not and since you may be helpfull the bug that i'm facing is that on my stock rom my s3 doesn't seem to get any charge even after an hour of bieng plugged in
sher111000 said:
I'm facing a bug eversince i updated to JB so instead of doing something about it i decided to flash a custom rom but since then i got bored with flashing and stuff and now want to return to my stock rom as i have a nandroid back of it so i want to do a factory reset to see if it removes the bug but i don't know if that will remove the root or not and since you may be helpfull the bug that i'm facing is that on my stock rom my s3 doesn't seem to get any charge even after an hour of bieng plugged in
Click to expand...
Click to collapse
When you move from custom rom to stock rom, you lose root access. It means you have to root again.
Moreover when you restore stock rom, nandroid back up is also lost
Sent from my GT-I9300 using Tapatalk 2
Related
just updated to the latest Saurom for samsung note at&T and lost my root and my contacts for some reason! I've flashed many roms and have always had my contacts back after entering my gmail account! I'm sill on the rom but no way to boot into cwm to reflash any idea's
Got it
I had to run unroot then reboot and cwm to get root back... Then logged onto my Gmail and went to contacts and did a restore from an earlier time and it brought back my contacts then I was able to get them on my phone
How in the world do you flash a custom ROM and end up withOUT root? I've been roming since my G1 days and have never heard of this, didn't even think it was possible! Regardless, its good thatbyou got it fixed, and even better that you had the sense to come back and report how you remedied the situation. Most people don't do that and anyone looking for a solution in the future are screwed.
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Ask in that forum
same thing happened to me after i flashed the rom :/ What did you use to unroot and root again through cwm? thanks.
Hey guys,
last night i noticed there was an update available for my phone, so without thinking i unrooted my phone through superuser without flashing back to my backup. So now the CWM app is gone and I don't have any root privileges so I don;t know how to get back to stock. Can anyone help?
Flash stock Rom with Odin
FIXED !!! thanks
ok, ill try to make it simple, ive been working on my tab since 1pm and its 11pm and am still f*cked up
So to make a long story a short one here is what happened
Since i updated to ICS, everything was fine except for flash player not playing my videos anymore, i found a thread explaining how to fix it BUT i didnt reinstall CWM when i update so i actually did (by mistake) a complete reset on my tab (losing all datas, picture, apps etc)
I was wise enough to make a backup on sept 30 b4 i update to ICS
so i found how to re root the tab on ICS, i did it with success, install CWM with odin
then i took rom manager and restore my apps and data and this is where it got complicated
the md5 mismatch popped out, founded how to fix it using terminal emulator, did it then restore
all my apps and settings where back up except for my pictures (its okay i had them saved on my pc)
so i thought i would simply re update to ICS and my life would be great......NOT !
now i keep getting an error: system UI has stopped
went back to recovery tried to wipe everything to factory reset and start all over again,
well my tab is now reset BUT that freaking system UI error keeps coming up and i cant do nothing
the tab is reset but cwm is still installed and i can still restore from my backup so actually i guess it mean the tab is not fully reset.
more, when i plug the usb cable, it doesnt show up on my pc so i cant explore the tab manually
now i dont know what to do, i've been googling for the past 2 hours, cant find a decent solution.
All i want is toget rid of that system ui error, reset the tab and then try again to restore my old backup so i can have my apps then re update to ICS
please, am really desparate, i need help
EDIT :
i think i might have brick my tab
actually while i was waiting for a reply, i went back into Odin and flashed twrp recovery that i got from another website
then i went into recovery and tried again to wipe everythig (cache, devlak and factory reset) i was then back to honeycomb 3.1 but still getting that systemui error
then i've hit system wipe wich has wipe my rom so now my tab isnt rebooting
its stuck on the samsung galaxy tab screen
while i wait for your help, im looking around to find and set back the stock rom
i feel really dumb atm
Try re-install your rom again by using odin
Sent from my GT-P7500 using xda premium
If it were me I would flash stock recovery and stock Honeycomb image and then manually update to ICS using OTA's if stock rooted ICS was the goal. I would not mess with ROM manager or restore apps and data using it as it is likely where you started to get into trouble.
I have seen the system ui error message before myself and it was when I had restored all apps and data blindly over a new install of ICS using titanium. I had to reflash the ROM again and opted instead to manually install the apps after which I restored data for them individually using titanium. Its a pain to do it but the best way to ensure a stable end result. From that point on the lesson learned was to not restore all apps but just the missing ones.
Sent from my SCH-I905 using Tapatalk 2
muzzy996 said:
If it were me I would flash stock recovery and stock Honeycomb image and then manually update to ICS using OTA's if stock rooted ICS was the goal. I would not mess with ROM manager or restore apps and data using it as it is likely where you started to get into trouble.
I have seen the system ui error message before myself and it was when I had restored all apps and data blindly over a new install of ICS using titanium. I had to reflash the ROM again and opted instead to manually install the apps after which I restored data for them individually using titanium. Its a pain to do it but the best way to ensure a stable end result. From that point on the lesson learned was to not restore all apps but just the missing ones.
Sent from my SCH-I905 using Tapatalk 2
Click to expand...
Click to collapse
thanks, after i sent that post, i finaly found the stock ICS rom for my tab and installed it,
now am back to the point where i want to restore my apps/data/pictures from my backup that i did with nandroid
thats where i need help, i still get the md5 mismatch but i know how to fix it using terminal emulator but i think the system ui problem comes up because the backup is from a honycomb 3.1 or 3.2 and now the tab is running ICS.
if i reinstall all my apps manually, do you know how i could restore my data from the nandroid backup ?
am trying to find my original 3.1 honeycomb rom but it seem that it doesnt exist on sammobile
Just manually reinstall everything and set it back up without restoring data. Otherwise you're looking for trouble in my opinion.
Just return back to original stock.
fbramm said:
Just return back to original stock.
Click to expand...
Click to collapse
thats what i did, i found one, then i restored my apps, then i updated to ICS
found a version of flash player working, installed it, and now am happy
all i have to do is to set back my home pages
guys i gotta say, i love this forum
thanks to all, actually, i did it alone but i couldnt do it without reading so many topics all around this forum
so THANK YOU:highfive:
and if someone need help to :
get the original rom for p7500R
get the ICS stock rom provided by samsung
need a working version of flash player on ICS
need help to root an ICS tab 10.1
I can help you ! just send me a pm :good:
Hey y'all.
So many threads ago I posted up on how to root a SGS2 I900P, which in the end I did no problems. The ONLY problem I encounted where I'd flash a different ROM and wanted to restore back to my factory loaded Orange UK rom, which when I restored it with no problems it just went through the 'boot loop' phase. I read up that this is caused due to a faulty emmc 'bricking bug' and luckily it was only "soft bricked".
Cut the long story short I managed to re-flash the Orange (UK) carrier firmware (after many USB cable changes and port swaps and fails) via Odin and retain my previously installed apps and so on and had to re-root. Is there a method or some sort of fix for the emmc bug issue for future wipes/restores ?
Something new I learnt in all that process too,
muffintastic said:
Hey y'all.
So many threads ago I posted up on how to root a SGS2 I900P, which in the end I did no problems. The ONLY problem I encounted where I'd flash a different ROM and wanted to restore back to my factory loaded Orange UK rom, which when I restored it with no problems it just went through the 'boot loop' phase. I read up that this is caused due to a faulty emmc 'bricking bug' and luckily it was only "soft bricked".
Cut the long story short I managed to re-flash the Orange (UK) carrier firmware (after many USB cable changes and port swaps and fails) via Odin and retain my previously installed apps and so on and had to re-root. Is there a method or some sort of fix for the emmc bug issue for future wipes/restores ?
Something new I learnt in all that process too,
Click to expand...
Click to collapse
To avoid brickbug is by flashing JB 4.1.2. (good alternative!)
But if you really like ICS then i suggest you move back to 4.0.3. There is no avoiding brickbug on 4.0.4.
If you have rooted it, you can check with 'Brickbug check' app on google play, to see if you have sane (or insane) chip (brickbug or not), cause most custom kernels and roms have found a solution to this bug, and use it on their roms/kernels. Which means on those you can safely wipe and restore etc.. (but check brickbug app first on google play)
Yep. Don't wipe a rooted phone running 4.0.4. And if you're really paranoid, don't even wipe a non-rooted phone running 4.0.4 (Entropy mentioned at least one case he knew of where someone borked their phone doing a wipe on a phone running 4.0.4 via stock Android recovery, tho it seems to be very rare).
The TL;DR is don't run rooted stock 4.0.4 if you mess with your phone in any way.
I know that's not a fix, but that's because there isn't one. Some chips aren't susceptible to the bug; there's an app floating around here somewhere/Google Play where you can check which chip you have (seems to be more that are susceptible).
Your 1st paragraph is a load of crap.Bootloop has nothing to do with "brickbug".More like by you not running kernel cleaning script,or not factory resetting before/after flashing a new rom.
As mentioned by others,just dont have 4.0.4 running on your phone.So you are still left with over 100 custom/stock roms to choose from........lol
Was the backup of JB? Or ICS? OP doesn't say. If it was JB, I'd be willing to bet that the bootloop was due to an attempt to restore the stock rom, but without restoring preload.
Sent from a galaxy far, far away
Hopper8 said:
Was the backup of JB? Or ICS? OP doesn't say. If it was JB, I'd be willing to bet that the bootloop was due to an attempt to restore the stock rom, but without restoring preload.
Sent from a galaxy far, far away
Click to expand...
Click to collapse
Im not sure Hopper.I am leaning towards the restore would be "cancelled" due to not being complete,rather than it succeeding leading to bootloop.
But hes not said.
And he cant get "factory" rom with a restore as it didnt come with cwm lol.
Sorry to clear things up.. I updated it to 4.1.2 via Kies many months ago. I used PhilZ method to root, no problem. Few months down the line since then I put LiquidSmooth 2.4 (few days ago) then restored a backup from PhilZ recovery and put 4.1.2 and everything back on no problem. Then restarted the phone and it when into a boot loop of the Orange and Samsung logo.
I'm not stupid as I've rooted my own SGS3 and Samsung Galaxy ACEs etc, Just forgotten to put that info in lol and yes I always use the Factory Reset to install a new rom.
And yes when I managed to get it restored from this so called boot loop (by putting 4.1.2 Orange UK firmeware back on via Odin) the EMMC brick bug is present as i've checked via an app via Google Play. My overall goal is to eliminate this problem or temp fix so I can put different roms on and if I don't like them recovery back to the latest restore without issues.
Are we on the same line now ?
And as we've said, you can't eliminate the problem. You can avoid the problem by not running 4.0.4 stock roms. It's really quite simple, but like a lot of people here you're trying to make it complex when there's no need to.
help me out here please
MistahBungle said:
And as we've said, you can't eliminate the problem. You can avoid the problem by not running 4.0.4 stock roms. It's really quite simple, but like a lot of people here you're trying to make it complex when there's no need to.
Click to expand...
Click to collapse
ok its a long story so i better get started... my friend had his phone rooted and installed a jelly bean version of Paranoid android and he wanted to put kitkat on it, he downloaded the cm11 latest nightly and told me to flash it i proceed to flash the phone but it failed and showed me "error status 7" so the phone couldnt get neither into the previous pa nor in the cm11... after some research and messing with the META INF stuff to sol the status 7 thing i found out that the problem was that he wasnt using a kitkat compatible recovery... i installled it and finally got to flash cm11.. that didnt came out as you may thought the phone showed it had -15246384352 % of battery made a freking glitch when the sreen rotated and it wouldnt recognize either of the sd cards (internal memory or external sd card) so i couldnt flash it again, wipe data/cache wouldnt solve the problem either... i turn into our ol friend odin and flashed stock JB wich worked perfectly except that i had the same issue with the memories... used philz to root the phone again, the try to format /system /data /emmc to check if that was the problem annnnd ta da the phone wont boot :silly: odin keeps failing to flash stock again and i dont jknow what to do....
sorry for the long post but i guess that you might need alll the info you could get for helping me...
thanks a lot
andreshbozo said:
ok its a long story so i better get started... my friend had his phone rooted and installed a jelly bean version of Paranoid android and he wanted to put kitkat on it, he downloaded the cm11 latest nightly and told me to flash it i proceed to flash the phone but it failed and showed me "error status 7" so the phone couldnt get neither into the previous pa nor in the cm11... after some research and messing with the META INF stuff to sol the status 7 thing i found out that the problem was that he wasnt using a kitkat compatible recovery... i installled it and finally got to flash cm11.. that didnt came out as you may thought the phone showed it had -15246384352 % of battery made a freking glitch when the sreen rotated and it wouldnt recognize either of the sd cards (internal memory or external sd card) so i couldnt flash it again, wipe data/cache wouldnt solve the problem either... i turn into our ol friend odin and flashed stock JB wich worked perfectly except that i had the same issue with the memories... used philz to root the phone again, the try to format /system /data /emmc to check if that was the problem annnnd ta da the phone wont boot :silly: odin keeps failing to flash stock again and i dont jknow what to do....
sorry for the long post but i guess that you might need alll the info you could get for helping me...
thanks a lot
Click to expand...
Click to collapse
Here is my situation.
I had 4.1.2 JB. Installed CM11 M8 and CWM_6.0.4.7(coming previously from Siyah) at the end of July. In the beginning of October my phone just shut down. That happened before on the same and previous rom so I wasn't worried. I turned it on and phone was in bootloop. That was strange because the last time that happened I installed Chainfire. So bootloop without any cause..that was strange. I tried making a backup before flashing the ROM. But I got an error. I can't remember but I can dig it somewhere if you want it. I tried then flashing recovery(bad idea) and Odin again reported an error. When I restarted phone I noticed that my Recovery mode was gone. Just gone and with no solution on how to restore it. I tried numerous methods OMAP drivers, heimdall, .pit file method but nothing. So I brought my sgs2 to the store where I bought it and they concluded that it was bad eMMC chip.
Now, your problem reminds me of mine because Odin wouldn't want to flash anything without an error(well, not exactly anything, I managed to flash some partition using Heimdall but it was not sufficient) but it doesn't have to be.
What version of cwm were you using?
hey guys
I recently decided to opt in to flashing 5.0 rom on my device, but ive read somwhere (http://forum.xda-developers.com/tmobile-galaxy-s5/general/warning-flashing-bootloader-modem-t3037034) that people are having trouble restoring backed up roms and even going back to NK2 with full odin wipe. I have also read that flashing a custom 5.0 kernel will resolve this issue. Is that true, i want to know by someone with expirience. And also can i flash custom roms while on 5.0 bootloader if i load it with a custom kernel.
IAM NOT planning on taking the OTA update but rather ViSiON-X Rom http://forum.xda-developers.com/showthread.php?t=2797336.
My main concern is being able to flash roms/restoring/backing up, specifically custom roms not touchwiz based and Kitkat.
THANKS IN ADVANCE
androidfine16 said:
hey guys
I recently decided to opt in to flashing 5.0 rom on my device, but ive read somwhere (http://forum.xda-developers.com/tmobile-galaxy-s5/general/warning-flashing-bootloader-modem-t3037034) that people are having trouble restoring backed up roms and even going back to NK2 with full odin wipe. I have also read that flashing a custom 5.0 kernel will resolve this issue. Is that true, i want to know by someone with expirience. And also can i flash custom roms while on 5.0 bootloader if i load it with a custom kernel.
IAM NOT planning on taking the OTA update but rather ViSiON-X Rom http://forum.xda-developers.com/showthread.php?t=2797336.
My main concern is being able to flash roms/restoring/backing up, specifically custom roms not touchwiz based and Kitkat.
THANKS IN ADVANCE
Click to expand...
Click to collapse
I downloaded 5.0. Was NOT satisfied and put KitKat back on. No problems doing that at all but I an NOT rooted.
androidfine16 said:
hey guys
I recently decided to opt in to flashing 5.0 rom on my device, but ive read somwhere (http://forum.xda-developers.com/tmobile-galaxy-s5/general/warning-flashing-bootloader-modem-t3037034) that people are having trouble restoring backed up roms and even going back to NK2 with full odin wipe. I have also read that flashing a custom 5.0 kernel will resolve this issue. Is that true, i want to know by someone with expirience. And also can i flash custom roms while on 5.0 bootloader if i load it with a custom kernel.
IAM NOT planning on taking the OTA update but rather ViSiON-X Rom http://forum.xda-developers.com/showthread.php?t=2797336.
My main concern is being able to flash roms/restoring/backing up, specifically custom roms not touchwiz based and Kitkat.
THANKS IN ADVANCE
Click to expand...
Click to collapse
I updated via Odin tar file.
About restoring from a nandroid custom recovery backup:
I think/thought I mentioned this in that first thread you linked, but, you cannot in any way restore an old backup onto a new version of android irregardless the device or recovery. Say the system apk, settings apk uses a file named xyz.dat in KitKat, it saves that file to your /data directory. You now go ahead and flash Lollipop which now that same system apk, the settings apk uses a file named yzx.dat, you go and restore your backup restoring the file xyz.dat. Now the settings apk which is a system apk, cannot find this file and runs into a bootloop because not finding the file should never happen but since you went behind its back to remove that file, you confused it majorly.
I use Titanium Backup to restore my apps, best money ever spent.
I personally went back to KitKat, cause, well, I missed xposed more than i thought i would lol. Everything just worked the way I wanted it to with xposed.
I did have to Odin flash a KitKat based ROM in order for it to work though. After that, I restored my full nandroid backup and everything is working again.
My recommendations to you:
1. Take a FULL backup using TWRP or other custom recovery, this includes backing up your system, data, and boot.
2. Flash the Lollipop update using Odin.
3. DO NOT WIPE DATA
4. Reboot.
You should see "android is upgrading" and have a Lollipop build with all your apps still there. i got a few force closes so I ended up wiping my data, but those apps that forced closed were all root apps that were looking for system files that didn't exist anymore.
elesbb said:
I updated via Odin tar file.
About restoring from a nandroid custom recovery backup:
I think/thought I mentioned this in that first thread you linked, but, you cannot in any way restore an old backup onto a new version of android irregardless the device or recovery. Say the system apk, settings apk uses a file named xyz.dat in KitKat, it saves that file to your /data directory. You now go ahead and flash Lollipop which now that same system apk, the settings apk uses a file named yzx.dat, you go and restore your backup restoring the file xyz.dat. Now the settings apk which is a system apk, cannot find this file and runs into a bootloop because not finding the file should never happen but since you went behind its back to remove that file, you confused it majorly.
I use Titanium Backup to restore my apps, best money ever spent.
I personally went back to KitKat, cause, well, I missed xposed more than i thought i would lol. Everything just worked the way I wanted it to with xposed.
I did have to Odin flash a KitKat based ROM in order for it to work though. After that, I restored my full nandroid backup and everything is working again.
My recommendations to you:
1. Take a FULL backup using TWRP or other custom recovery, this includes backing up your system, data, and boot.
2. Flash the Lollipop update using Odin.
3. DO NOT WIPE DATA
4. Reboot.
You should see "android is upgrading" and have a Lollipop build with all your apps still there. i got a few force closes so I ended up wiping my data, but those apps that forced closed were all root apps that were looking for system files that didn't exist anymore.
Click to expand...
Click to collapse
Yeah I avoided lollipop all together. People seem to be having too many problems with it.I installed NK2 via Odin and now rooted/exposed. Runs smooth and I can flash other Roms.
But I do have this one issue. My auto rotation rodent seem to be working I tried everything I can think of. At first boot it works for 10 minutes or 5 sometimes. Than it shuts down completely. Accelerometer isn't working either. No temple run movement or asphalt 8 (sucks). I did sensor firmwate update and ran samsung diagnostic. The sensor seem to be at 0,0 on x and y axis. At first boot they work fine though. Any help please. I even tried different kernel and software Roms to no Vail. And I don't think it's hardware cause it works for brief moments.
Sent from my SM-G900T using XDA Free mobile app
I let the lollipop update happen.. Used the last day and everything seems fine but I can't use Screen mirroring which I use alot.. anyway I downloaded the stock 4.4.2 md5 and odin completely successfully writes it and after it reboots it is stuck at the Tmobile 4gLTE bootscreen.. I've rebooted it and waited a long time.. as well as rewriting. Guess I'll have to download the stock lollipop tar and hope it boots
tri0xinn said:
I let the lollipop update happen.. Used the last day and everything seems fine but I can't use Screen mirroring which I use alot.. anyway I downloaded the stock 4.4.2 md5 and odin completely successfully writes it and after it reboots it is stuck at the Tmobile 4gLTE bootscreen.. I've rebooted it and waited a long time.. as well as rewriting. Guess I'll have to download the stock lollipop tar and hope it boots
Click to expand...
Click to collapse
The 4.4.2 .tar is a "non-wipe" .tar. You need to go into stock recovery and do a factory data reset after flashing.
Did the trick, thanks!
muniz_ri said:
The 4.4.2 .tar is a "non-wipe" .tar. You need to go into stock recovery and do a factory data reset after flashing.
Click to expand...
Click to collapse
Does downgrading like this trips Knox?
Thanks
chiquito3 said:
Does downgrading like this trips Knox?
Thanks
Click to expand...
Click to collapse
I downgraded my wife's phone using the official 4.4.2 firmware from sammobile, and it did NOT trip knox.