• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Unoffical] TWRP 3.0.2 1/25/17

spock1104 said:
I did and I thank you, I'm just trying to fully understand the post. Are you just reporting that the file manager works or are you suggesting a workaround to something? My apologies for sounding dense, the context just isn't coming across to me.
Click to expand...
No worries, I'm just reporting the file manager works and chmod works.
 
When flashing change of jinzo's APN fix it goes to aroma installer it just boots right up instead of allowing you to choose you desired APN. Has anyone else tried & had this happen? Happened to me twice when flashing the newest ROM!
 
mjhealy1978 said:
When flashing change of jinzo's APN fix it goes to aroma installer it just boots right up instead of allowing you to choose you desired APN. Has anyone else tried & had this happen? Happened to me twice when flashing the newest ROM!
Click to expand...
Use the file manager to grab /cache/recovery/last_log
 
mjhealy1978 said:
I have es file manager pro! How would I grab the files your asking for, sorry never done this!
Click to expand...

You can do this within twrp. Click "mount" and then check "System." Then click back arrow and select "Advanced," then select "File Manager." Click on "cache" folder and then "recover." Now you should see "last_log" file. Click on it and select "copy file." Then navigate to the folder you want to copy it to. If you have an sd card, you will see "sdcard" folder. Once you are in the folder you want to copy the file to, click on the check mark on the bottom right side of the screen and then swipe to confirm. That's it. Hope that helps!! Be careful, when in the system folder!!
 
alternatereality said:
You can do this within twrp. Click "mount" and then check "System." Then click back arrow and select "Advanced," then select "File Manager." Click on "cache" folder and then "recover." Now you should see "last_log" file. Click on it and select "copy file." Then navigate to the folder you want to copy it to. If you have an sd card, you will see "sdcard" folder. Once you are in the folder you want to copy the file to, click on the check mark on the bottom right side of the screen and then swipe to confirm. That's it. Hope that helps!! Be careful, when in the system folder!!
Click to expand...

That's overkill. Es file manager will work fine, otherwise use the file manager that comes with the ROM. Enable root access in either of them, go to the root directory, and navigate to the file. Long press the file and either share or copy, but find some way of posting so I can see it.

At work right now, can't give much detail.
 
mjhealy1978 said:
When flashing change of jinzo's APN fix it goes to aroma installer it just boots right up instead of allowing you to choose you desired APN. Has anyone else tried & had this happen? Happened to me twice when flashing the newest ROM!
Click to expand...

I have this exact problem as well. Any time I've tried to flash the APN fix on TWRP 3 (any build) it will start, but when it goes to display the selection of carriers, it has done a variation of the following:
  • lockup and reboot into system (most common)
  • corrupt the graphics, then lockup, reboot into system (only saw a couple times across earlier builds)
  • completely lockup and require me to pull the battery (only happened once with an alpha build)
I just went ahead and tried it again after getting my phone on the latest build of the ROM (with TWRP 2.8.7) and making sure all was working fine. Reflashed the 3.0.2-2 build and had the lockup+reboot into system. I've attached my last_log from the recovery folder (I renamed it when I pulled it off my phone) which seems to include my boot into 2.8.7 and flash of 3.0.2-2. It just doesn't seem that anything was captured from flashing the APN fix in 3.0.2... odd. One thing in particular that sticks out to me in the 3.0.2 boot is this specifically

Code: 
Starting the UI...
Overlay graphics may work (mdssfb_80000), but not enabled. Use TW_TARGET_USES_QCOM_BSP := true to enable.
setting DRM_FORMAT_RGBX8888 and GGL_PIXEL_FORMAT_RGBX_8888
cannot find/open a drm device: No such file or directory

Could it be the reason I've seen corrupt gfx before is there isn't a way to display them correctly? I know little to nothing about android in this aspect, so its purely speculation. Anyway, if there's any other logs or anything else you need me to grab, let me know and I'll get it asap!
 

Attachments

BiggieStylin said:
I have this exact problem as well. Any time I've tried to flash the APN fix on TWRP 3 (any build) it will start, but when it goes to display the selection of carriers, it has done a variation of the following:
  • lockup and reboot into system (most common)
  • corrupt the graphics, then lockup, reboot into system (only saw a couple times across earlier builds)
  • completely lockup and require me to pull the battery (only happened once with an alpha build)
I just went ahead and tried it again after getting my phone on the latest build of the ROM (with TWRP 2.8.7) and making sure all was working fine. Reflashed the 3.0.2-2 build and had the lockup+reboot into system. I've attached my last_log from the recovery folder (I renamed it when I pulled it off my phone) which seems to include my boot into 2.8.7 and flash of 3.0.2-2. It just doesn't seem that anything was captured from flashing the APN fix in 3.0.2... odd. One thing in particular that sticks out to me in the 3.0.2 boot is this specifically

Code: 
Starting the UI...
Overlay graphics may work (mdssfb_80000), but not enabled. Use TW_TARGET_USES_QCOM_BSP := true to enable.
setting DRM_FORMAT_RGBX8888 and GGL_PIXEL_FORMAT_RGBX_8888
cannot find/open a drm device: No such file or directory

Could it be the reason I've seen corrupt gfx before is there isn't a way to display them correctly? I know little to nothing about android in this aspect, so its purely speculation. Anyway, if there's any other logs or anything else you need me to grab, let me know and I'll get it asap!
Click to expand...

Thanks! That's the oddest thing, I can see you flash 3.0.2 and then boot into 3.0.2 but I can't see any logs from trying to load the APN. No need to reflash, but can you pull the log again and see if it mentions the zip name at all?

And from another angle, I added the TW_TARGET_USES_QCOM_BSP flag if you'd like to give this version a try...

http://www.mediafire.com/file/rywe5ww341dpu6u/twrp_302-bsp_volt.img
92C67EF063DF0C80494C57EAFA55FD96
 
Before rebooting to flash the new image, I checked the log again, it hasn't changed... still no mention of the zip. Can a recovery actually have a kernel panic? Anyway, flashed the new recovery image and tried to flash the APN fix, it worked! I was able to select my carrier and it completed, then I rebooted and everything was good. There seems to still be some graphics corruption, which I got a photo of (attached) but its totally useable. I've also attached the last_log again after flashing just in case there's anything you need, the second boot looks a lot better this time :) Thank you!
 

Attachments

  • 16326618_10155067350528783_1243521121_o.jpg
    16326618_10155067350528783_1243521121_o.jpg
    119.2 KB · Views: 190
  • twrp-3.0.2-bsp-last_log.txt
    twrp-3.0.2-bsp-last_log.txt
    58.7 KB · Views: 183
Hummm... interesting. I decided to flash back to the non-bsp 3.0.2-2 build and flash the APN fix again. I checked the last_log again and it shows no signs of the APN zip file. However, after it booted back into the system I peeked into /proc/last_kmsg and it shows an access denied to /dev/graphics/fb0 at the end of the log, but no other errors. At least it shows my attempt to flash the zip here :) I'll stick with the bsp build as it works, but I figured the extra information might be of some help.
 

Attachments

You must log in or register to reply here.
Back
Top Bottom