Related
I hacked on redbend_ua to make it a better phone hacking tool
first thing that has to go was the rebooting after any command
and the second thing was the stupid installing software splash screens
the first mod will probably segfault if used to batch install delta files
as I suspect there is some more code to update the progress bar on
the now NOP'ed installing software splash screen.
the second mod has batch mode NOP'ed so it wont do anything unless
you pass the dump,restore or compare commands which is fine for scripting
zImage and modem.bin installs.
/* This program is free software. It comes without any warranty, to
* the extent permitted by applicable law. You can redistribute it
* and/or modify it under the terms of the Do What The **** You Want
* To Public License, Version 2, as published by Sam Hocevar. See
* http://sam.zoy.org/wtfpl/COPYING for more details. */
Click to expand...
Click to collapse
Nice thanks
Sent from my vibrant
untermensch said:
I hacked on redbend_ua to make it a better phone hacking tool
first thing that has to go was the rebooting after any command
and the second thing was the stupid installing software splash screens
the first mod will probably segfault if used to batch install delta files
as I suspect there is some more code to update the progress bar on
the now NOP'ed installing software splash screen.
the second mod has batch mode NOP'ed so it wont do anything unless
you pass the dump,restore or compare commands which is fine for scripting
zImage and modem.bin installs.
Click to expand...
Click to collapse
sorry if this is dead info but how is this a tool? i need as many tools as possible. and i do not understand is there a place for specific knowledge on this that may go into a bit more detail?
justlovejoy said:
sorry if this is dead info but how is this a tool? i need as many tools as possible. and i do not understand is there a place for specific knowledge on this that may go into a bit more detail?
Click to expand...
Click to collapse
redbend_ua is used for installing OTA updates, but it also has other functions.
RedBend Update Agent %s
commands:
img [partition name] [delta file] [device node] [temp path]
fs [partition name] [delta file] [mount point] [temp path]
all
dump <source dev> <dest file>
restore <source file> <dest dev>
compare <dev1> <dev2>
png [png file name]
all
Click to expand...
Click to collapse
normally when you run a command it will take over the screen with a "Installing Software"
splash, and then reboot. you can get around the reboot by unlinking reboot but that is kinda
a kludge and the splash usually just scrambles the screen.
the mod does away with the splash and the reboot making redbend_ua less annoying to use.
you could even probably install kernels and modems without rebooting into recovery, though
you will have to reboot to use the new code.
for example if you want to install a kernel the command might look something like this
Code:
/data/local/redbend_ua restore /sdcard/zImage /dev/block/bml7
So I'm bumping this because tbh I was a little surprised to see it die out. I was expecting more to come out of it. I imagine you could potentially create an app to flash kernels and modems and then you just reboot for it to take effect. Might be worth looking into...
Edit: I'm going to look into it. I feel this would be extremely convenient for multiple reasons.
Whitehawkx said:
So I'm bumping this because tbh I was a little surprised to see it die out. I was expecting more to come out of it. I imagine you could potentially create an app to flash kernels and modems and then you just reboot for it to take effect. Might be worth looking into...
Edit: I'm going to look into it. I feel this would be extremely convenient for multiple reasons.
Click to expand...
Click to collapse
Whitehawk, dude, kick some butt doing this! It would be very convenient
Sent from the helm of Vibrant Territory!
Whitehawkx said:
So I'm bumping this because tbh I was a little surprised to see it die out. I was expecting more to come out of it. I imagine you could potentially create an app to flash kernels and modems and then you just reboot for it to take effect. Might be worth looking into...
Edit: I'm going to look into it. I feel this would be extremely convenient for multiple reasons.
Click to expand...
Click to collapse
Guess what i already did: SGS kernel flasher
Btw: Thanks untermensch.
neldar said:
Guess what i already did: SGS kernel flasher
Btw: Thanks untermensch.
Click to expand...
Click to collapse
I saw that and briefly hacked into it to pack it with vibrant kernels - gave it 1 try which failed and I moved on because I assume you have a check in place that didnt let me replace the kernel. Like to see this for us though.
Edit - reading your signature, I must have been working from an early or I9000 version at the time.
Thanks to Trekfan422991 for cluing me in on the Optimus 3D recovery.
Working:
Nandroid
ADB (after special driver install, need to tweak recovery for it to work with normal drivers)
Mounting USB to computer
Flashing zip files
Dangerous:
Fix Permissions (caused lots of crazy issues, fix by wiping data if you use it)
Sdparted (the sdcards are mount incorrectly, this will probably destroy your device)
I am in the process of making a recovery specifically for our device, it is mostly done and will be posted here when it is ready!
What you are going to need:
ADB (and know how to use it, don't ask in here)
Rooted Phone (again, that will not be covered, don't ask in here)
Optimus 3D recovery image [Download]
If you don't understand something in that list, DO A SEARCH AND LEARN, don't clutter the thread with crap!
Lets get started!
Lets start by getting the recovery.img file on the phone. Open up a cmd prompt and type:
Code:
adb push recovery.img /data
The rest of this will be done on the phone shell. In the cmd prompt type:
Code:
adb shell
We will need to have su access, In the cmd prompt type:
(If you haven't allowed shell su in SuperUser now would be a good time to accept the root request on the phone.)
Code:
su
Now we are going to backup your current recovery to your sdcard. In the cmd prompt type:
(make sure your sdcard is not mounted to your computer)
Code:
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
After that is done we are going to flash ClockWorkMod Recovery! In the cmd prompt type:
Code:
dd if=/data/recovery.img of=/dev/block/mmcblk0p6 bs=4096
Congrats! You now have ClockWorkMod Recovery! In the cmd prompt type:
(each line is single command)
Code:
rm /data/recovery.img
reboot
How to enable ADB access: (only if it's not working already)
Download and install: (unzip and install the 2 exe files)
http://www.mediafire.com/?j5m1plnvzb8r0zc
While booted into ClockWorkMod Recovery, go into your device manager, you should see an "LGE Android Composite Device" with a yellow triangle on it.
right click on it, update driver software...
select browse my computer for driver software
select let me pick from a list of device drivers on my computer
click the "Have Disk" button
click the "browse" button
browse to;
for 64bit:
C:\Program Files (x86)\LG Electronics\LG Android Driver\64BitADB
for 32bit:
C:\Program Files\LG Electronics\LG Android Driver
and select lgandadb.inf
click "ok"
From that list select "Android Sooner Single ADB Interface"
click "next"
click "yes" on the popup
Click to expand...
Click to collapse
Awesome Great Work. Did you figure out the Bootloader? Or is there even one should more be the question I suppose. Good thing I am having issues with permissions with this didn't notice the SD Card Mounting issue till just now. That I can't deal with atm.
malickie said:
Awesome Great Work. Did you figure out the Bootloader? Or is there even one should more be the question I suppose.
Click to expand...
Click to collapse
I found a few modes, but no drivers yet so I don't know what they are. Even if we break stuff the kernel and recovery are separate, so technically we should always be albe to get back into recovery to fix stuff.
thankyou DG for getting this started..
so now with my clockworkmod i just made a backup of stock rom... if i say change the framework and I get boot loop.. will this clockwork mod be able to restore the original rom without any problems???
tiny problem... might just be missing something... but after i made my backup and i choose reboot system now... it just goes back to recovery... how do i boot up my phone!!!
sorry if it is obvious... im super tired...
Trekfan422991 said:
tiny problem... might just be missing something... but after i made my backup and i choose reboot system now... it just goes back to recovery... how do i boot up my phone!!!
sorry if it is obvious... im super tired...
Click to expand...
Click to collapse
I got mixed up as to what partition to flash, you just flashed a recovery image over the kernel... its ok tho.
follow my instructions to the su part, then do this.
// this will restore the kernel
dd if=/sdcard/mmcblk0p5.backup of=/dev/block/mmcblk0p5 bs=4096
// this will backup recovery
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
// this will flash cwm
dd if=/data/recovery.img of=/dev/block/mmcblk0p6 bs=4096
OP is fixed!
edit--
and you have no adb access, this is going to get interesting!
haha... i shoulda noticed
____
LET THIS BE A LESSON FOR ALL OF YOU!!!!
THIS IS WHY YOU ALWAYS ALWAYS MAKE BACKUPS!!!!!!
NEVER SKIP THE BACKUP STEP!!!! haha
Trekfan422991 said:
LET THIS BE A LESSON FOR ALL OF YOU!!!!
THIS IS WHY YOU ALWAYS ALWAYS MAKE BACKUPS!!!!!!
NEVER SKIP THE BACKUP STEP!!!! haha
Click to expand...
Click to collapse
LOL! For sure that is why I always say, " Save early, save often, save to multiple locations!" haha.
47r0n1n said:
LOL! For sure that is why I always say, " Save early, save often, save to multiple locations!" haha.
Click to expand...
Click to collapse
sorry just side note:
how you liking your thrill compared to the evo 3d???
designgears said:
What you are going to need:
ADB (and know how to use it, don't ask in here)
Rooted Phone (again, that will not be covered, don't ask in here)
Optimus 3D recovery image [Download]
Click to expand...
Click to collapse
Thanks so much to DG & Trekfan, I've been looking everywhere for CWM!
I cannot find the download link to the recovery - in the quote above from the OP, where it says download, is that supposed to be a download link? I don't know if there's a typo or if I'm just missing something, but the "download" word doesn't link to anything for me. Instead, I thought I'd try searching for it in the optimus 3d forums, but search is down too Does anyone have a link?
Komodo Rogue said:
Thanks so much to DG & Trekfan, I've been looking everywhere for CWM!
I cannot find the download link to the recovery - in the quote above from the OP, where it says download, is that supposed to be a download link? I don't know if there's a typo or if I'm just missing something, but the "download" word doesn't link to anything for me. Instead, I thought I'd try searching for it in the optimus 3d forums, but search is down too Does anyone have a link?
Click to expand...
Click to collapse
I took it down for now, working on some issues.
Woohoo, got Trekfan422991 all fixed!
its true... i tested out my framework mod and it works great!!! look sway better then stock!!!
designgears said:
I took it down for now, working on some issues.
Click to expand...
Click to collapse
Ah, gotcha. I thought I was going crazy Thanks!
Let's rom this baby dg . I assume you also bought this with plans to possibly exchange it when the AT&T Galaxy S II comes out? I'm very impressed by the performance and build quality so far. The main thing it needs is a better theme... yikes!
designgears said:
Dangerous:
Fix Permissions (caused lots of crazy issues, fix by wiping data if you use it)
Sdparted (the sdcards are mount incorrectly, this will probably destroy your device)
Click to expand...
Click to collapse
After CWM is installed and working on our device, would it be safe to fix permission in "ROM Manager," or does that just fix permissions through whichever recovery is currently installed?
I'm guessing someone here knows how ROM manager works in this regard, but if not, I'd be happy to be a guinea pig... after all, I can make/restore backups now! : )
gtg465x said:
Let's rom this baby dg . I assume you also bought this with plans to possibly exchange it when the AT&T Galaxy S II comes out? I'm very impressed by the performance and build quality so far. The main thing it needs is a better theme... yikes!
Click to expand...
Click to collapse
Sorry for being OT but I must agree: if designgears made a Thrill ROM that's Cognition-esque then I'd consider keeping my Thrill, but considering he already has a ROM for the GSII, I imagine he's going to get the AT&T Galaxy S II? Side note, you know you've really earned some serious nerd-cred when other nerds (who you don't even know) speculate what your next cell is going to be
Komodo Rogue said:
Sorry for being OT but I must agree: if designgears made a Thrill ROM that's Cognition-esque then I'd consider keeping my Thrill, but considering he already has a ROM for the GSII, I imagine he's going to get the AT&T Galaxy S II? Side note, you know you've really earned some serious nerd-cred when other nerds (who you don't even know) speculate what your next cell is going to be
Click to expand...
Click to collapse
Not waiting on dg here. Think you missed the "let's" part. Working on a Thrill ROM as we speak. Just got the Thrill about an hour ago and I already dumped the system image, de-odexed it, created an updater-script, added root and busybox, removed bloat, and updated a few apps. Time to start theming, modding framework, and tweaking.
Im also working on a ROM but if we cannot flash zips with CWM then how am I supposed to flash the ROM? Are you going to flash it with Heimdall or something?
gtg465x said:
Not waiting on dg here. Think you missed the "let's" part. Working on a Thrill ROM as we speak. Just got the Thrill about an hour ago and I already dumped the system image, de-odexed it, created an updater-script, added root and busybox, removed bloat, and updated a few apps. Time to start theming, modding framework, and tweaking.
Click to expand...
Click to collapse
Oh, good to hear! Man I really have to sit down and try to learn some more technical stuff sometime, because ROM creation, and not even just the theming aspects, is so appealing to me.
Maybe you can create a thread placeholder and describe what you've done so far? We're really getting OT, sorry all.
timbrendelaz said:
Im also working on a ROM but if we cannot flash zips with CWM then how am I supposed to flash the ROM? Are you going to flash it with Heimdall or something?
Click to expand...
Click to collapse
Oh, I thought you could flash zips through adb after doing the fix? Or no? (((edit: wait, no, I was thinking about pushing .apks through ADB, not flashing .zip files))) Hopefully this is something DG's new recovery might address. If no to both, could you distribute ROMs via nandroid backup files of a fresh ROM installation? It would be incredibly inefficient, but it would work, right?
I have now successfully rooted my device by downloading the firmware, unpacking system.img.md5, adding the su binary, making an ext4 sparse image and installing that to the device using heimdall. Problem was, that on my first attempts the system became unstable, the UI restarted repeatedly, especially when manually switching WiFi and Data Mode. After double and triple checking everything I found that I could create a perfectly stable system image by following the same steps but just not adding the su binary. One further attempt placing the su binary in /system/usr/bin (does not exist) and using it as a backdoor to install the binary to /system/bin/su I now seem to have a stable and rooted system.
It appears that something has been detecting my initial and straightforward attempt to tamper with the system image and made the system to become unstable. I have seen a lot of errors from PackageManager in my logs but nothing conclusive.
Tom
RealBorg said:
I have now successfully rooted my device by downloading the firmware, unpacking system.img.md5, adding the su binary, making an ext4 sparse image and installing that to the device using heimdall. Problem was, that on my first attempts the system became unstable, the UI restarted repeatedly, especially when manually switching WiFi and Data Mode. After double and triple checking everything I found that I could create a perfectly stable system image by following the same steps but just not adding the su binary. One further attempt placing the su binary in /system/usr/bin (does not exist) and using it as a backdoor to install the binary to /system/bin/su I now seem to have a stable and rooted system.
It appears that something has been detecting my initial and straightforward attempt to tamper with the system image and made the system to become unstable. I have seen a lot of errors from PackageManager in my logs but nothing conclusive.
Tom
Click to expand...
Click to collapse
Hi Tom! I managed to root my s advance with this method, but in guide that I have read, was said that I should put the su binary on "/system/xbin/". I used that steps, by Xanonus. Over here everything gone right and after flashing, I got Supersu from Play store. If help you, please thanks Xanonus.
Sorry for bad English
johnnybr said:
Hi Tom! I managed to root my s advance with this method, but in guide that I have read, was said that I should put the su binary on "/system/xbin/". I used that steps, by Xanonus. Over here everything gone right and after flashing, I got Supersu from Play store. If help you, please thanks Xanonus.
Click to expand...
Click to collapse
Xanonus unnecessarily copies everything out from system to new_system, you can just add the su binary to the loop mounted image.
/bin/su is the location of the su binary on every Unix system and Superuser also installs the su binary to /system/bin/su. I wonder if it would make a difference (avoid instability) to place it in /system/xbin/su.
Tom
RealBorg said:
Xanonus unnecessarily copies everything out from system to new_system, you can just add the su binary to the loop mounted image.
Click to expand...
Click to collapse
I really suspected that, like you said, part of all that stuff was unnecessary.
About the place of su binary, well, I just wanna to help. I don't know nothing about linux and less of unix. But normally, while you are dealing with this kind of stuff, you should try. Cause things sometimes work when they shouldn't and don't work like they should. I can only say: God knows why...:silly:
Thread moved to General section, post in the relevant section next time.
Why use Heimdall to flash ? Odin3 works better
"None forget the bite.....of Viper...."
CallMeVentus said:
Why use Heimdall to flash ? Odin3 works better
Click to expand...
Click to collapse
heimdall is the method of choice when you are on linux and works like a charm
much easier than Odin which needs the image to be put into a .tar.md5 file
Tom
RealBorg said:
heimdall is the method of choice when you are on linux and works like a charm
much easier than Odin which needs the image to be put into a .tar.md5 file
Tom
Click to expand...
Click to collapse
I have tried heimdall but I can't make it work on Windows (7 X64, it never get to comunicate between pc and mobile). So when I was messing with my rom I have to try zillions of ways to make a image to work with Odin. In the end, make the image with ext4_utils and compress with tar on my virtual machine running ubuntu did the trick. If you don't put any md5sum verification or "md5" in the name of the file, Odin never check the file.
This was me trying to root hahhaa!!
I guess everyone that want play with Android should learn to use linux. ubuntu at least. I intend to learn linux, but I can't right now.
Sorry, crap english from google translator!
johnnybr said:
I have tried heimdall but I can't make it work on Windows (7 X64, it never get to comunicate between pc and mobile). So when I was messing with my rom I have to try zillions of ways to make a image to work with Odin. In the end, make the image with ext4_utils and compress with tar on my virtual machine running ubuntu did the trick. If you don't put any md5sum verification or "md5" in the name of the file, Odin never check the file.
This was me trying to root hahhaa!!
I guess everyone that want play with Android should learn to use linux. ubuntu at least. I intend to learn linux, but I can't right now.
Sorry, crap english from google translator!
Click to expand...
Click to collapse
Seriously?
How can hemidall work on windows when its designed for linux!
Sent from my GT-I9070 using xda premium
Shaaan said:
Seriously?
How can hemidall work on windows when its designed for linux!
Click to expand...
Click to collapse
Actually it has a windows version. Even Mac has a version of Heimdall. Take a look: http://www.glassechidna.com.au/products/heimdall/
Indeed I can't make it work... Perhaps on windows x86 it can work...
So I have done my homework and read tutorial guide and the nexus all in one beginners guide.
It took me a few hours to be able to get my pc to recognize my computer in fastboot mode using sdk and adp. (Hopefully my terminology is on track but doubtfully so).
So now in the command prompt, i can get the pc to recognize the phone in fastboot mode. Now all I really want to do is (this may sound silly) is to be able to use Air Mirror in airdroid... for now. I do like the stock android feel to this phone as I am new to nexus from the touchwiz **** from samsung.
So can i proceed to the commands of:
fastboot oem unlock
then
fastboot reboot
and then be done with it? Proceed to set up my google account and download my previous apps and contacts yada yada?
TIA
Hamm1701 said:
So I have done my homework and read tutorial guide and the nexus all in one beginners guide.
It took me a few hours to be able to get my pc to recognize my computer in fastboot mode using sdk and adp. (Hopefully my terminology is on track but doubtfully so).
So now in the command prompt, i can get the pc to recognize the phone in fastboot mode. Now all I really want to do is (this may sound silly) is to be able to use Air Mirror in airdroid... for now. I do like the stock android feel to this phone as I am new to nexus from the touchwiz **** from samsung.
So can i proceed to the commands of:
fastboot oem unlock
then
fastboot reboot
and then be done with it? Proceed to set up my google account and download my previous apps and contacts yada yada?
TIA
Click to expand...
Click to collapse
yup, make sure you have all data backed up to a pc, OEM Unlock will wipe your internal storage.
you also need to unlock developer settings, by tapping the build multiple times. Once unlocked you need to go into developer settings and click the check box to allow OEM Unlock
Afterwords if you want to run root, don't fastboot reboot you can use chainfires auto root and root-windows.bat and let it do its thing, then it will reboot and you can setup google account and move your files back over
If you want to flash TWRP, download that .img file and either use flashify to flash it from the google market or use fastboot flash recovery recovery.img
so it sounds like if i want root access, to do things such as air mirror from airdroid I need to flash cf's auto root?
Also in the all in one guide in imlicitly states to not skip the fastboot reboot step. Is this just a if you can do it, then do it step?
And yea, everything is backed up into google drive/cloud/plus and so on. So I am hoping once I am done I can setup my google account and everything should sync back as normal?
BTW thanks for the speedy reply.
Hamm1701 said:
so it sounds like if i want root access, to do things such as air mirror from airdroid I need to flash cf's auto root?
Also in the all in one guide in imlicitly states to not skip the fastboot reboot step. Is this just a if you can do it, then do it step?
And yea, everything is backed up into google drive/cloud/plus and so on. So I am hoping once I am done I can setup my google account and everything should sync back as normal?
BTW thanks for the speedy reply.
Click to expand...
Click to collapse
If you want to go the CF Auto root, you can just run root-windows.bat and it will actually perform the OEM Unlock step and complete that process for you, then it will root the phone and youll be back at the setup screen to enter your google account info, I think this will be the easiest route. It will take care of OEM Unlock, Adding Superuser and the binaries so you can run air mirror and any other root required app.
Yup if everything is backed up then once your login to the google account it will resync your apps and you can login to anything that needs credentials.
should I run fastboot reboot after it does its thing?
Hamm1701 said:
should I run fastboot reboot after it does its thing?
Click to expand...
Click to collapse
no, once you execute the root-windows.bat it will do all the fastboot commands, youll just have to hit a key on the CMD prompt after executing, it gives you a warning that OEM Unlock will wipe data, but you are already aware of that.
Basically, download cf-autoroot for shamu
unzip the zip into the same folder you have ADB installed (platform-tools)
get into adb and boot into bootloader mode or if your phone is in android already, adb reboot-bootloader
then root-windows.bat in the cmd window
and it will walk you through it from that point.
Circaflex said:
no, once you execute the root-windows.bat it will do all the fastboot commands, youll just have to hit a key on the CMD prompt after executing, it gives you a warning that OEM Unlock will wipe data, but you are already aware of that.
Click to expand...
Click to collapse
Cool, thanks for dealin with me. So now for the recovery. I downloaded the specified and latest vs of twrp recovery and I am told to rename it to and typed exactly the following after highlighting the file name: recovery.img
how can i verify that I have indeed named it recovery.img and not recovery.img.img
Hamm1701 said:
Cool, thanks for dealin with me. So now for the recovery. I downloaded the specified and latest vs of twrp recovery and I am told to rename it to and typed exactly the following after highlighting the file name: recovery.img
how can i verify that I have indeed named it recovery.img and not recovery.img.img
Click to expand...
Click to collapse
Do you have file extensions turned on for windows?
Depending on your version of windows it is different, but if they are turned on you would see the extensions for all files, if they are not turned on your files will not be showing extensions. If there is no extension rename the file to recovery and that's all if there are extensions youll see two .img's
Place that in your platform-tools folder as well, once autoroot is all installed and does its thing, set your phone up completely and get all the good stuff going
then power down and boot into boot loader or again use adb reboot-bootloader
then fastboot format cache (this wont harm any data or settings)
very important to then boot into recovery and let it load, then use recovery to reboot phone and youll be back in the android system
OR
download Flashify from the play store and select the .img you downloaded and it will flash the file, it works great
Hamm1701 said:
Cool, thanks for dealin with me. So now for the recovery. I downloaded the specified and latest vs of twrp recovery and I am told to rename it to and typed exactly the following after highlighting the file name: recovery.img
how can i verify that I have indeed named it recovery.img and not recovery.img.img
Click to expand...
Click to collapse
Just manually flash it....
fastboot flash recovery whatever-your-file-is-called.img
No need to rename it.
If you're going to remain rooted, it's a good idea to understand adb and fastboot correctly. Please take the time to read my thread.
http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
@Hamm1701 how did it go
Circaflex said:
@Hamm1701 how did it go
Click to expand...
Click to collapse
Yikes, didnt realize my post didnt go through last night. Well it went very well. I'll admit that when the little android guy was staying on "erasing" for a few to 5 ish min i started to panic a little. I was expecting something like erasing then installing then some other imaginative windows installation words.
But I am now trying to figure out why a certain app is not working 100% as it was before the root and unlock procedure. Ill be researching on learning how to provide feedback developers can use to make any neccasry changes. Do you know of any such threads/posts I can read up on in this regard?
Hamm1701 said:
Yikes, didnt realize my post didnt go through last night. Well it went very well. I'll admit that when the little android guy was staying on "erasing" for a few to 5 ish min i started to panic a little. I was expecting something like erasing then installing then some other imaginative windows installation words.
But I am now trying to figure out why a certain app is not working 100% as it was before the root and unlock procedure. Ill be researching on learning how to provide feedback developers can use to make any neccasry changes. Do you know of any such threads/posts I can read up on in this regard?
Click to expand...
Click to collapse
which app is misbehaving? Basically if you have a problem the easiest solution is to pull a catlog that will detail what your phone was doing and show the error. You can do this through ADB or a free program from playstore is called Catlog.
Circaflex said:
which app is misbehaving? Basically if you have a problem the easiest solution is to pull a catlog that will detail what your phone was doing and show the error. You can do this through ADB or a free program from playstore is called Catlog.
Click to expand...
Click to collapse
It was the manual camera app. So I think i figure out how to view and store catlogs. Going to post my question about it over in dev Q&A.
so I have a spare m7(UL) that I'd like to experiment with. I would like to try to port a rom made for the m8 to the m7, but cannot find any tutorials based on this specifically. If such a thing exists, could someone link me? if not, does anyone have any expertise with this?
at this point I have been able to successfully get the script to flash with successcode=1.0. ROM will not boot(as I expected) staying stuck on the boot logo. I don't know what logs would be useful besides the installer log which I will attach here, so please let me know.
EDIT: included kernel log and system log
Try use logcat
Sent from my One using XDA-Developers mobile app
tathanhlam66 said:
Try use logcat
Sent from my One using XDA-Developers mobile app
Click to expand...
Click to collapse
I can't reach adb until after the boot logo. just hangs at waiting for device. is there another way of getting the logcat, or anything else I can do?
bbmaster123 said:
I can't reach adb until after the boot logo. just hangs at waiting for device. is there another way of getting the logcat, or anything else I can do?
Click to expand...
Click to collapse
extract boot.img
edit ramdisk/default.prop
change line ro.adb.secure=1 -> ro.adb.secure=0
add botton line persist.sys.usb.config=mtp,adb
use new boot.img
tathanhlam66 said:
extract boot.img
edit ramdisk/default.prop
change line ro.adb.secure=1 -> ro.adb.secure=0
add botton line persist.sys.usb.config=mtp,adb
use new boot.img
Click to expand...
Click to collapse
Just finished installing cygwin and android kitchen, unpacked boot.img, and opened default.prop. all those were already set exactly like you said, so I just closed the file. copied over boothpath from "BASE" rom's boot.img in init_environ.rc (I believe thats what it was called, but I'm sure you know what I mean) repacked, and flashing now.
UPDATE: Rom failed to finish flashing with error code 7. ended with set_perm: some changes failed caused by a chown command for busybox in the updater-script, but I double checked and busy box is in /system/xbin like it should be. If I remove that line, the rom finishes flashing with success code 1.0 but fails to boot...