Database Develop

[GUIDE] Unbricking SamsungGalaxyMini

credits to those who found this out in other units
---------------------------------------------------------------------------------------------------
i have found a solution for this problem
by reading other units solutions (even if it's posted everywhere, i just want to share this)
this thing will solve the:
E: can't open /cache/recovery/log
E: can't mount /cache/recovery/last_log
and others
unbricking steps:
- remove sim card, and sdcard
- remove battery for even less than 30-20 seconds
- hold volume down, home key and power button simultaneously and put the battery, it will go directly to Download Menu
- open ODIN and DO NOT USE ONE PACKAGE, set the files, i used XXKPI with the 4 files, CSC, APBOOT, MODEM and CODE. dont use the ONE PACKAGE in this kind of flashing. i tested it but nothing happen so i used the other option.
- flash it, wait and done! back to normal.
i thought i should bring this up to the samsung center for the warranty
though i tried other options and experimenting
whew
thanks be to GOD.

Maybe post all the 4 files for all of us?
Luckily, I don't have my device bricked... yet.

yes, u should post a few of screens

sir sevenfolds. what is the difference between the onepackage and yun split package in 4 parts

ahmish said:
sir sevenfolds. what is the difference between the onepackage and yun split package in 4 parts
Click to expand...
Click to collapse
One packages contains all the needed files at a single tar or md5 file while using separate packages you use different tar for PHONE, PDA, CSC, BOOT in Odin... There is not much difference these file are also included in the one package zip file.

Bull **** ! This doesnt work ...this tutorial only for soft brick
---------- Post added at 05:17 PM ---------- Previous post was at 05:12 PM ----------
I tried every single thing after bricking my phone with ROM manager. Ended up giving my phone to the service center....Even they couldnt fix it. Now they r replacing the mother board...9 days over and I havent received my phone back...

same thing happened to mate, luckily the Samsung guys replaced under warranty, checkout my posts they might be of some use.

chemicalrage said:
Bull **** ! This doesnt work ...this tutorial only for soft brick
---------- Post added at 05:17 PM ---------- Previous post was at 05:12 PM ----------
I tried every single thing after bricking my phone with ROM manager. Ended up giving my phone to the service center....Even they couldnt fix it. Now they r replacing the mother board...9 days over and I havent received my phone back...
Click to expand...
Click to collapse
until now, nothing we can do for hard-brick without special tools

chemicalrage said:
Bull **** ! This doesnt work ...this tutorial only for soft brick
---------- Post added at 05:17 PM ---------- Previous post was at 05:12 PM ----------
I tried every single thing after bricking my phone with ROM manager. Ended up giving my phone to the service center....Even they couldnt fix it. Now they r replacing the mother board...9 days over and I havent received my phone back...
Click to expand...
Click to collapse
Good for you!!hahaha
Sent from my GT-S5570 using xda premium

[Q] [HELP!] Moto X XT1058 unbrickable!!!

Dear XDA community. After several days of trying alot of things I dare to bother you because Im really in need of your expertise (Excuse my english please, Im not native speaker).
I will explain everything in ordered manner, so the help may come easily:
Original state when device was gifted to me:
Device: Moto X XT1058 (Ghost Version 2013)
Bootloader: Unlocked
Rooted: Yes
Android Version: 4.4.4 (RETAIL-BR_4.4.4_KXA21.12-L1.26_52_cid12_CFC_1FF)
FIRST PROBLEM DETECTED: Wifi suddenly stopped working
Fix attempted: Hard reset (wipe, etc etc).
Result: Nothing changed
Alternate fix: Installed Lollipop 5.1 and wifi stayed the same (I used the method of going from 5.0.2 to 5.1).
Lollipop versions used: Blur Version 221..41.31 and 38 (5.0.2) and 222.21.2 (5.1) all of them ending in ghost_row.Brasil.en.BR
MEthod used: ADB, succesfull install (The tutorial I followed asked for use OTA for installing the first upgrade of the 5.0.2, but my wifi is not working and I havent payed my phone, so no Data for me this month )
So until that, everything was fine except wifi. I read in some forums that I should try the original stock rom for the device, so I succesfully downgraded to 4.2.2 version---> WIFI STILL NOT WORKING
Ok. I know Im stubborn, so I said, what the hell, lets return to the 4.4.4 version I used to have. I re installed and EVERYTHING WAS FINE also there.
Now, here is where it gets super weird because I really made a bad mistake, but I know there is some hope in this forums: I tried to install again 5.1 for the second time (using the little by little upgrade from 5.0.2 to 5.1) but I forgot that the first time, the tutorial demanded to install the 5.0.2 through OTA (By placing the file inside the root folder of the device). But as you may probably know, unless you have wifi or data the OTA wont let you go with the update (and I as I explained above, I dont have nether!!!, so thats why I used ADB with good results), so I stupidly tried to flash the 5.0.2 directlty from the device using recovery mode instead of using ADB (as an alternate step to OTA)--->Device bricked???
This is all the error list I have after all that mess, and I dont know what else to do:
-------------------------
START OF LIST
Status Code: 0 (it was on 3 before)
Boot Mode: Working but seems to be locked (used to have the "unlocked bootloader warning" before)
Error Showing when starting phone:
"downgraded security version
update gpt_main version failed
Failed to hab check for gpt backup: 0x35
CID Read Failure
Invalid CID Status 0x69 Customer ID error. Contact Dealer: 0xdead
Fastboot reason: Invalid CID"
Error showing when trying to go to Recovery Mode:
Boot Up Failed
Fix #1 attempted: Flashing Team Win Recovery from Fast Boot and Moto Fast Boot
Error #1 Shown on CMD prompt on PC:
"(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (9136 KB)...
OKAY [ 0.835s]
writing 'recovery'...
(bootloader) Permission denied
FAILED (remote failure)"
Error #1 Shown on device:
"Fastboot Reason: Invalid CID
USB Connected
getvar partition-type: recovery
getvar max-download-size
downloading xxxx (9355264) bytes
done"
Fix #2 attempted: Flashing stock rom using different Fastboot commands (RDB doesnt recognice device, but Fastboot do recognice device) such as "fastboot oem, etc etc--> its a big list)
Error #2 shown: Variable not supported! (in all cases)
Fix #3 attempted: Trying to re unlock bootloader in case is still locked using "fastboot oem get_unlock_data" command
Error #3 shown on CMD window: Could not get unlock data!
Error #3 shown on device: Process oem command: get_unlock_data
Fix #4 attempted: Trying to flash the stock rom from fastboot (version RETAIL-BR_4.4.4_KXA21.12-L1.26_52_cid12_CFC_1FF.img)
Error #4 shown on CMD on PC:
"(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (1 KB)...
OKAY [ 0.279s]
writing 'recovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.379s"
Error #4 shown on device:
"getvar partition-type: recovery
getvar max-download-size
downloading 1364 bytes
done"
Possible solution found (not working for me): To open the stock file with note pad and erase all get var lines and save, and try again. This stock rom im using doesnt have those lines. But any way, any attempt of flashing whatever ends in a "not valid" or something similar error
END OF LIST
____________________________
So I guess I have tried many things, I know Im missing something but Im not but a noob user, so I dont know how to interpetrate this errors and messages!! My only guess is that my device became "non rooted" and the bootloader is screwed in some way. I just... I just dont know what to do, I seriously need your help guys!!!!! I know it maybe is easier to go to a repair technician but I really would appretiate your help so I can learn from my mistakes!!!
Questions: Is there a way to root the device and fix the bootloader from Fastboot mode?
Thanks and more thanks to you all!!!!! May the gods of technology help us all!!! :angel:

I'm going to tell you what caused it, and why...
You attempted to downgrade ROM version (you had 5.1 and flashed an older rom)... and that is what messed you up.
There are many many warnings in these forums telling people DO NOT DOWNGRADE, even if you have an unlocked bootloader! For example, an entire thread -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202
As for how to fix it... With what is available to us today, there is no 100% safe way. However, in the threads you'll find others in the same/similar situation. You should be able to find a process to try to get you back to a working phone, BUT not everyone has been successful in recovering from this situation.

KidJoe said:
I'm going to tell you what caused it, and why...
You attempted to downgrade ROM version (you had 5.1 and flashed an older rom)... and that is what messed you up.
There are many many warnings in these forums telling people DO NOT DOWNGRADE, even if you have an unlocked bootloader! For example, an entire thread -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202
As for how to fix it... With what is available to us today, there is no 100% safe way. However, in the threads you'll find others in the same/similar situation. You should be able to find a process to try to get you back to a working phone, BUT not everyone has been successful in recovering from this situation.
Click to expand...
Click to collapse
Hi and thanks for kindly response. As you said, it was my silly mistake (in my desperate effort to see if the wifi issue was a software issue or not). Now I just had no other option than to take the device to a Motorola Lab, they said that some part of the hardware was burnen even befor I tried the downgrade...so nothing to do here.....thanks anyway

duendemago said:
Hi and thanks for kindly response. As you said, it was my silly mistake (in my desperate effort to see if the wifi issue was a software issue or not). Now I just had no other option than to take the device to a Motorola Lab, they said that some part of the hardware was burnen even befor I tried the downgrade...so nothing to do here.....thanks anyway
Click to expand...
Click to collapse
maybe with this thread you can resurrect your moto x http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057

If, as you say, the first thing that happened was that you lost WiFi then at that point in time a simple way to check for a hardware error would have been to look at what happens when you try to turn WiFi back on.
If WiFi tries to turn on and then just turns back off again in a second or so then the next step it to try turning on Bluetooth.
If Bluetooth does the same thing -- tries to turn on and then fails -- then that means, as Moto told you when they looked at it, that you have a hardware failure: If only one radio won't turn on then it's probably software/cache. If both won't turn on it's hardware.

glarepate said:
If, as you say, the first thing that happened was that you lost WiFi then at that point in time a simple way to check for a hardware error would have been to look at what happens when you try to turn WiFi back on.
If WiFi tries to turn on and then just turns back off again in a second or so then the next step it to try turning on Bluetooth.
If Bluetooth does the same thing -- tries to turn on and then fails -- then that means, as Moto told you when they looked at it, that you have a hardware failure: If only one radio won't turn on then it's probably software/cache. If both won't turn on it's hardware.
Click to expand...
Click to collapse
Thanks for response. In fact, Wifi turned on, but no wifi networks were shown at all, except some rare exceptions where you could see 1 or 2 maximum, but nether way it wouldnt connect to any, doesn´t matter if I was on 4.4.4 or 5.1, so my silly mistake was to downgrade to stock 4.2.2. I took it to Moto LAb and they warned me that their attempt to mount new software could lead to final total brick (no boot loader etc.), due to the lack of options, I accepted and now my Moto X is dead... RIP...and thanks to this wonderful community!!! :highfive:

miju12 said:
maybe with this thread you can resurrect your moto x http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
Click to expand...
Click to collapse
thanks i will try it

duendemago said:
Status Code: 0 (it was on 3 before)
Click to expand...
Click to collapse
That shouldn't be possible to go from 3 to 0. If you were status code 3 unlocked and relocked your bootloader you should be status code 2 locked now
---------- Post added at 08:08 PM ---------- Previous post was at 08:05 PM ----------
duendemago said:
thanks i will try it
Click to expand...
Click to collapse
I don't think you need that - you can still get into fastboot and have your device recognized. That method is for those who cannot get into fastboot and have their device recognized as a Moto X. It says QHSUSB_DLOAD instead. Based on what you have written, yours isn't in that state yet.
Call Motorola if you have to and get the device's unlock code. You should have a motorola account and have your device linked to it in My Stuff or whatever the equivalent is in your country's motorola web site.
---------- Post added at 08:16 PM ---------- Previous post was at 08:08 PM ----------
duendemago said:
Error Showing when starting phone:
"downgraded security version
update gpt_main version failed
Failed to hab check for gpt backup: 0x35
CID Read Failure
Invalid CID Status 0x69 Customer ID error. Contact Dealer: 0xdead
Fastboot reason: Invalid CID"
Click to expand...
Click to collapse
Try reading these threads too:
http://forum.xda-developers.com/showthread.php?t=2273574
http://forum.xda-developers.com/showthread.php?t=2375197

JulesJam said:
That shouldn't be possible to go from 3 to 0. If you were status code 3 unlocked and relocked your bootloader you should be status code 2 locked now
---------- Post added at 08:08 PM ---------- Previous post was at 08:05 PM ----------
I don't think you need that - you can still get into fastboot and have your device recognized. That method is for those who cannot get into fastboot and have their device recognized as a Moto X. It says QHSUSB_DLOAD instead. Based on what you have written, yours isn't in that state yet.
Call Motorola if you have to and get the device's unlock code. You should have a motorola account and have your device linked to it in My Stuff or whatever the equivalent is in your country's motorola web site.
---------- Post added at 08:16 PM ---------- Previous post was at 08:08 PM ----------
Try reading these threads too:
http://forum.xda-developers.com/showthread.php?t=2273574
http://forum.xda-developers.com/showthread.php?t=2375197
Click to expand...
Click to collapse
Thanks for kind response. Dont believe me...what do I know? Im also in shock with this 3 to 0 status!! An engineer in programing friend of mine told me that due to that locked state of the device, it was imposible to flash anything, no recovery, no nothing!!! I didnt know you could get the code by phone.. I will try to do that, maybe that could save my noob ass!!! Thanks sir!

JulesJam said:
That shouldn't be possible to go from 3 to 0. If you were status code 3 unlocked and relocked your bootloader you should be status code 2 locked now
Click to expand...
Click to collapse
And you shouldn't be able to change the CID, even with a Dev Edition.... But notice his says CID: 0xDEAD
We see this happen from time to time due to a failed downgrade attempt. It leaves the phone in an "unknown" state.
That being said, in the past we've seen some who are able to recover this by using mfastboot to flash the SBF which matched the newest ROM the user had on the phone (with some extra command lines). But in this case, since there isn't a 5.1 SBF, that is not an option.

duendemago said:
Thanks for kind response. Dont believe me...what do I know? Im also in shock with this 3 to 0 status!! An engineer in programing friend of mine told me that due to that locked state of the device, it was imposible to flash anything, no recovery, no nothing!!! I didnt know you could get the code by phone.. I will try to do that, maybe that could save my noob ass!!! Thanks sir!
Click to expand...
Click to collapse
Read these threads I linked to. It looks like these people had the same problem you did and solved it themselves:
http://forum.xda-developers.com/showthread.php?t=2273574
http://forum.xda-developers.com/showthread.php?t=2375197
---------- Post added at 04:40 PM ---------- Previous post was at 04:39 PM ----------
KidJoe said:
And you shouldn't be able to change the CID, even with a Dev Edition.... But notice his says CID: 0xDEAD
We see this happen from time to time due to a failed downgrade attempt. It leaves the phone in an "unknown" state.
That being said, in the past we've seen some who are able to recover this by using mfastboot to flash the SBF which matched the newest ROM the user had on the phone (with some extra command lines). But in this case, since there isn't a 5.1 SBF, that is not an option.
Click to expand...
Click to collapse
In the 2 threads I keep linking to, the people had the same problem that OP had but were able to solve it. He should read them.

JulesJam said:
That shouldn't be possible to go from 3 to 0. If you were status code 3 unlocked and relocked your bootloader you should be status code 2 locked now
---------- Post added at 08:08 PM ---------- Previous post was at 08:05 PM ----------
I don't think you need that - you can still get into fastboot and have your device recognized. That method is for those who cannot get into fastboot and have their device recognized as a Moto X. It says QHSUSB_DLOAD instead. Based on what you have written, yours isn't in that state yet.
Call Motorola if you have to and get the device's unlock code. You should have a motorola account and have your device linked to it in My Stuff or whatever the equivalent is in your country's motorola web site.
---------- Post added at 08:16 PM ---------- Previous post was at 08:08 PM ----------
Try reading these threads too:
http://forum.xda-developers.com/showthread.php?t=2273574
http://forum.xda-developers.com/showthread.php?t=2375197
Click to expand...
Click to collapse
JulesJam said:
Read these threads I linked to. It looks like these people had the same problem you did and solved it themselves:
http://forum.xda-developers.com/showthread.php?t=2273574
http://forum.xda-developers.com/showthread.php?t=2375197
---------- Post added at 04:40 PM ---------- Previous post was at 04:39 PM ----------
In the 2 threads I keep linking to, the people had the same problem that OP had but were able to solve it. He should read them.
Click to expand...
Click to collapse
Thanks!!! I will try those...nothing to lose here. The device remains at its lonely bootloader state with the "Invalid Cid" error when turned on, etc. I chat with a Motorla assistant and he said they CAN´T PROVIDE the unlock code for the Bootloader because they don´t have that info, the only way is the traditional "go to a web page and unlock here" way, but that didn´t work for me at all (the device shown errors when trying to obtain unlock code). Soooo I will keep trying guys! Thanks for kind responses!!!

duendemago said:
I chat with a Motorla assistant and he said they CAN´T PROVIDE the unlock code for the Bootloader because they don´t have that info,
Click to expand...
Click to collapse
The front line reps can't provide it but Tier 3 Tech support can. They are US based and you have to get a call back from them. It takes awhile before they will get back to you.
Try the other methods in the links first. I think that one link is in spanish too.

Here's what worked for me (I was in the exact same situation as you). For me the problem was to find the stock rom that was installed before it bricked, which in my case was the one in this link (Go down to: XT1053 Retail GSM Unlocked (Version: 222.27.5.ghost_row.Retail.en.US, Modded Version: 222.21.15.ghost_row.Retail.en.US) and choose the untouched version). Here's the thing, I don't know what was your las rom, so it is a matter of trying which retail rom was the one it got bricked in, it took me like 6 months of trying and trying. Btw, i'm using normal fast boot (not mfastboot) in Mac, and the instructions in this website. Please note that both of these commands gave me the error: FAILED (remote failure):
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
Click to expand...
Click to collapse
But it went ok when I rebooted it after finishing installation (took a long time to pass motorola logo tho).
PD. Phone status returned to UNLOCKED Status 3 after installing the OS.

{
"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"
}
This is Moto X Xt1058 ( 2013 ) At&t .. I tried to Root. But its Failed. Showing This Error , Anybudy Please Tell me can we Resolve this Error !
I Tried to Flash Rom with Rsd Lite . But its failing Gpt.bin....Please tell me anybudy

Bootloader unlock theory 2

I possibly found that the lg g4 can connect a serial console when in fast-boot and android with limited access, and that the boot-loader is based on little kernel
codeaurora.org/blogs/little-kernel-based-android-bootloader
It may be possible to connect uart via serial and map out how the bootrom loads the sbl and (aboot (bootloader))and possibly find a way to unlock the boot-loader
newandroidbook.com/Articles/aboot.html
so far acessing fastboot with a nuked laf partition only specific fastboot commands work. can not get oem-id or reboot/continue via fastboot
console=
/dev/tty
/dev/ttyHS0
/dev/ttyHSL0
/dev/ttyHSL1

gefiltefish1478 said:
I possibly found that the lg g4 can connect a serial console when in fast-boot and android with limited access, and that the boot-loader is based on little kernel
codeaurora.org/blogs/little-kernel-based-android-bootloader
It may be possible to connect uart via serial and map out how the bootrom loads the sbl and (aboot (bootloader))and possibly find a way to unlock the boot-loader
newandroidbook.com/Articles/aboot.html
so far acessing fastboot with a nuked laf partition only specific fastboot commands work. can not get oem-id or reboot/continue via fastboot
console=
/dev/tty
/dev/ttyHS0
/dev/ttyHSL0
/dev/ttyHSL1
Click to expand...
Click to collapse
Try posting this in here: http://forum.xda-developers.com/g4/help/unlock-technical-steps-to-make-unlocked-t3165391
Or even the general G4 forum; the audience appears bigger and you'll probably be able to get more brains taking a look at this!
It's quite interesting.

Dude, I was literally coming here to see if anyone had tried anything like USB serial console the way you'd do with like a raspberry pi or a more recent thin client and found this thread with the search feature.
I'm glad to see that it does, in fact, work. I was about to pitch the theory, but it seems you've not only arrived at the same theory, but have tried it yourself. +thanks for posting the results dude. Much appreciated. Hopefully this will lead to some kind of progress otherwise I'm just going to use an upgrade to get something else and sell my G4. I'm really getting tired of the total lack of ROMs. This isn't 2008 where only a couple carriers have Android phones and the developer base is tiny. What company thinks it's SMART to create only one model that can have the bootloader unlocked and then NOT make that model available on all carriers at the off-contract price?!

I'm guessing there is no way to edit the LK, and implement these changes to re enable fastboot commands without it throwing some type of error due to the fact of it not being signed? -
To selectively enable any fastbootcommand on user/production build, add the command as shown below:
File: bootable/bootloader/lk/app/aboot/aboot.c
Function: void aboot_fastboot_register_commands(void)
structfastboot_cmd_desccmd_list[] = {
/* By default the enabled list is empty. */
{““, NULL},
/* move commands enclosed within the below ifndefto here
* if they need to be enabled in user build.
*/
#ifndefDISABLE_FASTBOOT_CMDS
/* Register the following commands only for non-user builds */
{“flash:”, cmd_flash},
{“erase:”, cmd_erase},
{“boot”, cmd_boot},
{“continue”, cmd_continue},
{“reboot”, cmd_reboot},
{“reboot-bootloader”, cmd_reboot_bootloader},
{“oemunlock”, cmd_oem_unlock},
{“oemlock”, cmd_oem_lock},
{“oemverified”, cmd_oem_verified},
{“oemdevice-info”, cmd_oem_devinfo},
{“oemenable-charger-screen”, cmd_oem_enable_charger_screen},
{“oemdisable-charger-screen”, cmd_oem_disable_charger_screen},
{“oem-select-display-panel”, cmd_oem_select_display_panel},
#endif
};

Can we flash aboot of H811 to LS991 ?

Tctien342 said:
Can we flash aboot of H811 to LS991 ?
Click to expand...
Click to collapse
Nope i already asked that one

bump

TheMadScientist420 said:
bump
Click to expand...
Click to collapse
Any chance this will work? http://www.droidviews.com/unlock-bootloader-twrp-root-lg-v20/
When typed " id" in terminal i got similar results to what is shown in instructions.. Im on ls991zvf..

lowkeyst4tus said:
Any chance this will work? http://www.droidviews.com/unlock-bootloader-twrp-root-lg-v20/
When typed " id" in terminal i got similar results to what is shown in instructions.. Im on ls991zvf..
Click to expand...
Click to collapse
only prob is still oh never mind i do have a twrp lol i forgot kernals wouldnt be same we would need i thing the debug bootloader for ls991 which i actally read the other day on something trying to find us one.
in theory a debug or engineering bl should overite a qfuse in a way kinda thing device model specific but firmware versions usually dont matter or at least the few ive messed with on samsungs.
im in no way a dev but if someone could possibly mod one of the debug bls for us then yes may be possible because if im not mistaken the v20s are locked as tight as ours arent they`
---------- Post added at 04:19 PM ---------- Previous post was at 04:12 PM ----------
lowkeyst4tus said:
Any chance this will work? http://www.droidviews.com/unlock-bootloader-twrp-root-lg-v20/
When typed " id" in terminal i got similar results to what is shown in instructions.. Im on ls991zvf..
Click to expand...
Click to collapse
my g4 may be dying very soon i chucked it pretty hard the other day enough to crack the mother board near the noise cancelling mic and earpiece. destrotyed rear camera. bent the lcd and mother board in a bad kinda way . i might be down tonight to try it with v20s bootloader for the hell of it.
i had a spare lcd with a busted gorilla glass i put back on it lol 4 screen on my g4.
u gonna be around about 8 pm eastern time tonight ima dl most of the files now and when my kids goto bed we can try this with mine of coarse im not out anything if i hard brick and itll give me a reason to find a method to un hardbrick. i got alll thi .bins and firmware extractors if i need to make new boot images. i run cdma workshop qpst dfs all thge good old software i made my own ls991 .dll for old lg flashtool
plus my octobox came in finnaly with jtag
---------- Post added at 04:25 PM ---------- Previous post was at 04:19 PM ----------
im dling the v20 rom and going to attempt to rplace the system and stuff with my rooted zv6 system i got a couple ideas up my sleave on this one
---------- Post added at 04:29 PM ---------- Previous post was at 04:25 PM ----------
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
---------- Post added at 04:38 PM ---------- Previous post was at 04:29 PM ----------
screw it i aint got nothing goin on now im goin for it

TheMadScientist420 said:
only prob is still oh never mind i do have a twrp lol i forgot kernals wouldnt be same we would need i thing the debug bootloader for ls991 which i actally read the other day on something trying to find us one.
in theory a debug or engineering bl should overite a qfuse in a way kinda thing device model specific but firmware versions usually dont matter or at least the few ive messed with on samsungs.
im in no way a dev but if someone could possibly mod one of the debug bls for us then yes may be possible because if im not mistaken the v20s are locked as tight as ours arent they`
---------- Post added at 04:19 PM ---------- Previous post was at 04:12 PM ----------
my g4 may be dying very soon i chucked it pretty hard the other day enough to crack the mother board near the noise cancelling mic and earpiece. destrotyed rear camera. bent the lcd and mother board in a bad kinda way . i might be down tonight to try it with v20s bootloader for the hell of it.
i had a spare lcd with a busted gorilla glass i put back on it lol 4 screen on my g4.
u gonna be around about 8 pm eastern time tonight ima dl most of the files now and when my kids goto bed we can try this with mine of coarse im not out anything if i hard brick and itll give me a reason to find a method to un hardbrick. i got alll thi .bins and firmware extractors if i need to make new boot images. i run cdma workshop qpst dfs all thge good old software i made my own ls991 .dll for old lg flashtool
plus my octobox came in finnaly with jtag
---------- Post added at 04:25 PM ---------- Previous post was at 04:19 PM ----------
im dling the v20 rom and going to attempt to rplace the system and stuff with my rooted zv6 system i got a couple ideas up my sleave on this one
---------- Post added at 04:29 PM ---------- Previous post was at 04:25 PM ----------
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
---------- Post added at 04:38 PM ---------- Previous post was at 04:29 PM ----------
screw it i aint got nothing goin on now im goin for it
Click to expand...
Click to collapse
Yes i will be around.. I hope you have success.. I like the sprint variant for alot of reasons.. I think the octobox might do dumps to..

lowkeyst4tus said:
Yes i will be around.. I hope you have success.. I like the sprint variant for alot of reasons.. I think the octobox might do dumps to..
Click to expand...
Click to collapse
i think it does too
---------- Post added at 06:15 PM ---------- Previous post was at 05:50 PM ----------
gefiltefish1478 said:
I possibly found that the lg g4 can connect a serial console when in fast-boot and android with limited access, and that the boot-loader is based on little kernel
codeaurora.org/blogs/little-kernel-based-android-bootloader
It may be possible to connect uart via serial and map out how the bootrom loads the sbl and (aboot (bootloader))and possibly find a way to unlock the boot-loader
newandroidbook.com/Articles/aboot.html
so far acessing fastboot with a nuked laf partition only specific fastboot commands work. can not get oem-id or reboot/continue via fastboot
console=
/dev/tty
/dev/ttyHS0
/dev/ttyHSL0
/dev/ttyHSL1
Click to expand...
Click to collapse
Hey man u still around

I flashed one of the boot images on mine with. Twrp. And of coarse secure boot erroors so i have to restore and retwrp

TheMadScientist420 said:
I flashed one of the boot images on mine with. Twrp. And of coarse secure boot erroors so i have to restore and retwrp
Click to expand...
Click to collapse
Have you tried the octopus box bootloader unlock?

lowkeyst4tus said:
Have you tried the octopus box bootloader unlock?
Click to expand...
Click to collapse
no
i didnt even know it could

Yea after you mentioned you had one, i spent hours looking up what it can do.. It sim unlock, bootloader unlock, repair imei, hardbrick.. Who knows what else.. The cheapest one i found was $100..

lowkeyst4tus said:
Yea after you mentioned you had one, i spent hours looking up what it can do.. It sim unlock, bootloader unlock, repair imei, hardbrick.. Who knows what else.. The cheapest one i found was $100..
Click to expand...
Click to collapse
**** i spent 259. I got it for iemi repairs. And hard brick fix for g4 and a couple old htcs i have.

TheMadScientist420 said:
**** i spent 259. I got it for iemi repairs. And hard brick fix for g4 and a couple old htcs i have.
Click to expand...
Click to collapse
Im working on getting it.. Expensive but worth every penny.. As far as using it to unlock the bootloader, ive seen it done just by clicking the option in the software that should have came with it.. Ive seen it work with 3rd party jtaging software..
---------- Post added at 10:50 AM ---------- Previous post was at 10:19 AM ----------
Im gonna try calling Sprint today and asking for a bootloader unlock..
---------- Post added at 10:56 AM ---------- Previous post was at 10:50 AM ----------
TheMadScientist420 said:
**** i spent 259. I got it for iemi repairs. And hard brick fix for g4 and a couple old htcs i have.
Click to expand...
Click to collapse
Can this work via lg flash tool to convert say a ls991 to h811? Is there any special ools needed like octopus box?

I dont think we can cross flash to811. Ive tried askin that one may be possible with box but doibtfull
And sprint wont unlock bl. Only lg can. They would have to basicly give u the signature to sign ure own images. Unless they offer unlock when nougats released

TheMadScientist420 said:
I dont think we can cross flash to811. Ive tried askin that one may be possible with box but doibtfull
And sprint wont unlock bl. Only lg can. They would have to basicly give u the signature to sign ure own images. Unless they offer unlock when nougats released
Click to expand...
Click to collapse
http://forums.easy-firmware.com/showthread.php?9084-Convert-lg-tot

U gotta pay for the files. And thats the only site claims it can be done tht i see
---------- Post added at 11:43 AM ---------- Previous post was at 11:28 AM ----------
lowkeyst4tus said:
http://forums.easy-firmware.com/showthread.php?9084-Convert-lg-tot
Click to expand...
Click to collapse
Yea i signed up for that site a long time ago. And its a pay site. Cant find that tot any where else and not a garanty

TWRP - Need help downloading from Baidu

Can someone download this twrp and upload it to a mirror? It's for the Red Magic 3.
Password is: 6i3i
https://pan.baidu.com/s/1ZdMPjm2fEw...arentPath=/sharelink781715067-606770439204444

+6281281903288 contact me via whatsapp and i will share to you twrp file

tembokbesi said:
+6281281903288 contact me via whatsapp and i will share to you twrp file
Click to expand...
Click to collapse
OK at this point Ill try anything. I have my cell totally unlocked OEM an Bootloader an still have just a fastboot screen an little else no matter what I try and do.
I use whatsapp. Not sure how to add you or contact you through it?
The only thing i used it for was sending info to my boss
---------- Post added at 01:44 PM ---------- Previous post was at 01:43 PM ----------
Bryceicle1971 said:
OK at this point Ill try anything. I have my cell totally unlocked OEM an Bootloader an still have just a fastboot screen an little else no matter what I try and do.
I use whatsapp. Not sure how to add you or contact you through it?
The only thing i used it for was sending info to my boss
Click to expand...
Click to collapse
Edit: just found out how to add you

I already download twrp wait I share after some time

Any Twrp or EDL rom? Currently stuck in bootloop.

Flashing_locked

I'm having a problem with the bootloader, it is currently in "flashing_locked", I already tried to flash a rom stock, but the "flash permission denied", and the oem_unlocking is "connect to the internet or contact your carrier" but it does not work the operator chip and the Wi-Fi!
does anyone have a solution for this?
sorry for my flawed english

Coxinha2139 said:
I'm having a problem with the bootloader, it is currently in "flashing_locked", I already tried to flash a rom stock, but the "flash permission denied", and the oem_unlocking is "connect to the internet or contact your carrier" but it does not work the operator chip and the Wi-Fi!
does anyone have a solution for this?
sorry for my flawed english
Click to expand...
Click to collapse
Unlock the bootloader following
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my ali using XDA Labs

Coxinha2139 said:
I'm having a problem with the bootloader, it is currently in "flashing_locked", I already tried to flash a rom stock, but the "flash permission denied", and the oem_unlocking is "connect to the internet or contact your carrier" but it does not work the operator chip and the Wi-Fi!
does anyone have a solution for this?
sorry for my flawed english
Click to expand...
Click to collapse
I am in the same situation. Did you find a solution?
---------- Post added at 05:36 PM ---------- Previous post was at 05:34 PM ----------
it does not work

sd_shadow said:
Unlock the bootloader following
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
the "OEM unlocking" option is grayed out, I can't do anything

pepins said:
I am in the same situation. Did you find a solution?
---------- Post added at 05:36 PM ---------- Previous post was at 05:34 PM ----------
it does not work
Click to expand...
Click to collapse
good to know i'm not the only one

I keep looking for possible solutions, any solution will be shared here:good:

Some say a factory reset had helped them. Or try it with or without a SIM card.

thanks but the problem is not so simple
---------- Post added at 06:38 PM ---------- Previous post was at 06:33 PM ----------
the only possible solution is to provoke a hard brick in order to enter EDL mode. but how?

pepins said:
thanks but the problem is not so simple
---------- Post added at 06:38 PM ---------- Previous post was at 06:33 PM ----------
the only possible solution is to provoke a hard brick in order to enter EDL mode. but how?
Click to expand...
Click to collapse
I thought the same thing

Coxinha2139 said:
I thought the same thing
Click to expand...
Click to collapse
any progress?
i've been shutdown now, so have lots of time

digitaljeff said:
any progress?
i've been shutdown now, so have lots of time
Click to expand...
Click to collapse
still has no progress

I didn't recognize your wifi connection... Sorry!
Have you tried bluetooth-/USB-tethering to get online? You find it in same menu as wifi-hotspot settings.

WoKoschekk said:
I didn't recognize your wifi connection... Sorry!
Have you tried bluetooth-/USB-tethering to get online? You find it in same menu as wifi-hotspot settings.
Click to expand...
Click to collapse
I already tried, but it didn't work

https://support.google.com/pixelphone/forum/AAAAb4-OgUsst_UwpbjgNk/?hl=it

Lupask said:
https://support.google.com/pixelphone/forum/AAAAb4-OgUsst_UwpbjgNk/?hl=it
Click to expand...
Click to collapse
the problem I'm having is not that simple!

did anyone find any solution?

pepins said:
thanks but the problem is not so simple
---------- Post added at 06:38 PM ---------- Previous post was at 06:33 PM ----------
the only possible solution is to provoke a hard brick in order to enter EDL mode. but how?
Click to expand...
Click to collapse
have you tried
Code:
fastboot -i 0x2b4c oem ​​reboot-edl
or
Code:
adb reboot edl
i cant remember seeing if you had access to ADB and/or fastboot

digitaljeff said:
have you tried
Code:
fastboot -i 0x2b4c oem ​​reboot-edl
or
Code:
adb reboot edl
i cant remember seeing if you had access to ADB and/or fastboot
Click to expand...
Click to collapse
is in "<waiting device>", motorola drivers are updated

nothing works

Coxinha2139 said:
have you tried
or
is in "<waiting device>", motorola drivers are updated
Click to expand...
Click to collapse
Fastboot commands only work if d device is in fastboot mode
Adb commands only work when USB debugging is active (device is booted normally or custom recovery is booted)
Sent from my ali using XDA Labs