Develop Bugs

[Guide] How to recover your semi-brick

YES YOU NEED TO READ THIS WHOLE POST, PROB MORE THEN ONCE TO MAKE SURE YOU GOT IT. YES I KNOW HOW LONG IT IS, I TYPED IT!
*Also note that not all sections will apply to you. I have tried to seperate different senerios using * at each one. Also more then one section here may be needed by you.
the reason i call it a semi-brick is because a true brick can bot be recovered with out opening the case.
first go here and read this for info: http://forum.xda-developers.com/showthread.php?t=838484
now since your here im going to assume that its too late.
*things you will need.
copy of cwm recovery. get it here (the manual install link): http://forum.xda-developers.com/showpost.php?p=9145724&postcount=28
adb installed and working.
a known good rom, or nandroid backup. here is one: http://forum.xda-developers.com/showthread.php?t=836042 (use odex one)
a wpthis.ko for YOUR specfic kernel (run (adb shell cat /proc/version) that will tell you what kernel you have)
*first thing we need to know is, are you s-off or s-on now?
if your s-off just boot into clockwork mod recovery, wipe the phone and flash a known good rom and be done with it. if you dont have cwm recovery installed. boot into fastboot (vol down+power) you must have the sdk/adb installed and working, and type fastboot flash recovery LocationOfRecovery.img (where LocationOfRecovery.img= where you have the recovery, ie c:\android\recovery.img). once thats installed follow instructions above.
*if you are s-on:
will the phone boot into android? if so your not bad off.
if you want to unroot to return the phone, follow the unroot thread here: http://forum.xda-developers.com/showthread.php?t=835971
if you dont want to unroot then you have a couple of different options. if you have cwm recovery still installed, just follow instructions above and flash a known good rom. ive been told that boot.img (kernel) wont flash if you are s-on. the way to fix this (temporarily) is boot into recovery, but before you flash run these commands:
(put wpthis.ko in sdk folder)
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
then proceed to flash the rom. once booted into android skip down to, "now to get back to s-off"
*if you have stock or eng-recovery installed.
will the phone attempt to boot android at all? where is it stuck at?
a good min after it starts to try to boot, type these commands:
adb remount
adb shell
if you can get in shell then theres still hope. back out shell for a second and start here:
put the cwm recovery.img and wpthis.ko in your sdk folder
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb push recovery.img /data/local/recovery.img
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
# dd if=/data/local/recovery.img of=/dev/block/mmcblk0p21 (now wait a min or 2 to give it time to finish)
#sync (give it another min or to just to be safe)
#reboot recovery
at this point you should be in cwm recovery. follow instructions above for flashing with s-on.
*if you cannot get into shell while booting, but have eng-recovery installed, there might be some options.(however this is all theory)
boot into recovery-
if you are on linux using adb, you can try taking sh from /system/bin folder of any custom rom, chmod 0755 it, then push it to /system/bin and adb shell might work.
windows-
boot into recovery.
a system.img compatible with your installed kernel pushed may work. put the system.img into the sdk folder.
adb push system.img /data/block/mmcblk0p25
then reboot and see where you are. if that dont work, grab the modified miscnew.img here: http://www.4shared.com/file/pUPfrGi-/mmcblk0p17.html
rename it misc.img put it in sdk folder and
adb push misc.img /dev/block/mmcblk0p17
then reboot into bootloader with PC10IMG.zip on root of sdcard and it should run though. if it does your fully stock and get to start all over again.
*if you cannot get into shell, and you have stock recovery, s-on, and post OTA, im sorry your pretty screwed. as of right now the only thing thats gonna bring it back is a full img/update signed from htc thats equal to or higher then the version currently on the phone. (well and jtag of course)
*well now you've done one of the steps above. your booted into android, you have perm root, and cwm recovery installed, just still s-on. dont worry your almost there!
first take that wpthis.ko for you kernel and push it, and the eng hboot.
adb push wpthis.ko /data/local/
adb push hboot-eng.img /data/local
then from adb shell, or terminal root prompt:
# insmod /data/local/wpthis.ko (again you should get the function not implemented error)
NOW REMEMBER THIS NEXT STEP COULD MEAN DEATH FOR YOU G2 IF TYPED WRONG, AND AFTER ALL THIS HARD WORK!
# dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
wait a few mins to be sure its done.
# sync
wait a few more just cause.
reboot, you should now be s-off, cwm recovery installed, and free to do whatever you want. just dont go screwing it up again
* as new methods are discovered, or ones here are proven wrong, i will update as necessary. as of the writing post, 2 devices that i know of have been saved!
good luck!
wpthis.ko for bacon bits.03 kernel: http://www.4shared.com/file/OAcd1bix/wpthis-263221-cyanogenmod.html

before you post with problems make sure you have read this at least 2 times. have this info in you post:
what was the last running rom/kernel combo you had?
list EVERYTHING you have done since that point
which recovery is installed?
what happens in recovery when you type
adb devices?
adb remount?
adb shell?
does it try to boot? is it stuck on splash screen, or does it make it to boot animation? 1 min after you turn it on, what happens when you type:
adb devices?
adb remount?
adb shell?

Thank you, really, for taking the time to write this guide. I shared that dreadful feeling of a brick a little while ago, but made it out alive. I know this will help a lot of people.

I'm not bricked, semi bricked or none of that. Rootrd and running BB 0.3
This is the best guide to everything you would need. Too bad you can't post this at the beginning of every thread or some kind of link on every page. This would answer a lot of question if some people would look hard enough. I'm not some smart phone guy by no means. I just read a lot before I ask. In my further reading I can direct people.with further problems here.
Thanks for all your work and giving me another fun hobby
Peace
Sent from my T-Mobile G2 using XDA App

Question why is it that you have "dd if....../mmcblk0p21" in one area and towards the bottom you have "May brick phone ...dd if...../mmcblk0p18." Thought it should always be .../mmcblk0p18?
Phone: T-Mobile G2/Vision Rooted
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA

Good point . Not sure on that one
Sent from my T-Mobile G2 using XDA App

renn9420 said:
Question why is it that you have "dd if....../mmcblk0p21" in one area and towards the bottom you have "May brick phone ...dd if...../mmcblk0p18." Thought it should always be .../mmcblk0p18?
Phone: T-Mobile G2/Vision Rooted
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
Click to expand...
Click to collapse
if you look where im saying /mmcblk0p21 we are replacing RECOVERY with CWM. i do that because i just dont like the idea of trying to replace hboot from a looping system. worst case something goes wrong, you still have hboot and you can try again. screw up hboot, game over! then once android is back up and running we worry about hboot on mmcblk0p18.

you should not state that steps can be changed if people are brave, someone is going to sip parts and cry that their hboot is boned and now they have a BRICK, this is the best post i have seen in the G2 section thus far and i have been through almost every thread(with any kind of importance) in the dev section and 90% of them in general and Q&A. thank you for this post and let's hope people READ at least 5 times before even starting on this.

Gotcha
Phone: T-Mobile G2/Vision Rooted
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA

Amazing guide, thanks a lot.
fastludeh22 said:
the reason i call it a semi-brick is because a true brick can bot be recovered with out opening the case.
Click to expand...
Click to collapse
I have a full, honest-to-god brick in my drawer (executed dd if=/sdcard/hbooteng.img of=/dev/block/mmcblk0p18 with a wrong "hbooteng.img file).
I'm really, really interested in some guide or info about how to try and recover the brick. I don't mind if I have to open the case, there's not going down from where I am right now.
By the way, my second DZ just arrived, tomorrow I'll try to S-OFF it again... I will have nightmares tonight.

reycat said:
Amazing guide, thanks a lot.
I have a full, honest-to-god brick in my drawer (executed dd if=/sdcard/hbooteng.img of=/dev/block/mmcblk0p18 with a wrong "hbooteng.img file).
I'm really, really interested in some guide or info about how to try and recover the brick. I don't mind if I have to open the case, there's not going down from where I am right now.
By the way, my second DZ just arrived, tomorrow I'll try to S-OFF it again... I will have nightmares tonight.
Click to expand...
Click to collapse
Well it will take a jtag and a lot of research, since it hasn't been done to a g2 yet. Search g1 development forum dor debricking if u want an idea of what's involved.
I remember talking to gtrab a little about your problem. So did you use the wrong file, or did you type an address wrong? What file or typo was it exactly?
What happens when u try to boot into fastboot, or anything else?

{golf clap} on the post.
you sir, have incredible patience... and it's truly appreciated.

fastludeh22 said:
Well it will take a jtag and a lot of research, since it hasn't been done to a g2 yet. Search g1 development forum dor debricking if u want an idea of what's involved.
Click to expand...
Click to collapse
Mmm... It seems all of it is quite a bit over my head.
I remember talking to gtrab a little about your problem. So did you use the wrong file, or did you type an address wrong? What file or typo was it exactly?
What happens when u try to boot into fastboot, or anything else?
Click to expand...
Click to collapse
Don't ask me how I did it, but I actually downloaded a web page instead of the actual hboot file I should have used . I did it from the phone and didn't notice. Since I was supposed to rename it to make the typing easier, I didn't notice it was the wrong file.
Anyway, right now the phone is a complete brick. It doesn't respond to any button presses, the LED doesn't do anything when you plug in the charger... A complete brick.

Device offline?
fastludeh22 said:
before you post with problems make sure you have read this at least 2 times. have this info in you post:
what was the last running rom/kernel combo you had?
list EVERYTHING you have done since that point
which recovery is installed?
what happens in recovery when you type
adb devices?
adb remount?
adb shell?
does it try to boot? is it stuck on splash screen, or does it make it to boot animation? 1 min after you turn it on, what happens when you type:
adb devices?
adb remount?
adb shell?
Click to expand...
Click to collapse
Never used ADB before, followed [forum wont let me post outside links] to set it up. when typing adb devices while in recovery mode, get "list of devices attached
HT09PR204734
offline."
here is a screen shot : [forum wont let me post)
running windows 7 64bit...device not recognized by ADB at alll when stuck on splash screen....did some research couldnt find a real solution...soooo what do you recommend trying?

im stuck on the splash screen.. and i cant get adb to work either.. is missing a driver but i cant for the life of me find one ...

-FuRBz- said:
im stuck on the splash screen.. and i cant get adb to work either.. is missing a driver but i cant for the life of me find one ...
Click to expand...
Click to collapse
Download and instal PDANet, that gave me the drivers i needed for adb, now if only i could figure out how to get my device to register online through the ADB command interface.....

^^ you my friend are awesome! dl pdanet, was able to get the drivers.. was able to go into bootloader and did a recovery from there.. im up and running again!!

marley097 said:
Never used ADB before, followed [forum wont let me post outside links] to set it up. when typing adb devices while in recovery mode, get "list of devices attached
HT09PR204734
offline."
here is a screen shot : [forum wont let me post)
running windows 7 64bit...device not recognized by ADB at alll when stuck on splash screen....did some research couldnt find a real solution...soooo what do you recommend trying?
Click to expand...
Click to collapse
Sounds like you have stock recovery installed, with s-on and no adb/shell access, I'm sorry your pretty screwed. You can try factory reset and see if that helps boot, or to get adb access while trying to boot. Other then that, at the moment the only way to recover is a offical signed pc10img of version equal to or higher then what you have. I'm working hard to come up with something, ill keep you guys informed. I think u said in pm, you have already done the OTA, which makes you version number 1.22.something.
-FuRBz- said:
^^ you my friend are awesome! dl pdanet, was able to get the drivers.. was able to go into bootloader and did a recovery from there.. im up and running again!!
Click to expand...
Click to collapse
Glad you got it! After drivers installed, did you fix it per a section of the op?

it all happened because i had tried flashing cm 6.1- it got stuck on the splash screen but i had done a recovery prior to trying to flash... once i got the drivers installed i was able to get in to adb and do a reboot-bootloader and was able to get into the recovery file

fastludeh22 said:
Sounds like you have stock recovery installed, with s-on and no adb/shell access, I'm sorry your pretty screwed. You can try factory reset and see if that helps boot, or to get adb access while trying to boot. Other then that, at the moment the only way to recover is a offical signed pc10img of version equal to or higher then what you have. I'm working hard to come up with something, ill keep you guys informed. I think u said in pm, you have already done the OTA, which makes you version number 1.22.something.
Click to expand...
Click to collapse
Lame....so how often do they release official pic10img's....? are we talkin a month....or a year?

[GUIDE] Backing up a phone with broken display

I have seen several of threads asking about how to recover data from a phone that has a broken display.
Backing up a phone with broken display
Prerequisites
Rooted phone with broken display/digitizer/etc. Display is nonfunctional for whatever reason.
ADB for your platform. Downloads for Windows, Mac, and Linux can be found at my dev-host.
Drivers installed (Windows), rules file set up (Linux + Mac). Drivers for windows can be found here. Rules file for Linux can be found here.
Recovery file attached to this post. (twrp.img)
External sdcard with at least 2 GB free space inserted in your broken phone.
openrecoveryscript.txt file attached to this post.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Backing up your broken device
Extract the ADB zip somewhere convenient.
Move the twrp.img recovery file into the ADB extracted directory.
Move the openrecoveryscript.txt file into the ADB directory.
Open a command prompt / terminal window in the ADB directory.
Windows: Windows Key + R => Type in "cmd" then click "RUN".
Linux: Open a terminal window by selecting it from your applications.
ALL:
Code:
cd /path/to/ADB/directory
Pull the battery from your phone, place it back in and boot into recovery (VolUp + Home + Power).
Connect your phone to your computer
Make sure that the following command returns "XXXXXX recovery" before proceeding to the next step.
Code:
./adb devices
Expected output:
Code:
List of devices attached
XXXXXXX recovery
Now to install TWRP recovery to your device. Type the following commands ( after each line). Linux users: Make sure you prepend each command with "./", as in "./adb ...". ALL Make sure you type the commands in CAREFULLY.
Code:
adb push twrp.img /tmp/twrp.img
adb shell dd if=/tmp/twrp.img of=/dev/block/mmcblk0p18
Wait until the last command above returns an output similar to below before proceeding to the next step:
Code:
12916+0 records in
12916+0 records out
6612992 bytes (6.3MB) copied, 1.094278 seconds, 5.8MB/s
Now pull your phones battery and reboot into recovery once again.
Run the following command to make sure your phone has booted into recovery completely.
Code:
adb devices
Expected output
Code:
List of devices attached
XXXXXXX recovery
Type the following to set up a script that will backup your phone to your external sdcard.
Code:
adb push openrecoveryscript.txt /cache/recovery/openrecoveryscript
Reboot your phone once more. This time, TWRP will begin backing up your ROM.
Wait for the backup to finish. You will know it is finished when you feel your phone reboot once more.
Optionally, you can check the state of your backup by running the following command and reading the last couple lines of it's output.
Code:
adb shell cat /tmp/recovery.log
Click to expand...
Click to collapse
Click to expand...
Click to collapse
That's it! Your entire system (/system, /data, /cache, and boot) will be backed up to your external sdcard. Just pop the sdcard in your replacement phone and you're good to go.
Enjoy and donate to the TWRP devs! This would not be possible if TWRP did not use the OpenRecoveryScript scripting engine!

Or you can use skip's unified toolkit.
I literally just used it. Moving the backup to my new device right now.

loserskater said:
Or you can use skip's unified toolkit.
I literally just used it. Moving the backup to my new device right now.
Click to expand...
Click to collapse
Whatever floats your boat :good:

Sorry, had to
Sent from my SGH-I747 using Tapatalk 2

Actually, this process might directly meet my needs.
You mentioned that the recovery image and script were attached to the initial post, though I must be missing something in that I don't see where they might be. Perhaps you could offer a pointer, please?
- ooofest

Ah sorry, you can find the files here
http://forum.xda-developers.com/showthread.php?t=2353828
Don't use the twrp.img from there though...go to the twrp website and download the latest .img file for your phone (d2att)
Sent from my S3 on Sense 5 (you jelly?)

CNexus said:
Ah sorry, you can find the files here
http://forum.xda-developers.com/showthread.php?t=2353828
Don't use the twrp.img from there though...go to the twrp website and download the latest .img file for your phone (d2att)
Click to expand...
Click to collapse
Thanks - I downloaded the appropriate files, but wonder if this can be used on a stock phone.
That is, I was able to push twrp.img to /tmp/twrp.img, but cannot write in the next step:
Code:
adb shell dd if=/tmp/twrp.img of=/dev/block/mmcblk0p18
/dev/block/mmcblk0p18: cannot open for write: Permission denied
This is a stock AT&T phone, in recovery mode, never been rooted.
- ooofest

You need to be rooted for this to work.

CNexus said:
You need to be rooted for this to work.
Click to expand...
Click to collapse
Ya know . . . I need to read things more carefully. Was so excited to see something that might possibly help. Sorry about that.
It's been awhile since I looked into rooting the Galaxy S III and will look around, but don't recall that this can be rooted from recovery, unfortunately. And, it seems that USB Debugging is not turned on when it boots to the lockscreen.
Hm.
- ooofest

[Recovery][CWM][ATT-ONLY!] Flashable CWM recovery!

Hello everyone!
Here's another release thread for y'all!
What is this?
This is a flashable ClockworkMod recovery for the Optimus G Pro.
Special thanks to @djrbliss
You can safely flash this to your phone's recovery and enjoy modding bliss!​
How do I use this, and where do I get it?
Good question!
There are two ways to use the files provided here.
To Flash to Recovery:
Download this file to somewhere on your computer https://github.com/djrbliss/loki/raw/master/bin/loki_flash
Download this file http://downloads.codefi.re/thecubed/lgoptimusg_pro/gkatt/recovery/e98010g/gkatt-cwm-e98010g.lok
Run the following:
Code:
adb push loki_flash /data/local/tmp
adb push gkatt-cwm-e98010g.lok /data/local/tmp
abd shell
su
cd /data/local/tmp
chmod 755 loki_flash
./loki_flash recovery gkatt-cwm-e98010g.lok
To boot
Download this file: http://downloads.codefi.re/thecubed/lgoptimusg_pro/gkatt/recovery/e98010g/gkatt-cwm-e98010g.img
Use fastboot boot to boot it
DO NOT FLASH THE .IMG FILE TO YOUR PHONE. It is only meant for fastboot booting.​
Where can I find the source you used to build this?
All on my github!
http://github.com/thecubed/
Or, follow my guide here:
http://forum.xda-developers.com/showthread.php?p=43514195​
What can I do with this?
Right now, the possibilities are unlimited. Once a security-lax boot.img is released, we can flash that through recovery and let the modding commence.
Please remember though, modding /system with the stock boot.img will result in a security error!​
What works, and what doesnt?
I have so far tested making backup images, however I haven't tested restoring them.
I have also not tested external SD cards, since I don't have one with me at work.​
Can you show me a video?
Why yes I can!
As usual, please pardon the crappy camera work.​
I <3 you so much, how do I show my love?
You are so kind
I most definitely do not expect donations of any kind, however they are appreciated a lot.
I purchased this phone off-contract just to get it unlocked, if you are a kind soul and would like to send me a token of your appreciation I would love you forever.
XDA has a neat "Donate to me" button that should be on the left side of this page under my name. Donations go to purchasing new hardware to work on and other neat stuff, so they're always appreciated.​
Special Thanks!
In no particular order, special thanks to all of you guys!
djrbliss
synergy
Shelnutt2
DeamonFish
If I forgot anyone, let me know and I'll add you here!
​
Alright guys! Let me know if you find any bugs!

Can I flash this threw dd?
Sent from my LG-E980 using xda premium

Gotroot said:
Can I flash this threw dd?
Sent from my LG-E980 using xda premium
Click to expand...
Click to collapse
We could just run Loki flash from terminal and flash that way if no adb as for the second Part we'd need fastboot on our computer
Sent from my LG-E980 using xda premium

This is some serious progress! :thumbup::thumbup:
Sent from my LG-E980 using Tapatalk 2

Btw cube external sd does work !!!
Sent from my LG-E980 using xda premium

Gotroot said:
Can I flash this threw dd?
Sent from my LG-E980 using xda premium
Click to expand...
Click to collapse
Yes you can, just do the following:
Code:
adb push gkatt-cwm-e98010g.lok /data/local/tmp
adb shell
su
dd if=/data/local/tmp/gkatt-cwm-e98010g.lok of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Getting into recovery is as simple as "adb reboot recovery" or holding the proper volume keys.
I just recommend using Dan's excellent loki_flash utility since it checks to make sure you have the right bootloader in place already.

fastboot info
Would be nice to have more info on how to use fastboot with the .img file. I tried all I know with no results. Thanks!

G0bl1n said:
Would be nice to have more info on how to use fastboot with the .img file. I tried all I know with no results. Thanks!
Click to expand...
Click to collapse
Not sure what you're asking. To flash any .img file without any modifications requires our bootloader to be unlocked. What's going on here is everything needs to be "Loki'ed" so our phones are able to flash unsigned code through a custom recovery, bypassing our locked bootloader.
Fastboot is a way of testing unsigned code without having to necessarily flash it to any partitions.
Anyone correct me if I'm wrong, as I'm definitely not a developer. I just read a lot lol

thecubed said:
Hello everyone!
Here's another release thread for y'all!
What is this?
This is a flashable ClockworkMod recovery for the Optimus G Pro.
Special thanks to @djrbliss
You can safely flash this to your phone's recovery and enjoy modding bliss!​
How do I use this, and where do I get it?
Good question!
There are two ways to use the files provided here.
To Flash to Recovery:
Download this file to somewhere on your computer https://github.com/djrbliss/loki/raw/master/bin/loki_flash
Download this file http://downloads.codefi.re/thecubed/lgoptimusg_pro/gkatt/recovery/e98010g/gkatt-cwm-e98010g.lok
Run the following:
Code:
adb push loki_flash /data/local/tmp
adb push gkatt-cwm-e98010g.lok /data/local/tmp
abd shell
su
cd /data/local/tmp
chmod 755 loki_flash
./loki_flash recovery gkatt-cwm-e98010g.lok
To boot
Download this file: http://downloads.codefi.re/thecubed/lgoptimusg_pro/gkatt/recovery/e98010g/gkatt-cwm-e98010g.img
Use fastboot boot to boot it
DO NOT FLASH THE .IMG FILE TO YOUR PHONE. It is only meant for fastboot booting.​
What can I do with this?
Right now, the possibilities are unlimited. Once a security-lax boot.img is released, we can flash that through recovery and let the modding commence.
Please remember though, modding /system with the stock boot.img will result in a security error!​
What works, and what doesnt?
I have so far tested making backup images, however I haven't tested restoring them.
I have also not tested external SD cards, since I don't have one with me at work.​
Can you show me a video?
Why yes I can!
As usual, please pardon the crappy camera work.​
I <3 you so much, how do I show my love?
You are so kind
I most definitely do not expect donations of any kind, however they are appreciated a lot.
I purchased this phone off-contract just to get it unlocked, if you are a kind soul and would like to send me a token of your appreciation I would love you forever.
XDA has a neat "Donate to me" button that should be on the left side of this page under my name. Donations go to purchasing new hardware to work on and other neat stuff, so they're always appreciated.​
Special Thanks!
In no particular order, special thanks to all of you guys!
djrbliss
synergy
Shelnutt2
DeamonFish
If I forgot anyone, let me know and I'll add you here!
​
Alright guys! Let me know if you find any bugs!
Click to expand...
Click to collapse
If I have the old ClockworkMod, can I still do this or do I have to get rid of it somehow?

Are there any special precautions someone should take if they have this recovery already flashed to our phones?

Flashing with the latest "loki_flash" from dan's repos is segfaulting here and I'm too lazy to run it in gdb. The recovery works just fine with dd after zeroing the recovery partition out. Thanks mucho :good:

Coming from the Note I'm not use to locked bootloader.
Should we all install this if our goal is to eventually flash custom roms?

Yoreo said:
Are there any special precautions someone should take if they have this recovery already flashed to our phones?
Click to expand...
Click to collapse
Had that recovery and I had one of the first cwm Loki recoveries flashed this one just fine no issues
Sent from my LG-E980 using xda premium

acejoker25000 said:
Had that recovery and I had one of the first cwm Loki recoveries flashed this one just fine no issues
Sent from my LG-E980 using xda premium
Click to expand...
Click to collapse
Sounds good. Thanks.

madmack said:
Flashing with the latest "loki_flash" from dan's repos is segfaulting here and I'm too lazy to run it in gdb. The recovery works just fine with dd after zeroing the recovery partition out. Thanks mucho :good:
Click to expand...
Click to collapse
did the gdb backtrace:
Code:
Program received signal SIGSEGV, Segmentation fault.
0x4016ffa0 in memcmp () from /home/madmack/tmp/gdb/libs/libc.so
(gdb) bt
#0 0x4016ffa0 in memcmp () from /home/madmack/tmp/gdb/libs/libc.so
#1 0x00008868 in main ()
(gdb) bt
#0 0x4016ffa0 in memcmp () from /home/madmack/tmp/gdb/libs/libc.so
#1 0x00008868 in main ()
(gdb) quit
One of the memcmp commands is segfaulting. Perhaps @djrbliss can have a look when he gets some free time.

madmack said:
Flashing with the latest "loki_flash" from dan's repos is segfaulting here and I'm too lazy to run it in gdb. The recovery works just fine with dd after zeroing the recovery partition out. Thanks mucho :good:
Click to expand...
Click to collapse
what do you mean?
need zeroing the recovery partition before using dd to flash recovery image?
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/data/local/tmp/gkatt-cwm-e98010g.lok of=/dev/block/platform/msm_sdcc.1/by-name/recovery
GREAT.... I can using this to "adb reboot recovery" with CWM recovery on my E988 HK version ^^
so what is next, how to try boot my custom boot kernel ???

Timisone said:
If I have the old ClockworkMod, can I still do this or do I have to get rid of it somehow?
Click to expand...
Click to collapse
I have a few a questions. When do I run the commands? Command prompt in windows? What mode does my phone need to be in to flash this?

hkfriends said:
what do you mean?
need zeroing the recovery partition before using dd to flash recovery image?
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/gkatt-cwm-e98010g.lok of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Click to expand...
Click to collapse
It's just an extra step I like taking before flashing a partition with data that might be smaller than the original. And yes, that's pretty much what I typed.

madmack said:
It's just an extra step I like taking before flashing a partition with data that might be smaller than the original. And yes, that's pretty much what I typed.
Click to expand...
Click to collapse
another issue:
I am using loki_patch v1.5 to patch my custom build kernel
then I flash this Loki'ed kernel to my E988 (by CWM recovery) and it keep re-boot loop
(with the wording => Cause: Device Unlock, so boot success!!....) ==> it is the same Ok msg with boot to CWM recovery
which I believe if boot image LOKI'ed should be good
PS: I fixed this by re-flash the good boot image by CWM
Here is the output of the patching msg
[email protected]:/usr/android# ./loki_patch-linux-x86_64 boot aboot.img myboot.img myboot.lok
[+] loki_patch v1.5
[+] Detected target AT&T or HK LG Optimus G Pro build E98010g or E98810b
[+] Output file written to myboot.lok
[email protected]:/usr/android#

call me lazy, is there a zip file I could flash to do this from within the 2nd init recovery? :fingers-crossed:
I have never used adb before...

[q] SOLVED: ADB ROM PUSH ERROR: DEVICE NOT FOUND

EDIT:
I was trying to reflash JB 4.3 because of storage issues but unfortunately I accidentally deleted and formatted internal and sd storage, so Im left with no OS on my Gnex but I can boot on recovery and fastboot. Also before I deleted the internal I did not enable usb debugging yet at that time. Is there a way I can flash a stock image by just using toolkit? ty
I tried pushing through fastboot mode but it says error: device not found. I only have the platform tools on my pc.
UPDATE:
Finally got the file pushed into the sd card doing via recovery. Since I am using TWRP recevery it was not too obvious how to do it unlike CWRM which I used to use. I spent more than 24 hours looking for the right solution that would work for me and funny thing was I finally got the right way to one of the first threads i looked into but just didnt pay much attention to it which was here http://forum.xda-developers.com/showthread.php?t=1667929
"Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)"
lastforone said:
Instead of using a toolkit, just push a rom to ur sdcard using adb and flash it via recovery.. Or you can download the official image, boot into fastboot and flash it..
-
L4.1
Click to expand...
Click to collapse
You were right on spot unfortunately I didnt know how to do it. Thank you anyways...:highfive::highfive::highfive:
Ty for all those who tried to help me, thank you for the effort, well it was indeed a learning experience... ahihihihi

Instead of using a toolkit, just push a rom to ur sdcard using adb and flash it via recovery.. Or you can download the official image, boot into fastboot and flash it..
-
L4.1

lastforone said:
Instead of using a toolkit, just push a file to ur sdcard using adb and flash it... Or you can download the official image, boot into fastboot and flash it..
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
well then i need to download sdk first ty anyways

lolobabes said:
well then i need to download sdk first ty anyways
Click to expand...
Click to collapse
You do not need the whole sdk package. Just the adb + fastboot and few required files ... You can find the zip in erants guide..
Sent from my Galaxy Nexus using xda app-developers app

when i tried to push error device not found lol

lolobabes said:
when i tried to push error device not found lol
Click to expand...
Click to collapse
Use adb sideload from twrp and send the zip from your PC to your phone.
Sent from my Galaxy Nexus using xda app-developers app

lolobabes said:
when i tried to push error device not found lol
Click to expand...
Click to collapse
Go into your device manager if you have windows, and see if you have any errors.
If you do, you might have an exclamation mark for the device: Galaxy. You can manually install the drivers from here, point it to your toolkit, I guess, since you downloaded it already.

If he reads efrant's "android 101" -which is STICKIED ON GENERAL forum- just the first post, he'll know everything and downloaded everything he needs to know and have to interact with his device.
a manta wrote this.

Beauenheim said:
Go into your device manager if you have windows, and see if you have any errors.
If you do, you might have an exclamation mark for the device: Galaxy. You can manually install the drivers from here, point it to your toolkit, I guess, since you downloaded it already.
Click to expand...
Click to collapse
When I am on recovery yes theres an exclamation on samsung mtp device but in fastboot mode the samsung mtp does not appear but when I do fastboot devices there appears a device number so I thought I can do it on fastboot. thank you.
beekay201 said:
If he reads efrant's "android 101" -which is STICKIED ON GENERAL forum- just the first post, he'll know everything and downloaded everything he needs to know and have to interact with his device.
a manta wrote this.
Click to expand...
Click to collapse
I have read that already however I was hoping to just flash a file to the sdcard if is even possible considering I have formatted both internal and sdcard. I am very new to adb so its an easier way for me. But it seems then I will ave to do it the hard way. Thanks
PS
Not sure if this has any bearing but when I accidentally formated internal and sdcard it was a fresh 4.3 install and so android debugging was not enabled. Thanks

lolobabes said:
PS
Not sure if this has any bearing but when I accidentally formated internal and sdcard it was a fresh 4.3 install and so android debugging was not enabled. Thanks
Click to expand...
Click to collapse
Doesn't matter because if you reboot in bootloader you can use fastboot(if drivers are installed properly), fastboot always works, you don't need to enable anything for it.

sui785 said:
Doesn't matter because if you reboot in bootloader you can use fastboot(if drivers are installed properly), fastboot always works, you don't need to enable anything for it.
Click to expand...
Click to collapse
So meaning I can use fastboot to just push file to sdcard right? Tried to look for the right command but I cant seem to find the right one that works for me. Thank you.

tried doing this in fastboot "adb push romname.zip /sdcard/ROM/" had this error: device not found

lolobabes said:
tried doing this in fastboot "adb push romname.zip /sdcard/ROM/" had this error: device not found
Click to expand...
Click to collapse
Take it out of a USB 3.0 port.

lolobabes said:
tried doing this in fastboot "adb push romname.zip /sdcard/ROM/" had this error: device not found
Click to expand...
Click to collapse
lolobabes said:
So meaning I can use fastboot to just push file to sdcard right? Tried to look for the right command but I cant seem to find the right one that works for me. Thank you.
Click to expand...
Click to collapse
no, there's no ADB interface on FASTBOOT interface. You'll never be able to push anything through ADB in FASTBOOT interface. Please read the thread i talked about earlier, and this one too -> http://forum.xda-developers.com/showthread.php?t=1626895 - Just the first post of each will do.
Beauenheim said:
Take it out of a USB 3.0 port.
Click to expand...
Click to collapse
*EPIC*
*facedesk*
*grows more white hair*

xD I actually had this issue a few days ago, had issues for 4 hours, realized I had my cord plugged in a 3.0 port.
Really dumb noob moment.

UPDATE:
Finally got the file pushed into the sd card doing via recovery. Since I am using TWRP recevery it was not too obvious how to do it unlike CWRM which I used to use. I spent more than 24 hours looking for the right solution that would work for me and funny thing was I finally got the right way to one of the first threads i looked into but just didnt pay much attention to it which was here http://forum.xda-developers.com/showthread.php?t=1667929
"Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)"
lastforone said:
Instead of using a toolkit, just push a rom to ur sdcard using adb and flash it via recovery.. Or you can download the official image, boot into fastboot and flash it..
-
L4.1
Click to expand...
Click to collapse
You were right on spot unfortunately I didnt know how to do it. Thank you anyways...:highfive::highfive::highfive:
Ty for all those who tried to help me, thank you for the effort, well it was indeed a learning experience... ahihihihi

lolobabes said:
UPDATE:
Finally got the file pushed into the sd card doing via recovery. Since I am using TWRP recevery it was not too obvious how to do it unlike CWRM which I used to use. I spent more than 24 hours looking for the right solution that would work for me and funny thing was I finally got the right way to one of the first threads i looked into but just didnt pay much attention to it which was here http://forum.xda-developers.com/showthread.php?t=1667929
"Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)"
You were right on spot unfortunately I didnt know how to do it. Thank you anyways...:highfive::highfive::highfive:
Ty for all those who tried to help me, thank you for the effort, well it was indeed a learning experience... ahihihihi
Click to expand...
Click to collapse
I'm glad you sorted it out, that's the thing instead of teaching you step by step just left a hint on what you should do, helps you learn to do it on your own..
Peace,
L4.1

Thanks
Thanks for this. Was stuck with no factory image because had to wipe data because of encryption. Then was in dilemma of how to load the ZIP to sdcard without having to reflash the stock all over. This saved me the time. Thanks again

[TWRP][BL LOCKED][TEST][RootNeed] Twrp for Lg g4 with the BL locked, untested

I whipped up something quick based of stuff I used to do with the Droid X and what the Sony SP guys did.
This is twrp with a locked bootloader, the recovery partition is untouched, you can still get into that recovery. When the phone is booting, a green light will come on, hit volume up and then phone should vibrate within 3 seconds. If you hit the volume up then it should start loading twrp, otherwise it should continue with booting.
This is untested and I have a feeling the system will either not boot recovery, or not boot the main system.
This needs root.
This installs busybox, i know i should be using toybox
Someone please test, just extract the zip to your computer, plug in your phone, and run the appropriate file.
Do not test, I've tested it and I need to make changes
Sorry I was busy creating a new root method, got it working, almost done

Aaahh said:
I whipped up something quick based of stuff I used to do with the Droid X and what the Sony SP guys did.
This is twrp with a locked bootloader, the recovery partition is untouched, you can still get into that recovery. When the phone is booting, a green light will come on, hit volume up and then phone should vibrate within 3 seconds. If you hit the volume up then it should start loading twrp, otherwise it should continue with booting.
This is untested and I have a feeling the system will either not boot recovery, or not boot the main system.
This needs root.
This installs busybox, i know i should be using toybox
Someone please test, just extract the zip to your computer, plug in your phone, and run the appropriate file.
Click to expand...
Click to collapse
I need root to install it? Because marshmallow its unrootable

ericperez380 said:
I need root to install it? Because marshmallow its unrootable
Click to expand...
Click to collapse
Yup, in the future I might be able to make a marshmallow zip that'll let you run marshmallow with root and twrp. For that I need to relook into kernel modules because the kernel would have to be reloaded.

Aaahh said:
Yup, in the future I might be able to make a marshmallow zip that'll let you run marshmallow with root and twrp. For that I need to relook into kernel modules because the kernel would have to be reloaded.
Click to expand...
Click to collapse
Damn man you're a beast in does things good job doing this TWRP for locked bl, I'll be waiting till some feedback about this working

ericperez380 said:
Damn man you're a beast in does things good job doing this TWRP for locked bl, I'll be waiting till some feedback about this working
Click to expand...
Click to collapse
Yeah this opens the avenue for custom roms too, and multiboot and tons of stuff. Also, do not flash this if you are encrypted.

Aaahh said:
Yeah this opens the avenue for custom roms too, and multiboot and tons of stuff. Also, do not flash this if you are encrypted.
Click to expand...
Click to collapse
What you mean about encrypted, I don't know what's that

ericperez380 said:
What you mean about encrypted, I don't know what's that
Click to expand...
Click to collapse
If you encrypted your device. If you did you know.

Aaahh said:
If you encrypted your device. If you did you know.
Click to expand...
Click to collapse
No I don't encrypted it

Im at work.. Will Try to test it at home.
In between im bit confused how to flash this

Hopefully this will allow for us to write the drivers that would allow us to unlock the band's that are locked. If this allows us to write drivers.

So, just extract and run install.bat? On normal mtp mount?

Aaahh said:
I whipped up something quick based of stuff I used to do with the Droid X and what the Sony SP guys did.
This is twrp with a locked bootloader, the recovery partition is untouched, you can still get into that recovery. When the phone is booting, a green light will come on, hit volume up and then phone should vibrate within 3 seconds. If you hit the volume up then it should start loading twrp, otherwise it should continue with booting.
This is untested and I have a feeling the system will either not boot recovery, or not boot the main system.
This needs root.
This installs busybox, i know i should be using toybox
Someone please test, just extract the zip to your computer, plug in your phone, and run the appropriate file.
Click to expand...
Click to collapse
does it work with (vs986) version model

I'm interested to see if this works for the Canadian model (H812). Will keep watching this thread so good luck!

So the hope here is that we could downgrade to L, root, and then run this to get TWRP and install custom roms all without touching the recovery partition?
Has anyone had a chance to test this? I have a VS986 but it's the only phone I have with me right now so I'm hesitant to try myself

recharged20 said:
So, just extract and run install.bat? On normal mtp mount?
Click to expand...
Click to collapse
Yeah uses adb
ANDROID2468 said:
does it work with (vs986) version model
Click to expand...
Click to collapse
It should work with all G4s, exception might be T-Mobile
ReeS86 said:
I'm interested to see if this works for the Canadian model (H812). Will keep watching this thread so good luck!
Click to expand...
Click to collapse
Yeah it should, in fact it may work on yours but not the Verizon because I used the twrp from the international. Easy fix tho if that's the caw
Wumbonaut said:
So the hope here is that we could downgrade to L, root, and then run this to get TWRP and install custom roms all without touching the recovery partition?
Has anyone had a chance to test this? I have a VS986 but it's the only phone I have with me right now so I'm hesitant to try myself
Click to expand...
Click to collapse
Yeah I'm in the same predicament.

coolguy71261 said:
Hopefully this will allow for us to write the drivers that would allow us to unlock the band's that are locked. If this allows us to write drivers.
Click to expand...
Click to collapse
No that probably won't be as the drivers are probably locked at bootloader level not system

Wait. I'm confused.
Q: does it work with (vs986) version model
A: It should work with all G4s, exception might be T-Mobile
Q: I'm interested to see if this works for the Canadian model (H812). Will keep watching this thread so good luck!
A: Yeah it should, in fact it may work on yours but not the Verizon because....
Soooo - it should work with the verizon G4 or it shouldn't?

Aaahh said:
I whipped up something quick based of stuff I used to do with the Droid X and what the Sony SP guys did.
This is twrp with a locked bootloader, the recovery partition is untouched, you can still get into that recovery. When the phone is booting, a green light will come on, hit volume up and then phone should vibrate within 3 seconds. If you hit the volume up then it should start loading twrp, otherwise it should continue with booting.
This is untested and I have a feeling the system will either not boot recovery, or not boot the main system.
This needs root.
This installs busybox, i know i should be using toybox
Someone please test, just extract the zip to your computer, plug in your phone, and run the appropriate file.
Click to expand...
Click to collapse
I ran this with a Verizon G4 and it doesn't appear to work. I don't get a green light when I boot up nor does pressing the Vol Up button at any point during boot up appear to have any affect. Perhaps I'm missing something in order to get into TWRP but from what I can tell it does not work.
One other note, the batch file for the windows installation needs to be edited: In this section PUSH needs to be changed to INSTALL. Not sure it matters if it doesn't work overall but wanted to let the you know.
USH <------- Should be INSTALL
 @ECHO Let's go!
 @adb\adb kill-server
 @adb\adb wait-for-device
 @adb\adb push common\logwrapper /data/local/tmp/
 @adb\adb push common\twrp.cpio.gz /data/local/tmp/
 @adb\adb push common\busybox /data/local/tmp/
 @adb\adb push common\step1.sh /data/local/tmp/
 @adb\adb shell chmod 755 /data/local/tmp/step1.sh
 @adb\adb shell su -c "mount -o remount,rw /system"
 @adb\adb shell su -c /data/local/tmp/step1.sh
 @adb\adb shell rm /data/local/tmp/step1.sh
 @pause
 @goto MENU

shmoode1 said:
I ran this with a Verizon G4 and it doesn't appear to work. I don't get a green light when I boot up nor does pressing the Vol Up button at any point during boot up appear to have any affect. Perhaps I'm missing something in order to get into TWRP but from what I can tell it does not work.
One other note, the batch file for the windows installation needs to be edited: In this section PUSH needs to be changed to INSTALL. Not sure it matters if it doesn't work overall but wanted to let the you know.
USH <------- Should be INSTALL
@ECHO Let's go!
@adb\adb kill-server
@adb\adb wait-for-device
@adb\adb push common\logwrapper /data/local/tmp/
@adb\adb push common\twrp.cpio.gz /data/local/tmp/
@adb\adb push common\busybox /data/local/tmp/
@adb\adb push common\step1.sh /data/local/tmp/
@adb\adb shell chmod 755 /data/local/tmp/step1.sh
@adb\adb shell su -c "mount -o remount,rw /system"
@adb\adb shell su -c /data/local/tmp/step1.sh
@adb\adb shell rm /data/local/tmp/step1.sh
@pause
@goto MENU
Click to expand...
Click to collapse
It should not be install it should be push.
Did you use install or push
Does your phone still boot?
I had to guess the led paths so they may be wrong
It made a log, I'll send you the path of it on your phone so you can send it to me

Aaahh said:
It should not be install it should be push.
Did you use install or push
Does your phone still boot?
I had to guess the led paths so they may be wrong
It made a log, I'll send you the path of it on your phone so you can send it to me
Click to expand...
Click to collapse
I used install, otherwise when I tried to install it, Option 1, the CMD window just closed. When I changed it to Install it ran and showed TWRP Successfully installed.
Yes it still boots.
Let me know the path, I'll send the log file.