(NOTE TO MOD. PLEASE MOVE THIS POST TO THE INFUSE 4G GEN SECTION. THIS ISSUE MIGHT APPLY REGARDLESS OF THE PHONE BUT MY PHONE IS A INFUSE. THANKS.)
I seen this subject discussed but never really saw a answer, seems like everyone resorted to re installing firmware which I would like to avoid if I can.......
so, Ran into some trouble today trying to trying to do the 3e recovery mod today and had to reinstall stock firmware (using odin and gtg). Got root access and and was up and running. I went to updates just to see if anything was there and a update started and completed. the phone rebooted and was on the white and red update screen for about 4 secs and the phone rebooted again. When Got back to the home screen and got a message saying the update had failed. since then device management will not stop popping up. it stays in the task bar and if you use any process that needs it, it crashes and restarts itself. the message in the taskbar says "connecting to DM server" like its trying to get a update. how can I stop this without resetting the phone?
loulou704 said:
(NOTE TO MOD. PLEASE MOVE THIS POST TO THE INFUSE 4G GEN SECTION. THIS ISSUE MIGHT APPLY REGARDLESS OF THE PHONE BUT MY PHONE IS A INFUSE. THANKS.)
I seen this subject discussed but never really saw a answer, seems like everyone resorted to re installing firmware which I would like to avoid if I can.......
so, Ran into some trouble today trying to trying to do the 3e recovery mod today and had to reinstall stock firmware (using odin and gtg). Got root access and and was up and running. I went to updates just to see if anything was there and a update started and completed. the phone rebooted and was on the white and red update screen for about 4 secs and the phone rebooted again. When Got back to the home screen and got a message saying the update had failed. since then device management will not stop popping up. it stays in the task bar and if you use any process that needs it, it crashes and restarts itself. the message in the taskbar says "connecting to DM server" like its trying to get a update. how can I stop this without resetting the phone?
Click to expand...
Click to collapse
First we don't use Odin. As it is a different device post this in that device section.
Thread closed
I tried to update my rooted note but it just keeps rebooting. It goes through the set-up with percentage at the bottom, gets to 100% and then reboots like it's going to start. However, instead of starting, it just instead tries to upgrade again. It keeps going through this cycle.
I started it and used Odin to flash initial .tar with root in it and it's doing the same thing.
Please help!!!
grimloktt said:
I tried to update my rooted note but it just keeps rebooting. It goes through the set-up with percentage at the bottom, gets to 100% and then reboots like it's going to start. However, instead of starting, it just instead tries to upgrade again. It keeps going through this cycle.
I started it and used Odin to flash initial .tar with root in it and it's doing the same thing.
Please help!!!
Click to expand...
Click to collapse
Well, my suggestion would be to load up Kies on your computer. Connect the tablet, and see if you can do a firmware repair seeing as how you seemingly already tried to ODIN in another rom. Maybe you can try to boot into CWM and wipe the cache, dalvik, and factory reset, but I'm not so sure that will do anything for you.
OK. Used the update/tar from this file. Got me up and running but then gave me a message that update failed to install. I did, however, lose root rights.
http://forum.xda-developers.com/showthread.php?t=1847706&page=2
As risky as I am, I checked software update and found another update--this time smaller in size. Downloaded and installing...Wish me luck.
OK, That's appearing to work! Machine is rebooting and is again "optimizing applications."
yeah, the recent update came in 2 flavors. stock to LI3 which was 75 and LH2 to LI3 which was 40mb.
Glad to hear you got it up and running!
I have the shield tablet LTE version and after connecting to WIFI it immediately installed all OTAs upto the hotfix also. So here I am sitting with lollipop in my tablet and I decide to go for rooting and CWM installation.. After rooting using adb/fastboot and installing CWM image, I decide to disable ATTall access because I read that it stops the portable hotspot from working. So, did that and then process after process started crashing. First it started with background data not being enabled (playstore wouldn't open) , NVidia hub crashing, google text to speech crashing, etc.
So, I went to cwm and did factory reset. At the initial stages itself where it asks for language setup, the google text to speexh crashes and I cannot click next or proceed forward.
I flash the Lollipop OTA once again thinking it would overwrite the system but it didn't.. and the same issue keeps happening..
Now what do I do?
Regards
Alden
An update to the mess i was in...
I tried recovery mode at the fastloader boot menu and I got the robot lying down with a red exclamation mark sign. I pressed vol + key and it opened the original recovery I think. I wiped user data from this menu and rebooted. and now it has come to the original screen setup and so far no process crashes...
What could have caused this entire mess?
I am not sure what would cause your issues but i believe your best bet is to download the full rom image for your tablet and flash it via fastboot. That should get you back up and running. (Be warned doing this will erase everything on your tablet!! SD card will be untouched)
By fullmrom u mean the one from the nvidia developer website right?
Yes that is the one! I am currently at work so I cant post a link to it but if you need it ill try to post it once im off, in about 30-ish minutes. Good luck! (p.s. last resort is RMA)
Is your shield up and running once again? Just wanted to get an update. =]
Thanks javydawg, I didnt use the one on nvidias developer website as i simply did not have enough data left in my Internet plan .. its 2.3 gb in size... after recoVery i was left with lollipop so i flashed a 750 mb file tht i gt from these forums and updated it to the latest version.. i still haven't pinpointed the reason for my earlier trouble but will shout out if it happens again... have to be careful cos not sure if RMA is possible for me in India...
I'm really hoping you guys can help me out here. This is an S7 I bought from a Best Buy when I visited the US in 2017, and I got the Unlocked version so I would be able to use it back in my home country. Unfortunately, this is the second time I've had trouble with it in a span of 4 months and the first time it was a hardware problem and ended up quite expensive to get fixed.
Today I was using my phone normally when I decided to use the Google instant translation to translate something on my computer screen. That caused my phone to freeze, restart, and then tell me I was using an unauthorized flash and it was going to be locked, or something like that. Even after restarting a few more times, the phone would never get past that screen. I proceeded to factory reset/cache reset and from then on the phone just got stuck in a boot loop.
I learned that the fix would be to flash the phone. After a lot of work I found the G930UUESACSI1-20190930144640 firmware (the XAA version, for Unlocked) and successfully used Odin 3.13 at the Download Mode screen to flash my phone. It then restarted, went back to the blue screen, started installing some updates, when it was 100% it restarted again. Unfortunately, the loop remained. Galaxy S7 logo first, then the Samsung logo, then it just repeats.
I have also tried turning the phone off with the Recovery screen shut down option (since I can't seem to be able to turn it off with the power button right now), wait a few minutes, then turn it back on. Nothing changed.
Please, does anyone have any insight into this? What else could I possibly try, or what could I be doing wrong? I really don't want to send it to repair yet again in such a short time.
Many thanks in advance.
gabeblack said:
I'm really hoping you guys can help me out here. This is an S7 I bought from a Best Buy when I visited the US in 2017, and I got the Unlocked version so I would be able to use it back in my home country. Unfortunately, this is the second time I've had trouble with it in a span of 4 months and the first time it was a hardware problem and ended up quite expensive to get fixed.
Today I was using my phone normally when I decided to use the Google instant translation to translate something on my computer screen. That caused my phone to freeze, restart, and then tell me I was using an unauthorized flash and it was going to be locked, or something like that. Even after restarting a few more times, the phone would never get past that screen. I proceeded to factory reset/cache reset and from then on the phone just got stuck in a boot loop.
I learned that the fix would be to flash the phone. After a lot of work I found the G930UUESACSI1-20190930144640 firmware (the XAA version, for Unlocked) and successfully used Odin 3.13 at the Download Mode screen to flash my phone. It then restarted, went back to the blue screen, started installing some updates, when it was 100% it restarted again. Unfortunately, the loop remained. Galaxy S7 logo first, then the Samsung logo, then it just repeats.
I have also tried turning the phone off with the Recovery screen shut down option (since I can't seem to be able to turn it off with the power button right now), wait a few minutes, then turn it back on. Nothing changed.
Please, does anyone have any insight into this? What else could I possibly try, or what could I be doing wrong? I really don't want to send it to repair yet again in such a short time.
Many thanks in advance.
Click to expand...
Click to collapse
You need to clear the cache after flashing to get out of the boot loop.
Use the download key combo to restart. As soon as the screen goes black move to Volume up+home+power.
In the recovery menu choose clear/ Wipe cache, then choose reboot.
I apologize for not updating this thread before when it was still recent. The fact is that I didn't manage to fix my phone; clearing the cache after flashing did nothing to stop the loop.
I ended up taking the phone to the people who have fixed it in the past and after more than one month, they gave up. So I got my phone back and I want to try to give it another go before I just sell it for parts.
Unfortunately, my phone has come back even worse. Now it has no Recovery Menu to speak of, at least none that I can access; after a few seconds of the blue text on the top saying that it's entering recovery mode, it then proceeds to a blue screen saying: "Security Error: This phone has been flashed with unauthorized software and is locked.". I can still access Download Mode.
I have attempted flashing a few firmwares that I believe should have worked with my SM-G930U. Odin listed the attempts as "pass" and, after restarting and going back to the Download screen, it says the binary is Official. However, after trying to restart the phone normally, it starts displaying the blue screen again, and then, after going to Download mode, the binary is reverted to "Custom".
I believe right now the order of the day is to get the recovery menu to work again so I can do all the cache cleaning that seems to be required after flashing firmware. Any ideas at all on how I should proceed? Is there something specific I should download to fix the recovery menu?
How many files are you flashing in Odin, is it just 1 file in the AP slot, or 4 files: AP, BL, etc.? Also, is your phone rooted?
Drunkpilot said:
How many files are you flashing in Odin, is it just 1 file in the AP slot, or 4 files: AP, BL, etc.? Also, is your phone rooted?
Click to expand...
Click to collapse
Never rooted, was using the phone legit before it froze and entered boot loop. I flashed all 4 files, multiple times.
Someone tried fixing my phone a few days after I replied to this thread and some progress seems to have been made, but now the phone cannot get past a black screen with a "SBL Error! rdx_init!" in red text, and "upload mode" in yellow text. Still cannot access Recovery Mode, but Download Mode still works.
I did a little Googling on rdx_init errors and it seems I need a firmware dump from another G930U or something like that...any ideas on how I can proceed?
Flash it with Eng Boot in all slots using patched Odin. Reboot to recovery and wipe it. Reboot system. Then root it with advanced adb root. Links for all of this are here in xda. Enjoy
STA1NL3SS said:
Flash it with Eng Boot in all slots using patched Odin. Reboot to recovery and wipe it. Reboot system. Then root it with advanced adb root. Links for all of this are here in xda. Enjoy
Click to expand...
Click to collapse
Sorry, I'm not an expert at this by any means, I'm not sure what files to get. So far I've found and downloaded the following:
S7_Oreo_Nougat_Adb_Advanced_Root_V10
S7_Oreo_Nougat_Adb_Advanced_Root_V12
S7_Oreo_Su_Binary_Only_ADB_Root
But I had no luck flashing any of these cause my binary is 10. Is there any more help you can provide me? I really don't know how to proceed
gabeblack said:
Sorry, I'm not an expert at this by any means, I'm not sure what files to get. So far I've found and downloaded the following:
S7_Oreo_Nougat_Adb_Advanced_Root_V10
S7_Oreo_Nougat_Adb_Advanced_Root_V12
S7_Oreo_Su_Binary_Only_ADB_Root
But I had no luck flashing any of these cause my binary is 10. Is there any more help you can provide me? I really don't know how to proceed
Click to expand...
Click to collapse
I thought I had one in my phone, but I don't. If you look at the thread where you downloaded the Root_V12, you will see it. It's near the end of the thread somewhere.
Hi everyone last night i decided to root my ohone. I have had it for a while but for some reason hadn't got round to doing it.
I followed all the instructions firstly unlocking bootloader, TWRP then installing no verity and magisk etc and every looked to be good phone starts up with the the your device has been unlocked message and something about bad id key but then would start like normal and set about installing all my apps etc again for the phone to be back to how it was just rooted.
However tonight i restarted my phone and when it's went to start up it throws me into the fast loader screen wtih your device didnt stat up successfully use the software repair assistant on computer to repair your device.
I had only been installing my usual apps/ new luancher etc... however the only thing i think that could have caused an issue was i checked for an android version update and it found i already had the most up to date one so nothing was downloaded but possibly just checking has caused an issue ?
Any help with this would be appreciated.
I can still boot into team win recovery mode but was hoping as i've now installed everything a new... i could resolve this without another fresh install if possible ?
Thanks
fendertele said:
Hi everyone last night i decided to root my ohone. I have had it for a while but for some reason hadn't got round to doing it.
I followed all the instructions firstly unlocking bootloader, TWRP then installing no verity and magisk etc and every looked to be good phone starts up with the the your device has been unlocked message and something about bad id key but then would start like normal and set about installing all my apps etc again for the phone to be back to how it was just rooted.
However tonight i restarted my phone and when it's went to start up it throws me into the fast loader screen wtih your device didnt stat up successfully use the software repair assistant on computer to repair your device.
I had only been installing my usual apps/ new luancher etc... however the only thing i think that could have caused an issue was i checked for an android version update and it found i already had the most up to date one so nothing was downloaded but possibly just checking has caused an issue ?
Any help with this would be appreciated.
I can still boot into team win recovery mode but was hoping as i've now installed everything a new... i could resolve this without another fresh install if possible ?
Thanks
Click to expand...
Click to collapse
You could try reflashing the boot.img
What does getvar all say?
Code:
fastboot getvar all