Develop Bugs

[Q] Hboot 2.02 and /system/ partition size

My old evo decided to commit suicide
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyway got a new evo in, trying to get it rooted. Got as far as getting S-OFF which seems to be important:
Supersonic EVT2-3 SHIP S-OFF
Hboot 2.02.0000
Click to expand...
Click to collapse
Flash MISC, run the pc36img. Everything seems sane, then i do the rageagainstthecage exploit again, load on a recovery image. as soon as i reboot to recovery my /system/ partition size gets cut in half and then i can never boot again because random files are missing. Also flashing images fails because half the files dont copy. same with nandroid restores.
results from df before:
/system: 358400K total, 270140K used, 88260K available (block size 4096)
results from df inside recovery after mount -a
/dev/block/mtdblock4 179200 131460 47740 73%
Click to expand...
Click to collapse
I cant seem to find anyone else with this problem, ive tried it several times with different recovery images. WTF am i missing?

Have you tried unrevokeds unrooter? I used it when i got my second evo with 2.2 on it and i had no problems. Maybe the root method is causing the problems.

I had the same problem. I ran RUU using fastboot and it restored me to stock.

Same issue...
I was able to get su with hboot Super one click.. I can post a place to download if needed. My issue is with the crappy quality of this hardware ver (003) my wife has the original and i love it.

also
I also cannot get any roms to load... I used the traditonal push with no success... Although i have noticed on significant thing that seems to keep happening.... its always fails with the boot.img. I tried loading Fresh through the Rom manager and all it would do is kick me to recovery.... try to do it manually and all roms fail on the boot img.

After unmounting SD, still seeing, "Couldn't install on USB storage or SD Card".

After unmounting SD, still seeing, "Couldn't install on USB storage or SD Card".
It seems like I've tried just about everything. This has only been a problem since coming to ICS, no matter what ROM I'm running.
Attempting to download and install large apps & games from the Play Market presents the following error (which many of you have seen):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"Couldn't install on USB storage or SD card. "
I'm going to put this in bold, because many people will probably come in here and call me an idiot who needs to search the site (although I've been looking for a fix for about a month now):
The error is persistent even after unmounting and/or removing SD card and rebooting
I am currently running AOKP, but have seen the error on CM9 and Caulkin builds. I've purchased many games which I am unable to install and it has been very frustrating. Any advice?

That happens when not on a stock kernel. I have read that clearing cache and rebooting has fixed this issue for some. I am not sure if you could flash a stock kernel with that rom or not. I would look in the roms thread to see if flashing a stock kernel is possible or not.
Sent from my SPH-D710 using Tapatalk 2 Beta-5

Yeah, I've flashed a few kernels and cleared a few caches to no success. But you've given me an idea: flash a stock GB rom, download the apps, back up the .apk, flash back to ICS and install.
Pain in my ass!!

Rogue repacked kernels(cwm) or stock kernels(no cmw)? Its ussually the repacks causing market issues. I download Samurai vs Zombie(133mb) with no issue. Here is some no cwm kernels thanks to Team Nocturnal.
http://www.androidfilehost.com/main...end/Stable_Builds/BLEND ICS GOODNESS/KERNELs/
Sent from my SPH-D710 using Tapatalk 2 Beta-5

Thanks, I'll check it out and report back!

Can't Mount R/W In System after Root

Hi guys, anyone have a trouble with executing su in adb or trying to mount rw in system with root explroer? It just refuses to even though root check says I'm rooted.
I need this to get a newer version of CWMR and such...

That's strange, I have zero problems getting root in an adb shell, and was able to remount /system as rw both on the device and via adb. Have you opened the Superuser app and checked to see if it needs updated?

bakageta said:
That's strange, I have zero problems getting root in an adb shell, and was able to remount /system as rw both on the device and via adb. Have you opened the Superuser app and checked to see if it needs updated?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can't gain root access for some reason. Can you link me to a superuser zip you used?

What process did you use to get superuser? Mine is working fine.
Sent from my SGH-I927 using xda premium

Flashed the zip suggested in the thread rooting glide on 4.0.4 in development
| Powered By |
SAMSUNG GALAXY S III I747
AOKP JELLYBEAN

That's weird. Maybe it was a bad su flash? I had a problem before where it said I was rooted but titanium backup said I wasn't.
Sent from my SGH-I927 using xda premium

Someone post the zip they used to get root please
| Powered By |
SAMSUNG GALAXY S III I747
AOKP JELLYBEAN

From my post in the 4.0.4 leak thread:
bakageta said:
Rooted here, was as simple as flashing a superuser zip from CWM. This is the zip I used, I downloaded several to find one that would work and I honestly don't recall where I snagged it from, so apologies to whoever I stole it from.
I'll be setting up my fstab to swap the internal and sd card now, and restoring everything I use from TB.
Click to expand...
Click to collapse
I didn't bother to use the latest version as I was just replacing it with the latest SuperSU once I had root, and it worked just fine.

It gives me status 0...how'd you get it to flash?
Edit ugh also without my SIM card in there's no power menu or lock screen l
Sent from my SGH-I927 using xda premium

Flashed without issues in CWMR 6.0.0.1, nothing special needed... *shrugs*

did you use the one i posted? if so it worked for me.. but im using CWMR 5.0.2.7

Twrp issues

I've always used CWM but I see everyone basically recommending it. I've tried it in the past and I've never had it work probably, they just updated it to 2.4.2.0, so I figured I'd give it a shot. The time zone is set, time never is correct, battery is no where near correct, that doesn't bother me, however, I cannot make a backup. I CAN and do, but once I reboot and enter recovery again, it doesn't show up under restore. The backup is still in my phone though via root explorer. I usually fast boot flash the .IMG file, but I also used goo manager to just see if somehow it got corrupt. To be honest the only two features I like are being able to name your backups, and multi zip flashing is neat. What the ****?
TL;DR
Toro user
TWRP doesn't keep backups, date and battery info are incorrect.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Pretty sure this phone didn't exist in '99)
Sent from my MMuZZY'D SCH-i515

backups should be in /data/media/0/TWRP/...
because the virtual sdcard is in /data/media/0/ for android 4.2 and above

andQlimax said:
backups should be in /data/media/0/TWRP/...
because the virtual sdcard is in /data/media/0/ for android 4.2 and above
Click to expand...
Click to collapse
That's just a redirect.
Just how like that's the same for:
/storage/emulated/0
/storage/emulated/legacy
/storage/sdcard0
/sdcard/
Are all the same directory, same files.
REGARDLESS, twrp should account for the 4.2 filesystem as you needed to update your recovery going to 4.2 to have these issues corrected and my clockwork touch recovery works fine, and I've used the newest twrp, so it makes no sense, I've even backed up my storage, deleted /data/media while doing a full cleanup to have twrp and my ROM create the correct directories for 4.2 and it still doesn't work.
If it wasn't the correct version it would keep creating /x/0/0/0 everytime I flashed a new ROM which it doesn't.
I'm over it as twrp only has those two features which doesn't bother me and the interface is ugly IMHO.
Sent from my MMuZZY'D SCH-i515

andQlimax said:
backups should be in /data/media/0/TWRP/...
because the virtual sdcard is in /data/media/0/ for android 4.2 and above
Click to expand...
Click to collapse
notstevek said:
That's just a redirect.
Click to expand...
Click to collapse
It's not a redirect. /data/media/0 is the physical location of the data. The other locations are either fuse mounts or symlinks that point back to this location.

No Kernel Wakelock stats in BBS

I have no stats for Kernel Wakelocks in BetterBatteryStats. I've installed the latest version, installed the system app, but still get nothing. Everything else shows and works fine. Anyone else having this issue?

Yes, I face the same issue. Its a known issue and dev does not have cycles right now.

Cycles?
I think it also took a special fix for the LG g5 to show them...

Haldi4803 said:
Cycles?
Click to expand...
Click to collapse
lol...that's dev-speak for time for development work.

Ok, thanks for the heads up. It's not a huge deal, was just wondering if it was me, or something else.

I could be wrong but I get this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Custom Rom? Custom Kernel?
Installed as System App?

This is the leedroid rom, but it worked on the US ruu one too. I don't think I installed it as system.
Sent from my HTC 10 using XDA-Developers mobile app

V2.2B6?

devsk said:
HTC init scripts are not mounting the debugfs. That's the reason for missing kernel wakelocks in HTC 10. Do the following from a root shell:
Code:
mntP=$(grep /sys/kernel/debug /proc/mounts | awk '{print $2}')
if [[ "${mntP}" != "/sys/kernel/debug" ]]
then
mount -t debugfs none /sys/kernel/debug
fi
Relaunch BBS and it should show the kernel wakelocks now.
Click to expand...
Click to collapse
Don't forget su, and you need to kill the App after the command

Haldi4803 said:
Don't forget su, and you need to kill the App after the command
Click to expand...
Click to collapse
Is this something that needs to be run on every boot, or once run it should stay? If it needs to be re-run on boot I suppose I'll just make Tasker run the script.

duowing said:
Is this something that needs to be run on every boot, or once run it should stay? If it needs to be re-run on boot I suppose I'll just make Tasker run the script.
Click to expand...
Click to collapse
This needs to be done every boot and as root.