I am sorry for opening this thread.
After 2 days of waiting, it seems that the 3G forum section is useless in terms of helping the ones in need.
My issue: after i updated via OTA, the tablet, the 3G stopped working, the OTA corrupted the radio partition, and now it seems that my tablet is on first baseband (a backup radio it seems) released with the device which has some issues (wifi signal very crappy)
In fastboot the baseband appears N/A
My request, if someone knows, on which emmc partition is stored the radio i would be very grateful.
Also a dump of that partition would help also.
I cannot flash the radio via fastboot
apia-1231_0.17.0_1205.img
sending 'radio' (16384 KB)...
OKAY [ 2.001s]
writing 'radio'...
FAILED (remote: (BadParameter))
finished. total time: 2.018s
Also trying to dump the partition on the usual mount point results this
dd if=/dev/block/platform/sdhci-tegra.3/by-name/RDO of=/sdcard/RDO.img
/dev/block/platform/sdhci-tegra.3/by-name/RDO: cannot open for read: No such file or directory
In theory i should be able to restore by using the dd on the emmc partitions, but i don`t know which one it is.
ls /dev/block/mmcblk*
ls /dev/block/mmcblk*
/dev/block/mmcblk0 TO BIG
/dev/block/mmcblk0boot0 2.048KB (bootloader)
/dev/block/mmcblk0boot1 2.048KB (bootloader backup)
/dev/block/mmcblk0p1 12.288KB (boot or recovery)
/dev/block/mmcblk0p2 8.192 KB
/dev/block/mmcblk0p3 TO BIG
/dev/block/mmcblk0p4 TO BIG
/dev/block/mmcblk0p5 512KB
/dev/block/mmcblk0p6 10.240KB (boot or recovery)
/dev/block/mmcblk0p7 5.120KB
/dev/block/mmcblk0p8 512KB
/dev/block/mmcblk0p9 TO BIG
In my first look this is what i found, if someone can assist me with this, there are multiple users with this issue, so also others at some moment will be grateful if we fix this.
1) On which partition is the radio stored
2) Can someone dump that partition using dd ?
Again, sorry for creating this post, i don`t usually do things like this (old user, know how the things work around here), but i am a little bit desperate.
Managed to fix partially the issue.
In bootloader the Baseband still appears as N/A
What I did.
1) Mounted radio-tilapia-1231_0.18.0_0409.img
2) Copied the radio_update.zip
3) Rebooted the Tablet in RECOVERY
4) Presse Power Key and Volume Key Plus (first power key, while you keep the power pressed, press the volume key for 2 seconds, release)
5) Select "Apply Update From ADB"
6) Issue the command "adb sideload radio_update.zip
7) Wait till the update goes to end,, and select Reboot system now.
Now when you check in Settings/About Tablet/Baseband, you should have the Baseband which you applied via adb
For those in need, here is the radio_update.zip
http://globula.arctablet.com/Nexus7/radio_update.zip
Still the question remains open, HO KNOWS WHAT PARTITION IS THE ONE FROM THE RADIO ?
Hello
I have exactly the same issue reported by globula neagra.
In my case the issue started just after Nexus came back from Asus repair center with the motherboard replaced. .
As the radio cannot be flashed, the ota procedure fails.
Any idea how to recover the radio partition in order to flash the correct radio image file?
Regards.
My N7 2012 has the same symptoms (Baseband N/A in fastboot) after getting it back from Asus a couple of weeks ago. I believe they replaced the motherboard of my N7 if that matters. I was able to adb sideload the radio from 4.3 then fastboot all factory images from the latest update and then relock. Not sure if I should send it back since it will not install otas on its own, and I will have to adb sideload the radio every update. Thanks op for the info on adb radio update.
Sent from my Nexus 7 using xda app-developers app
My Nexus 7 2012 has the same problem. I could not update OTA and also fastboot update fails, because of Baseband N/A. Now I'm on 4.3 but with old Baseband. I didn't update it, because looks like everything is running.
Before my one was two times in service at Asus. One time they replaced the mainboard.
For sure the solution of globula neagra is a good workaround, but it is very strange that, after the motherboard replacement, you cannot update anymore a standard product with a standard OTA procedure.
Maybe something could be revised in the replacement process.....
flaps1970 said:
For sure the solution of globula neagra is a good workaround, but it is very strange that, after the motherboard replacement, you cannot update anymore a standard product with a standard OTA procedure.
Maybe something could be revised in the replacement process.....
Click to expand...
Click to collapse
UP
Can someone dump that partition using dd, as asked by Globula Neagra?
I don`t understand what exactly you talk about .. radio partitions etc. but if that helps I had a problem with the memory of the tablet: have 32g + gsm N7 and in storage tab it appears only 6gb availabale, so I downloaded nakasig-jwr66y-factory-bdbb7bd7.tgz , extracted the archive and in created folder there was
bootloader-tilapia-4.23.img
flash-all.bat
flash-all.sh
flash-base.sh
image-nakasig-jwr66y.zip
radio-tilapia-1231_0.18.0_0409.img
Using windows 8 I executed in CMD flash-all.bat and the script flashes the radio,bootloader,stock rom and many other things that I did not seen before.I can`t provide a link for download but it is in the forum.I`ll be happy if that can help you solve your problem! Just flash without fear
Blown_ouT said:
I don`t understand what exactly you talk about .. radio partitions etc. but if that helps I had a problem with the memory of the tablet: have 32g + gsm N7 and in storage tab it appears only 6gb availabale, so I downloaded nakasig-jwr66y-factory-bdbb7bd7.tgz , extracted the archive and in created folder there was
bootloader-tilapia-4.23.img
flash-all.bat
flash-all.sh
flash-base.sh
image-nakasig-jwr66y.zip
radio-tilapia-1231_0.18.0_0409.img
Using windows 8 I executed in CMD flash-all.bat and the script flashes the radio,bootloader,stock rom and many other things that I did not seen before.I can`t provide a link for download but it is in the forum.I`ll be happy if that can help you solve your problem! Just flash without fear
Click to expand...
Click to collapse
So it will erase all apps and data on N7?
vndnguyen said:
So it will erase all apps and data on N7?
Click to expand...
Click to collapse
Yes in that case executing the flash-all.bat it will wipe all the data and apps but you can try to manualy flash the radio and the bootloader with that latest version...and like I understand your problem you can`t lose much...still you can`t use your device
@Blown_ouT
I did tried several approaches, and actually what you are saying above broke my device and created the issue with the radio.
The bootloader is saying that my radio partition does not exist anymore, therefore you can not flash something that is not existent, and your method does not work.
Tough, the partition is not vanished it must be there but i think is corrupted somehow.
When i broke the device first time i did this:
1) Update the tablet using the OTA
2) Result was a broken radio
3) Tried to re-flash the tablet using the stand alone pack
-when i did this, i did not wanted to unlock the tablet, still the cmd file runned and erased everything from the tablet but not flashed nothing, which is the most stupid thing since i did not unlocked the device and therefore the restrictions were up (which are supposed to be in theory a non access to erase/write but still google allows you to brick your device with the cmd file without unlocking, but does not allow you to fix it till you unlock it, again VERY STUPID)
-i was able to flash all the files one by one except the radio
globula_neagra said:
@Blown_ouT
I did tried several approaches, and actually what you are saying above broke my device and created the issue with the radio.
The bootloader is saying that my radio partition does not exist anymore, therefore you can not flash something that is not existent, and your method does not work.
Tough, the partition is not vanished it must be there but i think is corrupted somehow.
When i broke the device first time i did this:
1) Update the tablet using the OTA
2) Result was a broken radio
3) Tried to re-flash the tablet using the stand alone pack
-when i did this, i did not wanted to unlock the tablet, still the cmd file runned and erased everything from the tablet but not flashed nothing, which is the most stupid thing since i did not unlocked the device and therefore the restrictions were up (which are supposed to be in theory a non access to erase/write but still google allows you to brick your device with the cmd file without unlocking, but does not allow you to fix it till you unlock it, again VERY STUPID)
-i was able to flash all the files one by one except the radio
Click to expand...
Click to collapse
Hello, just an update about this issue,
I started the RMA procedure and ASUS replaced me the motherboard again (already one had been replaced).
Yesterday i received back the Nexus, nothing had changed, the tablet has exactly the same issue.
At this point, i think there are only three possibilities:
1) all the motherboards used in the Repair center are faulty
2) there is something wrong in the ASUS procedure
3) the problem is not related to the motherboard but is somewhere else
I am very frustrated about this situation, 5 months of tablet and three times in repair center without repairing the issue.
flaps1970 said:
Hello, just an update about this issue,
I started the RMA procedure and ASUS replaced me the motherboard again (already one had been replaced).
Yesterday i received back the Nexus, nothing had changed, the tablet has exactly the same issue.
At this point, i think there are only three possibilities:
1) all the motherboards used in the Repair center are faulty
2) there is something wrong in the ASUS procedure
3) the problem is not related to the motherboard but is somewhere else
I am very frustrated about this situation, 5 months of tablet and three times in repair center without repairing the issue.
Click to expand...
Click to collapse
I do think is an issue on a software level.
Google/Asus don`t want to admit that the updates are "braking" the tablets.
Geez, I have the same problem, I also got my Nex7 GSM from the repair with the new motherboard.
They had one job....
globula_neagra said:
My issue: after i updated via OTA, the tablet, the 3G stopped working, the OTA corrupted the radio partition, and now it seems that my tablet is on first baseband (a backup radio it seems) released with the device which has some issues (wifi signal very crappy)
In fastboot the baseband appears N/A
Click to expand...
Click to collapse
When ASUS replaced my device's motherboard they reinstalled the factory 4.2 instead of the 4.4.4 it was on at the time. During the 4.3 OTA upgrade the device hung and now the baseband is N/A in the bootloader menu. Trying to flash factory images or just the radio itself obviously doesn't work.
Other than your excellent sideload work-around, have you found a proper fix for the radio partition itself?
globula_neagra said:
ls /dev/block/mmcblk*
/dev/block/mmcblk0 TO BIG
/dev/block/mmcblk0boot0 2.048KB (bootloader)
/dev/block/mmcblk0boot1 2.048KB (bootloader backup)
/dev/block/mmcblk0p1 12.288KB (boot or recovery)
/dev/block/mmcblk0p2 8.192 KB
/dev/block/mmcblk0p3 TO BIG
/dev/block/mmcblk0p4 TO BIG
/dev/block/mmcblk0p5 512KB
/dev/block/mmcblk0p6 10.240KB (boot or recovery)
/dev/block/mmcblk0p7 5.120KB
/dev/block/mmcblk0p8 512KB
/dev/block/mmcblk0p9 TO BIG
Click to expand...
Click to collapse
Still the question remains open, HO KNOWS WHAT PARTITION IS THE ONE FROM THE RADIO ?
Click to expand...
Click to collapse
By now it's probably common knowledge to you and others with this problem that when the Nexus 7 3G gets into this state, the radio partition doesn't show up in the list anymore. My tablet broke before I could have a look at what correct partition information looks like, and there isn't much about it on the Internet either. However, these seem to agree:
http://forum.xda-developers.com/showpost.php?p=35103211&postcount=16
http://www.0jl.com/blog/?p=2196
http://forum.xda-developers.com/showthread.php?p=45045265#post45045265
E.g.:
Code:
Device "/ dev / block / mmcblk0p1", the name of "SOS", format emmc, capacity 12M, mount --- storage recovery
Device "/ dev / block / mmcblk0p2", the name "LNX", format emmc, capacity 8M, mount --- storage boot
Device "/ dev / block / mmcblk0p3", the name "APP", format ext4, the capacity of 650M, mount "/ system", the storage system
Device "/ dev / block / mmcblk0p4", the name "RDO", format emmc, capacity 16M, mount --- store radio
Device "/ dev / block / mmcblk0p5", the name "CAC", format ext4, the capacity of 443M, mount "/ cache", storage cache
Device "/ dev / block / mmcblk0p6", the name "MSC", format emmc, capacity 512K, mount --- storage misc
Device "/ dev / block / mmcblk0p7", the name "USP", format, capacity 10M, mount --- storage ---
Device "/ dev / block / mmcblk0p8", the name "PER", format, capacity 5M, mount --- storage ---
Device "/ dev / block / mmcblk0p9", the name "MDA", format, capacity 512K, mount --- storage ---
Device "/ dev / block / mmcblk0p10", the name "UDA", format ext4, capacity 28G, mount "/ data", storage userdata
and
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
IOW, compared to grouper the tilapia has an extra 16M radio partition inserted at mmcblk0p4.
Tablets in this state had this partition corrupted or deleted. Would it be correct to deduce that the problem can therefore be fixed by correctly recreating the partition table and then reflashing the machine?
I'm only familiar with working with Windows partitions and haven't been able to find instructions for recreating the Nexus 7 3G's partition table specifically. Is the above information sufficient for doing that, and what commands are needed? My tablet's currently on 4.2.2 and comes with both fdisk and parted.
Thanks in advance,
Francois
globula_neagra said:
My issue: after i updated via OTA, the tablet, the 3G stopped working, the OTA corrupted the radio partition
Click to expand...
Click to collapse
This seems to be the common experience with radio partition corruption. It also seems the process that leads to this corruption could involve a corrupt bootloader.
It turns out that both recent factory images as well as at least the 4.3 OTA for the Nexus 7 3G contain a corrupt bootloader, see http://forum.xda-developers.com/nexus-7/general/info-nexus-7-3g-ota-bootloader-corrupt-t3033513. This means whether Android software is being installed manually or automatically, the target machine is potentially exposed to the corrupt bootloader.
Most firmware installs that include a new bootloader and radio software first install the bootloader, then boot into that, then next proceed with installation of the radio software, and then whatever else.
This opens up the possibility that failure to install and activate the new bootloader contributes to corruption of the radio partition when its upgrade is attempted. If I manage to test this once my machine is returned from repairs I hope to update. Any other thoughts or contributions in the meantime will be appreciated. Especially towards fixing the radio partition.
Related
Hi Everyone,
I thought I'd create a thread for this issue as it seems to be happening at an alarming frequency as of late. Here are some other threads for reference:
http://forum.xda-developers.com/showthread.php?t=1038768&highlight=recovery+mount+open
http://forum.xda-developers.com/showthread.php?t=1035464&highlight=recovery+mount+open
http://forum.xda-developers.com/showthread.php?t=1034261&highlight=recovery+mount+open
http://forum.xda-developers.com/showthread.php?t=1029474&highlight=recovery+mount+open
http://forum.xda-developers.com/showthread.php?t=991206&highlight=recovery+mount+open
http://forum.cyanogenmod.com/topic/...overy++mount++open__fromsearch__1#entry172534
If you're currently experiencing this issue, I'd like to get some information about your device to look for any trends or similarities:
1) Do you have a G2 or a DZ?
2) Which ROM was last running on your device?
3) Do you have the ENG HBOOT installed?
4) Aside from using ROM Manager to flash the recovery image, did you use ROM Manager for anything else (e.g. flashing ROMS)?
To me it seems people are running into this issue alot, and its happing around when the new recovery fix charge came out as well cm7 final came this could be a factor
ilostchild said:
To me it seems people are running into this issue alot, and its happing around when the new recovery fix charge came out as well cm7 final came this could be a factor
Click to expand...
Click to collapse
Which version of cwm are you referring to?
The newest recovery that fixes the off charge issue
maybe related:
http://forum.xda-developers.com/showthread.php?t=1044042
ilostchild said:
To me it seems people are running into this issue alot, and its happing around when the new recovery fix charge came out as well cm7 final came this could be a factor
Click to expand...
Click to collapse
Doubt it. Highly.
1)G2
2)CM 7 RC4
3)No eng hboot
4) I may have used rom manager to download roms a couple times as well as flashing roms
DON_58 said:
1)G2
2)CM 7 RC4
3)No eng hboot
4) I may have used rom manager to download roms a couple times as well as flashing roms
Click to expand...
Click to collapse
which cwm?
Im running 3.0.0.5
We have been looking into this issue on IRC for the past week or so. ANYONE WHO IS HAVING THIS ISSUE NEEDS TO STOP BY THE IRC CHANNEL.
We need to get some more info, right now we only have 2 cases to go on.
irc.freenode.net
#G2ROOT
The internal partitions of the emmc on the incredible are actually visible when connecting to your computer, so a lot of really smart folks formatted these partitions in an attempt to "fix" something that wasn't broken.
this resulted in recovery being unable to mount the partition.
i remember a long time ago helping someone troubleshoot through the process, it involved loading recovery, and using parted to partition and format the different blocks. (this thread here: http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/ i'm -Stevo-, although the problem was slightly different the same thing stands, no ability to mount cache.
Now, it's kind of annoying, i've found EVERY person i've ever dealt with that had this issue either disappears a half hour after you begin helping them, or are not advanced enough to use ADB (IT's gonna be required in this case if the above still stands)
There's a couple courses of action that can be taken here, you can manually try and format the partition using parted, or it could be as easy as opening adb shell and
mke2fs -t -ext3 /dev/block/mmcblk0p27
mount /dev/block/mmcblk0p27 /cache
i dunno, no one ever sticks around enough to try anything.
i couldnt even get someone to give me the output of
ls /dev/block
okay so i decided to live dangerously and recreate this error on my device. I made sure the cache partition was nice and corrupted and got greeted with this wonderful message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now this not the same situation that ALL people are in, but in this situation i opened adb shell and typed
mke2fs /dev/block/mmcblk0p27
reboot recovery
everything back to normal.
Now this is ONLY if your cache partition alone is corrupted, not if the actual paritions are just gone. in that case you'd want to check /dev/block and see the partitions listed, if they are all there as they should be (mmcblk0p25 mmcblk0p26 and mmcblk0p27) you can try and do the same.
hope this helps anyone.
Some things to remember though:
/cache/recovery/command is usually only invoked if your device is not properly rooted (check the numerous droid, evo, desire threads on this, they all had to restore an official RUU and root again to fix)
if there's nothing to mount in /dev/block have a feeling this is related to the emmc not initializing, in which case...
amazinglarry311 said:
okay so i decided to live dangerously and recreate this error on my device. I made sure the cache partition was nice and corrupted and got greeted with this wonderful message:
Now this not the same situation that ALL people are in, but in this situation i opened adb shell and typed
mke2fs /dev/block/mmcblk0p27
reboot recovery
everything back to normal.
Now this is ONLY if your cache partition alone is corrupted, not if the actual paritions are just gone. in that case you'd want to check /dev/block and see the partitions listed, if they are all there as they should be (mmcblk0p25 mmcblk0p26 and mmcblk0p27) you can try and do the same.
hope this helps anyone.
Some things to remember though:
/cache/recovery/command is usually only invoked if your device is not properly rooted (check the numerous droid, evo, desire threads on this, they all had to restore an official RUU and root again to fix)
I have a feeling this is related to the emmc not initializing, in which case...
Click to expand...
Click to collapse
You should make your own thread. I think this will help many people. Great job bro.
Sent from my HTC Desire Z/G2 using XDA Premium App
Hi !
We have to be carefull not to mix two issues here that might look similar to the user.
In both cases the recovery will give an error that it can't mount recovery.
One is that some partitions are corrupted and this can be fixed by recreating the partition as described by amazinglarry above or by reflshing the stock rom.
The second issue is that the emmc chip fails to initialize and in this case nothing can read or write the emmc. You can check if you have this case by booting into recovery and using adb to get a shell. In the shell do a "cat /proc/kmsg | grep mmc0" (i will reformat this tomorrow).
If you see messages that indicate that the emmc did not initialize, then you are in this boat.
There is currently no cure for this, but we try to find what causes this.
have fun - Guhl
Sent from my HTC Vision using XDA App
I'm glad that this issue is being worked on -- no one should have their phone suddenly brick.
Anyways, check out these IRC logs for more context: http://irclog.netripper.com/G2ROOT/2011/4/26/ (start from the middle)
The MyTouch 4G is also having the same problem, I'll be around here looking for solutions as well as maintaining a thread on the myTouch general side.
This happened to a friend's phone. I tired everything to get it fixed (I made a thread but I don't have the link) and ended up returning it to gat another one. What I'm curious about is how do you enter the partition commands? Is recovery (it was cwm 3.0.0.5 btw) able to provide adb access? If so, I was never able to get that and yes, I know how to use adb and have the drivers.
Sent from my HTC Vision using XDA App
I had the same problem. I started a few threads about it as well and posted everything I did (search my username so I dont fill up the thread) and I never got it fixed. Ended up just getting a new phone instead because it seemed like no one really knew much about the error and how to fix it.
SAAADD!
mke2fs /dev/block/mmcblk0p27
reboot recovery
I have this problem (for the second time actually...I was able to fix it the first time by flashing a 2.x.x.x CWM in EBL and formating the cache in that but no such luck the second time I got this error)
Anyhow I tried the above command for all (25/26/27) and it did not fix my issue...I also tried
cat /proc/kmsg | grep mmc0
to test if I have that fail to intialize issue. But it says that isn't a valid command in adb.
Any help? Also I read flashing PMG15.IMG in EBL fixes this but when I tried that I get the Failed PU error!! I think Im screwed huh?
Had same issue. one difference is that I flashed the rom on top of it and my phone bricked completely.
No hboot,no adb , nothingg
Sent from my HTC Desire Z using Tapatalk
I am beyond ecstatic, after 3 months of research, trial and error, I fixed my tablet!!
I am pleased to announce a fix to the dreaded QDLOAD 9008 brick! I've written this tutorial on the one tablet experimented on (LG-V410 aka Gpad 7.0 LTE US ATT), but I'm pretty certain others may find this helpful to other qualcomm msm based devices.
Background: I maintain that I can fix anything I break so I did the worst thing and corrupted the data on my LG GPAD LTE 7.0 (V410). As a result the tablet wouldn't go into any mode, no lights, even when charging, no screen image or light, nothing. When I plugged it into my computer, it wasn't even recognized, windows told me the device was having a problem. After a little experimentation I got it recognized (held power while connected to power cycle) by the computer as "QD BULK". Further research I found some drivers for Qualcomm devices and got the computer to recognize it as "QDLOADER 9008". I thought this was great news but from there got no where. I tried qpst, qfuse, hyperterminal, LG B2C, LG SUPPORT TOOL, EFS Professional, miflash, blankflash, etc... everything I tried got me nowhere. After 3 months, It is now fully operational and apparently CARRIER UNLOCKED, talk about a pot of gold at the end of a rainbow!!
WORD OF WARNING: This is not a simple matter, 9008 most likely means your Grand Partition Table is corrupted, and the poor thing doesn't have a clue how to function. My method is NOT GUARANTEED in any way, I will not be responsible if you turn your paper weight of a device into permanent paper weight or half functioning paper weight etc...PROCEED WITH CAUTION, this is not for the feint of heart nor a simple fix!! You've been warned!
PreRequisites:
-Windows (for expanding the KDZ) (there may be a linux alternative to LGFirmwareExtract)
-Linux and some basic experience with dd and navigating the terminal (I used ubuntu) --(again, nearly everything I'm about to explain can probaly be translated to another os.)
-KDZ for your device. http://forum.xda-developers.com/g-pad-10/general/kdz-lg-g-pad-7-0-v410-t3224867
-Replacement aboot and boot (see attached)
-KDZ Extractor ---http://forum.xda-developers.com/showthread.php?t=2600575
-TWRP http://forum.xda-developers.com/g-pad-10/development/recovery-twrp2-8-5-0lgv400-410-t3049568
-Fasboot and ADB http://forum.xda-developers.com/showthread.php?t=2588979
-A modified rom like Cyanogen mod etc... http://download.cyanogenmod.org/?device=v410
-16GB microsd card + a way of directly writing to it (i.e. usb card reader etc..) a second one is helpful but not required.
-Most important, Patience, beer, more patience, and more beer...
To teach a man to fish, some pertinent understanding: First thing to understand is how your main board works. Personally I disassembled my device and cross referenced every chip to do this, Good news is you don't have to. When power goes to the device, the SoC (system on a chip) looks to built in storage media for booting instructions (think low level here) and that in turn fires up everything else and then loads your kernel etc... You may be aware, there are two different types of computer systems out there, the old method used a BIOS, and the current uses UEFI. Older machines, when power was given to the system, the BIOS was responsible for firing up peripherals and finding the bootloader etc... UEFI (Unified Extended Firmware Instruction) however, relies on firmware on storage media to do all that.
For example, an x86 PC with a bios, when power is given to the board, the bios runs the show, testing equipment and waking up devices, then when it's ready, it looks to external media for a little magic byte at the end of the first sector of that media to indicate that it is bootable and in turn will boot (let those instructions take over). This style of booting media is called MBR or Master Boot Record.
Modern machines and most mobile devices use GPT or global partition table. There are quite a few advantages to GPT one primary being the possibility of many many more primary partitions, (MBR was very limited). The GPAD 7 LTE has 34 partitions to put things in perspective. When your device is stuck in 9008 mode, it is because it doesn't have a clue how to boot, most likely your GPT is corrupted. Fortunately, at least with the Gpad 7.0 this information does not have to be on the onboard internal memory chip. For this fix we will be constructing an sdcard to have all this info to get into a mode capable of writing to the emmc.
Without Further Ado, Here are the steps:
]PLUG THE TABLET INTO A CHARGER while you do the following (you may think it's been off and fully charged, but in reality it's probably been trying to boot over and over again while looking lifeless)
1.) Get the KDZ for your device (stock firmware)
2.) Extract the DZ using LGFirmwareExtractor
3.) Extract all the .bin files from the DZ using LGFirmwareExtractor
3b.) V410 US LTE ONLY - Replace aboot and boot with the files I attatched --I was fortunate enough to back them up before I hosed my tablet and they proved invaluable as the ones in the KDZ I linked to were causing strange graphic issues.
4.) open a terminal in linux and dd the sdcard with the file you extracted called "PrimaryGPT...."
I.E. "sudo dd if=/PATHTODZFILES/PrimaryGPT_0.bin of=/dev/sdx" (BE CERTAIN of the of= path, you can find yourself with more problems if you get that wrong) (run "sudo fdisk -l | less" first to verify what your sdcard's path is.)
This is where it gets tedious...:
5.) Do some hand stretches and start charting all 34 partitions on paper. Your sdcard is now partitioned with GPT and you need to know the name of each partition and its path. I.e. ("Partition name: LAF Located at /dev/sdXx")
6.) now for the fun part: dd every .bin to the corresponding partition EXCEPT: laf.bin and any of the system_xxxxx.bin files. (laf disables fastboot and the next step will bring you to a useless LG firmware download mode)( I.e. sudo dd if=/PATHTODZFILES/laf_xxx.bin of=/dev/sdXx) If some fail out, don't fret too much, I'm currently uncertain which ones are required and don't feel like corrupting my tablet again to figure that out. If the next step doesn't work you may need to revisit this step and ensure everything was accurate. It's easy to write down the wrong location for a partition and throw everything off
7.)Unmount your sdcard and put it in the tablet
8.) Press and hold power and volume up...If all went well, there is suddenly life to your paperweight!! Congratulate yourself and prepare for more fun... If nothing happened, revisit the above steps, more than likely something got flashed to the wrong partition.
9.)Now that you have fastboot, plug your tablet into the computer and use the following command: "fastboot boot TWRP.img" (or whatever the name or path is for your downloaded TWRP image.
10.) You should now be in TWRP and now your device is ADB ready, we are close to the home stretch...
11.) Now we need to load up an sdcard with all those dz files (except for laf and system images) and the custom rom like cyanogen mod. (if you only have the one sdcard you can unmount it and remove it while the table is in TWRP...crazy right?, if you opt for this, reformat the sdcard to ext or fat or whatever you please so the tablet can see all the bin files) Then put the sdcard into the tablet. You may need to remount the card in twrp before proceeding...
12.) Now from your computer type the following command "adb shell".
13.) now just like you did with the sd card dd PrimaryGPT_0.bin to the internal memory card, with the following command: dd if=/sdcard/PrimaryGPT_0.bin of=/dev/block/mmcblk0
14.) Grab the paper you wrote all the partitions down on and start doing the same thing you did to the sdcard to your tablet. You'll adjust the following command accordingly: "dd if=/sdcard/PARTITIONNAME.bin of=/dev/block/mmcblkpX (X being the partition number)
(again skip all system bin's and laf_xxxx.bin. Flashing laf disables fastboot on LG devices.)
15.) now time to install your custom rom, go through the prompts, clear your cache, and delvik cache and choose power off.
If all went well, you now have a tablet again, that's unlocked too!!!!! If not, don't lose faith, revisit the steps and ensure you didn't mistype or overlook something, this is so tedious it's easy to do. For instance, if you mistype your of=xxx it will create the file instead and give no error.
Post with your success stories, questions or difficulties and I'll try to help.
Yours Truly,
TheKiln
UPDATE/WARNING: Do not at any time under any circumstances dd directly from your host computer to the internal memory on your tablet, only do this via the asb shell. This may render a mode that I have not yet found a fix to, I will be working on it soon but from initial observation may be more complicated then the above instructions. With any invasive hacks like this tutorial there is always the possibility of making matters worse, so exercise caution and patience.
Quick Update/Revision : I am actively experimenting with this device and wanted to share that if your sbl1 and sbl1b partition is corrupt I have confirmed it will also cause 9008 mode. Therefore, it may be best to determine if the table is corrupt (try "parted /dev/block/mmcblk print"), and if not instead of wiping rewriting mmcblk0 try restoring sbl1 and sbl1b first. The V410 boots in the following order from what I can tell slb1->aboot->boot->system. So far I haven't found a downside to my prior instructions but to be less invasive just in case it might be wise to try this amendment.
I know my grand partition is corrupt, because after doing fastboot erase, basically everything, it came up as /dev/sdb. In a panic, I had deleted all the partitions, so now obviously my emmc storage is one big formated 16gb HD that cannot be seen in windows or linux no longer.
I just tried your method, found this post by doing a google search for:
sudo dd if=PrimaryGPT_0.bin
Had been doing just this, including the laf and many other ways. Am still getting the same thing though when putting the sdcard in the tablet, shows a 0% battery.
with the sdcard in the tablet I do get:
Bus 003 Device 063: ID 05c6:f006 Qualcomm, Inc.
Then after a few minutes, leaving it plugged into the USB I get:
Bus 003 Device 058: ID 1004:61a1 LG Electronics, Inc.
Also, with the sdcard in I do get KDZ_FW_UPD_EN to start updating but then get a perimeter error.
bethnesbitt said:
I know my grand partition is corrupt, because after doing fastboot erase, basically everything, it came up as /dev/sdb. In a panic, I had deleted all the partitions, so now obviously my emmc storage is one big formated 16gb HD that cannot be seen in windows or linux no longer.
I just tried your method, found this post by doing a google search for:
sudo dd if=PrimaryGPT_0.bin
Had been doing just this, including the laf and many other ways. Am still getting the same thing though when putting the sdcard in the tablet, shows a 0% battery.
with the sdcard in the tablet I do get:
Bus 003 Device 063: ID 05c6:f006 Qualcomm, Inc.
Then after a few minutes, leaving it plugged into the USB I get:
Bus 003 Device 058: ID 1004:61a1 LG Electronics, Inc.
Also, with the sdcard in I do get KDZ_FW_UPD_EN to start updating but then get a perimeter error.
Click to expand...
Click to collapse
Ive seen the exact mode you are referring to. Three possibilities:
1.) unplugged, hold down the power button for 30 seconds (or less if fastboot comes up)
2.) your sd card does not have all the necessary partitions to boot (which i just confirmed are specifically rpm, rpmb, tz, tzb, sbl1, sbl1b, PrimaryGpt(has to be done first), aboot and abootb)
3) They didn't dd quite right. from my active testing Ive found if you script the dd'ing it doesn't quite flash right, unless you add a delay after each step.
Its actually a very good sign you are seeing the 0% battery logo, sounds like you are almost there. Let me know what happens. Ill be happy to help guide you. Ive dedicated my v410 as a dev board so Im constantly running tests and reverse engineering it.
The 0% only shows up with the sdcard in, after I remove it, nothing. Tried wall charging it all night, that did nothing.
My theory is that if there was some way to mount the raw emmc and dd the primarygpt.bin to the raw emmc hd then the rest would be not problem.
I deleted the original EMMC partitions in gparted under linux after doing an erase fastboot -w laf, system, etc... something like that. After that the tablet did not show up again in gparted as soon as I unplugged it.
Right now I'm zero dd'ing my 16gb sd card, dang dd'ing seems to glue the partitions to the sdcard, If I try to fdisk the sdcard or delete the partitions using gparted, as soon as I dd the primarygpt.bin the old files reappear. Need to start fresh with 0s to the card.
In windows I can actually install specific lg drivers while in qualcomm hs_usb 9008 mode. The interesting thing with the sdcard in I can install the LG Android Net USB serial driver, which will not work while in 9008 mode.
bethnesbitt said:
The 0% only shows up with the sdcard in, after I remove it, nothing. Tried wall charging it all night, that did nothing.
My theory is that if there was some way to mount the raw emmc and dd the primarygpt.bin to the raw emmc hd then the rest would be not problem.
I deleted the original EMMC partitions in gparted under linux after doing an erase fastboot -w laf, system, etc... something like that. After that the tablet did not show up again in gparted as soon as I unplugged it.
Right now I'm zero dd'ing my 16gb sd card, dang dd'ing seems to glue the partitions to the sdcard, If I try to fdisk the sdcard or delete the partitions using gparted, as soon as I dd the primarygpt.bin the old files reappear. Need to start fresh with 0s to the card.
In windows I can actually install specific lg drivers while in qualcomm hs_usb 9008 mode. The interesting thing with the sdcard in I can install the LG Android Net USB serial driver, which will not work while in 9008 mode.
Click to expand...
Click to collapse
The 0% comes up when your sdcard is inserted because you are close to getting it done. You're going to have your computer running all night on the zero'ing but I can assure you that will be in vein. The whole point of this tutorial is so you can get into a mode in which you can flash the emmc. I can tell you are a little lost in the steps so pm me and I'll help you out. Also a word to the wise, you can try all you want with windows and the 9008 drivers, but seriously there is nothing out there specific to the v410 thats going to help you "engage" the 9008 mode. Not being stubborn I've just literally tried it all. If it's any credit I am clinically OCD. I can't sleep till I figure things out.
Finally, I see a hope is shining here!
I bricked my LG VK810, when I was trying to flash twrp, I refered to v500 pad instead and I flashed wrong img files (aboot, boot, sb1, sb2, sb3, tz & twrp.img) "only those 6 files" so I only need to replace those with the correct files, which I downloaded now.
I do not have Ubuntu, however I have CentOS, which i have not used for couple of years, so I forgot how to use it. also do I still need to use the LG Firmware Extractor?
please help
thekiln said:
This is where it gets tedious...:
5.) Do some hand stretches and start charting all 34 partitions on paper. Your sdcard is now partitioned with GPT and you need to know the name of each partition and its path. I.e. ("Partition name: LAF Located at /dev/sdXx")
6.) now for the fun part: dd every .bin to the corresponding partition EXCEPT: laf.bin and any of the system_xxxxx.bin files. (laf disables fastboot and the next step will bring you to a useless LG firmware download mode)( I.e. sudo dd if=/PATHTODZFILES/laf_xxx.bin of=/dev/sdXx) If some fail out, don't fret too much, I'm currently uncertain which ones are required and don't feel like corrupting my tablet again to figure that out. If the next step doesn't work you may need to revisit this step and ensure everything was accurate. It's easy to write down the wrong location for a partition and throw everything off
Click to expand...
Click to collapse
Please please please help, how to do those steps!
nmnm4alll said:
Please please please help, how to do those steps!
Click to expand...
Click to collapse
I am not certain exactly which partitions have to be flashed, the attached note I made was from what I can tell so far. I was simply noting that it may be best to try one partition at a time vs doing them all at once, it is at your own descretion. So as far as listing the partitions, I'm not familuar with the centos distro but in Ubuntu it is something to the effect of fdisk /dev/sdb -l or gdisk /dev/sda then p. I hope that answers your question, If not please be more specific to your exact question.
thekiln said:
I am not certain exactly which partitions have to be flashed, the attached note I made was from what I can tell so far. I was simply noting that it may be best to try one partition at a time vs doing them all at once, it is at your own descretion. So as far as listing the partitions, I'm not familuar with the centos distro but in Ubuntu it is something to the effect of fdisk /dev/sdb -l or gdisk /dev/sda then p. I hope that answers your question, If not please be more specific to your exact question.
Click to expand...
Click to collapse
Thank you very much for your response, I am sorry I have never flashed partitions before, sbut I noticed gparted is not on CentOS, so I downloaded Puppy precise Linux as I was able to find gparted and I tried using it as shown in this video, https://www.youtube.com/watch?v=6z1Tu9l8WNc
But I am confused now about how big and what are the formats for the 34 partitions which need to be created?
nmnm4alll said:
Thank you very much for your response, I am sorry I have never flashed partitions before, sbut I noticed gparted is not on CentOS, so I downloaded Puppy precise Linux as I was able to find gparted and I tried using it as shown in this video, https://www.youtube.com/watch?v=6z1Tu9l8WNc
But I am confused now about how big and what are the formats for the 34 partitions which need to be created?
Click to expand...
Click to collapse
Flashing PrimaryGPT_0.bin will automatically create the partitions. Flashing the individual partitions will give each partition the data needed. There should be no need to manually create partitions, if no partitions show up in gparted, the problem goes back to primarygpt, as that is the partition table.
I am not quite sure what you mean by:
thekiln said:
5.) Do some hand stretches and start charting all 34 partitions on paper. Your sdcard is now partitioned with GPT and you need to know the name of each partition and its path. I.e. ("Partition name: LAF Located at /dev/sdXx")
Click to expand...
Click to collapse
how to can I get the Partition names?
Edit: I finally was able to get Ubuntu installed on my computer, so please instruct accordingly, sorry I have been googling everything you have mentioned in your OP with no luck!
Thanks in advance.
nmnm4alll said:
I am not quite sure what you mean by:
how to can I get the Partition names?
Edit: I finally was able to get Ubuntu installed on my computer, so please instruct accordingly, sorry I have been googling everything you have mentioned in your OP with no luck!
Thanks in advance.
Click to expand...
Click to collapse
For the names I like to use "parted /dev/sdb" then "print" (sdb being the location of the sd card, might be sdc, sdd, etc..)
thekiln said:
For the names I like to use "parted /dev/sdb" then "print" (sdb being the location of the sd card, might be sdc, sdd, etc..)
Click to expand...
Click to collapse
Thanks for the command line, I came up with this 36 partitions
https://www.dropbox.com/s/bw8nj317y3v7pw6/VirtualBox_Ubunto_05_01_2016_08_59_03.png?dl=0
now how do I know each partition's path?
you have mentioned "I.e. ("Partition name: LAF Located at /dev/sdXx")"
so do I type for example: "modem: LAF located at /dev/sdb1" (sdb1 is my sdcard's path)?
thekiln said:
6.) now for the fun part: dd every .bin to the corresponding partition EXCEPT: laf.bin and any of the system_xxxxx.bin files. (laf disables fastboot and the next step will bring you to a useless LG firmware download mode)( I.e. sudo dd if=/PATHTODZFILES/laf_xxx.bin of=/dev/sdXx) If some fail out, don't fret too much, I'm currently uncertain which ones are required and don't feel like corrupting my tablet again to figure that out. If the next step doesn't work you may need to revisit this step and ensure everything was accurate. It's easy to write down the wrong location for a partition and throw everything off
Click to expand...
Click to collapse
Those are the files got extracted from the DZ file
https://www.dropbox.com/s/z3ebiy4vvnsy9oo/Untitled.png?dl=0
and this is a screenshot in Ubuntu after copying the file on a 64 memory stick and mounting it
https://www.dropbox.com/s/gqn35n1npklq8ld/VirtualBox_Ubunto_05_01_2016_09_30_15.png?dl=0
Do I just type: "sudo dd if=/media/mike/MEMORY/aboot_153600.bin of=/dev/sdb1" and so on for all .bin files?
Please try to write command lines as I do not have experience with Linux
I'll be honest and blunt, if you do not have experience with linux, a simple keystroke mistake could wipe your entire computer. I can't in good conscience recommend touching dd if you're not familiar with it. Not trying to be condescending or anything just really dangerous tools we are working with here.
it have problem
wow !!! i can see the LG logo in my tablet !!!
but i can't run next step !!!
pushed power + volume up button but i never changed screen !!
This is written on the screen.
"boot certification verify"
please help me i copy 34 partition on SDcard after that what can i do? please answer , this does not work (( 8.) Press and hold power and volume up...If all went well, there is suddenly life to your paperweight!! Congratulate yourself and prepare for more fun... If nothing happened, revisit the above steps, more than likely something got flashed to the wrong partition.
Issue
Hello, I've successfully followed the tutorial until step 9. When i flash TWRP it reboots and comes back to the fastboot screen.
If I hold the vol+ button when it is booting, the download mode screen flashes for a second and then it comes back to the fastboot.
I haven't been able to to anything else and would be very grateful if someone could help me with this.
Apparently there is no bootloader so it is stuck
I attached a picture of my screen
LG G Pad 7.0 V400
Is there a way to unlock Qualcomm 9008 from LG V400?
Finally my dead tablet went into fastboot mode.
Except windows cannot find a fastboot driver and fastboot command can't locate the device either. Any suggestions?
Hi All
i have a me176cx asus tablet and i rooted my tablet. After root process my tablet is worked for a while i mean 3-4 months and halted,
i saw the asus logo and gray-or-black screen.
For this problem i downloaded UL-K013-WW-12.10.1.36-user.zip file from asus site and i installed. But i get an error like "This package is for K013 devices..... bla bla" and i googled and i deleted 2 rows from updater-script
getprop("ro.product.device") == "K013" || abort("This package is for "K013" devices; this is a "" + getprop("ro.product.device") + "".");
and new rom installed without any problem. But result was same, Asus logo and gray-or-black screen.
Anyway, i downloaded the older version UL-K013-WW-12.10.1.36_KK-user.zip and i installed
now i just see this message.
AFU: test IFWI BIOS update.
FV File Size is 0x00300260
I cant open recovery menu, I mean
VOLUME+ and Power => NotWorking
VOLUME- and POWER => Not Working
Just Volume(+) plus Volume(-) plus POWER is working, i mean fastboot menu.
Can i install my tablet from this menu? Or what can i do for my tablet? What is your advice guys?
Sorry for my english.
Thanks.
I assume you were already on Lollipop before you started installing all these packages? Installing the _KK package was definitely a bad idea because it's only supposed to be used for upgrading from KitKat to Lollipop.
Luckily (at least as far as I know) the screen you are able to enter with Power + Volume Up + Volume Down ("DNX mode") can be used to recover most software problems. I haven't done this before, so hopefully someone else can share the necessary steps to restore your tablet.
it's not related with this thread
it's not related with this thread but i just want to share this picture
My son is open this menu, how? i dont know
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
lambdadroid said:
I assume you were already on Lollipop before you started installing all these packages? Installing the _KK package was definitely a bad idea because it's only supposed to be used for upgrading from KitKat to Lollipop.
Luckily (at least as far as I know) the screen you are able to enter with Power + Volume Up + Volume Down ("DNX mode") can be used to recover most software problems. I haven't done this before, so hopefully someone else can share the necessary steps to restore your tablet.
Click to expand...
Click to collapse
Hi
thanks for your replay, i tried somethink with fastboot but i didnt success.
I hope somebody can help me.
Thanks again.
pojeck said:
it's not related with this thread but i just want to share this picture
My son is open this menu, how? i dont know
Click to expand...
Click to collapse
Well, this menu will open if there is no bootloader on your tablet. The tablet has a UEFI implementation similar to regular PCs, and it's even possible to navigate and change options in this menu with a powered USB OTG adapter and an USB keyboard. Nevertheless, this wouldn't help in this case.
Just did a search in the forums and found a potential solution. You need fastboot installed on your PC (Google for instructions depending on your OS).
Extract esp.zip and droidboot.img from UL-K013-WW-12.10.1.36-user.zip
Extract efilinux.zip from esp.zip (in EFI/Intel/efilinux.zip)
Start DNX mode on your tablet (Power + Volume Up + Volume Down), you should see 3 "Fastboot starting" messages
Connect the tablet to your PC
Run these commands:
Code:
fastboot flash osloader efilinux.efi
fastboot boot droidboot.img
If it works you're in Droidboot again and can flash the original UL-K013-WW-12.10.1.36-user.zip from there.
Source: https://forum.xda-developers.com/showpost.php?p=64213291&postcount=163
lambdadroid said:
Well, this menu will open if there is no bootloader on your tablet. The tablet has a UEFI implementation similar to regular PCs, and it's even possible to navigate and change options in this menu with a powered USB OTG adapter and an USB keyboard. Nevertheless, this wouldn't help in this case.
Just did a search in the forums and found a potential solution. You need fastboot installed on your PC (Google for instructions depending on your OS).
Extract esp.zip and droidboot.img from UL-K013-WW-12.10.1.36-user.zip
Extract efilinux.zip from esp.zip (in EFI/Intel/efilinux.zip)
Start DNX mode on your tablet (Power + Volume Up + Volume Down), you should see 3 "Fastboot starting" messages
Connect the tablet to your PC
Run these commands:
Code:
fastboot flash osloader efilinux.efi
fastboot boot droidboot.img
If it works you're in Droidboot again and can flash the original UL-K013-WW-12.10.1.36-user.zip from there.
Source: https://forum.xda-developers.com/showpost.php?p=64213291&postcount=163
Click to expand...
Click to collapse
hi again
as you told me i did and recovery menu is working now.
C:\Temp>cd asus
C:\Temp\asus>
C:\Temp\asus>fastboot flash osloader efilinux.efi
sending 'osloader' (2009 KB)
fname=efilinux.efi...
2009 KB / 2009 KB
OKAY [ 0.085s]
writing 'osloader'...
OKAY [ 0.006s]
finished. total time: 0.094s
C:\Temp\asus>fastboot boot droidboot.img
downloading 'boot.img'...
OKAY [ 0.430s]
booting...
OKAY [ 0.001s]
finished. total time: 0.434s
C:\Temp\asus>
Click to expand...
Click to collapse
now what is the best way flash the original file UL-K013-WW-12.10.1.36-user.zip to the tablet?
because i tried with ASUS Flash Tool and it didnt success.
Thanks again.
pojeck said:
hi again
as you told me i did and recovery menu is working now.
now what is the best way flash the original file UL-K013-WW-12.10.1.36-user.zip to the tablet?
because i tried with ASUS Flash Tool and it didnt success.
Thanks again.
Click to expand...
Click to collapse
You can use the temporary TWRP recovery session from https://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096 (select twrp_hdpi_portrait.zip and use trigger T4). First make sure you have UL-K013-WW-12.10.1.36-user.zip on the external SD card so you can install it from there.
lambdadroid said:
You can use the temporary TWRP recovery session from https://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096 (select twrp_hdpi_portrait.zip and use trigger T4). First make sure you have UL-K013-WW-12.10.1.36-user.zip on the external SD card so you can install it from there.
Click to expand...
Click to collapse
Thanks for your replay
i did it and i copied zip file to sd card.
I get same error, this package is for "K013" devices; This is a "K013_1" (you can find in attachment)
and i delete 2 rows in UL-K013-WW-12.10.1.36-user-orjinal.zip\META-INF\com\google\android\updater-script
getprop("ro.product.device") == "K013" || abort("This package is for "K013" devices; this is a "" + getprop("ro.product.device") + "".");
show_progress(0.750000, 0);
1- i get message INSTALL from SD card complete
2- i have lot of text on screen and rebooted.
3- I just have gray/black screen.
I turn around
Hi All
i have a me176cx asus tablet and i rooted my tablet. After root process my tablet is worked for a while i mean 3-4 months and halted,
i saw the asus logo and gray-or-black screen.
Click to expand...
Click to collapse
Any idea?
pojeck said:
Thanks for your replay
i did it and i copied zip file to sd card.
I get same error, this package is for "K013" devices; This is a "K013_1" (you can find in attachment)
and i delete 2 rows in UL-K013-WW-12.10.1.36-user-orjinal.zip\META-INF\com\google\android\updater-script
getprop("ro.product.device") == "K013" || abort("This package is for "K013" devices; this is a "" + getprop("ro.product.device") + "".");
show_progress(0.750000, 0);
1- i get message INSTALL from SD card complete
2- i have lot of text on screen and rebooted.
3- I just have gray/black screen.
I turn around
Any idea?
Click to expand...
Click to collapse
Alright, but are you able to get it the Droidboot (with the Normal Boot, Recovery mode etc options) screen again now with Volume Down + Power? That means you've at least fixed your bootloader.
I'm not sure why your device isn't booting anymore. Have you tried a factory reset (you can also do that from TWRP).
Hi
Alright, but are you able to get it the Droidboot (with the Normal Boot, Recovery mode etc options) screen again now with Volume Down + Power? That means you've at least fixed your bootloader.
Click to expand...
Click to collapse
Yes, droidboot is working without any problem. But serial number is strange i think... You can find in attachment
Also recoverymenu is working. I'm getting error screen, after volumeup + Power i have no problem.
I selected
wipe data/factory reset
wipe cache partition
Result is same. After asus logo i have blank screen. This is my real problem.
Thank you so much.
pojeck said:
Hi
Yes, droidboot is working without any problem. But serial number is strange i think... You can find in attachment
Also recoverymenu is working. I'm getting error screen, after volumeup + Power i have no problem.
I selected
wipe data/factory reset
wipe cache partition
Result is same. After asus logo i have blank screen. This is my real problem.
Thank you so much.
Click to expand...
Click to collapse
The serial number on Fastboot is normal, it never displays the right one.
I don't know why your device doesn't boot anymore (and it's hard to figure out). My only other suggestion is that you give my Nougat ROM a try (see https://forum.xda-developers.com/me...-unofficial-lineageos-14-1-asus-memo-t3633341). It's very different from the original ASUS system so there is a certain chance that it'll work. Note that battery life is a lot worse on it though.
You can unlock your bootloader from Droidboot (since you can't boot normally currently). Download https://www.androidfilehost.com/?fid=312978532265362065, and take the ESP.img from there, then download https://github.com/me176c-dev/devic...recovery-3.1.1-20170810-UNOFFICIAL-me176c.img
Boot into Droidboot and run the following commands:
Code:
fastboot flash ESP ESP.img
fastboot flash recovery twrp-recovery-3.1.1-20170810-UNOFFICIAL-me176c.img
Power off your device, then press Volume Down + Power. Intel logo should show up, and ask if you want to go into recovery or fastboot. Go into recovery using Volume Down. Do a Factory reset again (it's under Wipe), then flash https://github.com/me176c-dev/devic...ge-14.1-20170815-UNOFFICIAL-me176c-signed.zip (e.g. put it on your external SD). Test if it boots successfully.
lambdadroid said:
The serial number on Fastboot is normal, it never displays the right one.
I don't know why your device doesn't boot anymore (and it's hard to figure out). My only other suggestion is that you give my Nougat ROM a try (see https://forum.xda-developers.com/me...-unofficial-lineageos-14-1-asus-memo-t3633341). It's very different from the original ASUS system so there is a certain chance that it'll work. Note that battery life is a lot worse on it though.
You can unlock your bootloader from Droidboot (since you can't boot normally currently). Download https://www.androidfilehost.com/?fid=312978532265362065, and take the ESP.img from there, then download https://github.com/me176c-dev/devic...recovery-3.1.1-20170810-UNOFFICIAL-me176c.img
Boot into Droidboot and run the following commands:
Code:
fastboot flash ESP ESP.img
fastboot flash recovery twrp-recovery-3.1.1-20170810-UNOFFICIAL-me176c.img
Power off your device, then press Volume Down + Power. Intel logo should show up, and ask if you want to go into recovery or fastboot. Go into recovery using Volume Down. Do a Factory reset again (it's under Wipe), then flash https://github.com/me176c-dev/devic...ge-14.1-20170815-UNOFFICIAL-me176c-signed.zip (e.g. put it on your external SD). Test if it boots successfully.
Click to expand...
Click to collapse
Hi Again
I did all steps. But i get an error, failed to mount "oemcfg" invalid argument (you can find in attachment)
Last 10 minutes i'm waiting in BlueLine
Is this normal?
EDIT : I'm still waiting here last 1 hour.
Am i need the shutdown?
Thanks for all
pojeck said:
Hi Again
I did all steps. But i get an error, failed to mount "oemcfg" invalid argument (you can find in attachment)
Last 10 minutes i'm waiting in BlueLine
Is this normal?
EDIT : I'm still waiting here last 1 hour.
Am i need the shutdown?
Thanks for all
Click to expand...
Click to collapse
Yes, I hope you've already turned it off. The first boot normally doesn't take longer than ~30 seconds. You will drain your battery if you keep it running for so long You can turn it off by pressing the power button for at least ~10 seconds.
The /oemcfg error could be a possible pointer what's wrong with your device. Try the following: Boot into TWRP again. First check if you have enough battery left. If not, you can try to charge it in TWRP. When you're done go to Advanced -> Terminal and first check if your serial number is okay:
Code:
getprop ro.serialno
... should display something like E5OKCY... (or maybe different, dunno what ASUS uses for each device).
Next we need to try to find out what's wrong with /oemcfg. Go to Mount and click "Config" a few times. I assume nothing happens (it doesn't get ticked). Go back to the Terminal and type:
Code:
dmesg > /external_sd/dmesg.txt
And upload dmesg.txt from your external SD here so I can check what's wrong.
Note: If you are experienced with ADB you can also use it to run commands instead of the builtin Terminal, but I guess the builtin Terminal might be easier to use.
lambdadroid said:
Yes, I hope you've already turned it off. The first boot normally doesn't take longer than ~30 seconds. You will drain your battery if you keep it running for so long You can turn it off by pressing the power button for at least ~10 seconds.
The /oemcfg error could be a possible pointer what's wrong with your device. Try the following: Boot into TWRP again. First check if you have enough battery left. If not, you can try to charge it in TWRP. When you're done go to Advanced -> Terminal and first check if your serial number is okay:
Code:
getprop ro.serialno
... should display something like E5OKCY... (or maybe different, dunno what ASUS uses for each device).
Next we need to try to find out what's wrong with /oemcfg. Go to Mount and click "Config" a few times. I assume nothing happens (it doesn't get ticked). Go back to the Terminal and type:
Code:
dmesg > /external_sd/dmesg.txt
And upload dmesg.txt from your external SD here so I can check what's wrong.
Note: If you are experienced with ADB you can also use it to run commands instead of the builtin Terminal, but I guess the builtin Terminal might be easier to use.
Click to expand...
Click to collapse
Hi
firstly Thank you very very very much for your interest
I did all, you can find thepictures and log file in attachment.
as you said me i click the config and nothing happened.
I found lots of "Can't find ext4 filesystem" error message. I think it's related with my problem
pojeck said:
Hi
firstly Thank you very very very much for your interest
I did all, you can find thepictures and log file in attachment.
as you said me i click the config and nothing happened.
I found lots of "Can't find ext4 filesystem" error message. I think it's related with my problem
Click to expand...
Click to collapse
Alright, indeed. The good news is that your serial number is fine and everything else in the log looks fine too. The bad news is that your /oemcfg partition was somehow destroyed, and it holds important data such as WiFi and Bluetooth mac addresses. The second good news is that most of the information is also stored in /factory additionally.
To save some time, it would be easiest if you send me a copy of your oemcfg and factory partition, then I'll try to restore the oemcfg partition based on the factory partition.
To get a copy of oemcfg and factory, type the following in the TWRP Terminal:
Code:
dd if=/dev/block/by-name/config of=/external_sd/oemcfg.img
dd if=/dev/block/by-name/factory of=/external_sd/factory.img
And upload oemcfg.img and factory.img (you may need to put them in a .zip first if XDA doesn't accept the upload).
lambdadroid said:
Alright, indeed. The good news is that your serial number is fine and everything else in the log looks fine too. The bad news is that your /oemcfg partition was somehow destroyed, and it holds important data such as WiFi and Bluetooth mac addresses. The second good news is that most of the information is also stored in /factory additionally.
To save some time, it would be easiest if you send me a copy of your oemcfg and factory partition, then I'll try to restore the oemcfg partition based on the factory partition.
To get a copy of oemcfg and factory, type the following in the TWRP Terminal:
Code:
dd if=/dev/block/by-name/config of=/external_sd/oemcfg.img
dd if=/dev/block/by-name/factory of=/external_sd/factory.img
And upload oemcfg.img and factory.img (you may need to put them in a .zip first if XDA doesn't accept the upload).
Click to expand...
Click to collapse
I get a copy of oemcfg and factory img files and zipped.
But size is 333KB
is this normal?
You can find the zipped file in attachment.
If you want to get original files i can send another link.
Thanks
pojeck said:
I get a copy of oemcfg and factory img files and zipped.
But size is 333KB
is this normal?
You can find the zipped file in attachment.
If you want to get original files i can send another link.
Thanks
Click to expand...
Click to collapse
The size is fine (just compression, and it works well for this because there is not much data in the partition), but there is something else wrong with the files. I think you've send the same partition (the broken one) twice.
In your screen shot you have dd if=/dev/block/by-name/config twice, but for the second command you need dd if=/dev/block/by-name/factory. Please run the second command from my post above again, and then post the ZIP again
lambdadroid said:
The size is fine (just compression, and it works well for this because there is not much data in the partition), but there is something else wrong with the files. I think you've send the same partition (the broken one) twice.
In your screen shot you have dd if=/dev/block/by-name/config twice, but for the second command you need dd if=/dev/block/by-name/factory. Please run the second command from my post above again, and then post the ZIP again
Click to expand...
Click to collapse
I'm so sorry about that
you can find the correct files in attachment
Thanks...
pojeck said:
I'm so sorry about that
you can find the correct files in attachment
Thanks...
Click to expand...
Click to collapse
Alright, the new files look fine. I need a while to fix the configs, and I'll be away for an hour or so I'll send you a potentially fixed partition in a few hours.
You may want to edit your two previous posts and remove the attachments because the partition can potentially contain sensible data (the serial number of the device, mac addresses etc) that may be abused. I've downloaded them so you can safely remove them now.
lambdadroid said:
Alright, the new files look fine. I need a while to fix the configs, and I'll be away for an hour or so I'll send you a potentially fixed partition in a few hours.
You may want to edit your two previous posts and remove the attachments because the partition can potentially contain sensible data (the serial number of the device, mac addresses etc) that may be abused. I've downloaded them so you can safely remove them now.
Click to expand...
Click to collapse
Hi
Thank you very much for your kindly notice
I deleted last img files and some pictures.
I'll wait for fixed files, Thanks again.
How to unbrick by sdcard from 9008 without QFIL
This method works ONLY for qualcomm devices (ANY non-UFS!!) which are already in QDL/EDL/9008 mode!
This method does *not* work for:
Samsung devices in general.
Details:
Samsung is doing things completely different while ofc a qcom based Samsung works with the same principal as "normal" devices. Just the process of building an hnbrick sdcard is different as you can get the pit (partition list) by heimdall but not a flashable gpt. Instead search for "sboot sdcard unbrick" or "sboot sdcard <your model>" . The important part here is "sboot" as that one will be loaded by the iROM when flashed properly (+other stuff).
UFS devices (so not for the G5 or later).
Details:
9008 bricks are not fixable on UFS NAND devices by booting from an SD card. The boot path is stored in QFPROM (on the CPU) and it is something like /dev/block/sdb or /dev/block/sde. On eMMC devices, the boot path is /dev/block/mmcblk0. If you have a 9008 brick, the SD card is seen as /dev/block/mmcblk0 so the phone will boot from it on an eMMC device since that IS the boot path. There is no way to make the SD card appear as /dev/block/sdX. And there is no way to change the boot path once you have a 9008 brick without a firehose. If you have a signed firehose, then you can fix your phone without needing an SD card As for cross flashing. I checked the RSA signature for the H930, H932, H933, and US998 and they are all different. If you flash any of the signed firmware (xbl, abl, hyp, modem, etc) from one of those devices, then you have a 9008 brick and no way to fix it yourself.I didn't bother checking the Verizon or Sprint models since they are even more locked down than the H932 is, but it appears from reading this thread that they have the same key as the US998 (I am not going to waste my time checking).-- Brian
Click to expand...
Click to collapse
If your device is connected and not detected like that the external sdcard method will NOT work for you.
On the LG G4 you can force the sdcard mode by following post #2 . I guess every device has a way to force that mode so google is your friend.
Hint --> If you have no sdcard and own a H815 device (only then) you can make use of these validated QFIL process here
Requirements
1) Ok first of all what you need is Linux. I highly recommend FWUL ( https://bit.do/FWULatXDA ) but any Linux is sufficient if you can handle it.
2) LG models only: you need the latest SALT version ( https://bit.do/SALTatXDA ) which is already included since FWUL v2.5 (one of the reasons why I recommend FWUL).
If you decide to use FWUL and start SALT it should prompt you when an updated SALT version is available. To be sure: just click the Update button in SALT once started.
3) you need an external sdcard which is (to be sure) bigger then your internal storage (the sdcard must have the same size of your internal storage! so in theory a 32GB card should work fine but some cards are sold as 32GB but the real size is less , i.e. 29 GB). Thats the most critical part here as the GPT will be invalid if it does not fit with the sdcard. you can't edit the GPT though as then internal checksum may fail and so it will not work to boot from the sdcard. so ensure you have a bigger sized sdcard to workaround any issues related to this.
4) Another important requirement for that external sdcard is: speed! If you want to ensure that you do not struggle ensure it is at least a class 10 card with UHS. It MIGHT work without UHS and it MIGHT work even on slower cards down to class 4 but when the storage is too slow the device rejects to boot from it as it ran into timeouts and so marking the sdcard as "not good enough" to boot from it.
Of course you can first try a lower speed sdcard but if you encounter issues here then it is likely related to the speed of the sdcard.
5) you need a 100% matching firmware (e.g a KDZ on LG's) for your device model - and very important: with a matching ARB of your current installed firmware!
If your current installed firmware has a higher ARB then the one you flash on the sdcard it will NOT work!
Find out what ARB means here https://bit.do/antirollg4
Steps
1. Boot FWUL (or ur personal Linux)
2. LG models only: Start SALT - ensure that it is v3.5 or higher
3. Extract the firmware file (e.g KDZ) but usually not all partitions are needed - just the bootloader stack
(depends on your device - the following is for any LG G4 model):
Primary GPT
sbl1
aboot
pmic
rpm
tz
laf
sdi
hyp
If you have not all or any of these (first check the note about UFS above) then you must identify your bootloader stack first.
A good start for this is here: https://lineageos.org/engineering/Qualcomm-Firmware but you may have to just try and error here.
For a quick & dirty try: flash every partition which is smaller then 150 MB (i.e. leave out system, cache, userdata and such).
4. Clean dmesg by opening a terminal and type:
Code:
sudo dmesg -c >> /dev/null
5. Connect your external sdcard to FWUL
6. Type this in the terminal:
Code:
dmesg
and find the connect messages there pointing to the device name. usually you see something like "mmcblk0" but sometimes it's different named like sdc or sdd or similar.
We do not need the pXX here. So if you see mmcblk0p1 we need only mmcblk0. If you see a sdc1 or sdd1 we just need sdc or sdd without the number.
7. The device name is needed now! Ensure it has the correct size by typing this in the terminal:
Code:
sudo fdisk -l /dev/mmcblk0
(replace mmcblk0 if you your device is named different in step 6).
This is important because the next step will erase your sdcard completely!
All your data get lost!
So if you choose the wrong one you may overwrite your PC storage in worst case! So double check this before proceeding.
You can do so by disconnecting the sdcard and if the command in this step gives a message about the device cannot be found - connect device again and re-do the above command. if it shows then again your device all is fine
8. Now flash the GPT (partition table) to your device in a terminal:
Change into the folder where you extracted the backup. If you leaved the default on SALT it's /tmp/extracteddz:
Code:
cd /tmp/extracteddz
sudo -s
dd if=PrimaryGPT.gpt of=/dev/mmcblk0 (replace mmcblk0 if you your device is named different in step 6)
sync
hint: do not close the terminal
9. Disconnect the sdcard and connect it again
10. Now flash the rest in a terminal:
First check if the GPT has been flashed fine:
Code:
ls -la /dev/disk/by-partlabel/
if you get nothing as a result or an error message something went wrong. Go back to step 4!
Move to the folder where you extracted the backup. If you leaved the default on SALT it's /tmp/extracteddz:
Code:
cd /tmp/extracteddz
LG G4 - ONLY - Flashing instructions for locked or official unlocked phone (If you UsU'd your device skip this!)
Code:
dd if=sbl1.bin of=/dev/disk/by-partlabel/sbl1
dd if=aboot.bin of=/dev/disk/by-partlabel/aboot
dd if=hyp.bin of=/dev/disk/by-partlabel/hyp
dd if=pmic.bin of=/dev/disk/by-partlabel/pmic
dd if=rpm.bin of=/dev/disk/by-partlabel/rpm
dd if=tz.bin of=/dev/disk/by-partlabel/tz
dd if=laf.bin of=/dev/disk/by-partlabel/laf
dd if=sdi.bin of=/dev/disk/by-partlabel/sdi
[B][COLOR="Red"][SIZE="4"]sync[/SIZE][/COLOR][/B]
Do [B][U]not forget[/U][/B] that last ("sync") command!! Otherwise it will very likely not work!
LG G4 - ONLY - Flashing instructions for an UsU'd device
Besides the KDZ extract you also need to grab the UsU unlock zip of your device model first then do this:
Code:
dd if=sbl1.bin of=/dev/disk/by-partlabel/sbl1
dd if=hyp.bin of=/dev/disk/by-partlabel/hyp
dd if=pmic.bin of=/dev/disk/by-partlabel/pmic
dd if=rpm.bin of=/dev/disk/by-partlabel/rpm
dd if=tz.bin of=/dev/disk/by-partlabel/tz
dd if=sdi.bin of=/dev/disk/by-partlabel/sdi
dd if=laf_UsU.img of=/dev/disk/by-partlabel/laf
dd if=aboot_UsU.img of=/dev/disk/by-partlabel/aboot
dd if=rawres_UsU.img of=/dev/disk/by-partlabel/raw_resources
[B][COLOR="Red"][SIZE="4"]sync[/SIZE][/COLOR][/B]
Do [B][U]not forget[/U][/B] that last ("sync") command!! Otherwise it will very likely not work!
11. Now everything is prepared. Take out your sdcard. Take out the battery and disconnect cable. Plugin the external sdcard. Put battery back.
Start the device in fastboot mode and use fastboot flash partition imagename.img
If there is no fastboot possible open the download mode.
For example on the LG G4:
Press volume up (only this) and keep it pressed.
Then connect USB cable while still keep the pressure on volume up for 20 seconds.
The download mode should come up.
Congrats you can now use e.g. LGup (or for Samsung, ODIN etc) for unbricking by flashing a regular firmware on it (beware of the ARB again).
Have fun! :highfive:
Support / TG group
Of course in this thread but also by Telegram. I have created a generic group for all stuff around Android : here.
Note:
be polite, don't ask to ask, be patient(!), respect the timezones, help others.
,-
Force SDCARD boot
How-To force booting from sdcard (LG G4 only) (e.g. when the device is NOT in 9008 / QDL mode)
You may know the 2-pin-bridge method which can enforce the 9008/QDL mode (on the back of the main board which is shown when disassembling the back cover).
Now you may think: you can enforce that mode by bridging these pins and then you could boot from sdcard as this guide here says 9008 mode is a requirement.
The answer is: NO. This will NOT work!
But there seems to be a way (which I personally never have tested!) to force that sdcard boot by doing the following.
Be aware: You do this on your own risk! Do not cry if something is failing/destroyed/whatever. Its totally up to you to proceed or not but its on your own risk like always when following guides.
prepare the sdcard as described in the above guide
insert the sdcard in the device
remove battery of the device
unplug usb cable
disassemble the back cover by loosen all screws
disassembling the mainboard like described here: fixit guide
on the FRONT of the mainboard find 5 (DAT0) and 6 (GND) as shown in the picture:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bridge these both and while bridging plugin the usb cable - WITHOUT TOUCHING anything with your fingers/body/soul on the mainboard!!!!
Keep thumbs pressed.. it may work if you flashed the correct files, with a matching ARB, in a correct way and [fill-on-on-whoever-u-believe-in] is with you
marzsalim said:
5. Connect sdcard with mobile ? Or sdcard just connect to pc? Please reply to me
Click to expand...
Click to collapse
Like I wrote to FWUL so yes to your PC where FWUL is running
Sent from my LG-H815 using XDA Labs
it seems either ubuntu 17.10 messes something up or salt 3.6-6 stable can't find partitions and i've downloaded two different h812 kdz.
commandervadeo said:
it seems either ubuntu 17.10 messes something up or salt 3.6-6 stable can't find partitions and i've downloaded two different h812 kdz.
Click to expand...
Click to collapse
This is happening to me too?
commandervadeo said:
it seems either ubuntu 17.10 messes something up or salt 3.6-6 stable can't find partitions and i've downloaded two different h812 kdz.
Click to expand...
Click to collapse
Shepxda said:
This is happening to me too?
Click to expand...
Click to collapse
upload the log after extracting a KDZ:
advanced menu -> Logfile -> upload button -> share the link
steadfasterX said:
upload the log after extracting a KDZ:
advanced menu -> Logfile -> upload button -> share the link
Click to expand...
Click to collapse
No, you see, when you select the KDZ and the location to extract to, no partitions are available to choose from. It's just a blank page
Shepxda said:
No, you see, when you select the KDZ and the location to extract to, no partitions are available to choose from. It's just a blank page
Click to expand...
Click to collapse
Yes. After this do what I said above. Give me the log.
Sent from my LG-H815 using XDA Labs
Hi, I have an H811 bricked this way, as it is bricked, I cannot check antirollback on phone's android.
On the rear label (the one with serial number near to battery) I can see model (H811) and it says H/W 1.0, S/W V10d
I search and saw that there is not V10d kdz for H811, is that data useful? Which kdz will be the best choice to use?
birry said:
Hi, I have an H811 bricked this way, as it is bricked, I cannot check antirollback on phone's android.
On the rear label (the one with serial number near to battery) I can see model (H811) and it says H/W 1.0, S/W V10d
I search and saw that there is not V10d kdz for H811, is that data useful? Which kdz will be the best choice to use?
Click to expand...
Click to collapse
do you remember at least if you had installed Android marshmallow or lollipop? Any chance that you have made a TWRP backup in the past? Or did you never unlocked your device?
Sent from my LG-H815 using XDA Labs
steadfasterX said:
do you remember at least if you had installed Android marshmallow or lollipop? Any chance that you have made a TWRP backup in the past? Or did you never unlocked your device?
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Never upgraded Android, I guess it was lollipop. No backups or unlock also, it just bootlooped and I bricked it trying to install a H812 image with lgup (I know which image I tried if it is useful, I remember editing a value because lgup was refusing to install h812 image on the h811, I didn't find h811 image for lgup bootloop flashing fix).
This was my reference when I destroyed the phone [emoji14]
https://www.reddit.com/r/lgg4/comments/45gfg2/dae_g4_series_msm_big_core_disable_tool_guide/
birry said:
Never upgraded Android, I guess it was lollipop. No backups or unlock also, it just bootlooped and I bricked it trying to install a H812 image with lgup (I know which image I tried if it is useful, I remember editing a value because lgup was refusing to install h812 image on the h811, I didn't find h811 image for lgup bootloop flashing fix).
This was my reference when I destroyed the phone [emoji14]
https://www.reddit.com/r/lgg4/comments/45gfg2/dae_g4_series_msm_big_core_disable_tool_guide/
Click to expand...
Click to collapse
well..omg..
ok so the h812 has no ARB. The h811 has. Here is the reason for your hard brick. Do not cross flash random files without knowing what you do really.
Start with 10h which is ARB 1 for the h811: http://downloads.codefi.re/autoprime/LG/LG_G4/H811/H81110H
download the single files or the KDZ and use SALT to extract. then follow the rest of the guide above.
if that fails to boot go on with ARB 2 : http://downloads.codefi.re/autoprime/LG/LG_G4/H811/H81110N
I would not recommend to go further then that as u otherwise will increase your ARB for sure.
The next step if that all above still fails would be to use QFIL with proper files for the h811 but beware: there are QFIL files marked as h811/h815/... which in fact are converting your device to a ls991. Best is to search XDA for other users reports which files gave them a good result.
Last but not least if your device is ARB 3 or higher all the above will fail (including the QFIL method) and your only chance to bring back life is the sdcard method described here but using ARB 3 or higher files.
.
I hate to say it but Im here....
LGG4 - 815eur - new frankenphone (new to me, chinese refurb) - received jan
never had a sim in it. only kept it on to see how long the battery would last in idle mode (airplane mode on, no wifi active)(14 days!) - LGUP to MM
still stock - no google play services installed yet, I was waiting for the UsU (woohoo steadfasterX!!, where do I send my bounty contribution?)
I was downloading all the required files for FWUL / Virtual Box last night, I was going to spend the afternoon getting to know the process/Arch linux, before attempting to mess with my phone... I was adjusting the pull down notification settings and it froze.
I waited till this AM, hoping maybe it would sort itself out. NOPE. Battery at 0.
Im at the logo bootloop with pulsing blue LED.
I have read the entire thread, I wanted to make sure that this workaround is the proper "fix" for this type of bootloop.
I was at v20k IIRC and I know for a fact my ARB was 0.
Im not sure where to dl the required files from several sources Ive tried, dont leave me feeling confident its a trusted source.
Any thoughts on what may have happened?
cheers
ac
steadfasterX said:
well..omg..
ok so the h812 has no ARB. The h811 has. Here is the reason for your hard brick. Do not cross flash random files without knowing what you do really.
Start with 10h which is ARB 1 for the h811: http://downloads.codefi.re/autoprime/LG/LG_G4/H811/H81110H
download the single files or the KDZ and use SALT to extract. then follow the rest of the guide above.
if that fails to boot go on with ARB 2 : http://downloads.codefi.re/autoprime/LG/LG_G4/H811/H81110N
I would not recommend to go further then that as u otherwise will increase your ARB for sure.
The next step if that all above still fails would be to use QFIL with proper files for the h811 but beware: there are QFIL files marked as h811/h815/... which in fact are converting your device to a ls991. Best is to search XDA for other users reports which files gave them a good result.
Last but not least if your device is ARB 3 or higher all the above will fail (including the QFIL method) and your only chance to bring back life is the sdcard method described here but using ARB 3 or higher files.
.
Click to expand...
Click to collapse
Cool!! It worked like a charm with H81110H file :laugh::laugh::laugh:
Now I can run it into download mode and I could see that info on SALT:
Device model: LG-H811
Firmware (laf): H81120v
Firmware (system): LGH811AT-01-V20v-310-260-APR-25-2017-ARB03+0
Carrier: TMO
Country: US
UsU: no
GPT compatibility: H811
LAF protocol: 1000001
AntiRollBack: 3
I don't want to make a mistake so now that it boots in download mode I will wait for options, which is the best choice now? Updating it with a .tot with LGUP (for the bootloop) or installing other rom (perhaps one with bootloop workaround)
Thanks for your great work!
Vishnuisgod said:
I hate to say it but Im here....
LGG4 - 815eur - new frankenphone (new to me, chinese refurb) - received jan
never had a sim in it. only kept it on to see how long the battery would last in idle mode (airplane mode on, no wifi active)(14 days!) - LGUP to MM
still stock - no google play services installed yet, I was waiting for the UsU (woohoo steadfasterX!!, where do I send my bounty contribution?)
I was downloading all the required files for FWUL / Virtual Box last night, I was going to spend the afternoon getting to know the process/Arch linux, before attempting to mess with my phone... I was adjusting the pull down notification settings and it froze.
I waited till this AM, hoping maybe it would sort itself out. NOPE. Battery at 0.
Im at the logo bootloop with pulsing blue LED.
I have read the entire thread, I wanted to make sure that this workaround is the proper "fix" for this type of bootloop.
I was at v20k IIRC and I know for a fact my ARB was 0.
Im not sure where to dl the required files from several sources Ive tried, dont leave me feeling confident its a trusted source.
Any thoughts on what may have happened?
cheers
ac
Click to expand...
Click to collapse
This unbrick will work only when you bricked your phone. It's not an ilapo fix and your description sounds like one. Your best chance is using a modded boot image with just 4 cores enabled. That requires an unlocked phone though.. There is a guide from me to create such boot images here on XDA.
birry said:
Cool!! It worked like a charm with H81110H file :laugh::laugh::laugh:
Now I can run it into download mode and I could see that info on SALT:
Device model: LG-H811
Firmware (laf): H81120v
Firmware (system): LGH811AT-01-V20v-310-260-APR-25-2017-ARB03+0
Carrier: TMO
Country: US
UsU: no
GPT compatibility: H811
LAF protocol: 1000001
AntiRollBack: 3
I don't want to make a mistake so now that it boots in download mode I will wait for options, which is the best choice now? Updating it with a .tot with LGUP (for the bootloop) or installing other rom (perhaps one with bootloop workaround)
Thanks for your great work!
Click to expand...
Click to collapse
You're referring to what TOT? The one containing just the aboot?
Sent from my LG-H815 using XDA Labs
steadfasterX said:
This unbrick will work only when you bricked your phone. It's not an ilapo fix and your description sounds like one. Your best chance is using a modded boot image with just 4 cores enabled. That requires an unlocked phone though.. There is a guide from me to create such boot images here on XDA.
You're referring to what TOT? The one containing just the aboot?
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Yes, anything that patches the bootloop. I am a bit confused with partition structure, the cpu workaround is done editing something in the aboot partition?
I just would like to patch the bootloop (I prefer to have the four tiny cores enabled instead of just one as it normally does and installing stock Rom).
birry said:
Yes, anything that patches the bootloop. I am a bit confused with partition structure, the cpu workaround is done editing something in the aboot partition?
I just would like to patch the bootloop (I prefer to have the four tiny cores enable instead of just one as it normally does and installing stock Rom
Click to expand...
Click to collapse
There are 2 patches available. The one with tot and the boot image one.
The TOT one which is something between 4 and 10 MB contains just the aboot one and disables the cores in the aboot itself.
The boot image one is made in the kernel cmdline
Both have the same effect.
The difference : the TOT aboot fixes it permanently (as long as you don't reflash a kdz/tot again). So you can flash custom ROMs without needing to care about it.
The boot image adjustment instead does not touch your aboot but needs to be done on ever new boot image you want to use.
Sent from my LG-H815 using XDA Labs
So then I have the patch that just contains the aboot partition (files are of exactly 4mb)
Downloaded from here: https://www.reddit.com/r/lgg4/...m_big_core_disable_tool_guide/
The problem is that there are several models in the file that I downloaded from there but H811 is missing, I cannot find a tot with just aboot for H811, is this really available? I would prefer to write a tot with just aboot that leaves all cores enabled and the faulty ones disabled, not just one core enabled as those tots does.
birry said:
So then I have the patch that just contains the aboot partition (files are of exactly 4mb)
Downloaded from here: https://www.reddit.com/r/lgg4/...m_big_core_disable_tool_guide/
The problem is that there are several models in the file that I downloaded from there but H811 is missing, I cannot find a tot with just aboot for H811, is this really available? I would prefer to write a tot with just aboot that leaves all cores enabled and the faulty ones disabled, not just one core enabled as those tots does.
Click to expand...
Click to collapse
Afaik there is none for the h811 and I highly recommend to not use any of the others to avoid bricking your phone again. So it seems you're stuck with modifying boot images
Sent from my LG-H815 using XDA Labs
Ok then, I will try this firmwares: https://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
Consider that ARB is 3, which firmware would be the correct one to use?
Edit: now after a pair of boots it started to get download mode in a random way, sometimes it does and sometimes it does not, could it be because I used a ARB 1 extrated kdz?
Hello people of XDA,
as I promised here, here's a tutorial for getting Android Oreo 8.1 up and running to your device.
NOTE: I DID NOT MAKE THIS TUTORIAL! This is a translated guide from 4PDA by nik-kst. I've also rehosted some of the files on Google Drive so you won't have to register on 4PDA(hopefully).
Code:
[B]Your warranty is now void. [/B]
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Now that the disclaimer is dealt with, let's get on with this tutorial shall we?
First things first, we need to grab a bunch of things:
SP Flash Tool;
MediaTek VCOM Drivers;
The Stock Kernel(it will make sense to you soon!);
Scatter file for repartitioning, drop it inside the stock kernel folder(credit to fca.sjc);
ADB and Fastboot of your choice;
New recovery;
Oreo's Backup, drop it inside a MicroSD card or drop it once you have re-partitioned the device successfully;
Once you have everything setup and extracted, you're ready to go!
First, we gotta go ahead and install VCOM drivers - we won't be able to do anything to our phone without them.
If you're running Windows 8/10, make sure to disable Driver Signature Verification.
Go to Device Manager, click Action at the top and click Add legacy hardware. A new wizard window will appear.
Choose Install the hardware that I manually select from a list(Advanced);
In the next window, choose Show all devices and click Next, then click Have disk...
Then you will be prompted to direct to the driver install info, so click Browse...
Now go to the folder of drivers and select the Setup Information file that's fitting for your computer, x86 for 32-bit and x64 for 64-bit.
You should now find 5 new devices in the list, add them one by one by repeating steps 2 to 6 until you have all of them installed.
Windows might complain about unsigned drivers, just allow their installation and proceed.
If your ports list looks similar to the picture below, then you're set for the next step!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Next, we'll want to back up the NVRAM partition, because AFAIK, it keeps important unique data about your device such as WiFi, IMEI etc. data.
Note: You may want to take out your MicroSD card and SIM cards prior to this just in case. Also, might be the possible fix if readback for NVRAM fails(needs confirmation).
First, open up Flashtool.exe as admin and go to Readback tab;
Click on Add, a new item in the list will appear. You want to double-click on it, so that a Save File window would appear.
Save that file anywhere you want, name it whatever you like, for convenience I've named mine ROM_NVRAM.
Now, you'll want to find the address in the memory for NVRAM partition. To do this, open up the stock firmware(credit to fca.sjc) scatter file in a text editor(like Notepad++), and find line partition_name: nvram
In that paragraph, find two values: linear_start_addr and partition_size they should be 0x380000 and 0x500000 respectively.
Punch in those values into the Readback block start address window, so it should look something like this:
Now, click Read Back, it should gray out along with Add and Remove.
Now, turn off your device, pull out the battery for about 30 seconds, reinsert it and DO NOT TURN IT ON YET! With the Volume Down "-" button pressed, plug in your device into the USB port.
The NVRAM partition should've been read and you'll get a giant green tick sign when it's done.
Now that that's done, we can start repartitioning our device.
Make sure your SP FlashTool is running as admin, otherwise restart it as admin.
Open up the Download tab and in the line Scatter-loading File click Choose and navigate to the 8.1 scatter file, it should be named MT6580_Android_scatter_8.1.txt.
From the dropdown list, select Format All + Download.
Again, take out the battery for 30 seconds and put it back in WITHOUT turning it back on.
Now click Download, and with the Volume down "-" button held down, plug the device into your PC. There should be a bunch of colored progress bars at the bottom of the window.
Once it's done, you should get the giant tick pop-up, after which you can disconnect the device, and start it normally.
NOTE: it takes a while for the first launch, so give it some time!
Once it starts up into the first launch wizard, we can now restore the NVRAM.
In order to activate the memory writing function of SP FlashTool, re-start it with admin and press Ctrl + Alt + V, the window header should have (Advanced mode) now.
From the Window drop-down, select Write Memory, it should redirect you to a new tab named accordingly.
In the File Path field, browse to the ROM_NVRAM backup that you made earlier.
In the Begin Address (HEX) field, copy the linear_start_addr value off the scatter file.
The region should be left at EMMC_USER.
Now, click the Write memory button, turn off the device, re-insert the battery just like before, and connect the device with the Volume Down "-" button pressed.
It should begin the writing of the NVRAM and once it's done a giant tick pop-up will appear.
Now after that is done, boot into the OS, check that everything works, including IMEI and WiFi.
Also, during the setup wizard or later in the settings setup a screen lock with a pattern or a PIN or a password(credit to fca.sjc), because the partitions may remain encrypted and show 0mb(needs confirmation)
Now you'll want to unlock the bootloader and flash the TWRP recovery.
Now this is a standard recovery flash, but for a quick summary:
Enable Developer options;
Enable OEM unlocking;
Reboot into bootloader mode(I like to use ADB for adb reboot-bootloader);
Make sure your device is detected via fastboot devices, if not, google some drivers for ADB;
Unlock the bootloader via fastboot oem unlock, and press the Volume up button to confirm the bootloader unlocking.
Now, reboot the phone, it will take a while to reboot, DO NOT PANIC AND WAIT.
Now that we have bootloader unlocked, we can flash the TWRP:
Go into bootloader mode;
Confirm you are being detected again by fastboot devices;
Flash the recovery with fastboot flash recovery [twrp recovery name].img;
now, WITHOUT booting into system we boot into recovery and confirm it works.
Now that you've done all this, you propably want to run Oreo now, eh? Well, here's what we do now:
Note: make sure you have the Oreo's backup zip extracted at it's own folder inside your MicroSD card or inside the phone's internal storage by now(thanks @ZappaDong for letting me know)
From recovery, select Wipe > Advanced Wipe and select system and vendor, and wipe them. Logs may complain about not seeing vendor, ignore that message.
Then, we restore everything from the Oreo backup;
Finally, do a factory reset(aka wipe Data, Dalvik and cache);
And reboot!
Now, fingers crossed, you should be booting into a fully functional 8.1 Oreo! if you did, congratulations!
Please let me know if I've made any mistakes and/or this has worked for you.
All credits go to the awesome people at 4PDA, especially nik-kst(if you're reading this, you the real MVP!), below I've linked the sources I've written this guide from.
Nik-kst's guide to repartitioning the device for Oreo;
Nik-kst's post about the Stable Oreo ROM.
Reserved for possible FAQ in the future
@aurismat, Hey man it worked as expected ! However, I was a bit confused on the repartitioning part when selecting ''Format all+download'' option then clicking ''start'' will only give an error stating that the IMG file of ''vendor'' is missing. (I am using SP FLASH v5.1744)
But nevertheless, I tried the ''Download only'' option and lucky it worked as well. I just wanted to clarify should it be Format all +download or Download only? Or is there a missing corresponding IMG file for vendor ?
Hey @JustAnormalGuy,
It should've been Format All + Download.
Also I'm glad that my post has helped at least one person.
Thanks for pointing out this omitted detail though, I'll edit the post ASAP.
Thanks for the translation!
--- solved ---
I have tried it three times but never managed to back up the NVRAM partition.
Error: s_dl-get_fram_setting_fail (5054) see attached screenshot
-----------
I have used Win 10 on my Mac and it worked.
Now I am stuck at step "5. Unlock the bootloader via fastboot oem unlock, and press the Volume up button to confirm the bootloader unlocking."
this looks O.K. to me
----------------------------------
>fastboot oem unlock
...
(bootloader) Start unlock flow
OKAY [ 16.047s]
finished. total time: 16.047s
-----------------------------------
But now nothing happens after
-----------------------------------
> fastboot reboot
rebooting...
finished. total time: 0.000s
-----------------------------------
It's stuck in
[Fastboot Mode] <<==
=> FASTBOOT Moe ...
and nothing happens.
UPDATE
O.K. I have used the Power Button to switch it off and on again, there was a small Android for a few seconds and the phone rebooted the second time. Now I am waiting for it to finish booting.
UPDATE 2
TWRP is working now
And what TWRP.img should I use for
"3. Flash the recovery with fastboot flash recovery [twrp recovery name].img;"
in the next paragraph? Is this the "New recovery;" from the download section at the top?
Thank you!
Missing tips:
- Put both scatter files inside the stock kernel folder before starting.
-I used the stock scatter file for the NVRAM backup then the 8.1 scatter only for the Formal all+Download step.
- When you first run the stock ROM, set up a pin or a password, otherwise you will have failed to mount data in twrp and data will show as 0mb due to its encryption.
@aurismat does that WW file includes the new vendor release?
In the vendor, a bug was detected, the camera with the auto flash turned on, did not turn on (rather, it turned on and off immediately), the flash when shooting video.
Now everything works as it should: yes2:
Fixed vendor: 07/07/2018
https://yadi.sk/d/DUGRYLnc3YtADV
I did everything according with this tutorial. Sadly my mobile network is not connecting idk why. I get an error saying Simprocessor and it doesnt connect on mobile network. It detects the networks but wont connect. Im going back to stock until someone can help me fix it.
@ZappaDong:
Yes, you should use the one I provided the link at the list of downloads.
Also, a bit late and I may be wrong, but your DRAM reads may be hindered by a MicroSD card(confirmation needed). Try ejecting it before you read off the NVRAM.
@fca.sjc:
First of all, thanks for pointing out my missing tips.
I'm not really sure if it includes the fixed vendor. I didn't really have any issues with the camera's flash, so they already included it(?)(again, needs confirmation).
For failed connections, make sure you flashed the NVRAM correctly(hence why you should test the telephony after you've repartitioned to stock 5.0 with the NVRAM backup flashed).If you failed to do that, I was told you should be able to recover the NVRAM data with Maui(?) software(confirmation needed, once again).
Thanks to both of you for pointing out these tips, I'll update the guide and credit you when I'll have more time. Cheers!
[*]For failed connections, make sure you flashed the NVRAM correctly(hence why you should test the telephony after you've repartitioned to stock 5.0 with the NVRAM backup flashed).If you failed to do that, I was told you should be able to recover the NVRAM data with Maui(?) software(confirmation needed, once again).
[/LIST]
Click to expand...
Click to collapse
After repartition, wifi, 3g and mobile signal works fine. I just cant flash twrp after unlocking bootloader otherwise i get a bootloop (unable to mount data and storage). So after i installed twrp and wiped/restore vendor and system, i reflashed stock recovery to acess android and then, restarted again to recovery. At this point, i did the write memory step again, using old vendor and the new vendor. None seem to work. I even backed up NVRAM using TWRP at first to make sure i did it right and tried to restore from there and it doesnt seem to be an IMEI issue. Maybe it has something to do with the frequency. Im on Brazil right now and idk
It does recognize my Sim card, my number, it downloads the data operators and etc but it doesnt connect to the mobile signal idk why. The bug starts at the restore step so it has something to do with this part.
I just test stuff but im pretty experienced at flashing and reflashing, etc. I guess only a dev can help and i actually went back to 7.1 UHANS rom, wich i got from 4pda.ru. Before using this rom, I was having a bluetooth audio stream bug and Ive tested like 4-5 roms, one for each kernel that was there. Lets see if someone can help me with this, cause i want oreo for better bluetooth audio stream.
Thanks for your help so far. I really apreciate it. This device is very good and we dont see many mods here on xda for it.
aurismat said:
@ZappaDong:
Yes, you should use the one I provided the link at the list of downloads.
Also, a bit late and I may be wrong, but your DRAM reads may be hindered by a MicroSD card(confirmation needed). Try ejecting it before you read off the NVRAM.
Click to expand...
Click to collapse
Thanks again!
I am using Windows 10 (bootcamp on the iMac) now and I have read the description in the 'old' [ROOT/TWRP] thread but used the files you have provided.
TWRP is working now, but I got an error that the ZIP file on the SD card was corrupted. Maybe I have damaged it when copying it to the SD card under OS X.
I am just redownloading it with Windows 10 and give it another try. (Yandex is very slow now, about 60 KB/s)
------------------------------------------------------------------
UPDATE
I have downloaded "WW_Phone-user_810_O11019_1528478718_release.zip" again, put in on the SD card, booted into Recovery, wiped system and vendor and chose "Install" , selected the "WW_Phone-user_810_O11019_1528478718_release.zip" file.
But I still get an error message.
Installing zip file '/external_SD/WW ... release.zip'
Checking for digest file
Skipping Digest Check: no Digest file found
[IN RED]Invailid zip file format!
Error installing zip file '/ 'external_SD/WW ... release.zip' [/IN RED]
Updating partion details...
...done
I have just copied the zip file from the download folder to the SD card - have I missed anything?
ZappaDong said:
And what TWRP.img should I use for
"3. Flash the recovery with fastboot flash recovery [twrp recovery name].img;"
in the next paragraph? Is this the "New recovery;" from the download section at the top?
Thank you!
Click to expand...
Click to collapse
Yup that one
@ZappaDong, yeah I kind of forgot to mention again - you should've extracted the .zip in which the backup came in. It's a backup, not an installation zip.
It needs to be extracted into its own folder inside the MicroSD card, so that then it could be used by TWRP to recover the partitions.
Thanks for pointing this out to me though, gonna edit it ASAP.
@fca.sjc bro AFAIK that problem of yours could be because of one or more of the following:
1. Your IMEI is missing or null. I would suggest SN Write tool (since I already tried it). Is quite effective, it is comparable to Maui Meta although I haven't tried it yet. (Tutorial here ==> https://forum.hovatek.com/thread-12306.html )
It is better to use PC restore tools since it writes directly to the nvram unlike apks like Chamelephon which (according to what I know) writes only to nvdata.
2. You need to switch the sims. What i mean is just if you have 2 sims on your phone, switch sim 1 in with sim 2. I forgot the explanation on it but it helps.
3. You need to switch off data connection on the other sim. On the several roms I tried on 4pda including this 8.1 pixel based rom, upon first bootup, the data connection on both sims are already on, therefore 3G cannot work. So first turn both sim's connection off then check if network mode is set to 3G. If not do the Solution #2.
JustAnormalGuy said:
@fca.sjc bro AFAIK that problem of yours could be because of one or more of the following:
1. Your IMEI is missing or null. I would suggest SN Write tool (since I already tried it). Is quite effective, it is comparable to Maui Meta although I haven't tried it yet. (Tutorial here ==> https://forum.hovatek.com/thread-12306.html )
It is the best IMEI restore tool since it writes directly to the nvram. (Meaning it retains even after wipes to data, system etc. via twrp)
2. You need to switch the sims. What i mean is just if you have 2 sims on your phone, switch sim 1 with sim 2. I forgot the logic on how that helps but I've seen it as a solution as the phone rereads the sims.
3. You need to switch off data connection on the other sim. On the several roms I tried on 4pda including this 8.1 pixel based rom, upon first bootup, the data connection on both sims are already on, therefore 3G cannot work. So first turn both sim's connection off then check if network mode is set to 3G. If not do the Solution #2.
Click to expand...
Click to collapse
Thanks for your help bro. I did check the IMEI while i was on this oreo rom. It seem to be ok. Number was there but i did not check if it was the right number. I might check it when i try to flash again. Probably later today when i'm home.
The problem wasnt just data connection, it was the connection itself. I couldnt call or receive SMS to activate whatsapp, for example. Like i said previously, those features were ok after repartitioning (on stock repartitioned). After the restore step, i did check all network options, including data, network mode, network connections available,etc. I'll follow your tutorial to restore the IMEI if the numbers are different then. I'll remember to take some screenshots next time so you guys can help me figure out what the problem is. Thanks again
aurismat said:
@ZappaDongIt's a backup, not an installation zip.
Click to expand...
Click to collapse
Yes, that did the trick. The installation went through and everything seems to work now.
Thank you again for your patience.
I saw there in the forum 4pda that are doing roms project treble pro zenfone go, only that I can not understand the mode of installation, you know how?
Ricardo Flowers said:
I saw there in the forum 4pda that are doing roms project treble pro zenfone go, only that I can not understand the mode of installation, you know how?
Click to expand...
Click to collapse
Yeah, it is possible -
FIrstly you'd need a vendor image that has fixed RIL(telephony) - vendor off this thread's 8.1 has RIL broken in Treble ROMs.
Luckily you can get it off any 8.1 custom ROM off ska-vova in 4pda. Just download any of his .zips(i.e. his ResurrectionRemix ROM(which imo is just official ResRemix with their Russian preference for a browser, but fine)), flash them and then backup the /vendor off it(and /boot for good measure)
Buuuuut then you need a TWRP that supports system image flashing - not sure if the one I provided here has it, if it hasn't - I'll post it here.
Then all you need to do is flash the Treble image, restore the /vendor(and /boot if you need to) and hope for the best!
Sadly the Havoc OS 2.0, the only ARM A-Only Pie-based ROM available here didn't work for me - just straight bootloops.
Your mileage may vary - if you get the Havoc OS 2.0 instaled, I'd love to read about it.
aurismat said:
Yeah, it is possible -
FIrstly you'd need a vendor image that has fixed RIL(telephony) - vendor off this thread's 8.1 has RIL broken in Treble ROMs.
Luckily you can get it off any 8.1 custom ROM off ska-vova in 4pda. Just download any of his .zips(i.e. his ResurrectionRemix ROM(which imo is just official ResRemix with their Russian preference for a browser, but fine)), flash them and then backup the /vendor off it(and /boot for good measure)
Buuuuut then you need a TWRP that supports system image flashing - not sure if the one I provided here has it, if it hasn't - I'll post it here.
Then all you need to do is flash the Treble image, restore the /vendor(and /boot if you need to) and hope for the best!
Sadly the Havoc OS 2.0, the only ARM A-Only Pie-based ROM available here didn't work for me - just straight bootloops.
Your mileage may vary - if you get the Havoc OS 2.0 instaled, I'd love to read about it.
Click to expand...
Click to collapse
Can you do a tutorial? I did not quite understand how it installs. Sorry, google translate does not help.
Deleted