Develop Bugs

[HOWTO] Create a GoldCard - Bypassing the RUU/SPL CID check to Root/Downgrade

If you are stuck on a ROM you don't like (t-mobile/asian carrier etc.) you can use this howto to create a goldcard to bypass the CID checks so you can downgrade and root your Hero.
01. Download QMAT 5.06 here
It’s a demo version so will only run for 10 minutes.
02. Format your SD card to FAT32. Please keep in mind some brands of SD cards do not work.
03. Use adb to run this command: adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
04. Copy the SD card cid code displayed after the adb command.
05. Start Qmat and Click on Cyptoanalysis Tools > Crypto Toolbox.
06. Look at the bottom, there is a text box (beside the “Reverse String” button) enter the SD card cid code you got earlier.
Click on the “Reverse String” button, the result is reversed…
Example: 532600bd227d9c0347329407514d5402
07. Copy the reversed SD card cid code.
08. Go to QMAT goldcard site here to generate your goldcard (yes it says for G1 but works for our Hero too).
09. Enter your email. For the correct SD card cid code, you need to replace the first 2 characters to 00.
Example: From “532600bd227d9c0347329407514d5402” to “002600bd227d9c0347329407514d5402”
10. Click Continue and you will receive the goldcard.img in .zip format in your email.
11. Go to your email, download the zip file and save it to a directory and unzip it to goldcard.img
12. Download HxD Hex Editor from here
13. Install and launch HxD Hex Editor program. (make sure you use "Run as Administrator" under Vista and win 7)
14. Go to Extra tab > Open Disk. Under Physical disk, select Removable Disk (Must be your SD card), uncheck “Open as Readonly), click OK.
15. Go to Extra again, Open Disk Image, open up goldcard.img which you’ve saved/unzipped earlier.
Now, you should have two tabs, one is your removable disk, the other is goldcard.img. Press OK when prompted for “Sector Size” 512 (Hard disks/Floppy disks), click OK.
16. Click on goldcard.img tab. Go to Edit tab > Select All, edit tab again > copy.
17. Click on the “removable disk” tab. Select offset 00000000 till offset 00000170 (including the 00000170 line), click on Edit tab and then Paste Write.
18. Click on File > Save. now you can exit the program.
19. Reboot your phone with this SD Card (now GoldCard) inside
20. Use the Official HTC RUU to downgrade to 2.73.405.5 (which you can get here) from which you can fastboot boot and/or root your phone with flashrec.
Done.
Credits:
Original heads up by tangzq with link to this
That site used the XDA Sapphire goldcard howto here
And apparently myself and XDA as this builds on the HTC knowledge from the old days (here)
In any case, enjoy your new found freedom

Holy ****znit it works! Downgrading!!!!!

Hmm. I've followed the guide and successfully skipped the CID lock check of the device and flashed it to version 2.73.405.5 WWE. Problem is, I can't seem to get the device to boot into recovery mode after using flashrec (I did download and flash it just fine). the recovery mode (home + power) booted the device but it hangs at the boot screen where it says HERO. Any idea?
Edit: Ah. a little bit of the update. while the buttons do not work, i can use adb shell reboot recovery; however, after using flashrec, it still shows the old recovery screen ?
Edit2: confirmed, recovery flasher doesn't work now im using the SEA rom
I'll try the RUU_Hero_HTC_WWE_1.76.405.6_WWE_release_signed_NoD river.exe rom later

I had the same issue with Recovery Flasher I couldn't to boot into recovery. I was also unable to downgrade to the 1.7 roms due to a bootloader version error, arghhh. Anywho, managed to work my way round it, i'll explain below. I've got a T-Mobile G2 updated to the latest rom (so no root access).
I first followed the instructions on making a goldcard and then flashed the 2.73.405.5 WWE rom fine.
Now make sure you have the cm-hero-recovery.img (http://content.modaco.net/dropzone/modacopatchedrecovery-1.0.zip) on the root of your sdcard. Aswell as Instant Root (http://neilandtheresa.co.uk/Android/) now install Instant Root on the phone. It should pop up with a notification "instant root was sucessfully" or along those lines. (If you have a problem installing Instant Root make sure Settings>Applications>Unknown Sources is checked)
Instant root then allows for root access with adb shell using the following 2 commands:
1) adb shell
then
2) su
the icon should change from a $ to #.
Now flash the recovery image with the following command:
1) flash_image recovery /sdcard/cm-hero-recovery.img
This shouldn't take that long once completed it will go back the # prompt example below.
# flash_image recovery /sdcard/cm-hero-recovery.img (I typed this)
flash_image recovery /sdcard/cm-hero-recovery.img (this pops up)
# (this shows the flash completed)
Now pull out your usb cable and battery, turn on the phone with the battery in place while holding the home button and it should boot into the custom recovery .
Well, I hope this helps someone and I didn't just waste my time . Oh, thanks for posting the goldcard instructions.

it worked!!!
Thanks so much! I did the exact process before (see other thread) but I must have missed something. Following this process exactly is what did it. I am guessing something about the reboot and the RUU is where i went wrong before.
I can confirm this works on the 2.73.707.9 ROM

Yaaahaaaayyhaahhahahaahaayyyyyyyyyyyy!!! I feel so happy for all you guys who had this problem (although I myself did not!!)

I kind of half gave up at 6:00 am yesrterday and i just woke up (1
:27pm) and followed the instructions here and BAM! got a working nandroid backup and a custom rom \o/!!! thanks to all of you!

so it's tested and proven for 2.73.707.9?great!

umm ... guys.. if u dont mind me asking...... why do we need it?
do we have hero versions which cant be rooted with any methods?

dying4004 said:
umm ... guys.. if u dont mind me asking...... why do we need it?
do we have hero versions which cant be rooted with any methods?
Click to expand...
Click to collapse
yup, we couldn't root certain asian carrier roms and t-mob rom and they couldnt downgrade so the where stuck, until now....

tianci86 said:
so it's tested and proven for 2.73.707.9?great!
Click to expand...
Click to collapse
CONFIRMED! it works on 2.73.707.9 , just got 2.73.405.5 , im so happy , thanks soo much guys your the best

My Hero..... lol
Thanks, I thought I would be owned by T-Mobile for ever after the ROM update
Now I'm back to the HTC default ROM (NOT T-Mobile G2 Touch!!!), cup of coffee time before Rooting flashing etc and remaining from now on faithful to Paul and the MoDaCo ROM

hey guys!
i have a question
im a owner of an tmobile g2 touch and want to have the new firmware of the htc hero can i use this hack to update to the newest firmware because at the moment it says if i want so update: error this rom is not for your device, and so on..
thx !
bye
sry for my english im from germany

gyounut said:
hey guys!
i have a question
im a owner of an tmobile g2 touch and want to have the new firmware of the htc hero can i use this hack to update to the newest firmware because at the moment it says if i want so update: error this rom is not for your device, and so on..
thx !
bye
sry for my english im from germany
Click to expand...
Click to collapse
ja das stimmt

thx jesterz
successfully update singapore hero 2.73.707 to 2.73.405, rooting in a while...
{
"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"
}

d0s said:
I had the same issue with Recovery Flasher I couldn't to boot into recovery. I was also unable to downgrade to the 1.7 roms due to a bootloader version error, arghhh. Anywho, managed to work my way round it, i'll explain below. I've got a T-Mobile G2 updated to the latest rom (so no root access).
I first followed the instructions on making a goldcard and then flashed the 2.73.405.5 WWE rom fine.
Now make sure you have the cm-hero-recovery.img (http://content.modaco.net/dropzone/modacopatchedrecovery-1.0.zip) on the root of your sdcard. Aswell as Instant Root (http://neilandtheresa.co.uk/Android/) now install Instant Root on the phone. It should pop up with a notification "instant root was sucessfully" or along those lines. (If you have a problem installing Instant Root make sure Settings>Applications>Unknown Sources is checked)
Instant root then allows for root access with adb shell using the following 2 commands:
1) adb shell
then
2) su
the icon should change from a $ to #.
Now flash the recovery image with the following command:
1) flash_image recovery /sdcard/cm-hero-recovery.img
This shouldn't take that long once completed it will go back the # prompt example below.
# flash_image recovery /sdcard/cm-hero-recovery.img (I typed this)
flash_image recovery /sdcard/cm-hero-recovery.img (this pops up)
# (this shows the flash completed)
Now pull out your usb cable and battery, turn on the phone with the battery in place while holding the home button and it should boot into the custom recovery .
Well, I hope this helps someone and I didn't just waste my time . Oh, thanks for posting the goldcard instructions.
Click to expand...
Click to collapse
Did it last night and got it working, used the AMON Hero recovery image instead and partitioned my sd card without going through the manual adb solution.
Cheers

could this be adapted for the sprint hero?

Sprint Hero support request strongly seconded, i am desperate to get my CDMA Hero rooted.

have you guys tried using thesame method and got anywhere? I mean, from what I know is that you can't even boot in to recovery mode right? have you guys tries the adb method to boot into rec mode at least?

Aces!!!!
Worked on Indian 2.73.720 like a charm.
Thanks.

defy/defy+ bootloader=7,finally got ROOTED`with method

thanks to the forum‘s rule but I cannot post any links in the thread.You have to see them by yourself.
originally posted on bbs.dospy.com/thread-14368781-1-404-1.html by johnnever
bl 7 got rooted at last, thanks to vid190 @bbs.mfunz.com (where the Mokee OS origins)
1. Flash tinyurl.com/cty4s79 with RSD lite after wiping your phone.
2. Flash johnnever's rom (website in China,you may have a very low speed)
Divided in two parts,unzip them together.
part1:dl.dbank.com/c04rtbzxlm
part2:dl.dbank.com/c0qbym7a3b
click the button "下载" left besides "100M" to down it.
3. Wipe your phone and see
Go to bbs.mfunz.com/thread-381759-1-1.html if u wanna see some "technical" details.

Man I hope this is legit and works. So pissed off when Motorola "bricked" my phone by installing BL7 and removing root.

I cannot download because it asks me to sign in or create an account

The full ways to Create a BL7 root file
From vid190(from bbs.mfunz.com)
(An Unlocked BL6 defy needed)
To download the root file, please click http://forum.xda-developers.com/showthread.php?t=1595013
1. Prepare a BL6 sbf
2. Root the BL6 sbf via OTA-ROOT(shell root)
3. Flash in the BL7 sbf when second rebooting
(p.s. SHELL ROOT: add the following lines to the .prop file to mount
2.3 ro.sys.atvc_allow_all_adb=1 ，
4.0 ro.kernel.qemu=1 )
4. Use dd tool in busybox, push busybox to data/local/tmp
5. adb shell data/local/tmp/busybox dd if=/dev/block/mmcblk1p21 of=/sdcard/mmcblk1p21-system.img
6. Done, a root file is made.
Full code, see the grey texts
http://bbs.mfunz.com/thread-381759-1-1.html

不需要亚太的那个sbf
BL=7的可以直接flash
---------- Post added at 09:00 AM ---------- Previous post was at 08:59 AM ----------
uploading dropbox

Have anybody an Idea to Root defy+ DFP 231 with Bootloder 9.10

Finally,good news!,CM7 CM9 with BL7 and more ...

CodeRedXM said:
I cannot download because it asks me to sign in or create an account
Click to expand...
Click to collapse
Just put in your email address, create a password, and when you click on the image verification box, just put in the number you see. They'll send an email to your address to verify it, then you can download the files.
edit: I've uploaded them to mediafire. Note - I HAVE NOT TESTED THESE YET, just put them up to make it easier for people here to download.
mediafire.com/?c42owizzedrkted
mediafire.com/?7bxq4hnrugyl88e

very nice!

This TOTALLY WORKS. Just did it on my Defy+ (tmobile - UK). It didn't boot after the first rom was flashed, but I just removed the battery when RSD said it was complete, and reinstalled it holding the up button to get into the bootloader. Flashed the 2nd rom, and I'm up and running. Installed Adfree to test it, and it worked perfectly. VERY happy with this. I want to go to the nearest Motorola office and wave it around
Edit: Update - I've installed Adfree, and RootBrowser, both requested superuser permissions and were granted them ok after hitting ok. I've tested the file access by deleting the default camera click ogg file, and that worked fine. Also used ESFileExplorer to backup and remove the bloatware that Motorola adds on (Media Share etc). Phone is VERY quick now.

[Guide] Unbricking Solution for LG Nitro HD (P930)

Unbricking Guide:
(Guide for the American version of the device - LG Nitro HD)
*** Remember, whatever you do, you do at your own risk and responsibility for your actions rests solely on you ***​
Introduction:
Sorry, I know my english is not so well as I want, but I tried to explain all steps in this guide for people who never flashed their devices before.
Please, don't mirror links to required tools and files on other sites! Daily traffic is limited!​
Required tools:
1) ADB: Get it from here - Android Developer SDK , and then specify the path (PATH) to the folder containing the ADB.
Alternate method: copy the folder ADB from the folder SuperOneClickv2.3.2_ShortFuse to the drive C:/ on the computer, and then specify the path (PATH) to the folder containing the ADB.
How to specify the path to the ADB:
My computer (right mouse button) -> Properties -> Advanced System Settings -> Environment Variables -> In the lower window find the line Path and double click on it -> At the end of the string "Value" add the complete path to the ADB (eg C:/ADB) and click OK (don't forget to add ";" before).
2) SuperOneClick: Link - Mirror1 - Mirror2
3) LG P930 drivers: Link - Mirror1 - Mirror2
4) KDZ_FW_UPD_EN: Link - Mirror1 - Mirror2
5) Small HTTP Server:
a) shttp3: Link - Mirror1 - Mirror2
b) www: Link - Mirror1 - Mirror2
Required files:
1) V10F_00.kdz: Link - Mirror1 - Mirror2
2) boot.img: Link - Mirror1 - Mirror2
3) recovery.img: Link - Mirror1 - Mirror2
4) firmware.img: Link - Mirror1 - Mirror2
5) baseband.img: Link - Mirror1 - Mirror2
6) system.img: Link - Mirror1 - Mirror2
So now we have everything we need to restore our system. It remains only to extract all the files and you can get to work.
The process of resuscitation:
1) Install the drivers from folder LG P930 drivers.
2) Install the B2CAppSetup from folder KDZ_FW_UPD_EN.
3) Install shttp3.exe on drive C:/, note "I agree with this license, and I accept all items", "Update entry in main menu" and "Add to startup".
4) Run the program http.exe, click the right mouse button on the top of the Small Server and select Server -> Settings...
5) Go to the tab HTTP, in the "TCP/IP port for HTTP server" change port 80 to port 9002 and at the top right click on OK.
6) Unpack content of the www.ziр in the folder C:/shttps/www.
It is important:
Small Server software must be running, or unbricking will not be possible.
7) Open with a notepad (as Administrator) file hosts, which is located in C:/Windows/System32/drivers/etc and at the end add the following:
127.0.0.1 csmg.lgmobile.com
Save and exit.
8) Switch the phone to Download mode:
Turn off the phone, if you have not turned off.
Disconnect the USB cable from the phone if connected.
Hold down Volume Up and connect the USB cable to the phone.
Hold Volume Up until the screen: Download mode.
9) Open the folder KDZ_FW_UPD_EN and run the program UpTestEX_mod2_marwin.exe
10) Click on the folder icon in the row "Select kdz file" and select the file V10F_00.kdz
11) Click on "CSE web upgrade test".
12) In the window that appears, click on "Upgrade Start".
13) In the next window that appears, you will be prompted to select country and language, which will use the program. Since few of us know Korean, change the language to English, and follow on.
14) The program will begin to flash update file V10F_00.kdz on your phone.
It is important:
If you notice that the software update stuck at 4%, close the program through Task Manager and go to step 5!
15) When the update reaches 90% of your phone will reboot. Do not do anything until the upgrade is finished completely!
It is important:
If you notice that the upgrade program generated an error at 93%, do not panic. Just forcibly restart the phone.
If you notice that the upgrade program stucked on 90% for a long time, just forcibly close the upgrade program and move on to getting root.
16) Phone revived, you can begin to get root.
Getting root:
So, your phone is officially revived the Korean language with Korean firmware by default.
Before proceeding, make sure that your phone is connected to a PC in PC Software mode.
1) A gesture from the bottom-up on the lock screen will take you to the master wizard (where everything is in Korean). Press the left button on the bottom of the screen and two seconds later your phone will "talk" to his native English. You can continue to follow the master wizard, but honestly, it's unnecessary. We just wanted to change the language.
2) Install the drivers on the PC from folder LG P930 drivers. After that, wait until the PC to install additional drivers.
3) Go to Settings -> Applications -> Development and turn on "USB debugging".
4) Run SuperOneClick.exe and click Root.
5) Wait for the completion of the root. Check in the phone that the program Superuser appears.
* If it appears, then we can begin to flash the original AT&T's images.
* If not, repeat the procedure for obtaining root.
It is important:
Be patient, sometimes it takes about 20 times to get root.
I strongly recommend to use SuperOneClick 2.3.2 version to get root! Version 2.3.3 for some reason doesn't work with our phone.
Restoring the original Nitro HD images:
1) Connect your phone to your PC in Mass Storage mode (select the type of connections Mass storage).
2) Copy to the root of the SD-card all 5 images (boot.img, recovery.img, firmware.img, baseband.img and system.img).
3) Upon completion of copying of images put the phone back into a PC Software mode and make sure USB debugging enabled.
4) On your PC go to Start -> Run -> write cmd and click OK.
5) In the window that appears, use the following commands are strictly in the order in which they are registered (otherwise, again, get a brick and will have to start from scratch):
Code:
adb shell
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
dd if=/sdcard/firmware.img of=/dev/block/mmcblk0p1
dd if=/sdcard/baseband.img of=/dev/block/mmcblk0p14
dd if=/sdcard/system.img of=/dev/block/mmcblk0p27
6) Wait for the completion of the last command (it takes quite a long time) and forcibly turn off the phone.
7) At the same time hold down the Power button and Volume Down and wait for the screen: Factory reset.
8) Double-click on the power button, confirming our actions.
* Phone will start factory reset and will restart at the end.
Congratulations! Now your phone has an AT&T's operator firmware and root-rights.
Guys, I'm really happy to be a part of this great community, but I decided to move on. Thanks to all of you!

HI,
hey, quick question sort of on/off-topic ;-)
does it matter which kdz i initially flash? in other words, after all the new images are moved over, the initial kdz is irrelevant right? Reason I ask is I did this using the v10i kdz

scott0 said:
HI,
hey, quick question sort of on/off-topic ;-)
does it matter which kdz i initially flash? in other words, after all the new images are moved over, the initial kdz is irrelevant right? Reason I ask is I did this using the v10i kdz
Click to expand...
Click to collapse
No, it doesn't matter. You can flash any kdz you want, but I prefer the v10f.

why's the preference for v10f?
I can go back and reflash my device with the v10f if it's better, easy breezy.

scott0 said:
why's the preference for v10f?
I can go back and reflash my device with the v10f if it's better, easy breezy.
Click to expand...
Click to collapse
It's only because of getting root. I have tried to get root with v10i.kdz many times and I have never succeeded. With v10f.kdz I have not any problems to get root. Yes, sometimes it takes about 10-20 attempts to get root, but in the end is always obtained.

My phone is stuck at the pink LG Optimus LTE screen, there is a progress bar below which moves for few seconds initially but then freezes.
The update tool completes the flashing to 100% and says update completed but the phone doesn't boot.
Any help??
fyi, I was on CM9 nightly before this and wanted to go back stock.

jainanshal said:
My phone is stuck at the pink LG Optimus LTE screen, there is a progress bar below which moves for few seconds initially but then freezes.
The update tool completes the flashing to 100% and says update completed but the phone doesn't boot.
Any help??
fyi, I was on CM9 nightly before this and wanted to go back stock.
Click to expand...
Click to collapse
Sorry, I don't know what is the steps you need to do before you want to go back to stock from CM9. I guess you need to flash the original boot.img before, but I'm not sure.

But is there any way to go past this LG Optimus LTE screen or install recovery from outside or flashing img partitions from this state?
Plz help... it seems my phone is gone

jainanshal said:
My phone is stuck at the pink LG Optimus LTE screen, there is a progress bar below which moves for few seconds initially but then freezes.
The update tool completes the flashing to 100% and says update completed but the phone doesn't boot.
Any help??
fyi, I was on CM9 nightly before this and wanted to go back stock.
Click to expand...
Click to collapse
Did you try doing a factory reset?

yes did.. no use, still the same.
---------- Post added at 10:31 AM ---------- Previous post was at 09:56 AM ----------
There's one more thing..
The marwin tool from the KDZ_FW_UPD_EN.zip file i downloaded using the above link does not have any option to "CSE web upgrade test", the option it gives me is only "Normal web upgrade test". Till now i have been using only that and does it does complete the flashing process, although leads to the pink horror.

Uploading LGP930AT-01-V10j-310-410-FEB-26-2012.zip Please Wait...
Ill update this post when it finish's. This is the latest version they have for it. You can just recover using LGNPST. Ill grab dll later to. Just place in E-mode. Select DLL select TOT and restore.

@amoamare,
Is this just the small 20mb update or is it the full recovery image?

Hello, sorry to derail your thread for a minute, but just dropping by to let you know that this thread has been featured on the XDA Portal
Link
http://www.xda-developers.com/android/unbrick-your-lg-nitro-hd-with-this-guide/
I hope you enjoy it!

@Malnilion,
Its a full 300 MEG File in .TOT format needs to be flashed using LGNPST. It is not the standard system, recovery, boot.img formats.
You must use LGNPST to flash the device, but you can flash in recovery mode to unbrick a device.
---------- Post added at 07:48 PM ---------- Previous post was at 07:38 PM ----------
LGP930AT-01-V10j-310-410-FEB-26-2012.zip
^ Click to download the latest .tot file. You can recover, or just simply go back to stock using LGNPST.
File is 300Megs

@amoamare,
This is truly awesome! This should completely eliminate the need for people to flash the SU-640 rom if they brick their Nitro.

Now you still need the dll for this phone and LGNPST.
Also fair warning. I don't know if GSM phones when flashed in recovery or not loose there IMEI like the cdma versions. Im not responsible for any damages.
I will upload the dll when I get back.

Thank you thank you thank you
I registered on this site just to say thank you for this. I actually never bricked my phone ... just installed the ota update to v10j, which made it impossible to root it. So I followed this guide (I know it was probably a little risky) and finally rooted my phone after a week of failed attempts.
Thanks.

amoamare said:
LGP930AT-01-V10j-310-410-FEB-26-2012.zip
^ Click to download the latest .tot file. You can recover, or just simply go back to stock using LGNPST.
File is 300Megs
Click to expand...
Click to collapse
I'm just curious, but... what is the source of this file? Is there a version of this for the AT&T V10f firmware?

amoamare said:
@Malnilion,
Its a full 300 MEG File in .TOT format needs to be flashed using LGNPST. It is not the standard system, recovery, boot.img formats.
You must use LGNPST to flash the device, but you can flash in recovery mode to unbrick a device.
---------- Post added at 07:48 PM ---------- Previous post was at 07:38 PM ----------
LGP930AT-01-V10j-310-410-FEB-26-2012.zip
^ Click to download the latest .tot file. You can recover, or just simply go back to stock using LGNPST.
File is 300Megs
Click to expand...
Click to collapse
This looks like a ray of life for my phone which is dead since past 2 days... Thanks a ton!!
Can someone plz comment or elaborate more on this tool and how to use it? Also, how about the IMEI issue @amoamare mentioned?
Did any1 try this?

This will be excellent if it is ATT stock V10f.
Question: do we need to select type? ex: CDMA or CMDA-Smart Phone (WM) or doesnt matter?
(For ATT Nitro HD)
Thanks everyone!

V500 im not able to get into bootloader

Hi,
I just want to unlock bootloader on my g pad and flash custom rom. I did this many times on Nexus devices, also sony.
I installed sdk, next Google drivers and my tablet is detected by computer as adb interface.
But when I type command - adb reboot bootlader
Tablet just reboots. I'm not able to get into fastboot. Plz help. It's v500 version. My software version is v50020d.
Earlier I didn't know that LG locks bootloader and I tried many times to flash custom recovery. One time I had made a mistake and using flashify - I flashed twrp for v510. But LG support tool helped me to repair it. Probably it flashed stock with full wipe becsuse I lost data so everything should be fine now but as You can see - it isn't...
HTC One M8

Also command adb reboot oem-unlock only reboots it
HTC One M8

The v500 has a locked bootloader. You need to root first and then install a older aboot and recovery in order to flash roms. This device like the g2 uses loki to bypass the lg lock.

Ok. I've already rooted my device but every time I try to flash twrp using "loki" method I end with screen like this...
{
"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"
}
HTC One M8

WKD622 said:
Ok. I've already rooted my device but every time I try to flash twrp using "loki" method I end with screen like this...
HTC One M8
Click to expand...
Click to collapse
Okay, so that message providing you wait a bit and see twrp start, means that you have successfully bypassed the locked bootloader...
If it freezes there and nothing happens that would be something different... The second sentence reads differently if Loki has bypassed things. The screen above seems to indicate that Loki is not successfully bypassing (hence my edits to this post) it should say something different in the second line if Loki is successful. My tablet is at home right now so I can't take a picture of a working Loki bypass...
A successful bypass should say something like: Device unlock so boot success!

After this screen twrp turns on.
Edit
Okey... Maybe I've done something wrong. Could you tell me how to flash this recovery in points?
I'm not very familiar with LG...
HTC One M8

WKD622 said:
Twrp turns on.
HTC One M8
Click to expand...
Click to collapse
Excellent, then you have successfully installed twrp and you can get into twrp recovery. Next do a backup to an sdcard (if you have one), download a rom to that card and install it...
---
Does TWRP start can you get into it?

muiriddin said:
Excellent, then you have successfully installed twrp and you can get into twrp recovery. Next do a backup to an sdcard (if you have one), download a rom to that card and install it...
Click to expand...
Click to collapse
I had also done this and flash cm but nothing changed.
Maybe this screen was a result of flashing twrp using flashify.
Yesterday I flashed stock so now I want to begin this process one more time . Could You tell me how to do it?
HTC One M8

----
Yes. But now it come to my mind that this problem with booting was a result of twrp for v510 flashed using flashify and next Loki method. Because maybe at the end twrp was for v500 and it worked but I wasn't able to flash anything because it "thought" that I'm using v510. But next i delete line in updater-script connected with authorization and as a result I flashed cm for my v500 but this boot screen didn't changed.
So as you know next thing I've done was flashing stock and now I want to start from beginnig without problems .
Could you tell me how? :/
HTC One M8

WKD622 said:
Yesterday I flashed stock so now I want to begin this process one more time . Could You tell me how to do it?
HTC One M8
Click to expand...
Click to collapse
Okay, my process from a fresh install of 4.4.2 is:
make sure to download everything you need before you start this process and read through it carefully...
1. Root device using stumproot, thread located here:
http://forum.xda-developers.com/lg-g3/orig-development/root-stump-root-lg-g3-sprint-verizon-t2850906
Other root approaches potentially will work as well, I use stump since it also works on my phone...
2. Download and use step 3 from idioterror's thread here:
http://forum.xda-developers.com/showthread.php?t=2698267
You will need to modify his batch file to properly work the details for that are in the thread, the download by itself will not work without changing a line in the batch file (if I recall from memory find the query for 50010b and change it to 50010d.)
If that worked the batch file ends with an attempt to reboot into recovery. Unplug the cable after the batch file sends the reboot command so the adb reboot recovery command can properly complete and get you into recovery...
if the tablet boots back into stock try another adb reboot recovery manually(or use flashify to reboot into recovery), again unplug once the reboot starts.
If that does not get you into TWRP but instead gets you into stock recovery you need to do the steps in idioterror's batch file manually go here for details:
http://forum.xda-developers.com/showpost.php?p=56707177&postcount=15
(be really careful with the dd comands if you do this a mistype with them will be very dangerous)).
Once you have this working recovery you need to decide which base you are going to use with your tablet, the 4.2.2. base (for AOSP based roms) or the 4.4.2 base (for recent stock based roms). The recoveries for the 4.2.2. and 4.4.2 are different see the details in this thread:
http://forum.xda-developers.com/showthread.php?t=2551499
You can run AOSP based roms on the 4.4.2 firmware but you will typically need to flash a 4.4.2 replacement kernel like redkernel or mani... See the proper threads in the development section...
If you are going to run AOSP based roms with the standard kernel skip to 3b...
3a. I am running a 4.4.2 firmware base and a redkernel on lollipop myself, make sure to install the latest 2.8.0 recovery for the 4.4.2 firmware base... You can now flash stock based roms, or AOSP roms with a 4.4.2 capable kernel do not do step 3b for stock based roms...
3b. Install the 4.2.2. base (will actually install a different recovery partition and aboot partition, however it will get your firmware back to 4.2.2. which is what almost all of the AOSP roms expect...) thread and download details here:
http://forum.xda-developers.com/showthread.php?t=2719411
That download is huge and takes a while to flash, don't panic, but make sure that the MD5's match since a failed flash for that one can brick the tablet...
4. Enjoy your rooted and rommable tablet!

muiriddin said:
You will need to modify his batch file to properly work the details for that are in the thread, the download by itself will not work without changing a line in the batch file (if I recall from memory find the query for 50010b and change it to 50010d.)
If that worked the batch file ends with an attempt to reboot into recovery. Unplug the cable after the batch file sends the reboot command so the adb reboot recovery command can properly complete and get you into recovery...
if the tablet boots back into stock try another adb reboot recovery manually(or use flashify to reboot into recovery), again unplug once the reboot starts.
If that does not get you into TWRP this step failed and youwill have to manually walk through what the batch file does... Stop and ask me or someone else for further assistance (or open up idioterror's batch file and figure out what it does so you can do it manually (be really careful with the dd comands if you do this a mistype with them will be very dangerous)).
Click to expand...
Click to collapse
You need to know that yesterday back to stock was my second one. 1st time few days ago I edited script as You wrote here form v50020b to d and it didn't boot to recovery. The same result was when it comes to booting to recovery using app like flashify.
So unfortunately I need to do it with the hardest way . I will try. It will be very nice experience.
I belong to crx team as a (very) novice member so I hope Cr3pt will help me looking at instruction You wrote for me if something goes wrong.
Thanks a lot. Probably everything will be okey but there is an option that I will be back here with more questions. :E
Thanks a lot.
HTC One M8

Does it boot into the stock recovery instead with two really strange errors?
WKD622 said:
You need to know that yesterday back to stock was my second one. 1st time few days ago I edited script as You wrote here form v50020b to d and it didn't boot to recovery. The same result was when it comes to booting to recovery using app like flashify.
So unfortunately I need to do it with the hardest way . I will try. It will be very nice experience.
I belong to crx team as a (very) novice member so I hope Cr3pt will help me looking at instruction You wrote for me if something goes wrong.
Thanks a lot. Probably everything will be okey but there is an option that I will come with more questions.
Thanks a lot.
HTC One M8
Click to expand...
Click to collapse

HTC One M8

WKD622 said:
HTC One M8
Click to expand...
Click to collapse
Yeah, idioterror's script is failing, when I had that happen I had to manually do what was in the batch file via an adb shell. I can't write those instructions until later tonight (assuming my little girl sleeps tonight that is)...
Something has changed which causes his script to fail that I haven't tracked down yet (there is a thread on this somewhere in the LG GPAD forums)... It is either the newest LG drivers, or a newer adb.exe install or something that is conflicting with idioterror's script... his approach still works, you just have to manually do it...
One additional thing, when I manually did it, I had already installed busybox so I did not use his tools (dd etc) I used the ones that I had already installed (I use the BusyBox Pro from Stericson in the play store for this, his free version should also work).

Step by Step Aboot/Recovery when the script fails
WARNING: I'm trying to help, I assume that you know how to recover from mistakes by reverting to stock with LG's software if needed. This is the procedure I followed by manually doing what Id10tError had in his batch file... If anything fails below I messed up in translating the instructions. I did not run the dd commands on my tablet to check since I have already done this process. Please be careful... If you find errors I will try and help... the dd command does have the ability to completely destroy your tablet if you use it incorrectly... if you have questions or see a difference between my instructions and the batch file ask and I'll be glad to answer questions. This was translated from idioterror's script, any errors are mine not his.
I assume that you have installed busybox, (this gives you a working dd on the device)
you have rooted your tablet
and you have adb working on your computer.
You could potentially also do this from the tablet itself if you copy the files needed to the proper locations (skip the push part below) and use a terminal directly. I also assume that you have downloaded idioterror's aboot replacement stuff from my earlier instructions. On the computer go to the directory that you opened the zip file and do a directory listing you should see:
the dd lines below may wrap depending upon how you are displaying this...
The directory should contain:
11/12/2014 09:59 PM <DIR> .
11/12/2014 09:59 PM <DIR> ..
05/16/2014 08:48 PM 524,288 aboot.img
05/16/2014 08:48 PM 815,104 adb.exe
05/16/2014 08:48 PM 96,256 AdbWinApi.dll
05/16/2014 08:48 PM 60,928 AdbWinUsbApi.dll
05/16/2014 08:48 PM <DIR> busybox
05/16/2014 08:48 PM 11,001,856 recovery.lok
07/07/2014 04:41 PM 4,156 runme.bat
then type
adb shell
su
mkdir /sdcard/flash_tmp/
exit
exit
adb push ./aboot.img /sdcard/flash_tmp/aboot.img
adb push ./recovery.lok /sdcard/flash_tmp/recovery.lok
adb shell
su
chmod -R 777 /sdcard/flash_tmp
dd if=/sdcard/flash_tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/flash_tmp/recovery.lok of=/dev/block/platform/msm_sdcc.1/by-name/recovery
rm -rf /sdcard/flash_tmp/
exit
exit
adb reboot recovery
unplug the cable once it starts rebooting and enter TWRP recovery...
It will be dim if you are coming from the 4.4.2 base, go to a dark room if needed so you can see it and flash a newer 4.4.2 recovery next if you are planning on using stock roms, or flash the 4.2.2. base otherwise... see my earlier post for a link to the recovery thread or the 4.2.2 base.

Thanks!
Everything works perfect
HTC One M8

Step 3 of idioterror's thread doesn't work.
You said:
2. Download and use step 3 from idioterror's thread here:
http://forum.xda-developers.com/showthread.php?t=2698267
However, I am unable to download the file from the link.
Do you know of another location where the file can be downloaded?
Thanks in advance!
Morty.

How To Guide [GUIDE] Change Splash screen for this phone!

NOTE: I am not responsible for any bricked devices. DO THIS AT YOUR OWN RISK!
Click to expand...
Click to collapse
I recently changed my splash screen logo from samsung to a custom one i made in pixlr. Its looks coool. A video is attached below.
REQUIREMENTS:
- ROOTED A32 4G
- usb c cable (to connect to pc)
- windows PC (for zipping and etc.)
- ADB installed on your pc. (For running shell commands) [OR YOU COULD USE SOME TERMINAL EMULATOR]
If your doing this on your phone just follow along, i included seperate commands.
STEPS:
1. Download attached up_param.bin (i extracted this from android 11 firmware. it shld work with fine with 12 they are same. Since downloading whole firmware takes alot of time)
2. Install 7zip if you already didn't from here.
3. Make a working directory anywhere
4. Use 7 zip to extract up_param.bin to a folder.
After extracting this is what you should see
{
"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"
}
These are all the images!
5. modify files as you like. (MAKE SURE THE DIMENSIONS ARE THE SAME. AND DO NOT REMOVE ANY IMAGE IT COULD BRICK)
NOTE: DO NOT TOUCH DOWNLOAD MODE IMAGES. if you f**k them up you will never be able to get into download mode again
You can replace boot_warning.jpg, logo.jpg (main file responsible logo), letter.jpg (the logo that shows for a split second), svb_orange.jpg (boot loader unlock warning)
6. select all images -> right click -> add to archive.
7. set it to tar.
8. set compression method to GNU.
This is what it should look like
9. Click on OK.
10. Now connect your A32 to the PC. (enable USB debugging)
11. Copy over the tar file that was generated by 7zip to anywhere. i am gonna assume we placed it in the internal storage (/sdcard/)
12. Run the following commands.
NOTE: I am editing the original thread since i checked in up param file of my new a13 fw and found new file. Its for if the battery temperature is too high. if you modify the up param from a11 fw and flash that it may not exist and the phone will boot loop if it wants to display the menu...
iM UPLOADING A13 stock up_param HERE FROM A325FXXU2CVK3.
Uploaded as up_param-a13.bin
adb shell (Phone users skip this.)
su
(Grant su permission if the popup comes up).
Then run
ls -l /dev/block/platform/****/by-name
After you get a long output. Search for up_param.
(We all have the same phone but just in case some people with diff samsung mtk phones come here).
now we just have to run 2 more commands and we are done!
Taking backups incase something goes wrong.
(People with different phones replace your up_param partition name here.)
dd if=/dev/block/mmcblk0p35 of=/sdcard/backup-param.bin
Now flashing our new modified up_param with new images
dd if=/sdcard/filename.tar of=/dev/block/mmcblk0p35
WE ARE DONE! now reboot and enjoy the new logo!

CREDITS:
- Orignal post: here.
Also video attached below

Captain_cookie_200 said:
I recently changed my splash screen logo from samsung to a custom one i made in pixlr. Its looks coool. A video is attached below.
REQUIREMENTS:
- ROOTED A32 4G
- usb c cable (to connect to pc)
- windows PC (for zipping and etc.)
- ADB installed on your pc. (For running shell commands) [OR YOU COULD USE SOME TERMINAL EMULATOR]
If your doing this on your phone just follow along, i included seperate commands.
STEPS:
1. Download attached up_param.bin (i extracted this from android 11 firmware. it shld work with fine with 12 they are same. Since downloading whole firmware takes alot of time)
2. Install 7zip if you already didn't from here.
3. Make a working directory anywhere
4. Use 7 zip to extract up_param.bin to a folder.
After extracting this is what you should see
View attachment 5775661
These are all the images!
5. modify files as you like. (MAKE SURE THE DIMENSIONS ARE THE SAME. AND DO NOT REMOVE ANY IMAGE IT COULD BRICK)
NOTE: DO NOT TOUCH DOWNLOAD MODE IMAGES. if you f**k them up you will never be able to get into download mode again
You can replace boot_warning.jpg, logo.jpg (main file responsible logo), letter.jpg (the logo that shows for a split second), svb_orange.jpg (boot loader unlock warning)
6. select all images -> right click -> add to archive.
View attachment 5775663
7. set it to tar.
8. set compression method to GNU.
This is what it should look like
View attachment 5775665
9. Click on OK.
10. Now connect your A32 to the PC. (enable USB debugging)
11. Copy over the tar file that was generated by 7zip to anywhere. i am gonna assume we placed it in the internal storage (/sdcard/)
12. Run the following commands.
adb shell (Phone users skip this.)
su
(Grant su permission if the popup comes up).
Then run
ls -l /dev/block/platform/****/by-name
After you get a long output. Search for up_param.
View attachment 5775673
(We all have the same phone but just in case some people with diff samsung mtk phones come here).
now we just have to run 2 more commands and we are done!
Taking backups incase something goes wrong.
(People with different phones replace your up_param partition name here.)
dd if=/dev/block/mmcblk0p35 of=/sdcard/backup-param.bin
Now flashing our new modified up_param with new images
dd if=/sdcard/filename.tar of=/dev/mmcblk0p35
WE ARE DONE! now reboot and enjoy the new logo!
Click to expand...
Click to collapse
Very good thanks

kilam9900 said:
Very good thanks
Click to expand...
Click to collapse
hehe your welcome. hope it works epikly for you. (if you do it)

Captain_cookie_200 said:
hehe your welcome. hope it works epikly for you. (if you do it)
Click to expand...
Click to collapse
I will do it but I am scare to f**k size so I will do it on PC

kilam9900 said:
I will do it but I am scare to f**k size so I will do it on PC
Click to expand...
Click to collapse
oh lmao. if you do end up breaking your up_param it would still boot fine. but downlaod mode would break until a proper up param file is flashed again.

Captain_cookie_200 said:
oh lmao. if you do end up breaking your up_param it would still boot fine. but downlaod mode would break until a proper up param file is flashed again.
Click to expand...
Click to collapse
I'm reassured

I recommend using dd oflag=direct,sync if=/sdcard/filename.tar of=/dev/block/mmcblk[...] otherwise you may get all sorts of problems, even a bricked phone, especially if you reboot straightaway after flashing. Inside Android all data transfers are cached, it's not the Download tool where everything is synchronous (or at least flushed before reboot).

uluruman said:
I recommend using dd oflag=direct,sync if=/sdcard/filename.tar of=/dev/block/mmcblk[...] otherwise you may get all sorts of problems, even a bricked phone, especially if you reboot straightaway after flashing. Inside Android all data transfers are cached, it's not the Download tool where everything is synchronous (or at least flushed before reboot).
Click to expand...
Click to collapse
i didnt have to deal with anything like that. i did multiple flashes atleast 15 flashes using dd to the up param partition and i did not brick my phone at all. worse you could get is a black screen while booting. and your download mode would not work. but its easy to get it back just flash the up param file again the one that was backed up. although thanks for the info. i did this using recovery. could also be done while booted into android itself

Captain_cookie_200 said:
i didnt have to deal with anything like that. i did multiple flashes atleast 15 flashes using dd to the up param partition and i did not brick my phone at all. worse you could get is a black screen while booting. and your download mode would not work. but its easy to get it back just flash the up param file again the one that was backed up. although thanks for the info. i did this using recovery. could also be done while booted into android itself
Click to expand...
Click to collapse
I ran into this problem when rebooted the phone using the "reboot" shell command right after the "dd". When rebooting from the UI all caches are flushed, of course, but the "reboot" command is a bit crude method I suppose (although in Linux it's always absolutely graceful). Anyway, the logo screen looked absolutely fine, and the system booted okay, but when I tried to enter Download I got the black screen and the boot loop, and no way to either enter Download, Recovery or boot the system. In fact the only thing that still worked was forced reboot (Power + Vol Down). I was able to get out of this situation by connecting the charger and holding Power + Vol Down to force the phone into the off state, then I connected it to the PC and tried entering the Download mode once again, and this time it worked although the graphics was all messed up.

uluruman said:
I ran into this problem when rebooted the phone using the "reboot" shell command right after the "dd". When rebooting from the UI all caches are flushed, of course, but the "reboot" command is a bit crude method I suppose (although in Linux it's always absolutely graceful). Anyway, the logo screen looked absolutely fine, and the system booted okay, but when I tried to enter Download I got the black screen and the boot loop, and no way to either enter Download, Recovery or boot the system. In fact the only thing that still worked was forced reboot (Power + Vol Down). I was able to get out of this situation by connecting the charger and holding Power + Vol Down to force the phone into the off state, then I connected it to the PC and tried entering the Download mode once again, and this time it worked although the graphics was all messed up.
Click to expand...
Click to collapse
did you touch the download mode images in any way? i dont know why this happened for you. i guess i did press the reboot button instead of using the command. since i do it on first fw reflash and i flash a gsi immdiiately afterwards... download shouldnt have died like that tho. i messed with my down load images completely. i competely replaced them with diff new images that are diff sizes too. i dont know why this is happening for you. my download works fine. although it reverts to the old download image somehow once on downloading mode. for confirmations it does show my edited images.

Captain_cookie_200 said:
did you touch the download mode images in any way? i dont know why this happened for you. i guess i did press the reboot button instead of using the command. since i do it on first fw reflash and i flash a gsi immdiiately afterwards... download shouldnt have died like that tho. i messed with my down load images completely. i competely replaced them with diff new images that are diff sizes too. i dont know why this is happening for you. my download works fine. although it reverts to the old download image somehow once on downloading mode. for confirmations it does show my edited images.
Click to expand...
Click to collapse
I suppose your Download still worked fine because the up_param tar archive was complete and not corrupt, and even image files were normal and not chopped in the middle of the data stream. In my case it was the latter, when cache is not flushed the data stream is just cut, and such a simple program as Download obviously cannot handle broken files. The Download tool itself is kept in the separate "debugger" flash memory, I guess it has the default graphics too which can be displayed if no graphics is found in up_param.

uluruman said:
I suppose your Download still worked fine because the up_param tar archive was complete and not corrupt, and even image files were normal and not chopped in the middle of the data stream. In my case it was the latter, when cache is not flushed the data stream is just cut, and such a simple program as Download obviously cannot handle broken files.
Click to expand...
Click to collapse
oh i see. thanks for telling about this. it would help people alot from preventing to brick their phone from bricking

Captain_cookie_200 said:
oh i see. thanks for telling about this. it would help people alot from preventing to brick their phone from bricking
Click to expand...
Click to collapse
Correction: 'dd oflag=direct,sync' does not work in Android shell, the working alternative is 'dd conv=fsync'

Captain_cookie_200 said:
I recently changed my splash screen logo from samsung to a custom one i made in pixlr. Its looks coool. A video is attached below.
REQUIREMENTS:
- ROOTED A32 4G
- usb c cable (to connect to pc)
- windows PC (for zipping and etc.)
- ADB installed on your pc. (For running shell commands) [OR YOU COULD USE SOME TERMINAL EMULATOR]
If your doing this on your phone just follow along, i included seperate commands.
STEPS:
1. Download attached up_param.bin (i extracted this from android 11 firmware. it shld work with fine with 12 they are same. Since downloading whole firmware takes alot of time)
2. Install 7zip if you already didn't from here.
3. Make a working directory anywhere
4. Use 7 zip to extract up_param.bin to a folder.
After extracting this is what you should see
View attachment 5775661
These are all the images!
5. modify files as you like. (MAKE SURE THE DIMENSIONS ARE THE SAME. AND DO NOT REMOVE ANY IMAGE IT COULD BRICK)
NOTE: DO NOT TOUCH DOWNLOAD MODE IMAGES. if you f**k them up you will never be able to get into download mode again
You can replace boot_warning.jpg, logo.jpg (main file responsible logo), letter.jpg (the logo that shows for a split second), svb_orange.jpg (boot loader unlock warning)
6. select all images -> right click -> add to archive.
View attachment 5775663
7. set it to tar.
8. set compression method to GNU.
This is what it should look like
View attachment 5775665
9. Click on OK.
10. Now connect your A32 to the PC. (enable USB debugging)
11. Copy over the tar file that was generated by 7zip to anywhere. i am gonna assume we placed it in the internal storage (/sdcard/)
12. Run the following commands.
NOTE: I am editing the original thread since i checked in up param file of my new a13 fw and found new file. Its for if the battery temperature is too high. if you modify the up param from a11 fw and flash that it may not exist and the phone will boot loop if it wants to display the menu...
iM UPLOADING A13 stock up_param HERE FROM A325FXXU2CVK3.
Uploaded as up_param-a13.bin
adb shell (Phone users skip this.)
su
(Grant su permission if the popup comes up).
Then run
ls -l /dev/block/platform/****/by-name
After you get a long output. Search for up_param.
View attachment 5775673
(We all have the same phone but just in case some people with diff samsung mtk phones come here).
now we just have to run 2 more commands and we are done!
Taking backups incase something goes wrong.
(People with different phones replace your up_param partition name here.)
dd if=/dev/block/mmcblk0p35 of=/sdcard/backup-param.bin
Now flashing our new modified up_param with new images
dd if=/sdcard/filename.tar of=/dev/block/mmcblk0p35
WE ARE DONE! now reboot and enjoy the new logo!
Click to expand...
Click to collapse
NOTE: I am editing the original thread since i checked in up param file of my new a13 fw and found new file. Its for if the battery temperature is too high. if you modify the up param from a11 fw and flash that it may not exist and the phone will boot loop if it wants to display the menu...
iM UPLOADING A13 stock up_param HERE FROM A325FXXU2CVK3.
Uploaded in orignal thread as up_param-a13.bin

I made it and works perfectly, thanks for the tutorial!!

ApiYoshi said:
I made it and works perfectly, thanks for the tutorial!!
Click to expand...
Click to collapse
glad to hear thatt. and your welcome

how to apply this on snapdragon devices
they don't have up_parem.bin file ??

elswerky said:
how to apply this on snapdragon devices
they don't have up_parem.bin file ??
Click to expand...
Click to collapse
they do? check inside bl file of your firmware. Or using the partition list command should show it

Captain_cookie_200 said:
they do? check inside bl file of your firmware. Or using the partition list command should show it
Click to expand...
Click to collapse
Bl file itself doesn't have up_parem.bin file
Unlike exynis devices which have it
And am.nit familiar with partition as you said if you can helping me
Talking about tab S6 w8th android 12 , OneUi 4.1