I rooted my Nexus S 4G and was running MIUI but decided to go back to the stock ROM for awhile. When attempting to go back over to MIUI, I can no longer get into Recovery and now the stock ROM won't boot either, stuck on loading animation.
I'm on a Mac, is there anything I can do? Thanks
redsprocket said:
I rooted my Nexus S 4G and was running MIUI but decided to go back to the stock ROM for awhile. When attempting to go back over to MIUI, I can no longer get into Recovery and now the stock ROM won't boot either, stuck on loading animation.
I'm on a Mac, is there anything I can do? Thanks
Click to expand...
Click to collapse
Boot into boot loader. Use fastboot to flash a recovery. Reinstall your rom of choice.
Thanks, I was able to get Recovery working again and after trying a few things was able to get back into my ROM, but I'm still not able to flash back and forth different ROMs. Seems my root isn't sticking with this method:
http://forum.xda-developers.com/showthread.php?t=970237
The root file on there is for ecalir/froyo only. Go into rm>download rom> superuser and download "superuser 2.3.6.3 efgh" and that should work.
Sent from my Nexus S 4G using xda premium
redsprocket said:
Thanks, I was able to get Recovery working again and after trying a few things was able to get back into my ROM, but I'm still not able to flash back and forth different ROMs. Seems my root isn't sticking with this method:
http://forum.xda-developers.com/showthread.php?t=970237
Click to expand...
Click to collapse
did you wipe data(factory reset) before flashing different roms? you have to. you dont need to wipe data only when updating the same rom.
Ahhh, that must be my problem. I got so used to not wiping on MIUI that I assumed I could jump between ROMs without wiping. Thank you and apologies for the remedial posts.
redsprocket said:
Ahhh, that must be my problem. I got so used to not wiping on MIUI that I assumed I could jump between ROMs without wiping. Thank you and apologies for the remedial posts.
Click to expand...
Click to collapse
no apologies needed, thats why we're here
First off, I searched. I can't seem to find any documentation on special flashing procedures. I'm not new to flashing, in fact i'd say I'm addicted to it on my other phones.
Every ROM I try to flash on 2.3.6 rooted using Atrix bootloader/CWM makes my device unbootable. I did the OTA to 2.3.6 and used the moto fail approach to root.
I'm wiping dalvik/cache/data, standard stuff. Every time I've had to use RSD Lite to get back to working.
Am I missing another step that's known to the community but not included in flashing instructions?
ventowtf said:
First off, I searched. I can't seem to find any documentation on special flashing procedures. I'm not new to flashing, in fact i'd say I'm addicted to it on my other phones.
Every ROM I try to flash on 2.3.6 rooted using Atrix bootloader/CWM makes my device unbootable. I did the OTA to 2.3.6 and used the moto fail approach to root.
I'm wiping dalvik/cache/data, standard stuff. Every time I've had to use RSD Lite to get back to working.
Am I missing another step that's known to the community but not included in flashing instructions?
Click to expand...
Click to collapse
Read this hope it helps
http://forum.xda-developers.com/showthread.php?t=1511616
Trail and error is the only way I learn. Running sv6 with a little flavor
ventowtf said:
First off, I searched. I can't seem to find any documentation on special flashing procedures. I'm not new to flashing, in fact i'd say I'm addicted to it on my other phones.
Every ROM I try to flash on 2.3.6 rooted using Atrix bootloader/CWM makes my device unbootable. I did the OTA to 2.3.6 and used the moto fail approach to root.
I'm wiping dalvik/cache/data, standard stuff. Every time I've had to use RSD Lite to get back to working.
Am I missing another step that's known to the community but not included in flashing instructions?
Click to expand...
Click to collapse
So, after you flash, your phone won't boot at all, or does it boot to Moto boot image and hang? Sounds like you have a good handle on the flashing steps. Not sure why it won't boot. Which roms have you tried that this has happened with?
Sent from my MB865 using xda's premium carrier pigeon service
Apex_Strider said:
So, after you flash, your phone won't boot at all, or does it boot to Moto boot image and hang? Sounds like you have a good handle on the flashing steps. Not sure why it won't boot. Which roms have you tried that this has happened with?
Sent from my MB865 using xda's premium carrier pigeon service
Click to expand...
Click to collapse
It just gets stuck on the Moto boot image. I thought I was being inpatient so i left it for 30 minutes but it didn't progress past that.
I tried Romulus/Remus and Lithium to no success.
Whenever you first used A2 bootstrap did you select Bootstrap recovery first and did it give you Success before selecting reboot recovery?
JRW 28 said:
Whenever you first used A2 bootstrap did you select Bootstrap recovery first and did it give you Success before selecting reboot recovery?
Click to expand...
Click to collapse
yes, I got the success message from bootstrap.
so after following the instructions to install CWM on every boot, I can install a ROM now but it just gets stuck on the loading screen. i'm doing a factory reset to see if that fixes it. already tried wiping dalvik and cache.
You are doing a factory wipe before you install the ROM right? The factory wipe in CWM wipes cache also. Then just do dalvik.
Sent from my MB865 using xda premium
Try replacing your sdcard? Or remove the sdcard when booting up
How do you unroot the GS3 and get back to stock unrooted? I am currently just stock rooted. I'm just done with flashing and don't want to worry about something happening to my phone while I'm rooted, and am sick of it not being able to take the VZW update on a daily basis. I understand there is an unroot in the superuser app, is it as simple as clicking that and it will unroot by itself? Is there more I need to do? Thanks for your help!
Bump
Many ways to unroot, you could use SuperSU and select remove root, then uninstall the app then reboot or use universal unroot app from play store.
buhohitr said:
Many ways to unroot, you could use SuperSU and select remove root, then uninstall the app then reboot or use universal unroot app from play store.
Click to expand...
Click to collapse
Thank you. Once you perform either or these methods, can you still root again in the future if you decide to?
I unrooted through SuperSU. Went to install the VZW update and it went into Teamwin Recovery. When it was trying to update the software and running all the checks, etc. I saw "checking for MD5 file...no MD5 file found." What is this and is this what is causing me to not be able to take the update? Am I supposed to still have Teamwin Recovery? How do I get rid of it? Root Checker said I'm unrooted now.
Where do I go from here? Thanks again!
Bump
irl5fan said:
Bump
Click to expand...
Click to collapse
Flash this file:
http://forum.xda-developers.com/showthread.php?t=2795659
With this guide:
http://forum.xda-developers.com/showthread.php?t=2586319
Then you're unrooted and up to date, but you'll erase all of your data. So backup all the pictures and music you want to keep.
Sent from my HTC6525LVW using Tapatalk
BadUsername said:
Flash this file:
http://forum.xda-developers.com/showthread.php?t=2795659
With this guide:
http://forum.xda-developers.com/showthread.php?t=2586319
Then you're unrooted and up to date, but you'll erase all of your data. So backup all the pictures and music you want to keep.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
None of the links to the files have anything in them. Is there another way? Any other location to find these files?
irl5fan said:
None of the links to the files have anything in them. Is there another way? Any other location to find these files?
Click to expand...
Click to collapse
You're right, try to search for it in Google. I didn't bookmark anything.
Sent from my HTC6525LVW using Tapatalk
irl5fan said:
I unrooted through SuperSU. Went to install the VZW update and it went into Teamwin Recovery. When it was trying to update the software and running all the checks, etc. I saw "checking for MD5 file...no MD5 file found." What is this and is this what is causing me to not be able to take the update? Am I supposed to still have Teamwin Recovery? How do I get rid of it? Root Checker said I'm unrooted now.
Where do I go from here? Thanks again!
Click to expand...
Click to collapse
Dude.... You shouldn't be rooting if you don't know what TWRP is.... LMAO!
You need to flash stock recovery to take the OTA, you should of backed it up when you first flashed TeamWin to the device and it would of been a simple reflash through Flashify and it would of been good.
Now you need to download Odin (A PC flash tool) and reflash through that programme....
Sent From V500
Using XDA App
unroot gs3
LiamAtkins90 said:
Dude.... You shouldn't be rooting if you don't know what TWRP is.... LMAO!
You need to flash stock recovery to take the OTA, you should of backed it up when you first flashed TeamWin to the device and it would of been a simple reflash through Flashify and it would of been good.
Now you need to download Odin (A PC flash tool) and reflash through that programme....
When did I say I didn't know what TWRP is? So if I flash stock recovery will that get me where I want to be...stock unrooted and able to take OTA updates. I never did flash any custom roms or anything while I was rooted.
Click to expand...
Click to collapse
irl5fan said:
When did I say I didn't know what TWRP is? So if I flash stock recovery will that get me where I want to be...stock unrooted and able to take OTA updates. I never did flash any custom roms or anything while I was rooted.
Click to expand...
Click to collapse
Sorry, I realise my reply come of a little arsey, I will explain.
If you take the OTA in stock recovery it will go through, but as soon as you flash a custom recovery you give up the right to an OTA whilst on said recovery,
Instead you either:
1. Flash a custom ROM, and do updates with there ROM team.
2. Wait for stock ROM to come in a flashable zip for Custom Recoverys.
If you have root and stock recovery and take it, sometime it will go through, sometimes it won't.... Like Samsung Knox for example....
Sometimes it will take but as soon as you boot back up you will have no root.
If you OTA in Custom Recovery it will boot to TWRP and most likely abort straight away and bad things will ocure.
Mixed Partitions no ROM etc...
Now back to your question....
Yeah Stock non rooted you can take OTA (but in Samsung's case, they have a flash counter, that keeps track of system mods)
Best bet would be flash through Odin, to out-the-box firmware and take the OTA from there...to avoid any conflicts with the system.
I do apologise for my earlier post mate, write back if you got it upgraded.
LiamAtkins90 said:
Sorry, I realise my reply come of a little arsey, I will explain.
If you take the OTA in stock recovery it will go through, but as soon as you flash a custom recovery you give up the right to an OTA whilst on said recovery,
Instead you either:
1. Flash a custom ROM, and do updates with there ROM team.
2. Wait for stock ROM to come in a flashable zip for Custom Recoverys.
If you have root and stock recovery and take it, sometime it will go through, sometimes it won't.... Like Samsung Knox for example....
Sometimes it will take but as soon as you boot back up you will have no root.
If you OTA in Custom Recovery it will boot to TWRP and most likely abort straight away and bad things will ocure.
Mixed Partitions no ROM etc...
Now back to your question....
Yeah Stock non rooted you can take OTA (but in Samsung's case, they have a flash counter, that keeps track of system mods)
Best bet would be flash through Odin, to out-the-box firmware and take the OTA from there...to avoid any conflicts with the system.
I do apologise for my earlier post mate, write back if you got it upgraded.
Click to expand...
Click to collapse
No problem. This has been a long drawn out process over the past few months, so forgive me for all the questions and details of events. This is where I'm at. When I started the unrooting process, as stated above, used triangle away to reset the counter and then I unrooted through SuperSU. According to root checker apps I am unrooted, but I believe my bootloader is still unlocked. And obviously still have TWRP. Phone Info: SCH-I535, Version 4.1.2, Baseband I535VRBMF1.
Given that info, do I still flash the stock firmware (from here?--->) (http://downloadandroidfiles.org/download-sch-i535-vzw-i535vrbmb1-1360821900-zip/) and then flash stock recovery? Does flashing stock firmware re-lock my bootloader? Thanks for your help.
irl5fan said:
No problem. This has been a long drawn out process over the past few months, so forgive me for all the questions and details of events. This is where I'm at. When I started the unrooting process, as stated above, used triangle away to reset the counter and then I unrooted through SuperSU. According to root checker apps I am unrooted, but I believe my bootloader is still unlocked. And obviously still have TWRP. Phone Info: SCH-I535, Version 4.1.2, Baseband I535VRBMF1.
Given that info, do I still flash the stock firmware (from here?--->) (http://downloadandroidfiles.org/download-sch-i535-vzw-i535vrbmb1-1360821900-zip/) and then flash stock recovery? Does flashing stock firmware re-lock my bootloader? Thanks for your help.
Click to expand...
Click to collapse
So you used Triangle Away to clear the flash counter?
Great, so the only thing you need now is the stock recovery image for your device,
I would say just flash the stock recovery image through Odin, but their is that many models
with different numbers, it would be easier flashing 4.1.2 firmware again through Odin.
In future bud if your gonna be messing with ROMs and Recovery files I recommend this:
Flash recovery with this:
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en_GB
(Backup Stock Recovery 1st)
Backup Stock EVERYTHING, Boot, System, EFS, Data etc in Recovery of choice.
Move backup to computer or cloud storage.
Then all you need to do to go back is triangle away, restore stock backup, restore stock recovery, unroot through SuperSU.
And the OTA should work.
Sent From V500
Using XDA App
LiamAtkins90 said:
So you used Triangle Away to clear the flash counter?
Great, so the only thing you need now is the stock recovery image for your device,
I would say just flash the stock recovery image through Odin, but their is that many models
with different numbers, it would be easier flashing 4.1.2 firmware again through Odin.
In future bud if your gonna be messing with ROMs and Recovery files I recommend this:
Flash recovery with this:
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en_GB
(Backup Stock Recovery 1st)
Backup Stock EVERYTHING, Boot, System, EFS, Data etc in Recovery of choice.
Move backup to computer or cloud storage.
Then all you need to do to go back is triangle away, restore stock backup, restore stock recovery, unroot through SuperSU.
And the OTA should work.
Sent From V500
Using XDA App
Click to expand...
Click to collapse
I just want to clarify before I go ahead and do anything and get myself into a pickle. Are you saying to flash 4.1.2 firmware instead of stock recovery? Or am I still flashing both of them? If so, which order? Does that link I posted look like it is the correct firmware to you? Also, I have an older version of Odin on my computer, does that matter or should I get the newer one first?
irl5fan said:
I just want to clarify before I go ahead and do anything and get myself into a pickle. Are you saying to flash 4.1.2 firmware instead of stock recovery? Or am I still flashing both of them? If so, which order? Does that link I posted look like it is the correct firmware to you? Also, I have an older version of Odin on my computer, does that matter or should I get the newer one first?
Click to expand...
Click to collapse
Stock recovery is in the firmware file mate, when you flash the firmware it flashes the recovery, clears internal SD card (move pictures, videos, music to PC) & Radio, Modem, EFS basically everything on the phone gets flashed to how it is when you buy it from a store. Whats your model number?
And no it shouldn't matter, I've never seen any issues rise with using older Odin Programmes.
Do you have experience using Odin?
If not:
http://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
That guide covers how to use it, where to place the firmware file etc.
Any questions just ask
Sent From V500
Using XDA App
LiamAtkins90 said:
Stock recovery is in the firmware file mate, when you flash the firmware it flashes the recovery, clears internal SD card (move pictures, videos, music to PC) & Radio, Modem, EFS basically everything on the phone gets flashed to how it is when you buy it from a store. Whats your model number?
And no it shouldn't matter, I've never seen any issues rise with using older Odin Programmes.
Do you have experience using Odin?
If not:
http://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
That guide covers how to use it, where to place the firmware file etc.
Any questions just ask
Sent From V500
Using XDA App
Click to expand...
Click to collapse
My model number is SCH-I535. I have used Odin before, but I'll take a look at the guide just to make sure. Thanks for your help!
LiamAtkins90 said:
Stock recovery is in the firmware file mate, when you flash the firmware it flashes the recovery, clears internal SD card (move pictures, videos, music to PC) & Radio, Modem, EFS basically everything on the phone gets flashed to how it is when you buy it from a store. Whats your model number?
And no it shouldn't matter, I've never seen any issues rise with using older Odin Programmes.
Do you have experience using Odin?
If not:
http://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
That guide covers how to use it, where to place the firmware file etc.
Any questions just ask
Sent From V500
Using XDA App
Click to expand...
Click to collapse
I just wanted to say thanks for helping out someone in our forums with the VZW variant, I was going to chime in but I see you had things under control. It's just odd to see so many people in our forums who don't have the version we have
From my Wicked S3 on SOKP
ShapesBlue said:
I just wanted to say thanks for helping out someone in our forums with the VZW variant, I was going to chime in but I see you had things under control. It's just odd to see so many people in our forums who don't have the version we have
From my Wicked S3 on SOKP
Click to expand...
Click to collapse
No problem, glad I can help.
Verizon edition Models tend to get overlooked as oppose to International variants which is a shame, I think both should get equal recognition. Not just Sammy Verizon, most Verizon models and also Google Play Edition Model Phones/Tablets get pushed aside.... Crying shame.
LiamAtkins90 said:
Stock recovery is in the firmware file mate, when you flash the firmware it flashes the recovery, clears internal SD card (move pictures, videos, music to PC) & Radio, Modem, EFS basically everything on the phone gets flashed to how it is when you buy it from a store. Whats your model number?
And no it shouldn't matter, I've never seen any issues rise with using older Odin Programmes.
Do you have experience using Odin?
If not:
http://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
That guide covers how to use it, where to place the firmware file etc.
Any questions just ask
Sent From V500
Using XDA App
Click to expand...
Click to collapse
Everything worked out great, flashed the stock firmware and was able to take the OTA. Thank you so much for your help, it's greatly appreciated!
ok. is it even possible to have two recoveries running at once? On normal boot-up, I get the safestrap screen asking to continue or enter recovery. I have flashed TWRP and I can get to TWRP by fastbooting and entering recovery that way. I feel i have set myself up to brick in the hard sense. I just unlocked w/ sunshine and am trying to make a backup before i really start screwing stuff up.
If you're unlocked with TWRP then safestrap is redundant since you can't utilize the extra ROM slots.
Sent from my XT1080
that was kind of my thoughts too. I did remove safestrap manually. Im still tying to update with the latest OTA, but with no luck. thanks.
teerout said:
that was kind of my thoughts too. I did remove safestrap manually. Im still tying to update with the latest OTA, but with no luck. thanks.
Click to expand...
Click to collapse
The update isn't going through because you have TWRP installed. Flash to stock recovery and try again.
Sorry I left that out, I have removed TWRP. I have returned to as stock as I can. Flashed back to factory. Still no success on OTA update. Im hunting for the files now and i will hopefully flash it myself.
Moto Droid Maxx firmware found here->https://motorola-global-portal.cust..._detail/a_id/95417/p/30,6720,8882/reg/1192476 - you have to sign in...
Is there a difference between the Samsung J327P and the Samsung J320P? I'm trying to determine a difference so I can find the correct root file and process to root my phone. Every way I've tried so far has gotten stuck at trying to unlock my bootloader.
Vikings09876 said:
Is there a difference between the Samsung J327P and the Samsung J320P? I'm trying to determine a difference so I can find the correct root file and process to root my phone. Every way I've tried so far has gotten stuck at trying to unlock my bootloader.
Click to expand...
Click to collapse
They are completely different, one has Exynos chips and the other is Qualcomm chipset, one has marshmallow and the other has lollipop, rear camera is different, the hardware and Kernel are different.
You need files specifically for the model you have.
Are you saying that you've successfully rooted your device another way but you're getting stuck at unlocking the bootloader? If you are truly rooted then it isn't a problem with how you rooted. Are you sure your bootloader can be unlocked?
Sent from my SM-S903VL using Tapatalk
Droidriven said:
They are completely different, one has Exynos chips and the other is Qualcomm chipset, one has marshmallow and the other has lollipop, rear camera is different, the hardware and Kernel are different.
You need files specifically for the model you have.
Are you saying that you've successfully rooted your device another way but you're getting stuck at unlocking the bootloader? If you are truly rooted then it isn't a problem with how you rooted. Are you sure your bootloader can be unlocked?
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I'm not rooted, I attempted attempted to flash TWRP and it seemed to be a success till I tried to enter TWRP and it just boots the phone up. So ATM, I seem to have no recovery as TWRP isn't working and the stock ROM isn't available for me to flash back on. So can I get stock recovery back just be doing a reset from my settings or do I just have to wait it out till it's supported?
Vikings09876 said:
I'm not rooted, I attempted attempted to flash TWRP and it seemed to be a success till I tried to enter TWRP and it just boots the phone up. So ATM, I seem to have no recovery as TWRP isn't working and the stock ROM isn't available for me to flash back on. So can I get stock recovery back just be doing a reset from my settings or do I just have to wait it out till it's supported?
Click to expand...
Click to collapse
You'll have to flash a copy of your stock recovery or your stock firmware, if you can find a copy.
Next time, do a better job of searching about your device and what can and CAN'T be done on whatever device you might have.
No, a factory reset won't fix it, in fact, a factory reset from settings on rooted devices only bricks the device and then the WHOLE OS has to be reflashed.
It isn't the same on mobile devices as it is on PC. On PC there is a partition that has a copy of your OS stored on it and factory reset reflashes that back to your main partition.
On mobile, factory reset only wipes what you've installed in user partition, your recovery is not in user partition so you'll still have the issue after resetting.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
You'll have to flash a copy of your stock recovery or your stock firmware, if up can find a copy.
Next time, do a better job of searching about your device and what can and CAN'T be done on whatever device you might have.
No, a factory reset won't fix it, in fact, a factory reset from settings on rooted devices only bricks the device and then the WHOLE OS has to be reflashed.
It isn't the same on mobile devices as it is on PC. On PC there is a partition that has a copy of your OS stored on it and factory reset reflashes that back to your main partition.
On mobile, factory reset only wipes what you've installed in user partition, your recovery is not in user partition so you'll still have the issue after resetting.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I'm just gonna leave it as is rn because the phone works tbh, I just don't have a working recovery. The stock ROM doesn't seem to be available atm as the phone was just recently released. I'm sure it will be released at some point, and I'm not too worried about it. If anything, I can just pay it off and upgrade to a different phone.
Use crom apk by Samsung to unlock your bootloader.....till the files come out that's as far as me or ne of us r getting
Update twrps have been tried to compile with no success till Ashyx (our luck to have his services) recieves the kernel source
https://forum.xda-developers.com/android/development/samsung-j3-root-t3544157/page9
There is a rooted boot.img that ill be testing since i havbe access to exclusive stock firmware and have recourse should ne th ing be wrong....ie a brick.
https://forum.xda-developers.com/android/development/samsung-j3-root-t3544157/page9
Kindly redirect to this thread