Database Users

Soft Bricked!! I think?

hey guys pretty sure I soft bricked my s4(NC5). I was trying to revert my Hyperdrive root back to factory cause the wifi wasn't working. But I think when I thried to unroot it erased everything. I can get phone into download mode still. And when I turn on the phone I get: Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. Tried Kies but program doesn't recognize my phone. Installed/re-installed drivers, but didn't fix. I'm pretty new to customizing my phone this way, but all I want is my phone back to factory. If anyone can fix this with Odin or something I would appreciate a walkthrough or link to another forum if there is 1.

Just flash the latest stock rom and you will be fine.

LG GPad 7.0 LTE (v410) Firmware Update (?)

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.

Odin doesn't recognize my s7 edge (trying CF auto root)

Hi, I've been reading the thread for CF auto root to give it a go. I've downloaded the drivers (I've got 1.5.51 now installed, haven't been able to find later ones), I've got the 2.74 SU version that helps to overcome a recent security policy update issue reverting root status and the CF auto root zip file (CF-Auto-Root-hero2lte-hero2ltexx-smg935f.zip) which has odin 3.10.6 included (not quite sure if I can use any recent odin version). I even got my stock firmware com sammobile and extract the proper boot.img from the AP* file (just in case I got something wrong at sometime). I've enabled the OEM unlock too on developer options. I understand I can give it a go without having to go with a custom recovery (still not sure and haven't got the whole picture about the dm-verity thingy and what effects has on the device but someone mentioned something like loosing the encryption or so). This is my first try on getting root on my s7 edge G935F (international version), so it shouldn't have any boot.img problem (but trying to be prepare since I can't go about without my phone being working).
So, I've got my phone into download mode, started odin, loaded on AP the tar.md5 file from the CD auto root zip file (CF-Auto-Root-hero2lte-hero2ltexx-smg935f.tar.md5), connect the device throuhg usb cable and I was expecting Odin to recognize it but nothing happens. Since in the threads I've been researching for s7 edge there is no indication on waiting to see something happening on ODIN (but in some other threads - not s7 edge related though - mention something about having to see a blue indicator on COM), I'm not quite sure if I'm expected to just hit start even if no apparent change is happening on ODIN nor there is some drivers installing/configuring when connecting the device on download mode. Since I'm quite new to this, I'm no sure if I should connect the device first with some other option enabled, like USB debugging or if I'm missing something quite obvious for someone familiar with flashing with odin?
Kind regards for any help!
PS. I did tried to find an answer through searching but foung nothing related s7 edge wise so I'm at a loss not even knowing if just hitting start without having the device recognized on ODIN will do any harm at all (that newbie I am)

Try odin 3.11
Aldo plug your phone in first and than once recognised load the autoroot to ap

skinza said:
Try odin 3.11
Aldo plug your phone in first and than once recognised load the autoroot to ap
Click to expand...
Click to collapse
Thank you skinza for your reply, I did tried what you suggested and although it wasn't enough for getting it solved it helped me to know I was on the correct path and that I could use an updated odin.. finally, the problem was on embarrassing one since I went into download mode but hadn't push the volume up to get into the actual ODIN mode (too newbie of me but I was trying to follow the instructions I'd found and none were that specific - a bit afraid of messing it up). Nonetheless, thanks again for your time! Kind regards!
Edit: Now I'm rooted (thanks CF) and it took less than expected (a couple of mins or so). I didn't go the custom recovery way, so it might have been that.

cmanh said:
Thank you skinza for your reply, I did tried what you suggested and although it wasn't enough for getting it solved it helped me to know I was on the correct path and that I could use an updated odin.. finally, the problem was on embarrassing one since I went into download mode but hadn't push the volume up to get into the actual ODIN mode (too newbie of me but I was trying to follow the instructions I'd found and none were that specific - a bit afraid of messing it up). Nonetheless, thanks again for your time! Kind regards!
Edit: Now I'm rooted (thanks CF) and it took less than expected (a couple of mins or so). I didn't go the custom recovery way, so it might have been that.
Click to expand...
Click to collapse
Not a problem mate
Just fyi you will need twrp if you want to install custom roms like superman rom or echo rom etc

skinza said:
Not a problem mate
Just fyi you will need twrp if you want to install custom roms like superman rom or echo rom etc
Click to expand...
Click to collapse
Thanks again! for now I won't be going for a custom rom but wanted to be able to install a firewall to stop some apps from draining my prepaid data (limited)..
I was planning on having xposed installed but it seems I need a custom recovery for that as well.. I used to have xprivacy on a previous nexus 4 and loved I could limit some permissions that are still missing now on marshmallow but haven't got a grip yet as per the effects due to the dm-verity thing.. would you happen to know anything about it? and I was also wondering about if I do need to have the OEM unlock still enabled now that I'm rooted? (The later because I'd been robbed of my cellphones in the past - even recently a new s7 edge that didn't last me even a month and wouldn't want to let them have an easy pie on having the device available)
Regards!

I'm facing the same issue but even after going into download mode properly after pressing vol up
odin doesn't detect my s7 edge
I've installed all the drivers also

Singhathia said:
I'm facing the same issue but even after going into download mode properly after pressing vol up
odin doesn't detect my s7 edge
I've installed all the drivers also
Click to expand...
Click to collapse
Got the same issue. I'm new with this. My colleague wants me to learn and test and load Lineageos on some brand new S7 G930F devices he gave me which I have already switched to dev mode with OEM unlock and USB debugging on and the devices smoothly jumped into ODIN downloading.... mode
I also have the proper Samsung USB Driver installed. (did it several times after ODIN didn't recognize my device)
However, according to the manual, I should start up ODIN, then connect the device via USB cable to the workstation (as unsuccessful I already tried 3 workstations with Windows 7 and Windows 10) whilst having the phone in download mode... .BUT NOTHING APPEARS in the Log field and the ID:COM Box doesn't change colour and my manual says that it should.
My workstation however recognizes the devices with positive messages so I guess the drivers are good.
My co-worker gave me ODIN v3.10, but as this didn't work I downloaded and installed V3.12, but unfortunately also without any luck.
What am I doing wrong?

which OS?

S7 edge SM-G935F
Hey guys,
i tried rooting my s7 edge but after i got into TWRP my phone went into a bootloop. when i got back download mode, odin still found my phone, though everytime i tried to enter TWRP again, odin said there was a FAIL and my phone immediatly went back into bootloop. I tried to reinstall the samsung usb drivers but now odin cant find my phone anymore.
Before i screw up even more, can someone please help me? right now im stuck in download mode and odin 12, 11, and 10 all wont recognize my phone, also not if i use different cables. my windows laptop however still gives me the device found and device disconnected sound everytime i (dis)connect my phone.
any ideas?
thanks
EDIT: Okay i tried my USB 3.0 port and now odin found my phone. just weird... now i just need to solve the problem that I'm still stuck in the Bootloop but that probably doesnt belong in this thread

did i brick my device?

basically this is how it went, installed an android 10 rom, it was buggy so i flashed back to stock miui with adb to fully reset everything, installed a recovery and went back to pixel experience
now the phone won't recognize my sim card and wont find any wifi connections, miui also did not find any wifi connections and wont recognize the sim either
am i screwed? is my device bricked?

Have you used the tool from xiaomiflash.com for the stock ROM?

Probably lost IMEI too? Modem could be broken and needs to be reflashed. No way without edl i guess. I dont know. Needs some pro advice. I would like to know about this too.

7enas said:
Probably lost IMEI too? Modem could be broken and needs to be reflashed. No way without edl i guess. I dont know. Needs some pro advice. I would like to know about this too.
Click to expand...
Click to collapse
yeah that was the problem, i added a few lines to the terminal in twrp and fixed it

good afternoon , loop infinite
I have a problem, after installing the recovery I installed a custom custom rom the viperos, after restarting it gave an infinite loop in the logo, then I tried to install the syberiam rom and I also stay in the infinite loop, and so two other rom , and I can not flash the original rom with the XiaoMiFlash.exe, I thank from now and who can give me a light ...
greetings from brazil

Device not starting/black screen after stock-ROM flash via Odin

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