I have a Galaxy S6 SM-G920V rooted using PingPongRoot years ago. I've never updated the phone, so it's still on Android 5.0.2.
Recently it's been having battery indicator issues: thinks it's charging when it's not and vice versa. I replaced the battery and even the charging port (having to remove the screen and all that). Still no luck.
After backing up everything with Titanium backup, what are my options? I can't even perform a factory reset, since the phone gets stuck in a boot loop until I remove the battery. Will flashing the ROM using traditional methods (ODIN) even work with a Verizon phone? Is there a newer version of Android for this phone that still has root? (Nougat?) Without root, I probably can't reset everything I backed up with Titanium Backup.
Any advice would be greatly appreciated. Thanks.
shanebelcroft said:
I have a Galaxy S6 SM-G920V rooted using PingPongRoot years ago. I've never updated the phone, so it's still on Android 5.0.2.
Recently it's been having battery indicator issues: thinks it's charging when it's not and vice versa. I replaced the battery and even the charging port (having to remove the screen and all that). Still no luck.
After backing up everything with Titanium backup, what are my options? I can't even perform a factory reset, since the phone gets stuck in a boot loop until I remove the battery. Will flashing the ROM using traditional methods (ODIN) even work with a Verizon phone? Is there a newer version of Android for this phone that still has root? (Nougat?) Without root, I probably can't reset everything I backed up with Titanium Backup.
Any advice would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Google search:
"Return to stock (your specific model number)"
That will find what you need in order to reflash your stock firmware.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Google search:
"Return to stock (your specific model number)"
That will find what you need in order to reflash your stock firmware.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
If I reflash to stock, would my only option for root still be to just apply PingPongRoot again? Does root exist for a newer version of Android for a SM-G920V? or only other models like SM-G920F?
Thanks.
shanebelcroft said:
If I reflash to stock, would my only option for root still be to just apply PingPongRoot again? Does root exist for a newer version of Android for a SM-G920V? or only other models like SM-G920F?
Thanks.
Click to expand...
Click to collapse
If you flash the same firmware as what you had when you rooted your device, you will still be able to root using the same rooting method that you used the first time. If you flash a firmware that is newer than what you had, your rooting method may not work.
Flash your firmware then root with PingPongroot like you did before.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
If you flash the same firmware as what you had when you rooted your device, you will still be able to root using the same rooting method that you used the first time. If you flash a firmware that is newer than what you had, your rooting method may not work.
Flash your firmware then root with PingPongroot like you did before.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
With Odin I was able to flash a stock OE2 ROM (everything passed) following this guide: https://forum.xda-developers.com/verizon-galaxy-s6/verizon-s6-stock-restore-files-t3096000, but now the phone shuts off after showing the boot logo. "Custom" still appears in the logo. I tried a factory reset, per the guide, but that didn't change anything.
Are there any other things I can try?
Thanks
shanebelcroft said:
With Odin I was able to flash a stock OE2 ROM (everything passed) following this guide: https://forum.xda-developers.com/verizon-galaxy-s6/verizon-s6-stock-restore-files-t3096000, but now the phone shuts off after showing the boot logo. "Custom" still appears in the logo. I tried a factory reset, per the guide, but that didn't change anything.
Could the other options in Odin help? Repartition? NAND Erase All?
Thanks
Click to expand...
Click to collapse
What version of Odin are you using? Are you using a version of Odin from around the same time that your device was new to the market? Have you tried using the modified version of Odin that is available here? Have you tried Cosmy's Odin?
Don't use the NAND erase all option, that tends to cause more problems than it solves.
Yes, if you can find a copy of the PIT file for your specific device, you can flash it in the PIT tab in Odin along with the firmware in its slot(s) and select the "repartition" option in Odin while flashing the firmware and the PIT.
You can also try extracting the system.img from the firmware and convert it to an Odin flashable .tar.md5 then flash it in the AP slot. Then power of the device then immediately boot back into download mode and try flashing the entire firmware again.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
What version of Odin are you using? Are you using a version of Odin from around the same time that your device was new to the market? Have you tried using the modified version of Odin that is available here? Have you tried Cosmy's Odin?
Don't use the NAND erase all option, that tends to cause more problems than it solves.
Yes, if you can find a copy of the PIT file for your specific device, you can flash it in the PIT tab in Odin along with the firmware in its slot(s) and select the "repartition" option in Odin while flashing the firmware and the PIT.
You can also try extracting the system.img from the firmware and convert it to an Odin flashable .tar.md5 then flash it in the AP slot. Then power of the device then immediately boot back into download mode and try flashing the entire firmware again.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I've tried both Odin 3.10.6 and Odin3 v3.14.1_3B_PatcheD. Both pass without any issues. I still can't get passed the Samsung logo after flashing the stock OE2 ROM. For what it's worth, even plugging the phone into a charger just brings up the Samsung logo.
What's the reasoning for flashing system.img individually?
shanebelcroft said:
I've tried both Odin 3.10.6 and Odin3 v3.14.1_3B_PatcheD. Both pass without any issues. I still can't get passed the Samsung logo after flashing the stock OE2 ROM. For what it's worth, even plugging the phone into a charger just brings up the Samsung logo.
What's the reasoning for flashing system.img individually?
Click to expand...
Click to collapse
Because flashing the system.img by itself can solve the "custom" status and allow the full firmware to flash.
Did you try flashing your PIT along with the firmware and repartition?
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Because flashing the system.img by itself can solve the "custom" status and allow the full firmware to flash.
Did you try flashing your PIT along with the firmware and repartition?
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thanks for the suggestions.
I extracted system.img, remade a tar, and flashed it alone. Still gave the custom logo. I then did a full flash again. No luck.
I tried flashing with the full firmware, with re-partition checked and ZEROFLTE_USA_VZW.pit selected as the pit file (supposedly the pit file for SM-G920V). Still no luck.
If this is an issue with the bootloader, and this being a Verizon phone, I'm probably not going to have much luck, am I?
shanebelcroft said:
Thanks for the suggestions.
I extracted system.img, remade a tar, and flashed it alone. Still gave the custom logo. I then did a full flash again. No luck.
I tried flashing with the full firmware, with re-partition checked and ZEROFLTE_USA_VZW.pit selected as the pit file (supposedly the pit file for SM-G920V). Still no luck.
If this is an issue with the bootloader, and this being a Verizon phone, I'm probably not going to have much luck, am I?
Click to expand...
Click to collapse
As long as your hardware isn't corrupted or damaged, you should be able to restore the device.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
As long as your hardware isn't corrupted or damaged, you should be able to restore the device.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I wouldn't be surprised if it's the hardware. The phone is 5 years old. Maybe the battery level reading issue was a symptom of that instead of software or battery problems. Maybe as a last hail Mary, I'll disassemble the device again and make sure all the connectors are really connected. I don't think it's worth buying a new motherboard. Better to buy a new phone, one I can root, anyway.
Thanks for the help!
shanebelcroft said:
I wouldn't be surprised if it's the hardware. The phone is 5 years old. Maybe the battery level reading issue was a symptom of that instead of software or battery problems. Maybe as a last hail Mary, I'll disassemble the device again and make sure all the connectors are really connected. I don't think it's worth buying a new motherboard. Better to buy a new phone, one I can root, anyway.
Thanks for the help!
Click to expand...
Click to collapse
I'd say it is probably worth upgrading anyway, the unlocked unbranded Pixel phones are available for decent prices on Swappa.com. They can be used on Verizon, are easily rooted, currently have plenty of custom development and will continue to get custom development for years to come.
If you like using root and having custom software installed, do NOT get anything that is a Verizon branded device, they lock the bootloader on absolutely everything they offer these days.
Sent from my SM-S767VL using Tapatalk
Related
I'm not noob to flashing or soft brick recovering but this has me confused...
I was running unNamed lastest for a lil while now. Everything was working fine until here recently, while stopped at a rest area checking a webpage my phone cut of and got stuck on a boot loop, only showing the kernal splash screen. Was like wtf? Tried pulling battery ,wiping cache and dalvik. No help. Was like that's fine, have a cwm back up from week ago. Nope didnt work. Was like ok let me try flashing something on my phone that's saved on sd. Flashed Miui, didn't work. Finally got back and tried using this Odin One click "Odin3 One-Click Downloader Stock I-777 UCKH7 with Root no BL" by entropy from the flashing without triggering flash counter guide. Still boot loops only showing the black Samsung Galaxy S II screen. This is after 3 what the odin says as 3 successful flash attempts.
I'm at my wits end, of all the soft bricking i've recovered from, where I assumed as long as a bad bootloader flash didn't happen and i could still get to download mode I'm fine, it could be fixed. But this has me stumped.
*After going into 3e recovery and trying to wipe data, it won't even now go back into 3e recovery. Attempts to but says something like deleting cryption meta data or something of that nature.
-confused-
Nerz said:
I'm not noob to flashing or soft brick recovering but this has me confused...
I was running unNamed lastest for a lil while now. Everything was working fine until here recently, while stopped at a rest area checking a webpage my phone cut of and got stuck on a boot loop, only showing the kernal splash screen. Was like wtf? Tried pulling battery ,wiping cache and dalvik. No help. Was like that's fine, have a cwm back up from week ago. Nope didnt work. Was like ok let me try flashing something on my phone that's saved on sd. Flashed Miui, didn't work. Finally got back and tried using this Odin One click "Odin3 One-Click Downloader Stock I-777 UCKH7 with Root no BL" by entropy from the flashing without triggering flash counter guide. Still boot loops only showing the black Samsung Galaxy S II screen. This is after 3 what the odin says as 3 successful flash attempts.
I'm at my wits end, of all the soft bricking i've recovered from, where I assumed as long as a bad bootloader flash didn't happen and i could still get to download mode I'm fine, it could be fixed. But this has me stumped.
*After going into 3e recovery and trying to wipe data, it won't even now go back into 3e recovery. Attempts to but says something like deleting cryption meta data or something of that nature.
-confused-
Click to expand...
Click to collapse
The one-click downloader is NOT from me, it's a repack of my tar file - and it's starting to sound like the one-click is doing something weird and not flashing the kernel properly.
Use regular old Odin (or Heimdall) to flash the raw tar package.
I'll try it. Though I don't understand how I am in the position I am in from browsing the web on my phone to directly going into a hootloop that neither that odin one click will fix, or any cwm roms won't fix.
Sent from my GT-I9000 using XDA App
I won't have access to computer till later today but I'm trying to figure out what could be wrong. I was thinking that maybe my partitions were bad, but doesn't that odin used, repartition, using a pit file (think that is what pit is for)? Although, this was not from a flash, but rebooted from a couple weeks old successful flash of unNamed while browsing the web so I don't see how that can be the problem. However, even if the partitions were bad, wouldn't odin fail a flash because it has no where to send the firmware files? Also if it was a type of hardware failure, such as processor, wouldn't it not even show the kernel Galaxy S II splash screen? Or is this something that only the gpu handles? It was able to get into cwm before I used the odin though so I can't believe it's cpu because I'm sure that recovery should use it. Just can't figure it out, never had a problem with a boot loop a flash couldn't fix.
If I can't get it to work, will flashing a stock kernel with cwm increment the flash counter? If not I guess I could access my internal sd, try and pull my pictures and the roms off there and then send it to warranty. However I really don't want to. Thanks to anyone in advance.
Sent from my GT-I9000 using XDA App
Nerz said:
I won't have access to computer till later today but I'm trying to figure out what could be wrong. I was thinking that maybe my partitions were bad, but doesn't that odin used, repartition, using a pit file (think that is what pit is for)? Although, this was not from a flash, but rebooted from a couple weeks old successful flash of unNamed while browsing the web so I don't see how that can be the problem. However, even if the partitions were bad, wouldn't odin fail a flash because it has no where to send the firmware files? Also if it was a type of hardware failure, such as processor, wouldn't it not even show the kernel Galaxy S II splash screen? Or is this something that only the gpu handles? It was able to get into cwm before I used the odin though so I can't believe it's cpu because I'm sure that recovery should use it. Just can't figure it out, never had a problem with a boot loop a flash couldn't fix.
If I can't get it to work, will flashing a stock kernel with cwm increment the flash counter? If not I guess I could access my internal sd, try and pull my pictures and the roms off there and then send it to warranty. However I really don't want to. Thanks to anyone in advance.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Ok so after flashing the odin file from http://forum.xda-developers.com/showthread.php?t=1286432 it is still bootlooping at splash screen.
I'm not sure what my options are right now. I'm pretty sure bootloaders can't be the problem. I can't re-partition from odin because it says it can't open the specified file "(Line: 1828)". Is this because it doesn't have pit file? I don't understand how this problem manifested.
If I need to pull contents from sd card from cwm, will flashing a cwm kernal increment flash counter?
Don't repartition using a PIT, it's a great way to screw up your phone. (Hopefully you haven't flashed a PIT at all yet... If you have, I don't quite know what's going on.)
Sent from my GT-P7510 using Tapatalk
Entropy512 said:
Don't repartition using a PIT, it's a great way to screw up your phone. (Hopefully you haven't flashed a PIT at all yet... If you have, I don't quite know what's going on.)
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
Have yet to flash a pit file.
Sent from my GT-I9000 using XDA App
I'm in the same situation, except with a Sprint GSII. Have you found a fix, yet?
Juq said:
I'm in the same situation, except with a Sprint GSII. Have you found a fix, yet?
Click to expand...
Click to collapse
Hello there from colombia, i have the same thing over here, i`m stuck with a SGS SGH I777 the flash counter says 7 and either flashing CWM 5 or re-uploading stock room wont work, i have no way to buy a jig and it is pretty odd that im in a different country and i can`t send my phone for warranty repair, i`ve read all over and seems like there is no answer for this. Can anyone get rid of the Deleting Crytion Meta data?? this is all i get. ( and eternal boot loop ).
Thanks in advance.
hardgrid said:
Hello there from colombia, i have the same thing over here, i`m stuck with a SGS SGH I777 the flash counter says 7 and either flashing CWM 5 or re-uploading stock room wont work, i have no way to buy a jig and it is pretty odd that im in a different country and i can`t send my phone for warranty repair, i`ve read all over and seems like there is no answer for this. Can anyone get rid of the Deleting Crytion Meta data?? this is all i get. ( and eternal boot loop ).
Thanks in advance.
Click to expand...
Click to collapse
Will try to help, but will need more specific information.
The OP of this thread started bootlooping while checking a web page in his browser. So, how did it happen for you? Please give as much exact information as possible. Was it after a flash? Or did it start while you were using the phone? Or how?
Mine was connected to an aftermarket car charger while it happened. I read a post somewhere and a couple ppl it happened to believed the same thing, since it was in my 30 day trail period I sent it back to Sams club and got my replacement today. Since I didn't have a jig at the time, I didn't want to flash a cwm kernel and increase my flash counter so I lost some pics of my kids.
Not sure if it was charger related but I couldn't find a fix and wouldn't really call myself a noob at flashing. Might have some things to learn nut far from a noob.
Sent from my I897 using XDA App
I have a sch-i605 verizon note 2. It is stuck in a boot loop. I can not access recovery, only download mode. I have flashed with odin over 20 times and am still stuck. I have tried all stock files, pit, all versions of odin, 3 different oem cables, 3 different pcs (1 win7 premium, 2 winXP), all 10 different USB ports. I have rebooted the pc's several times. I can get the stock samsung file from their site and the root66 stock rooted file to pass in odin but the phone is still in a bootloop. Please help if you can with any ideas, thanks!
heggood said:
I have a sch-i605 verizon note 2. It is stuck in a boot loop. I can not access recovery, only download mode. I have flashed with odin over 20 times and am still stuck. I have tried all stock files, pit, all versions of odin, 3 different oem cables, 3 different pcs (1 win7 premium, 2 winXP), all 10 different USB ports. I have rebooted the pc's several times. I can get the stock samsung file from their site and the root66 stock rooted file to pass in odin but the phone is still in a bootloop. Please help if you can with any ideas, thanks!
Click to expand...
Click to collapse
Flash root66 in Odin with the PIT and check the NAND erase option in Odin.
Sent from my SCH-I605 using XDA Premium HD app
heggood said:
I have a sch-i605 verizon note 2. It is stuck in a boot loop. I can not access recovery, only download mode. I have flashed with odin over 20 times and am still stuck. I have tried all stock files, pit, all versions of odin, 3 different oem cables, 3 different pcs (1 win7 premium, 2 winXP), all 10 different USB ports. I have rebooted the pc's several times. I can get the stock samsung file from their site and the root66 stock rooted file to pass in odin but the phone is still in a bootloop. Please help if you can with any ideas, thanks!
Click to expand...
Click to collapse
What did you do before you started getting the bootloops? Just wondering for background on what happened to better steer you in the right direction.
Dido
BoostedB18C said:
What did you do before you started getting the bootloops? Just wondering for background on what happened to better steer you in the right direction.
Click to expand...
Click to collapse
I have the very same problem been without vzw note for about two weeks. What happend to me was i had flashed goodness noteworthy for the sprint/vwz note II i was suppose to flash three files from 3minit in order for the rom to work correctly but i ended up flashing something for the sprint version... Hopefully i can get some help from this too. . . Thank you in advance!
BoostedB18C said:
What did you do before you started getting the bootloops? Just wondering for background on what happened to better steer you in the right direction.
Click to expand...
Click to collapse
Not exactly sure what happened with the phone. I bought it from a guy that does lots of flashing to his devices and he said he messed it up and took it to a repair place that tried to reflash it for him and he said the tech said the battery died in the process. I plan to try the idea posted above about checking nand erase in Odin but won't be able to till tomorrow, any other ideas will be much appreciated.
heggood said:
Not exactly sure what happened with the phone. I bought it from a guy that does lots of flashing to his devices and he said he messed it up and took it to a repair place that tried to reflash it for him and he said the tech said the battery died in the process. I plan to try the idea posted above about checking nand erase in Odin but won't be able to till tomorrow, any other ideas will be much appreciated.
Click to expand...
Click to collapse
The issue is Root66, and I believe the alternative recovery ROM, doesnt wipe the internal SD so whatever is causing your issue may still be there in some form or fashion. If that doesn't work then you could try the VRALJB or VRALL4 restore Roms and see if they work, if the guy was a flasher then he may have unlocked it before the VRAMC3 update screwed everything up.
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
The issue is Root66, and I believe the alternative recovery ROM, doesnt wipe the internal SD so whatever is causing your issue may still be there in some form or fashion. If that doesn't work then you could try the VRALJB or VRALL4 restore Roms and see if they work, if the guy was a flasher then he may have unlocked it before the VRAMC3 update screwed everything up.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
What do you mean by, "the issue is root66?" Are you saying I shouldn't use it to flash? Those other 2 Roms when I have tried normally to flash it only runs for about 30 seconds then Odin says fail (vral4 & vraljb). The vramc3 and root66 actually runs the entire cycle and Odin says pass but phone stays stuck on flashing Samsung note 2 logo.
heggood said:
What do you mean by, "the issue is root66?" Are you saying I shouldn't use it to flash? Those other 2 Roms when I have tried normally to flash it only runs for about 30 seconds then Odin says fail (vral4 & vraljb). The vramc3 and root66 actually runs the entire cycle and Odin says pass but phone stays stuck on flashing Samsung note 2 logo.
Click to expand...
Click to collapse
I mean that the Root66 ROM doesn't completely wipe the phone like the VRALJB and VRALL4 Roms do because of the way it was made, like I said earlier though if you check the NAND Erase box in Odin before flashing it should get you back to normal.
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
The issue is Root66, and I believe the alternative recovery ROM, doesnt wipe the internal SD so whatever is causing your issue may still be there in some form or fashion. If that doesn't work then you could try the VRALJB or VRALL4 restore Roms and see if they work, if the guy was a flasher then he may have unlocked it before the VRAMC3 update screwed everything up.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
OK, so I have tried the ticking Hand Erase All in Odin 3 times now with root66, did not work either. But now there is a difference, not sure if its good or bad. When I try to power on the phone it goes to the android downloading logo without the Odin mode script in the top left hand corner, instead of bootlooping the note 2 logo.
shangrila500,
I'm up and running now. I tried the vraljb rom after the 4th attempt of root66 failing and vraljb worked. I guess doing the erase in Odin made that work, thanks very much. the phone is now on 4.1.1, should I do a manual update or no?
heggood said:
shangrila500,
I'm up and running now. I tried the vraljb rom after the 4th attempt of root66 failing and vraljb worked. I guess doing the erase in Odin made that work, thanks very much. the phone is now on 4.1.1, should I do a manual update or no?
Click to expand...
Click to collapse
Its up to you what you want to do, if you would like to update to VRAMC3 and keep the phone locked then you can go ahead and take the OTA. If you wanna unlock I would go ahead and unlock on VRALJB instead of updating, then flash the ROM of your choosing.
Sent from my SCH-I605 using XDA Premium HD app
if your stuck in a boot loop like i was, try the verizon wireless software upgrade assistant and use the repair assistant... worked for me!!
haskatice said:
if your stuck in a boot loop like i was, try the verizon wireless software upgrade assistant and use the repair assistant... worked for me!!
Click to expand...
Click to collapse
Do you mind uploading a copy of this program. I cant seem to find it anywhere and I desperately need it!
I can't find that verizon program anywhere either. I've tried most everything suggested. I even tried plugging in my wife's SCH-i605 and it didn't load the verizon program.
try the verizon wireless software upgrade assistant and use the repair assistant
Click to expand...
Click to collapse
Me three. Where's that software upgrade assistant at?
ok i got the same problem i took the ota 4.3 and im stuck in boot loop on samsung note 2 screen it just keeps flashing..
I have tried pulling the battery out i cant get into recovery it doesnt get that far... any ideas?
hayabusa3303 said:
ok i got the same problem i took the ota 4.3 and im stuck in boot loop on samsung note 2 screen it just keeps flashing..
I have tried pulling the battery out i cant get into recovery it doesnt get that far... any ideas?
Click to expand...
Click to collapse
I've been at this constantly since my earlier posts. I can't reliably say what's causing it but the only fix that I have is to restore a Nandroid backup of Clean ROM that I have then try again. Sometimes it reboots, sometimes it's bootloop. Weird.
I have same original issue. My i605 is stuck on Samsung boot screen and I cannot access recovery mode. Download works. I've tried root66 with PIT and NAND Erase via Odin 3.09 several times. Odin says PASS but phone never gets past boot screen. I rooted phone about 18 months ago and don't recall steps. I was running CM11 for past 6 months. Any ideas?
Got It
heggood said:
I have a sch-i605 verizon note 2. It is stuck in a boot loop. I can not access recovery, only download mode. I have flashed with odin over 20 times and am still stuck. I have tried all stock files, pit, all versions of odin, 3 different oem cables, 3 different pcs (1 win7 premium, 2 winXP), all 10 different USB ports. I have rebooted the pc's several times. I can get the stock samsung file from their site and the root66 stock rooted file to pass in odin but the phone is still in a bootloop. Please help if you can with any ideas, thanks!
Click to expand...
Click to collapse
just simply flash under the "PDA" tab.. i can include the link to it if u want
ive got the same kind of issue
heggood said:
I have a sch-i605 verizon note 2. It is stuck in a boot loop. I can not access recovery, only download mode. I have flashed with odin over 20 times and am still stuck. I have tried all stock files, pit, all versions of odin, 3 different oem cables, 3 different pcs (1 win7 premium, 2 winXP), all 10 different USB ports. I have rebooted the pc's several times. I can get the stock samsung file from their site and the root66 stock rooted file to pass in odin but the phone is still in a bootloop. Please help if you can with any ideas, thanks!
Click to expand...
Click to collapse
i get the go to verizon, go directly to verizon, do not pass go and bring 200 bucks for a new chump phone message after installing the new twrp app from the freekin play store. my device is supported as per their list of supported devices and i was trying to install 2.84 like they advised before going to 3.0. i cant even get it to turn off without cracking the case and removing the battery. plz advise... i love that phone so much, ghetto ass cracked screen and all. its rooted and running alliance rom 26 or 30 at the time of this most unfortunate event. send donations in lieu of flowers PLZ HELP
Completely stock, not rooted, locked bootloader running 4.1 and went for the 4.3 upgrade OTA and it downloaded the update completely fine and went through the update. But on the first initial reboot i got stuck at the Samsung Galaxy Note 2 screen when the phone first turns on. This is as far as it will go. I AM able to get into download mode by pressing home+power+ vol down. i AM NOT able to get it into recovery at any way possible. Found the stock 4.3 software and flashed it VIA odin and everything looks good. It has the downloading bar loading and it says PASSED with the green light. But still never boots past the Samsung Galaxy Note 2 logo at the beginning. Tried using the PIT file i found to repartition and still says passed with the same outcome.
It almost seems like to me that it deleted the ROM and has nothing to boot up. I've been scratching my head for 2 weeks. Any help would be much appreciated.
Bump
yzbrad99 said:
Completely stock, not rooted, locked bootloader running 4.1 and went for the 4.3 upgrade OTA and it downloaded the update completely fine and went through the update. But on the first initial reboot i got stuck at the Samsung Galaxy Note 2 screen when the phone first turns on. This is as far as it will go. I AM able to get into download mode by pressing home+power+ vol down. i AM NOT able to get it into recovery at any way possible. Found the stock 4.3 software and flashed it VIA odin and everything looks good. It has the downloading bar loading and it says PASSED with the green light. But still never boots past the Samsung Galaxy Note 2 logo at the beginning. Tried using the PIT file i found to repartition and still says passed with the same outcome.
It almost seems like to me that it deleted the ROM and has nothing to boot up. I've been scratching my head for 2 weeks. Any help would be much appreciated.
Click to expand...
Click to collapse
Just to get the fact you got the stock file here http://forum.xda-developers.com/showthread.php?t=2040264 and probably used this pit file from this guide http://forum.xda-developers.com/showthread.php?t=2024207?
You used the oem usb cable that came with the phone? I mean it sounds like it worked.
I did use that pit file but i used the stock file from a different source. Will try this new file in this new link. OEM cable and tried 2 other cables. Will report back...
MunkinDrunky said:
Just to get the fact you got the stock file here http://forum.xda-developers.com/showthread.php?t=2040264 and probably used this pit file from this guide http://forum.xda-developers.com/showthread.php?t=2024207?
You used the oem usb cable that came with the phone? I mean it sounds like it worked.
Click to expand...
Click to collapse
Ok so after messing with this for a while with different cords and different computers I think this thing is just hard bricked. I feel like I've tried everything. I just flashed back to stock on my Note 3 on the same computer with the same cord and it worked fine. But when I try with this Note 2 i'm having no luck.
I even tried deleting all drivers and reinstalling them. I'm using ODIN 3.09 and putting the TAR file in the AP slot and the pit file in the pit spot. Even tried not using the pit file. Still same result. It recognizes the Note 2 in the ODIN screen and accepts the TAR file and loads like normal, says PASSED in green but then on reboot it sticks at the Samsung Galaxy Note II logo. It never even wants to boot the ROM. I've been messing with tons of phones since my first Android and never been so stumped! About to send this to Samsung thinking it's a hardware issue.
I don't know how many Odin versions there are but I've only ever used 3.07 on the note 2. Would be worth a try.
Sent from my SCH-I605 using XDA Premium 4 mobile app
yzbrad99 said:
Ok so after messing with this for a while with different cords and different computers I think this thing is just hard bricked. I feel like I've tried everything. I just flashed back to stock on my Note 3 on the same computer with the same cord and it worked fine. But when I try with this Note 2 i'm having no luck.
I even tried deleting all drivers and reinstalling them. I'm using ODIN 3.09 and putting the TAR file in the AP slot and the pit file in the pit spot. Even tried not using the pit file. Still same result. It recognizes the Note 2 in the ODIN screen and accepts the TAR file and loads like normal, says PASSED in green but then on reboot it sticks at the Samsung Galaxy Note II logo. It never even wants to boot the ROM. I've been messing with tons of phones since my first Android and never been so stumped! About to send this to Samsung thinking it's a hardware issue.
Click to expand...
Click to collapse
no luck with this? im currently dealing with the same issue
Make sure after you odin with stock and pit file you go to the stock recovery(volume up, home and power) and do a factory reset and wipe cache! I had the same thing happin and got stuck at Verizon boot and the above worked for me and i have read in other posts that is what others suggest too!
Hope this help:thumbup:
Sent from my SCH-I605 using xda app-developers app
any update on this, i have one doing the same thing
Snakehn said:
any update on this, i have one doing the same thing
Click to expand...
Click to collapse
Goody68 said:
Make sure after you odin with stock and pit file you go to the stock recovery(volume up, home and power) and do a factory reset and wipe cache! I had the same thing happin and got stuck at Verizon boot and the above worked for me and i have read in other posts that is what others suggest too!
Hope this help:thumbup:
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
elykatupac said:
no luck with this? im currently dealing with the same issue
Click to expand...
Click to collapse
brandonhatty said:
I don't know how many Odin versions there are but I've only ever used 3.07 on the note 2. Would be worth a try.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No luck whatsoever. Ended up trying different Versions of ODIN, different computers, all different types of drivers, USB cables, OEM cables. NOTHING.
Called Samsung repair facility in Texas and the told me it was still under warranty. Lucked out! They repaired it for free. I honestly think the Verizon 4.3 OTA messed up something on the hardware, but don't really understand how.
I received this verizon Galaxy Tab 10.1 as a gift and a project, but haven't been able to make any progress.
The tablet was bought from a taxi company that used it was in car entertainment. When booted, an app immediately starts up and removes the navigation bar. If you are fast enough, you can get to the settings and uninstall this app before it starts, or what I have found to be easier, just use shell commands to hit home and uninstall while the app tries to regain control.
The table is currently running 3.2, and cannot update over wifi, nothing happens.
Root was gained by an unknown method, but the SU app won't open up. I can access su through the shell however.
I have tried flashing a cwm recovery through ODIN which says is successful but if it is booted straight to the recovery it is still stock.
Flashing ROM's through ODIN appear to be successful, but just boots right back to the original rom and recovery.
Adding anything to the SD card or anywhere else accessable to the stock recovery does not work either because the SD card is reformatted to the original contents every time.
This also occurs with any apps that are installed, each one is removed when rebooted except for SU. And Rom Manager FC's when CWM is attempting to flash.
nvflash will not work either because the bootloader is locked.
I don't know much about the boot sequence for android, but I looked for any init. files that are out of the ordinary and cannot find anything.
I'm giving this tablet away when I finally figure it out, I just want to fix it. Any help would be awesome and let me know if I've left something out.
Even if no one has any specific suggestions, can someone post a PIT file for a SCH-i905? I have seen the stock firmware that can be flashed through ODIN but it does not stick on my unit.
Thanks!
Excuse my English but my original language is Spanish.
The default verizon tablet brings in recovery an option that reloads the original recovery. If units installed CWM via Odin must access the recovery option (Vol +) on 1st boot and enter the option to leave cmw (reboot) will give you the option of not recovering the recovery.
The other alternative is to flash via odin the original software look it by google "PDA_HC31_EG01Ba_AP352081user_CP1033580_LTE20110704_0708"
in this case the tab stay with the factory version.
if the team does not have SIM must type top left - top right - bottom left, bottom right and then vol + to unlock.
good look
This is the post that you are needing.
http://forum.xda-developers.com/showthread.php?t=1342995
Sent from my SM-N900V using XDA Premium 4 mobile app
i had the same problem but pulling the sim and unlocking as mentioned above helped a lot then went through the whole rooting process through odin and have not had any issues with anything reverting back to stock. only issue now is not very many roms for our model "bummer" all in all still a good droid tablet for what i paid lol if you still havent got it going let me know and i will give you all the directions and steps i used
I have tried installing PDA_HC31_EG01Ba_AP352081user_CP1033580_LTE2011070 4_0708 through Odin3.
I do boot directly into recovery after installing CWM, the stock recovery still persists. I have tried several times because I know sometimes it does not stick.
I have also tried flashing the factory image linked in that xda post "[ROM]EG01 - Factory STOCK ODIN Image - VZW LTE Tab 10.1".
Boots right back up and starts the same taxi cab show case media software it normally does.
One thing I did not note in the first post. I do have root access when the tablet is booted into the os, but I do not when the tablet is in recover. I dont know if this is unusual or not.
I can also install busy box, but have yet to find out his would be useful.
I also do not have access to nvflash, but I think this is normal because the bootloader is not unlocked.
http://forum.xda-developers.com/showthread.php?p=49924392
Might work for you too. This is a post I made in another thread.
Sent from my Nexus 4 using Tapatalk
baystallion said:
http://forum.xda-developers.com/showthread.php?p=49924392
Might work for you too. This is a post I made in another thread.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Awesome, I'll give this a go when I get home.
Was there a p4vzw twrp version some where in those links?
Looks like all of the ones referenced were 3g and wifi only.
Sidenote: I don't care if I keep 4g functionality or not, I will only be using this for wifi, if that makes fixing the problem any easier.
hsbr said:
Was there a p4vzw twrp version some where in those links?
Looks like all of the ones referenced were 3g and wifi only.
Sidenote: I don't care if I keep 4g functionality or not, I will only be using this for wifi, if that makes fixing the problem any easier.
Click to expand...
Click to collapse
Search for infamous AOKP 4.2 thread. I think it has twrp for p4vzw.
Sent from my GT-P7500 using Tapatalk
eushaun99 said:
Search for infamous AOKP 4.2 thread. I think it has twrp for p4vzw.
Sent from my GT-P7500 using Tapatalk
Click to expand...
Click to collapse
I was able to find the thread, thanks!
After downloading the odin flashable twrp, I tried first with Odin3, but it failed. Then I flashed with JOdin, this first pulled a PIT file from the tab then failed to repartition. If I ran it without repartitioning it said it was sucessful, but if I boot straight into recovery the stock android recovery still comes up.
I have a way to get a pit file now though, so that's nice.
hsbr said:
I was able to find the thread, thanks!
After downloading the odin flashable twrp, I tried first with Odin3, but it failed. Then I flashed with JOdin, this first pulled a PIT file from the tab then failed to repartition. If I ran it without repartitioning it said it was sucessful, but if I boot straight into recovery the stock android recovery still comes up.
I have a way to get a pit file now though, so that's nice.
Click to expand...
Click to collapse
Don't use the Odin way. First flash cwm recovery, then flash the twrp zip file.
Sent from my GT-P7500 using Tapatalk
eushaun99 said:
Don't use the Odin way. First flash cwm recovery, then flash the twrp zip file.
Sent from my GT-P7500 using Tapatalk
Click to expand...
Click to collapse
I can't flash CWM in the first place. I have listed all of the different methods I tried flashing CWM with in the OP.
hsbr said:
I can't flash CWM in the first place. I have listed all of the different methods I tried flashing CWM with in the OP.
Click to expand...
Click to collapse
Oh, then I can't help you then. Sorry.
Sent from my GT-P7500 using Tapatalk
hsbr said:
Even if no one has any specific suggestions, can someone post a PIT file for a SCH-i905? I have seen the stock firmware that can be flashed through ODIN but it does not stick on my unit.
Thanks!
Click to expand...
Click to collapse
Yes please i have an issue my tablet got stuck on samsung logo i tried to flash another rom because i cant fing any rom for this tablet US Callular
i905. Tab 2 10.1.
If any one can provide a stock odin or something to make this tablet work i would appreciated?
Made this for myself, and noticed other people wanting it. If you are in anyway unsure of what your doing, please don't flash Odin packages. I'm not on here all that often to answer questions, so please refer to aaricchavez's thread as I'm sure the same questions will be asked.
I was able to flash by pulling the battery, then vol-dwn + home + pwr. Choose vol-up for downloader and flash. Worked on the second try. See screenshots bellow.
What you do to your phones on you, consider this: Warning flashing Bootloader/Modem/ FULL FIRMWARE LOLLIPOP
Updates seem to work best after a shutdown and battery pull. If camera stops working, clear your caches and reboot.
Flashable in Odin:
Bootloader/BL:
FOL1 Bootloader
FOL1 Bootloader
Phone/CP:
FOL1 Modem
FOL1 Modem
TWRP Recovery:
Recovery
My Customized Recovery:
2.8.7.0 Recovery
I have tried numerous times to install bootloader but it stays on dob1. I got the modem just fine. Don't understand why
Sent from my SM-G900T using Tapatalk
I've tried updating my bootloader& modem as well as the firmware in Odin 3.09 & 3.10 & all it keeps doing is failing can someone PLZ help
The only way I've been able to flash the last few modems and bootloaders is by pulling the battery, and even then It may take a few times. DOB1 took me 4 or 5 times.
And if your wondering, the modems a huge improvement. At least for me anyways. I'm up in the hills of the SF east bay and got very spotty LTE before, no longer an issue.
Could I use flashfire to flash the boot and modem?
Edit, I know it's possible to flash full firmwares but not sure about boot and modem
zounduser said:
Could I use flashfire to flash the boot and modem?
Edit, I know it's possible to flash full firmwares but not sure about boot and modem
Click to expand...
Click to collapse
Bootloader no modem yea
Tried using flashfire to install the modem but its not working. Still on ob1
Sent from my Samsung Galaxy S5 using Tapatalk
Can I flash just the modem if I'm already rooted using a CM12 ROM (Temasek unofficial)?
Does flashing a full stock ROM immediately update the bootloader and modem?
Can I flash just the modem if I'm already rooted using a CM12 ROM (Temasek unofficial)?
Click to expand...
Click to collapse
Yup. On rare occasion partitions respond in strange ways to odin flashing, ie. partitions other than what you're flashing become unwriteable. But for the most part that's a rarity.
Does flashing a full stock ROM immediately update the bootloader and modem?
Click to expand...
Click to collapse
Depends on your existing version, and the version your upgrading to, but with rare exception yes.
Is this the newest BL and modem for our phones?
highaltitude said:
Is this the newest BL and modem for our phones?
Click to expand...
Click to collapse
As of 10/10/15 FOG6 is, I just uploaded.
thanks for this. just realized today there was an update.. only a one letter difference, took a while to realize it!
can someone upload the new one?
Just wanted to add this. Was having a hard time flashing BL and CP
1. removed the sd card (tmobile thing I read somewhere)
2. took off the md5 off the file name so it was just a .tar file
3. put both files in to oden 3.11 and on the first flash had auto reboot NOT checked, then pulled the USB cable and pulled Battery.
4. then booted to download mode with cable in and and battery in and reflashed with auto reboot checked.
I installed omega rom v20 and I had a bootloop because I didnt have a 6.x.x bootloader and modem.
I came from 4.x.x and I almost just installed a stock 6.x.x to get the updated BL and CP, then root that.
I have had good luck with omega, but I use TB to clean out all the Samsung stuff. I purchased the App for $7, worth every penny.