Database Develop

[DEV][BRAINSTORM] Fully-working CWM Recovery

While the recovery we have at the moment, fruit of the hard work of xantaro, unclecracker and digitalfrost, is enough for most operations there are some things bugging me that is in our interest to fix with the ultimate aim of adding it to ROM Manager and thus get official support.
Current issues:
1. It isn't the latest version of CWM and isn't official.
2. It doesn't have USB mount working.
3. It doesn't have ADB working.
4. It doesn't support EXT4.
Now, I have tried to fix these but recoveries are a new domain for me and at a first attempt I couldn't bring some of these to work. Compiling the latest version was easy and an important first step towards official; however, all others I couldn't do it and I don't think we should talk with koush before fixing all this.
Here are my short attempts:
- For USB mount I defined on the BoardConfig the path for UMS lun0 file. The path seems to be correct and there's no other file in /platform/ as I've found out by running a ls -R. I have no idea why it's not working.
- For ADB, I made sure the persist.adb.service is set to 1 and the init.rc is starting it. This being said, I don't know what's missing. Perhaps this is of interest?
- For EXT4 support I thought it was just a matter of adding alternative FS to recovery.fstab. Seems I was wrong though.
So, does anyone want to join in and help?
This is really new territory to me and I have a quite faint idea of what I'm doing.
A few guidelines:
- Read this to get an idea.
- You'll need CM sources (repo init... repo sync...)
- The CWM recovery source is in /bootable/recovery
- Here is my device source and a patch file for some changes on recovery src *
- Run build commands (. build/envsetup.sh, lunch full_p970-eng, make -j4 recoveryimage)
* If you don't change what I did on the recovery source you won't have a key to select.
Also, I have CWM 4.x at the moment on my OB but since it does the same as the already posted 3.x I don't deem necessary to share it; but if anyone wants, I'll upload it.
I'll join the party when I come from the mini-vacations, hope there'll be some progress meanwhile!

Great
i'll try to do some help,maybe little

If anyone wants you can request a pull from my source.
Also, here's a flashing CWM 4.x. I renamed it Nova recovery for the lulz.
http://www.multiupload.com/R7WGNYTL7G

Changes on the Source to get selectbutton to work shouldn´t be necessary. Adding "BOARD_HAS_NO_SELECT_BUTTON := true" to boardconfig.mk suffices to get selectbutton to work.
EXT4 Backup and Restore worked for me after editing the fstab file.
For the ADB and USB mount problem i have no Idea what is missing. Like you said, adb daemon should get started througt the initscript.
BTW. seems like the Progressbar isn´t working on the newer Versions of CWM

xantaro said:
EXT4 Backup and Restore worked for me after editing the fstab file.
Click to expand...
Click to collapse
Could you release a new version or tell us how to do it? Thanks

To get EXT4 working in my O2X builds my /data line looks like this:
Code:
/data ext3 /dev/block/mmcblk0p9 NULL auto

xantaro said:
Changes on the Source to get selectbutton to work shouldn´t be necessary. Adding "BOARD_HAS_NO_SELECT_BUTTON := true" to boardconfig.mk suffices to get selectbutton to work.
Click to expand...
Click to collapse
I thought the flag wasn't suffice. Thanks.
Rusty! said:
To get EXT4 working in my O2X builds my /data line looks like this:
Code:
/data ext3 /dev/block/mmcblk0p9 NULL auto
Click to expand...
Click to collapse
Nice tip, I'll try.

knzo said:
While the recovery we have at the moment, fruit of the hard work of xantaro, unclecracker and digitalfrost, is enough for most operations there are some things bugging me that is in our interest to fix with the ultimate aim of adding it to ROM Manager and thus get official support.
Current issues:
1. It isn't the latest version of CWM and isn't official.
2. It doesn't have USB mount working.
3. It doesn't have ADB working.
4. It doesn't support EXT4.
Click to expand...
Click to collapse
Hey,
I know this is an old thread but still if u have not resolved the problem with ADB and USB follow these instruction:
Before we start:
My mobile is Spice Mi-410 (Qualcomm made), also known as Cherrymobile magnum, Wellcomm, Motorola triumph in different countries. So may be these tweak will not work with your device. (But you can give it a try )
I hope you know how to unpack recovery.img of your device (or boot.img if your recovery ramdisk is stored in boot.img like Xperia Arc) if not then follow this guide to unpack recovery.img and extract recovery ramdisk into a folder.
Tweak
For ADB: Open init.rc file from recovery ramdisk/initram using any editor of your choice
Put this line at the end of "on init" section
Code:
write /sys/module/g_android/parameters/product_id ####
where #### should be replaced by your device's product id.
(if you dont know what it is then connect your mobile to PC and issue "lsusb" command in ubuntu terminal, you should see something like this
Bus 001 Device 027: ID 0489:c000 Foxconn / Hon Hai
Here c000 is my devices product id and Foxconn is my device's manufacturer)
Though /sys/module/g_android is not present in our device but this worked for me.
Please note that the device id is case sensitive, so write what you see on PC
For USB: For this add following line at the end of "on boot" section in init.rc file
Code:
echo 1 > /sys/class/usb_composite/usb_mass_storage/enable
For your device first confirm the location of /sys/class/ ###### / ####/usb_mass_storage/enable
Since this location vary from device to device.
This should enable usb storage mounting from recovery.
Best of luck!!

One option for load rootfs image in native mode is necesary
enviado

[Q] Boot manager for O2x

All,
I found a useful app which many would be interested in buying (a paid app).
It is Boot manager which allows 4 ROMs to be stored on SD card and the user can switch b/w the ROMs by a simple reboot.
Currently our device is not supported but the dev on market link says he will give instructions on how to support it unofficially for any device
I ain't an expert but if someone who is good at these things, he may try to make this app compatible for our phone enabling many users to try it.
The market link is :
https://market.android.com/details?id=com.drx2.bootmanager&feature=search_result

This would be great i would also be interested in this hopefully someone could work with the dev and get it working on the o2x

Just as a catcher-upper...
..has anyone figured out what the manuel settings would be?
DEVICE: LG OPTIMUS 2x
SDCARD BLOCK: 1024?
SYSTEMSIZE(mb):(would thisbe my current rom size? ex:clockwworkmod backup?) about 500mb
DATASIZE(mb): (would this be a stand Kang size?) about 100mb
CACHESIZE(mb): about 48mb
Can anyone look this over and give me their thoughts?

Rezvonflux said:
Just as a catcher-upper...
..has anyone figured out what the manuel settings would be?
DEVICE: LG OPTIMUS 2x
SDCARD BLOCK: 1024?
SYSTEMSIZE(mb):(would thisbe my current rom size? ex:clockwworkmod backup?) about 500mb
DATASIZE(mb): (would this be a stand Kang size?) about 100mb
CACHESIZE(mb): about 48mb
Can anyone look this over and give me their thoughts?
Click to expand...
Click to collapse
DEVICE: p990
SDCARD BLOCK: go to recovery mount CACHE, DATA, SYSTEM, SDCARD and EMMC than start ADB shell on your PC and type: Mount SDcard (press enter) then tipe Mount now you should see the block auf your SDCard
SYSTEMSIZE(mb):335mb
DATASIZE(mb): choose what you want i took 650mb
CACHESIZE(mb): same as DATA i choosed 65
works fine but i get a problem with the backup of the Boot IMG

Lukas94 said:
DEVICE: p990
SDCARD BLOCK: go to recovery mount CACHE, DATA, SYSTEM, SDCARD and EMMC than start ADB shell on your PC and type: Mount SDcard (press enter) then tipe Mount now you should see the block auf your SDCard
SYSTEMSIZE(mb):335mb
DATASIZE(mb): choose what you want i took 650mb[/B]
CACHESIZE(mb): same as DATA i choosed 65
works fine but i get a problem with the backup of the Boot IMG
Click to expand...
Click to collapse
I'm using Rom Toolbox, there's a setting in it for my SDCARD. It was set for 128, but I've brought it up to 1024.... is that what they mean?

Rezvonflux said:
I'm using Rom Toolbox, there's a setting in it for my SDCARD. It was set for 128, but I've brought it up to 1024.... is that what they mean?
Click to expand...
Click to collapse
No, it is the android r/w buffer size
Inviato dal mio Smartpad810c usando Tapatalk

Does Boot Manager Pro work with our Optimus 2x's? Can I switch between Temasek's KANG build P204-66 and CyanogenMod9 (SelfKANG2)?

Lukas94 said:
DEVICE: p990
SDCARD BLOCK: go to recovery mount CACHE, DATA, SYSTEM, SDCARD and EMMC than start ADB shell on your PC and type: Mount SDcard (press enter) then tipe Mount now you should see the block auf your SDCard
Click to expand...
Click to collapse
It's more simple to run Terminal Emulator on your phone and type 'mount' command .....
/dev/block/mmcblk0p1 is the block device where /system is located.

Trystan34 said:
Does Boot Manager Pro work with our Optimus 2x's? Can I switch between Temasek's KANG build P204-66 and CyanogenMod9 (SelfKANG2)?
Click to expand...
Click to collapse
Exactly what i wanted to use it for, tho i think i saw something about the SK3 being out now.
Well, i chickened out Wasn't so sure on some of the values and i don't exactly consider myself totally android savvy yet.
But, if anyone else want's to give it a shot... i'd be glad to try again...i think...

Well, its sad to say but at least I got a reply back :
" The app won't work on the p990 unfortunately. "
So, guess we'll have to wait foe something else to come around
Sent from my Optimus 2X

I e-mailed the developers and they said "None of the LG phone's are supported at this time. We've made some attempts to add lg phone's but haven't been able to get any of them to work."

[Q] Download mode messed up

Preface:
I was performing a nandroid restore and then accidentally removed the battery at some point.
Situation:
Phone does not boot past black and white galaxy S screen.
Going into Clockwork Recovery, I am unable to factory reset, or start a restore because it seemingly is not able to detect any of the storage of the device....
(sample messages below):
Code:
E:unknown volume for path [/data]
E:unknown volume for path [/cache]
E:unknown volume for path [/sdcard]
E:unknown volume "/data"
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
Furthermore, I can't just re-flash in download mode because the computer refuses to detect it in windows. At first I thought it was a driver problem, because i've had difficulty with my computer detecting the phone at times, but now I suspect download mode is broken somehow (after trying to reinstall the drivers and installing kies, and various combinations therein). When the phone is plugged into a different computer ( laptop ) running linux, I get messages like these on the command line:
Code:
usb 1-1: device not accepting address 2, error -71
usb 1-1: device descriptor read/64, error -71
usb 1-1: device descriptor read/8, error -71
hub-1.0:1.0: unable to enumerate USB device on port 1
On another note assuming I can't resolve this in a more delicate manner, can someone tell me if it is possible to use a jtag programmer to flash the phone?
Would using a jig to get into download mode make a difference?
Thank you very much for your assistance.

Wich Rom where you trying to restore to?
and what Rom were you on before you hit the Restore button?

pzayx said:
Wich Rom where you trying to restore to?
and what Rom were you on before you hit the Restore button?
Click to expand...
Click to collapse
I was trying to restore to stock JVR (rooted, no lagfix, semaphore kernel I think), from the ice cream sandwich port.

okey, i see, you might need to download android sdk and download the latest usb package or search around for the drivers for Nexus, since the usb drivers for galaxy s doesnt work with cm7/ics builds.
if you manage to make your pc recognise your phone you could check out this thread:
http://forum.xda-developers.com/showthread.php?t=1134975
btw, if you want to restore from ICS to stock gingerbread i think you will have to install a stock gingerbread ROM before you restore.
Hope this helps you!
(edit: if you find the driver or download it from SDK you can head here http://www.dkszone.net/setup-install-adb-android-debug-bridge-windows-7 to see a guide for how to set the driver manually)

Hm, Well I had already had the SDK and the drivers on my computer, but do I need to do anything special to install them? I recall previously trying the [right-click inf > Install] method, for some reason, but that didn't work

zeco said:
Hm, Well I had already had the SDK and the drivers on my computer, but do I need to do anything special to install them? I recall previously trying the [right-click inf > Install] method, for some reason, but that didn't work
Click to expand...
Click to collapse
i had to manually set the drivers,
i used this thread to do it:
http://www.dkszone.net/setup-install-adb-android-debug-bridge-windows-7
Just jump straight to step #7 if you have the drivers

Upon selecting the driver, windows immediately complains:
"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
Agh, And I thought this might actually work too.
EDIT:
Unknown if this is a success or not... but i've been alternating computers trying various permutations of fixes, and this time my laptop actually says the word samsung in the device manager....
EDIT2: Odin Sees it! I am going to try to flash JVR now... then retry restore from there....
P.S. I hope to god this is not related, but I actually just dropped my phone in between switching to attempt on laptop....
EDIT3: Detection, but immediate failure open attempting to flash. Then rebooted phone and now upon pressing start again it seems to be flashing.........
P.P.S: I've got to say, the most stable thing about this series of phone has got to be the bootloaders :#, Like seriously, this thing is boss.
EDIT4: Well. Managed to flash, Now I just get stock recovery with the same problem of it not finding the storage... I guess I will try flashing with repartion and a PIT?

I had to manually choose the folder where i store the Android SDK.
like c:\sdk\sdk\
it sucks when things dosent work like they should do!

So Yeah... Despite not really changing very much at all, download mode connects, and My phone now boots, Which is a lot better than where I was at previously So thanks for your help.

yw, happy i could help you!

The next mystery to solve is why Recovery is still screwed, and why I can boot my device anyway....

Hmm
So youre still getting the E:\ unknown volume *****?
Wich odin version do u use?
I had to use Ezodin last time to get it to flash,
then i flashed full stock JVH (with pda, phone & csc)
but i guess you could try to flash a stock Gingerbread bootloader too,
http://forum.xda-developers.com/showthread.php?t=1089989 Here is both Froyo and Gingerbread bootloaders.
And i have Atached EZodin for you.

[SOLVED] Help please.

Hey everyone, I hope you guys are having a great day/night
I'm fairly new to android but please help
So I was updating cyanogenmod in my HTC One, and when it rebooted back it got stuck on recovery. I'm currently stuck on TWRP and been trying to look for solutions online. I tried the RUU but i can't find any for my HTC One, I'm in Canada and I have Rogers as my carrier.
I've also tried to sideload ROMs through ADB but I kept getting errors, such as failed to write data protocol, and when I push a file over to my HTC One and try to installing it through /sdcard it gives me the error of unable to mount data.
It's been a week without my HTC One And I miss it.

MSumthing said:
Hey everyone, I hope you guys are having a great day/night
I'm fairly new to android but please help
So I was updating cyanogenmod in my HTC One, and when it rebooted back it got stuck on recovery. I'm currently stuck on TWRP and been trying to look for solutions online. I tried the RUU but i can't find any for my HTC One, I'm in Canada and I have Rogers as my carrier.
I've also tried to sideload ROMs through ADB but I kept getting errors, such as failed to write data protocol, and when I push a file over to my HTC One and try to installing it through /sdcard it gives me the error of unable to mount data.
It's been a week without my HTC One And I miss it.
Click to expand...
Click to collapse
Try renaming the rom file to update.zip , then use adb to push the file to your phone. Also, are you rebooting your phone into twrp, and then trying to push your files? You need to be in your boot menu..
If your still stuck, let me know. I may have time to use team viewer and show you. That is, in between periods, Hockey game is about to start lol

g2tegg said:
Try renaming the rom file to update.zip , then use adb to push the file to your phone. Also, are you rebooting your phone into twrp, and then trying to push your files? You need to be in your boot menu..
If your still stuck, let me know. I may have time to use team viewer and show you. That is, in between periods, Hockey game is about to start lol
Click to expand...
Click to collapse
Hey, I renamed it and still gives me the error of E:Unable to mount '/data' & E:Unable to mount internal storage. Though these errors always showed up every time i tried to flash a ROM. And what do you mean by rebooting your phone into TWRP and then trying to push the files?
LEAFS <3 LOL

Are you pushing the files while your on twrp? Or just on the boot menu (volume up + power). From what I remember you can only push the files when your on your bootmenu.
Also, type adb devices in order to confirm if your device is actually being recognised by your computer.
Sent from my HTC One using Tapatalk

g2tegg said:
Are you pushing the files while your on twrp? Or just on the boot menu (volume up + power). From what I remember you can only push the files when your on your bootmenu.
Also, type adb devices in order to confirm if your device is actually being recognised by your computer.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Yup, I'm pushing file when I'm on TWRP, and my device is recognised by my computer

Try shutting your phone off, and once its completely shut off, press the power and volume down button. Once the boot menu comes up (it will say recovery, fastboot etc) try it again.
Sent from my HTC One using Tapatalk

g2tegg said:
Try shutting your phone off, and once its completely shut off, press the power and volume down button. Once the boot menu comes up (it will say recovery, fastboot etc) try it again.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I'm at the bootloader now, but when I try to push the file through ADB it says error: device not found.

There might be a problem with your adb drivers. Are you in Toronto area?
Sent from my HTC One using Tapatalk

g2tegg said:
There might be a problem with your adb drivers. Are you in Toronto area?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Oh, Nope I live in Brampton

I'm in Niagara lol. I could use team viewer but that's up to you.
Sent from my HTC One using Tapatalk

g2tegg said:
I'm in Niagara lol. I could use team viewer but that's up to you.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Anything that will make my HTC One work again

g2tegg said:
I'm in Niagara lol. I could use team viewer but that's up to you.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
That means yes xD, just reply whenever you want to

PM sent
Sent from my HTC One using Tapatalk

How did it go?

SaHiLzZ said:
How did it go?
Click to expand...
Click to collapse
It's not fixed yet

SaHiLzZ said:
How did it go?
Click to expand...
Click to collapse
Hey, I've tried your tutorial before but no luck , If you can can you walk me through it? step by step? My HTC One has no OS though and is unable to flash ROMs since it's unable to mount '/data' or internal storage.

MSumthing said:
Hey, I've tried your tutorial before but no luck , If you can can you walk me through it? step by step? My HTC One has no OS though and is unable to flash ROMs since it's unable to mount '/data' or internal storage.
Click to expand...
Click to collapse
what do mean unable to mount /data
did you try sideloading: http://forum.xda-developers.com/showthread.php?t=2317986
if need be, update HTC Drivers, adb sdk, and recovery.

nkk71 said:
what do mean unable to mount /data
did you try sideloading: http://forum.xda-developers.com/showthread.php?t=2317986
if need be, update HTC Drivers, adb sdk, and recovery.
Click to expand...
Click to collapse
When I try to flash a ROM throught TWRP, TWRP would fail and give an error saying "E: Unable to mount /data" & "E: Unable to mount internal storage"
I've also tried sideload but during the sideloading it would stop and give an rror of "failed to write data protocol fault"

MSumthing said:
When I try to flash a ROM throught TWRP, TWRP would fail and give an error saying "E: Unable to mount /data" & "E: Unable to mount internal storage"
I've also tried sideload but during the sideloading it would stop and give an rror of "failed to write data protocol fault"
Click to expand...
Click to collapse
you want to check partitions? it's a bit low level, so no rushing stuff, OK!!
reboot to recovery (it is stable right, no random reboots), then make sure adb devices sees your phone, then:
adb shell
~ # cat /proc/emmc
~ # mount
stay in the shell, and copy/paste (no screenshot, just copy/paste the command prompt) output and we'll continue.

nkk71 said:
you want to check partitions? it's a bit low level, so no rushing stuff, OK!!
reboot to recovery (it is stable right, no random reboots), then make sure adb devices sees your phone, then:
adb shell
~ # cat /proc/emmc
~ # mount
stay in the shell, and copy/paste (no screenshot, just copy/paste the command prompt) output and we'll continue.
Click to expand...
Click to collapse
Hey, sorry for delayed reply, my HTC One had no battery. what do you mean by checking partitions? and yes ADB sees my phone.

[jem][CWM Advanced Edition] PhilZ Touch

Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
To take a screen shot, just long press outside a menu (2 sec and slightly change pressure after the delay)
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Credits @Hashcode
Download links
Last version can be found here:
Amazon Kindle Fire HD 8.9" (jem)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
XDA:DevDB Information
[jem][CWM Advanced Edition] PhilZ Touch, a Tool/Utility for the Amazon 7" Kindle Fire HD
Contributors
Phil3759, Hashcode
Version Information
Status: Stable
Created 2014-04-17
Last Updated 2014-04-20

Hello Phil,
I tested the recovery out, and it doesn't seem to bring the display up.
The error message that jumps out at me in the recovery.log is:
E:Error connecting to Vold! (No such file or directory)
E:Error in select (Invalid argument)
E:Error connecting to Vold! (No such file or directory)
E:Unable to send command to vold!
E:Error connecting to Vold! (No such file or directory)
E:Error in select (Invalid argument)
E:Error connecting to Vold! (No such file or directory)
Nothing really of note in kmsg or elsewhere.
Thoughts?

Hashcode said:
Hello Phil,
I tested the recovery out, and it doesn't seem to bring the display up.
The error message that jumps out at me in the recovery.log is:
E:Error connecting to Vold! (No such file or directory)
E:Error in select (Invalid argument)
E:Error connecting to Vold! (No such file or directory)
E:Unable to send command to vold!
E:Error connecting to Vold! (No such file or directory)
E:Error in select (Invalid argument)
E:Error connecting to Vold! (No such file or directory)
Nothing really of note in kmsg or elsewhere.
Thoughts?
Click to expand...
Click to collapse
The screen is black?

nice to see your recovery for KFHD. :good:
is this for tablets in landscape mode?

Phil3759 said:
The screen is black?
Click to expand...
Click to collapse
Yeah screen is black but I have adb access.

Would it help if I ran some tests of the jem/tate repos against standard CWM?
I'm not sure those have been built as I've been keeping all the kindles on TWRP (mainly due to the original Kindle Fire's not having volume keys)

Hashcode said:
Would it help if I ran some tests of the jem/tate repos against standard CWM?
I'm not sure those have been built as I've been keeping all the kindles on TWRP (mainly due to the original Kindle Fire's not having volume keys)
Click to expand...
Click to collapse
ah, sorry
I thought you had a working cwm when I saw a device tree that was looking properly done
If you have no CWM, you cannot run this as it is a cwm mod
However, it is probably just a graphics issue if adb is working

Phil3759 said:
ah, sorry
I thought you had a working cwm when I saw a device tree that was looking properly done
If you have no CWM, you cannot run this as it is a cwm mod
However, it is probably just a graphics issue if adb is working
Click to expand...
Click to collapse
I sync'd up my recovery init.rc files so that CWM can be built as well as TWRP from the same tree.
Let's see if Philz now works as well.

Update 6.27.2
Hope it works

Phil3759 said:
Update 6.27.2
Hope it works
Click to expand...
Click to collapse
Works!
Couple notes:
- There's a minor bit of artifacting along the camera edge of the LCD for a moment before the main UI is shown. It goes away so it's a minor issue.
- Touch works
- Button navigation works
- Screen dimming via timeout works
- Battery % shows as "0%" the sysfs entry is non-standard: /sys/class/power_supply/bq27541
- Time is UTC (wasn't sure where to set that to PDT to check valid time, but I think I'm 7-8 hours off of UTC which would be close)
I didn't get a chance to flash anything with it as I had a phone call.

Hashcode said:
Works!
Couple notes:
- There's a minor bit of artifacting along the camera edge of the LCD for a moment before the main UI is shown. It goes away so it's a minor issue.
- Touch works
- Button navigation works
- Screen dimming via timeout works
- Battery % shows as "0%" the sysfs entry is non-standard: /sys/class/power_supply/bq27541
- Time is UTC (wasn't sure where to set that to PDT to check valid time, but I think I'm 7-8 hours off of UTC which would be close)
I didn't get a chance to flash anything with it as I had a phone call.
Click to expand...
Click to collapse
Thank you a lot
Will add credits in OP
Will fix battery path too
Time can be setup under GUI Settings

Phil3759 said:
Update 6.27.2
Hope it works
Click to expand...
Click to collapse
Flashed a ROM just now and it seemed to work just fine.

It works.
Thanks phil and hashcode

Hashcode said:
Flashed a ROM just now and it seemed to work just fine.
Click to expand...
Click to collapse
About battery path
I try to read this:
Code:
"/sys/class/power_supply/bq27541"
Should I append a 'capacity' at the end?
Code:
BATTERY_LEVEL_PATH := "/sys/class/power_supply/bq27541/capacity"

6.27.3 Update
- fix display of battery capacity

screen capture is working?

Added again credits to @Hashcode
Seems like editing project always kills credits and bottom of post

Phil3759 said:
Added again credits to @Hashcode
Seems like editing project always kills credits and bottom of post
Click to expand...
Click to collapse
Not sure if this is whats happening to you. But I notice if I use the normal post edit link on a DevDB project. Make some changes.
Then use the project "edit" button and make some more changes. You'll lose the changes you made the first time.
Sent from my SM-N900V using Tapatalk

Hashcode said:
Not sure if this is whats happening to you. But I notice if I use the normal post edit link on a DevDB project. Make some changes.
Then use the project "edit" button and make some more changes. You'll lose the changes you made the first time.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Exactly what is happening to me

FYI: Newest recovery file: philz_touch_6.48.4-jem.img doesn't have a portion of the exploit in it, so that it stays on the Yellow "Kindle Fire" screen and never gets to the 2nd-bootloader.
It's fine