Hi guys,
I have the international version of the Galaxy S3 and I have a little problem. The first thing I did when I've got it was root it with Odin and everything went fine but now I see the rooting doesn't work as it should. Buisybox says it needs to be rooted and SuperSu is configured to allow everything. Also, when I launch CWM Manager (v3.55) a popup says that it should be used with CF-Root v5.0 or newer.
My question is, how should I update everything? When I format/upgrade my old Galaxy S2 to give it to my dad, I simply flashed CF-Root to the CW10 and it broke the phone's boot. Luckily I had backed up everything using CF-Root the day before. Should I uninstall it first? How? And how can I do it without loosing the backup I'll make to my S3 before I try anything?
What I mean is... how can I update everything in a "clean" way?
Thanks in advance!
I recently rooted my note using "method 2". However when I flashed a jellybean Rom, I lost s pen functionality. So after flashing firmware after firmware last night, I got it back to ics (however, snote kept crashing upon boot, so I had to disable it). The spen is working and all.
So, from here, how do I go about getting jellybean with working s pen from here?
Hello Everybody,
I'll make this short and sweet. I've tried to flash cyanogen mod using the installer, it says it was successful but it wasn't. All it did was reset my touchwhiz (Using Samsung Galaxy S3 i747M Rogers version) back to it's original state. I also think root was removed. I tried to use my CWM recovery file, but it didn't work. It actually messed with my radios and I had no service. My screen was also spammed with "gapps has stopped working" messsages. I've fixed that part of the issue by flashing the stock touchwhiz. My apps/pictures are still there, but app data has been deleted. CWM did not restore properly. Is this due to root being removed? If I re-root my phone, will I be able to get it back to the state is was in before trying to flash cyanogen?
I have a Verizon Galaxy SCH-I535, it had Android 4.3, but I downgraded it to 4.1.2 creating a custom-stock ROM.
Now I rooted it, unlocked the bootloader, installed TWRP 3.0.0 and tested other recoveries as well, and also flashed several ROMs, all of them correctly but when the ROMs starts, just about to show the FIRST SCREEN of the Setup Wizard, the image crashes and shows blinking colored dots.
At the end the only ROM I can have booted is the 4.1.2 that I saved.
Can anyone tell me how can I do to have a different ROM installed, and thta is correctly booted,thanks.
aaronkish said:
I have a Verizon Galaxy SCH-I535, it had Android 4.3, but I downgraded it to 4.1.2 creating a custom-stock ROM.
Now I rooted it, unlocked the bootloader, installed TWRP 3.0.0 and tested other recoveries as well, and also flashed several ROMs, all of them correctly but when the ROMs starts, just about to show the FIRST SCREEN of the Setup Wizard, the image crashes and shows blinking colored dots.
At the end the only ROM I can have booted is the 4.1.2 that I saved.
Can anyone tell me how can I do to have a different ROM installed, and thta is correctly booted,thanks.
Click to expand...
Click to collapse
I have my old S3 running CleanRom and I've for the most part never had an issue with the setup wizard on that device. On others have. Are you clearing the cache and the dalvik after flashing the rom?
Sent from my Nexus 6
ShapesBlue said:
I have my old S3 running CleanRom and I've for the most part never had an issue with the setup wizard on that device. On others have. Are you clearing the cache and the dalvik after flashing the rom?
Sent from my Nexus 6
Click to expand...
Click to collapse
Yes, I always clean cache, dalvik, system, data and even internal storage.
I have tried with:
(5.0.2)aicp_d2vzw_lp-8.0-RELEASE-20150210
(5.1.1)aicp_d2vzw_lp-9.0-NIGHTLY-20150605
(5.1.1)cm-12.1-20150606-NIGHTLY-d2vzw
(5.1.1)OCT-L-M6-FINAL-5.1.1-20151229-d2vzw
(5.1.1)Slim-d2vzw-5.1.1.beta.0.12-OFFICIAL-20151116-0147
(6.0.1)Broken-v4.6-d2vzw-6.0.1-OFFICIAL-20160503
(6.0.1)Slim-d2vzw-6.0.1.alpha.0.2-WEEKLY-20160628-0745
No luck with any of those, but I restored the backup I did before(Android 4.1.2), and everythings works fine. Funny thing is that it even shows the screen for "Updating apps 1 of 83" and so, but when it "wants" to start it crashes and reboots in a few seconds.
But, anyways, that is past now, I lost my mind and flashed the stock 4.3, it hardbricked my phone, I used the unbrick method for 4.4.2 and I don't know how I ended up with the wrong kernel so there is no going back now, I flashed stock 4.4.2, so no downgrade possible now.
I have read about JTAG solution to downgrade, is it possible?
I bought the Octoplus Dongle for Samsung Lite, but I don't think it works for this type of problem.
I will ask in a different thread. Thanks anyways.
aaronkish said:
Yes, I always clean cache, dalvik, system, data and even internal storage.
I have tried with:
(5.0.2)aicp_d2vzw_lp-8.0-RELEASE-20150210
(5.1.1)aicp_d2vzw_lp-9.0-NIGHTLY-20150605
(5.1.1)cm-12.1-20150606-NIGHTLY-d2vzw
(5.1.1)OCT-L-M6-FINAL-5.1.1-20151229-d2vzw
(5.1.1)Slim-d2vzw-5.1.1.beta.0.12-OFFICIAL-20151116-0147
(6.0.1)Broken-v4.6-d2vzw-6.0.1-OFFICIAL-20160503
(6.0.1)Slim-d2vzw-6.0.1.alpha.0.2-WEEKLY-20160628-0745
No luck with any of those, but I restored the backup I did before(Android 4.1.2), and everythings works fine. Funny thing is that it even shows the screen for "Updating apps 1 of 83" and so, but when it "wants" to start it crashes and reboots in a few seconds.
But, anyways, that is past now, I lost my mind and flashed the stock 4.3, it hardbricked my phone, I used the unbrick method for 4.4.2 and I don't know how I ended up with the wrong kernel so there is no going back now, I flashed stock 4.4.2, so no downgrade possible now.
I have read about JTAG solution to downgrade, is it possible?
I bought the Octoplus Dongle for Samsung Lite, but I don't think it works for this type of problem.
I will ask in a different thread. Thanks anyways.
Click to expand...
Click to collapse
Did you update the radio/baseband to NE1? No need to utilize a jtag as your flashing custom roms so the device is already bootloader unlocked
Edit: nevermind you updated to the latest stock so as you already know your bootloader is locked
Sent from my Nexus 6
Hi Guys,
Hopefully this is in the right section
I have a Note 4 SM-N910G and its just turned absolutely useless since I factory flashed it. I have rooted it before and bricked it and un bricked it before so have some experience with it. I recently wiped my phone and did a firmware restore using Samsung Kies and since I did the phone is absolutely useless. It started out fine for an hour or two and now it lags by like a minute with any action, even trying to bring up the keyboard when typing. It will reset itself, lock itself, crash, just un useable. I've tried reflashing it again stock a couple times and still the same everytime. It went from perfectly fine to dreadful with the original mentioned restore. I did just recently get an error code of "sbl1 partition doesn't exist" in Boot recovery mode.
Does anyone know if this is fixable and not a hardware issue?
Should I try and just root it again and flash a non-oem rom? (I havent had the time to do it recently)
many thanks,
Tekkado
Hi Guys,
Also I should add that when I was rooted the phone was fine but when i went to unroot through super user the phone was still functioning as though rooted and I couldnt download software updates because my device was "modified".
So thats when i just flashed stock firmware and again now flashing through odin aswell it proceeds fine then the device will say installing updates and then give a no command error or seandroid not enforced. Everytime is basically a different message.
How can I just wipe everything and get back to stock?
Thanks
So to add to this is there any relationship between the firmware running and the bootloader? I just realised that before i tried to flash stock firmware i was rooted and didnt un root via superuser because in the past that did jack all.
I flashed dr. ketan rom this morning and the phone was operating as normal very snappy but as soon as i downloaded a new app from the play store (reddit and chrome) again it turned to absolute crap.
Is there a disconnect here that i missing that can be fixed?
Thanks