G Pad 8.3 GPE (V510) restoring back to stock from soft brick

[Archon810]

Hey guys,

Today is one of those days. I got both the Z Ultra and the G Pad GPE, and the Z Ultra won't turn on, and the G Pad is soft bricked after only flashing TWRP and SuperSU and nothing else (which I've done countless times before).

After updating the G Pad 8.3 GPE to 4.4.2, I booted into fastboot and oem unlocked, then flashed TWRP from http://forum.xda-developers.com/showthread.php?t=2565431 and the latest SuperSU.

At this point, the tablet will no longer boot and will immediately kick back to TWRP. I've tried formatting data through TWRP and through fastboot format userdata, but it still boots to TWRP.

Usually, with a Nexus device, I'd just flash the factory image, but with a GPE, LG hasn't provided them (yet?). There's a thread dedicated to converting the V510 to V500 (http://forum.xda-developers.com/showthread.php?t=2564149), but it doesn't explicitly state that recovery of the V510 itself using those files would work, especially after it's already been updated to 4.4.4. I don't want to screw this up any further.

Any ideas at this point?

Thank you.

 

[djkinetic]

Hey guys,

Today is one of those days. I got both the Z Ultra and the G Pad GPE, and the Z Ultra won't turn on, and the G Pad is soft bricked after only flashing TWRP and SuperSU and nothing else (which I've done countless times before).

After updating the G Pad 8.3 GPE to 4.4.2, I booted into fastboot and oem unlocked, then flashed TWRP from http://forum.xda-developers.com/showthread.php?t=2565431 and the latest SuperSU.

At this point, the tablet will no longer boot and will immediately kick back to TWRP. I've tried formatting data through TWRP and through fastboot format userdata, but it still boots to TWRP.

Usually, with a Nexus device, I'd just flash the factory image, but with a GPE, LG hasn't provided them (yet?). There's a thread dedicated to converting the V510 to V500 (http://forum.xda-developers.com/showthread.php?t=2564149), but it doesn't explicitly state that recovery of the V510 itself using those files would work, especially after it's already been updated to 4.4.4. I don't want to screw this up any further.

Any ideas at this point?

Thank you.

In twrp goto advanced then file manager, navigate to /sdcard/TWRP and delete .twrps file, this controls the TWRP settings, reboot back into system, then recovery and it should see the partitions again.

 

[mpmilestogo]

Hey guys,

Today is one of those days. I got both the Z Ultra and the G Pad GPE, and the Z Ultra won't turn on, and the G Pad is soft bricked after only flashing TWRP and SuperSU and nothing else (which I've done countless times before).

After updating the G Pad 8.3 GPE to 4.4.2, I booted into fastboot and oem unlocked, then flashed TWRP from http://forum.xda-developers.com/showthread.php?t=2565431 and the latest SuperSU.

At this point, the tablet will no longer boot and will immediately kick back to TWRP. I've tried formatting data through TWRP and through fastboot format userdata, but it still boots to TWRP.

Usually, with a Nexus device, I'd just flash the factory image, but with a GPE, LG hasn't provided them (yet?). There's a thread dedicated to converting the V510 to V500 (http://forum.xda-developers.com/showthread.php?t=2564149), but it doesn't explicitly state that recovery of the V510 itself using those files would work, especially after it's already been updated to 4.4.4. I don't want to screw this up any further.

Any ideas at this point?

Thank you.

I had the exact same issue as you. I've tried any number of things including repacking the latest cm nightly and removing some lines from files that seemed would work. I can flash the gpad now but I get a blue and pink screen. I did have the recovery coming up each time no matter what as well. I did the zip you mentioned, but it needs to have a line removed from the zip archive that calls loki.sh or the flash will fail. I could not get the latest cm 11 nightly to work today. I'm going to try making the changes to the 510 to 500 package that will edit out the line that calls loki which fails each time at an assert line in the flashing.

I have not seen the regular OS in some time now and there are no restore images. I'm not sure with all the stuff I've done that it would come back but I think we need something like a zip archive we can flash that was made from a gpe device. I don't care if its the 4.4 or the 4.4.2 at this point.

I am going to try changing the archive you mentioned above this evening using 7zip and remove the line that calls for loki.sh and see if it works.

If I have no success, I'm going to reformat everything in twrp and open an RMA for it.

 

[djkinetic]

I had the exact same issue as you. I've tried any number of things including repacking the latest cm nightly and removing some lines from files that seemed would work. I can flash the gpad now but I get a blue and pink screen. I did have the recovery coming up each time no matter what as well. I did the zip you mentioned, but it needs to have a line removed from the zip archive that calls loki.sh or the flash will fail. I could not get the latest cm 11 nightly to work today. I'm going to try making the changes to the 510 to 500 package that will edit out the line that calls loki which fails each time at an assert line in the flashing.

I have not seen the regular OS in some time now and there are no restore images. I'm not sure with all the stuff I've done that it would come back but I think we need something like a zip archive we can flash that was made from a gpe device. I don't care if its the 4.4 or the 4.4.2 at this point.

I am going to try changing the archive you mentioned above this evening using 7zip and remove the line that calls for loki.sh and see if it works.

If I have no success, I'm going to reformat everything in twrp and open an RMA for it.

why would you install the v500 CM on a v510, when the kernel gets loki patched...as for a stock restore, the files are available, but you have to use LG Flash, problem is that the dll needed thats currently floating around does not work, there is an updated dll that was released, the source is trying to get a hold of it, as soon as its available a post will be maid. As long as you didnt bork the bootloader then a restore back to stock will be possible.

 

[Archon810]

why would you install the v500 CM on a v510, when the kernel gets loki patched...as for a stock restore, the files are available, but you have to use LG Flash, problem is that the dll needed thats currently floating around does not work, there is an updated dll that was released, the source is trying to get a hold of it, as soon as its available a post will be maid. As long as you didnt bork the bootloader then a restore back to stock will be possible.

Lovely. Hopefully, that means the restore is coming for me as well.

The difference between GPE and Nexus devices is so apparent to me now... at least Google always makes sure you can go back to stock.

 

[Jack Zheng]

Hey guys,

Today is one of those days. I got both the Z Ultra and the G Pad GPE, and the Z Ultra won't turn on, and the G Pad is soft bricked after only flashing TWRP and SuperSU and nothing else (which I've done countless times before).

After updating the G Pad 8.3 GPE to 4.4.2, I booted into fastboot and oem unlocked, then flashed TWRP from http://forum.xda-developers.com/showthread.php?t=2565431 and the latest SuperSU.

At this point, the tablet will no longer boot and will immediately kick back to TWRP. I've tried formatting data through TWRP and through fastboot format userdata, but it still boots to TWRP.

Usually, with a Nexus device, I'd just flash the factory image, but with a GPE, LG hasn't provided them (yet?). There's a thread dedicated to converting the V510 to V500 (http://forum.xda-developers.com/showthread.php?t=2564149), but it doesn't explicitly state that recovery of the V510 itself using those files would work, especially after it's already been updated to 4.4.4. I don't want to screw this up any further.

Any ideas at this point?

Thank you.

And i met the issue with my LG V500. And I use the download mode to install the original official rom. I am not sure it works on V510, But myabe you can try it.
1. Download the LG MOBILE SUPPORT TOOL by this link:http://www.lg.com/us/support-mobile/lg-V500-White
2. install the software in computer, Plug in USB cable with computer, Open the software LG MOBILE SUPPORT TOOL.
3. Turn off Pad and unplug.
4. press hold both volume up and volume down, Then plug in usb cable, And then pad is in downlaod mode
5. USB driver will be insatlled automatically
6. In LG MOBILE SUPPORT TOOL, click option---.country and language-OK, then click option--upgrade recovery
7. It will installe original official rom automatically.
8. After about 1.5 hours, The pad will be installed the last official room.

 

[Mixinitup4Christ]

Hey guys,

Today is one of those days. I got both the Z Ultra and the G Pad GPE, and the Z Ultra won't turn on, and the G Pad is soft bricked after only flashing TWRP and SuperSU and nothing else (which I've done countless times before).

After updating the G Pad 8.3 GPE to 4.4.2, I booted into fastboot and oem unlocked, then flashed TWRP from http://forum.xda-developers.com/showthread.php?t=2565431 and the latest SuperSU.

At this point, the tablet will no longer boot and will immediately kick back to TWRP. I've tried formatting data through TWRP and through fastboot format userdata, but it still boots to TWRP.

Usually, with a Nexus device, I'd just flash the factory image, but with a GPE, LG hasn't provided them (yet?). There's a thread dedicated to converting the V510 to V500 (http://forum.xda-developers.com/showthread.php?t=2564149), but it doesn't explicitly state that recovery of the V510 itself using those files would work, especially after it's already been updated to 4.4.4. I don't want to screw this up any further.

Any ideas at this point?

Thank you.

AutoPrime's Post contains the stock partitions for the V510. You should be able to flash those via fastboot to get back to stock. Heck, you might even try just flashing the recovery.

 

[mpmilestogo]

AutoPrime's Post contains the stock partitions for the V510. You should be able to flash those via fastboot to get back to stock. Heck, you might even try just flashing the recovery.

I'm game for flashing the recovery and the fastboot fun. Going to try the recovery first. Cannot be any worse than what it is now.

---------- Post added at 06:05 PM ---------- Previous post was at 05:22 PM ----------

AutoPrime's Post contains the stock partitions for the V510. You should be able to flash those via fastboot to get back to stock. Heck, you might even try just flashing the recovery.

I am most likely ignorant about things around tot files and how to flash them. The zip archive only contains a tot file. I am judging you need the LG flash tool for that file type. Someone mentioned that the existing DLL file would not work for LG flash.

Can someone verify that we need an updated DLL for LG Flash to flash the recovery tot file? Once we have that, we should be able to flash the recovery tot file using the LG tool?

 

[Mixinitup4Christ]

I'm game for flashing the recovery and the fastboot fun. Going to try the recovery first. Cannot be any worse than what it is now.

---------- Post added at 06:05 PM ---------- Previous post was at 05:22 PM ----------



I am most likely ignorant about things around tot files and how to flash them. The zip archive only contains a tot file. I am judging you need the LG flash tool for that file type. Someone mentioned that the existing DLL file would not work for LG flash.

Can someone verify that we need an updated DLL for LG Flash to flash the recovery tot file? Once we have that, we should be able to flash the recovery tot file using the LG tool?

You don't want the zip file just the recovery partition image. Once you have that downloaded, go in to fastboot and

fastboot flash recovery *location of file*/17-recovery.img

.

 

[oldblue910]

This is, unfortunately, a known issue with the Nexus 5 and Nexus 7 2013 as well.

With recent Google devices, the bootloaders have been tweaked to change the "chain of events" that happens during a bootloader unlock. No longer does the data wipe happen during the unlock process. Instead, the bootloader unlocks, then forces the boot chain to stock recovery upon the next reboot. Stock recovery then goes and wipes your data, and resets the boot chain back to normal boot.

This is where it gets tricky. If you flash TWRP before allowing stock recovery to wipe the data, you're going to get stuck. It appears that TWRP has no idea what to do with the automated commands that stock recovery interprets on that first post-unlock reboot. Since you flashed over stock recovery, it's going to boot to TWRP every time until the boot chain gets reset back to normal. This is something that the TWRP team will probably want to look at.

On Nexus devices this hasn't been a big deal because the stock recovery images are available via factory images. For the G Pad 8.3, though, this is a big problem. If someone has a copy of the stock recovery image, could you provide it for flashing to see if this fixes his problem?

 

[Archon810]

mpmilestogo, did flashing stock recovery work for you and if so, did it do anything?

 

[djkinetic]

mpmilestogo, did flashing stock recovery work for you and if so, did it do anything?

I can provide a stock recovery from 4.4 as far as I know the recovery is the same on 4.4.2 but I'm not entirely positive.

Sent from my LG-G2 using Tapatalk

---------- Post added at 03:29 PM ---------- Previous post was at 03:28 PM ----------

This is, unfortunately, a known issue with the Nexus 5 and Nexus 7 2013 as well.

With recent Google devices, the bootloaders have been tweaked to change the "chain of events" that happens during a bootloader unlock. No longer does the data wipe happen during the unlock process. Instead, the bootloader unlocks, then forces the boot chain to stock recovery upon the next reboot. Stock recovery then goes and wipes your data, and resets the boot chain back to normal boot.

This is where it gets tricky. If you flash TWRP before allowing stock recovery to wipe the data, you're going to get stuck. It appears that TWRP has no idea what to do with the automated commands that stock recovery interprets on that first post-unlock reboot. Since you flashed over stock recovery, it's going to boot to TWRP every time until the boot chain gets reset back to normal. This is something that the TWRP team will probably want to look at.

On Nexus devices this hasn't been a big deal because the stock recovery images are available via factory images. For the G Pad 8.3, though, this is a big problem. If someone has a copy of the stock recovery image, could you provide it for flashing to see if this fixes his problem?

Exactly why I let the tab complete the unlock and do a full reboot into system.

Sent from my LG-G2 using Tapatalk

 

[Archon810]

Exactly why I let the tab complete the unlock and do a full reboot into system.

Sent from my LG-G2 using Tapatalk

This should be a huge warning in ALL CAPS and red letters for TWRP threads then :S At least from now on. But since we hit the same problems before in Nexus devices, I think every thread should say it for safety.

 

[Archon810]

As for the recovery, please do. Should it just be flashable with fastboot?

 

[Mixinitup4Christ]

You don't want the zip file just the recovery partition image. Once you have that downloaded, go in to fastboot and

fastboot flash recovery *location of file*/17-recovery.img

.

As for the recovery, please do. Should it just be flashable with fastboot?

recovery partition image

 

[Archon810]

recovery partition image

Decided to take the plunge. We have a successful boot!!!

Didn't even flash it, just booted it live via fastboot.

c:\Users\Archon810\Downloads>fastboot boot 17-recovery.img
downloading 'boot.img'...
OKAY [  0.304s]
booting...
OKAY [  0.018s]
finished. total time: 0.322s

I suppose it did its thing that it was set out to do that TWRP didn't know to do and reset whatever flag was rebooting it into recovery every time. Spinning Android, then a reboot, normal loading logo, and now I'm at the setup screen.

Thank you, sir!

 

[djkinetic]

Decided to take the plunge. We have a successful boot!!!

Didn't even flash it, just booted it live via fastboot.

c:\Users\Archon810\Downloads>fastboot boot 17-recovery.img
downloading 'boot.img'...
OKAY [  0.304s]
booting...
OKAY [  0.018s]
finished. total time: 0.322s

I suppose it did its thing that it was set out to do that TWRP didn't know to do and reset whatever flag was rebooting it into recovery every time. Spinning Android, then a reboot, normal loading logo, and now I'm at the setup screen.

Thank you, sir!

Glad u got it to boot.

Sent from my LG-G2 using Tapatalk

 

[sualpine]

I too am in this camp. I can't fastboot flash the provided system img for V510 on my V510, it results in : FAILED (remote: data too large)

 

[Mixinitup4Christ]

I too am in this camp. I can't fastboot flash the provided system img for V510 on my V510, it results in : FAILED (remote: data too large)

Are you trying to flash system or recovery? What about running it live like Archon810?

fastboot boot *location of file*/17-recovery.img

 

[sualpine]

Are you trying to flash system or recovery? What about running it live like Archon810?

fastboot boot *location of file*/17-recovery.img

I flashed TWRP and formatted system data cache and internal storage forgetting that TWRP currently cant flash 4.4.X because of the binary error.

So ive been trying to fastboot flash system and it gives me that error.