Related
Just plugged the Gpad in to charge and this popped up. Hoping it's 5.0.
It's just sitting on 0% for the longest time.
I will update the status when I have something to report.
#fingerscrossed
-----------------------------
Updated on post:
Nothing. False alarm. I don't know how or why my tablet ended up on the update recovery screen because it was already powered on when I plugged it in, but no update.
That mode is only to update via lgflashtools....
My cousin's v410 is dead and I plugged it in to a USB wall charger. Some conductive trash must have been in the plug, I guess, because it rebooted to firmware update mode on me, instantly and from any state. If you see this mode unplug your tablet, hold down power to restart, and try a different cord or blow/clean the trash out of the plug.
Update to Lollipop lg G pad 7.0 lte v410 AT&T if you got a root issue
I had rooted my lg G pad and could not update to lollipop update this is how I got it to work. I removed the SD card and Sim card then I unrooted the tablet and restarted it. I also performed a hard reset from the settings menu. Make sure you unselected the data backup and automatic restore before resetting, now reset tablet. When it restarts just log into the WiFi and nothing else. Now go to settings and go to update center to find the firmware update download it and install it.
jlvvela84 said:
I had rooted my lg G pad and could not update to lollipop update this is how I got it to work. I removed the SD card and Sim card then I unrooted the tablet and restarted it. I also performed a hard reset from the settings menu. Make sure you unselected the data backup and automatic restore before resetting, now reset tablet. When it restarts just log into the WiFi and nothing else. Now go to settings and go to update center to find the firmware update download it and install it.
Click to expand...
Click to collapse
I'm too waiting for the same update, did you get any new link for that, mine is on 4.4.2 v41010d
No the update I got it through the settings menu on the tablet go to about tablet and then to check for updates that's how I got it.
Does anyone have any KDZ files?
I had a corrupted Stock ROM on a G Tab 7 Tablet due to applications that were installed by the previous owner; no matter what I did, Addware apps would always install on there own; I mean, even after restoring factory settings via the settings, or via the hardware combinations keys to reset to factory settings, It would reset the device but it would still install all the annoying apps as if they were Factory installed; weird, I had never seen something like this in any device I've worked on.
Anyways, since Factory Reset wouldn't help I had to Flash the Tablet.
I found the V41007h_0.kdz file which I was able to flash using the the LG Flash tool.
But now there is a a watermark in red "userdebug 4.20.17(42001700)" in the Home Screen.
So I'm hoping at the very least I can find a KDZ file to go back to the firmware version that the Tablet had which was V41010d.
Does anyone have any links to point me in the right direction?
If you can't post it in public, please Private message the links.
Thanks in advance for your help.
RaudelJr said:
Does anyone have any KDZ files?
I had a corrupted Stock ROM on a G Tab 7 Tablet due to applications that were installed by the previous owner; no matter what I did, Addware apps would always install on there own; I mean, even after restoring factory settings via the settings, or via the hardware combinations keys to reset to factory settings, It would reset the device but it would still install all the annoying apps as if they were Factory installed; weird, I had never seen something like this in any device I've worked on.
Anyways, since Factory Reset wouldn't help I had to Flash the Tablet.
I found the V41007h_0.kdz file which I was able to flash using the the LG Flash tool.
But now there is a a watermark in red "userdebug 4.20.17(42001700)" in the Home Screen.
So I'm hoping at the very least I can find a KDZ file to go back to the firmware version that the Tablet had which was V41010d.
Does anyone have any links to point me in the right direction?
If you can't post it in public, please Private message the links.
Thanks in advance for your help.
Click to expand...
Click to collapse
You've flashed a KDZ that contained a test build. If you follow the steps in my thread here http://forum.xda-developers.com/g-pad-10/general/tutorial-lg-gpad-v410-5-1-to-4-4-t3232150 then you can recover the lost space of your internal SD card and run custom ROMs. Unfortunately I don't think there is currently a way to go back to stock 5.0.2 from this point. If there is, it has not been documented in this form (to my knowledge).
Please post in my thread if you need help with that process.
jlvvela84 said:
No the update I got it through the settings menu on the tablet go to about tablet and then to check for updates that's how I got it.
Click to expand...
Click to collapse
I could not get it through SIM card because i don't have an AT&T SIM neither i live in the US nor AT&T has any services nearby, so i definitely need a zip file that might be an OTA or something that can be installed via ADB or system recovery. please share somethings for me.
Update LG Gpad 7.0
talvigi said:
I'm too waiting for the same update, did you get any new link for that, mine is on 4.4.2 v41010d
Click to expand...
Click to collapse
I was trying to update my GPad 7.0 to 5.0.2 or 5.1.0 from 4.4.2 and no OTA updates no matter what I do.
I'm on Android 4.4.2 with software version v41010d. Hardware says LG-V410 in "about tablet" section.
What's the quickest easiest way. I'm concerned that this is an older tablet and isn't updateable or has some update problems so that is the reason for my question. Maybe I'll keep it on 4.4.2 but wanted to run latest Kodi which won't work with anything but 5.0 or greater.
cejack said:
I was trying to update my GPad 7.0 to 5.0.2 or 5.1.0 from 4.4.2 and no OTA updates no matter what I do.
I'm on Android 4.4.2 with software version v41010d. Hardware says LG-V410 in "about tablet" section.
What's the quickest easiest way. I'm concerned that this is an older tablet and isn't updateable or has some update problems so that is the reason for my question. Maybe I'll keep it on 4.4.2 but wanted to run latest Kodi which won't work with anything but 5.0 or greater.
Click to expand...
Click to collapse
I never saw the OTA captured or a 5.X stock rom posted here, sorry. AT&T is notorious for blocking the release of firmware packages for their branded devices, so you won't find a V410 kdz from LG support either. If you can't get the System Update to work from the Settings menu, you might be stuck as far as stock goes. There wasn't much interest in updating stock in the community here because stock 5.0 patched the vulnerability that let us sign our own boot images. That effectively blocked TWRP and custom roms since the bootloader can't be unlocked. You could try the old take your sim out, reboot and check for the update trick. Some people say that doesn't work, and others swear by it.
There are plenty of 5.X and higher custom rom options, if you want to update the system that way. Tesla, Tipsy, and Validus were all 5.1 roms and they're still on androidfilehost.com. LOS and Candy have been updated up to 7.1. I keep Tesla on my V410 and it works great. All the custom roms rely on being on the 4.4 stock bootloader and radios since the kitkat bootloader was the only one vulnerable to the Bump exploit, so you're in a good place to start from.
jason2678 said:
I never saw the OTA captured or a 5.X stock rom posted here, sorry. AT&T is notorious for blocking the release of firmware packages for their branded devices, so you won't find a V410 kdz from LG support either. If you can't get the System Update to work from the Settings menu, you might be stuck as far as stock goes. There wasn't much interest in updating stock in the community here because stock 5.0 patched the vulnerability that let us sign our own boot images. That effectively blocked TWRP and custom roms since the bootloader can't be unlocked. You could try the old take your sim out, reboot and check for the update trick. Some people say that doesn't work, and others swear by it.
There are plenty of 5.X and higher custom rom options, if you want to update the system that way. Tesla, Tipsy, and Validus were all 5.1 roms and they're still on androidfilehost.com. LOS and Candy have been updated up to 7.1. I keep Tesla on my V410 and it works great. All the custom roms rely on being on the 4.4 stock bootloader and radios since the kitkat bootloader was the only one vulnerable to the Bump exploit, so you're in a good place to start from.
Click to expand...
Click to collapse
I find it strange that there isn't a separate device category on XDA for GPad 7.0. I guess there must be a reason - but it's probably too geeked out for a common humanoid like me to understand.
cejack said:
I find it strange that there isn't a separate device category on XDA for GPad 7.0. I guess there must be a reason - but it's probably too geeked out for a common humanoid like me to understand.
Click to expand...
Click to collapse
You aren't the first person to wonder about that. We requested a different forum for the V400/410 early on and it never happened. I don't know why. It does get confusing. You'll find the V400, V410, V480, V700 and probably a few more devices discussed here. A large majority of the development is for the V400/410, though.
Fastboot loop problem. pls help me.
Hi Dear Friends ( sorry my bad eng.)
I will tell you what I do.
1. My Device V410 AT&T version v41010b
2. İ setup my computer lg drivers & lg flash tool & lg one root and V41007h_0.kdz
3. i used one click root and successful.
4. i did my tablet download mode ( volume + and plug usb cable )
5. Start lg flash tool / select v41007h_0.kdz / and click CSE Flash button ( CDMA & DİAG )
6. Start Korean and Engilsh
7. Process pc screen %7 and tablet screen %6. and froze. i go to sleep early morning after 6 hours later. ı look process remain the same.
8. ı closed tablet unplug usb cable.
9. open tablet but only fastboot screen. ı try restart button after fastboot screen / i try restart bootloader select but only black screen.
10. power of and try open only fastboot screen.
what do I have to do now ? Please Help me.
Trane46 said:
Hi Dear Friends ( sorry my bad eng.)
I will tell you what I do.
1. My Device V410 AT&T version v41010b
2. İ setup my computer lg drivers & lg flash tool & lg one root and V41007h_0.kdz
3. i used one click root and successful.
4. i did my tablet download mode ( volume + and plug usb cable )
5. Start lg flash tool / select v41007h_0.kdz / and click CSE Flash button ( CDMA & DİAG )
6. Start Korean and Engilsh
7. Process pc screen %7 and tablet screen %6. and froze. i go to sleep early morning after 6 hours later. ı look process remain the same.
8. ı closed tablet unplug usb cable.
9. open tablet but only fastboot screen. ı try restart button after fastboot screen / i try restart bootloader select but only black screen.
10. power of and try open only fastboot screen.
what do I have to do now ? Please Help me.
Click to expand...
Click to collapse
Download twrp for the V410 to a computer, then connect the tablet to the computer and try using this command with fastboot:
Code:
fastboot boot twrp.img
That should boot you into TWRP without actually flashing it. If it works, from there you should be able to try to wipe and flash some roms. Sorry, but I'm not convinced it will work in the state your tablet is in. If your device is falling back to fastboot, your laf partition is blank or damaged and very possibly some other partitions are missing or damaged too, and that might prevent TWRP or roms from working right.
If that fails, you can use fastboot to restore the laf partition and hope that brings back download mode so you can try the kdz again:
Code:
fastboot flash laf laf.img
I've restored my laf this way; I actually intentionally nuked laf to enable fastboot. I can provide laf.img if you decide to try this.
I've searched but apparently it seems like most of the answers have been deleted or redacted.
My problem...
I was just given a Yoga Tab 2 from my sister who has given up on trying to fix it.
The tab was on 5.01 and rooted when she got a system update. She ran the update but now the tablet freezes during/after the boot animation.
It will go into fastboot but is not recognized by ADB.
She tried to install the original Lollipop firmware through recovery but ended up getting a system 7 error.
This is exactly what I see when in the bootloader screen
FASTBOOT MODE
PRODUCT_NAME - YT2
VARIANT - YOGA Tab1
HW_VERSION -
BOOTLOADER VERSION - unknown
IFWI VERSION - Blade_21.x64.0005.R00.1504101447 FFD8_X64_R_
SERIAL NUMBER - BaytrailD454B***
SIGNING - ?
SECURE_BOOT - ?
E: No valid installer medium found
I know nothing about Lenovo and how they do things but I know that with HTC you have to go back to 100% locked and stock before you can install an OTA. If you do try the OTA usually just won't install but unfortunately this thing seems to be at least soft bricked.
Is there a way for me to maybe roll back? I've read about people going back to KK in order to get the LP OTA but all links to the KK firmware are gone.
Thanks a lot, I appreciate any help I can get...
BTW, She is under warranty but of course she was rooted and is worried that repair will cost her almost as much as she paid for the Tab when they realize and void her warranty.
If its the same as the 1050f try these files.
http://tinyurl.com/zmmaww5
http://tinyurl.com/zgt7sjo do not bother about the warning with this one, its something to do with its size, just download it.
corasman said:
If its the same as the 1050f try these files.
http://tinyurl.com/zmmaww5
http://tinyurl.com/zgt7sjo do not bother about the warning with this one, its something to do with its size, just download it.
Click to expand...
Click to collapse
Thank you. I used the Restore KitKat Bios you posted along with an 830F specific KitKat firmware from the Russian Lenove site. Worked fine after editing the flash.xml file to allow for a larger system.img file.
The tablet is now back from the dead. Unfortunately it gets the 5.0 update but fails in the Lenovo Recovery when trying to flash the OTA. It gets to 100%, stays like that for a bit and then a blue X saying flash failed. After that I'm back to a black screen and have to reflash the kitkat firmware to get up and running again.
I have no idea why the OTA flash constantly fails but I guess I have to do a bit more research and hope I can get her up to date.
Did you set the country code , without setting it updates fail.
Look at this advice from ionioni to me about setting the code
http://forum.xda-developers.com/thinkpad-tablet/general/set-country-code-t3308024
corasman said:
Did you set the country code , without setting it updates fail.
Look at this advice from ionioni to me about setting the code
http://forum.xda-developers.com/thinkpad-tablet/general/set-country-code-t3308024
Click to expand...
Click to collapse
Outstanding!!! I entered the code in contacts and it gave me a menu of different countries to choose from. I Chose US and she rebooted, went into recovery, ran a bit and rebooted into another fresh install which looked completely different. We're talking different wallpaper, and different apps. After that it successfully installed 4 or 5 OTAs and as far as I can tell it is now completely up to date!
Android Version is 5.01
Build is S100250-160119
Kernel Version is 3.10.20-x86_64byt-g9f7fad7
Security patch is dated 2016-02-01
I'll wait a few days before I root and install Xposed just to be 100% certain it's up to date.
Of course my sister will probably ask for it back now.
Either way, THANK YOU VERY MUCH corasman!!! Your help has been invaluable!
I am so pleased it worked for you, ionioni helped me so much and now I am trying to do the same for others.
(Soft-)Bricked S7 Edge/G935F with FRP lock & DRK error, but no root/OEM unlock/ADB
Hello guys,
I bought a, what I thought to be, soft bricked S7 Edge (G935F) from the bay. It was listed as having sw issues, so I thought I could easily fix the issue myself. Stupid me, this one really isn't easy to fix. I've tried a lot of different hints that I found meandering around the web, but none of them have proofed working so far. I would appreciate some help because I don't seem to be making any progress.
When I got the phone, it would boot directly into Android Recovery with a dm-verity error on the bottom.
Below is what I have tried already:
1 . First I did the obvious, factory reset and wipe partition. No change.
2. Downloaded the latest firmware with updato (SM-G935F Region DBT) and flashed with Odin. It then booted into a screen with a hazard sign and a DRK error (Device does not have DRK, please install DRK first. press any button). Then returned to Android Recovery with variations of the DRK and dm-verity error messages
3. I flashed the same firmware again. This time the phone booted up to a Samsung error that said to use SmartSwitch's Emergency recovery. I tried but it asks for a recovery code and I don't have one.
4. I used an older version of SmartSwitch which gave me the initialization option where you need to input the device model and SN - SmartSwitch decided not to cooperate and noted that the S7 edge does not support initialization
5. I tried to flash CF-autoroot but it gave an error in Odin and failed because it is "Blocked by FRP Lock". I can't boot normally into android. Any workaround?
6. I used a dm-verity workaround file (G935FXXU1DQC4_FIX_DRK_dm-verity.tar) to actually get the phone booted up- but then it asks for the account information to do away with the FRP lock. And the former owner does not want to give me his login information. In addition, none of the workarounds (bluetooth, modem terminal prompts, etc.) did work.
7. Flashed oldest Android version I could find for the G935F - 5.1.1 - this gave me a prompt right after reboot that looks like the password request for encrypting memory. default_password and variations did not work. I am still stuck with...
No Support SINGLE-SKU
Supported API: 3
dm-verity error...
failed code : 0x02
...in the recovery
8. I flashed the combination file and was able to boot into Factory Binary and used the IMEI recovery option which is supposed to fix also the DRK issue. No luck.
So, this is where I am right now. If anyone out there still has sparks of hope, I would be delighted to hear about them.
Thanks much in advance!
Conversion software and ADB Shell
Small update - I booted into factory mode again using the conversion firmware. This way, I could connect to the device via ADB and use ADB shell. There is a guide (here: https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516) which guides through IMEI recovery using the conversion software and factory mode - that is supposed to also help with DRK issues. Did not work for me.
Another great guide (here: https://forum.xda-developers.com/no...fix-drk-dm-verity-factory-csc-serial-t3422965) used ADB shell to push and repair the DRK with some additional files. Since the device is not rooted, I did not get very far, either.
So, no progress whatsoever.
In summary, I can get the device booted up into factory mode using the conversion firmware, or, by using the dm-verity tweaked firmware, I can end up in the Google Account locked part of the initial start-up settings.
Any ideas?
Have you looked at the process to completely re-do a phone stuck in the Google auth log-in? At least that is how I understand where you are stuck. I have a phone arriving soon that I will need to re-flash to get out of that, via Odin.
JeffDC said:
Have you looked at the process to completely re-do a phone stuck in the Google auth log-in? At east that is how I understand where you are stuck. I have a phone arriving soon that I will need to re-flash to get out of that, via Odin.
Click to expand...
Click to collapse
Hi JeffDC,
Thanks a lot for the reply. How would this process look like? I have flashed the phone with all sorts of variations of Android L, M and N - plus the combination fw and the one with the dm-verity/DRK workaround which at least got the phone booted up. But then I am stuck at the google auth request.
I cannot flash anything custom since the FRP lock is on.
Hence, if there is any other way to re-do the phone as you are saying, I would live to hear about it.
https://forum.xda-developers.com/s7-edge/help/s7-edge-custom-binary-block-frp-lock-t3347688
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
https://forum.xda-developers.com/no...fix-drk-dm-verity-factory-csc-serial-t3422965
JeffDC said:
https://forum.xda-developers.com/s7-edge/help/s7-edge-custom-binary-block-frp-lock-t3347688
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
https://forum.xda-developers.com/no...fix-drk-dm-verity-factory-csc-serial-t3422965
Click to expand...
Click to collapse
Hi JeffDC,
Thanks a lot for the links.
Link #1: I can flash the file #1 and get the device visible for ADB by using the combination FW before starting the steps. Unfortunately, step #2 does not work due to lack of permissions. I guess because of missing root.
Links #2 and #3: These are the guides I was already referencing in my post #2 - they both do not work due to, I guess, missing root.
Smart Switch initialization
Update: I got smart switch to do the update and initialization for the device. Workaround was to use a different real serial number than the one of the actual device (I can only assume that it has got to do with country presets).
Cool stuff, all went smooth - but, still the same result. The device ends up in recovery showing the dm-verity error (failed code : 0x02) with FRP lock on and no root.
https://forum.xda-developers.com/ve...-factory-reset-protect-unlock-t3414590/page11
Interesting read, particularly ignoring the trojan squabbling.
Uses script and setup files to get around FRP.
I suggest you to re-try flashing with Odin the Stock Marshmallow Firmware. Then Boot Into Stock Recovery do a Full Wipe.
zzThrain said:
I suggest you to re-try flashing with Odin the Stock Marshmallow Firmware. Then Boot Into Stock Recovery do a Full Wipe.
Click to expand...
Click to collapse
Thanks for the recommendation. Done that (MM downgrade and full wipe) - same result, still DRK error only booting to recovery.
JeffDC said:
https://forum.xda-developers.com/ve...-factory-reset-protect-unlock-t3414590/page11
Interesting read, particularly ignoring the trojan squabbling.
Uses script and setup files to get around FRP.
Click to expand...
Click to collapse
Hi JEffDC, thanks for the follow-up hints. Very interesting read and approach. As commented in the other thread, I think the package download link in the opening post is dead. I am also curious to see 2 more complexities in action:
1. Will this work on a G935F variant (Exynos vs Snapdragon)?
2. The only way for me to get to the Google Account prompt is by using the modded dm-verity version mentioned in my first post - but I am not sure I can get ADB access enabled simultaneously
Good luck.
Deleted
Hey sathiere,
Came across this. It apparently removes the FRP before the system can start it up! Let me know what you think. I'm going to try it on a locked Edge next week or two. Seems to go right after the FRP protection file.
https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
and the download link works.
JeffDC said:
Hey sathiere,
Came across this. It apparently removes the FRP before the system can start it up! Let me know what you think. I'm going to try it on a locked Edge next week or two. Seems to go right after the FRP protection file.
https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
and the download link works.
Click to expand...
Click to collapse
Hi JeffDC, came across that thread last night - checked it out, but cannot really make sense of it just now. I will be posting directly in this one in the next minutes.
Regarding the link for the other thread - the google drive link for me shows invalid/no content...
sathiere said:
Hi JeffDC, came across that thread last night - checked it out, but cannot really make sense of it just now. I will be posting directly in this one in the next minutes.
Regarding the link for the other thread - the google drive link for me shows invalid/no content...
Click to expand...
Click to collapse
Yes, I am hoping for a response to my post there, near the end, clarifying. I think I get the method, and it's really pretty straight forward, really.
sathiere, I think basically what it does is provide two connections to the phone at the same time, one via Odin, and the other via direct ADB.
Step one is to flash a Universal boot loader, which is unlocked or can be unlocked via ADB. Now with the locked boot loader out of the way, on to getting rid of FRP.
Step two is run the. bat file which deletes the Persistence file, which is the Google encrypted setup file/FRP file. BOOM, FRP gone.
Then either stay on the Universal bootloader, or go back and flash the OEM.
Brilliant!
I have the same problem with a sm930f binary 2 boot loader. Stock Rom doesn't start and frp lock. How you fix it ? Thank you
Try this method
https://forum.xda-developers.com/general/general/solved-bypass-frp-lock-drk-error-t3779082
Hello, I'm a total novice when it comes to android modifications and whatnot, so I'll make this to the point.
I was trying to help my dad uninstall the bloatware on his Galaxy Grand Prime (running Lolipop 5.1.1), which includes some of the apps listed in this thread: https://forum.xda-developers.com/grand-prime/help/bloatware-apps-t3079843
I used Kingoroot (which I read worked with mixed results) to one-click root his phone and used Root Uninstaller (https://play.google.com/store/apps/details?id=com.kunkunsoft.rootuninstaller&hl=en) to uninstall Samsung Account, Samsung Push service, Samsung Billing, Galaxy apps, and TMobile TV. Root Uninstaller said it required a reboot to uninstall packages so I rebooted and was greeted with a never-ending TMobile splash screen that would vibrate 4 times every 10-ish seconds. I cannot boot into safe mode either as I've tried the methods shown on TMobile's own website to do so with this model to no avail.
I've tried looking up the vibrating splash screen and some said that means it's bricked.
Is there any way to fix this without any loss of data?
Thanks.
FlareF said:
Hello, I'm a total novice when it comes to android modifications and whatnot, so I'll make this to the point.
I was trying to help my dad uninstall the bloatware on his Galaxy Grand Prime (running Lolipop 5.1.1), which includes some of the apps listed in this thread: https://forum.xda-developers.com/grand-prime/help/bloatware-apps-t3079843
I used Kingoroot (which I read worked with mixed results) to one-click root his phone and used Root Uninstaller (https://play.google.com/store/apps/details?id=com.kunkunsoft.rootuninstaller&hl=en) to uninstall Samsung Account, Samsung Push service, Samsung Billing, Galaxy apps, and TMobile TV. Root Uninstaller said it required a reboot to uninstall packages so I rebooted and was greeted with a never-ending TMobile splash screen that would vibrate 4 times every 10-ish seconds. I cannot boot into safe mode either as I've tried the methods shown on TMobile's own website to do so with this model to no avail.
I've tried looking up the vibrating splash screen and some said that means it's bricked.
Is there any way to fix this without any loss of data?
Thanks.
Click to expand...
Click to collapse
You can downloa the official frimware and flash if with odin
ealam said:
You can downloa the official frimware and flash if with odin
Click to expand...
Click to collapse
Does that format the storage to do so or does it simply restore it to stock 5.1.1? I have no idea how to flash ROMs so pardon my questions.
FlareF said:
Hello, I'm a total novice when it comes to android modifications and whatnot, so I'll make this to the point.
I was trying to help my dad uninstall the bloatware on his Galaxy Grand Prime (running Lolipop 5.1.1), which includes some of the apps listed in this thread: https://forum.xda-developers.com/grand-prime/help/bloatware-apps-t3079843
I used Kingoroot (which I read worked with mixed results) to one-click root his phone and used Root Uninstaller (https://play.google.com/store/apps/details?id=com.kunkunsoft.rootuninstaller&hl=en) to uninstall Samsung Account, Samsung Push service, Samsung Billing, Galaxy apps, and TMobile TV. Root Uninstaller said it required a reboot to uninstall packages so I rebooted and was greeted with a never-ending TMobile splash screen that would vibrate 4 times every 10-ish seconds. I cannot boot into safe mode either as I've tried the methods shown on TMobile's own website to do so with this model to no avail.
I've tried looking up the vibrating splash screen and some said that means it's bricked.
Is there any way to fix this without any loss of data?
Thanks.
Click to expand...
Click to collapse
You can downloa the official frimware and flash if with odin
FlareF said:
Does that format the storage to do so or does it simply restore it to stock 5.1.1? I have no idea how to flash ROMs so pardon my questions.
Click to expand...
Click to collapse
No. It shouldn't format SD card storage or anything in sort. Although after flashing the firmware still doesn't fixed the bootloop issue your having then only way is to hard reset everything (which will wipe everything from data to storage files).
Check out this thread for flashing ROMs. It has great instructions for even beginners or noobs.
https://forum.xda-developers.com/grand-prime/general/guide-flashing-stock-rom-t3039167
Good luck
Hello, everyone,
I tried to install LineageOS on my S10 Plus yesterday. That worked so far, but I found that it didn't have a decent camera app and the Samsung Watch wasn't that easy to connect either. So I thought I'd just go back to the Stock ROM again. I then downloaded the latest stock firmware according to this guide and installed it with Odin. The installation also runs through, after the installation the mobile phone starts and after the start screen there is an Android man with the signature "Erasing". After a few seconds, the device turns off and stays black. Even if I put it on the charger or try to restart it, nothing happens. I keep getting into download mode and recovery, but that's about it. Multiple reinstallations and resets via the recovery didn't help - the phone just won't start.
I used the CSC_... and not the HOME_CSC_... at the firmware is the right one for my phone.
Is there any way I can salvage the device? I'm afraid that something in the memory is defective now, which has nothing to do with the flashing itself. Do you have any ideas?
Many thanks!
tefracky said:
Hello, everyone,
I tried to install LineageOS on my S10 Plus yesterday. That worked so far, but I found that it didn't have a decent camera app and the Samsung Watch wasn't that easy to connect either. So I thought I'd just go back to the Stock ROM again. I then downloaded the latest stock firmware according to this guide and installed it with Odin. The installation also runs through, after the installation the mobile phone starts and after the start screen there is an Android man with the signature "Erasing". After a few seconds, the device turns off and stays black. Even if I put it on the charger or try to restart it, nothing happens. I keep getting into download mode and recovery, but that's about it. Multiple reinstallations and resets via the recovery didn't help - the phone just won't start.
I used the CSC_... and not the HOME_CSC_... at the firmware is the right one for my phone.
Is there any way I can salvage the device? I'm afraid that something in the memory is defective now, which has nothing to do with the flashing itself. Do you have any ideas?
Many thanks!
Click to expand...
Click to collapse
same thing happened to me today. but I flashed my s10e the bootloader and modem file of android 9 from twrp, the phone did not boot up and I loaded the stock rom again, then when I open it, it's the same as yours, I really need urgent help.
Releases · corsicanu/9820-bootloaders_and_modems
Contribute to corsicanu/9820-bootloaders_and_modems development by creating an account on GitHub.
github.com
EDİT: Anyway, I solved the problem, I flashed the bootloader and modem file that is suitable for my current version from the same site with twrp and the phone turned on. maybe you can solve it by flashing the bootloader and modem file suitable for the current version. try if you want
Thanks a lot, this worked!
tefracky said:
Thanks a lot, this worked!
Click to expand...
Click to collapse
I'm glad it worked.
I was very afraid that the phone died, what did you do for 5 days in this state?
Now I have a question in my mind: When Samsung releases an update in the future, will the bootloader and modem files be updated when we update it with odin? won't it be updated? After that, do we will always update manually as twrp? do you have any idea?
Well, I simply didn't use a mobile phone in these days. It was a very "interesting" experience, but not a huge problem. I sometimes opened WhatsApp as Windows App (interestingly, which works without phone).
I don't know, what happens at a Samsung Update, but until Android 13, I will not update (so probatly never). In our German forum (www.android-hilfe.de), a pre rooted and debloated "Stock"-Firmware is provided, but I can't install it, since my Bootloader is too new (V15 instead V14 for the ROM). When it is possible, I will install this firmware. If you are interested, here is the link: https://www.android-hilfe.de/forum/...3-2022-stock-rom-v2-0-pre-rooted.1000713.html
tefracky said:
Well, I simply didn't use a mobile phone in these days. It was a very "interesting" experience, but not a huge problem. I sometimes opened WhatsApp as Windows App (interestingly, which works without phone).
I don't know, what happens at a Samsung Update, but until Android 13, I will not update (so probatly never). In our German forum (www.android-hilfe.de), a pre rooted and debloated "Stock"-Firmware is provided, but I can't install it, since my Bootloader is too new (V15 instead V14 for the ROM). When it is possible, I will install this firmware. If you are interested, here is the link: https://www.android-hilfe.de/forum/...3-2022-stock-rom-v2-0-pre-rooted.1000713.html
Click to expand...
Click to collapse
thanks, if i'm going to use stock rom i prefer to root it myself